0
0

Dear Sir/Madem,

Thank you for providing such a good library for the Windows Mobile. I’m in the middle of writing a small mp3 player using the FMOD 3.75 library. But it’s found that FMOD does not support A2DP. I’ve searched the forum but it seems the Windows CE development of FMOD is stopped after 3.75. Will you reconsider to continue the support again?

The problem of FMOD with A2DP is that not only there is no sound come out from the BT headset, the playing speed is also reduced. It seems that FMOD has difficulty to communicate with the wave output device when a BT headset is connected. Besides, I’ve found a piece of notes from a WM expert at http://blogs.msdn.com/medmedia/archive/ … ws-ce.aspx
, he said that…

"When the BT A2DP driver becomes associated, it becomes the "default wave device". For the moment this is done with a hack that moves it to device 0, although this might change in the future. If one wants audio to auto-magically get rerouted to the new device while it’s playing, the application needs to monitor this notification. When the application receives the notification, it needs to take one of two actions:

  1. Stop and restart the filter graph. A side effect of this will be to force the wave renderer to close and reopen the default wave device. The pro of this method is that it’s fast. The con is that it probably won’t handle the case of switching from a wave driver that supports SPDIF to one that doesn’t.

  2. Tear down the filter graph and rebuild it. The pro of this is that it can do a full rebuild of the topology and can switch between drivers that do/don’t support WMAPro-over-SPDIF. THe con is that it might take awhile.

Ideally an application might try method 1, and if that fails, switch to 2."

Hopefully, the FMOD will continue it’s development on the Windows Mobile platform.

Looking forward to your promptly reply.

Cheers,
A_C

  • You must to post comments
Showing 0 results
Your Answer

Please first to submit.