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: How does queue really work (and what component best fits my definition (Read 1496 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

How does queue really work (and what component best fits my definition

I lent a friend my external hard drive and didn't get it back for a while. During that time I used GoneMAD Music Player on my tablet and phone. I never really thought about queuing until then! I just started using foobar once I got my HD back and even after reading multiple of threads, I still don't really understand how queue works in foobar.

Can anyone explain (in simple terms) what it is to me? What does "add to playback queue" really do?

Also, I've gotten used to certain "queue" functions that I'm not quite sure exists for foobar (in components and out of the box). So, what component best matches what I'm looking for?

- When in shuffle mode, the "queue" rearranges to the order that it will play in (this is my main priority, I use shuffle 99% of the time)
- Adding a song to the queue at the front does not change the queue after playing that song (basically, GMMP's "play next" and Spotify's "add to queue")
- Shows what's going to play next, no matter what (changes when clicking a song in search, changing playlists, clicking on an artist/album, etc.)
- If it's playing from one playlist, removing a song from the queue does not remove it from the playlist (useful when I'm in shuffle mode and think "nah I don't want to listen to that right now")
- Can rearrange the queue manually

Thanks in advance!

P.S. Replies from me will be slow because I'm currently in finals week and just typing this up before I start my day-long  cramming session.

How does queue really work (and what component best fits my definition

Reply #1 –
My understanding is that it simply marks the selected files as next in line after your current song finishes. The queued tracks will always play in order, ignoring the rules of your currently selected playback mode (such as shuffle). Once all of them have been played (the queue is drained), playback resumes as normal (such as - according to your previously selected rule - shuffling tracks). Think of it as a way of saying 'make sure to go through these for me, then you can play as usual'.

The queue is a hidden playlist that is normally not surfaced to the user. There have been some components that could make it visible but I don't know how well they worked. It is also always a manually composed list (it does not show your next song, unless you manually queue something up, and once that is drained, it shows nothing). Adding tracks to the playback queue does not alter your regular playlist in any way either, unlike the enqueue option in windows explorer, which would add the files to the end of your regular playlist.

How does queue really work (and what component best fits my definition

Reply #2 –
I always like to think of it as a manually selected virtual playlist that gets priority over your other playlists/play mode until all queued tracks are played. I use foo_queuecontents to view and edit my queued tracks.

How does queue really work (and what component best fits my definition

Reply #3 –
This has been covered before.

What The Q?

Won't win an award for gentlemanly conduct but it covers the bases.

How does queue really work (and what component best fits my definition

Reply #4 –
Quote from: RonaldDumsfeld on
This has been covered before.

What The Q?

Won't win an award for gentlemanly conduct but it covers the bases.


I've read the thread before. I kinda got intimidated by the debate. Re-reading it, I think I understand it now. I guess that answers my first two questions!

So I take it that no component exists for what I'm exactly looking for? I'm trying to use foo_queuecontents as of a couple of minutes ago. I guess I'll have to get into the habit of queuing my playlists instead of just double clicking on them.

Thanks to everyone who posted in the thread!
 

How does queue really work (and what component best fits my definition

Reply #5 –
Quote from: Daeron on
It is also always a manually composed list (it does not show your next song, unless you manually queue something up, and once that is drained, it shows nothing).


Sorry for bringing up an old thread but I spoke too soon. I didn't like using foo_queuecontents.

Is there any component that will always show the next songs, even if it's not manually queued and to have it work alongside the manual queue? Is it possible to create such a component?