Page MenuHomePhabricator

Button LED for MCU not updated correctly
Closed, ResolvedPublic

Description

I have a X-touch running on my PC mixing station install. I can set up buttons for layer change with "On midi event+change" to enable the feedback light on the button to show which layer is active. But when I save the settings and restart the app and X-touch the settings doesn't seem to be loaded correctly and is back to "On note up+change"

Tested on both beta and release version of the app

Platform: Windows
Variant: XM32
Version: 0.3.2(80)

Event Timeline

Could not reproduce, even after restarting the app the button controller still has "On midi event" selected as output mode

{{userId:1}}

ok I tried everything maybe you can take a look at my file, I cant even change the name and save it. I am talking about "From - A 84"
https://1drv.ms/u/s!AriktNgt_L_2gboF20TqzNmbUdtyLw?e=FQlKtD

{{userId:84}}

You're using "MCU" mode. If the X-Touch is also in MCU mode the buttons should work without any changes.
That's also why you can't change the output mode, because MCU has a defined output behavior that is not editabe/saved in the settings.

{{userId:1}}

Ok, but when I change it it works like I want. The led feedback shows in which layer I am. But you say that’s not possible in MCU mode. Should I put it in HUI mode is this recommended?

{{userId:84}}

Make sure the X-Touch is also in MCU mode. If it is then this is a bug and I'll try to reproduce it. (I only tested a BFC2000 and Wing-MCU since I don't have a X-Touch but they should all behave the same in MCU)

{{userId:1}}

Yes x-touch is in MCU mode

{{userId:84}}

AnonymousTaskBot changed the task status from Open to Confirmed.Jul 8 2020, 3:35 PM
david renamed this task from Midi settings not saved correctly to Button LED for MCU not updated correctly.Jul 8 2020, 3:41 PM
AnonymousTaskBot mentioned this in v1.1.4.
AnonymousTaskBot mentioned this in v1.3.0.
AnonymousTaskBot mentioned this in v0.4.0.
AnonymousTaskBot mentioned this in v1.1.3.
AnonymousTaskBot mentioned this in v1.1.3.
AnonymousTaskBot mentioned this in v1.1.0.
AnonymousTaskBot mentioned this in v1.1.3.
AnonymousTaskBot mentioned this in v1.1.3.
AnonymousTaskBot mentioned this in v1.1.3.

The fix will be inlcuded in todays hotfix

{{userId:1}}