How Far Back To Go for Workable MIDI

[Steve@ZooWest]

Tried 12.5; fail. 12.4 - initially better, but still unusable once I got into it. Most common issue - stuck notes.

Ivory Piano seems to be the main culprit at the moment until it's committed; it's just that my workflow doesn't allow me to do that. Most everything is in flux until the bitter end.

Those on Windows 10, what previous version(s) are working reasonably well with midi for you? 11.3.2 has been mentioned a couple times...

Windows 10
PT 12.4

[JuanPC]

W7sp1
Hd12.3.1

W10 is officially supported in PT12.5 only.

Want to try 8.1 Pro, maybe later.

http://avid.force.com/pkb/articles/e...tibility-Chart

External midi timing depends, internal is flawless.

[nigelpry]

For the most stable rock solid MIDI performance on a computer ever ....

.... Steinberg's Pro24 or Cubase on the Atari ST, preferably the Mega4 model, and with Steinberg's MIDEX+ attached to provide 2xMIDI In, 4x MIDI Out, SMPTE in/out and 4x Dongle slots.

Those were the days ....

I've never, from day one of using Pro Tools (I started on 7.4), been happy with its MIDI functionality.

That's why I keep my Cubase up to date ;-)

[TOM@METRO]

True, Pro Tools MIDI is not up to what others have to offer. But let's keep hoping.

[JuanPC]

Here I have perfect Midi timing...
http://duc.avid.com/showthread.php?t=380434
Occasional Ghost Phantom notes in PT,... Not to worry.

[nigelpry]

Originally Posted by TOM@METRO

True, Pro Tools MIDI is not up to what others have to offer. But let's keep hoping.

Be assured, I do keep hoping, because I much prefer SOME aspects of PT's functionality and GUI to Cubase's. That's all that keeps me using PT.

For me, there are a few key areas of MIDI functionality that need augmenting, enhancing, improving etc.

Here are a few of my 'must haves' ...

1) A proper drum editor window, as much like Cubase's as possible, with drum maps, note naming, note in to note out translation, and the ability to set any note to send out on any midi channel to any midi port, so you can have a single cohesive drum map that triggers sounds from multiple hardware and VI drum sound sources.

2) Per midi channel and midi port CC maps, with CC number naming so that you can specify what each CC number is actually mapped to, which has to be on a per instrument basis (whether VI or hardware), hence why it needs to be per channel and port ... The same CC number often controls totally different parameters on different hardware and VIs.

3) Extend CC to cover ALL CC numbers and include RPN and NRPN.

4) An alternate solution for viewing automation as it happens other than automation lanes, e.g. Quick/smart control knobs, again defined per instrument, possibly by allowing instrument and MIDI tracks to have a second adjacent strip in the mix window.

5) Per instrument and global automation view presets, to make it easy to display combinations of automation lanes of your choosing.

6) Folder Tracks to help manage screen real estate used by all track types, especially handy when you want to have lots of automation lanes easily accessible.

7) The ability to seperate out and/duplicate automation lanes of your choosing into different folders, as presets, so that for example, you could have CCs for filter cutoff and resonance across all instruments visible within one folder.

8) A better Click plugin, with some of the old TL Metro features, such as the ability to allocate your own sounds, but able to set both sound and volume 'per beat', not just down beat and the rest, and able to cope with setting up more complex rhythms within an overall time signature.

9) MIDI Effects, insertable in MIDI and Instrument tracks as plugins .... On instrument tracks if you instantiate the VI say in Insert slot C, then slots A and B should be 'converted' to be MIDI effect slots, as they will modify midi data coming from the track's midi clip BEFORE the data reaches the VI. I haven't really thought through how we might want to deal with any MIDI data generated by the VI. Maybe a right click on any insert slot should allow switching it from a midi to audio fx slot and vice versa.

I have more, but the above would go a very long way to meeting my needs.

[john1192]

Watch Out for the Commit Bug .. if it is the last item in your Undo History it Will Crash Your System .. be careful .. there is a thread here at the DUC ..

[Stig Eliassen]

Well, I know MIDI Merge worked in 7.4.2.