Spotify web player in moOde local display

[TheOldPresbyope]

@Ale2.0

From your question in the "Upcoming moOde 8.2.3 release" thread, I inferred you are trying to run the Spotify web player (https://open.spotify.com) in the moOde local display (which uses chromium-browser). If my inference is wrong, then this message is just a typing test.

Out of curiosity, I tried reaching the Spotify web player using Raspberry Pi OS on my Pi400. It works fine and can stream to the Spotify renderer on any of my moOde players. This is with chromium-browser 104.0.5112.105, same as the version installed in moOde.

Then, on a moOde player with a LCD display, I hacked /home/pi/.xinitrc to start chromium-browser at https://open.spotify.com. The expected first page showed up and I proceeded to log into my premium account [1]. Oops, instead of the Spotify home screen, I get a "Playback of protected content is not allowed" screen. I did a little digging on the InterWeb™ and figured out that the desktop version of RaspiOS installs library libwidevinecdm.so but the lite version does not.

I just needed to run the following on my moOde player

Code:

sudo apt-get install libwidevinecdm0

and restart the local UI.

Now I can log into my Spotify account, select a playlist, direct the stream to the Spotify renderer running on the same or other player, and listen.

At this point, however, the wheels came off the wagon: the interface became unusable (IMHO) as I tried to look for other selections. I won't go into details; you can explore for yourself. 

To add insult to injury, the app even forgets my login credentials despite me choosing "remember me". Admittedly, I didn't explore why this difference with the desktop version of RaspiOS.

At this point I'm done since I'm not interested in this use case personally. Perhaps with some more poking you can make it work for you.

Regards,
Kent

[1] I plugged in a USB keyboard to use in logging in.

[Ale2.0]

@Ale2.0

From your question in the "Upcoming moOde 8.2.3 release" thread, I inferred you are trying to run the Spotify web player (https://open.spotify.com) in the moOde local display (which uses chromium-browser). If my inference is wrong, then this message is just a typing test.

Out of curiosity, I tried reaching the Spotify web player using Raspberry Pi OS on my Pi400. It works fine and can stream to the Spotify renderer on any of my moOde players. This is with chromium-browser 104.0.5112.105, same as the version installed in moOde.

Then, on a moOde player with a LCD display, I hacked /home/pi/.xinitrc to start chromium-browser at https://open.spotify.com. The expected first page showed up and I proceeded to log into my premium account [1]. Oops, instead of the Spotify home screen, I get a "Playback of protected content is not allowed" screen. I did a little digging on the InterWeb™ and figured out that the desktop version of RaspiOS installs library libwidevinecdm.so but the lite version does not.

I just needed to run the following on my moOde player

Code:

sudo apt-get install libwidevinecdm0

and restart the local UI.

Now I can log into my Spotify account, select a playlist, direct the stream to the Spotify renderer running on the same or other player, and listen.

At this point, however, the wheels came off the wagon: the interface became unusable (IMHO) as I tried to look for other selections. I won't go into details; you can explore for yourself. 

To add insult to injury, the app even forgets my login credentials despite me choosing "remember me". Admittedly, I didn't explore why this difference with the desktop version of RaspiOS.

At this point I'm done since I'm not interested in this use case personally. Perhaps with some more poking you can make it work for you.

Regards,
Kent

[1] I plugged in a USB keyboard to use in logging in.

Ciao Kent

Thank you very much for sharing your experiences!

I did the same but never came over the warning...
It is not quite logical to me but may the cause be that I am using an RPI3?

I yet don't want to belive it but it seems the most logical answer to me.

Thank you very much.

[TheOldPresbyope]

I would be *very* surprised if using a Pi3 instead of a Pi4 makes the difference but someone else will need to figure out the actual cause.

[Ale2.0]

I think I found the culprit...

I am pretty sure I am running 64Bit moode as it seems kinda suggested whilst downloading.

But apparently it won't work with 64bit.
Maybe I can install 32bit chromium? (any problems to be expected?)

I'lll have to play around in order to confirm it but If you're running 32bit it would be a rather safe guess.

Greetings

Interesting links:
https://www.raspberrypi.com/news/raspber...os-64-bit/
https://raspberrypi.stackexchange.com/questions/124652/still-cannot-watch-netflix-despite-installing-widevine
https://forums.raspberrypi.com/viewtopic.php?t=329426

[TheOldPresbyope]

Nice find.

I could have sworn I'd loaded 64-bit desktop RaspiOS on my Pi400 but I just checked and it's 32-bit (armv7l). Naturally it's running 32-bit Chromium.

Since I've already reflashed the uSD card I used in my quick-n-dirty moOde test of Spotify Web Player I can't swear to what was on it. I do almost 100percent of my moOde testing with the 64-bit version but I know there was at least one 32-bit copy lying around at one point. I might have grabbed it without thinking.

Anyway, it'll be easy enough for you to test on your system.

ETA - Shouldn’t cause any problems just replacing 64-bit chromium-browser with 32-bit version but easy enough to revert if there are. Or just start with the 32-bit moOde image.

Regards,
Kent

[Nutul]

Nice find.

I could have sworn I'd loaded 64-bit desktop RaspiOS on my Pi400 but I just checked and it's 32-bit (armv7l). Naturally it's running 32-bit Chromium.

Since I've already reflashed the uSD card I used in my quick-n-dirty moOde test of Spotify Web Player I can't swear to what was on it. I do almost 100percent of my moOde testing with the 64-bit version but I know there was at least one 32-bit copy lying around at one point. I might have grabbed it without thinking.

Anyway, it'll be easy enough for you to test on your system.

ETA - Shouldn’t cause any problems just replacing 64-bit chromium-browser with 32-bit version but easy enough to revert if there are. Or just start with the 32-bit moOde image.

Regards,
Kent

Hi all,

super-off-topic this one of mine, but... what do you goys mean with the "ETA" acronim? Asking, because "Estimated Time of Arrival" doesn't suit the case...

Thanks.

[TheOldPresbyope]

I picked it up from Tim on the assumption it meant”edited to add” or somesuch. If it means something else, then my bad.

[Tim Curtis]

ETA = Edit To Add

[Nutul]

Thanks for sharing, guys.

ETA: Off-topic closed. ;-)

[Ale2.0]

Hello there, regarding just replacing chrome I ran into issues which I seem to be unable to resolve:

   

Anyone more knowledgeable who could help me?
(uninstalling chromium is not possible)