Upgrade to GK 0.35.0 = problems, confusion

[pojke]

I upgraded from version 0.28.8 to version 0.35.0 but haven't gotten the new one to work properly.
Doom9 doesn't seem to have a guide for the new one so I followed the instructions here (http://www.rita.lt/guides/GKnot_MPEG2toAVI.htm).

I'm accustomed to adding the audio by selecting "size" and then the mp3 file (encoded in r4r), but the new intructions say to select "bitrate" and leave the audio encoding until the last steps. I'd prefer to have the audio encoding done first so that it could be part of the bitrate calculations.

I've been using a 30-second TV commercial (mpeg2, interlaced) as a test.
With version 0.28.8, GK produced a 1500K file with very good video quality, but the new version produces a 674K file that looks terrible no matter how I set the bit rate. I can set the target size to 5mb and it still produces the 674K file. The calculations under "Bits/(Pixel*Frame)" don't seem accurate at all. I used to be able to rely on the "load" number, which now, doesn't even appear until after the compressibility test.

Here's the log (http://204.127.198.24/~nonpc/pics/3-13gk.log):

Actually, I'd go back to the old version just to avoid all this, if I could find a way to get mpa audio to mp3 in that one.

Any solutions?

[jggimi]

...I'm accustomed to adding the audio by selecting "size" and then the mp3 file (encoded in r4r), but the new intructions say to select "bitrate" and leave the audio encoding until the last steps. I'd prefer to have the audio encoding done first so that it could be part of the bitrate calculations....Doom9's guide uses R4R, therefore the audio is already converted. Using "size" is correct in that case. If you use GK for audio conversion, using "bitrate" is the correct method, as you do not yet have a converted audio file to select. "Bitrate" estimates the audio file size....I can set the target size to 5mb and it still produces the 674K file....You should completely uninstall and reinstall XviD. This symptom often happens when one XviD release is installed on top of another.

[pojke]

If the bitrate method is an estimation, isn't encoding the audio first a preferred method?
I would be happy with using r4r for the DVD backups; I just couldn't figure out how to convert .mpg files (that I've recorded from TV) with it.
Actually, I did manage it (through dvd2avi I think) but it apparently used mpa audio for the final avi instead of mp3, and I assumed that was a waste of space.

Essentially, I want to be able to do 2 things with XviD:
1. Back up DVDs, hopefully using the audio encoding first method.
2. Encode mpeg2 files from TV saved from my ATI-AIW tuner.

Did I make a mistake by changing versions of GK?

As for the encoder, I did reinstall XviD before this happened (using the control panel add/remove method). Strangely, there were 2 XviD items in the add/remove, but I uninstalled both of them. I think one was a 167K codec that was installed long ago. I'll try uninstalling again.

I should add that I was originally using XviD 1.0-09052004 but after uninstalling, I decided to go with 1.1.0-30122005

[shon3i]

Did I make a mistake by changing versions of GK?
Maybe but i will say no, beacouse GK 0.35.0 is not much different, but if you not get troubles with 0.28.8 you should be back on earlier version.

[pojke]

I reinstalled XviD again with no luck at first, but then decided to reinstall GK as well (and reboot twice). For some reason that seemed to work. I knew something was different because the XviD settings were suddenly "unrestricted." The first time, they had remained the same even after uninstalling.

Now it seems XviD is working fine, so the only remaining question is whether it's better to encode audio first (as with r4r) or last (as with the new GK). Does it make a difference?
If so, how would that be done with the new GK?

[jggimi]

Estimates of soundtrack filesize based upon bitrate are reasonable in that your compressibility testing aims for a range of values, such as 40%-60% (per Doom9) or 60%-80% (consensus of most GK users). If you look in your logs, you will see only slight bitrate adjustments. As an example, in the log you provide via a link:Calculator:
VideoSize: 3659 kbyte.
Audio1Size: 406 kbyte.
Audio2Size: 0 kbyte.
Overhead: 30 kbyte.
AviSize: 4096 kbyte (4 mbyte).
FilesSize: 0 kbyte.
TotalSize: 4096 kbyte (4 mbyte).
Interleaving: vbrmp3
Bitrate: 1153 k(=1000)Bits/s
Frames: 779
FPS: 29.970
Duration: 00:26
Quality: 0.268 bits/(pixel*frame).
CompCheck3: 0.000 bits/(pixel*frame).
CompCheck5: 0.276 bits/(pixel*frame).
Resolution: 448 x 320
.
.
.
11:09:36 PM: MP3-File-Size is 432 kb.
11:09:36 PM: Audio 1, determined: 432 kb
11:09:36 PM: Audio 1, calc: 406 kb
11:09:36 PM: New Bitrate for Movie = 1145 k(=1000)Bits/s

[jggimi]

One addition: you asked if it is possible to use GK to encode audio before doing calculations. Certainly. Click on the Encoder tab, select your audio source, and submit an audio-only job.

[pojke]

Thanks,

That's good news about the audio encoding flexibility. I tried it and it worked well, so I guess I'll keep the new version. Just takes some getting used to.