Log in

View Full Version : Gordian Knot with x264 support is here (v 0.34.8 beta)


Pages : 1 2 [3] 4

len0x
5th February 2005, 17:54
Indeed its a bug, but not where you would think - try clicking on "don't check" checkbox and you'll see what I mean :)

*Edit* Actually it was implemented that way for all checkboxes (their state is remembered but not visually updated on the next start of GK)

MacAddict
6th February 2005, 14:54
Haven't seen this mentioned anywhere but what is the reasoning for a full first pass to do a 5% compression test via XviD? I obviously noticed the "SelectRangeEvery(0,0)" in the script no matter what codec is selected. I must be missing something here:confused:

len0x
6th February 2005, 15:22
SelectRangeEvery(0,0) in the script is not used - its overwritten when actual comp test starts (you can veify that by looking at LastCompCheck.avs). And after first comp test is done you'll see proper values in the script window as well (basically snip_size is not initialized before first comp test is started as i was thinking of dynamic snip size depending on codec properties).

niamh
6th February 2005, 15:30
I just tried and for me the first comp test runs the full movie, not the 5%. After aborting it, it behaves normally, until I close GK and re-open it.

MacAddict
6th February 2005, 21:37
Originally posted by niamh
I just tried and for me the first comp test runs the full movie, not the 5%. After aborting it, it behaves normally, until I close GK and re-open it. Actually I can verify this also. I let it run through about 20,000 frames and canceled Vdub, GK then updated the compression ratio percentage. Requesting different percentage values for the compression tests doesnt seem to have an effect, the entire movie is encoding for some reason.

@len0x
Thanks again for your contributions to this invaluable tool!

Arlong
7th February 2005, 12:34
Same problem here. In the AVS SelectRangeEvery is always set to (0,0) even if I try to run a 5% comp test. Actually it needs to be edited manually [SelectRangeEvery(280, 14)]. Odd, CT worked the first two times I ran it. ;)

Many thanks for the development of GK, len0x... I just love it! :)

len0x
7th February 2005, 15:20
Fixed a couple of bugs and new DGIndex is bundled. Beware that all d2v projects have to be rebuilt.

sillKotscha
7th February 2005, 15:52
nice :)

I've noticed one thing:

- the "calculate Frame-overhead" isn't remembered if you switch between the codecs... not fully true, this only concerns xvid.

len0x
7th February 2005, 16:05
Its supposed to be always _unchecked_ for XviD.

sillKotscha
7th February 2005, 16:10
it's supposed to be the way it is??

point??

niamh
7th February 2005, 16:50
XviD has the feature built-in, so to speak, so it's supposed to be unchecked in GK, _always_ ;) (And it's been this way since forever too)

len0x
7th February 2005, 17:06
Because XviD takes target size instead of target bitrate its able to calculate frame overhead directly in the codec.

sillKotscha
7th February 2005, 17:19
Originally posted by niamh
(And it's been this way since forever too)

I've started (re-) using GKnot since it support x264... that's why I stumbled over this behaviour for the first time...

loni_blues
8th February 2005, 00:18
len0x,

I cannot open a d2v file just made with DGIndex RC2 with latest GK 0.34.6.
What's wrong?

mongoosesRawesome
8th February 2005, 05:32
I also can no longer open d2v files with the new version of GK (0.34.6). Using the new version of DGIndex (1.2.0 RC2).

len0x
8th February 2005, 11:57
You have to redo your projects with correct version of DGIndex, old ones will not work.

I (and lot of others it seems) do not have any problems opening new d2v files.

loni_blues
8th February 2005, 14:48
len0x,

I was only describing a problem with d2v files made with the new DGIndex RC2 when trying to open them with the new GK 0.34.6. I have tried once more, with Forced Film, without it. With different idct algorithms. I have uninstalled GK, reinstalled it. I always get the "File is not a valid...". mongoosesRawesome seems to be having the same problem.
Perhaps there is some other thing we're overlooking. Would very much appreciate you looking into the issue.
Hopeless,
Kind Regards,
loni_blues

len0x
8th February 2005, 14:55
I'd be happy to if I was able to reproduce it...
Can you attach d2v file please?

len0x
8th February 2005, 16:01
Btw, what kind of CPU do you guys have? (those with d2v problem)

loni_blues
8th February 2005, 17:18
But of course, I should post the d2v file.
My CPU is AMD Athlon 1.20 GHz. The OS is Windows XP SP1.
I am posting a couple of them, one with FF.
Thanks a lot

loni_blues
8th February 2005, 17:20
Here is another d2v.

len0x
8th February 2005, 17:22
Nothing wrong with it. Some ppl reported that DGDecode 1.2RC2 is no longer working for them so I guess it might be the same problem. You can try opening d2v manually through AVS in vdubmod and see if there are any errors.

niamh
8th February 2005, 17:29
I've an Athlon too and XP SP1, and it works(thought I'd mention)

loni_blues
8th February 2005, 19:31
Well, well. I cannot open the d2v in Vdubmod through Avisynth. So it's not a Gk problem after all.
I'm gonna check the Dvd2avi forum.
Regards.

len0x
8th February 2005, 22:33
make sure DGDecode.dll is the same in both DGMPGDec dir and your avisynth plugin dir, coz if you have custom avisynth plugin dir then GK's installer will not be able to write there.

loni_blues
8th February 2005, 23:40
len0x,
Thanks a lot!
I mixed up things quite a bit with installing from your installer, installing RC1 with the installer of GK 0.34.5 and reinstalling RC2 directly from the zip file by DG.

Now things are like this: With no Forced Film the d2v can be opened both in Gk and Vdubmod. But with FF applied it fails in both programs.
Back to Dvd2avi forum!

mongoosesRawesome
9th February 2005, 05:56
It looks like RC3 of DGIndex fixed everything for me (I had the force film problem). Just remember to replace the file DGDecode.dll in your avisynth plugins directory (lenox said this earlier).

TripleA
9th February 2005, 14:37
One question before I try this new GK: is there any spyware in it? If so, how should I go about disabling it/them?

len0x
9th February 2005, 14:48
ppl are getting too paranoid... there is no adware/spyware in GK and never will be.

TripleA
9th February 2005, 15:09
Thanks for clearing that. But I do believe there are grounds for my paranoia in this particular case: no one was told of the addition of spyware to AutoGK. It sets a precedence, you know...

Now let's see if the new GK can eat the new D2Vs...

[Edit: Works, of course. But the old one could have worked as well, for all I know: I had moved my AVISynth plugin directory and forgotten to accordingly update the batch file that "propagates" DGDecode.dll]

len0x
9th February 2005, 15:40
Now I'm waiting for DGIndex 1.2.0 to be released and will do full repack of GK as 0.35 stable :)

Subwars
9th February 2005, 17:12
hi i don't believe this is a feature as yet not that i've seen in any options anyway but to be able to have a set default processor priority thruout the entire rip process is this an option that can be built in??

len0x
10th February 2005, 12:12
why not change default priority option in VDubMod instead?

Subwars
10th February 2005, 12:37
:rolleyes:
:stupid:
:thanks:

len0x
11th February 2005, 16:21
Bundled with latest DGMPGDec and its no longer possible to change name of the mpeg2 decoding library (to avoid all the confusion when upgrading).

mongoosesRawesome
11th February 2005, 16:27
Are there any changes besides supporting RC3 of DGIndex?

len0x
11th February 2005, 16:29
As you can see from the history only one (x264 comp test related).

niamh
11th February 2005, 16:44
version 0.34.8 beta is out

Where did 0.34.7 go? :p

len0x
11th February 2005, 16:48
it was up for 10 min and then I discovered x264 comp test bug :)

niamh
12th February 2005, 18:19
I have a feature request (/ducks)....add the possibility to hardcode text subs, as well as idx/sub in the avs window....
This entails
- ability to browse for text subs in the avs window
- replacing vobsub(filename) by textsub(filename.extension) in the pre-made avs in that case (and probably half a million lines of code :D)

Reasons I'm asking:
I) I've had to explain the manual procedure at least 4 or 5 times over in the subtitles forum (never mind outside of doom9)
II) I know the advanced avs caters for it, but
a)not many people seem to use it yet
b)it's bewildering for basic users, as it's so complete, so then we're back to I)


If it wasn't too much of a hassle, it would be a really nice feature IMO (personally I'd rather burn alive than hardcode any subs, but there you are, lots of people like it that way)
If it is hard to implement, well I've asked at least :)

iradic
12th February 2005, 20:13
hi,

first - thanks for your great work...

second - feature request (i saw the one before so :) ) ... if it is possible do add something like "LOCK HEIGHT" checkbox (or similar) so when changing AR gknot changes width ...

thanks and bye...

len0x
12th February 2005, 20:37
I'm not taking feature requests atm :)

But TextSub stuff is pretty easy to do though (ini files have to be updated to allow different filtering in open dialogs).

niamh
12th February 2005, 21:15
Originally posted by len0x
[B]I'm not taking feature requests atm :)

Is why I ducked ;)

len0x
12th February 2005, 21:35
try this: http://www.autogk.me.uk/gk.zip
Does it work?

niamh
12th February 2005, 22:17
Sorry for the delay, I just had an interesting issue with my graphics card drivers, that turned every character on screen into chinese(with assorted pink cubes) :D. had to look into that first

It nearly works :) all that's missing is the extension in the textsub line (vobsub() doesn't require it, textsub() does)

BruceL
12th February 2005, 23:52
@len0x
As always, thank you for your terrific work! :)

len0x
12th February 2005, 23:59
Should be working now. Same link.

niamh
13th February 2005, 00:16
yup, works great now :) thanks :)

OMINUS
14th February 2005, 19:57
i installed the latest gknot 0.34.8 and i am trying to use it with my captured avi-but there is a problem
when i try to make a comp test i get the error:
avisynth open failure:
fielddeinterlance:yv12 or yuy2 data only etc

i know that the problem is with the colourspace because
the above error happens only with my asv2 captured avi (colorspace YCbCr ) whereas with my mjpeg captured avi (yv12 colorpsace) i have absolutely no problem and i can encode perfectly with gk

so is there any command i have to put in the avs script generated from gk in order to bypass this error?i am a little novice concerning avs ;) so i need your help here

anyway thanx in advance

killingspree
14th February 2005, 20:13
converttoyv12() would probably be a good idea... but you could also try converttoyuv2()

kr
steVe