I have test buttons defined with that new option for those two
"Show Floating menu..." and "Go Back/Previous..." actions
here is what happens:
(iPhone and iPad shows the same menu.)
pressing the button on the iPhone: both iPhone and iPad triggers action
pressing the button on the iPad: both iPhone and iPad triggers action
( or in other words menu and navigation is the same on both devices )
this is what I would assume should happen...
pressing the button on the iPhone triggers only the action for the iPhone
and will show a different menu now on the iPhone only...
and similar/analog when that button is pressed on the iPad...
yes, 5.308 fixed the "Device That Sent Last Command" option",
Menu navigation can now be indenpendent on multiple devices, nice...
thanks a lot,
Christian
Today, the latest version was upgraded. btt: 5.3.15. btt mobile: 0.23. It was tested again. The problem still exists and it still disconnects frequently.
There is no feeling that the network is special. There is also no firewall. The interconnection between iPhone and Mac for other applications is all normal.
BTT crashes in a loop after restarting with an old floating menu I reactivated last week, and I had to reinstall BTT. Now, even if I reactivate the remote app, the BTT mobile presets are not reappearing.
Just a note in case a crashloop or similar happens, always try to start BTT with safe mode enabled using this terminal command, this can get around most crashes:
I know we are in early alpha tests with "BTT Mobile"...
I noticed that once "BTT Mobile" is connected (and showing a menu)
the BTT Mac app becomes (quite a bit) slower over here,
(as menus are refreshed on the fly, which is quite nice when designing the menu)
But the BTT Mac is slower even when not working on a floating menu,
therefore:
Could you consider to add a setup option (in BTT Mac) for BTT Mobile, like
„Do not refresh BTT Mobile content while BTT got focus / is front window“
At the moment I use the below workaround or
close the BTT Mobile app manually before I work in the BTT Mac app...
I can't really think of a reason why it would be slower (it doesn't seem to be here). Maybe it is related to your large menu, but I can't see how BTT Mobile would trigger any re-renderings.
Is it only slower if a BTT Mobile client is connected?
yes, that happens when the BTT Mobile client is connected, the menu is shown and BTT Mac is focused...it happens also when your example menu is used.
My 'large' menus are as such quite fast and speed is fine for me...handling two iPad at the same time, works...
What is still an issue (not related to BTT Mobile) is to read the Ableton screen at 6 different positions to find out which BTT menu button needs to be updated (audio Playing/Stopped etc. etc). That takes about 1-2 sec before the updated BTT menu (during navigation) can be shown (and that is on its own fast...) anyway...
more than happy with the current alpha, you did a top job !
Thx,
Christian