nvrec-open Mailing List for NewVideoRecorder

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

Hello,

I've gone through steps 1-5 in the INSTALL file, but now don't know how 
to run the program.

Can you help me out, please?

Thanks,

Greg

Hi all:
I've created a new branch of nvrec in
http://bitbucket.org/abeamud/nvrec2/ using mercurial.

This branch, is focused only in ffmpeg libs. I've cleaned all the rest
of the encoders like (nuv, divx4, etc..), avilib support...
Only the ffmpegrec binary is generated and works with last (yesterday)
versions of libavformat, libavcodec, etc...

ffmpeg provides a lot of codecs a formats, that's the reason to not
maintain divx4 support, for example, because libavcodec has a better
mpeg4 codec.

If you want to test it, patch it or other type of collaboration, you are
welcome.

Greetings.

PD: comments, suggestions...

Hi all:
I've created a new branch of nvrec in 
http://bitbucket.org/abeamud/nvrec2/ using mercurial.

This branch, is focused only in ffmpeg libs. I've cleaned all the rest 
of the encoders like (nuv, divx4, etc..), avilib support...
Only the ffmpegrec binary is generated and works with last (yesterday) 
versions of libavformat, libavcodec, etc...

ffmpeg provides a lot of codecs a formats, that's the reason to not 
maintain divx4 support, for example, because libavcodec has a better 
mpeg4 codec.

If you want to test it, patch it or other type of collaboration, you are 
welcome.

Greetings.

PD: comments, suggestions...

Мой новый адрес - il...@tr.... 

My new email address  is il...@tr....

Same drill, different target:
Divxfile support was unmaintained, non-working, and obsoleted by ffmpeg. 
In order to clean up the nvrec code base, support for avifile divx has 
been removed from the SVN. Users needing divxrec should use older releases.

-- Heikki Lindholm

Мой новый адрес - il...@tr.... 

My new email address  is il...@tr....

Librte support was unmaintained, non-working, and in my opinion 
obsoleted by ffmpeg. In order to clean up nvrec code base, support for 
librte has been removed from the SVN. Users needing rterec should use 
older releases.

-- Heikki Lindholm

Hi,

Purchase your medication from our site because it costs less.

http://www.vodrx*.com - Remove "*" to make the link working!

--

ferret? Well, it might be easier to get past a dragon if he were a
ferret, Harry thought dully, hed be smaller, much less easy to see from
a height of fifty feet..

Good day,

VlA_AGRA  $1, 80
ClA_ALIS  $3, 00
LEV_VlTRA $3, 35

http://www.printeryml*com
( Important ! Replace "*" with "." )

--
fairly well.
Hope its Angelina,  said Fred as Harry, Ron, and Hermione sat down.
So do I!  said Hermione breathlessly. Well, well soon know! 

Still trying to work through upgrading a box that does nvrec on two cards
from linux 2.4 to 2.6.

The devil seems to be in the details, as always.

I am using nvrec-20030316 and ffmpegrec 0.4.6.

I realize these are not new versions, but as previously discussed, the
ffmpegs newer than 0.4.8 have an msmpeg4v2 bug, and this is the newest
combination of the two that seems to compile and run. (advice here
welcome)

When both encoders are running, it can go for a period of time, but then
it starts filling the logs with:

Jun 26 04:40:52 pod25 kernel: bttv0: timeout: drop=1250287
irq=9624018/34603968, risc=1c07507c, bits: VSYNC HSYNC OFLOW FDSR
Jun 26 04:40:52 pod25 kernel: bttv0: reset, reinitialize
Jun 26 04:40:52 pod25 kernel: bttv0: PLL can sleep, using XTAL (28636363).
Jun 26 04:41:05 pod25 kernel: bttv1: timeout: drop=2740513
irq=4704839/298681652, risc=1c0d007c, bits: VSYNC HSYNC OFLOW FDSR
Jun 26 04:41:05 pod25 kernel: bttv1: reset, reinitialize

...and nvrec never exits. (despite being told to run just a certain number
of frames)

  Since nvrec never exits, then no other recordings take place and both
encoders are hung until restarted.

  Note that this does not occur with linux 2.4.x.

  I realize these are "old version" and this is primarily a kernel/bttv
thing and not an nvrec thing. However, has this been noted before and is
there a workaround?

  I am just having a whale of a time trying to upgrade this box to 2.6
(for other reasons) and keep the video recording working.

El mi=E9, 29-06-2005 a las 09:15 +0300, Yurii Sokolov escribi=F3:
> Hello all,
> I tried to start capture by "divx4rec  -xvid -o output.avi" and saw
> the message "can not open output.avi - no such file or directory".
> What to do?

What version of nvrec are you using?
Can you paste all the command output...?
XVID (for now) is unsupported in the lastest version of nvrec...

Greetings.

Hello all,
I tried to start capture by "divx4rec  -xvid -o output.avi" and saw the =
message "can not open output.avi - no such file or directory". What to =
do?
El mi=E9, 22-06-2005 a las 11:55 -0400, Trevor Boicey escribi=F3:
> Antonio Beamud Montero wrote:
> > Yes, this is a known problem, I have been recording with nvrec and al=
sa
> > with two sound cards, but three hours later the driver starts to repo=
rt
> > some problems and the recording stopped...
> >=20
> > When I have more time I'll try to debug this issue.
>=20
>    OSS seems to work fine, so no biggie.
>=20
>    Although... I spoke too soon. Still more troubles, although probably=
=20
> not nvrec more likely ffmpeg.
>=20
>    Whenever I try to output to mspeg4v2, the image is distorted from=20
> about the middle down. All other codecs work fine, but that one breaks.=
=20
> (and spits out many "dct cliped" messages).
>=20
>    I found a page using google yesterday where another user had the sam=
e=20
> problem on ffmpeg > 0.4.8. Strangely, I can't google that page today.
>=20
>    Anyways, so I attempted to go back to ffmpeg 0.4.8, but then I have=20
> to keep chasing my tail backwards to find nvrecs that will compile with=
=20
> older ffmpegs.

Well, ffmpeg in every new version introduces new api changes, and I have
to review all the code to compile with the last release. The best is to
use the ffmpeg-0.4.9pre1.

>    I ended up back at ffmpeg-0.4.6 and nvrec-20030316 in order to get i=
t=20
> working. :<
>=20
>    At least it works again and now with v4l2 and kernel 2.6.11.12, but =
I=20
> was hoping to be a lot more current.

nvrec-cvs + ffmpeg-0.4.9pre1 +  kernel > 2.6.8 must works without
problem.=20

Greetings.

Antonio Beamud Montero wrote:
> Yes, this is a known problem, I have been recording with nvrec and alsa
> with two sound cards, but three hours later the driver starts to report
> some problems and the recording stopped...
> 
> When I have more time I'll try to debug this issue.

   OSS seems to work fine, so no biggie.

   Although... I spoke too soon. Still more troubles, although probably 
not nvrec more likely ffmpeg.

   Whenever I try to output to mspeg4v2, the image is distorted from 
about the middle down. All other codecs work fine, but that one breaks. 
(and spits out many "dct cliped" messages).

   I found a page using google yesterday where another user had the same 
problem on ffmpeg > 0.4.8. Strangely, I can't google that page today.

   Anyways, so I attempted to go back to ffmpeg 0.4.8, but then I have 
to keep chasing my tail backwards to find nvrecs that will compile with 
older ffmpegs.

   I ended up back at ffmpeg-0.4.6 and nvrec-20030316 in order to get it 
working. :<

   At least it works again and now with v4l2 and kernel 2.6.11.12, but I 
was hoping to be a lot more current.

-- 
Trevor Boicey, P. Eng.
Ottawa, Canada, tb...@br...
ICQ #17432933 http://www.brit.ca/~tboicey/

El mar, 21-06-2005 a las 13:50 -0400, Trevor Boicey escribi=F3:
> Trevor Boicey wrote:
> >   I tried upgrading it to kernel 2.6.11, and it works for one card bu=
t=20
> > if I try to start recording from the second card, it never makes the=20
> > output file... it just pauses for a few seconds then starts spitting =
out=20
> > that "No place to put data - discarding 0" message until stopped.
>=20
>    A workaround seems to be using -ua oss instead of -ua alsa. Then it=20
> will work in parallel nicely.

Yes, this is a known problem, I have been recording with nvrec and alsa
with two sound cards, but three hours later the driver starts to report
some problems and the recording stopped...

When I have more time I'll try to debug this issue.

>    Many thanks, Antonio.
>=20

Greetings

Trevor Boicey wrote:
>   I tried upgrading it to kernel 2.6.11, and it works for one card but 
> if I try to start recording from the second card, it never makes the 
> output file... it just pauses for a few seconds then starts spitting out 
> that "No place to put data - discarding 0" message until stopped.

   Wait, I think I solved this problem as well as a lot of the build 
problems I have been having.

   Slackware created a directory /usr/include/linux that had in it, 
among other things, a videodev.h. This is a copy of the videodev.h from 
2.4.29.

   When I upgraded to 2.6.x, or patched with kraxel-patch, that file was 
still getting referenced by nvrec rather than the proper one in the 
kernel build tree.

   So... it wasn't correctly building for v4l2, and probably had some 
bad constants and #defines that was causing all of the invalid arguments.

   So at least from loose testing, I have it working with 2.6.x, ffmpeg 
0.4.9-pre1, and nvrec CVS latest.

   Something small is happening though that is perhaps worth reporting.

   With 2.4.x and v4l1 I can capture on two cards at once without issue.

   However, with this build, the second one blocks on audio, strace 
shows it blocking on open("/dev/snd/pcmC0D0c", O_RDRW). It will block 
there until the other capture stops.

   A workaround seems to be using -ua oss instead of -ua alsa. Then it 
will work in parallel nicely.

   Many thanks, Antonio.

-- 
Trevor Boicey, P. Eng.
Ottawa, Canada, tb...@br...
ICQ #17432933 http://www.brit.ca/~tboicey/

Antonio Beamud Montero wrote:
> it's usage is proffesional or home made?

   No no just a PC to record TV, not making a set top box or anything.

   When I said "build a box" I didn't mean actually physically build 
one, I just mean to configure a linux box specifically for nvrec.

> How many hours do you want to record without stop?

   Well, TV shows, so... an hour? Maybe two?

   But I would like to be able to use more than one card at a time.

   I have that working system I talked about before, kernel 2.4.26, 
ffmpeg 0.4.9-pre1, nvrec-cvs current, and it works fine and does more 
than one show at a time using two cards. But I would like to upgrade 
that box.

   I have some other unrelated issues on it that would be helped if I 
upgraded it. The box does a few other things (like X10 control).

   However, the nvrec/bttv system seems a little finnicky. I seem to 
need to try a lot of versions and compiles and tests to get a working combo.

   I tried upgrading it to kernel 2.6.11, and it works for one card but 
if I try to start recording from the second card, it never makes the 
output file... it just pauses for a few seconds then starts spitting out 
that "No place to put data - discarding 0" message until stopped.

   The output file isn't even created, which seems strange.

   I would also like to use v4l2 (so I can monitor with xawtv while it's 
recording), but if I attempt to build for v4l2 it seems to try doing a 
v4l1 core init anyways and then fails with invalid argument on set window.

   Rather than send a list of complaints to this list, I figure I would 
build the box freshly using a new deployment and whatever versions of 
kernel/bttv/ffmpeg/nvrec are known to work together well.

-- 
Trevor Boicey, P. Eng.
Ottawa, Canada, tb...@br...
ICQ #17432933 http://www.brit.ca/~tboicey/

El vie, 17-06-2005 a las 10:56 -0400, Trevor Boicey escribi=F3:
>    ...to continue an earlier discussion on build issues...
>=20
>    I am looking to build a box specifically for nvrec.
>=20
>    Is there any recommended version list for things like:
>=20
> - Kernel
> - bttv drivers
> - gcc
> - ffmpeg
> - ...etc?

it's usage is proffesional or home made?
How many hours do you want to record without stop?

>    I had some issues before as discussed but was able to get a working=20
> system. I would like to start again and try to have the best system=20
> possible and then hopefully be able to use the newest drivers and such.
>=20
>    Cheers.
>=20

   ...to continue an earlier discussion on build issues...

   I am looking to build a box specifically for nvrec.

   Is there any recommended version list for things like:

- Kernel
- bttv drivers
- gcc
- ffmpeg
- ...etc?

   I had some issues before as discussed but was able to get a working 
system. I would like to start again and try to have the best system 
possible and then hopefully be able to use the newest drivers and such.

   Cheers.

-- 
Trevor Boicey, P. Eng.
Ottawa, Canada, tb...@br...
ICQ #17432933 http://www.brit.ca/~tboicey/

Antonio Beamud Montero <antonio@li...> wrote:

>  the ffmpeg directory must be at the same level as nvrec, not in the
>  nvrec source directory, ie:
>  
>   ffmpeg/   nvrec/ 

Thank you, nvrec wanted a link to the DIRECTORY, not to the PROGRAM
ffmpeg. That cured that.

> What version of divx4linux are you using?

The one I downloaded from www.divx.com/divx/linux, 5.0.5. The tarfile
is called divx4linux-std-20030428.tar.gz, and in decore.h there
is a line

decore.h:#define DECORE_VERSION         20021112

Yours,

-- Howard

------------------------------------------------------------------------
Dipl.-Phys. H. Schultens                            Tel: +49 551 39-5914
Zentrum Physiologie                                 Fax: +49 551 39-5923
Humboldtallee 23                           eMail: hschult(at)gwdg(dot)de
37073 Goettingen     WWW: http://www.neuro-physiol.med.uni-goettingen.de
Germany
------------------------------------------------------------------------

El vie, 03-06-2005 a las 14:32 -0400, Trevor Boicey escribi=F3:
> > Try using cvs version of nvrec and stable version os ffmpeg.
>=20
>   Ok.
>=20
>   ffmpeg-0.4.9-pre1 and nvrec cvs compiled on one machine that has gcc-=
3.3.4.
>=20
>   On another machine that has gcc 2.95.3, compile failed with:
>=20
> nuvfile_core.c: In function `nuvfile_core_rotate':
> nuvfile_core.c:222: parse error before `char'
> nuvfile_core.c:224: `name_buffer' undeclared (first use in this functio=
n)
> nuvfile_core.c:224: (Each undeclared identifier is reported only once
> nuvfile_core.c:224: for each function it appears in.)
>=20
>   ...however this was trivially fixed by moving the declaration of "cha=
r
> *name_buffer;" up two lines to be above the "if(!nuvc)" code.
>=20
>   Might be worth changing in the code in order to let it compile with
> 2.95.3. As old as 2.95.3 is, it's worth keeping around because it is on=
e
> version of gcc that cleanly compiles MPlayer.

Ok, I have fixed it to compile with 2.95 gcc version... No problem at
all...

>   ...unless there is a later version of gcc that compiles all including
> MPlayer? I know the MPlayer docs are full of detailed problems that
> happen with certain versions of gcc, quite a headache.
>=20
>   I'll experiment with this and send you a trace offline if I can still
> make it crash doing asf.
>=20
>   Many thanks.
>=20
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.Net email is sponsored by: NEC IT Guy Games.  How far can you s=
hotput
> a projector? How fast can you ride your desk chair down the office luge=
 track?
> If you want to score the big prize, get to know the little guy. =20
> Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=3D20
> _______________________________________________
> Nvrec-open mailing list
> Nvr...@li...
> https://lists.sourceforge.net/lists/listinfo/nvrec-open

El lun, 06-06-2005 a las 10:51 +0200, Howard Schultens escribi=F3:
> Dear nvrec-open,
>=20
> with the last 2 releases of nvrec and the CVS version, I get the
> following error with ./configure
>=20
> *******************************************************
> configure: WARNING: ffmpeg not installed.  Download it from:
> configure: WARNING: http://ffmpeg.sf.net/
> configure: WARNING: Build it and create a symlink called ffmpeg in the
> configure: WARNING: same directory where the nvrec source directory is
> configure: WARNING: located.
> configure: WARNING: ffmpegrec will NOT be built.
> configure: WARNING: ***************************************************=
****
> configure: WARNING: ffmpeg-0.46+ not installed.  Download it from:
> configure: WARNING: http://ffmpeg.sf.net/
> configure: WARNING: Build it and create a symlink called ffmpeg in the
> configure: WARNING: same directory where the nvrec source directory is
> configure: WARNING: located.
> configure: WARNING: Image format conversion will not be available.
>=20
> I have installed the latest version of ffmpeg in /usr/local/bin and
> there is a symbolic link in the nvrec source directory.

the ffmpeg directory must be at the same level as nvrec, not in the
nvrec source directory, ie:

 ffmpeg/   nvrec/=20

> Further, all the versions of nvrec I tried bomb out of make with
> the error:
>=20
> In file included from aconv_mad.c:11:
> mcplay.h:16: error: parse error before "yuv_pic_t"
> mcplay.h:16: warning: type defaults to `int' in declaration of `yuv_pic=
_t'
> mcplay.h:16: warning: data definition has no type or storage class
> make[3]: *** [aconv_mad.o] Error 1
> make[2]: *** [all-recursive] Error 1
> make[1]: *** [all-recursive] Error 1
> make: *** [all] Error 2
>=20
> The erroneous line in mcplay.h is:
>=20
> #ifdef _DECORE_H_
>          typedef DEC_PICTURE yuv_pic_t;        <<<<<<<<<<<<<<<<<<<<<<<<
> #else
> #warning Including own yuv_pic definition!
>          typedef struct
>          {
>                  void *y;
>                  void *u;
>                  void *v;
>                  int stride_y;
>                  int stride_uv;
>          } yuv_pic_t;
> #endif /* decore.h */
>=20
> In other words, apparently decore.h (from divx4linux) does not contain
> a definition of DEC_PICTURE.

What version of divx4linux are you using?

> My operating system is SuSE Linux 9.0.
>=20
> Thanks for help.  Please reply to me directly, as I am not subscribed
> to the list.
> -- Howard
> -----------------------------------------------------------------------=
-
> Dipl.-Phys. H. Schultens                            Tel: +49 551 39-591=
4
> Zentrum Physiologie                                 Fax: +49 551 39-592=
3
> Humboldtallee 23                           eMail: hschult(at)gwdg(dot)d=
e
> 37073 Goettingen     WWW: http://www.neuro-physiol.med.uni-goettingen.d=
e
> Germany
> -----------------------------------------------------------------------=
-
>=20
>=20
> -------------------------------------------------------
> This SF.Net email is sponsored by: NEC IT Guy Games.  How far can you s=
hotput
> a projector? How fast can you ride your desk chair down the office luge=
 track?
> If you want to score the big prize, get to know the little guy. =20
> Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=3D20
> _______________________________________________
> Nvrec-open mailing list
> Nvr...@li...
> https://lists.sourceforge.net/lists/listinfo/nvrec-open

Dear nvrec-open,

with the last 2 releases of nvrec and the CVS version, I get the
following error with ./configure

*******************************************************
configure: WARNING: ffmpeg not installed.  Download it from:
configure: WARNING: http://ffmpeg.sf.net/
configure: WARNING: Build it and create a symlink called ffmpeg in the
configure: WARNING: same directory where the nvrec source directory is
configure: WARNING: located.
configure: WARNING: ffmpegrec will NOT be built.
configure: WARNING: *******************************************************
configure: WARNING: ffmpeg-0.46+ not installed.  Download it from:
configure: WARNING: http://ffmpeg.sf.net/
configure: WARNING: Build it and create a symlink called ffmpeg in the
configure: WARNING: same directory where the nvrec source directory is
configure: WARNING: located.
configure: WARNING: Image format conversion will not be available.

I have installed the latest version of ffmpeg in /usr/local/bin and
there is a symbolic link in the nvrec source directory.

Further, all the versions of nvrec I tried bomb out of make with
the error:

In file included from aconv_mad.c:11:
mcplay.h:16: error: parse error before "yuv_pic_t"
mcplay.h:16: warning: type defaults to `int' in declaration of `yuv_pic_t'
mcplay.h:16: warning: data definition has no type or storage class
make[3]: *** [aconv_mad.o] Error 1
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2

The erroneous line in mcplay.h is:

#ifdef _DECORE_H_
         typedef DEC_PICTURE yuv_pic_t;        <<<<<<<<<<<<<<<<<<<<<<<<
#else
#warning Including own yuv_pic definition!
         typedef struct
         {
                 void *y;
                 void *u;
                 void *v;
                 int stride_y;
                 int stride_uv;
         } yuv_pic_t;
#endif /* decore.h */

In other words, apparently decore.h (from divx4linux) does not contain
a definition of DEC_PICTURE.

My operating system is SuSE Linux 9.0.

Thanks for help.  Please reply to me directly, as I am not subscribed
to the list.

-- Howard
------------------------------------------------------------------------
Dipl.-Phys. H. Schultens                            Tel: +49 551 39-5914
Zentrum Physiologie                                 Fax: +49 551 39-5923
Humboldtallee 23                           eMail: hschult(at)gwdg(dot)de
37073 Goettingen     WWW: http://www.neuro-physiol.med.uni-goettingen.de
Germany
------------------------------------------------------------------------

> Try using cvs version of nvrec and stable version os ffmpeg.

  Ok.

  ffmpeg-0.4.9-pre1 and nvrec cvs compiled on one machine that has gcc-3.3.4.

  On another machine that has gcc 2.95.3, compile failed with:

nuvfile_core.c: In function `nuvfile_core_rotate':
nuvfile_core.c:222: parse error before `char'
nuvfile_core.c:224: `name_buffer' undeclared (first use in this function)
nuvfile_core.c:224: (Each undeclared identifier is reported only once
nuvfile_core.c:224: for each function it appears in.)

  ...however this was trivially fixed by moving the declaration of "char
*name_buffer;" up two lines to be above the "if(!nuvc)" code.

  Might be worth changing in the code in order to let it compile with
2.95.3. As old as 2.95.3 is, it's worth keeping around because it is one
version of gcc that cleanly compiles MPlayer.

  ...unless there is a later version of gcc that compiles all including
MPlayer? I know the MPlayer docs are full of detailed problems that
happen with certain versions of gcc, quite a headache.

  I'll experiment with this and send you a trace offline if I can still
make it crash doing asf.

  Many thanks.

El vie, 03-06-2005 a las 13:44 -0400, Trevor Boicey escribi=F3:
> > Use the last stable, and if you find problems compiling with it, send
> > me.
>=20
>   Ok, it's kind of a mess to explain because I've tried so many version=
s,
> but I did a quick run through and here's the status:
>=20
>   MOST LIKELY you will not care about all this debug information becaus=
e
> the versions I am trying to build against each other don't make sense,
> but for completeness:

Try using cvs version of nvrec and stable version os ffmpeg.

>=20
>   Using the latest latest of each (ffmpeg daily, nvrec by CVS) I get:
>=20
> if gcc -DHAVE_CONFIG_H -I. -I. -I.    -DFFMPEG -I../ffmpeg/libavformat
> -I../ffmpeg/libavcodec -DHAVE_CONVERT -O3  -mcpu=3Di686 -march=3Di686
> -funroll-loops -ffast-math -fomit-frame-pointer -fno-exceptions -pthrea=
d
> -D_FILE_OFFSET_BITS=3D64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -Wal=
l -MT
> ffmpegrec-ffmpegfile_core.o -MD -MP -MF
> ".deps/ffmpegrec-ffmpegfile_core.Tpo" -c -o ffmpegrec-ffmpegfile_core.o
> `test -f 'ffmpegfile_core.c' || echo './'`ffmpegfile_core.c; \
> then mv -f ".deps/ffmpegrec-ffmpegfile_core.Tpo"
> ".deps/ffmpegrec-ffmpegfile_core.Po"; else rm -f
> ".deps/ffmpegrec-ffmpegfile_core.Tpo"; exit 1; fi
> ffmpegfile_core.c: In function `ffmpeg_set_codec_video':
> ffmpegfile_core.c:154: error: structure has no member named `frame_rate=
'
> ffmpegfile_core.c: In function `copy_avcodec_context':
> ffmpegfile_core.c:169: error: structure has no member named `frame_rate=
'
> ffmpegfile_core.c: In function `ffmpegfile_core_init':
> ffmpegfile_core.c:615: error: structure has no member named `frame_rate=
'
> ffmpegfile_core.c:616: error: structure has no member named `frame_rate=
'
> ffmpegfile_core.c:617: error: structure has no member named `frame_rate=
'
> make[2]: *** [ffmpegrec-ffmpegfile_core.o] Error 1
> make[2]: Leaving directory `/root/builds/nvrec-cvs-20050603'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/root/builds/nvrec-cvs-20050603'
> make: *** [all] Error 2
>=20
>   ...probably the most sensible action would be to see why the two dail=
ies
> no longer like each other.

Well, ffmpeg guys change frecuently the libavcodec and libaformat
apis... soon, I'll review the code again...

>   Ideas?
>=20

2002	Jan	Feb	Mar	Apr	May	Jun (15)	Jul (49)	Aug (18)	Sep (9)	Oct (27)	Nov (44)	Dec (41)
2003	Jan (36)	Feb (21)	Mar (22)	Apr (56)	May (13)	Jun (31)	Jul (24)	Aug (22)	Sep (4)	Oct (12)	Nov (12)	Dec
2004	Jan (4)	Feb (2)	Mar (2)	Apr (5)	May	Jun (1)	Jul (4)	Aug (1)	Sep (9)	Oct (27)	Nov (2)	Dec (1)
2005	Jan (8)	Feb	Mar (8)	Apr (3)	May	Jun (30)	Jul	Aug	Sep	Oct	Nov	Dec
2007	Jan (2)	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov (4)	Dec
2009	Jan	Feb	Mar	Apr	May	Jun	Jul (2)	Aug	Sep	Oct	Nov	Dec
2011	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct (1)	Nov	Dec

nvrec-open Mailing List for NewVideoRecorder

nvrec-open — Open discussion and general help on NVrec.