I have an Alesis Coda (with integrated USB output) that I have connected via USB to my Macbook Pro: it works very well.
When I connect the same keyboard using the same USB cable (and tested with two different USB to USB OTG adapters) to my Samsung Galaxy 6 android device running android 6.0.1 and latest updated synthesia, it drops notes, drops the "up" key signal (synthesia thinks the key remains down forever), and has various other glitches that render it unplayable. Note that it does this when I'm playing only one or two notes at a time (ie. not a whole lot of activity, I'm just learning piano).
What would be the best way to troubleshoot this and help to get it fixed?
Alesis Coda connected to Samsung Galaxy 6 (android)
When describing problems, always mention your OS and game version (shown at the bottom of the title screen).
If your keyboard has USB or MIDI ports, there is a tremendously high chance (>99%) it will work with Synthesia. See what you'll need on the keyboards page.
If your keyboard has USB or MIDI ports, there is a tremendously high chance (>99%) it will work with Synthesia. See what you'll need on the keyboards page.
Hmm, we've heard of lots of different Galaxy's having trouble with MIDI by simply disallowing Synthesia access to the USB port, but not of lost/corrupt data coming in.
Is the USB cable connecting your Coda very long? Does it travel near anything that might cause EMF (like a speaker, cell phone, or power line)? It might be worth trying a different MIDI-enabled app on your Galaxy to see if the same problems show up there.
Is the USB cable connecting your Coda very long? Does it travel near anything that might cause EMF (like a speaker, cell phone, or power line)? It might be worth trying a different MIDI-enabled app on your Galaxy to see if the same problems show up there.
-
- Posts: 4
Well here is some more information:
I have two cables: 1) normal USB "printer" cable (USB-A to USB-B, I believe. It's about 3 feet long and had a long and successful life connected to my scanner without issue), and 2) USB OTG adapter to USB-A female
I have attached cable #1 to my Macbook: success! (Inconvenient because I don't have a way to securely put the macbook next to the keyboard, and I'd have to take it away from my computer desk)
I have attached cable #1 and #2 to a generic chinese tablet running Android 5.0: Success!
I attached the same cables #1 and #2 to my Samsung Galaxy S6 Active: notes missed (misses 'down' events and 'up' events, the latter causes the song to freeze forever in the mode I'm using.)
No, the USB cables are not near any sources of RF. They are several feet away from AC power cords, and there are no flourescent lamps anywhere near.
In the end, the tablet works, so I'll probably just dedicate that tablet to the keyboard, as it doesn't otherwise have a purpose in life. It would be nice to have the galaxy working, but it's not critical. I'm willing to debug and help if you want to pursue it.
I have two cables: 1) normal USB "printer" cable (USB-A to USB-B, I believe. It's about 3 feet long and had a long and successful life connected to my scanner without issue), and 2) USB OTG adapter to USB-A female
I have attached cable #1 to my Macbook: success! (Inconvenient because I don't have a way to securely put the macbook next to the keyboard, and I'd have to take it away from my computer desk)
I have attached cable #1 and #2 to a generic chinese tablet running Android 5.0: Success!
I attached the same cables #1 and #2 to my Samsung Galaxy S6 Active: notes missed (misses 'down' events and 'up' events, the latter causes the song to freeze forever in the mode I'm using.)
No, the USB cables are not near any sources of RF. They are several feet away from AC power cords, and there are no flourescent lamps anywhere near.
In the end, the tablet works, so I'll probably just dedicate that tablet to the keyboard, as it doesn't otherwise have a purpose in life. It would be nice to have the galaxy working, but it's not critical. I'm willing to debug and help if you want to pursue it.
-
- Posts: 4
I checked another MIDI app and my keyboard works ok.
So: same exact cables and everything and synthesia works 100% with my crappy/cheap chinese tablet, but drops notes on samsung galaxy 6.
On the Galaxy 6 itself, synthesia drops notes, but another MIDI app seems to work ok.
So: same exact cables and everything and synthesia works 100% with my crappy/cheap chinese tablet, but drops notes on samsung galaxy 6.
On the Galaxy 6 itself, synthesia drops notes, but another MIDI app seems to work ok.
That is an interesting set of data.
The first half (works on one tablet; not the other) seems to be in favor of Synthesia working correctly.
The second half (works in another app; not in Synthesia) seems to be against Synthesia working correctly.
Hmm.
Do you happen to know if the other app is using any of the new, official MIDI support added to Android in the 6.0 (Marshmallow) update? Until 6.0, the only way to get MIDI support was to include our own, low-level USB driver right inside Synthesia. Since 6.0 (and now, almost two years later, that almost one third of devices are running it), we've been hoping to hook into the new infrastructure on devices that support it. I suspect this might fix the problem you're experiencing (along with adding new features like Bluetooth MIDI support, etc.). It doesn't look like it's going to make it into Synthesia 11, but hopefully shortly afterward.
The first half (works on one tablet; not the other) seems to be in favor of Synthesia working correctly.
The second half (works in another app; not in Synthesia) seems to be against Synthesia working correctly.
Hmm.
Do you happen to know if the other app is using any of the new, official MIDI support added to Android in the 6.0 (Marshmallow) update? Until 6.0, the only way to get MIDI support was to include our own, low-level USB driver right inside Synthesia. Since 6.0 (and now, almost two years later, that almost one third of devices are running it), we've been hoping to hook into the new infrastructure on devices that support it. I suspect this might fix the problem you're experiencing (along with adding new features like Bluetooth MIDI support, etc.). It doesn't look like it's going to make it into Synthesia 11, but hopefully shortly afterward.