XviD support

[Head Hunter]

I was wondering if the next version of Gknot was going to support XviD. After seeing Doom9's latest comparison I thought it was a good balance between Divx4 and SBC and being ISO compliant is just another plus. I hope Gknot will add this codec, if not I guess I'll just use the manual way.

[MaTTeR]

This would be so awesome:D I have to agree...Doom9's article has convinced me I need to get into the XviD scene.

[rui]

Well, this is a feature request that a must subscrive :)
XviD impressed me too. And i am a long time divx4 supporter

[Krack]

I've made all my movies with SBC because of it more details. In fact I used to take them on 2 CDs because of the blocks. perhaps this codec couls help me to make very good and detailed movies on 1 CD.
I hope that the further version of Gknot will support it too.

[murattttt]

I'm just adding a new reply in order to make WEF pay attention to this thread. Yes we are capable of making our owm Xvid movies but it would surely be amazing to automotize the process with the excellent Gknot tool. Besides Xvid promises the brightest future amongst all the other codecs. I believe in open source to the last.

[zulu]

yeah, that would be great!
GKnot would become even more important to the encoding community ;)

[Ripe73]

I want it too:D ....soon as possible

[rui]

TheWEF, is any hope for Gnot supporting Xvid in futurereleases?
Or we should just stop anoying you about this ? :D

[rui]

After reading Doom9's XviD guide, i think that it wouldn’t be too difficult for TheWEF to create a third option in Gnot to work with XviD.
We can always do the stuff manually, but...it would be a lot better if it worked like divx3 or divx4 does. That way i could step way from the computer a only return when the movie is ready.
TheWEF, if you read this, what do you think?

[Head Hunter]

Has anyone heard anything from TheWEF recently? Is he just not responding in this thread or in any?

[MaTTeR]

I was wondering the same thing. I haven't seen him at all lately. Perhaps he is just busy with life or maybe a new version of Gknot:)

[Doom9]

he's just busy with life in general.. and most normal people have put their real life stuff before their online life (exclude me from that.. I find time for this stuff no matter how much there's going around me)
we have some pretty nifty ideas for GKnot's feature.. but it will take quite some time to make it all come together.

[rui]

Well people, lets have faith.:p

[-h]

Not that I've used GKnot before, but automating XviD via an external tool could give 'interesting' results depending on how the codec's internal state is stored by the program - I assume GKnot pops up the codec configuration box when you configure the 1st and 2nd pass?

It's just that the internal XviD codec/config structure is going to keep changing - sending the same config data from an old build to the current build will bring it all crashing down.

Apart from that, nothing has to change - the stats file is the same format as Nandub, but I guess a few GKnot options will have become redundant.

-h

[rui]

Originally posted by -h
Not that I've used GKnot before, but automating XviD via an external tool could give 'interesting' results depending on how the codec's internal state is stored by the program - I assume GKnot pops up the codec configuration box when you configure the 1st and 2nd pass?-h

Nope, it doesn't. Actually, we never see the codec configuration box. We just choose the final video size, resolution and crop, choose begining of credits, resizing filters, noise filters, audio parameters, and Gnot does the all thing automatically.

Originally posted by -h

It's just that the internal XviD codec/config structure is going to keep changing - sending the same config data from an old build to the current build will bring it all crashing down.
-h

Hum, this could be a problem...:confused:

[Head Hunter]

I never thought of that before. Well maybe when the config structure is a bit more fixed we can hope for an automated way. Until then V-dub's job control is our best hope, at least for automating both passes in the main movie.

[-h]

Ooh. :)

I know there isn't any intention to freeze the codec's feature list, and any new feature means another 32-bit variable shoved into the codec/config struct.

Codec's store and retrieve their 'state' by doing a block copy of the data supplied by the calling application - if that data is invalid, XviD will either use the result of its internal error checking, or just bomb out completely with some obscure ICM_COMPRESSBEGIN error. Either case isn't really acceptable for useful encodes.

-h

[rui]

Okay. You are the boss:)