Wow, OK. I wasn't aware of those options. I'll have to do some reading. Thanks again!
- Gerry On Thu, Oct 16, 2014 at 7:29 PM, J. Liles <[email protected]> wrote: > Ah, yes. I use the index, vid, and pid options of the snd-usb-audio module > to ensure that all my USB MIDI devices get the same enumeration no matter > what order they are plugged in/initialized. > > On Wed, Oct 15, 2014 at 8:48 PM, Gerry Patterson <[email protected]> > wrote: > >> Hello, >> >> Sorry for the late reply, I ended up travelling for a bit. I found that >> using a2jmidid provided better named ports that when using Jack "raw" MIDI >> driver. This provided more consistent operation with jackpatch restoring >> the connections to the various devices upon session reload. Does that >> match your experience? Perhaps it is because a sometimes I plug MIDI >> devices into the computer in a different order. Jack was creating MIDI >> ports like MIDI_CONTROL_1, MIDI_CONTROL_2, MIDI_CONTROL_3.... Those >> weren't always the same thing so the patches would get miss-connected. >> With a2jmididd, the MIDI ports would be the device name so things would >> usually match up properly. >> >> I reported an issue <https://github.com/original-male/non/issues/141> in >> the tracker regarding receiving OSC messages in non-timeline. >> >> Thank-you and best regards, >> >> - Gerry >> >> On Thu, Oct 2, 2014 at 11:12 PM, J. Liles <[email protected]> wrote: >> >>> Yeah, you can if you want. It might be helpful if you share exactly the >>> controls you'd like to affect. >>> >>> a2jmidid should now longer be necessary (with recent improvements to >>> JACK's MIDI driver). I use 'raw' personally. >>> >>> On Thu, Oct 2, 2014 at 8:54 PM, Gerry Patterson <[email protected]> >>> wrote: >>> >>>> Hello, >>>> >>>> Thank you for the prompt reply! Should I file an issue? >>>> >>>> Is it recommended to use jack-midi 'seq' or 'raw' vs a2jmidid with >>>> non-midi-mapper? >>>> >>>> Thanks again, >>>> >>>> Gerry >>>> On Oct 1, 2014 11:03 PM, "J. Liles" <[email protected]> wrote: >>>> >>>>> >>>>> >>>>> On Wed, Oct 1, 2014 at 8:48 PM, Gerry Patterson < >>>>> [email protected]> wrote: >>>>> >>>>>> Hello, >>>>>> >>>>>> I have been fiddling attempting to get a Korg nanoKontrol2 working >>>>>> with the Non suite. First, I was able to get control of non-mixer >>>>>> (outside >>>>>> of NSM) using mididings as documented on the wiki. I then spent >>>>>> considerable amount of time trying to get things working inside of NSM. >>>>>> I >>>>>> eventually stumbled across a reference to non-midi-mapper which got >>>>>> things >>>>>> working. I was continuing to use mididings, but then abandoned it, in >>>>>> favor of the remote control learning functions. >>>>>> >>>>>> This controller also as a set of mute/solo/record buttons for each of >>>>>> the 8 tracks it has faders and knobs for. I have been able to map the >>>>>> mute >>>>>> button to the mute buttons on mixer strips, but the record and solo >>>>>> functionality seems to require sending OSC messages to non-timeline. >>>>>> This >>>>>> controller also has a set of transport controls that I am itching to make >>>>>> work as well... >>>>>> >>>>>> Does non-timeline support receiving OSC messages? If so, is there a >>>>>> list of example formats? I would expect I would have to use >>>>>> non-midi-mapper with mididings for these functions. >>>>>> >>>>>> Thank-you and best regards, >>>>>> >>>>>> - Gerry >>>>>> >>>>> Non Timeline doesn't currently support OSC control of those things. >>>>> But it's on my TODO list. And yes, you'd need to use the midi mapper for >>>>> it >>>>> then. >>>>> >>>>> >>>>> >>> >> >
