what is an ILLEGAL FLOATING DECIMAL, pls help

[milwaj83]

while converting a movie with tmpge, it stops and tells me that there is a "illegal floating decimal point calculation order". so i am stuck after that, pls help.

[nocam1334]

I've gotten that message before too. It usually happens when I try to increase my audio bitrate from 192 to 224 or higher. Not sure exactly what it means, though.

[lazzonya]

i've gotten that annoying message (usually after 10hrs of encoding) too. i've found it to occur when one of 3 things happens:

1. as posted above, the audio rate change
2. when there is a bad frame in the original file (at whatever frame corresponds to the % of the encode completed )
3. when i try to do another operation (usually some kind of media player) while encoding.

good luck!

[flumpf]

But is there any way to recover from this? I have a divx from the net that halts with this message at 92%.

[lazzonya]

i've found no recovery. when it's a file problem, you can preview the file in tmpeg's source frame range. move to the approximate frame of the problem (by using your percentage). usually, the first bad frame will appear all messed up in the preview (colored lines/blocks/no video), and continue until a good frame is reached. i then encode around the bad section of frames using the source frame settings. you lose a small section of the movie, but it's usually not enough to scrap it.

[Freshman]

I have found that the DivX 4.01 or 4.02 codecs will sometimes be able to get past corrupt frames, whereas 3.11a would produce the floating point error. Raising the priority of the DirectShow-Reader in TMPGEnc (under Options/Environmental Settings/VFAPI-Plugin) as well might help.

If this doesn't work, look for two programs called "DivFix" and "AviDefreezer", but I haven't used them enough to be able to give you proper instructions for using them.