cpd73 wrote:
> formats.playlists, player.playlist
If I remove the PlayHLS plugin then the playlist is saved but I see a
another couple of errors which probably aren't important.
+---+
|Filename: playlist1.log
cpd73 wrote:
> formats.playlists, player.playlist
OK, with those logs set to info I get the attached log. The PlayHLS
plugin seems to be interfering.
+---+
|Filename: playlist.log |
slartibartfast wrote:
> Hmm I checked the modification time of the m3u file and it wasn't
> updated until I saved it and overwrote it from the default skin. Which
> logging settings should I use?
formats.playlists, player.playlist
*Material debug:* 1. Launch via http:
slartibartfast wrote:
> When I add a Tidal track from the play queue to a playlist I see a
> message
> Added to 'playlistname'
> Also while it does add the track to the playlist in LMS it doesn't save
> the m3u file so when LMS is restarted the playlist reverts to the old
> saved playlist. In
cpd73 wrote:
> H LMS -should- save playlist on changes, and does for me. With
> appropriate logging enabled, when adding a track from the queue to a
> playlist I see:
>
> >
Code:
> >
> [22-04-10 19:00:54.3931] Slim::Player::Playlist::modifyPlaylistCallback
slartibartfast wrote:
> When I add a Tidal track from the play queue to a playlist I see a
> message
> Added to 'playlistname'
> Also while it does add the track to the playlist in LMS it doesn't save
> the m3u file so when LMS is restarted the playlist reverts to the old
> saved playlist. In
slartibartfast wrote:
> When I add a Tidal track from the play queue to a playlist I see a
> message
> Added to 'playlistname'
> Also while it does add the track to the playlist in LMS it doesn't save
> the m3u file so when LMS is restarted the playlist reverts to the old
> saved playlist. In
cpd73 wrote:
> Nope, can't find any "Adding <> to playlist" messages in Material... I,
> perhaps wrongly, assumed that after DSTM added a track to the queue,
> Material adding this track to a stored playlist, that a) in the stored
> playlist this track had no meta-data and b) when adding to the
mherger wrote:
> > As stated earlier, it is Material that is invoking JSONRPC to add a
> > track to a -stored- playlist via:
> >
> >["playlists", "edit", "playlist_id:", "cmd:add",
> "url:"]
>
> The original poster mentioned a message "adding null to playlist". I
> can't find this string
As stated earlier, it is Material that is invoking JSONRPC to add a
track to a -stored- playlist via:
["playlists", "edit", "playlist_id:", "cmd:add", "url:"]
The original poster mentioned a message "adding null to playlist". I
can't find this string in LMS. Are you showing this?
mherger wrote:
> The command adding that URL to a playlist then is responsible of
> grabbing the track information it wants to show. That's why I keep
> asking for the command used in this action.
Yeah, sorry, I just haven't had the time to dig into that, but I don't
understand how that gets
mherger wrote:
> The command adding that URL to a playlist then is responsible of
> grabbing the track information it wants to show. That's why I keep
> asking for the command used in this action.
As stated earlier, it is Material that is invoking JSONRPC to add a
track to a -stored-
(IMHO, I'm guessing that probably wouldn't happen at all if DSTM
included the #EXTINF data for streamed tracks, because that's the one
and only difference between those tracks and all the other tracks that
have always worked properly.)
#EXTINF is a playlist file format specific thing. DSTM
slartibartfast wrote:
> Could you try disabling Qobuz so Tidal is used instead?
Well, I finally decided to disable the Qobuz plugin, thinking I'd try to
make my system look as much like yours as possible. DSTM then added
tracks from Tidal, which I was able to add to a playlist without
problem.
14 matches
Mail list logo
