Re: [SlimDevices: SqueezeCenter] How can I create Playlists accessible by other programmes?

2016-01-30 Thread Mnyb
streifenleopard wrote: > Oh man that sounds like a lot of manual work. So we have 2016 and still > such a simple task is not accomplished... you can use notepad or similar and do a search and replace it takes a couple of seconds

Re: [SlimDevices: SqueezeCenter] Random mix not working in LMS 7.8?

2016-01-30 Thread JJZolx
This sounds like an age-old problem/misconception. You _will_ sometimes get songs from the same album played back-to-back in a random mix. Even if you're playing songs from your whole music library it can happen. The fewer songs (narrower the criteria) for the mix, the greater the chance that it

Re: [SlimDevices: SqueezeCenter] Random mix not working in LMS 7.8?

2016-01-30 Thread JJZolx
Look in the web interface at My Music > Random Mix. There's a setting for the genres that are included in the mix. That may be the problem. JJZolx's Profile: http://forums.slimdevices.com/member.php?userid=10 View this

Re: [SlimDevices: SqueezeCenter] Random mix not working in LMS 7.8?

2016-01-30 Thread JohnQCitizen
I found the culprit: one of the genre tags was selected, and only songs from that one album were in that genre. Not sure how that happened. I cleared that genre selection, and now when I select "random tracks", I get the expected behaviour. Delete thread if necessary ... user error rather than

Re: [SlimDevices: SqueezeCenter] Random mix not working in LMS 7.8?

2016-01-30 Thread JohnQCitizen
JJZolx wrote: > This sounds like an age-old problem/misconception. You _will_ sometimes > get songs from the same album played back-to-back in a random mix. Even > if you're playing songs from your whole music library it can happen. The > fewer songs (narrower the criteria) for the mix, the

Re: [SlimDevices: SqueezeCenter] LMS 7.9 Segmentation Fault

2016-01-30 Thread humanshield
I re-posted this over in the beta forum at http://forums.slimdevices.com/showthread.php?105122-Segmentation-Fault-Nightly-Build=844520#post844520 so this can be deleted, but I do not seem to be able to handle that