Playlist Generator Pro (1.1.0.0) (Not Responding)

[radiodungog]

Dmitry,

Our music library files are stored on a NAS connected with 1Gbps Ethernet.

We have our source music categorised and stored in playlist files like:

Bin_1950.m3u  ...  267 tracks
Bin_1960.m3u  ...  924 tracks
Bin_1970.m3u  ...  1,959 tracks
Bin_1980.m3u  ...  3,845 tracks
Bin_1990.m3u  ...  13,133 tracks
Bin_2000.m3u  ...  13,966 tracks
Bin_2010.m3u  ...  1,782 tracks
Bin_Gold.m3u  ...  978 tracks
Bin_Top40.m3u  ...  1,876 tracks
Bin_Sequence_Start.m3u  ...  1 track

I realise this is a lot of tracks in the source playlists - and those numbers will come down considerably when I complete the Top-40 tagging process.

When I run the Playlist Generator Pro I always get the above "Not Responding" message on the Log window.  It eventually completed the job but it is very slow to do it.


Any suggestions ?  Or just sit tight and wait for it to finish ?



Thanks,  Jamie C.

 

[djsoft]

When I run the Playlist Generator Pro I always get the above "Not Responding" message on the Log window.  It eventually completed the job but it is very slow to do it.

Any suggestions ?  Or just sit tight and wait for it to finish ?

Jamie,

Currently, yes, just wait till it completes the job. It's a known problem. PLGen needs to read the files in order to build the playlist, and as files reside on a network storage, this process can take considerable amount of time. It doesn't respond to system messages because it's busy building the playlist. In one of the next updates it will be changed and PlGen will show the progress with percentage. But the time needed to do the job will still remain the same (at least you'll see it's active and Windows won't mark it as non-responsive).

 

[radiodungog]

Dmitry,

Thanks for the answer.  That makes sense.

BTW, those files and playlists that I used above were all in FLAC.  As an experiment yesterday I changed the format over to MP3 versions of the music and I reduced the bins (playlists) to 500 songs in each.  As a result it worked much better - but still came up with "Not Responding".

The progress bar sounds like a good idea.  Feedback to the user is a big advantage.


Thanks,  Jamie C.