Fixed in RC-2--the Export Playlist function now supports tracks on the virtual CD.

Anonymous wrote:First I'm starting to wonder, playlist can contain songs from VirtualCD, can't they?

Playlists can contain tracks from the virtual CD, but exported .m3u playlists can't at the moment. We're trying to fix this prior to release.

-Rusty

First I'm starting to wonder, playlist can contain songs from VirtualCD, can't they?

I tried a lot of things:
From MS Access, I edit SongsDB.mdb and in the Medias table filled the column TurnedSN with '1' instead of '0'.
I changed the VirtualCD directory because I had a quote in the directory name.
I've reinstalled songs-db beta version 1.4 (Build: 1.540) over beta version 1.4 (Build: 1.519).
I've reinstalled songs-db beta version 1.4 (Build: 1.540) from scratch
on the same PC running Windows XP,
on another PC running Windows ME.

The effect was always the same, whatever node I used.
I saved to virtual CD a few songs
The only way to see something more than
#EXTM3U
in the playlist was to keep the CD in the CD-rom.
I only used accessible tracks in my playlists.
I was able to play all songs without the CD in the CD-rom, so the reference to the VirtualCD file must be correct.

Some more detailed information about updating Medias.TurnedSN:

After executing the following SQL-statement
UPDATE Medias SET Medias.TurnedSN = 1;
I got this error when starting Songs-DB:
Songs-DB
Invalid parameter. (C:\Projects\Common\VirtualTrees.pas, line 24209)
I couldn't do anything at all.
When trying to close Songs-DB, I got this error:
Access violation at address 00660FB7 inmodule 'Songs-DB.exe'. Read of address 00000000.

After executing the following SQL-statement
UPDATE Medias SET Medias.TurnedSN = 1
WHERE (((Medias.IsAudioCD)=1));
I could open Songs-DB, but when I closed it right away without doing anything in Songs-DB, I saw in Access that Medias.TurnedSN was always back to 0.

I think that this problem is caused by the fact that some of the tracks you try to export are not accessible (they probably appear in grey instead of black and cannot be played without their media inserted). Such tracks are not exported because their drive letter isn't known and thus their full path cannot be properly written to the exported file. Is this the case?

Jiri

I'm running Windows XP and I updated the Medias table as described in the above topic, which didn't change anything, I think.

Not all playlists fail.
It works fine from the node Artist, but it fails from the node Playlists.
For some Playlists there is more than the first line, but never all the songs I selected.

There was a problem introduced in Beta 3 for users upgrading SDB 1.3 and using Windows 95/98/ME, which resulted in faulty links between the database and actual tracks stored on HD/CD media (more info appears in the Beta 4 announcement which also describes how to fix this: http://www.songs-db.com/forum/viewtopic.php?t=411 ). Are you experiencing this problem?

If not, can you also tell me:
-Do all playlists fail to export? If no, what are the characteristics of the playlists that do fail to export?
-Does the failure to export occur when you're trying to export tracks from a particular node?

thx.

I've installed songs-db beta version 1.4 (Build: 1.519) over beta version 1.4 (Build: 1.506), which was in turn installed over songs-db 1.3.
(I thought it may matter as I've read something similar in the Accessible Songs to Playlists:Accessible Tracks topic).

When I choose Export to Playlist..., the exported file only contains
#EXTM3U