- This topic has 35 replies, 4 voices, and was last updated 6 years, 8 months ago by Zhao Yitian.
August 20, 2016 at 11:23 am #28154
So you mean your WIDI BUD with new firmware paired with Mi.1 without any problem, but when you send CC#11 from Korg Microkey through Mi.1 to WIDI BUD (connected with you Windows 10 PC), then it caused delay at WIDI BUD side?August 20, 2016 at 7:53 pm #28155
Sorry I did not make it more clear. The WIDI BUD with the new beta firmware paired with the Mi.1. No issue there. The midi controller keyboard I was using is a Korg MicroArranger not Microkey keyboard, and the Mi.1 was plugged into the 5 pin midi out of the Korg MicroArranger. When I begin to play, there is severe latency from the start. I tried the same setup on a different computer. The latency issue is the same.
In regards to cc#11, it makes the latency even worse. I used a midi accordion as the controller. The bellows sends out cc#11. When I work the bellows just a little bit playing a few notes, it must be choking the WIDI BUD. Not only does it cause extreme latency, but notes are hung. The WIDI BUG is such a great idea. I hope we can solve the issue. Thanks.August 21, 2016 at 3:50 am #28156
Thanks, this is clear enough. We will test from our side and get back to you soon, I am sure this will be solved in firmware update. By the way, one more question, did you try to update the Mi.1 firmware as well?August 21, 2016 at 3:58 am #28157
I was the early adopter when Quicco Sound had a Kickstarter going on for their Mi.1. At first, it just could not handle all the cc#11 from my midi accordion on multiple channels. After the firmware update, it works great though the very 1st generation of the Mi.1 which I have can not be updated to the lastest version of firmware because it requires new hardware. Then again, I can never choke my Mi.1 after the firmware update.August 21, 2016 at 4:50 am #28158
Ok, got it. Can we know the firmware version of your Mi.1?August 21, 2016 at 5:09 am #28159
It says 2.2.1August 21, 2016 at 5:18 am #28160
Thanks. By the way, if you did not send CC#11 but instead of other control message such as CC#01 of modulation, will you have same problem?August 21, 2016 at 5:25 am #28161
Not Modulation, bu I tried pitch bend just now. Because of the severe latency just in playing notes, pitch bend makes the latency even worse.August 21, 2016 at 6:23 am #28162
So you mean if you only play the notes, it still has latency there?
Will test it through this way, thanks!August 21, 2016 at 7:22 am #28163
Yes, that’s exactly what I meant. Just a single note from the start has lot of latency. I used different DAWs, two computers, and so forth to see if it was a pilot error on my part or if there is any issue with my system.August 21, 2016 at 5:32 pm #28164
Ok, clear. Our CTO will check it on Monday, thanks!August 21, 2016 at 11:13 pm #28165
I tested my C.24 Miselu Bluetooth keyboard with the WIDI BUD. As I expected it worked much better than the Mi.1. So the issue is with the Mi.1. I look forward to your test results with the Mi.1.August 22, 2016 at 4:04 am #28166
Ok. Thanks very much for your help. 🙂August 23, 2016 at 8:48 am #28167
I just wanted to add that even though the C.24 Miselu Bluetooth keyboard works much better with the WIDI BUD in terms of latency than the mi.1 with WIDI BUD, the velocity is pretty abrupt. It goes from quiet to loud rather too quick and abrupt. I thought it was the keyboard of the C.24 Miselu, but when I connected it to the iPad over Bluetooth, the velocity level was very smooth.August 23, 2016 at 9:09 am #28168
This sounds very strange, because the velocity message is always with MIDI note message, one note has one velocity message, and the transmission will not change the message, how can that be different? Maybe you can use the MIDI monitor to check on your iPad, for example you can compare the velocity message from WIDI BUD and USB MIDI and see whether they are different (you can do same for iPad Bluetooth and USB MIDI too.).
- You must be logged in to reply to this topic.