IR Loader crashes when I try to switch IRs rapidly.
It happens very randomly when switching IR. I’m testing an empty pedalboard with IR Loader Cabsim only and it is not even connected to input and output. Sometimes it takes 3 attempts, sometimes it takes 50 attempts or more.
The problem is that it crashes even when switching snapshots and the IR saved on each snapshot is always the same.
Recap:
IR Loader Cabsim alone crashes randomly when you try to change IR rapidly.
If you have a pedalboard that contains IR Loader Cabsim and you have multiple snapshots with same IR selected, it crashes randomly even if you jump from one snapshot to another (without changing IR then). This is super annoying since in a live situation it can crash at every snapshot change!
Can you define “switching IR rapidly”? Isn’t switching IRs a binary step with a finite pace (one on while the other is off switching to another on while the first is off)?
-OR-
Do you mean scrolling quickly from one IR in a list to another, that have several other IRs between them?
I wonder if CV Parameter Modulation would allow you to create a foot-press that jumps directly to a specific IR in the list, the same way it allows you to jump to a specific volume or effect level (with some experimentation of course).
@redcloud I don’t know if it happens only with me, but when I try to open the link to the video it says that it was archived. Have you managed to solve the issue?
Have you tried change the IRs following in a logical sequence instead of randomly picking each one? Do you think it’s possible to be related to a specific IR? I could not replicate here.
Yes, I selected a subset of 10 IRs end selected 1 by 1 sequentially, up and down. When it crashed, I rebooted the Dwarf and selected another subset of 10 IRs from another “vendor”. So it seems that it’s not related to a particular IR or format (48kHz, 1024 samples for all my IRs anyway).
It’s easier to replicate the issue with a mouse macro recorder. Anyway it happens faster with crowded pedalboards and this suggests a memory leak (even if memory occupation is low).
Yes, I can refresh the page or click on the Reload button when disconnection happens. The device responds to both physical footswitch and knob input. It seems that the only thing that stops working is the dsp processing.
ok. So for the audio to get back you need to reboot it, correct?
If the audio gets back with the refresh of the WebGUI I would say that the problem is quite weird.