Fri, Oct 11
Could not reproduce
Thu, Oct 10
Will be added with the next update for v1.0.10
Wed, Oct 9
Fri, Oct 4
Thu, Oct 3
Tue, Oct 1
Issue is reproducable in a certain android environment with certain usb midi devices connected. Not sure what the root cause is yet
Seems like it's related to android 8 somehow
Mon, Sep 30
I would like to have this also for the android version of MS QU
Sat, Sep 21
Either, I guess. It's actually something I could see using myself. In the heat of the moment, I have clicked on the wrong mixer.
Do you mean the mixer selection (e.g. qu16, 24,...) or the series selection?
Wed, Sep 18
As already mentioned the goal is to have a unified UI for different mixers. Therefore the mixer specific terminology won't be applied everywhere.
Tue, Sep 17
Because MS-Pro serves a lot of mixers, I think also it will be a lot of work for David to change all function names to the mixer-function-names (doesn't it?). I work with A&H QU 16, but I think it is not soooo problematic to remember the MS-Pro-specific terminology, but I don't have Alzheimer yet ;-) (sorry, joke!). So most time I work with the MS-App... only for some specific things I do it on the mixer itself. Never had problems with the light terminology differences. But if it would be possible to assimily for MS-QU, I would not be angry... :-)
btw, when you're creating a task, you can assign it to Wishlist.
This is an interesting question. As someone who uses MSP with a number of different mixers, I would like the labels to be as consistent as possible whichever mixer I'm operating. Q vs BW is another example. Perhaps an option?
Sun, Sep 15
In offline mode only bus 1 is linked. Therefore by default you can only pan bus 1/2
Sep 14 2019
Sep 11 2019
Sep 9 2019
Sep 8 2019
This is not an issue. The value itself can be modified much more fine granular than single integer values. Therefore mixing station shows the full precision of the value
Sep 6 2019
Currently in beta test
I think i found the root cause
No feedback received
Sep 2 2019
The mixer actually allows finer control than just integer values, therefore the app shows decimal places
Waiting for screenshot
Aug 30 2019
This seems to only occur on Samsung Tab A devices. The current assumption is that it's a OS/driver related issue as all other devices work fine
Aug 24 2019
Aug 17 2019
Aug 14 2019