03-16-2025, 02:48 PM
(03-16-2025, 01:59 PM)TheOldPresbyope Wrote: The Chromecast protocol and software are not open source nor completely reverse engineered. Hence, moOde doesn’t have a Chromecast renderer.
I just tried VLC apps on my Google Pixel 6a phone (Android 15) and my Apple iPad (iPadOS 18.3.2). Both successfully stream music to my moOde player using Bluetooth and the iPad using AirPlay. The moOde renderers are enabled, of course.
Regards,
Kent
PS - I’m a native English speaker (well, American English, anyway). I often have to apologize for oddities or inaccuracies in my posts. You’re doing fine!
Hi Kent
thanks for the nice words, I used to be fluent back in the times I worked and lived in MN but those days are over :-( and I'm sometimes struggling with finding the right words ... anyway ...
okay, well now it's working but I don't know why ...
the good : it's working, VLC is playing from the Android to the Moode RPi, audio info (from the web interface of the player locked in 'bluetooth active' mode, similar to the mode when LMS is active
information shows audio chain = Bluetooth - hw - Device
the bad : <tdb>
the ugly : the Android phone suddendly has seen two BT devices
- one named accordingly to the name I defined in the Moode player admin interface "Nowhere"
- the other named "Moode1 Bluetooth"
I see the two devices from the shell with bt-device -l and from bluetoothctl
But where the hell is the 2nd BT device coming from with a name (Moode1) which doesn't exists on my confirguration (for clarity I defined everything to 'Nowhere')
I keep searching ...
PS : for the 2nd option, I am not trying to cast to a Chromecast
I am trying to cast to the Moode device from VLC running on a computer, using the rendering option, but the Moode device (ie, the Rpi, is not seen)