View Single Post
Posts: 17 | Thanked: 0 times | Joined on Jul 2008
#169
Originally Posted by Johnx View Post
Well, it's not perfect yet and the "setup program" is somewhat less than elegant, but it "works for me" (TM) and I couldn't convince anyone else to test it. Just follow the instructions carefully and it should work well.

That's it for now. Tell me how it works for you. Keep in mind this is very beta, and that I don't consider this finished yet. If anyone is interested in the "source" package for this .deb tell me and I'll upload it as well. It's really just a script and a config file.

-John
Hi John,

I tested this on a brand new freshly flashed diablo installation. Being a newbie of the highest order, it took me a while to get everything together. I first had trouble installing mPlayer due to a lack of three libraries, (libtheora0, libmad0, libogg0). I then found those libraries, but they were incompatible, until I found out about the "Red Pill" trick. I have to say, your package installed nicely, and also I'd like to thank the many commenters who have left clues about the various tricks of the trade involving installation for those of use who are neophytes.

Here's my application: I have a home audio system (Sony HT-CT100) and attached to the digital media port I have the Sony TDM-BT1, a bluetooth input device with the A2DP profile. This device works flawlessly with my Nokia N75, which has A2DP support built in.

I'm using mPlayer version mplayer_1.0rc1-maemo.29.n8x0_armel.deb with the KMPlayer gui. I'm using a2dp-support_0.9_all.deb, with the osso-statusbar-cpu running in the system tray (a great suggestion). The music I'm playing is the files that were ripped from CDs.

I have no problem at all connecting with the device, and the music plays, except there is a great deal of skipping. A song will play for about a second, then skip with a gap of about 1/2 second and then continue to play. Once it seemed like the pitch of the songs were altered. There are not any problems with crashes or functional changes in the mPlayer, which is good. I'm guessing that the processing is not keeping up the the data stream.

I was wondering: do you have a suggestion on what to do next? Any suggestions would be greatly appreciated. Being a newbie, I don't think I'm qualified to try Simon's porting of the A2DP encoding in the DSP, unless it was packaged as a deb file. If it is not too difficult, I could try, but the directions would have to be pretty explicit. Also, am I using the latest version of your software?

Finally, when I first tried to sync up my N810 to the TDM-BT1, I sent a support request to Nokia, explaining that I could connect with my N75 but not my N810, and asked them if they supported A2DP. I got the usual boilerplate reply: A2DP is not supported and we don't recommend using third party products blah, blah, blah. I have to think, though, that Nokia is aware of this glaring hole in the capability of the N810, seeing that the N810 is a perfect tool for storing, playing and streaming music. After all, the first request for this (bug 667) was in 2006.. It seems a bit odd that my N75 works like a charm and the presumably more powerful N810 is still lacking the A2DP profile. Is there a technical reason for this?

Anyway, thanks again to everyone for their contributions, and I'm looking forward to any new developments.