ffvfw

[sh0dan]

@milan: Sorry about the older libraries - I just copied the libraries from the last build, because I didn't know where to get them. I don't have access to the system that compiles this, as I'm on my backup computer at home.
I think someone with the proper setup should do a binary - I'll update the one on the site, when you post it.

[Kamui-Dash]

This is pretty dumb but I was wondering if any1 got 2pass working from jobcontrol? I usually gets PARSE ERROR. Does any1 knows what this means?

[grabengulli]

I try to compile the libavcodec_enc.dll but i have had an error:

ffvfw\src\ffmpeg\libavcodec\ratecontrol.c(131) : error C2520: conversion from unsigned __int64 to double not implemented, use signed __int64

what can i do?

thanks,
GrGu

[athos]

Originally posted by grabengulli
I try to compile the libavcodec_enc.dll but i have had an error:

ffvfw\src\ffmpeg\libavcodec\ratecontrol.c(131) : error C2520: conversion from unsigned __int64 to double not implemented, use signed __int64

what can i do?

thanks,
GrGu

Do you compile with gcc? what version?
I suggest you use gcc for this (libavcodec, mplayer and libmpg2), as parts of the code is hand-optimized in assembler. If you use VC++, these parts will be unoptimized, or rather only the usual automatic optimizations by the compiler. I have compared using gcc and intel c++ compiler in vc++, and gcc is a lot faster thanks to the assembly parts.

[grabengulli]

I have tried it with gcc and all works fine. Thanks.

Grgu

[milan]

@kempfand
I wanted that registry entry to be added by installer, but then ffvfw was reported twice by VirtualDub and other VFW software so I decided to not do this.

@sungey
Stats files produced by ffvfw should be compatible with those produced by XviD. However ffvfw doesn't fill kblk, mblk and ublk fields. If needed I could fix that.

@grabengulli
Which Visual C++ version are you using? I just tested it with VC6+SP5+Processor pack and it compiles fine. Of course GCC is preferred compiler for libavcodec, but I want it to be compileable using VC too.

@Bach, @Kamui-Dash
I'll check that immediately.

[milan]

@Bach
I'm not able to get that error. Please try to capture debug data using DebugView (www.sysinternals.com), maybe there will be something useful.

@Kamui-Dash
Which version of VirtualDub are you using? ffvfw state data are quite long (usually about 1500 bytes) and maybe not every VirtualDub version is able to handle that. I just tested VirtualDubMod 1.4.13 and it works fine.

BTW I updated ffvdub and had similar problem storing the filter data to allow scripting support. The buffer supplied by VirtualDubMod was not big enough.

[Blight]

milan:
are you keeping tabs on the ffdshow thread? there are a few bugs I've reported that could use resolving.

[milan]

I'm now focused more on ffvfw. I know about ffdshow issues which need to be solved, but I'd like to do that after ffvfw release.

[Kamui-Dash]

I used a vdub ver where i first copied the vdub files in nandub folder than vdubmod in it afterwards. The problem has been solved after I installed vdub in its own folder.

[JasonFly]

What does really mean Divx3 when choosing the encoder setting.
Does it mean that the movie will be encoded whith ffvfw and will only have a div3 fourcc or does it mean that you can encode in divx3 with ffvfw?

[milan]

When selecting Divx3 ffvfw uses libavcodec to encode video to DivX 3 compatible format. You should be able to decode it by the original DivX 3.11 codec. Same goes to MSMPEG4v2, however older versions of libavcodec produced buggy streams.

[grabengulli]

Originally posted by milan
@grabengulli
Which Visual C++ version are you using? I just tested it with VC6+SP5+Processor pack and it compiles fine. Of course GCC is preferred compiler for libavcodec, but I want it to be compileable using VC too.

I use VC6+SP5 but without the Processor pack . Only with MASM & NASM.

[milan]

Then try to install the processor pack or at line 69 of ffvfw/src/ffmpeg/libavcodec/common.h (applies to current CVS) change

# define uint64_t_C(c) (c ## ui64)

to

# define uint64_t_C(c) (c ## i64)

However I don't know how it will affect the encoding, but I guess it should be OK. Even in ffmpeg CVS the i64 suffix is present, I changed it only in ffvfw CVS copy of libavcodec.

[LigH]

Nitrogen's mirror seems to be dead, but the greek Pathfinder is still alive:

http://homepages.pathfinder.gr/ffvfw

[unixfs]

Hi,

using ffvfw-20030325.exe (15/4 release crashes when using mpeg2enc)
I made a couple of short two-pass encoding of a black and white movie and a cartoon, using mpeg2enc-mpg1 and the following settings:

resolution: 352x288, search-radius 32, 4x4: 2, 2x2: 2, no alt-curve, payback proportionally, 772 kb/s, output to an external file.

I compared the output of both with the corresponding encodings made using libavcodec's MPEG1; to me it seems that mpeg2enc's results are
quite superior, but are much slower (roughly 9 fps during both passes on my Athlon XP 1500+). Surely it's a good solution for making VCDs without using TMPG.

@milan: as far as I know mpeg2enc doesn't support 2-pass encoding natively, is it a feature that you added? It's great!.

Can it be made faster?

Thanks very much for you excellent work.

[milan]

I didn't performed any comparison of libavcodec mpeg1 encoding and mpeg2enc. I added mpeg2enc because I wanted to have an MPEG2 encoder in ffvfw and when Nic released his mpeg2enc compile I tested it and it seemed quite good to me.

I don't know if I can make it faster. Maybe it'd be useful to replace mpeg2enc quantization and DCT routines with those from libavcodec, but I don't think I'm capable of doing this now.

mpeg2enc two pass encoding uses the XviD two pass code. I find it very flexible and using it for Theora too. However this code doesn't have option for setting minimum bitrate which would be probably useful for MPEG1/2 encoding.
In MJPEGtools CVS log I saw that the mpeg2enc developers are implementing their own two pass encoding routines.

[sungey]

EDIT : wrong forum ... sorry

[grabengulli]

Originally posted by milan
Then try to install the processor pack or at line 69 of ffvfw/src/ffmpeg/libavcodec/common.h (applies to current CVS) change

# define uint64_t_C(c) (c ## ui64)

to

# define uint64_t_C(c) (c ## i64)

However I don't know how it will affect the encoding, but I guess it should be OK. Even in ffmpeg CVS the i64 suffix is present, I changed it only in ffvfw CVS copy of libavcodec.

I have tried it but it dosn't work. I have had the same error like before. I think this is an error at Visual Studio on my PC and not in the Source Code, because yesterday I had the same error in an other Source Code.

GrGu

[downloada]

hi,

i don't know if this has been posted in this thread before (if it's been, than sorry!), but i have a problem with the 2003-03-25-version of ffvfw.

since i installed that version, everytime i open the "compression"-dialog in vdub/vdubmod, an error message saying msvcrtd.dll was missing pops up twice, the same thing happens when clicking on ffvfw in that dialog. i don't have that .dll on my pc and i couldn't find it on the net, so i don't know what would happen if i put that dll in my windir.

i didn't encode with it (just installed it because it was needed for one ffdshow-version), but it's impossible to do an automated encode via gordianknot with this errormessage, because i have to click it away twice. for now, i have uninstalled it and everything works fine, so it has to be a problem with ffvfw.

cu