MPD is there an option: BACK

[ski007]

Sorry if I didn't read it clearly, but is there a "back" option in the MPD/MPC program? I don't mean "next/prev" because that only works sequentially. What if I wanted to select, for example, number 7 ( mpc play 7 )...then, for example, (mpc play 102), and with one click return to "7" again, meaning the "back" option? Is there such an option in MPD/MPC?

[MaxKellermann]

No.

[ski007]

Thanks for the info! I think that if this option isn't in mpd/mpc to this day, it's probably difficult to add and maybe unnecessary for most users.
Ps. I managed to create a few scripts using Gemini that do this correctly for both MP3 music from USB and radio stations... but it was a real struggle and took me a few hours. I'm not a programmer. I mostly use the remote control and the program: triggerchappy / Armbian system / bananapim2pro / mpd v0.24.12.

Regards

[YennisFM]

No, MPD/MPC does not have a browser-style “Back” function. mpc prev only moves to the previous position in the current queue.

On our music server, we solved this by adding a separate history layer around MPD. MPD still handles playback, but our application records every played track using its actual file path and a normalized artist/title identity. Because of that, we are not limited to moving sequentially through the queue.

For example, after playing queue item 7 and then item 102, we can select the earlier track from the history and play it again directly. It is better to store the MPD file URI or path instead of only the queue number, because queue positions can change when tracks are inserted, removed or automatically refilled.

The same principle can also work for radio stations by storing the station URL or playlist entry.

So the architecture is roughly:

• MPD handles playback.
• A separate script or application monitors track changes.
• Played tracks and radio stations are stored in a history database.
• A Back button or history list selects the required earlier item.
• The selected file or stream is sent back to MPD.

Nice work getting your scripts working, especially if you are not a programmer. For this kind of project, an AI coding tool such as Codex can also be useful. It can inspect the existing MPD, MPC, triggerhappy and remote-control setup, create the required scripts, connect them to buttons, and help test the complete workflow.

It is still important to make backups and test each step before replacing anything, but a feature like this can now be implemented much faster than before.

So it is not a standard MPD feature, but it can be added quite reliably as an external history layer.