I'm running DVD2SVCD 1.13b2, AviSynth 2.52, and a motion adaptive script supplied by Dialhot. I've got my file prediction factor set to 0.96, my CD size set to 800, and all # of CD's set to 1 (under the bitrate heading).

Most of the times, the final file size of a ripped DVD will be pretty close to 800 meg. However, somtimes, I'll get a little file (20 or s0 meg), that usually cotains the credits or a very small piece of the movie.

Since I've got all of my 'number of CD's' set to 1, shouldn't I get just 1 file? I've searched, and can't come up with a good reason, and as this is more in the class of an annoyance than a showstopper, it's not ter5ribly important, but nonetheless any advice gladly accepted.

thanks

Tom

The reason is that bbMPEG is set too multiplex and cut the movie at exactly (CDsize MB - 5 MB)= 795 MB.
So, the final .mpg file can't be bigger than 795 MB (cause of that when using CQ the filesize will not be calculated exact), bbMPEG make a new file after 795 MB.
It's any the audio- and video bitrate that are depending of the CD size, not the bbMPEG settings!

Thomas Davie,
see if you have only one .mpv file,if yes,
open bbmpeg (under d2s folder) and load the
"encoded video.... .mpv" and the "encoded audio... .mp2"
... mux it again!
you will got only one mpeg file!

follow this adjusts to use bbmpeg:

http://www.kvcd.net/forum/viewtopic.php?t=2224



hint...
next time you use d2s adjust in bitrate tab:
more 2 minutes in movie time(lenght)
and more 6mb in cdsize!

Thanks for responding. But I'm not sure that I understand the answer Can bbMPEG be set to cut at, say (CDsize MB - 0 MB), or is it always set at -5 MB? So, if bbMPEG *always* cuts at -5 MB, than should I set my CDsize MB = 795, or 790 or lower in the bitrate tab??? I had thought, that with my audio set to 128 kbps, my DVD would just be encoded at a bit rate enough such that a CD would be filled. To say the least, I am puzzled

If I set CD size to 1000 MB, then I guess that the program would set the bitrate to fill out the CD to ~1000 MB, correct?

thanks

Tom

(or will the CQ just max out to 100?....but since I've found that I can play raw MPEG's from DVD+RW and -R, this might not be a bad thing).

excuse me again:

Thomas Davie,
in the dvd2svcd.ini ,you can see that d2s program
have control of BBmpeg that work like d2s need.
if you chhose 800mb size,d2s will give 794mb(less 6mb)
b u t
using the "manual way" like i post, bbmpeg will encode as only one file!


and if you want 1000mb you can set the bitrate to 100,
but you will got this size if your movie have time for this size...
it means,if the movie have 10 minutes,i can't believe that you got 1000mb.
this is one of the reasons that Kwag is developing CQMatic!

A little hint there : a CD80 contains exactly 807 Mbn without overburning.

So set this value in DVD2SVCD insteed of the default value "800" in the birate tab. The cut will be done at 803 Mb and not 795.

I did today a perfect KVCd from DVD2SVCD that is exactly 801 Mo !

hey PHIL...please
details,details...


script,cce or tmpgenc,file prediction factor(if tmpgenc)... ...etc,etc.

Iv'e just changed my CD file size to 807, and am trying another encode right now. I also checked the reference post you listed and changed my bb<PEG settings to be in accordance with that.

But, uh....2 more minutes in movie length? My movie is 2h, 40m, 30s....so I'm not quite sure what you mean.
Now, and this may be important, but under the bitrate tab, , the max average is blank. I quickly figure out what the bit rate would be for this movie and then made the max average 50 points less, Will report back when the mobie is finished.

Thanks Jorel (and Dialhot and Azel)

2h, 40m, 30s = ~160minutes

adjust in bitrate tab:
between "0" and "165" mins. Use "1" CD size "807"

than in misc. tab click recover,load and mux again!

or mux as "manual" with bbmpeg like i posted!

Re running D2S created one 802 Mb file and a 33 Mb file.

Tom

Moreover, if under the bitrate tab, all 'Use CD's' are set to one, should the program use, well....just 1 CD (bbMPEG shouldn't split?)

Tom

yes Thomas Davie

you have to choose "use (all) cds" with the same size
and the " time" (between-and) too...all equals!
but you encode the movie again
you don't needed that,was only change the values in bitrate tab
and mux again......i wrote it to you

now ,if you encode the movie again,you got a big file size
and have to encode one more time.
802+33= too big

But, all CD's were set to 1, and 807 MB (that is what you mean use (all) cds with the same size, isn't it?).

Yeah, I encoded the movie again, because I had deleted the files before I had read your response And yes, re encoded the movie again, but my question is this 'at a size of 1 CD at 807 MB, shouldn't the program be creating just 1 file with a size of no greater than 807 MB'? I understand that bbMPEG is set to split, but I do not see these options anywhere, even under the advanced settings.

Ah, time to watch the Rolling Stones on TV and a beer.

I'll try again tomorrow.

Thanks Jorel

Tom

Rolling Stones

where they are now?

in Toronto for what has come to be called (at least here in Canada) as the SARS concert. Also with AC/DC, Rush, Tea Party and some other groups. It's been shown on a Canadian TV station, but unfortunately they seem to keep cutting away for commercials.

Tom

stones?

rush?

ac/dc?

and some more?!?!?

and i'm here in Brasil.....far away from Toronto!

Nothing really exceptionnal in what I did Jorel, except that I made a
"semi-manual" prediction. I explain below.

So used DVD2SVCD, "my" MA script (he one you called MA Philter
), TMPGEnc.

The settings where : Audio 128 Kb/s, Video min 64, Video max
2300, medium sizes set to 807 for every time range (in bitrate
tab), initial CQ 70, fator prediction 1.000,.

I encoded a MPEG1 video but muxed as SVCD (the best choice for
my player) and used the standard SVCD resolution.

Why do I say I made a "semi-manual" prediction ? In fact the
automatic prediction of D2S is also screwed up by the MA script.
D2S did a first try at 70, then go to 74, then 75, then 82, then 68... !!!

I saw in the log that at 75 the results where very close to the final
size wanted. So I stopped the process, did a "recover" and this
time I set the CQ to "fixed value" of 75.

Everything went perfectly.

Tom, I'm not sure you understand when we are saying that size
prediction is screwed up by the new MA script

That means that all former tools that used to work perfectly, don't
work anymore. That include D2S.

What is your problem there ? D2S calculates that with a CQ of 70
(it's an exemple, I don't know the real value you had), the final size
will be correct. So it does the encode. But... the final result is too
big...

What you have to do there is to make a "recover", ans set the CQ
to a fixe value of 68 for instance.

There is no other way for the moment (I'm making some tests to
find a solution but didn't find yet).

ha,ha ha....

yours last 2 posts are 2 guides Phil

thank you for that.


ps:
your inspiration is too high today friend,more than habitual !

Ah, this post makes it clear. Plus, your above post. I've got an initial CQ rip of 70 starting right now. I'll look at the log and file size when I get home from work, and then (assuming it is necessary), recover with a fixed appropriate CQ value.

Thank you.

Tom