"Invalid Floating Point Operation" message
Moderator: Gurus
-
- Posts: 3
- Joined: Mon Jan 17, 2005 1:08 pm
"Invalid Floating Point Operation" message
I am using a PC running on Windows ME. I am using the latest version of MediaMonkey. I receive this error message at random times (for example, 1 out of every 5 sessions). In almost every instance I was playing from a list (artist, my entire collection, whatever) with shuffle and continuous play selected and level playback volume on. I love this program and will continue using it. However, I would like to no longer see this cryptic error message. I hate restarting the program all the time and interrupting whatever else I'm doing. Please help. Thanks.
You need to be more specific when saying the latest version as there are two latest version available.
The latest stable release is MM 2.2.2
The latest beta is MM 2.3 beta 4
The latest stable release is MM 2.2.2
The latest beta is MM 2.3 beta 4
Download MediaMonkey ♪ License ♪ Knowledge Base ♪ MediaMonkey for Windows 2024 Help ♪ MediaMonkey for Android Help
Lowlander (MediaMonkey user since 2003)
Lowlander (MediaMonkey user since 2003)
-
- Posts: 3
- Joined: Mon Jan 17, 2005 1:08 pm
Invalid Floating Point Operation
Sorry about that. I am referring to the stable version.
-
- Posts: 3
- Joined: Mon Jan 17, 2005 1:08 pm
invalid floating point
no i don't use anything non-standard at all. frankly i wouldn't know how.
Then please generate a debug log as described here: http://www.mediamonkey.com/forum/viewtopic.php?t=69 and e-mail it to me.
Jiri
Jiri
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
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