500 Song Limit in 7.5?

[iPhone]

OK. Using a number for Maximum Playlist Length doesn't work, and following the info popup and using a zero doesn't work. But, a blank space does. Of course, it is intuitively obvious!

I wonder if any other character might work the same way? Might have to play with this when I have more time.

But, thanks folks for the help. Very much appreciated.

z88

Just to make sure something weird isn't going on, did you try a more realistic number like 2500 or 4000? Or are you saying no number worked? I haven't had an issue with any number under 10000.

[awy]

I really cannot see how ' ' (space) or '0' would make a difference as the preference value. All the code that uses this just tests it as a boolean (first) and ' ', '0', 0 and undef are all false in perl.

In my own tests, and those of a colleague, 0 always works as expected.

It may be that a (playlist) rescan is needed after changing the preference value.

[Phil Leigh]

I've just retested this on 7.6 XP using the default skin and the preference setting works perfectly and exactly as it should.

[MrC]

... and ' ', '0', 0 and undef are all false in perl.

As a minor correction, the non-empty string *' '* is considered TRUE:

$ cat booltest.pl

printf "Boolean truth?  *$_* : %s\n", ($_ ? 'TRUE' : 'FALSE') foreach (0, '0', '', undef, ' ');

$ perl booltest.pl
Boolean truth?  *0* : FALSE
Boolean truth?  *0* : FALSE
Boolean truth?  ** : FALSE
Boolean truth?  ** : FALSE
Boolean truth?  * * : TRUE

[awy]

Yes, of course. Thanks. Hangs head in shame.

[bruce]

This seems like an unnecessary way to drive less-than-expert users crazy. How many users go to the Advanced/Performance menu?

If someone has a 1000 song playlist, why assume they don't want it? If the performance hit is really big, then at least warn the user somehow the first time they try to scan a larger playlist. But I have a hard time believing the restriction is necessary.

[usch]

I had an unpleasant experience the other day when the server decided to add every single non-album track in my library to the current playlist (is it really expected behavior that "Play Other Songs In Album" applies to "No Album", too?) and was quite happy when it stopped at 500.

[paf]

I have this problem with my SB Radio with SBS 7.5.0 running on a Synology NAS.

Setting the limit on SBS to more than approx. 750 (or 0 or empty) causes a non-playable playlist on the radio (can list the song, but play does not work).

I don't think that saved playlists are limited to 500 items, just that no more than 500 items will be added to the current playlist at a time. I think the limit was put in place as a performance consideration for the people who inevitably try to add every track in their library to the playlist and then don't understand why the server appears to freeze for 10 minutes.

Unfortunately, I don't think that the above is true.

I tried with a limit of 10. Each time I select the playlist, it contains the same 10 songs. If at least the radio would select each time 10 songs randomly, it would not be so bad.

This limitation is really TERRIBLE!!! The cheapest iPods work better.

I'm so disappointed about the bugs, the limitations, the bad ergonomy and the inexistent documentation of SB Radio and SBS!!!

[JJZolx]

Unfortunately, I don't think that the above is true.

I tried with a limit of 10. Each time I select the playlist, it contains the same 10 songs. If at least the radio would select each time 10 songs randomly, it would not be so bad.

Isn't that exactly what you would expect? A playlist is an ordered list, so if limiting it to X songs then you'd expect it to play the first X songs every time.

What I'm saying is easy to test. Change the limit to 20 and then _without_ rescanning, do you get 20 songs or 10? If the limit was imposed when the playlist is scanned, then you'd get 10. I think you should see 20, which means that the entire playlist was probably scanned into the database, but it's being limited only when you attempt to play it.

[paf]

Isn't that exactly what you would expect? A playlist is an ordered list, so if limiting it to X songs then you'd expect it to play the first X songs every time.

What I'm saying is easy to test. Change the limit to 20 and then _without_ rescanning, do you get 20 songs or 10? If the limit was imposed when the playlist is scanned, then you'd get 10. I think you should see 20, which means that the entire playlist was probably scanned into the database, but it's being limited only when you attempt to play it.

...so what's the purpose of scanning the entire playlist into the database if the playing device takes every time the SAME first 500 songs?

The system could at least give the option that each time another 500 songs are chosen when extracting the playlist from the database!