FYI, there is a new maintenance release of foobar2000 out - version 0.9.6.8.Changelog:Fixed weird behaviors of the “stop after current” option.
With activated option "Stop After Current" foobar 0.9.6.8 exactly does what the option's name says.With earlier versions of foobar2000 with Columns UI the cursor does NOT move to the next track in the playlist but remains on the file of which playing has been finished.
Is there a possibility to return to that former behavior with Columns UI?
The behavior of this feature was changed in 0.9.6 (IIRC) to really stop after current, not on current or something like that.
I assume that's what you are referring to here, hence I renamed this thread. And moved the other posts from the other one here, please don't do that, we read everything.
Till foobar 0.9.6.7 I have heard them and then performed file operations on every single file I just have listened to, because foobar stopped ON current.
The situation now is that for each file I must scroll one position upwards.
So is there any possibility to avoid this self-acting jump to the next file? If not this would stand for some ten thousands clicks more I have to do.
"Stop on Current" component doesn't work with Random playback order. It is a hack that lets playback advance to the next track but immediately calls foobar to jump to Previous track. Also you must disable "Stop After Current" when using it.
New version here. This one uses a timer callback that is called every second so it will actually stop a bit earlier than the track really ends.
You seem to be the first one to provide real usage scenario for which the "broken" behavior was better.
Simplified the system and made it work with those very short files too. Download here.
New version utilizes foobar's built-in playback queue functionality to do its thing. When queue contains items that menu is visible. Try not to pay attention to it - it's nothing dangerous.