Gordian Knot 28.8 is muxing with wrong app?

[DavidW]

I usually rip/encode my movies with XviD 1.0 and a VBR MP3 audio stream. This used to work fine. (Note that it's been more than 6 months since I last used GK) But recently I decided to rip/encode a few movies and downloaded the latest version of GK and it stopped working so flawlessly.

When I awoke the next morning all 8 of the movies I started the night before had horibble sync problems. I tried several different bitrates, XviD compression levels etc. (I knew that was a long shot), but to no avail. I still had sync problems.

Well, yesterday I started a rip/encode and noticed that it was trying to use VDubMod to mux the video/audio streams. I've tried using VDubMod on VBR streams before and immediately recalled the error message stating that it doesn't support VBR. I then recalled that the prior installation of GK always used NanDub to mux streams containing VBR.

Why is it using VDubMod instead of NanDub? (Sorry if this has been asked before but I did a brief search and couldn't find any threads directly related to this problem.)

Thanks in advance for your help.
--David Woodward

[manono]

Hi-

Since it's been awhile since you've ripped any movies, perhaps you're still using DVD Decrypter or Smart Ripper to demux the audio? With the new DG Index, it's imperative that you get the audio from DG Index (formerly DVD2AVI), or else you're almost guaranteed to get audio asynch. And there's nothing wrong with muxing MP3 with VDubMod.

[DavidW]

Originally posted by manono
Hi-

Since it's been awhile since you've ripped any movies, perhaps you're still using DVD Decrypter or Smart Ripper to demux the audio? With the new DG Index, it's imperative that you get the audio from DG Index (formerly DVD2AVI), or else you're almost guaranteed to get audio asynch. And there's nothing wrong with muxing MP3 with VDubMod.

No, I only rip the VOB files with DVDDecrypter. DVD2AVI produces the AC3 files and then BeSweet uses lame or whatever to change it to a VBR MP3. Then after encoding the video with XviD it tries to mux the two streams using VDubMod.

I have manually muxed the two streams using NanDub and the sync problems are gone using it.

Is it possible that I have the wrong version of VDubMod installed somehow? What version should be installed?

Thanks again, David

[niamh]

Wasn't it GK 0.28.8 that was bundled with a dodgy Besweet, and gave horrible synch problems?
try either updating Besweet, or better, get GK 0.32 :)

[manono]

You're right, niamh. I should have remembered the problems I had with that version of GKnot. If I remember correctly, it was an earlier version of DG Index that was the problem. I could be wrong though. In any event, DavidW, you should upgrade your GKnot and try again.

[DavidW]

Originally posted by niamh
Wasn't it GK 0.28.8 that was bundled with a dodgy Besweet, and gave horrible synch problems?
try either updating Besweet, or better, get GK 0.32 :)

0.32 fixed the problem and everything was working great until I tried to encode another movei and it suddenly couldn't find the stats file for the second XviD pass anymore.

After aborting the encoding I ran Gordian Knot again and tried to verify the XviD settigns under the options tab. The settings seemed to be ok but when I clicked "OK" I got this error:

Error 87 : The parameter is incorrect.
:Unable to query key info.

I thought maybe it was a registry setting so I clicked the "Delete Registry Keys" button and stil had the same error. So I reinstalled, same error... uninstalled and reinstalled, same error... rebooted same error.

Then I tried opening one of the same d2v file that I was using on the previous encode, and it said it wasn't a valid file. So I made a new one and it GK accepted it, but I still get the same error when trying to save XviD settings.

Any ideas?

Thanks again,
David

[DavidW]

<ahem> Nevermind... I must have clicked on the wrong shortcut yesterday when I was setting up an old game.

Apparently you get the previously mentioned error if you run GK in Win95 Compatibility mode. :)

Ooops.

Anyway, thanks for the help!

--David