@tomkat83 said:
My guess is that you messed something up with the PATH variable. This line takes the existing paths of Rasplex and then adds your additional new path to Squeezelite # Path to squeezelite bin PATH=$PATH:/storage/.plexht/userdata/squeezelite
Then drop $PATH command later: # Start SqueezElite $SL_BINARY -n $SL_NAME -o $SL_SOUNDCARD
Hi tomkat83,
Could you post your autostart.sh file because, i think i 'missing something and for example every forum speaking of autostart in openelec specify a syntax like this : (script)&
So I’m not quite confident with your code.
Anyway thank you for your time.
Look at my very first post, step 6. My entire autostart.sh is there. Works perfectly :-).
You have to be careful when copy-pasting anything into SSH sessions - in my case, that introduced an unwanted line break in the very last line, which broke my autostart.sh. Simply remove the line break then.
@tomkat83 said:
You have to be careful when copy-pasting anything into SSH sessions - in my case, that introduced an unwanted line break in the very last line, which broke my autostart.sh. Simply remove the line break then.
OK thanks I’ll pay attention to last line. By the way, can you explain (I mean in your comment you said what is the function but not what are the variables and why) this portion of your autostart, because in my configuration the output is not the HDMI but the HifiBerry Amp+, : #ALSA-SETUP ############ #Force Alsa output to HDMI (2=HDMI) amixer cset numid=3 2 #Set Alsa volume to 100% amixer cset numid=1 400
Also the -Z in your command : # Start SqueezElite $SL_BINARY -n $SL_NAME -o $SL_SOUNDCARD -a $SL_BUFFER -r $SL_BITRATE -C $SL_TIMEOUT -z
Sorry by advance for my newbie question but in the piece of code, for starting the SqueezeLite, you don’t declare the path you set in the variables as PATH, how does the raspberry pie know the path ?
@KMickael, judging from your edits, you managed to get everything running by now? Could you please share your autostart.sh for others?
The amixer commands tell SqueezeLite what audio output to use and at what volume (SqueezeLite uses alsa).
The PATH thingy is indeed the path variable :-). Check https://en.wikipedia.org/wiki/PATH_(variable). Hence by appending the squeezelite path to PATH, you don’t need to call squeezelite with its path. I did not manage to call squeezelite directly without this “detour”.
Because I have several raspberry pi in my flat, I had to add this variable in each AutoStart (with a fake MAC Address because with the real one there is a conflict with Rasplex) :
SL_MAC_ADDRESS="01:01:01:01:01:01”
I can confirm that it works with Plex Media Player for Raspberry Pi 2. Only need to create userdata/squeezelite folders and change the path from plexht to plexmediaplayer. SSH password is plex
@robicc said:
I can confirm that it works with Plex Media Player for Raspberry Pi 2. Only need to create userdata/squeezelite folders and change the path from plexht to plexmediaplayer. SSH password is plex
Thanks for the info.
Suggest you start a new topic in the Plex Media Player forum, this is the Rasplex forum.
@KMickael said:
I tried to setup a fresh new installation on Rasplex 1.0.1 but my autostart doesn’t work anymore. Squeezelite is not load on start.
Now I got Squeezlite on start but not the Rasplex’s GUI
So after some tests, i can say that is the buffer variable ( SL_BITRATE=“384000”) who is responsable. When I desactivate this variable Rasplex GUI can start but Squeezelite doesn’t work. And When i activate the setting SL_BITRATE, Squeezelite works but not Rasplex.
@KMickael said:
I tried to setup a fresh new installation on Rasplex 1.0.1 but my autostart doesn’t work anymore. Squeezelite is not load on start.
Now I got Squeezlite on start but not the Rasplex’s GUI
So after some tests, i can say that is the buffer variable ( SL_BITRATE=“384000”) who is responsable. When I desactivate this variable Rasplex GUI can start but Squeezelite doesn’t work. And When i activate the setting SL_BITRATE, Squeezelite works but not Rasplex.
I don’t know why but with Rasplex 1.0.1 i have to comment those 2 lines in the autostart : Bitrate and Buffer. Anyway it’s working
@KMickael said:
I tried to setup a fresh new installation on Rasplex 1.0.1 but my autostart doesn’t work anymore. Squeezelite is not load on start.
Now I got Squeezlite on start but not the Rasplex’s GUI
So after some tests, i can say that is the buffer variable ( SL_BITRATE=“384000”) who is responsable. When I desactivate this variable Rasplex GUI can start but Squeezelite doesn’t work. And When i activate the setting SL_BITRATE, Squeezelite works but not Rasplex.
I don’t know why but with Rasplex 1.0.1 i have to comment those 2 lines in the autostart : Bitrate and Buffer. Anyway it’s working
I’m experiencing crashes (in fact a freeze but i can’t connect to Rasplex via ssh) with Rasplex. I changed the SD Card and maked a clean install but Rasplex (when playing a movie or a cartoon) is still craching after few minutes (arround 5).
@KMickael said:
I tried to setup a fresh new installation on Rasplex 1.0.1 but my autostart doesn’t work anymore. Squeezelite is not load on start.
Now I got Squeezlite on start but not the Rasplex’s GUI
So after some tests, i can say that is the buffer variable ( SL_BITRATE=“384000”) who is responsable. When I desactivate this variable Rasplex GUI can start but Squeezelite doesn’t work. And When i activate the setting SL_BITRATE, Squeezelite works but not Rasplex.
I don’t know why but with Rasplex 1.0.1 i have to comment those 2 lines in the autostart : Bitrate and Buffer. Anyway it’s working
I’m experiencing crashes (in fact a freeze but i can’t connect to Rasplex via ssh) with Rasplex. I changed the SD Card and maked a clean install but Rasplex (when playing a movie or a cartoon) is still craching after few minutes (arround 5).
I’ll try with another Rpi 2 today.
So after a lot of testing. The problem was i was not using the Rasplex Installer.
@KMickael said:
I tried to setup a fresh new installation on Rasplex 1.0.1 but my autostart doesn’t work anymore. Squeezelite is not load on start.
Now I got Squeezlite on start but not the Rasplex’s GUI
So after some tests, i can say that is the buffer variable ( SL_BITRATE=“384000”) who is responsable. When I desactivate this variable Rasplex GUI can start but Squeezelite doesn’t work. And When i activate the setting SL_BITRATE, Squeezelite works but not Rasplex.
I don’t know why but with Rasplex 1.0.1 i have to comment those 2 lines in the autostart : Bitrate and Buffer. Anyway it’s working
I’m experiencing crashes (in fact a freeze but i can’t connect to Rasplex via ssh) with Rasplex. I changed the SD Card and maked a clean install but Rasplex (when playing a movie or a cartoon) is still craching after few minutes (arround 5).
I’ll try with another Rpi 2 today.
So after a lot of testing. The problem was i was not using the Rasplex Installer.
I was having issues with squeezelite behaving with RasPlex 1.0.3. Squeezelite would keep
“going away” when viewing the list of players in the LMS setup tab – like the daemon was restarting over and over. However, if I disabled the autostart.sh and launched it manually from ssh, it worked fine. I never determined exactly what was wrong, but I assume there was some conflict with RasPlex during initialization, so I moved the contents of autostart.sh to a separate script, squeeze.sh, and added a “sleep 30” at the top of the squeeze.sh script. Autostart.sh is now just one line “/storage/.config/squeeze.sh&”. This fixed whatever my problem was. I am sharing this is case someone else encounters the same issue.
I’ve been going crazy, because my rasplex became a Squeezelite player without my having actually installed anything on it…
I’ve just realised that I am using the LMS-to-UPnP bridge plugin for LMS and that has automatically added the Rasplex RPi as a player. It all works fine, although you can’t synchronize, so that may be a simpler way of dealing with this. You can just install it from the LMS Plugin repository or here
@gcgst1 said:
I was having issues with squeezelite behaving with RasPlex 1.0.3. Squeezelite would keep
“going away” when viewing the list of players in the LMS setup tab – like the daemon was restarting over and over. However, if I disabled the autostart.sh and launched it manually from ssh, it worked fine. I never determined exactly what was wrong, but I assume there was some conflict with RasPlex during initialization, so I moved the contents of autostart.sh to a separate script, squeeze.sh, and added a “sleep 30” at the top of the squeeze.sh script. Autostart.sh is now just one line “/storage/.config/squeeze.sh&”. This fixed whatever my problem was. I am sharing this is case someone else encounters the same issue.
This is awesome. I got everything working based on recommendations from this thread, including the wait/sleep parameter here.
I had to change the bit rate to SL_BITRATE=“192000” for it to work, but that’s fine.
Does anyone know if there is a functional difference between using this on Rasplex vs another Squeezelite system, like PiCorePlayer? Do we give anything up?
It seems the latest Rasplex has broken this. LMS still sees my Rasplex as a Squeezelite option, but no sound comes out. Anyone have an idea of what happened?b
