AUTOMIX transition style (automatic) is faulty with Hardware connected.

NOTE: Please use the search function above before posting to avoid creating duplicate topics.

  • Device model 2019 MBP, i7, 16gb RAM:
  • Version of operating system (Macos sequoia):
  • Version of djay v5.2.8:
  • Hardware/controllers used Hercules T7:

Summary of the issue:
I have noticed an issue: My automix transition style and duration are both set to “automatic” but, when I have any of my controllers connected, the automix is stuck on just one transition style (i think is either fader or dissolve) and it doesn’t cycle thru the many nice options (it is as if djay loses its AI capability once controller is connected). The duration too is fixed (i think to 2 bars). This makes the automix transitions very monotonous and boring within minutes. Without a controller, the automix is fine and flawless! Crossfader FX is OFF

How to reproduce the issue:
Connect controller, set automix transition style/duration to “Automatic” and listen to the mix for a few dozen songs> Note the monotony of transition and compare to same automix with laptop only (no controller connected)

Hi @Armigo, thanks for the details about your setup and the issue. Please check to make sure you have Crossfader FX turned Off.

Yes, it’s OFF, and was off too when i first noted the issue. To add more details: it is as if the automix function does not have a lot of choices, so it tends to repeatedly use the same transition style when set to “automatic” - so much so that the listener starts to note the monotony. Even if by some luck it picks a new one, the repetition of that style starts again.
I am pretty sure this si not the behaviour when running laptop alone (without any tweaks)…but I am continuing to give it a much more listening hours and keep comparing

Okay thanks for confirming @Armigo. We will do some testing to see if we can replicate it.

Hi again @Armigo, engineering tested with your same setup and Automix on Automatic setting with theT7 connected is working as expected. Can you please try updating to 5.2.9 to see if that solves the issue? Thanks!