Here is the preset for AVI XviD fullscreen in WinFF:
-f avi -r 29.97 -vcodec libxvid -vtag XVID -vf scale=640:480 -aspect 4:3 -maxrate 1800k -b:v 1500k -qmin 3 -qmax 5 -bufsize 4096 -mbd 2 -bf 2 -trellis 1 -flags +aic -cmp 2 -subcmp 2 -g 300 -acodec libmp3lame -ar 48000 -b:a 128k -ac 2
Does anyone know how to make the audio CBR, pls? I've googled several times and have found various commandline options but it's all very confusing. The above works but outputs VBR which I don't need or want.
Thanks so much in advance! I find commandline very confusing as you're given so many options in many "tutorials" but so little actual working examples and none that talk about CBR when dealing with the rest of the code for video <sigh>
+ Reply to Thread
Results 1 to 12 of 12
Thread: CBR audio in WinFF?
Yes, what Chug a Bug has suggested above is true.
The version of FFmpeg that's supplied with WinFF-1.4.2 does show VBR instead of CBR.
Find ffmpeg.exe in your Program Files > WinFF folder and replace it with the latest version from Zeranoe.com.
Here ---> http://ffmpeg.zeranoe.com/builds/
This will cure the VBR problem, but some of WinFF's presets might not work properly with a different version of FFmpeg...
(For example, libfaac is not included with zeranoe's FFmpeg).
VirtualDub pops up error messages, too, with VBR audio and it's not a question of just switching that error off. Since I do a lot of slicing up with VirtualDub, I've learned that anything it likes plays well on my media devices whereas what it doesn't like, I invariably have troubles with audio synch (media devices - i.e., standalone DVD player, media player, flat screen TV with USB support).
I'll pop on over today to that link to get the new FFmpeg. That part is easy. But with regards to the presets, if that Widescreen ones works with CBR audio, that's all I need.
With regards to the DLL, should be a simple matter to pull it from another folder. I remember seeing it in another vid conversion app's folder.
Are these the only problems encountered, a missing DLL and presets that may not work, when replacing the FFmeg.exe in the WinFF folder?
I got the new FFmpeg.exe file and found several versions of the dll you mention - actually, 7 of my other vid conversion apps had it so I just chose the largest and latest version and copied that into the WinFF fldr <g>. I'm just ran a preview of an AVI to convert when I saw this yellow error line:
-t is not an input option, keeping it for the next output; considering fixing your command line.
which makes me realize something ... AutoGK produces a nice log file so you have an idea of any errors AGK encounters (too bad AGK only handles AVIs!!!!!!). Is there a switch or something that will output a "log" for each converted AVI that we can add to the WinFF preset somehow? Or is there someway to retrieve the conversion info in some other way?
GSpot says audio is CBR but it would be nice not to have the error pop up in VirtualDub nonetheless ...
I just spent several hours converting files and all of them have the same problem showing VBR instead of CBR audio.
Does anyone know how to definitively fix this issue, by any chance?
I dl this FFmpeg version from the above-mentioned page: FFmpeg git-c995644 32-bit Static (Latest) (2012-11-05)
Did the thought ever occur to you to VirtualDub might be wrong? I find it VERY interesting that you have concluded that VirtualDub is perfect and unable to make any mistakes. I second what bat999 says. And the fact that Gspot has a different answer than virtual dub is further proof that my first sentence might be right.
This is an interesting one. So I did a test encode myself and sure enough VirtualDub reports a warning about VBR but MediaInfo reports it as CBR.
So out of curiousity I demuxed the mp3 audio with VirtualDubMod, fed it into mp3DirectCut, then saved it without modifying anything, remuxed it back into the AVI with VirtualDubMod again and fed it into VirtualDub and, hey presto, no warnings this time, everythings hunky dory.
I figured that mp3DirectCut would output a "clean" version of the MP3 and fix any oddities that ffmpeg introduced into the headers etc, which proved to be the case, no transcoding necessary.
Personally though I wouldn't be using FFmpeg to transcode video tbh, there are better tools out there, its a jack of all trades, but master of none.
Last edited by Chug a Bug; 13th Nov 2012 at 20:59.