• narfnarf

    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#?

    posted in I/O hardware diyread more
  • narfnarf

    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!

    posted in I/O hardware diyread more
  • narfnarf

    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...

    posted in I/O hardware diyread more
  • narfnarf

    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!

    posted in I/O hardware diyread more
  • narfnarf

    Thanks! That make sense... I hadn't noticed those numbers being sent out but just checked the print output and they do!

    I'm sure I'll eventually find how to do it, but any pointers on how to filter midiin output with that criteria would be great... I'm guessing some sort of if statement..

    Thanks again

    posted in I/O hardware diyread more
  • narfnarf

    Hello!

    I have a hardware sequencer that does not transmit NRPN's, so I'm using PD to translate CC's going from the sequencer into NRPN's to external gear.

    I also need all the midi data coming from the sequencer such as clock, notes, other CC's, etc... This is why I'm using midiin --> midiout. My only gripe is that the CC's I'm using from my sequencer to modify the external NRPN's still get dumped into midiout.

    I've thought about skipping midiin-->midiout and instead routing all notes, midiclkin, ctlin... etc. individually, but I feel like that's major overkill.

    Does anyone know a better way to filter out CC's from incoming midi while allowing all other MIDI data through?

    Something like:

    [midi + cc1 + cc2] --in--> PD[-cc1] --out--> [midi + cc2]

    Thanks!

    posted in I/O hardware diyread more
  • narfnarf

    Thank you @pulsed -- I'm figuring it out, but honestly I never thought it would be so simple. This is awesome. My next challenge is to figure out how to run this on a raspberry pie headless, but that will be a different thread.

    posted in I/O hardware diyread more
  • narfnarf

    Awesome! Than you very much.

    posted in I/O hardware diyread more
  • narfnarf

    Hello,

    Has anyone tried to set up PD as a MIDI translator that will take an incoming MIDI CC value and output a Program change value?

    If so, can you provide a few tips--I'm a newbie.

    Thanks!

    posted in I/O hardware diyread more

Internal error.

Oops! Looks like something went wrong!