Forums [Archives] Forums [Archives] (
-   Video Encoding and Conversion (
-   -   TMPGEnc: Illegal Floating Decimal Point Error (

rendalunit 02-20-2003 07:37 AM

Illegal Floating Decimal Point Error
I'm getting this error about 50% of the time these days with tmpgenc 2.510. It just happened again using this script:



I haven't touched the vbv buffer- it's 40

I'm beginning to wonder if it's a bug in tmpgenc 2.510 causing this :?: Anyone else see this error a lot lately?


big 02-20-2003 08:21 AM

trick from perfectcell

try that it comes from worked for me to...i was able to clear that but now i am stuck with bbmpeg when tells me that it is unable to write to output i can not miux my files...

First of all, you have to download virtualdub. In the KVCD template fórum exists a post with the links to download the programs. This post its sticky and the name is "Downloads".

Get the program, install in your HD ( unzip ) , and in the directory you installed the program exists a .exe named auxsetup.exe. Execute this program and choose "Install Handler".

Open your virtualdub and load your .avs script. In the file menu choose "Start frameserver". You'll see the name of your script. Press enter and then choose a name for your .vdr file ( for example movie.vdr ).

Open TMPGenc and loads the movie.vdr, choose your template and start to make your KVCD, because your filters and etc are loaded in virtualdub and put direct in your tmpgenc.

Jellygoose 02-20-2003 10:02 AM

Hi ren!

I've come across this error a lot lately too... First of all you should adjust your TMPGEnc Environmental Settings right if you haven't yet.
Check this link for it :

Other than that you could try big's suggestion. It appeared to me that some specific filter Combinations cause this. try temporalsmoother(2,1) and see if that changes anything...

heller 02-20-2003 11:50 AM

Gotten this problem a lot lately with 2.510, and Perfectcell's solution of frameserving with V-dub has worked wonders for me (slows down encoding a little, though). Also solved a weird problem on my laptop of not being able to load any avs files at all witih TMPEnc (2.59 and 2.510)--kept giving me "cannot open file or unsupported type" even though V-dub opens it fine. Go figure! :?

rendalunit 02-20-2003 12:46 PM

hey guys!

I checked the Environmental Settings and everything looked okay- I increased the DirectShow priority a little.. I'm wondering about this though- if you have an .avs with lots of LoadPlugin lines does avisynth use memory to load the dlls even though the filter isn't called?



even though I'm not using Dust, BlockBuster, and FluxSmooth are they in the memory somehow? I'm just wondering if the decimal floating point error could be memory related because I do have other apps running while it's encoding :roll:

Also in FitCD I set the destination size round to 8, I wonder if I should roll it back to 1 or increase it to 16?

I'll frameserve with VDub as a last resort but I'd much rather understand why this error keeps popping up! :wink:


Fiz 02-20-2003 01:14 PM

I've also had this problem 75% into an encode! :cry: I'd also like to know what causes it so if anyone finds out that would be cool!

To save time, I opened what had been encoded in vdub and got the very last but one frame number (as the last frame was corrupt). I then set the trim statement in my avs script so that it starts from the next frame from that.

trim(16481, 0)

I set tmpegenc off again to finish the last 25% using another file name.

To append the 2, I used the merge & cut functionality in tmpegenc. I added both m1v files in the screen and on the first part set the slider to the end. I used the button ¦<< to go back 1 frame and set this as the end marker.

The output file was muxed in bbmpeg as normal and surprisingly I did not have any sync errors. I wasn't sure it would work because tmepgenc cannot accurately cut kvcd encodes, but because it was only cutting 1 frame at the end it seemed to work. :D

heller 02-21-2003 09:32 AM

Well, frameserving with V-dub doesn't always help!
I actually got this error again yesterday even when frameserving (at a different point in the film than I ever got errors before). I wonder if realunit's idea of loading extra plugins is true...I load all of them also even though I don't use half of them.

urban tec 02-21-2003 09:39 AM

I've had this a lot lately too, but up until now I have not been able to put my finger on any one particular cause

heller 02-21-2003 12:03 PM

I'm starting to think that particular combinations of filters along with cq's higher than ~70 lead to this, but I haven't done extensive testing to figure it out.

rendalunit 02-21-2003 09:53 PM

I encoded "Heist" three times with TMPGenc 2.510. The first two times I got the "illegal floating decimal point" error and the third time the encoder just froze- no error message.

Now I just finished encoding "Heist" using the same script with TMOGenc 2.58 and it did the whole movie with no errors. I also had a couple apps running at the same time too.

Maybe 2.510 has a bug :idea:

Fiz 02-23-2003 05:19 PM


Originally Posted by ren
Now I just finished encoding "Heist" using the same script with TMOGenc 2.58 and it did the whole movie with no errors...

Ren, did you have to change anything in 2.58? I got the error while encoding an animation first with 2.510, then using perfectcells solution of frameserving from vdub. I got the same error at different stages. I then tried what you suggested with 2.58 and I still get the error! :x :x :x
I even ghosted my machine back to a clean image before I tried everything.

I am now encoding again with avisynth 2.05 to see if that helps, but another 6 hours to go...

To find a pattern to why this happens, I suggest we post what filters we are using and what CQ we are encoding at. May help us get to the bottom of it.

I was using filters FaeryDust and Convolution3d with legalclip and sampler. My CQ was 70.

rendalunit 02-23-2003 08:08 PM


Originally Posted by Fiz
Ren, did you have to change anything in 2.58?

no, I didn't change anything in 2.58. The only filters I used were bilinear resize, temporal smoother and legal clip and I encoded with cq=98. If I encounter this problem again (I'm sure I will) I'll note the filters I'm using and the cq and also environmental priority settings which are DirectShow-1 and ReadAVS.dll -1 (the others are off).

big 02-23-2003 09:31 PM

been having same problem as you is my script...been using tmpenc 2.59 & 2.58...can not put a cq value higher than 70...80 would be my reference value but ot will not take it...

LoadPlugin("C:\Program Files\NimoCodec Pack\Mpeg2dec\Mpeg2dec.dll")
LoadPlugin("C:\Documents and Settings\Mes documents\Programmes\GripFit_preview_0.0c\GripFit_ Preview.dll")
LoadPlugin("C:\Documents and Settings\Mes documents\Programmes\FluxSmooth-1.0\FluxSmooth.dll")
LoadPlugin("C:\Documents and Settings\Mes documents\Programmes\LegalClip-0.2\LegalClip.dll")
LoadPlugin("C:\Documents and Settings\Mes documents\Programmes\Sampler-0.2a\Sampler.dll")
LoadPlugin("C:\Documents and Settings\Mes documents\Programmes\DustV5\DustV5.dll")
LoadPlugin("C:\Documents and Settings\Mes documents\Programmes\TemporalCleaner\TemporalClean er.dll")

avisource("C:\Documents and Settings\Mes documents\Films\Lilo.Et.Stitch.FRENCH.DVDRiP.DiVX-Ulysse.avi")
GripCrop( width=528, height=480, overscan=2)

Fiz 02-24-2003 05:08 AM

Got the same error with Avisynth 2.05 so it rules that out. :? Going back to 2.07 and Tmpegenc 2.510...

I'm trying CQ 69.9 so that I can finish this particular encode. Not sure if it will work but it fails in different places so it's hard to tell unless I leave it running all the way.


Originally Posted by ren
and also environmental priority settings which are DirectShow-1 and ReadAVS.dll -1 (the others are off).

I haven't tried these yet, might give it a go. Just want the encode to finish once! :!:

Fiz 02-25-2003 06:21 AM

Well I'm still having endless trouble with this encode (toy story 2). :cry:

Even if I create a VFAPI avi file from the D2V and use this as the input, it still seems to fail with the same error. I've tried everything that has been suggested so far (even lowering the CQ) but it still fails. The strange thing is that it fails in different places but always between 10% and 25% of the encode.

Is it worth making an huffy lossless avi and trying that way? Anyone else battling to death with one encode thats not working? :( HELP!

wazoqaz 02-25-2003 08:17 AM

I had the same problem about a month ago. No matter what I tried I just could not get a successful encode. I even tried doing a huffy lossless avi in VDub.

I finally got the encode to work by switch from CQ to CQ_VBR. I finally decided that I was willing to sacrifice a little quality just so that I could have the darn thing encoded.

So try CQ_VBR and see if you have any luck.

Fiz 02-25-2003 08:39 AM


Originally Posted by wazoqaz
So try CQ_VBR and see if you have any luck.

Thanks wazoqaz :D , am starting of an encode with CQ_VBR now. I'll set the max and min bitrates the same and do a sample to work out what the CQ should be. Will let you know if it worked!

rendalunit 02-25-2003 07:51 PM

Maybe the problem could be with Avisynth :?: I see that there's been some changes to v2.07 and now there's a 2.08

kwag 02-25-2003 07:55 PM


Originally Posted by rendalunit
I see that there's been some changes to v2.07 and now there's a 2.08

Where's that version 2.08 8O

rendalunit 02-25-2003 07:58 PM

hi kwag,



All times are GMT -5. The time now is 03:18 PM  —  vBulletin © Jelsoft Enterprises Ltd

Site design, images and content © 2002-2022 The Digital FAQ,
Forum Software by vBulletin · Copyright © 2022 Jelsoft Enterprises Ltd.