Disconnectiong board : WaitSync Timeout

#1

Hello,
I am experimenting things with a 4 tracks loopstation patch, based on the lrec object. I added 2 filters and lfos to control them, and 2 stomp delay objects (and also a mixer).
I experiment the patch using through patcher as I have no midi controller.

After a while (from seconds to some minutes),and somehow randomly, I have a disconnect request issue. The looper keeps playing and I have to connect the board again.

I tried to format the sd card with util/format (with success).
I 've tested with various usb wires, shaked a little bit the plug and it looks OK.

Note that before disconnecting Patcher begins to get slow an lags.

Is it a SRAM overload? DSP looks OK.

Thank you for your help, I have a lot to learn!

I am with 1.0.12, brand new board (flashed last month) on Xubuntu 18.04
Here are the logs (I found some threads quoting them but with no help for me).

Ping: WaitSync Timeout, disconnecting now
Disconnect request
java.lang.InterruptedException
java.lang.InterruptedException
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:502)
at java.awt.EventQueue.invokeAndWait(EventQueue.java:1315)
at java.awt.EventQueue.invokeAndWait(EventQueue.java:1296)
at javax.swing.SwingUtilities.invokeAndWait(SwingUtilities.java:1348)
at axoloti.USBBulkConnection.DistributeToDisplays(USBBulkConnection.java:1079)
at axoloti.USBBulkConnection.processByte(USBBulkConnection.java:1258)
at axoloti.USBBulkConnection$Receiver.run(USBBulkConnection.java:868)
at java.lang.Thread.run(Thread.java:748)

#2

this is most likely an issue with the patcher, not the board. i have this disconnect requests also, mostly when i turn a dial the first time after the patch goes live. i then take it live again and that cures the problem. this works on OSX

#3

Hi,
thx for your answer, but unlike @lokki, patcher (or my patch) keeps disconnecting the board, even after the first attempt. Is it linked to a power limitation of my computer ram? tweaking too much through patcher?

Another clue for this issue?

Thank you!

#4

Hi,
Now I can affirm that is not due to one particular patch since the same Waitsync timeout disconnection request occurs while running other patches (somehow randomly).
Thx for your help

#5

I was having that error and It was because of using more than 8 modulation sources. The solution was to add the extra modulation sources in the view/settings menu.

#6

I'm not sure what causes this error, but it does happen to me a lot too.
To me it seems like there's a problem in the communication with the computer over the usb at moments that the patcher uses more cpu on the computer or something like that. I noticed it happening more when I have a game opened in chrome, that runs on java. So perhaps java itself is the culprit..
I once asked a friend for help, but as soon as I told him it ran on java, he laughed and walked away..

#7

Hello, thank you for your ideas and feedback.
I tried this afternoon to increase modulation sources and it has disconnected once and no more then. I can tweak as much as my mouse allows me!
@servandisco, I didn't see this option before. Just to understand, is it saving sram to adjust to the exact amount of modulation? (and sources), something to do with scanning parameter changes?

#8

Hi @Quentin , yes, the amount of presets and modulations have an influence on Sram.. I'm not super techy but I did read that trick once in some "saving sram" topic and I apply it myself now as I hit more frequently the sram limit than the cpu one..
Here is the thread: https://sebiik.github.io/community.axoloti.com.backup/t/saving-sram-tips/4412/9
happy patching!
S