2016-01-04 17:14 GMT+03:00 Luiz Augusto von Dentz <luiz.dentz@xxxxxxxxx>: > Hi Kyle, > > On Sat, Dec 26, 2015 at 1:18 PM, Kyle Shneider <shneiderkyle@xxxxxxxxx> wrote: >> I'm testing a2dp profile. bluetoothd gets commands from connected >> device, but there are no audio. >> As i get it, reading code of simple-player, you should either pass >> actual player's path as argument of simple-player script of change >> hardcoded /test/player to actual player's path... something like that, >> correct me if i'm wrong. Binded player should have mpris interface, >> like /org/mpris/MediaPlayer2/rhythmbox >> But all linux players use session bus, and in our case we work with >> org.bluez on system bus. So how to properly bind any linux media >> player to simple-player script. > > If you have control over the player you may want to register directly > using the media interface, if you just want to bind an existing player > then you can use tools/mpris-proxy tool, it will detect MPRIS > compatible players and register them, but as the name suggests it will > proxy messages back and forth so it is not recommended for production, > it is just a testing tool. > > -- > Luiz Augusto von Dentz Thanks for answer, Luiz. Current questions: 1) For registering any media player (via RegisterPlayer(object player, dict properties)) i should use it's proxy object on session bus? 2) Audio stream binding happens automatically after registering endpoint and player or there is something more have to be done? Bluetooth daemon finds necessary registered player by itself? 3) Am i right that for a2dp sink i should use MediaControl1 interface and for a2dp source MediaPlayer1? It's just not so obvious reading media-api.txt. -- Kyle Shneider -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
