You will need to set GMA2 to recognize Channel 2 notes for these. I convert all of these from there respective channels and notes number to put out Notes on Channel 2 only. You might want to later set this to momentary state if you want tighter control on your LED state and have Bome MIDI translator manage the LEDвЂ™sДisabled all of your translators 1.30 through 1.35ДЎ.36 and 1.37 handles mapping for all Number buttonsДЎ.38 and 1.39 handles mapping for A|B buttonsДЎ.40 and 1.41 handles mapping for Solo buttonsДЎ.42 and 1.43 handls mapping for Record Arm buttons I only tested this on paper so if there is something not working, let me know.ДЄdded Init Preset and set it to send Init string to your APC-40 at project start.Д .0 вЂ“ Triggers a timer вЂњInitвЂќ at project openД .1 вЂ“ Triggers a timer вЂњInitвЂќ if you hit your computer escape keД .2 вЂ“ Sends the APC40 an initialization string to ensure it is in toggle state. Outgoing: Note on MIDI CH1 note pp velocity qq Subtract 1 this will produce 0-39 instead of 1-40 (my preference) Multiply by Chanel to get note this way CH will have notes 0-7 CH2 will have notes 8-15 etc If pp57 then exit rules, skip outgoing action Only do this for notes 53-57 which are on the main pad matrix Incoming : Note ON Any MIDI CH set to oo Any note set to pp any velocity set to qq If GMA2 will not accept these messages as unique (same note different MIDI Channel), then it is possible you would need to remap your controller.ДЄn example would be below, this will translate notes 53-57 on CH1-8 to Notes 0-39 on MIDI CH 1 Column 1 sends on MIDI Channel 1, Column 2 sends on MIDI Channel 1 etc. I spent cash, and it still doesn't work.Hi, on the APC 40 MK2 button matrix, each button gives the same note number but on a different channel. Both are examples of rushed incomplete implementations, that have never been finished.ДЄnd what is even more frustrating is that I purchased my controller device based on the marketing promises. The incomplete functionality in wirecast gives them no choice. Sorry to be blunt, and I know it is not your decision personally, but it is the same reason why people don't use rendezvous. Why would they purchase midi hardware, when they know others who tried have been disappointed, with no light at the end of the tunnel. With a half baked incomplete implementation, it is not surprising that your customer base is not interested. Let me provide a candid answer in response. If enough interest comes from the community regarding this, I am certain the priorities would change to reflect. WIFI/Bluetooth MIDI (TouchOSC would be great).Audio Mixer track pinning(or global/static audio mixer mode).Custom work around commands that are only accessible by menu bar and not primary UI.UI shading for easy mapping like Ableton.To truly make MIDI useful in Wirecast, I see a host of things needing to change: To date, I am not aware of any other reports similar to your crash regarding MIDI, though it sounds severe enough to not be isolated to your workflow. With so little usage/interest of MIDI, the team has opted to focus efforts on other areas of the app that offer benefit to a wider subset of users.

However, the vast majority of users seeking control surface support in Wirecast have opted for the XKEYS custom controller we developed in tandem with XKEYS. The MIDI functionality has been de-prioritized due to lack of interest from the wider customer base as a whole.ДЄs an 'audio guy' and hobby-musician, I look forward to an Ableton-style custom midi mapping paradigm within Wirecast.

Thank you for reaching out and asking about this.

Akai apc 40 mk2 modul8 mapping