separate ctlin and ctlout for two MIDI devices

Reply to separate ctlin and ctlout for two MIDI devices on Wed, 11 Mar 2015 12:50:35 GMT

narfnarf — Wed, 11 Mar 2015 12:50:35 GMT

Hello!

Is there a way to specify the which midi device sends/receives CC's via ctlin/ctlout? Using ctlin/ctlout currently sends/receives CC's on all devices, which is not very useful.

I'm trying to use two midi interfaces to translate MIDI from an external sequencer to a drum machine, and another from the drum machine to the sequencer.

Thanks!

Reply to separate ctlin and ctlout for two MIDI devices on Wed, 11 Mar 2015 14:03:41 GMT

alexandros — Wed, 11 Mar 2015 14:03:41 GMT

I guess you have to specify the device's channel... does the device send MIDI messages apart from receiving? Open [ctlin]'s help patch and check the device's channel and use that as the second argument to [ctlout] (first argument is controller number).

Reply to separate ctlin and ctlout for two MIDI devices on Wed, 11 Mar 2015 21:40:20 GMT

narfnarf — Wed, 11 Mar 2015 21:40:20 GMT

Hi Alexandros, thanks for your reply.

Yes, I can specify the channel, but as far as im concerned those midi channels don't determine which midi device will be utilized. Each midi device has an input and output.

Midiin/midiout do support a "port" setting, and that does control which midi device is utilized, but the this parameter is nonexistent in ctlin/ctlout objects.

The only way I can think of still being able to specify the device is to rewrite ctlin using midiin and specifying the device, but I'm new in PD and this might set me back a few weeks...

Reply to separate ctlin and ctlout for two MIDI devices on Wed, 11 Mar 2015 22:42:38 GMT

gsagostinho — Wed, 11 Mar 2015 22:42:38 GMT

@narfnarf Hi Narfnarf,

Have a look on this conversation from some years ago, it may help you with what you need (I didn't test it because I don't have more than one MIDI device to plug in on my computer): http://lists.puredata.info/pipermail/pd-list/2010-10/083853.html

Cheers!
Gilberto

Reply to separate ctlin and ctlout for two MIDI devices on Wed, 11 Mar 2015 23:27:10 GMT

narfnarf — Wed, 11 Mar 2015 23:27:10 GMT

Gilberto!

According to that post I should be able to address the additional midi device by specifying its midi channel + 16. (16 being the midi channels from the 1st device.

I will try this solution when I get home and report back to the forum with my findings. BTW, in running off raspberry pi. I read somewhere that other OS's might not support multiple midi devices. Just wanted to throw that out there for anyone looking for a similar solution.

Thank you!

Reply to separate ctlin and ctlout for two MIDI devices on Wed, 11 Mar 2015 23:29:58 GMT

gsagostinho — Wed, 11 Mar 2015 23:29:58 GMT

According to that post I should be able to address the additional midi device by specifying its midi channel + 16

That's exactly why I sent this to you, but I had no means of testing it.

I will try this solution when I get home and report back to the forum with my findings

That would be highly appreciated!

Good luck and take care!
Gilberto

Reply to separate ctlin and ctlout for two MIDI devices on Thu, 12 Mar 2015 03:51:50 GMT

narfnarf — Thu, 12 Mar 2015 03:51:50 GMT

OK, some good news and bad... But maybe there is a workaround I'm not aware of.

The good news: When specifying channel 17 the 2nd midi device is indeed used on channel 1.

The bad news is that in order to specify a midi channel, you have to provide an argument for the cc# first, which forces you to ignore all other cc#'s. ...unless someone knows how to specify the channel without specifying the cc#?

Reply to separate ctlin and ctlout for two MIDI devices on Thu, 12 Mar 2015 07:32:13 GMT

bang — Thu, 12 Mar 2015 07:32:13 GMT

hi, you could try [ctlin} like this:

Reply to separate ctlin and ctlout for two MIDI devices on Mon, 24 Jul 2017 12:30:05 GMT

weightless — Mon, 24 Jul 2017 12:30:05 GMT

I needed something similar so I patched this abstraction for doing that.

cc.zip

Reply to separate ctlin and ctlout for two MIDI devices on Tue, 25 Jul 2017 02:55:43 GMT

NoDSP — Tue, 25 Jul 2017 02:55:43 GMT

@weightless That's interesting. I almost but do not quite understand that patch. Perhaps it is because I do not understand the specific use case.

The O.P. seems to be talking about translating controller messages in a real-time sequencing environment. For that I tend to leave out as much calculation as possible and just use a single route object with all the ports/controller I need to filter the midin and 3 element list substitution to program the output objects.

Reply to separate ctlin and ctlout for two MIDI devices on Tue, 25 Jul 2017 07:19:56 GMT

weightless — Tue, 25 Jul 2017 07:19:56 GMT

@NoDSP This was in relation to post #7. By using [ctlin] you can specify just the cc# in the argument, but you can't specify just the midi channel. The purpose of this was to be able to get all cc# on one particular midi channel, or just one cc depending on what arguments you provide.

Reply to separate ctlin and ctlout for two MIDI devices on Tue, 25 Jul 2017 13:16:28 GMT

NoDSP — Tue, 25 Jul 2017 13:16:28 GMT

@weightless Ah, I see. My method for that has always been to break out all the separate channels I need with the first route (ie [route 1 2 3]) then use the individual outputs to more route objects with the desired controller numbers for each channel. Keeps it tight.

Reply to separate ctlin and ctlout for two MIDI devices on Tue, 25 Jul 2017 15:45:36 GMT

orangepickle — Tue, 25 Jul 2017 15:45:36 GMT

I had the same problem, I used spigots:

Reply to separate ctlin and ctlout for two MIDI devices on Sun, 27 Aug 2023 09:40:12 GMT

gazzyjuruj — Sun, 27 Aug 2023 09:40:12 GMT

maybe you can use comport and define different channels? but that's for hardware stuff i guess..