Hi

I have this problem with TMPGENC
before i used KVCD MPG2,
but i try MPG1 and i think result is better so i used KVCDx3 MPG1

last monday i try to convert a dvd to KVCD 544*576 MPG1 with kvcd*3 template and latest script.

The first time i use a CQ of 65 and was ok but file to small
so i increased CQ to 75 and after 30minutes of conversion i have this error
i try to increase the level of priority as recommended in some poste but nothing changed.

I have never had this error when i convert to MPG2

Version of TMPGENC = 2.58
Version of Avisynth = 2.08
Source = DVD (75minutes)
script used = latest script

jp

You could try upgrading to 2.510, and/or setting AviSynth/VirtualDub Script Reader to the Highest priority in Options, Environmental setting, VFAPI Plugin.

ok

i will try it.
But why it work with MPG2 conversion and not with MPG1

jp

I never had this error before, but in the last few weeks I got it several times.
I am using TMPGEnc 2.511. I read somewhere that this problem is related to the source file being not ok. I usually get rid of this error using VirtualDub and opening the file with the extended options, selecting Rederive Keyframe Flags, and then doing a direct stream copy of the file.


Hope it helps.

Gaudi

If I get that error, I usually raise VBV buffer size in TMPGEnc from 40 to 60, helps with me!

__________________
¨¨°º©©º°¨¨°º©CHERONAPH©º°¨¨°º©©º°¨¨

ok

i will try your setting
last saturday, i tryed twice.
The first, it works
and the second no

jp

hi

it works

thanks

jp

Just wanted to thank CheronAph for his hint about raising the VBV buffer! I recently ran into this dredead illegal floating decimal point calculation order problem (yet again!) on some cartoon DVDs I was converting (by the way, I only seem to come across this error while converting fullscreen anime/cartoon sources).

Anyways, I had tried every single hint listed in the long thread in the TMPG forum about this issue, and nothing worked! (even "fixes" that had previously worked for me). Even a bare avs script with no filters would not work. I finally tried CheronAph's tip, and it worked! I tried a VBV of 50 and it worked for most of them, but I had to go as high as 70 on a couple as well. It did increase filesize a little bit, but was well worth it since it saved me a big headache...and the resulting files play fine on my dvd player.

So I definetly would recommend trying this VBV buffer fix to anyone experiencing Illegal Floating Decimal Point errors.

-d&c

Got the problem on Shrek today. Thanks for the hint Cheronaph and your recommendation D&C. What does this parameter actually do?

In case you didn't know new Tmpgenc is out with some fixes that could relate.

Version : 2.513. dated 2003/6/12

ozjeff99