I surely will test as soon as possible (I think I’ll wait for the official release after the RC).
I agree that it has to be seen on the field to be properly adjudicated. Maybe my worries are not justified.
On the other hand, it could be that the pedalboard/snapshot names are too small, too.
I’ve played in lots of dark stages and I know that a clear display is vital when you’re in a hurry to find the right patch for the next song. Often a large bright 7 segment led numeric display with just the number of the patch is much more straightforward than the full name.
Could indeed be useful but IMHO on stage the device should be usable without additional devices, expecially pedalboards and other stuff like that (thay are literally intended to be put on the floor). A tablet would additionally require a stand and not everybody would want it.
Noted. as expected we likely need to increase the graceful timeout period allowed on CC devices…
I am adding it to the backlog, will get to it very soon.
Good catch! This is an old issue we kinda forgot about, now brought back to the conversation again.
The issue happens because the CC devices initialize in parallel. Whoever happens to init first gets the id 1, then 2, etc.
We are discussing possible solutions for this.
I have seen this before as well, but it is not easy to reproduce. thanks for mentioning bypass.
Maybe it is a specific state of bypass and momentary mode that triggers this. Will try to get this fixed too.
Thanks for the heads up, I will investigate these plugins, since the issue is likely in them.
Do you know if you had them fully up to date when you were using them?
Yes, this was done only for the Duo pedalboard navigation.
Is this lagging or simply like “1 action behind”? Say, whatever last action you did is always delayed by another action.
If instead things are just lagging and slow to react to changes, well, two different issues.
Hi!
Thanks for your interest.
Concerning the bypass issue it’s easy for me to reproduce because it happend with every pedalboard, with 2 or 1 control chain connected. Another issue is that the led state of effect bypass is not sent to controlchain footswitch whrn loading a pedalboard or snapshot. I just realised too that for some effects the led status is not sent to the corresponding footswitch when switching bypass in the Web Editor. But if I use the controlchain footswitch the led light up correctly
The state of led footswitch 1 and 2 are swapping , same thing for 3 and 4. But only when using the Web Editor.
For the issue the Mod Duo controls (rotary and switch) that are lagging sometimes I mean it is not slow reaction but all action are delayed by another action. I did not understand immediatly what happened Iand I was first thinking it just a slow reaction but now that’s clear this is the issue.
Besides the visual hiccups RC1 worked well for me. I especially like the new layout on the device screens. If you depend on your Duo(X), I’d recommend waiting for the 1.10 stable release. Otherwise, just give it a go and if you do not like it, go back to the older version.
I still have no idea on how I will go about reproducing this…
You only have this behaviour on a specific browser on a specific system, right? or is it more widespread?
Well, it used to work fine with the Mozilla-Browser so something definitely changed. I could offer you to have a look at the FF developer console or have a team viewer session if you want to look for yourself. When RC2 is out I would also update to it and try again with all FF plugins disabled. Failed to do that last time.
How many GB of data can a Duo/DuoX/Dwarf store in the “File Manager”?
Is it possible to graphically display the complete hard disk usage in the File Manager above “Size”? That would be helpful for managing the audio/MIDI/… data.
Is it possible to graphically display the complete hard disk usage in the File Manager above “Size”? That would be helpful for managing the audio/MIDI/… data.