Reply to thread

Message

<blockquote data-quote="Joe Sanborn" data-source="post: 81130" data-attributes="member: 2062">Re: Uli Behringer of The Music Group Q&amp;ADear Steve,Full MIDI support is quite a relative term when using standard CC commands, considering the disparity between 10,000 parameters on the X32 side, and only ~120 CC commands per MIDI channel.There are not a lot of technical challenges, but rather challenges identifying what would be satisfying to most customers’ expectations.&nbsp;We are considering something like this with one of the future firmware updates:MIDI CH01 &gt; CC1…CC80 to control the channel/bus Faders (0…127)MIDI Ch02 &gt; CC1…CC80 to control the channel/bus Mutes (0,1)MIDI Ch03 &gt; CC1…CC80 to control the channel/bus Pan (0…64…127)MIDI Ch01 &gt; PCH &gt; program change commands to recall scenes 1…100 (is already implemented)&nbsp;Equalizers have on/off state, 4-6 bands with 4 parameters each, so it’s a total of 17 or 25 parameters per channel. Multiplied by 40 channels and 25 buses we get a total of 1280 EQ parameters. This might be spread over a minimum of 10 different MIDI channels in a pretty obscure pattern … Considering the three channels we used up already, there would only remain 3 MIDI channels for all the rest you are looking to control.&nbsp; So, the classic continuous controller approach is obviously not very useful for this.&nbsp;Providing anything more than faders, pans, and mutes would only make sense with a comprehensive Sysex implementation. We are currently not convinced it is worth the effort creating a dedicated Sysex map, because OSC is much more powerful and it already exists.Thanks for your feedback.Best regards&nbsp;Joe SanbornManager, Channel MarketingMUSIC GroupBEHRINGER</blockquote>

[QUOTE="Joe Sanborn, post: 81130, member: 2062"] Re: Uli Behringer of The Music Group Q&A Dear Steve, Full MIDI support is quite a relative term when using standard CC commands, considering the disparity between 10,000 parameters on the X32 side, and only ~120 CC commands per MIDI channel. There are not a lot of technical challenges, but rather challenges identifying what would be satisfying to most customers’ expectations. We are considering something like this with one of the future firmware updates: MIDI CH01 > CC1…CC80 to control the channel/bus Faders (0…127) MIDI Ch02 > CC1…CC80 to control the channel/bus Mutes (0,1) MIDI Ch03 > CC1…CC80 to control the channel/bus Pan (0…64…127) MIDI Ch01 > PCH > program change commands to recall scenes 1…100 (is already implemented) Equalizers have on/off state, 4-6 bands with 4 parameters each, so it’s a total of 17 or 25 parameters per channel. Multiplied by 40 channels and 25 buses we get a total of 1280 EQ parameters. This might be spread over a minimum of 10 different MIDI channels in a pretty obscure pattern … Considering the three channels we used up already, there would only remain 3 MIDI channels for all the rest you are looking to control. So, the classic continuous controller approach is obviously not very useful for this. Providing anything more than faders, pans, and mutes would only make sense with a comprehensive Sysex implementation. We are currently not convinced it is worth the effort creating a dedicated Sysex map, because OSC is much more powerful and it already exists. Thanks for your feedback. Best regards Joe Sanborn Manager, Channel Marketing MUSIC Group BEHRINGER [/QUOTE]

Verification