"Requested bitrate is too low. Estimated minimum x kbps
Hi all. I am using the la-*test*-('") VFW build 600 and GordianKnot. I don't know why, but in the last month (when I was using the la-*test*-('") VFW builds from www.x264.nl), I am facing a strange error when I am encoding with x264, which wasn't there in the last year I am using it. This error came up relatively lately and is there for every VFW build I have tried (556, 573 and now 600). When the first pass is over, a pop-up window appears and says "Requested bitrate is too low. Estimated minimum x kbps". x is a different number every time, either too small or too high. In the same time, VirtualDubMod also pop-up an error with code -100, which I believe that is the result of the previous error. Very strangely, this damn error message was appearing at the same time (after the first pass) when I was encoding with x264 CLI using agkp add-on for GK. So I am sure that it is an encoder error (or a GK error?). Can someone help me with that? I am setting all the options in GK as usual, so I can't understand what is this. Thanks.

The APIs and internals of x264 have gone through revision somewhere down the line, and GK has been discontinued somewhere down the line, too. Since it doesn't seem to allow the user to set VfW-only settings--and rather tries to access everything itself through API, this poses a problem if any APIs change. I suggest for you to try to use an encoder that allows user control over the VfW selection process, and tell me the results. If the problem happens again with a different encoding program, let me know! After all, you could try to use a non-bitrate controlled mode like CQ, which doesn't depend on the bitrate and instead compressed the source video down to a certain specified quality level... By the way, Revisions after 586 are DTSUnited/KN exclusives and won't be appearing on x264.nl any more.

Hi DTS and congratulations for your excellent work! If I understood correctly, you are telling me that an internal change has been done in x264 and since then, the GK cannot use the codec, correct? I am using only bitrate-based modes in 2-pass. So I can't use GK anymore! If this is true, what other programs for x264 VFW do you know, which are so flexible as GK? (I am very curious about what program you personally use for your rippings). I have to add that I am in love with mkv, ogg vorbis, chapters etc. Can you explain what do you mean by this? Since it doesn't seem to allow the user to set VfW-only settings--and rather tries to access everything itself through API, this poses a problem if any APIs change. I suggest for you to try to use an encoder that allows user control over the VfW selection process GK provides access to the configuration panel of x264, so I can't understand what do you mean. Thanks.

GK works flawlessly with *all* vfw builds...API changes don't affect GK because it uses only vfw interface.

where can I find VFW source code?
I saw Cli has source code available. Where can I find vfw source for this specific VFW x264 edition? Thanks!

Thanks a lot! you gugs did a wonderful job.

Hi all. DTS, could you please answer to my questions? I tried with another one DVD and my problem persists (see my shots). Please answer to my previous post. 1) Is it possible these problems to be caused by the settings? I don't use the default x264 settings and I have modified slightly your guide's advices (for best quality). 2) I am confused by kurtnoise's comment. Kurtnoise, do you use the la-*test*-('") GK (0,35 v2) and the la-*test*-('") x264 VFW (r600) and you encode flawlessly? You didn't have any error? Here my shots: http://img87.imageshack.us/img87/9476/errorconsolewx0.jpg http://img183.imageshack.us/img183/6553/vdmerrorau6.jpg http://img183.imageshack.us/img183/1185/vdmcrashji3.jpg

Hmm, interesting that Vdub also throws an error. Please post the following information: 1. System information (OS, processor, RAM info, etc) 2. Version of VirtualDub used 3. The exact modifications you made to x264 settings 4. Colorspace and compression mode used (i.e. Fast Recompress, ..., Full Processing, and RGB32,...,YV12, etc) 5. What was the last x264 VfW build you used that worked? I hope I can help you address your problem, but I need this info first :) Thanks.

Hi DTS and thanks for your support. 1. Windows eXPerience SP2, P4@3,82 GHz with HT, 2 GB DDR@450 MHz DC, GeForce 7800GS+ AGP card, WD Raptor 74 GB HDD, Plextor 760SA DVD+RW. 2. VDM v1.5.10.2 build 2542 3. How can I send you some screenshots in a rar file? 4. I haven't used VirtualDub directly, just GK. How can I access this info? I don't know many about colorspaces. 5. I really don't remember (maybe 53x). I am not even sure if the problem started because of a new x264 build or because of something else. I mean that I am not 100% sure that it wasn't there at all eg at rev534 and was suddenly appeared at rev556. The first and second time I didn't pay any attention. But the last 1-2 months the problem is very sharp. I was trying to resolve it with a newer version, but this didn't help me. Thanks.

Well, I've looked but I still can't seem to be able to reproduce the bug. Is your (amazing) system stable? 3. Well, take screenshots of anything by pressing Print Scr (it's a key above the insert key on standard keyboards), opening Paint, pasting the screenshot in, and saving the files (jpg is small and good). Then of course, you can upload your rar of screenshots via rapidshare, megaupload, yousendit, or any free hosting site (or your own site) and drop me the link! Take as many screenshots as you can and put them into the rar--I don't mind a large filesize (though a bunch of .jpg would be nice). A lot of internals have changed since 534, so I can't pinpoint anything specific (and I'm not a core coder anyway). What happens if you try replacing the Virtualdubmod file with the la-*test*-('") regular VirtualDub (naming it exactly as Vdubmod was named)? It just might help, because VirtualDubMod 2542 (and the whole 1.5 core) is very, very old. PPS: Colorspace info is found here:

Hi, well i got the same problem. i started to encode a anime movie of 2 hours and 31 min. i use the standard settings. and i get that my bitrate is too low. it wanted to have a bitrate of minimal 1000000 kb i tried 1000, 1200 and 1700. i also get that -100 error. i got that error before like 8-9 times but then i just restart the encode with the same settings and its ok. but this time it didnt want to encode pass 2. im also using your la-*test*-('") build and gnot 0.35. gnot users vdubmod 1.5.10.2 edit: i tried the same movie but then only a 1 min of it on the same settings and it works fine. it seems it cant handle the long movie of 2 hour and 30 min. it always says bitrate too low requested or minimal is then between 1000000 and 1800000 kbs i use the partition descision on 6b. i might have to try me gui now but me gui didnt like me the last time :( edit2: i tried cuttin the movie in half and tried it again with the same settings still the same problem. i also tried with megui same problem i always get bitrate to low. is there any way to fix this. :( :( :(

there im back :P i did a few -*test*-('")s i took the same d2v file and different settings i used my normal settings 800 bitrate en on 6 and 6b i tried both give me bitrate too low. i tried it on 1(fas-*test*-('")) it went well. now im trying 6b again but with chroma me unchecked and it just past the first pass. so i think there is something wrong with the chroma me setting wrong. what even stranger is. i uninstall ed everything me-gui gnot x264 cccp mkv tool 1.7 and restart the computer. just installed your x264 build 600 and gnot rip pack for the rest nothing. the first encode went fine. even on 6b with chroma me checked. but then the second encode. same problem again. i also tried different files and d2v files. edit: after its doen at the end of the 2nd pass it gives that error again -100 error and that bitrate is too low..

Do you get the same error after you unchecked Chroma ME?

yes same error. what i did now was. uninstalled everything. reboot. install my x264 codec and gnot again. i used the same setting except the ivtc in avs i have unchecked and it encodes going good now.. when i check it it gives the same error again. but that option also makes the file smaller. i still dont know what the problem is or where the problem lies