Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: "Stop after current" + "Next" (Read 14809 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

"Stop after current" + "Next"

Reply #25 –
Small and efficient, just the way I like it
Thanks again

Moderation: Removed unnecessary full-quote of the preceding post.

"Stop after current" + "Next"

Reply #26 –
Very bad realisation!

I want stop current song then select next song and that is all.
But  foobar play next song minimum 1 sec after end of previous is  reached.
I must put this plugin to trash.

"Stop after current" + "Next"

Reply #27 –
thanks!
I would like a more descriptive name like foo_stoponnext but its working as I wanted

edit: ok, I don't like that it starts the next track before stopping (I get a popup for the next track). It would be better if it would stop and then change the coursor to the next track or something like that.

"Stop after current" + "Next"

Reply #28 –
Quote from: pIv on
Very bad realisation!
It is the only one possible.
Quote from: pIv on
I want stop current song then select next song and that is all.
But  foobar play next song minimum 1 sec after end of previous is  reached.
There is no function like "select the next track", if you take the possibilities like different playlists, orders and display modes into account. I can only get notified when the next track starts playing and stop it. But when this happens, some samples are already on their way to the soundcard, which is good and expected.
I knew that this can't be done 100% right even before I started. However, the delays were either inaudible or just a split second when I tried it. Maybe because my DSP pipeline isn't half a mile long.
Quote from: pIv on
I must put this plugin to trash.
That drives me to tears, really. I hope you'll find a better realisation soon.
Full-quoting makes you scroll past the same junk over and over.

"Stop after current" + "Next"

Reply #29 –
This is a great example of what happens when you implement something for people who are already being exceptionally picky about the implementation of an existing feature.

Probably why Peter doesn't come around more often.
elevatorladylevitateme
 

"Stop after current" + "Next"

Reply #30 –
Quote from: shakey_snake on
This is a great example of what happens when you implement something for people who are already being exceptionally picky about the implementation of an existing feature.

Probably why Peter doesn't come around more often.


It's a shame that pIv has been outrageous in reacting to Yirkha, who was kind enough to try and address the problem with his component (in a way that is totally satisfactory to me, BTW). However, the reaction of a single person shouldn't be a basis for a gross generality.

As I said before, I have the experience of working on providing free software on the web, and I have dealt with kind and not so kind people along the way. However, feedback from all users has to be taken in account if you want to adapt your software to their needs. Having one single problem with a software doesn't count as "exceptionnally picky" to me. After all, the "reset stop after current after stopping" option has made it into foobar core, and it's about as big an option as what we asked for. Without it, you only have to reset the option yourself each time you use it.