Midi Users Response to PT12

[take77]

Hi,
I'm starting this thread so that info can be garnered on the Midi users experience with PT12.
Particularly those who have requested a bug fix for the Midi merge/sustain pedal "double note" bug.
I haven't encountered this yet but thought I'd start a thread for those who are still requesting bug fixes in the Midi dept.
Just want to see if PT 12 is satisfying those users better.

[25ghosts]

I have not been able to manifest any changes in Midi.

That does NOT mean that none are present. But I have not been able to detect them.

[dr_daw]

Originally Posted by take77

Hi,

I'm starting this thread so that info can be garnered on the midi users experience with PT12.

Just wondering if there are any improvements or new issues to be advised of?

If any are noticed during this time of initial release, please post them here.



For my part, I have not yet claimed my upgrade and would like to monitor the response of PT12 users for a time before I do so.



Thanks for your feedback.

What is the capacity that you're using MIDI at this time? I'm about to dive into installing the Air package and see what kind of demon lurks. As it stands, aside from a different 'quick start' dialogue, PT 12 is PT 11 with the promise of new features.

I'll be testing sessions that have both midi and audio (albeit, I will need to mute the bounced down audio and reinstate the midi data, as I do not keep midi going once I'm happy with the sound. You're just asking for trouble otherwise, regardless of DAWs)

[Southsidemusic]

Well we use LOADS of VI and midi programming and can say it is exacly like PT11HD in regards to midi features, nothing new, nothing lost. Same and working well for us.

[take77]

Originally Posted by Southsidemusic

Well we use LOADS of VI and midi programming and can say it is exactly like PT11HD in regards to midi features, nothing new, nothing lost. Same and working well for us.

OK Thanks.
I now understand it is primarily the addition of new features and not so much a re-write of any code.

[take77]

Originally Posted by dr_daw

What is the capacity that you're using MIDI at this time? I'm about to dive into installing the Air package and see what kind of demon lurks. As it stands, aside from a different 'quick start' dialogue, PT 12 is PT 11 with the promise of new features.

I'll be testing sessions that have both midi and audio (albeit, I will need to mute the bounced down audio and reinstate the midi data, as I do not keep midi going once I'm happy with the sound. You're just asking for trouble otherwise, regardless of DAWs)

I've had PT 11 for just over a month and completed two exclusive midi demos with no production impediments.
Full on VI use and editing.
Nothing that stands in the way of attaining a finished project anyway.

It sounds like the midi functionality remains the same so perhaps I'll do the upgrade to 12.

[take77]

Originally Posted by 25ghosts

I have not been able to manifest any changes in Midi.

That does NOT mean that none are present. But I have not been able to detect them.

Thanks for the reply.
The project I'm working on is my own and not for a professional client so no risk taken.
Sounds like I can just open it in 12 and resume work.

[take77]

Good question

[K.I.]

Hi.

triggerv1.1.2 of stevenslatedrums doesn't receive Midi in PT12.
It's no problem in PT11.

[Chingy]

While you CAN complete MIDI-based projects in PT, there are many threads around desired improvements (especially compared to the MIDI editors of Cubase and Logic). Sadly, it doesn't seem AVID is listening or interested.