What channel / which cc are used? #3
Replies: 4 comments 1 reply
-
I figured it out. Many thanks. Success and new great ideas. |
Beta Was this translation helpful? Give feedback.
-
I'm having difficulty getting full use of MIDI CCs. If I specify 0x0, and then the proposed CC number in z_config:
I can use CCs to control them. But if I do the same for the ADSR controls, nothing happens:
Is it possible to access all parameters on a given channel simply using incoming CCs? Are there docs that explain Synth_SetRotary and Synth_SetSlider? Why does rotary or slider matter? Can I just bypass that and send only the CC number and value somewhere? |
Beta Was this translation helpful? Give feedback.
-
oh, that's perfect! I look forward to playing around with this.
…On Sun, Jan 28, 2024 at 3:02 AM Marcel ***@***.***> wrote:
Hey,
it doesn't matter if it is rotary or slider. I just used these functions
to get a better overview when working with a specific controller. The map
would be enough using direct callback functions. In some cases you would
like to avoid writing a function for each features.
At the moment there is a callback for raw messages ref.
https://github.com/marcel-licence/ML_SynthTools/blob/main/src/midi_interface.h
line 177.
You could check the bytes to detect the CC messages and process them.
Hope this helps.
—
Reply to this email directly, view it on GitHub
<#3 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIUOOHKXCIBV7ZLFCRHV7MLYQYV3ZAVCNFSM4YXCEBBKU5DIOJSWCZC7NNSXTOKENFZWG5LTONUW63SDN5WW2ZLOOQ5TQMRXGA3DGOA>
.
You are receiving this because you commented.Message ID:
<marcel-licence/esp32_basic_synth/repo-discussions/3/comments/8270638@
github.com>
|
Beta Was this translation helpful? Give feedback.
-
...and thank you... Forgive my manners.
…On Mon, Jan 29, 2024 at 12:43 AM Coatsie Coates ***@***.***> wrote:
oh, that's perfect! I look forward to playing around with this.
On Sun, Jan 28, 2024 at 3:02 AM Marcel ***@***.***> wrote:
> Hey,
> it doesn't matter if it is rotary or slider. I just used these functions
> to get a better overview when working with a specific controller. The map
> would be enough using direct callback functions. In some cases you would
> like to avoid writing a function for each features.
>
> At the moment there is a callback for raw messages ref.
> https://github.com/marcel-licence/ML_SynthTools/blob/main/src/midi_interface.h
> line 177.
>
> You could check the bytes to detect the CC messages and process them.
>
> Hope this helps.
>
> —
> Reply to this email directly, view it on GitHub
> <#3 (reply in thread)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AIUOOHKXCIBV7ZLFCRHV7MLYQYV3ZAVCNFSM4YXCEBBKU5DIOJSWCZC7NNSXTOKENFZWG5LTONUW63SDN5WW2ZLOOQ5TQMRXGA3DGOA>
> .
> You are receiving this because you commented.Message ID:
> <marcel-licence/esp32_basic_synth/repo-discussions/3/comments/8270638@
> github.com>
>
|
Beta Was this translation helpful? Give feedback.
-
Playing notes are possible on all channels. There is no check implemented
-> ref. void HandleShortMsg(uint8_t *data)
Changing parameters are associated to the contol change message (0xb0):
-> ref. void Midi_ControlChange(uint8_t channel, uint8_t data1, uint8_t data2)
Because I had a weird setup of my midi controller the mapping is a bit strange.
You can adopt the implementation for your own needs by calling:
when using specific messages. Data1 refers to the cc you want to use. Data2 is the value transmitted by your controller.
Beta Was this translation helpful? Give feedback.
All reactions