TMPGEnc: Illegal Floating Decimal Point Error - Page 2

Fiz · #21 02-26-2003, 08:42 AM

I encoded with CQVBR and it did not error so thanks wazoqaz!

But I overshot by 50Mb even though the sample size was almost spot on. I can also see more macroblocks in some scenes compared to my incomplete encodes using CQ so I see what you mean by sacrificing quality.

Quote:

Originally Posted by ren

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

Thanks Ren, as I probably need to encode it once more to hit the mark, I'll try again with CQ and 2.08

digitalize · #22 02-26-2003, 12:16 PM

I had this issue a couple of times on certain fullscreen movies. I fixed the problem by unchecking SSE and SSE2 in the CPU tab. This obviously slows the encode process down some.

big · #23 02-28-2003, 02:29 PM

is it worth it to encode with cqvbr to solve that problem???

or is it better to use a lower cq value if it is working with a low value???

MrRobot · #24 03-05-2003, 08:32 PM

I just started getting the "illegal decimal...error" in TMPGEnc 2.58 with the current avs script everyone seems to be using. Anybody figured this one out or a good workaround? I'm like Ren in that I would like to solve this problem. My encodes quit at different places during the encodes. Here's my script:

LoadPlugin("D:\Video3\mpeg2dec_dll\MPEG2DEC.dll")
LoadPlugin("D:\Video3\mpeg2dec_dll\GripFit_preview .dll")
LoadPlugin("D:\Video3\mpeg2dec_dll\blockbuster.dll ")
LoadPlugin("D:\Video3\mpeg2dec_dll\legalclip.dll")
LoadPlugin("D:\Video3\mpeg2dec_dll\sampler.dll")
LoadPlugin("D:\Video3\mpeg2dec_dll\dustv5.dll")
LoadPlugin("D:\Video3\mpeg2dec_dll\decomb.dll")
LoadPlugin("D:\Video3\mpeg2dec_dll\temporalcleaner old.dll")

AVisource("D:\JanesFinished\JanesProjectRev6.avi") + AVisource("D:\JanesFinished\JanesProjectRev601.avi ") + AVisource("D:\JanesFinished\JanesProjectRev602.avi ")

LegalClip()
FieldDeinterlace()
GripCrop( width=352, height=480, overscan=1 )
GripSize()
SpaceDust()
TemporalCleaner()
Blockbuster(method="noise", variance=.3, seed=1 )
GripBorders()
LegalClip()
#Sampler(length=24)
ConvertToRGB24

kwag · #25 03-05-2003, 10:19 PM

Hi MrRobot,

I think your line ConvertToRGB24 should go AFTER the AVisource line

-kwag

MrRobot · #26 03-08-2003, 08:06 AM

Actually, putting the ConvertToRGB24 line works by putting it at the end like that. I have encoded several projects on my PC running windows ME with this line at the end. If you remember, the old FitCD had this line at the end also. My laptop running windows XP doesn't need this line however.

I have encoded .d2vs with the dust filters on several occasions with success. Now they seem to hang up the encoding. I tried both SpaceDust and FaeryDust with this particular avi and had no success. When I commented that filter out, it encoded like a champ. Go figure.

Thanks alot for all you do. Your patience is awesome. You da man!!!!!!!!!!!!!!

vhelp · #27 03-08-2003, 09:22 AM

Morning everyone.. rendalunit.. MrRobert,

* did you install or un-install any apps and/or drivers (any)
recently ??

* did you (and others here) try and drag your AVS scripts into
vdub, to see if it opens, and then proceed to scan through
it (by dragging the time-line marker Lf to Rt) ??

* have you all tried feeding the AVS script into vdub (w/out any
convertToRGB24()) and let vdub do the color conversion, then
frameserve it into TMPG. This is the route I usually take in my
encodes.

I'm one of those who suffer the color issues if I frameserve (directly)
an AVS script into TMPG. instead, I have to go the AVS -> vdub -> TMPG
route and everything is perfect (color'wise)
It may all very well be that you may have to take this route. But, it's
not really all that bad. I rather prefer it this way anyways, as I can
see my changes when I fiddle w/ AVS scripts

If you add in the line version() in your AVS script,
(but preferebly create just the script w/ version() in it)
and dragged it into vdub let us knew what it says so we can see
exactly what version of AVS you are using.

rendalunit..
I tried your script as is copy/past into a new AVS file, and
dragged into vdub, and yes, it worked there. I scanned through
the whole *.D2V file that way, and got no errors yet.
Did you try this route ??
And, if you don't mind my asking, where in the encode are you getting
this error (if during encoding) ??

rendalunit..
for test perpuses, I'm encoding the first 21 minutes of Get Karter
using your script and feeding the AVS script directly into TMPG. Yes, I
at the moment, I can see I'm suffering the color issues. I can see the
color as it looks solor flare'ishy or something like that. But, I'm
not keeping this, and again, it's for test purposes. I'm trying to see if
it crashes or give me an error message like yours or others here. Well,
it's got like 50 minutes left to go. I'll report back my final results. K ?

Note: I've ben meaning to install the latest AVSynth version but
due to other things going on, I haven't yet reached that point. So, the current
version of mine is still: Avisynth v1.0 beta 5

Well, I must say, I have like 18 different windows opend w/ things going
on, and 57% resources left, but so far, I'm having no trouble w/ encoding
the original script at hand.

Have a good day all.
-vhelp

vhelp · #28 03-08-2003, 10:35 AM

Morning everyone.. rendalunit.. MrRobert,

FYI:
Ok, I just finished the first 21 minutes of encode and all went well.
hmmm... So, I don't know why you are having issues.
I used TMPG v2.53 and Avisynth v1.0 beta 5
and the output was "solor flare city" but good quality still.. and no sound..
I forgot about the sound

rendalunit..
I did notice something odd, you AddBorders( 8,68,8,68 ) was curious..
as I could see the empty space on top and bottom, in other words, it actually
shrank the video clip top to bottom some. But, quality was good.

-vhelp

dazedconfused · #29 03-19-2003, 04:24 PM

Well, I've gotten this "Illegal floating decimal" error twice this morning with TMPG 2.510 (this makes about the 4th or 5th time for me over ~ 2 months of kvcd-ing). Both times today, it happened @ 73% (source position 16:44) into the encoding of a ~ 23minute fullscreen anime.

Since this hasn't happened very often for me, I decided to just try the exact same script and settings on the 2nd try to see what would happen (the first 2 times I ever got this error, I simply lowered my CQ by .1 and then it worked). I guess I'm going to have to try that trick once again here and see if it works (hopefully I won't have to resort to any of the other "things to try" listed in this thread). It'd be nice if there would be a totally stable TMPG release one of these days...it seems like there's always some tiny bug here or there that needs working out.

Guess we really can't complain though, considering the price!

-d&c

Code:

here's the script I was using:

Mpeg2Source("E:anime.d2v")
Telecide()
Decimate()
LegalClip()
GripCrop(width=544, height=480, overscan=2, source_anamorphic=false)
GripSize()
mergeluma(blur(.25))
mergechroma(blur(1.2))
FaeryDust()
MSharpen()
FluxSmooth(15,10)
TemporalCleaner()
DctFilter(1,1,1,1,1,.5,.5,0)
GripBorders()
LegalClip()

*by the way, does anyone know if this filter ordering is ideal? Or should I place mergeluma/chroma or MSharpen elsewhere? It's my first time doing anime. Thanks.

rendalunit · #30 03-19-2003, 04:55 PM

Wow i wonder why the board didn't show my any new posts in this thread since last month

Quote:

Originally Posted by vhelp

I used TMPG v2.53 and Avisynth v1.0 beta 5

hi vhelp,
that version of avisynth you're using is kinda old isn't it

You might consider upgrading your versions of AviSynth and TMPGEnc

So far I haven't had this error and I've been doing lot's of encoding lately

I'm using:
TMPGEnc 2.58
AviSynth 2.08

*not using GripCrop because I found it's super slow with some DivX sources for some reason

my system is P4 1600 w/ win xp

I'm not frameserving with VDub because it disrupts my routine too much

ren

sh0dan · #31 03-19-2003, 05:06 PM

Try the newest 2.08 "legacy" build from the CVS-bin site in my sig. This seem to cure many "Float point" problems!

kwag · #32 03-19-2003, 07:36 PM

Got it

Thanks sh0dan

-kwag

vhelp · #33 03-19-2003, 07:50 PM

hi rendalunit.. pal..

>> Wow i wonder why the board didn't show my any new posts in this thread
>> since last month

..I know how you feel. I'm having this same issue (even now, as I write this)
over had dvdrhelp - - Star Wars.. thread there, that I posted at a few times
and I was keeping track w/ it. Now, I have to find out (at work) that it's
ben updated w/ new items - rats !!

>> that version of avisynth you're using is kinda old isn't it You might
>> consider upgrading your versions of AviSynth and TMPGEnc

yes, ya bumm he he..

I'm still finishing up on lots of projects and I really
don't want any excuse for any of them to have other issues, by installing
other codecs or plugins etc, in other words, I don't want to taint/jinx meself.
However, if all it is is a DLL, I'd be

HAPPY

to push it into my ..\systems
directory and give AVIsynth a go.. and not to mention mauddib's.. app
(though I have tried it out quite a bit, but that most of the "latest" Filters he
incorporated don't work do to the version of AVIsynth I have. I heard that it was
just a DLL, but I can't be sure. Do you (or anyone know) ?? ??

>> I'm using:
>> TMPGEnc 2.58
>> AviSynth 2.08

Thanks, but I'm sticking w/ TMPG v2.53 for now. I have no complaints, and see
no real benefit to upgrading to higher version.
I'll look into AVIsynth, pending yourr' or anyone elses response to Q above.

Well, I've ben messing around w/ some more divX stuff. In one project, I'm
planning on capping an hour's worth of some movie and encoding it to divX and
finally, see how it looks when re-ended to MPEG-2 (CVD maybe)
I don't know if you do divX project (divX -> TMPG -> kvcd) but if you do,
and you want to check out some samples, I'll post here for you (and others)
K ?

Gosh, so many fun things to do he he.. Don't you just love it all ??

Well, it's 7:49pm here in NY.. Have a good evening everyone.
-vhelp

MrRobot · #34 03-19-2003, 10:22 PM

I got rid of my illegal floating point problems by going back to fluxsmooth and blockbuster noise instead of faerydust and temporalcleaner.

dazedconfused · #35 03-20-2003, 07:37 PM

Follow up to my previous post:

1) raising CQ by .1 (60 to 60.1) didn't help, although it did get to 76% instead of 73% completed.

2) lowering CQ by .1 (60 to 59.9) didn't help (as it previously had for me on two 16:9 movies that incurred an "illegal float" error). Errored at same exact spot.

3) Installing Avisynth 2.08legacy didn't help. (CQ60) Same Error, same spot.

4) Strange behavior! lowering CQ to 59.9 while using Avisynth 2.08legacy didn't help. But, TMPG had made it to 100% complete and showed no floating point error! In actuality, it had stopped at the same spot as before because the m1v was the same size as previous ones that had errored at 73%.

5) Used SpaceDust instead of FaeryDust in the script and it finally worked! 100% completed, no "illegal float" error, correct final m1v size.

What a pain in the a**!

It took ~ 2days to encode one lousy 23-minute 'toon! I mean, I'm a patient guy(I usually use FaeryDust for goodness sake!...so you know I've gotta be patient!

), but this was pushing my limits. What's strange is that this particular episode was the 7th one in the series, and I had already used the exact same script on the previous 6 with no problems whatsoever. Then I ran into all these problems on the 7th one. They were all practically identical I'd say in terms of their makeup (colors/size/action/etc). Oh well. I don't know what set this little bug off or from where it derived exactly, but I hope I don't EVER see it again. Think I'm gonna switch to SpaceDust instead of FaeryDust for the rest of this series, that's for sure.

Thanks to all for your advice.

-d&c

UPDATE#2: I ran a batch encode of 9 more episodes last night substituting only SpaceDust for FaeryDust in my previous script with no other changes, and no errors occurred. I guess it was just something about that particular episode and the combination of filters I was using with FaeryDust.

gbon · #36 04-02-2003, 11:08 AM

Did this issue die for lack of interest or was it cured by something in the previous posts?

I would like to know if it was solved.

thanks

labomba · #37 04-06-2003, 10:28 PM

Hi Guys

My turn to fight with this illegal damn...:

Look this log of Tmpgenc 2.58

Code:

Start: 6/4/2003 22:27:58
End: 6/4/2003 23:52:35
Dealing time: 01:24:37
-------------------------------------------------------------
E:\LILOSTITCH_LAM\VIDEO_TS\LILOSTITCH_LAM.m1v
  Format: ToK (MPEG-1 704x480 23,976fps CQ 80,34)
  Video: E:\LILOSTITCH_LAM\VIDEO_TS\LILOSTITCH_LAM.avs
  Audio: none

  Result: Illegal floating decimal point calculation order
  Dealing time: 01:24:37
-------------------------------------------------------------

The same with 2.510 version, I'm trying to solve this about 1 week (worse: 7 long nights

).

Can anyone help ???

LaBomba

PS. Some figures: avisinth 2.08, anime DVD souce, using a lot of scripts options, including MSharpen() filter ever.

jorel · #38 04-06-2003, 10:45 PM

hi labomba

i got some problems using avisynth 2.08...

using TMPGenc 2.510 ,2.59 or 2.58 !
after remove avisynth 2.08, all versions is working fine!

maybe is your problem too,..

ps:
sometimes i read that versions of TMPGenc have bugs,
one faster than another,etc.
i never feel any differences in this versions...for me all working and got the same size,time to encode,etc!

labomba · #39 04-06-2003, 11:27 PM

Thanks Jorel!

I downloaded the 2.08 legacy version adviced by Shodan. If this problem occurs again, I'll back to the 2.07 version.

LaBomba

dazedconfused · #40 04-07-2003, 01:55 AM

Hey Labomba,

Posting the script you used when you got the error might be helpful (emphasis on "might").

I've been using avisynth 2.08-Legacy ever since Sh0dan recommended it in this thread, and I haven't had another problem since then on any regular movies I've encoded. After I switched from FaeryDust to SpaceDust, the rest of the cartoons I was working on at the time I posted in this thread all completed 100% successfully. Maybe try changing a few of the filters you're using? Good luck.

-d&c