[bug][Foobar2000 v.1.3.14] ESplaylist: Strange messing with the playbackorder

2017-01-03 20:55:30

Hello,

yesterday I updated from v.1.3.13 to 1.3.14. I had no problems before with this component.

Description of the problem:
I have columns ui with ESPlaylist. I have set the playback order to default.
Now foobar plays the songs (1-9) in the following order:
Title:
1,2,6,9,4,3
When I push the button NEXT after 3 no song is played although 5,7,8 are missing.
The title names are named with tracknumber. title

I tried default ui, no problem.

Edit:
After switching to colums ui and trying other playlist components everything is working fine again.
I am not able to understand what the problem was.

Has someone had similar problems?

Re: [bug][Foobar2000 v.1.3.14] ESplaylist: Strange messing with the playbackorder

Reply #1 – 2017-01-03 21:00:55

Same set up and no such problem.

Re: [bug][Foobar2000 v.1.3.14] Strange playbackorder caused by Library tree

Reply #2 – 2017-01-07 20:25:59

Hello 
Now I have the same problem again. But after push the button next while playing title 1 the playback stops.
In Esplaylist the tracks are in the order from 1 to 9.

But when I switch my colums ui layout to columns playlist the tracks are sorted in a different way( so that title 1 is at the end of the playlist).

I tried to reproduce the bug but it is strange.

It seems that the library tree sends the tracks in a different order. With album list I have no problems. In Esplaylist the albums are shown sorted.

Does someone know if there is a way to change that?
I  haven't recognized a special scheme in the way the files are added to playlist.

Edit:
Using drag and drop from library tree -> messed up order
Using context menu in Library tree-> everything okay.

Has someone an idea what ths problem could be?

Re: [bug][Foobar2000 v.1.3.14] ESplaylist: Strange messing with the playbackorder

Reply #3 – 2017-01-07 20:51:03

Maybe it has to do with displaying the tracks in order, but they're not really in order in the playlist? Sorting them within their groups, so to speak.

Do the tracks still appear in order if you switch off grouping or if you display the same playlist in a different playlist control?

Re: [bug][Foobar2000 v.1.3.14] Library tree: Drag an Drop messes track order

Reply #4 – 2017-01-07 21:35:22

Setting grouping to none leads to show the order in which the titles will actually play (titles ore sorted in weird order via drag and drop).

The order in which the tracks are added seems to be different with every new start in Foobar2000: (when I remove the titles close foobar, start foobar and ad the tracks again)
first:
3,5,8,4,1,7,2,6,9
Then:
4,5,6,8,9,1,7,2,3,

Never seen such a behaviour like that 

If some has an idea what the problem could be that would be helpful.

Re: [bug][Foobar2000 v.1.3.14] ESplaylist: Strange messing with the playbackorder

Reply #5 – 2017-01-07 22:06:51

It's not a "problem" so much as a self-sorting behavior of the playlist control. They're getting added in a semi-random order by the drag operation, rather than being sorted first. The grouping pattern is set to sort them in track and disc number order, regardless of the actual playlist item order.

You'll have to select the whole group, then go to Edit -> Selection -> Sort and reorder them according to track and disc numbers. Or convince the author of the playlist to hard sort drag and drop target additions by the current grouping pattern, assuming it's still in development.

Re: [bug][Foobar2000 v.1.3.14] ESplaylist: Strange messing with the playbackorder

Reply #6 – 2017-01-07 22:20:41

Thanks for your help

I found the solution of the problem:
The drag and drop behaviour must be configured under each view. Click right on the view and choose edit view. In the opnening window there is "Sort tracks sent to playlist by" and there only stood "artist" now I edited "%artist%/%album%/[%discnumber%.].%tracknumber%"

Sorry. I really did not recognized there was an option.

I found it very strange that the order in which the tracks were adde were so different.

The topic can be closed.