And i found another usecase for it..
I do run Alarms on some players.
Whenever that Alarm is active it wipes the last playlist from that
player and adds the alarmplaylist/file as its playlist.
So it doesnt matter if that particular DSTM is a bug or a feature.
If you really what do "save" your
gregklanderman wrote:
> Nice that you found that work-around, but it really seems to just be a
> bug in DSTM.
>
i am pretty sure its a feature not a bug
eg /plugins/playhistory (also from Michael) do show these tracks.
There was a discussion about "i started with this track and dtsm drifts
Sound familiar?
https://forums.slimdevices.com/showthread.php?95219-Recurring-playlist'
JJZolx's Profile: http://forums.slimdevices.com/member.php?userid=10
View this thread:
gregklanderman wrote:
> Great idea, I cannot tell you how many times I've accidentally hit play
> instead of add over these many years.
>
> I'm not sure you really have to intercept every update to the current
> playlist, possibly just intercepting the clear playlist that happens
> when you
tuc wrote:
>
> It made me think about another feature that I have been wishing for for
> a long time:
> Sometimes I (or friends) accidentally zap the active playlist by
> pressing "play" to an item found by a search in the music library. I
> would like to be able to "go back" to the previous
DJanGo wrote:
>
> That moves the 1st file to 2.nd place and back again.
> And that move is recon by lms and it saves the cached playlist.
Nice that you found that work-around, but it really seems to just be a
bug in DSTM.
I haven't used DSTM but I think I think maybe Michael wrote that
DJanGo wrote:
> btw: there is a "issue" in the script
>
> it always move the first tracks to 2.nd postion when there is a 2nd
> Track and moves it back to its org. position to ensure dstm filled
> playlists are updated.
> By doing this the filestamp of the playlist is changed before copied
DJanGo wrote:
> We are talking/writing about the same.
>
> A saved Playlist- is an entirely different kind of flying altogether!-
> ;-)
I tried your one-liner yesterday and it works!
Thanks a lot.
-thomas
--
*Server*: Raspberry Pi 3 running LMS 7.9.0
*Players*: SB receiver + 4 SB boom,
DJanGo wrote:
> save the script, make it executable and let it run
>
btw: there is a "issue" in the script
it always move the first tracks to 2.nd postion when there is a 2nd
Track and moves it back to its org. position to ensure dstm filled
playlists are updated.
By doing this the
tuc wrote:
> Sometimes I (or friends) accidentally zap the active playlist by
> pressing "play" to an item found by a search in the music library. I
> would like to be able to "go back" to the previous active playlist. Now,
> this is quite tricky since it would require every update to the
tuc wrote:
> PS: I will try your solution to my original post later today and let you
> know how it went.
> PPS: Long live LMS :-)
first please make sure you've got an answer
Code:
which nc
which sed
otherwise you need to install nc / sed
DJanGo wrote:
> We are talking/writing about the same.
>
> A saved Playlist- is an entirely different kind of flying altogether!-
> ;-)
Again thank you!
I have now digested the command you provided (at least to some
degree:-)). It is the first time I have thought about what the CLI can
really
tuc wrote:
> Wow, so cool! Thanks!
> Just to be sure.
We are talking/writing about the same.
A saved Playlist- is an entirely different kind of flying altogether!-
;-)
DJanGo's Profile:
DJanGo wrote:
> add that line in front of your crontab reboot similar to this:
>
> pl:ay:er:ma:ca:dd:re:ss -> the mac adresss of the player
>
> >
Code:
> >
> printf "pl:ay:er:ma:ca:dd:re:ss playlist move 0 1\n pl:ay:er:ma:ca:dd:re:ss
playlist move 1 0\nexit
tuc wrote:
> I do use "Dont stop the music". I will try your suggestion. Thanks very
> much.
>
> I have a crontab entry that makes the server reboot at night (perhaps
> overkill on a linux based system :-)) so it would be even better if I
> didn't have to do anything. Or perhaps I could do
DJanGo wrote:
> Do you use Dont Stop The Music / Lastmix?
>
> If yes - just add another / remove any track on your own to the playlist
> before you stop lms.
> Adding tracks from dstm didnt didnt trigger "change the cached / stored
> playlist".
I do use "Dont stop the music". I will try your
It should be possible to resolve your problem without you having to
start from scratch.
Knowing it is a self-install helps to remove some lines of enquiry.
Paul Webster
http://dabdig.blogspot.com
Author Radio France (FIP etc) plugin
Paul Webster wrote:
> Did you install LMS by yourself or use 3rd-party package like
> piCorePlayer (pCP)?
Oh, I installed LMS myself. I hadn't looked into pCP. I will have a look
now.
Cheers.
-thomas
--
*Server*: Raspberry Pi 3 running LMS 7.9.0
*Players*: SB receiver + 4 SB boom, two
Do you use Dont Stop The Music / Lastmix?
If yes - just add another / remove any track on your own to the playlist
before you stop lms.
Adding tracks from dstm didnt didnt trigger "change the cached / stored
playlist".
Did you install LMS by yourself or use 3rd-party package like
piCorePlayer (pCP)?
Paul Webster
http://dabdig.blogspot.com
Author Radio France (FIP etc) plugin
Paul Webster's Profile:
Paul Webster wrote:
> Perhaps implies that the playlist is being stored in memory and being
> written to "disk" (much) later.
> Are you using pCP to host your LMS?
Thanks for your quick reply.
Oops, I dont know what pCP is :rolleyes:
My LMS is running on a Raspberry Pi on my local network
Perhaps implies that the playlist is being stored in memory and being
written to "disk" (much) later.
Are you using pCP to host your LMS?
Paul Webster
http://dabdig.blogspot.com
Author Radio France (FIP etc) plugin
Paul
Hi there,
I run LMS on a Raspberry Pi with two groups of players. Group1: 4 synced
players (1 SB receiver and 3 SB boom), Group2: 1 player (1 SB boom).
When I occasionally either reboot the server or restart the
squeezebox-server service, the active playlists on the players gets
reset to some
23 matches
Mail list logo