Mac 4.20 Lockups and/or showing wrong playing information
If I have the BluOS controller app running when the Mac wakes from sleep, or maybe even when it has been in the background for a while, I see:
* The play/pause button does not work at all, or it will pause but never play
* The play/pause button state doesn't reflect the playing state
* The play queue is completely out-of-date
* The mini-player and main player show completely out-of-date information, from tracks played a long time previously. The play progress continues to progress and play time change, but doesn't necessarily have anything to do with what is actually playing.
-
Same problems here. And the problems were there on 3.x also. I remember some Java exceptions popping up there.
So yeah, after waking Mac from sleep, close and start BluOS controller. Every. single. time.
After a while I developed the strange habit of only starting the controller when I wanted to actually control the system and close it afterwards.
And because the binary is still not optimized for Apple's M1 processors, my phone is quicker, so i'd rather use that instead.
For me, there is no fun in using the Mac controller in the state as it is now. It's slow, bulky, clunky and unreliable.
You would think a redesign of the controller on 4.0 would deliver a fast, reliable universal binary.
I doubt this will ever be fixed.
0 -
I don't find the iOS app to be much better, and the extra steps in unlocking the phone, launching the app, etc. is irritating.
The iOS app seems like it was designed by half a dozen people who never talked and decided on standards. The weird in consistencies in UI controls used, visual glitches, fonts, spacing, alignment, capitalisation, localisation, and basic usability issues, are irritating.
It certainly doesn't feel premium.
0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
2 Kommentare