|
|
Dec 3, 2008 at 3:03pm
recalling presets interrupts scheduler?
I’m doing some fairly simple step sequencer stuff, sending out midi sequences determined by a couple of matrixctrl objects and a few multisliders, which i can store in a preset object.
when I change sequence by recalling a different preset, the midi output is interrupted, and mistimes for a beat or so.
I’ve tried using pattrstorage, and if anything the glitch is worse.
Any ideas why this is, and how i can avoid it ?
|
|
|
Dec 3, 2008 at 7:04pm
can you post a simple example of what you are experiencing? Do you have Overdrive turned on?
-ben
|
|
|
Dec 4, 2008 at 12:51am
my bad…
simplified the patch and sure enough, preset was flushing some notes that shouldn’t have been flushed…….works fine now
just bought Max 5….the interface is great so far.
|
|
|
Dec 10, 2008 at 7:42pm
actually I still have a problem with this
this patch shows how using midi input to change a preset (that causes a few calculations to occur) causes notes to be output erratically, but using the computer keyboard doesn’t cause an interruption.
i have no idea why this is but its ruining my acid lines.
|
|
|
Dec 10, 2008 at 10:01pm
If I turn Overdrive on it works fine.
-A
|
|
|
Dec 10, 2008 at 10:21pm
Actually – I tell a lie, there does seem to be some kind of difference in performance between using the keyboard and using MIDI.
Perhaps there’s just too much going at high priority. Try putting a defer before the preset object.
-A
|
|
|
Dec 10, 2008 at 10:57pm
|
