New in 7.9: "Don't Stop The Music"

[mechaMecha]

>I'd still say you have to figure out "who" (which plugin) is adding the
tracks using which command. Then we can look into why that command would
only see null instead of actual track information. Look at the browser's
dev tools to see what command Material is sending to the server. Enable
logging for control.command (which will be super noisy, but helpful).

OK. I'll try to do this later today. Thanks.

[mechaMecha]

Have you looked at the entries in the playlist's m3u file? Perhaps the URL saved there for a track added via DSTM is different to a manually added track? As stated, all Material does is add the track's URL to playlists.

I'll take a look later today. Thanks.

[mherger]

New in 7.9: "Don't Stop The Music"

> It absolutely does. I don't have a Spotify account, but I enabled the
> plugin thinking I might try Spotify at some point. So "Spotify
> Recommendations" appears as an option for DSTM. When I select it, it
> adds local tracks.

Most likely because DSTM would fall back to random tracks, as Spotty
wouldn't return any recommendations if it's not configured correctly.

[mechaMecha]

Most likely because DSTM would fall back to random tracks, as Spotty
wouldn't return any recommendations if it's not configured correctly.

Makes sense. All I know is that, when I select Spotify Recommendations, it adds local tracks, which is what I mentioned earlier.

[slartibartfast]

Have you looked at the entries in the playlist's m3u file? Perhaps the URL saved there for a track added via DSTM is different to a manually added track? As stated, all Material does is add the track's URL to playlists.

My Tidal track which displays correctly shows as
#EXTURL: wimp://11945009.flac
wimp://11945009
I did notice that tracks added to playlist do not appear in the m3u file unless you manually save the playlist.

Sent from my Pixel 3a using Tapatalk

[RobbH]

Have you looked at the entries in the playlist's m3u file? Perhaps the URL saved there for a track added via DSTM is different to a manually added track? As stated, all Material does is add the track's URL to playlists.

Here's mine. A Qobuz track added to the queue by DSTM from a random mix that only uses online files, then saved to an existing playlist:

#EXTURL:qobuz://18086827.flac
qobuz://18086827.flac

Could the issue be that LastMix/Last.fm uses some other format for the url of online tracks?

[mechaMecha]

Have you looked at the entries in the playlist's m3u file? Perhaps the URL saved there for a track added via DSTM is different to a manually added track? As stated, all Material does is add the track's URL to playlists.

Just took a look at my current play queue's m3u file.

Local track added manually:

#EXTURL:file:///C:/Users/Public/Music/Fine%20Young%20Cannibals/Fine%20Young%20Cannibals/Move%20To%20Work%20-%20Fine%20Young%20Cannibals%20-%20Fine%20Young%20Cannibals.m4a
#EXTINF:207,Move To Work
C:\Users\Public\Music\Fine Young Cannibals\Fine Young Cannibals\Move To Work - Fine Young Cannibals - Fine Young Cannibals.m4a

Streamed track added manually:

#EXTURL:qobuz://13112529.flac
#EXTINF:-1,To Our Knees by Low from The Invisible Way (Édition StudioMasters)
qobuz://13112529.flac

Local track added by DSTM:

#EXTURL:file:///C:/Users/Public/Music/Tori%20Amos/From%20The%20Choirgirl%20Hotel/She%27s%20Your%20Cocaine%20-%20Tori%20Amos%20-%20From%20The%20Choirgirl%20Hotel.m4a
#EXTINF:222,She's Your Cocaine
C:\Users\Public\Music\Tori Amos\From The Choirgirl Hotel\She's Your Cocaine - Tori Amos - From The Choirgirl Hotel.m4a

Several streamed tracks added by DSTM:

#EXTURL:qobuz://44536217.flac
qobuz://44536217.flac
#EXTURL:qobuz://44536211.flac
qobuz://44536211.flac
#EXTURL:qobuz://3493217.flac
qobuz://3493217.flac

Streamed tracks queued via Don't Stop The Music are missing #EXTINF data.

[mechaMecha]

Could the issue be that LastMix/Last.fm uses some other format for the url of online tracks?

I don't think that's the problem, because when I use other options for DSTM (not LastMix/Last.fm), the same null/unknown issue still happens with streamed tracks that have been integrated into my music library from Tidal and Qobuz. No matter which option I choose, any streamed track added to the queue by DSTM results in a null/unknown entry when I try to save it to a playlist.

[slartibartfast]

Just took a look at my current play queue's m3u file.

Local track added manually:

#EXTURL:file:///C:/Users/Public/Music/Fine%20Young%20Cannibals/Fine%20Young%20Cannibals/Move%20To%20Work%20-%20Fine%20Young%20Cannibals%20-%20Fine%20Young%20Cannibals.m4a
#EXTINF:207,Move To Work
C:\Users\Public\Music\Fine Young Cannibals\Fine Young Cannibals\Move To Work - Fine Young Cannibals - Fine Young Cannibals.m4a

Streamed track added manually:

#EXTURL:qobuz://13112529.flac
#EXTINF:-1,To Our Knees by Low from The Invisible Way (Édition StudioMasters)
qobuz://13112529.flac

Local track added by DSTM:

#EXTURL:file:///C:/Users/Public/Music/Tori%20Amos/From%20The%20Choirgirl%20Hotel/She%27s%20Your%20Cocaine%20-%20Tori%20Amos%20-%20From%20The%20Choirgirl%20Hotel.m4a
#EXTINF:222,She's Your Cocaine
C:\Users\Public\Music\Tori Amos\From The Choirgirl Hotel\She's Your Cocaine - Tori Amos - From The Choirgirl Hotel.m4a

Several streamed tracks added by DSTM:

#EXTURL:qobuz://44536217.flac
qobuz://44536217.flac
#EXTURL:qobuz://44536211.flac
qobuz://44536211.flac
#EXTURL:qobuz://3493217.flac
qobuz://3493217.flac

Streamed tracks queued via Don't Stop The Music are missing #EXTINF data.

Mine don't have #EXTINF either but still display track data. You were looking at the play queue m3u file, what do you see in the playlist m3u file that you added the track to?

Sent from my Pixel 3a using Tapatalk

[mechaMecha]

Mine don't have #EXTINF either but still display track data. You were looking at the play queue m3u file, what do you see in the playlist m3u file that you added the track to?

Same thing. All tracks have #EXTINF data except for the streamed tracks that DSTM added to my play queue.

[slartibartfast]

Same thing. All tracks have #EXTINF data except for the streamed tracks that DSTM added to my play queue.

Yup you are right my playlist m3u file also contains #EXTINF data for local tracks but not for online tracks. Even so, my online tracks in the playlist do show track information and cover art so something else is causing the issue.

Sent from my Pixel 3a using Tapatalk

[mherger]

New in 7.9: "Don't Stop The Music"

> I don't think that's the problem, because when I use other options for
> DSTM (*not* LastMix/Last.fm), the same null/unknown issue still happens
> with streamed tracks that have been integrated into my music library
> from Tidal and Qobuz. No matter which option I choose, any streamed
> track added to the queue by DSTM results in a null/unknown entry when I
> try to save it to a playlist.

Have you figured out what command is being used to add those tracks to
the playlist? Because everything else is nice chatting, but doesn't
really get us closer to the actual problem...

[mechaMecha]

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. I re-enabled the Qobuz plugin, and now it's working! I'm now able to add DSTM-streamed songs that appear like they should. Even tracks that were previously appearing as "unknown" in the list now show track title and artist, although I often need to open the playlist twice, otherwise DTSM-added streamed tracks still show as "unknown." (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.)

So, I guess it took the old "turn it off and on again" trick to get it working...

Anyway, thanks for taking the time to help me out, slaritbartfast and cpd73. I greatly appreciate it!

[mherger]

New in 7.9: "Don't Stop The Music"

> (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 certainly does
not have to deal with this. All it does (no matter where a track is
coming from), is add a URL. This can be something like
file://home/music/some/track.mp3, or qobuz://123456.flac. It's just a URL.

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.

[cpd73]

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 playlist via:

["playlists", "edit", "playlist_id:<playlist id>", "cmd:add", "url:<track url>"]

Note no metadata is sent, simply the track's URL. I've looked at the LMS code (playlistsEditCommand in Slim/Control/Commands.pm) and can see that I could also pass 'title' - but, in my experience, this does not seem to be required. However, I fail to see why there would be a difference between a track added via DSTM or manually, both should have the same URL. Perhaps as its added manually LMS cache's the meta-data so knows what to write to the M3U file?

I could update my call to pass "title:XXXX" - but not sure what should be in the title. Just title? Artist? Album? If so what format? "Title - Artist, Album" ???

-----

The above is assuming you mean "stored playlist" by "playlist" and not the current play queue. (This is the reason I call the play queue "play queue" and not "play list" - to make the difference obvious).