|
Avid Pro Audio CommunityHow to Join & Post • Community Terms of Use • Help Us Help YouKnowledge Base Search • Community Search • Learn & Support |
#1
|
|||
|
|||
Strange MIDI behavior in PT7.1
Hey, all.
I'm getting some very strange behavior when I do a drag 'n' drop of MIDI data into Pro Tools. So far this holds true with BFD and EZ Drummer groove libraries. I don't know if other MIDI data does the same. If I have a large MIDI region, say 20 or more bars, then drag 'n' drop, say, a 1-bar phrase into the middle I will usually get one of the following things happening: [*]Data is pasted, but all MIDI data following is deleted to the end of the original MIDI region. (Sometimes I can still "see" the MIDI data on the screen, but the background shading is gone and it's not really there... ) [*]Data is merged with the underlying MIDI data and all MIDI following deleted, as above.[*]Data is pasted, but all MIDI BEFORE is deleted from the original region.[*]Data is pasted, but RANDOM BARS of MIDI data deleted from the original region. I was running PT7.1cs5, and updated to PT7.1cs9 with no change in behavoir. Has anyone else seen this? Can anyone reproduce this? Is this a known issue with some system? My system particulars are: Pro Tools HD|2 v7.1cs5 (now cs9) Mac OSX 10.4.6 Dual 1GHz MDD "Blowhole" 1.75 GB RAM I have some screen captures to illustrate if this is not clear -- but I don't think there is a way to include them with a post here... Ray |
#2
|
||||
|
||||
Re: Strange MIDI behavior in PT7.1
Have you tried drag'n'drop the midi to a new track just above/below the track you're working on?
This is to see how drag'n'drop behaves with new tracks. Some applications, like Melodyne, exports the midi from bar 1 no matter where the audio starts in the session. This might be user-definable in Melodyne, but it doesn't matter to me. I never merge midi tracks. I figure if you import midi regions into both existing and new midi tracks you'll soon start to see a pattern of how PT behaves, eh?
__________________
Studio rig - Pro Tools|HDX 2018.7 | Logic Pro X.4.2 | Avid HD I/O (8x8x8) | 6-core 3.33 Westmere w/24GB RAM | OS 10.12.3 | D-Command ES | Eleven Rack | Vienna Ensemble Pro 5 Mobile rig - Macbook Pro i7 w/16GB RAM | UA Apollo 8p | Pro Tools|HD 2018.3 | Logic Pro X.4.2 | OS 10.12.6 |
#3
|
|||
|
|||
Re: Strange MIDI behavior in PT7.1
I've tried dropping the MIDI on a different track. It comes in where I drop it at approximately the proper length (*).
If I then drag it up onto the instrument track into the middle of the other region, I will get the same behavior. It does not always happen 100% of the time. While messing around trying to get a sense of what affects this, at some point, everything will start to work as expected. (*)I suspect it may have something to do with how PT treats MIDI files with no tempo and meter info, which a lot of these groove libraries remove due to differing behaviour in different hosts. I've noticed that PT will default to 4/4 for imported grooves, even if the session is in 3/4. A 3/4 MIDI region dragged in will come in at 4 beats regardless. The only way I've gotten this to work reliably is to first cut a hole the exact length in the existing MIDI region. Of course, this requires a whole bunch more steps to do what should only require one. Does no one else get this? Is it just some "miracle" of my particular system? Ray |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Global MIDI Offset strange behavior | Oroz | Pro Tools TDM Systems (Mac) | 1 | 02-02-2009 10:16 AM |
Strange Global Midi Offset Behavior | cc1 | Pro Tools TDM Systems (Mac) | 4 | 06-07-2007 07:21 PM |
Strange Midi Click behavior | davec | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Win) | 1 | 12-27-2005 07:05 PM |
strange midi behavior? Is it a bug? | Alex Rodriguez | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Mac) | 3 | 08-23-2004 07:53 AM |
Strange behavior | EdCastillo | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Mac) | 9 | 09-01-2000 11:46 PM |