But, back to the fmod, will I be having a lot of trouble if I were to develop in WinCE, then, later migrate into Win Mobile. Will I be having a lot of surprises in terms of this function?? Feel a bit uneasy about this, since it is not so portable across the platform.
The other thing is that I was wondering whether when I started to play the music, do I need to stop it when it reaches the end of the song or it will automatically stop by itself.
The file just stops playing, and the current position as returned by FMOD remains at the end of the file. My code tests this on a timer to detect when playing has finished. (As I said in the recent thread on (not) getting events from Sound().) But my code is using the timer to update the %age progress through the file anyway.
I've no idea! Like I indicated WinCE is a bit of a movable feast. At least one user here (ceaser) tried getting his app running on WinCE but I believe he gave up and went over to the Windows Mobile version of the device he was targeting.
However, since Fmod is asychronous and there is not call-back function to this, hence you are using a timer to track the end of the playing. :icon_clap:
So, the Fmod.Stop will be used as a user interrupt to stop the playing. Doing an Fmod.Play will resume back the same position where we were previously stopping, I assume.
I've no idea! Like I indicated WinCE is a bit of a movable feast. At least one user here (ceaser) tried getting his app running on WinCE but I believe he gave up and went over to the Windows Mobile version of the device he was targeting.
So, the Fmod.Stop will be used as a user interrupt to stop the playing. Doing an Fmod.Play will resume back the same position where we were previously stopping, I assume.
I think that is correct, though I chose to reset the playing point back about 2 seconds from the point where the user clicked "Pause", at least partly because my files are often speech, so a bit of overlap is useful. Thus I capture the value of fmod.Position before doing fmod.Stop1. It might be that reversing that sequence would always return start-of-file!
Another discovery about FMOD: on the desktop (my XP, anyway) it will play MIDI files, but not on my WM5.0 device.
I think that is correct, though I chose to reset the playing point back about 2 seconds from the point where the user clicked "Pause", at least partly because my files are often speech, so a bit of overlap is useful. Thus I capture the value of fmod.Position before doing fmod.Stop1. It might be that reversing that sequence would always return start-of-file!
Another discovery about FMOD: on the desktop (my XP, anyway) it will play MIDI files, but not on my WM5.0 device.