Hi! Can you please tell what was your idea about this issue?
I suspect it being about one or more message types to sorta clog the lines between the device controller and the main system. Like having MIDI sync enabled, which causes a lot of internal messages to be generated because of MIDI drift and constant readjustment being made to the BPM value.
If that is the case, then I know where the code system some optimizations…
Okay. So do you need anything from my side? Maybe logs when this happens?
Can you tell me if you are using MIDI sync or MIDI clock out?
thanks
I’m using MIDI sync. No MIDI out.
alright, so that confirms my suspicions of what is wrong (in our software).
does the issue go away when you disable midi sync? (that is, transport mode is “internal”)
confirmation would be great. because then I know exactly where to look in order to fix the issue,
I will try as soon as will be near my gear.
The issue is still there, even without connection to my PC. In addition, I’m using my Launchpad pro MK3 as my keys/sequencer to trigger ModDuoX, and it is connected to USB-host port of ModDuoX.
What I did:
Started to play around with my patch until this problem shows up. Then switched MIDI to internal, stopped transport. Disconnected from PC.
But unfortunately, the problem still there and only reboot to solve this. Also, I ticked auto controller restart, after some time controller restarts automatically.
Timing is really random, could take 15-20-30-45 minutes after a reboot before the problem shows up again.
I guess it looks like some kind of buffer getting overloaded. Because I’ve noticed if I stop everything and then just wait 10-15 min ModDuoX back again to normal operation. But it is could be a controller restart because I’m not staring 15min straight on DuoX screen.
PS.
There is also a bug with pedalboard naming. When I’m giving a name to my pedalboard and then saving it, after reboot the name is switched to another one which is from the factory bank. For example my pedal name: 123456 then it is DRM - ONYX/CAB/MODULAY
And one more.
When snapshots assigned to the endless knob after I’m getting to the middle of the list I need to make two “clicks” with a knob to jump to the next snapshot.
PSS: I just caught the problem while was recording the bug with an endless knob. And all my gear was not playing anything, my clock was stopped either. MIDI sync was internal.
Bump.
Any updates?
Unfortunately not yet. With the celebrations holidays, the team just got back to work yesterday.
As soon as there’s some news we will let you know.
Hope that you understand it
Hello, Jon. No problem!
1 Like
Hi,
I still experiment issue when upgrading. Unfortunatly I didn’t had enough time to try youe proposed solutions. Now I try to upgrade to 1.10.0.2141.
1 It doesn’t work with the web browser . The mod duo display “starting upgrade …” for about 15 minutes. Nothing happens
2 Same with manual upgrade, from systme menu of the browser and menu of the Mod duo
3 So I try the method " Troubleshooting Reinstall via LiveSuit". everything works fine until I get the window “Upgrade…”. After clicking Phoenix suite crashes. I deplug and replug the Mod duo, I get the window “Tips: does mandatory format…” I click Yes and I get this message
So what can I do? And what doesn’t run?
Thanks for answer
Hello Pascal,
I would need a bit of memory refresh here.
What is happening with your device? Can’t you access the WebGui? Does it work normally without the WebGui?
Hi Jon
Thanks for answer. Yes my mod duo works fine and I normally access the web GUI. The problem happens when I try to make an update.
1 from the web GUI: the update download and the mod duo freezes on the message (something like) “…is now updating please wait”.
2 same thing when trying a manual update.
3 So, after reading several wikis I though it could be a good idea to reinstall the system via Live Suite. I think I followed precisely the instructions before getting the message I sent in my last post.
This issue is not really annoying as far as I can use my mod duo , but it just worry me as far as no system update seems possible.
So you tried the LiveSuit option but the unit is still booting after that has failed?
Might be you have a Duo with MMC, while LiveSuit is only suitable for reinstalling for NAND units.
Details at Troubleshooting Reinstall Duo - MOD Wiki
Do the device screens still work correctly?
Yes everything is working correctly: The Duo boots up and the screens display are Ok. You’re right, after further search I think I have a MMC. It was not very clear for me that reinstalling with live Suite was only for NAND.
So what can I do?
Thanks
Try to force the system to start in restore mode.
So basically:
- turn off the unit
- hold down the left knob and footswitch down while powering on the unit
- keep holding for 5 seconds
if all goes well, unit should enter in restore/update mode.
I try your mehod. the duo freezes (waiting for about 15 minutes) on splash creen with MOD DUO on the right screen and the logo on the leftt screen.
hmm alright so that explains why the update is failing.
not sure how it got into this state… some previous install attempt aborted at the beginning?
in any case, we can just reinstall, just wondering the best way now…
do you have a linux or macos machine around? a VM would work too.
Yes I Have a linux PC (Ubuntu). May be possible to share a mac