For me kvcd works at 704x576 mpeg1, gop 25 on a dvd. Authored with tmpgenc dvd author. I've just made the test. I've tried also 480x576 with dvd lab and it works too. 8) I can put easily 5 movies on a dvd. That's great :D

What standalone do you have Aragorn ?

I've got a philips dvd 955. I've bought it 3 years ago.

I think that GOP is related to processing power of decoder
(hardware or software) and also to video buffer size,
and this one is more important.
As it mentioned already, nowdays standalone players are capabale to porocess GOPs over 25 (of course the quality depends also on sequience IPB type frames), but players have certain limitations on video buffer size.
So the question is - how many frames buffer holds?
The reason I am asking this because I can specify video buffer size in encoding and also it is specified in multiplexing.
Reading the thread while getting buffer underruns:
http://thread.gmane.org/gmane.comp.v...yer.user/22839

I just want to say that I did my first try on DVD-RW yesterday and my pioneer DV454 accepts a KDVD done with my "old" videos I did for KVCD.

In other words : a MPEG1 352*240 GOP24 video authored with TMPGENC DVD Author is read without any problem !

I do not try yet with higher resolutions.

Note: TMPGENC Author took 40 minutes to make a DVD image of 583 Mb !!! Is that normal ?
(96% of the CPU was use doruing all the process - I have a P4 1.4Ghz).

Returning to the question: how large video buffer can be?

Current windoze encoders suggested 40KB for VCD, 112KB for SVCD, 224KB for DVD and mentioned that these values are minimum. How these arbitrary figures sneaked into encoding procedures and source code?

Video buffer size is closely connected to bitrate control and maximum GOP.

In regular TmpgEnc DVD Author as any other Authoring programm doesn't need that much cpu power, its more a HD power thing.
But as your KVCDs in regular come with a 44.1khz sound, TmpgEnc DVD Author got an automatic resample engine, this option is viewable at the sound input field ... so your sound will be resampled to 48khz.
And thats another issue: If the Quality by doing this could suffer. Cause if you go in with a 44.1khz 112kbit Audio this will be resamled at 48khz 112kbit (as I know) = Quality loss in audio. ?! We should figure that out.

Did you only choose one movie to burn on cd for testing or did you put several KVCD based tracks in one project??
EDIT: Yes you did as I re-read your post again ..

That's also what I was thinking. But with my 120GB/7200rpm/8Mo memory HD, that shouldn't be a problem :-)

Okay ! I didn't think about that. That's sure that for at least one of the track the sound was in 44.1 because it was a regular VCD (I made a DVD with 2 tracks : one regular VCD and a KVCD).

You can't resample a compressed audio. You have to decode/resample/reencode. And as mp2 isn't a lossless format, for sure the quality suffer a little.

I just answered to that above :-)

I know, but there are differences in resampling engines and so lets see if it would be better to let do besweet the decode/resample/reencode way or if it also will come out in a smae quality if TmpgEncDVD Author reencodes it.
But anyhow "decode/resample/reencode" a 112kbit or even a 128kbit, .... oh oh ... and I think 95% of all encoded KVCDs around the globe do got 128kbit or below that. And so I think in case of re-authoring already made KVCDs to DVD we should use Bewseet to "reencode" that existing mpeg2 to at least 160kbit and do a comparison. Thats what I meant. :)

As I already do not trust tmpgenc audio engine, I won't either trust the one in tmgenc author (I guess it's the same !).
So I think about using besweet for that. And you're surely right : it's a good idea to do the new file in 160. This way the loses will be lesser than if we reencode in 128.