Host Port Midi Note out issue (receive error: LIBUSB_ERROR_PIPE)

Hello all has anyone managed to send midi out of the host port, I am attempting to send clock out usb host port 1 using factory object midi/out/clock and am getting a patch load error, I just want to see if someone can replicate this before I put it down as a bug, slightly concerned it is some kind of midi loop issue that I have created, while I’m at it, is the midi routing page working or is it to be done as it states “todo:deploy virtual midi ports”

USB device found
Connected to device.
Firmware version on attached device: 3.0.1.0, crc=0x9922E990
Generate code complete
Compiling patch.
/Users/reubenfinger/Library/Akso/build/xpatch.cpp: In member function ‘void rootc::instanceclock__1::dsp(rootc*, bool, bool, bool&, int32_t&, int32_t&, int)’:
/Users/reubenfinger/Library/Akso/build/xpatch.cpp:120:24: warning: integer overflow in expression of type ‘int’ results in ‘2147483647’ [-Woverflow]
_posfrac &= (1<<31)-1;
~~~~~~~^~
Memory region Used Size Region Size %age Used
SRAM: 3356 B 384 KB 0.85%
SRAM2: 0 GB 8 KB 0.00%
SRAM3: 1768 B 118 KB 1.46%
CCMSRAM: 964 B 116 KB 0.81%
SDRAM: 0 GB 32 MB 0.00%
done /Users/reubenfinger/Library/Akso/build/xpatch
Done compiling patch.
receive error: LIBUSB_ERROR_PIPE
Control transfer failed: -9
Disconnected from device.
java.io.IOException: java.util.concurrent.TimeoutException
java.io.IOException: java.util.concurrent.TimeoutException
at axoloti.connection.USBBulkConnection_v2.read(USBBulkConnection_v2.java:856)
at axoloti.live.patch.PatchViewLive.lambda$goLive$7(PatchViewLive.java:279)
at axoloti.job.JobProcessor.lambda$exec$0(JobProcessor.java:21)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:834)
Caused by: java.util.concurrent.TimeoutException
at java.base/java.util.concurrent.CompletableFuture.timedGet(CompletableFuture.java:1886)
at java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:2021)
at axoloti.connection.USBBulkConnection_v2.read(USBBulkConnection_v2.java:852)
… 5 more

So I did a bit of further investigation and uploaded the patch below to both Axoloti and Akso and it works on the axoloti but fails on Akso (ignore midi channels they were set to proper channels while testing)

same error USB device found
Connected to device.
Firmware version on attached device: 3.0.1.0, crc=0x9922E990
Generate code complete
Compiling patch.
Memory region Used Size Region Size %age Used
SRAM: 7444 B 384 KB 1.89%
SRAM2: 0 GB 8 KB 0.00%
SRAM3: 1884 B 118 KB 1.56%
CCMSRAM: 2864 B 116 KB 2.41%
SDRAM: 0 GB 32 MB 0.00%
done /Users/reubenfinger/Library/Akso/build/xpatch
Done compiling patch.
receive error: LIBUSB_ERROR_PIPE
Control transfer failed: -9
Disconnected from device.
java.io.IOException: java.util.concurrent.TimeoutException
java.io.IOException: java.util.concurrent.TimeoutException
at axoloti.connection.USBBulkConnection_v2.read(USBBulkConnection_v2.java:856)
at axoloti.live.patch.PatchViewLive.pollDisplays(PatchViewLive.java:206)
at axoloti.live.patch.PatchViewLive.lambda$new$4(PatchViewLive.java:237)
at axoloti.connection.USBBulkConnection_v2$PeriodicPinger.run(USBBulkConnection_v2.java:1424)
at java.base/java.lang.Thread.run(Thread.java:834)
Caused by: java.util.concurrent.TimeoutException
at java.base/java.util.concurrent.CompletableFuture.timedGet(CompletableFuture.java:1886)
at java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:2021)
at axoloti.connection.USBBulkConnection_v2.read(USBBulkConnection_v2.java:852)
… 4 more

Logged as a Bug on Github

This is definitely a bug. Thanks @reubenfinger !

1 Like

Hi!. To add to what @reubenfinger has already posted, I’m having a similar error when using the midi/out/cc thin object, which i use to get visual feedback from the patch on the led buttons of a Korg nanokontrol2.
i am getting this error:

USB device found
Connected to device.
Firmware version on attached device: 3.0.1.0, crc=0x9922E990
Generate code complete
Compiling patch.
Memory region Used Size Region Size %age Used
SRAM: 3020 B 384 KB 0.77%
SRAM2: 0 GB 8 KB 0.00%
SRAM3: 1752 B 118 KB 1.45%
CCMSRAM: 880 B 116 KB 0.74%
SDRAM: 0 GB 32 MB 0.00%
done /Users/gustavo/Library/Akso/build/xpatch
Done compiling patch.
Control transfer failed: -1
receive error: LIBUSB_ERROR_IO
Disconnected from device.
java.io.IOException: java.util.concurrent.TimeoutException
java.io.IOException: java.util.concurrent.TimeoutException
at axoloti.connection.USBBulkConnection_v2.read(USBBulkConnection_v2.java:856)
at axoloti.live.patch.PatchViewLive.pollDisplays(PatchViewLive.java:206)
at axoloti.live.patch.PatchViewLive.lambda$new$4(PatchViewLive.java:237)
at axoloti.connection.USBBulkConnection_v2$PeriodicPinger.run(USBBulkConnection_v2.java:1424)
at java.base/java.lang.Thread.run(Thread.java:834)
Caused by: java.util.concurrent.TimeoutException
at java.base/java.util.concurrent.CompletableFuture.timedGet(CompletableFuture.java:1886)
at java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:2021)
at axoloti.connection.USBBulkConnection_v2.read(USBBulkConnection_v2.java:852)
… 4 more

Any news on this bug?
bug is still present in current 3.0.1 release.

is there a workaround?
receiving notes just fine

No further movement on this bug yet, although from memory the device port has no such bug.

3.0.1 is the 1st and current release, there is a Dev version on Github and Nic has stated that he is working on the bugs, but…

he has been radio silent for a while, the world is topsy turvy right now so I am sure he has his reasons, other than those that he has previously stated…

I’m sure an update from him would go a long way to appease those of us who purchased Akso, but honestly the poor guy has probably burnt himself out, new job, new city and trying to mitigate the backlog of Akso orders placed as well as having to deal with the fiasco that postage is at the minute, and refunds too…all sounds like a hell of a lot of work to me,

I’ll admit that what Akso offers is tantalizing, and I think a lot of us are Axo users so we know more than most the punishing constraints of SRam on our big ideas, so it is frustrating , with all of that potential, that the things we now take for granted on the Axo fall prey to bugs in Akso when we hit that live button, but I have faith that Nic will come good when the dust settles, I mean people are still receiving their orders, so I’m guessing he is making fulfilling those orders his first priority, when he gets the time.