Single song selection from Search keeps unrelated search results in queue

App version

Beta

Issue description

When using Smart Queue and Smart Flow with Jellyfin + AudioMuse, selecting a song from Search results behaves differently than selecting the same song from other areas of the library.

Settings:

  • Smart Queue enabled globally
  • Smart Flow enabled globally
  • Default song click action: Play no automatic queue
  • Personal Mix Size: 100

When selecting a song from Favorites, albums, artists, playlists, or other library views, Symfonium behaves as expected:

  • The selected song becomes the seed track.
  • Smart Flow generates Sonic Analysis recommendations from that song.
  • Recommended songs are inserted after the selected song.

The issue occurs only when selecting a song from Search results containing multiple matches.

When selecting a song from Search:

  • The selected song correctly becomes the playing track.
  • Smart Flow/Sonic Analysis also works correctly and inserts recommended songs after the selected track.
  • However, Symfonium also keeps the Search results as queue items before and after the selected song.

Example:
Searching “sweet” and selecting “Sweet Home Alabama” results in:

  • Search results before the selected song
  • Sweet Home Alabama (selected seed)
  • 5 Smart Flow/Sonic Analysis recommendations
  • Remaining Search results

The Search results appear to be treated as a playlist/context instead of being discarded when “Play no automatic queue” is selected.

This appears separate from the Smart Flow recommendation count itself. The AudioMuse integration is working because similar track requests are being made and recommendations are generated correctly.

Device type

Phone

Media provider

Jellyfin

Steps to reproduce

  1. Enable Smart Queue globally.
  2. Enable Smart Flow globally.
  3. Set Default song click action to “Play no automatic queue”.
  4. Connect Symfonium to Jellyfin with AudioMuse/Sonic Analysis enabled.
  5. Open Search.
  6. Search for a term with many results (example: “sweet”).
  7. Select “Sweet Home Alabama” by Lynyrd Skynyrd.
  8. Open the queue.

Expected:

  • Only the selected song should start playback.
  • Smart Flow should generate recommendations from that song.

Actual:

  • The selected song starts correctly.
  • Smart Flow generates Sonic Analysis recommendations correctly.
  • Search results are retained in the queue around the selected song.

Additional testing:

  • Selecting the same song from Favorites, albums, artists, playlists, or other library views works correctly.
  • Searching until only one result remains also works correctly.
  • The issue only occurs when selecting from a Search result list with multiple matches.

Additional information

Symfonium beta version includes the new global Smart Queue and Smart Flow settings.
AudioMuse integration is functioning correctly. When Smart Flow is triggered, AudioMuse receives the similar tracks request (/api/similar_tracks) and returns Sonic Analysis recommendations.
The Sonic Analysis/Smart Flow tracks are identifiable and appear correctly after the selected seed track.
The issue is only with Search result playback retaining the search result list as queue context.
This does not happen when selecting songs from Favorites, albums, artists, playlists, or other library views.
If the Search is narrowed down to a single exact result, playback behaves correctly because there are no additional search results to preserve.
The current behavior makes broad Search impractical for Smart Flow because selecting one song unintentionally keeps unrelated search matches in the queue.

Screenshots

I searched existing issues first

on

I understand that logs are mandatory

on

Log upload name / description

Cr33pin84

Just to confirm, are you aware that Search page does not use the main “Default track action” setting?

The main one for other library views is under Interface → Navigation and media start. Sounds you like have this one set already.

But the Search-specific default action is listed under Interface → Search page. Please confirm that this option is also set to “Play (No automatic queue)”. If not, set it here as well and your problem should be resolved. :crossed_fingers:

That was exactly it. I completely overlooked the separate Search page setting and assumed the main “Default track action” applied everywhere. Once I changed the Search page action to **Play (No automatic queue)**, it behaved exactly as expected.

Thanks for catching that and pointing me to the correct setting—I appreciate the help!