f1tzi.the.cracker
30th June 2007, 19:18
I know this kind of behaviour from GordianKnot has been reported before, but I didn't really find any practical answers as to *why* this happens, or how to fix it.
I've been using GordianKnot successfully for some time, and it always predicted the size of the files very accurately. However, now without any apparent reason, the files turn out oversized. I ripped 50min episodes to 460MiB, and it worked fine. Then it just didn't. I didn't change any settings, nothing. Xvid always produced oversized files, which after joining the audio exceeded 600MiB! In GK I noticed weird behaviour in the resolution window... It allocated too many bits per pixel*frame, in relation to the chosen resolution. This behaviour came out of nowhere. I tried uninstalling the Xvid codec and then reinstall it, didn't help. I uninstalled GordianKnot rip pack and reinstalled, didn't have any effect either. Then I tried using DivX, and the files turned out fine (slightly undersized from what GK predicted). What the... I mean... It did seem like the problem was at least partially with GK, but then again Xvid just didn't encode the video according to the video size I specified on 2nd pass, which was the value from GK. Anyway GK+DivX seems to work.
Another question, about FFmpeg. I really don't know what I'm doing with it, but I tried playing around with it a little and googled some advise, and I thought I knew enough to at least produce encoded files with certain bitrate, but no. FFmpeg always used ~300 kbit/s for bitrate, without any interest in what I had inputted as "-b" parameter. I tried variable bitrate also, with different values, but it just didn't react to any bitrate suggestions from my part, EXCEPT when I used the "copy" value for vcodec parameter - then it copied the video source with bitrate around 5000-6000 kbit/s, though the source was around 8000 kbit/s (according to FFmpeg). So it was "all or nothing" with FFmpeg, practically. Also, in man page of FFmpeg it says about "-b" param: "Set the video bitrate in kbit/s (default = 200 kb/s)." - I've heard people say that it in fact interprets the value in bits/s, so I took that into account and played along with different values such as 1162000 and 1162k, but it always encoded at 200-300 kbit/s...
I input the command something like this: "ffmpeg -i input.m2v -vcodec mpeg4 -b 1162k out.avi"
I've been using GordianKnot successfully for some time, and it always predicted the size of the files very accurately. However, now without any apparent reason, the files turn out oversized. I ripped 50min episodes to 460MiB, and it worked fine. Then it just didn't. I didn't change any settings, nothing. Xvid always produced oversized files, which after joining the audio exceeded 600MiB! In GK I noticed weird behaviour in the resolution window... It allocated too many bits per pixel*frame, in relation to the chosen resolution. This behaviour came out of nowhere. I tried uninstalling the Xvid codec and then reinstall it, didn't help. I uninstalled GordianKnot rip pack and reinstalled, didn't have any effect either. Then I tried using DivX, and the files turned out fine (slightly undersized from what GK predicted). What the... I mean... It did seem like the problem was at least partially with GK, but then again Xvid just didn't encode the video according to the video size I specified on 2nd pass, which was the value from GK. Anyway GK+DivX seems to work.
Another question, about FFmpeg. I really don't know what I'm doing with it, but I tried playing around with it a little and googled some advise, and I thought I knew enough to at least produce encoded files with certain bitrate, but no. FFmpeg always used ~300 kbit/s for bitrate, without any interest in what I had inputted as "-b" parameter. I tried variable bitrate also, with different values, but it just didn't react to any bitrate suggestions from my part, EXCEPT when I used the "copy" value for vcodec parameter - then it copied the video source with bitrate around 5000-6000 kbit/s, though the source was around 8000 kbit/s (according to FFmpeg). So it was "all or nothing" with FFmpeg, practically. Also, in man page of FFmpeg it says about "-b" param: "Set the video bitrate in kbit/s (default = 200 kb/s)." - I've heard people say that it in fact interprets the value in bits/s, so I took that into account and played along with different values such as 1162000 and 1162k, but it always encoded at 200-300 kbit/s...
I input the command something like this: "ffmpeg -i input.m2v -vcodec mpeg4 -b 1162k out.avi"