Protools midi sequencer

[Paul Nelson]

Will the midi sequencer in Protools ever be upgraded?
I currently use logic but would use protools sequencer more
if I could do step time programming and use an arpegiator.
Simple to do I'd think.

[NuBus]

How about Midi Scrub!!!!

I've been doing that since the 80's

[Paul Nelson]

Exactly! I was a performer usr since version1.2. After using performer and logic and protools
I"m confused as to why features and functions we've been using for close to
20 years is not available on this "post millenium state of the art product"!

[PTUser NYC]

Before they add more MIDI features, I'd like to see it simply get tighter.

If you record a simple MIDI Kick Snare eighth note type groove (Kick = dotted quarter, eighth, half note, snare on 2 & 4, 8ths an the hat), quantize it, and listen to it, you can feel that it isn't anywhere near as tight as, say, an MPC60.

Take a kick, snare and hat sample, put the audio regions on the beats, and build the same groove - much tighter now, isn't it?

I realize that there are all kind of delays in synthesizers and MIDI, but what about this?

When I slave Reason 2.5 to Pro Tools 5.1.3cs5 via MTC, I can see Reason chaning tempo wildly to follow the discrepancies. Sure, its CLOSE, but compare that to the same Reason Track bounced as audio and imported into Pro Tools, and the difference is staggering.

Audio is TIGHT on Pro Tools, MIDI has too much slop. Whats the point of advanced groove quantize, if the tempo is gonna drift so bad?

[Dr Fletch]

Yeah and another thing! Because of Pro Tools' inadequecy in the midi domain, I use Cubase (used to be Studio Vision Pro, those were the days) and lock the two macs with MTC. Not bad, but ok sync.

NOW, I've upped it to 6.4. OSX.3.4 Using ProTools as master it's fine, but when ProTools is the slave...It can wander alarmingly!!!

me?

the price of progress