Midi question - probably a stupid one

A place for developers to share ideas and assist each other in solving problems.

Moderators: valis, garyb

Post Reply
manfriday
Posts: 234
Joined: Tue Jan 09, 2007 5:41 am
Location: St. Charles, IL

Midi question - probably a stupid one

Post by manfriday »

Im pretty new to the SDK, and someone asked me about making a simple device to allow only specified CC's while blocking all others.
It seemed pretty simple, and I used a module Byte2Extract module to accomplish it.
However, It seems not all the values are getting picked up by the byte2extract module. Some get dropped, and it depends on how quickly the values are sent.
I guess it makes sense as the midi stuff is mostly asynchrnous, right?
I am just wondering if there is a way to improve the responsiveness of the module, or if it's just the cost of doing business in the asynchronous midi realm?

thanks!
User avatar
Shroomz~>
Posts: 5669
Joined: Wed Feb 23, 2005 4:00 pm
Location: The Blue Shadows

Post by Shroomz~> »

I think some midi values being dropped when sent quickly is to be expected from midi controller (CC) data in general. It's not a fast or high resolution spec, so it just can't cope properly with fast manipulations. Bring on the NRPN support !! :D
Post Reply