KVR Audio

dougsyo · Post by **dougsyo** » Thu Mar 19, 2009 4:18 pm

Maybe it can be done with vstlua as well.

Also, SuperMidiScripter.zip appears to really be a .rar file - it wouldn't open with Windows zip support, right-click and open with WinRar showed it to be a .rar file so I renamed it.

Doug

insertpizhere · Post by **insertpizhere** » Fri Mar 20, 2009 1:54 am

shamann wrote:I'd thought Mr. insertpiz might have something appropriate:

http://www.kvraudio.com/forum/viewtopic.php?t=192282

But I'm not sure any of those could drop channels in bulk.

midiChs_noGUI will do that. it can reroute channels, or if you set a channel to below 1 ("--"), it's blocked.

shamann · Post by **shamann** » Fri Mar 20, 2009 2:09 am

Thanks, good to know, it seemed like something you would have already covered.

insertpizhere · Post by **insertpizhere** » Fri Mar 20, 2009 2:35 am

runagate wrote:MidOx and MidiYoke are needlessly fiddly.
I use Usine, it reports midi messages right on it's main panel.

Also, acousmodules has a great6 midi monitor. I just have bad eyes, and the data flies by too fast.

have you tried my midi monitor? it will record basically an unlimited amount of data, and then you can scroll back up to see it. it's also resizable, so you can see more at once.

runagate · Post by **runagate** » Fri Mar 20, 2009 3:15 am

I love your resizable GUIs!

Problem is: no internet at home. So this is taking forever.
I did use your plug to record the midi (obviously I have all you and nic's but not the documentation necessarily) and it's... even more bizarre than I thought.

I even resorted to midiOx but can't understand the midi routing from the documentation... I think the "filter" I set up worked great, but I can't seem to interface this with the midi yoke to my DAWs... I think I need to make "maps" or somesuch. Ugh. The "pointless" pitchbend which gets sent on every chord change also all gets sent on the same channel as the pitchbend wheel, which is infuriating and I think might mean I simply have to not use PB at all on the device.

Thanks. I'll be back again

insertpizhere · Post by **insertpizhere** » Fri Mar 20, 2009 5:26 am

that is weird. the only thing i can think of is if the pitch bend messages on chord changes are large jumps and the ones from the wheel are in smaller steps, there could be a way to fix it. i would be interested to see a midi file of this thing's output...

runagate · Post by **runagate** » Fri Mar 20, 2009 6:39 am

will do

I certainly would like to make something that'd enable this device to work for others in the future

I paid $125 for it
Nothing else has a midi "strum plate" nor 84 chords

Contrariwise, the EWI just works as advertised. Suzuki, what in hell were you thinking? lol

runagate · Post by **runagate** » Fri Mar 20, 2009 7:34 pm

midi log

That's a download link to my attempt to capture midi-ox data (which failed) and record the output in FL, saved as a midi file.

SuperMidiScripter obviously would work but after 2 hours of trying to parse it I obviously am in over my head. I think it's beyond my ken

insertpizhere · Post by **insertpizhere** » Fri Mar 20, 2009 9:04 pm

ok, i see some center pitch bend (along with some other junk) at the beginning and end of the midi file, and some normal-looking pitch bend in the middle.

is it the stuff at the beginning and end that needs to be filtered out?

runagate · Post by **runagate** » Fri Mar 20, 2009 9:19 pm

insertpizhere wrote:ok, i see some center pitch bend (along with some other junk) at the beginning and end of the midi file, and some normal-looking pitch bend in the middle.

is it the stuff at the beginning and end that needs to be filtered out?

Woot! I'm getting wifi and I saw that you DLed the file so I came back to check.

Well, let's see. "center" pitchbend - that's smart. I didn't think of that. The random piles of PB come from changing chords with the "chord buttons" regardless of whether you are stumming the plate or not. You're correct that the "centered" PB messages are coming from the actual whell I was playing.

The EWI also sends "centered" PB messages from both the "bite sensor" in the mouthpiece and from the "up" and "down" thumb sensor plates - unless you reassign it to send midi CC#s.

Channel 10 always sends drum notes, no matter what. Which is idiotic.

QChord Manual wrote:MIDI Channel 3 - CHORD PLUS
MIDI Channel 5 - AUTO CHORD 1
MIDI Channel 6- AUTO CHORD 2
MIDI Channel 7- AUTO CHORD 3
MIDI Channel 8- AUTO CHORD 4
MIDI Channel 9 - BASS
MIDI Channel 10- DRUMS
MIDI Channel 14,15,16 - STRUMPLATE
Your MIDI device should have the ability to receive all MIDI channels or
to channel select to receive only the channels that you desire.

CC# 7, 61, 90 & 93... I think that these up/down arrow or dial controllers could come in handy. Looking at the captured data it seems that those CC's are sent only when you muck with the actual physical controls and not just arbitarily like some of the other junk. And in Midi-Ox there's a LOT of junk...

Prog Change: mostly an annoyance, though potentially useful to some users. I don't use this type of message so I'm not familiar with it's use in my DAWs.

It also sens Stystem :Clock and Realtime :Commands whatever the hell that is.

Now let me ask you this, and I think I've verified this but I'd like to be sure: If I keep just the channels 14, 15 & 16 it'll send all the relevant notes and I can just ignore the "chord plus" on channel 3 unless I for some reason don't want to use the "strum plate", correct?

Seems loony to me that 4 octaves of strum sensors get sent on 3 channels of midi. I'm thinking that I'll route all 3 of those to just one channel. That I know how to do without any problem.

runagate · Post by **runagate** » Fri Mar 20, 2009 9:29 pm

screenshot of QChord behavior in Midi-Ox

I can't seem to get any of the types of "log" to work in Midi-Ox, so here's a pic.

insertpizhere · Post by **insertpizhere** » Fri Mar 20, 2009 10:26 pm

i think midi-ox only logs its own output, not its input. so you have to route the input to some output within midi-ox to get anything to show in the log.

FL must be doing something weird when capturing or saving the midi file, because everything in it is on channel 1. therefore it's hard to say anything about how to filter the channels... also, the pitch bend in your midi-ox screenshot looks pretty weird, but i didn't see anything like that in the midi file.

runagate · Post by **runagate** » Fri Mar 20, 2009 11:06 pm

hmm I'll keep plugging away at it keeping hyour advice in mind

I figure once I hit on a solution I can keep it forever and pass it along to the next sucka

FL's channel thing... it's because you have to "prepare" it for midi export with a macro then export as a midi file. I'd forgotten about it reducing it all to channel 1. It's not as though all the midi info gets into FL anyways, it just ignores a lot of it.

/thinking cap on

runagate · Post by **runagate** » Mon Mar 23, 2009 10:04 pm

Oddly setting the midi channel to "--" in Usine has no discernable effect in Usine on any of my midi gear. Would setting everything to -- block all midi signals? It doesn't appear to be the case for me.

Optomadic · Post by **Optomadic** » Mon Mar 23, 2009 10:45 pm

insertpizhere wrote:FL must be doing something weird when capturing or saving the midi file, because everything in it is on channel 1. therefore it's hard to say anything about how to filter the channels...

Yea FL does add a bunch of nasty messages that you cannot turn off. Very annoying.

Suzuki QChord - help filtering the midi output into my DAW