We’ve just released dLive V2.02
Download it - https://www.allen-heath.com/hardware/dlive-series/all-models/resources/
Read about it - https://www.allen-heath.com/content/uploads/2024/10/dLive-Release-Notes-V2.02.pdf
We’ve just released dLive V2.02
Download it - https://www.allen-heath.com/hardware/dlive-series/all-models/resources/
Read about it - https://www.allen-heath.com/content/uploads/2024/10/dLive-Release-Notes-V2.02.pdf
Have you updated the MixPad app to include FX control and assignment?
Great work!
Right clicking on soft rotaries and entering values in Director is still broken here. Not listed under “known issues” either.
I had no trouble right clicking in Director and entering a specific value. You need to right click on the numerical value listed below the rotary however, not the actual rotary knob itself. Perhaps this is the disconnect you are experiencing.
Right-clicking the values is working on three different devices here. I use Windows.
The problem is with aux/FX sends. Both on win and Mac. It’s acknowledged by A&H, but not in the “known issues” list.
Proof video…
Ok, I can confirm it, after I watched your video.
Hope it gets fixed in the next update.
Not a showstopper to me.
Hi,
We experienced fader problems with the new firmware. During Scene Changes with crossfade time - the fader stuck. We can’t change to the previous firmware-version, because it is not available in the download area…
Please, can you fix that?
Cheers
Johannes
Have you tried recalibrating faders since the update? I’m not sure where the fader calibration is stored, but it is conceivable that an update might change the stored values.
If you do want to roll back to a previous version, I am seeing options in the dropdown on the right of the download page for lots of previous versions, including 2.10 and 1.9A.
The V2.01 is now available. I will downgrade until A&H fixes the bugs.
Thanks!
Just FYI - 2.01 is a lot more buggy than 2.02! I suspect downgrading to 2.01 isn’t going to fix anything, and may actually cause more problems.
we ran 2.01 without any issues - upgrading coused problemes - in our usecases. But thanks for your reply!
The bug shown in my video above is still present in 2.03 and still not filed as “known issue”