Bluetooth reconnect in Song
Search the forum before posting your idea.
No explicit, hateful, or hurtful language. Nothing illegal.
No explicit, hateful, or hurtful language. Nothing illegal.
-
- Posts: 4
Hi there,
I recognized that when I’m coming back to my piano, fire up my iPad -> Synthesia I want to just come back to the song where I left it. That seems to work, but it sure says “oops no connection...”. I then have to go out of the song to the settings and tab on Bluetooth and then connect...
Is it possible to add a button to the “oops” message and there trigger the reconnection to stay in the song?
That would be awesome
Thanks Seb!
I recognized that when I’m coming back to my piano, fire up my iPad -> Synthesia I want to just come back to the song where I left it. That seems to work, but it sure says “oops no connection...”. I then have to go out of the song to the settings and tab on Bluetooth and then connect...
Is it possible to add a button to the “oops” message and there trigger the reconnection to stay in the song?
That would be awesome
Thanks Seb!
I thought as much.
Does the Synthesia app request BT permissions? Then at least it might be possible according to what I read about the bluetooth-central permission set on
https://developer.apple.com/library/arc ... round.html
Might only be regarding BT LE devices though.
Does the Synthesia app request BT permissions? Then at least it might be possible according to what I read about the bluetooth-central permission set on
https://developer.apple.com/library/arc ... round.html
Might only be regarding BT LE devices though.
As a general rule, I try to make Synthesia as friendly a neighbor as possible. (This is why it will NEVER modify a single byte of a MIDI file.)
On Android, adding the kinds of Bluetooth permissions you mentioned also requires adding Location permissions because Bluetooth device names can be used in a sort of wardriving-style attack to discover a user's physical location. I'd rather keep Synthesia's attack surface as small as possible. The fewer permissions my code has and less mission-critical it is, the happier I am. If I mess something up with Bluetooth, I might drain your battery in a few minutes.
(This actually caused a bit of friction with The One Smart Piano Hi-Lite integration: for whatever reason, they decided their device shouldn't be allowed to pair. So to communicate with it, you have to use an ad-hoc, unpaired connection while scanning for Bluetooth devices. This may make sense for The One's own apps, but having Synthesia constantly scanning for devices that less than 1% of our users have doesn't make any sense. So, that one is wired-only for now.)
So, the short version is yes: Synthesia could ask for control over your device and pair/reconnect all sorts of things, but as a policy stance I don't want that kind of power.
On Android, adding the kinds of Bluetooth permissions you mentioned also requires adding Location permissions because Bluetooth device names can be used in a sort of wardriving-style attack to discover a user's physical location. I'd rather keep Synthesia's attack surface as small as possible. The fewer permissions my code has and less mission-critical it is, the happier I am. If I mess something up with Bluetooth, I might drain your battery in a few minutes.
(This actually caused a bit of friction with The One Smart Piano Hi-Lite integration: for whatever reason, they decided their device shouldn't be allowed to pair. So to communicate with it, you have to use an ad-hoc, unpaired connection while scanning for Bluetooth devices. This may make sense for The One's own apps, but having Synthesia constantly scanning for devices that less than 1% of our users have doesn't make any sense. So, that one is wired-only for now.)
So, the short version is yes: Synthesia could ask for control over your device and pair/reconnect all sorts of things, but as a policy stance I don't want that kind of power.
One optimization request: when I'm in a song and the connection is lost, I get the yellow trip alert. The options button takes me directly to the bluetooth connection screen and when done right back to the song position.
When I tap on a song and there is no connection, the song practice screen offers the connections button fix it. But - when reconnecting via this route I get taken back to the settings page instead of the song practice page after successfully reconnecting.
Suggestion: take me back to the song practice page here as well.
When I tap on a song and there is no connection, the song practice screen offers the connections button fix it. But - when reconnecting via this route I get taken back to the settings page instead of the song practice page after successfully reconnecting.
Suggestion: take me back to the song practice page here as well.
Hmm, this one might be a little trickier. That message on the song settings screen can be there for any number of reasons (and not just because of a recent device disconnect). If the device settings were a simple popover (like the Bluetooth settings screen), that wouldn't be so bad, but that would take a larger rework.
Oh, sorry for the confusion! That's the only reason it appears, but I meant you might actually have no available devices for a variety of other reasons. (One good reason is that you simply don't have any MIDI devices.)
My impression (from emailed questions, at least) is that Bluetooth devices are used less than 10% of time (vs. any other kind of digital piano connections), so sprinkling "Bluetooth Settings" buttons all over the interface has a chance to confuse/mislead more users than it helps.
My impression (from emailed questions, at least) is that Bluetooth devices are used less than 10% of time (vs. any other kind of digital piano connections), so sprinkling "Bluetooth Settings" buttons all over the interface has a chance to confuse/mislead more users than it helps.