(Bug) Reversed DJ Stretch genre transitions

[viraldark]

Server Version#: 1.41.5.9522
Player Version#: 4.11.5

The DJ Stretch feature exhibits a bug when inserting transitions between two adjacent tracks with vastly different profiles.

My understanding is that it is meant to provide a gradient to make such transitions less jarring. Certainly, this requires the library to contain suitable tracks but even when they do exist and the DJ selects them, I notice that it plays the inserted tracks in the reverse order.

For example, if transitioning from an an intense, guitar-heavy track to a low tempo track that’s closer to ambient, the DJ will play the inserted tracks in this sequence: lowest tempo closest to target, faster tempo with more guitar, fast tempo with most guitar. So you get to experience the jarring transitions twice.

The DJ tracks here were are actually very good selections but the order is reversed.

The player logs are attached.

Plexamp-Logs-2025-03-21-1.zip (2.0 MB)

This happens often but I don’t always notice as I may not be paying attention or the adjacent genres are close enough for this to not be noticeable.

Thanks.

[OttoKerner]

@viraldark

My understanding is that it is meant to provide a gradient to make such transitions less jarring.

No, that is not what a sonic adventure is.

[elan]

@OttoKerner

No, that is not what a sonic adventure is.

That’s what it is actually supposed to be

I think I see the issue, we’ll move to a slightly slower way of adding the tracks to the play queue which should more accurately preserve order!

[viraldark]

Thanks, much appreciated.

[elan]

I looked at this again, and it appears that it is functioning correctly, or at least I can’t reproduce an issue with it over here. The tracks show up in the play queue in the order intended.

I’ve added some more logging for the next release, so if you see it misbehaving again we can compare what order it thinks it added in with the order you see.

When doing a path in higher-dimensional space, it might not always seem rational to our brains, which are looking more for specific things like “loudness” vs “calmness”.

[viraldark]

Thanks, will keep an eye on it.

Most of my listening is via the iOS app. Do you have an ETA for the release, with the additional logging, on this platform?

[elan]

In the coming weeks.

[Tangs]

I have the same issue it should also be revert :

1308453407566901.zip (179.9 KB)

I noticed it the 27th march, around 16h20

[elan]

This is what I see added:

library%2Fmetadata%2F360686%2C340192%2C497477

This corresponds to the order:

• /library/metadata/360686
• /library/metadata/340192
• /library/metadata/497477

Do you know how to verify in your library which these are?

[Tangs]

I don’t know how, but if you explain it to me i’ll look for it

[elan]

Go to the web app, to go any track and click … Get Info and then View XML. You’ll see the URL in the browser contains … /library/metadata/XXXXX where XXXX is a number. Replace that with the numbers above to look up the tracks in your database.

[pockems]

Wanted to tag on another example of this - it seems like the Diana Ross and Dinah Washington tracks should be adjacent (both being jazzy/soul songs) and the Modern Lovers with the Beatles track (which sound remarkably similar). This also has been happening to me fairly frequently over this and last year.