Forums

Full Version: Playlists
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
I have several play lists with no checks in the selection boxes. Presently .93b starts playing the next selection on the list anyway. I would prefer that the next selection was not automatically played.
That's pretty odd, but I have been able to duplicate it, I think. Just to be clear, are you saying that if you create an AudioCodex playlist, add some tracks to it, and uncheck all tracks, then when you play one of those tracks it plays them all, despite them being unchecked?

Thanks,
Hi Cal,

I wasn't aware of this error, thanks for pointing it out; the scenario of all tracks disabled in a playlist wasn't something I had allowed for in the code that selects the next track when not in loop-single mode. I have fixed this today so it behaves the way you suggest, so this will be available in the next release, which will be online sometime in the coming week.

Cheers,

Mark Hill
MachineCodex Software.

alex Wrote:
That's pretty odd, but I have been able to duplicate it, I think. Just to be clear, are you saying that if you create an AudioCodex playlist, add some tracks to it, and uncheck all tracks, then when you play one of those tracks it plays them all, despite them being unchecked?

Thanks,


Cal says -- That is correct. When it gets to the of the current track, instead of stopping and waiting, the next track starts to play even though the box is not checked. It also does this in the Library where I also keep every track unchecked.

Cal is right; I have confirmed that the error manifests if all the playlist items are unchecked.

THe reason it happens in 0.93b is that in normal (loop-playlist) mode, at the end of the currently playing track, the app was programmed to look for the next enabled track in the current playlist, and to continue checking through the playlist by up to the total number of items in the playlist before giving up. At that point, the checker (wrongly) returns the current track in its buffer, which will always end up being the next track in the list, as the checking algorithm loops over the last track and starts again from the first track, and expires once it reaches what will mathematically always be the track following the track that just finished.

I modified the code so that if no enabled items are found, no track is returned, so the player will no longer auto-advance if all playlist items are disabled, giving you an effective 'play-once' functionality.

This is now implemented in the current build, and will be available in the forthcoming 0.94b release.

Cheers,

Mark Hill
MachineCodex Software.
Hi all,

Just a quick note to let you all know we have fixed this issue in version 0.94b; in 'play list' mode, if all tracks in a playlist are disabled, when a track is started manually, the track will play once, and then playback will stop.

Cheers,

Mark Hill
MachineCodex Software

mantis Wrote:
Hi all,

Just a quick note to let you all know we have fixed this issue in version 0.94b; in 'play list' mode, if all tracks in a playlist are disabled, when a track is started manually, the track will play once, and then playback will stop.

Cheers,

Mark Hill
MachineCodex Software


Thank you very much. This was one of my critical fixes that I needed in my enviroment. I appreciate you making this fix.

Reference URL's