Kvcd: Avi illegal floating point calculation? Is kvcd3 the cause?
 

Hi,

I have a problem when I try to encode an anime avi file around 3 percent I get an "illegal floating demical point calculation" error and it never passes this point. I've been using the kvcd3 528x480 template and I've also tried the kvcd2 template and it still wouldn't work. I than tried increasing direct show in environmental settings in tmpgenc to a higher priority such as 2 than 3, still nothing errors at the same point. BTW I've been using the latest tmpgenc program which is 2.512.52.161

Than for no reason I try to encode the same file with the standard vcd ntsc film template that ships with tmpgenc, and it worked perfectly, I have an anime series which has 8 episodes and with the kvcd's template I was only able to encode 1 out of 8 and I've tried about 3x. Now with the vcd template I just used it did all 8 flawlessly, but I would prefer to use the kvcd3 templates because the file size is smaller and I can fit more episodes per cd and the quality is SUPER SUPER HOT!!! compared to the vcd's.

Anyhow, I'm not saying that the kvcd3 template is flawed but is there a setting I can change to make it work with my avi's. If you need to know which settings I use just ask.

Thanks!

Scan the AVIs with VirtualDub to see if there are any errors in them, thats what usually causes illegal floating decimal point. Don't know why it would work with the standard template though. If VirtualDub does find an error you can try cutting that part out with the same program.

I've scanned all 8 files and they had 0 frames masked, so what might it be.

HI RAVEN2K2

i have this problem wtih tmpgenc
i don't think it is a problem with AVI becauise i have this when convert from a DVD

and sometimes it works and sometines no, WHY????

jp

I've tried it with 3 versions of tmpgenc and the same thing happens with all 3, the avis have been scanned and they have no errors. Right now i'm doing another anime with like over 36 episodes and it works when encoding to vcd, but only like 6 out of 36 will work if I use any of kvcd templates, weird, can anyone help, thanks!

We've discussed this problem in the TMPGEnc Forum already guys. :wink: There are a lot of approaches to solve this bug, but what helped for me was this:
I went back to version 2.54a which worked like a charm on that particular movie :wink:
try it out!

It still does the same thing with version 2.54, what can be the cause?

What version of Avisynth are u working ?
If it's v2.08 try 2.07 - In some cases it works better than 2.08 !!!??
bman

Can you please post your script in here?

I don't use scripts, what i do i simply go to encoding the avi file directly with tmpgenc, I do the video and audio at the same time.

I have the same problem sometimes and only with CQ. :(
I have already tested all suggestions from various forums (I have also tried - as suggested by Jellygoose - the different TMPG version), but the problem remains...
I have recently found a solution that until now works great for my case: I downclock (yes, downclock! :oops: ) my P4 2.4Ghz lowering FSB (bios advance setting) only before running any encoding: a bit more time to obtain full movie, but nomore error!
I hope this can help someone... :wink:

hi

i sorted this problem by increase the value of vbv buffer size to 60
(fin,d in this forum) and now it works

jp

Whats the vbv value and where is it located?

Also, just thought about this and I thought I should let you know, i'm currently downloading lots of things from emule so my drive is heavily fragmented, so is it possible if my drive isn't defragmented that's whats causing the errors using kwag's templates, cause it works fine with the default vcd template, just asking?

IN THE VIDEO WINDOW
THE DEFAULT VALUE IS 40

JP

The VBV buffer tweak worked wonderfully for me.

Sometimes a quick repair with VirtualDub did (opening and rekeying the entire movie and then saving with direct stream copy), but others not.

The change of this setting should do alone.


Gaudi

Hi. I'm new here but I might help.

I totally eliminated Legalclip() from my scripts and never had the Floating Point error again. I tried removing the filters one by one, but only getting rid of Legalclip() did the trick.

Hope it works for you too.