KVCD: File size vs cq value?
 

is it normal to you that if i use kvcdx3, that the file that i get when encoded with tmpgenc is around 411 mo with no sound...the sound file 78 mo...my initial avi was 700 mo?

am i losing too much quality???

what can do if so because i can not go very high with my cq value...60 is the top...

thx

Re: file size?
 

It depends on the length of the avi but as it is probably a movie then 411 mb is pretty small

Why cant you go above cq value 60?

a
 

lenght of movie is 85 minutes (avi file was 700 mo)...if i go with a cq higher than 60 i have illegal floatinf point from tmpgenc & bbmpeg is unable to write to output file...i have burned it anyway and quality seems fine to my eyes...what is fun is that we can put the movie on one cdr only...just want to confirm quality wise if it is normal that that result (file size) is lower than the source file...

You should try to do something about that "Illegal Floating Point" issue buddy! :lol:
You'll be amazed how your movie will look with a CQ above 60!
check here : http://www.vcdhelp.com/tmpgenc.htm#problems

:wink:

If you was having "Illegal Floating Point" problems, I think the problem it´s some incompatibility with the dust filter and sansgrip filters to resize ( gripsize, gripcrop ).

But I need to use these 2 filters, so what I have to do? Simple, make virtualdub frameserve your .avs script to tmpgenc. I started to do this and never get a error again. :wink:

a
 

hi jellygoose,

i have tried everything at this site and i still have problems...with tmpgen when cq is too high i have illegal floating point error and when i do not have an error message with tmpgenc i have problems with bbmpeg which tells me that it is unable to write to output file...

the only cq value which is working is around 60...i am stuck...

big

PerfectCell,

How exactly to you get VirtualDub to framserve the avs script to TMPGEnc (sorry if this is a newbie type of question but I am totally unfamiliar with this process)? If you load the AVS into virtualdub what do you have to do to get TMPEnc to then encode the movie?

I've had problems with illegal floating point errors also, but mine were related to changing the VBV from the default of 40 to lower values (smaller file sizes at equivalent resolutions)--this solution may work for me too.

Thanks! :)

again
 

hi Perfectcell,

thank you for your advice for virtual dub & frameserver...it worked and i do not have the illegal floating error but i still have my problem with bbmpeg...at 70% of the mux it stops and i still have the following message...unable to write to output file...nobody is able to tell me why it is working with cq value of 60 and not working with a higher value...

that is why i think i will have to keep my cq value as low as possible for kvcdx3 template...

thx

big

help
 

tried perfectcell hint to resolve tmpgenc illegal floating point message and it worked...thanks a lot...but i am still stuck with bbmpeg...i simply can not mux with cq value higher than 60...it is always telling me that it is unable to write to output file...

question is...is there a lot of difference in quality with cq 60 & cq 80 using kvcdx3? because with cq 60 everything is working...

thx

hi big,

what version of TMPGenc are you using?

thx,
ren

hi big, have you tried to mux using mpeg tools in tmegenc as a test? It may be worth trying to see if it muxes all the way or if it fails at the same place. I can't say if it will produce sync errors or not but its worth trying :)

I get good muxes using TMPGenc instead of BB

a
 

hi guys,

rendalunit...it is version 2.59

fiz...i have tried and it works fine with tmpgenc but the only thing is that we can't specify the size of the cd (794 mo) in tmpgenc...so that is the main inconvenient if we want to make one cd because bbmpeg we can specify the 794 mo...

a
 

if we mux with tmpgenc is there a way that we can burn only on one cd using kvcdx3 and nero because we can not specify the 794 mo like in bbmpeg???

hi big,

not related to the floating decimal error- you shouldn't use tmpg 2.59 because it has a major bug that makes the file sizes too large.

ren

Yes, use version 2.58 or the new 2.5.10 ( the one I´m using ) .