Log in

View Full Version : floating point query


pcs334
2nd May 2002, 23:36
hi
i`ve only been using (trying:( ) dvd2svcd for about a week although i`m not new to riping dvd`s.
I`m using cce 2.64 because 2.5 gives me strange artifacts occasionally, although it does work well apart from that.
The problem i`m getting with cce 2.64 is this error message generated by dvd2svcd while encoding- "is not a valid floating point value.
Then when the encoding finishes cce hangs before crashing and dvd2svcd hangs.

Any ideas anybody plzz
;)

markrb
2nd May 2002, 23:48
2.64 is not officially supported. Only 2.5 or 2.62 are supported.

Mark

orbit-r
12th June 2002, 12:34
hi
never had this problem before but now i got the same error message as pcs334..
anybody know what this message means?

thanxs
orbit-r

equilibrium
13th June 2002, 14:00
If you look at Cinema crafts site CCE Pro 2.66 that they are now on, specifies a Pentium 4 as the CPU of choice. I'm guessing 2.64 may have done as well.

What CPU do you have ? I'm guessing you are both AMD Athlon. I am as well btw and I stick to using 2.5 and don't have any issues with it.

If you are getting floating point errors I would guess that it is due to inconsistencies between AMD FPU's and P4's.

If you follow all the recommendations on this site for optimising your system for encoding (de-fraged hard disk, plenty of space, upto date 4 in 1 drivers if you have Via chipset etc, etc. ) 2.50 should do you fine, whichever type of processor you have.

Equilibrium

orbit-r
13th June 2002, 15:30
hi
after patching with the newest tsunami patcher everything wents fine.
i guess its right that cce have problems with the athlon cpu (some commands and stuff) however this was the first and hopefully the last time i got this error:)

thanx
orbit-r
ps: i don`t think its a HD space problem...

equilibrium
13th June 2002, 16:59
Good to here.

Btw. I wasn't implying it was a HD space problem, it's just one of the healthy principles for encoding that you keep plenty of additional free space and keep the data defragged. But thats just one of a number of principles for keeping encoding reliable.

All I ment was follow the general house keeping bits and I find that 2.5, AMD, Via combination works fine.

Regards