rewire~: queue stepped on itself ?
i received this error message while sending midi data to reason through the rewire~ object. what does it mean exactly and how might i avoid it? i assume it means that there was too much midi information being sent to reason at one time, so i was curious if there might be a way to filter my midi messages as to avoid this error from happening. how much should i filter? i assume this is like in max, when you need to flush the note out object, but i'm not sending midi info through noteout (using midi messages to [rewire~]) so im not sure how i could 'flush' this information. thanks for the help.
did not. hopefully a c74 guy will see this later today and can help out. i also contacted propellerhead about this; see what they say. I tried using a speedlim object to limit the midi info that got through - but at a speedlim value of 32nd notes at 100 BPM (75 ms), i still got the message after a rather short period of time. ive started sending my midi info through the computer's built in midi channels (maxMSP1, maxMSP2, IACDriver) but that only allows me 3 voices for midi, as opposed to the 65 available to me through the midi message to [rewire~]. but ive encountered no problems with midi through this method (since it's sent through a noteout object, one can always just 'flush').
my mistake :-D, you're right. i guess the midi message not working isn't such a problem then. i bet reason advises one to use rewire instead so that their program can handle the midi info (tho it clearly is ineffective at that).
great :-D glad to see this issue resolved.
two year bump! /using the work around.