Will 5.03 work with Gknot?

[dvd2mpeg4]

Just curious to know if the new divX 5.03 will work with GKnot .27 or is it only divX 5.02 compatible?

[unimatrixzer0]

I just tried to encode something and when it started the 2nd pass I got a whole bunch of errors and warnins. Couldn't open the .log file either. Don't think it even created one. Dunno if its gknot or if its something wrong with the codec.

[unimatrixzer0]

Just put 5.02 back on and all the warnings and errors were gone. Guess its not compatible with 5.03 yet.

[hug0b0ss]

Even if 5.03 was compatible with Gknot.. IMO...i can't see there being any major improvements in picture quality compared to divx5.02 rips..
Staying with 5.02 is your best bet.. get the pro version .. if you don't have it already...

peace! :D

[dvd2mpeg4]

Thanks for the replies; I think I'll just wait until TheWEF or Doom9 gives the okay. Thanks for an AWESOME program in GKnot .27 :D

[colordog]

I just tried a whole bunch of encodings with GKnot 0.27 and DivX 5.0.3 -- they all had error saying they couldn't open filename.LOG at the end of the 1st pass - it looks like it's not being created (isn't in the directory). For instance:

11:24:38 PM: Started DivX5-First Pass: C:\vobs\MOVIE\VIDEO_TS\Movie.avs
12:43:58 AM: Finished DivX5-First Pass. Duration: 1 hour, 19 minutes, 19 seconds.
12:43:58 AM: Trying to open Log-file.
12:43:58 AM: Error: Could not open C:\vobs\MOVIE\VIDEO_TS\Movie.log
12:43:58 AM: Error: Could not count encoded Frames.
12:43:58 AM: Speed: 0.000 Frames per Second.
12:43:58 AM: WARNING: Number of counted frames differs from settings!
12:43:58 AM: WARNING: Settings: 141494
12:43:58 AM: WARNING: Counted: 0
12:43:58 AM: WARNING: Difference: 141494
12:43:58 AM: Correcting Bitrate...
12:43:58 AM: Original Bitrate = 1121 k(=1000)Bits/s
12:43:58 AM: ERROR: Correction impossible.
12:43:58 AM: Now encoding at 1121 k(=1000)Bits/s

[killingspree]

have you uninstalled the previous divX version before installing 5.03? i ahd the same problem when i installed 5.02 over 5.01. it helped to uninstall both and then reinstall only 5.02. also this could be an adware problem, if you didn't remove it correctly this sometimes also happens. so if you don't want to switch back to 5.02 try to do a clean reinstall first.

regards
steVe

[colordog]

I didn't officially uninstall 5.0.2 before installing 5.0.3, but I was fairly sure that the upgrade program removed the 5.0.2 components first, but perhaps I'm wrong.

I can say for sure that this isn't an adware issue, because I'm not using the ad-ware supported version (Yup, I actually paid for it).

[jonny]

No, it's not compatible, the internal codec data format is changed so changes in the code must be made to reflect this (same goes for divx5enc and all the others programs that generate codec parameters)

[hug0b0ss]

have you uninstalled the previous divX version before installing 5.03? i ahd the same problem when i installed 5.02 over 5.01. it helped to uninstall both

This is the thing that upsets me about divx...
Unlike DirectX for example which will remove and overwrite the necessary files for you automatically...DivX does not .. which will lead to Gknot crashes if it has not been removed and then freshly installed..I think the DivX team needs to address this issue..

Peace!!

[Evil Andy]

Actually DivX 5.0.3 seems to find, remove and overwrite the correct files just fine.

As Jonny said it just doesn't work with Gordian Knot. The CLI has changed so Gordian Knot can't call the codec correctly and the format of the first pass log file has also changed so Gordian Knot can't read that for compressibility checks.

[killingspree]

somehow it doesn't seem to work with virtuldub either.
what i did:
ripped the dvd
created d2v project
importet in gordian knot
- bitrate calc, resizing, cropping
saved the avs file
imported the avs into vdub
made a job list:
first pass (using no special settings)
2nd (nth) pass...

but after virtualdub has (succesfully i think) encoded the first pass, it cannot load the divx.log file, instead it tries to overwrite the existing one with the nth pass feature.

what am i doing wrong?
regards
steVe

PS: i'm hoping for an adapted version of gknot since i just love this program! (:

[cpuuk]

Just adding my comfirmation- I did a clean install of win2k OS and put in GK 27, plus the new 503 DivXpro, and I too get the "unable to create *.log/ 0000 frames per second/ frame count mismatch" error messages.

[jonny]

The problem is not only related to the log file.
Using GKnot with DivX5.03 means that you are passing wrong data to the codec. So the settings you have specified are probably not keeped (b-frames, gmc, qpel, rc parameters...).
There is no sense to test... it's technically not possible to make GKnot 0.27 work with 5.03.

[Cyco]

Originally posted by jonny
The problem is not only related to the log file.
Using GKnot with DivX5.03 means that you are passing wrong data to the codec. So the settings you have specified are probably not keeped (b-frames, gmc, qpel, rc parameters...).
There is no sense to test... it's technically not possible to make GKnot 0.27 work with 5.03.

Interesting... I have updated the 5.02 DivX codec to 5.03... Then I tested it with GKnot and it worked...
No errors in log file and the new *.avi was ok.

[cpuuk]

Originally posted by jonny
The problem is not only related to the log file.
Using GKnot with DivX5.03 means that you are passing wrong data to the codec. So the settings you have specified are probably not keeped (b-frames, gmc, qpel, rc parameters...).
There is no sense to test... it's technically not possible to make GKnot 0.27 work with 5.03.


Did you use any of the Pro features during the encode?

[jonny]

Interesting... I have updated the 5.02 DivX codec to 5.03... Then I tested it with GKnot and it worked...
No errors in log file and the new *.avi was ok.


Interesting too :D
The next time you have a succesful encode with GKnot0.27+DivX5.0.3, please go to VDub > Video > Compression > DivX Pro 5.0.3 Codec to see what are the settings for the encode you have done...

My last post in this thread :p

[bullfrog]

It does not work either with the compressibility test?

we can use the test of compressibility and later we make the manual codification with VirtualdubMod...

Thanks

[jonny]

To make a comp. test i suggest you to take a look here:

http://forum.doom9.org/showthread.php?s=&threadid=44414

[Evil Andy]

@jonny
I think you're misunderstanding, I believe they mean they're using Gordian Knot to calculate the bitrates and generate the avs files and then loading them into VDub and setting compression settings etc. manually.

@killingspree
VDub's working fine. In n-pass DivX overwrites the log file each pass as it re-examines its distribution of bitrate. You can stop it asking if it's ok to overwrite the file by checking the box marked Do not prompt for errors and warnings.

[George922]

I can confer, I am a newbie at divx encoding, just started last week.

Im glad I bumped into this thread, I was wondering why the compressibliltiy didnt work.


I guess I will reinstall everything, but I can say, my movies came out fine. I did see the log error and the compressibility error.

[lordtear]

I can understand the worry about the 5.0.3 problems. The thing that confuses me is... Why worry about 5.0.3 right now? It just came out. I installed it just to see the differences between it and 5.0.2. There were slight differences in encoding -- better quality and LITTLE higher compression. Overall, not impressive enough to worry about it. I love the new options in the configuration utility and the more stable playback on certain systems. It's still a little buggy on some systems, though. Right now, 5.0.2 is very stable and WIDELY used. I reinstalled 5.0.2 and am using it fully with no problems on reinstall or anything. Let's give Wef a chance to work on a fix -- Wef is aware of the situation and will eventually give us our fix. Keep on playing with the 5.0.3 and maybe give some info to Wef about what you discover --- that is, if you enjoy messing around with the new codec and GKnot. For all the others out there that just want great looking vidz with extremely stable output... stay with 5.0.2. That, and GKnot 0.27 will provide an excellent answer to all your questions!

lordtear

[Babeinternational]

It is a good way to go on learning how things work, now that everybody is aware of the incompatibilty of GK .27 and DivX 5.0.3.
After all, letting GK do all the work for a while makes you a little "rusty".
And now that there is n-pass encoding, and also AVISynth 2.5, with full YV12 support, and VirtualDubMod (Fast recompress), it is quite a crime to continue using techniques not yet updated.
So let's start using those new filters, manually, and stay tuned.
I'm confident in finding those new things in a next release, and be sure I would jump on it, but I have to say it is quite refreshing to encode manually again. Time consuming, but worth it.

[Evil Andy]

@Babeinternational
Well said. Due to the incompatiblities between Avisynth 2.5, DivX 5.0.3, Gordian Knot 0.27 and VirtualDub I've actually learnt how to use Avisynth properly and started experimenting with Xvid and OGM files, with pleasing results. Its almost criminal to ignore all those great Avisynth plugins out there.

If the Wef does get out another version of GK before completing his uber secret project to replace GK then I hope he'll include some of these plugins eg. Convolution3d is far better IMHO than Avisynth's internal denoisers, Dup for cutting down anime filesizes etc. etc.

[binky the stunt cat]

I installed 5.03 shortly after it came out.
I did have some problems with the compressability test, untill i realised that i'd left V Dub's codec settings on the multipass-1st pass.
Changed it back to 1 pass, closed V Dub, and it's been working like a charm ever since..
Could be psycological, but i'm liking 5.03 more than 5.02...now i just have to go through the whole "This file isnt working, what do i do?" dilemma again.....can't plebs use G Spot and figure it out for themselves :p

[JohnMK]

Originally posted by Evil Andy

VDub's working fine. In n-pass DivX overwrites the log file each pass as it re-examines its distribution of bitrate. You can stop it asking if it's ok to overwrite the file by checking the box marked Do not prompt for errors and warnings.

I can't find this option. Care to help me out? Thanks. :)

[N_F]

I believe the option is below those boxes where you set your log and mv file.