by chrisbo » Wed Mar 16, 2005 3:32 am
I have the same problem, with the "Invalid floating point" popup. There is another dimension to it, though...
When I start MM and try to analyze the volume of a track, MM searches the file until very near the end, and then just breaks before the tag is written.
This problem doesn't occur when I have had an "Invalid floating point" and restarted MM. Then the analyzing runs smooth and fine.
Strange? Yes.
This might help you developers to track this problem down...
/Chris
I have the same problem, with the "Invalid floating point" popup. There is another dimension to it, though...
When I start MM and try to analyze the volume of a track, MM searches the file until very near the end, and then just breaks before the tag is written.
This problem doesn't occur when I have had an "Invalid floating point" and restarted MM. Then the analyzing runs smooth and fine.
Strange? Yes.
This might help you developers to track this problem down...
/Chris