I think I have found a bug.
A subpatch, assigned a midichannel (other than ch1) in it's settings (eg. "2") will receive the control messages on the assigned channel when run standalone, but not when run as a subpatch.
Anyone experience or ideas with this?
When I set the subpatch channel to 1 the CC messages arrive, when I set it to anything else, it no longer works. So it's not the device (external, Novatin LaunchControl on the USB, works like a charm on other cases)
Thanks!
K
rereading your post i think i know what is going on. you have to open the subpatch when you have it inserted in your main patch. then go to EDIT->Settings and make sure you enable "has midi selector" in the appearing dialog. that way you can specify in the main patch GUI to which channel and device a subpatch reacts. this is useful because you can now load multiple times the same subpatch and set it to different channels for example...
Hey @lokki,
I have the selector in place already. I tried all possible combinations of device / channel / port. Notes work, CCs don't...
K
can you post a patch that exhibits the problem so i can try here? maybe one of the midi/in/cc objects has a bug? (there are several to try)
as a workaround you can try this patch:
dynmidichannelcc.axp (2.2 KB)
it has a midi/cc object, where you can adjust the channel at runtime. this is not really recommended, but you can test if it works with this object to debug further.
Ok, partially solved by cleaning out the patch to make a test for this post...
actually the "parameter on parent" dials are not updated which made me believe there was no change.
First I noted that if I directly assign a CC on the subobject on the parent patch, it works, even with the correct channel
So this is a cumbersome but working solution
Then I noted a discrepancy between the setting on the patch and the settings from the menu
Further exploration exposed that it actually works, but the dials on the parent are not updated. So I must have gotten the discrepancy problem combined with the dials not being updated which made me conclude it did not work. Still this sounds like a bug
Patch in attachment for verification
Thanks for helping out!
K
CCtestsub.axs (1.4 KB)
CCtest.axp (3.6 KB)
yes, i would think of that as a feature rather then a bug. you assign cc's only in the main patch, because that is what you will see when you open it up.
but i agree it is not fully intuitive... 
glad you got it "working"
the settings in the menu are overriden by the selector, so no need to worry about those.
If you want to use cc inside subpatches and have them channel dependant, this object here works fine.
midi/in/cc
You wont be able to see the knobs, like you would in the way you are trying. BUT, you can always make a display in the main patch to see what is going on. Something like this:
Thanks,
This get's me a long way.
What is the "midiport" actually?
How is it different from the channel? I noticed I can break things touching it
K
Actually I dont know. I would have thought it would be the same as midi device, but since we have midi device on Axoloti I am not sure what the port is for. Personally I just leave it at omni. As far as I remember I didnt have any problems with that
I want several instances of a subpatch in a main patch. If I pre-assign all the controls, and just have to change the channel per instance, this is a big timesaver as my midicontroller has "pages" with the same hardware buttons to the same CCs, but with a different channel
K
Well, everything in the main patch is only assignable to ONE channel. All dials represented in the main channel, even though they are located on a subpatch, which is assigned to another channel, they will we assigned to the main patch channel.
If you want several channels, I think the way to go is doing it the way I suggested. Then you can, as you describe, simply just copy the subpatch and change the midi channel and you have another setup on a another channel.
midiport refers to devices that have more than one port, i.e. some usb-midi synths or controllers. essentially this allows to send on more then 16 channels from those devices.
Nice to know
Dont have any devices with more than one port, so never needed to take that into consideration.
