blairell

ive been programming this sequencer that just sends out midi. its my 3rd or fourth big max patch.

im wondering why all the timing goes to hell when i drag a window in max. my cpu usage is only 1-2%, and yet a simple window drag makes it run horribly.

can anyone else identify with this or what might be the issue? thanks for any help.

ive been programming this sequencer that just sends out midi.  its my 3rd or fourth big max patch.

im wondering why all the timing goes to hell when i drag a window in max.  my cpu usage is only 1-2%, and yet a simple window drag makes it run horribly.

can anyone else identify with this or what might be the issue?  thanks for any help.


max-runs-slow-window-drag

kidding... run it in overdrive so window redraw is low-priority.

eventually you will want to run your clock from a phasor~ rather than a metro, but it sounds like you're getting the clock from Live anyway.

yeah. lives clock isn't the greatest. when it gets to 32 steps per bar i think my beats start sounding a little fuzzy. it could be my pathc but i dont think so with the testing ive done. need to figure out a way of generating another clock with phasor, but taking the tempo and start and stop messages from live's clock.

yeah.  lives clock isn't the greatest.  when it gets to 32 steps per bar i think my beats start sounding a little fuzzy.  it could be my pathc but i dont think so with the testing ive done.  need to figure out a way of generating another clock with phasor, but taking the tempo and start and stop messages from live's clock.


yeah, it's a combination of phasor~ and edge~ so edge bangs out the transition from rising to resetting of the wave (from peak at 1 back to 0). There's a lot of info on good audio-rate timing on the forums.

max runs slow - window drag