07-12-2023, 07:02 AM
Pete,
I really want to help you, but not sure what advice to give. I have a Samsung Tab A7 (so earlier model than yours) and I tested the bluetooth MIDI functionality with my SX600, and once I got everything connected properly (which required some finessing with a WIDI UHost), then it all worked great and I would send/receive registrations with no issues, which involves complex system exclusive messages. I have tested this same functionality with a Samsung Tab S4, and Tab S8 Ultra, and both work great as well. So as far as I can see, the MIDI functionality is working as designed and there are no bugs that I can locate. I don't have a beatbuddy or GT1000 (I have a Boss GT10 that works great though), so I can't speak to whatever issues you are facing with those devices. The captured MIDI messages you showed from MIDI-OX shows that MobileSheets is transmitting the correct information, so that seems to indicate that the BeatBuddy is at fault here if it's not responding properly to the messages MobileSheets is sending, or there is some other issue that I can't derive from the information you have provided about how your library is setup. If you bring up the song editor, go to the MIDI tab, tap +, set up a message, and tap "Test MIDI Command", that should trigger the functionality on the BeatBuddy. It's the simplest way to test things. If that works without issue, then try creating a new song and send the message. If that doesn't work, something bizarre is happening, so kill MobileSheets, go into the bluetooth settings, forget the pairing with the beatbuddy, turn bluetooth off, turn it back on, go into MobileSheets, go to the Configure MIDI Connections screen, connect to the beatbuddy (which should then ask you to pair) and repeat the test again to see if things work properly.
While testing MIDI over the last several years, I've often seen weird situations where MobileSheets can enter a state where every message is sent and received twice, because Google's library somehow is establishing multiple connections to the same device. Killing and restarting the app fixes it and it's hard to figure out how to reproduce the problem. I've also seen issues with the MIDI code in the OS itself is in such a state that you have to reboot the device to get things back into a working state and then everything works properly. For most of these types of issues, there is nothing in the MobileSheets code itself that can be done to fix the issue because it seems to be happening either in the underlying OS libraries or in the OS itself. I don't know if any of this applies to the situation you are encountering, but I just wanted to mention it, because sometimes you do have to restart the device, mess with the pairing, disconnect and reconnect devices, etc, but once they are in a good state, things should continue to work properly from that point on.
Mike
I really want to help you, but not sure what advice to give. I have a Samsung Tab A7 (so earlier model than yours) and I tested the bluetooth MIDI functionality with my SX600, and once I got everything connected properly (which required some finessing with a WIDI UHost), then it all worked great and I would send/receive registrations with no issues, which involves complex system exclusive messages. I have tested this same functionality with a Samsung Tab S4, and Tab S8 Ultra, and both work great as well. So as far as I can see, the MIDI functionality is working as designed and there are no bugs that I can locate. I don't have a beatbuddy or GT1000 (I have a Boss GT10 that works great though), so I can't speak to whatever issues you are facing with those devices. The captured MIDI messages you showed from MIDI-OX shows that MobileSheets is transmitting the correct information, so that seems to indicate that the BeatBuddy is at fault here if it's not responding properly to the messages MobileSheets is sending, or there is some other issue that I can't derive from the information you have provided about how your library is setup. If you bring up the song editor, go to the MIDI tab, tap +, set up a message, and tap "Test MIDI Command", that should trigger the functionality on the BeatBuddy. It's the simplest way to test things. If that works without issue, then try creating a new song and send the message. If that doesn't work, something bizarre is happening, so kill MobileSheets, go into the bluetooth settings, forget the pairing with the beatbuddy, turn bluetooth off, turn it back on, go into MobileSheets, go to the Configure MIDI Connections screen, connect to the beatbuddy (which should then ask you to pair) and repeat the test again to see if things work properly.
While testing MIDI over the last several years, I've often seen weird situations where MobileSheets can enter a state where every message is sent and received twice, because Google's library somehow is establishing multiple connections to the same device. Killing and restarting the app fixes it and it's hard to figure out how to reproduce the problem. I've also seen issues with the MIDI code in the OS itself is in such a state that you have to reboot the device to get things back into a working state and then everything works properly. For most of these types of issues, there is nothing in the MobileSheets code itself that can be done to fix the issue because it seems to be happening either in the underlying OS libraries or in the OS itself. I don't know if any of this applies to the situation you are encountering, but I just wanted to mention it, because sometimes you do have to restart the device, mess with the pairing, disconnect and reconnect devices, etc, but once they are in a good state, things should continue to work properly from that point on.
Mike