|
Avid Pro Audio CommunityHow to Join & Post • Community Terms of Use • Help Us Help YouKnowledge Base Search • Community Search • Learn & Support |
#1
|
|||
|
|||
Consolidate Muted Midi Region = Deleted Midi Events
Like the subject says, when I consolidate a muted midi region, all events within the selection are deleted. Is this a bug?
PS, Why am I dealing with muted midi regions in the first place? Well how else am I supposed to export an individual midi track? Grrr.
__________________
2.8 Ghz (8-Core) Mac Pro 8 Gigs Ram PTLE 8.0 |
#2
|
|||
|
|||
Re: Consolidate Muted Midi Region = Deleted Midi Events
Quote:
__________________
MacPro3ghz, 6GB, 10.7.5, PT10.3.2, Digi002 factory/toolkit2/PTIEP, 11R |
#3
|
|||
|
|||
Re: Consolidate Muted Midi Region = Deleted Midi Events
Funny, I remember doing just that and not getting the results I wanted. Now I am. I think you fixed it!
But still there's something fishy with the consolidating muted midi regions. Try it if you can and see if you get the same result. (empty region) thx
__________________
2.8 Ghz (8-Core) Mac Pro 8 Gigs Ram PTLE 8.0 |
#4
|
|||
|
|||
Re: Consolidate Muted Midi Region = Deleted Midi Events
Oh and flommer,
Do you know how to retain channel info when exporting? If I export only the drums the GM file doesn't know its a mapped drum track.
__________________
2.8 Ghz (8-Core) Mac Pro 8 Gigs Ram PTLE 8.0 |
#5
|
|||
|
|||
Re: Consolidate Muted Midi Region = Deleted Midi Events
Quote:
Quote:
filosofem |
#6
|
|||
|
|||
Re: Consolidate Muted Midi Region = Deleted Midi Events
As per filo, yes it does delete all the events in a muted region when consolidating.. Don't know why that is a good thing..
But it suggests that there must be an alternate workflow for what you are trying to accomplish, so explain that in better detail... Why are you muting regions? Just for exporting regions? In that case, I don't know why you would be consolidating first.. I did notice that if you consolidate with MIDI MUTE automation, the notes are retained.. Not the same though, huh.. From the manual: Quote:
When dragging the .mid back into PT, it is hard to tell what the channel assignment is, because you have to assign a device first anyway, then pick a CH (from the MIDI output dropdown menu)
__________________
MacPro3ghz, 6GB, 10.7.5, PT10.3.2, Digi002 factory/toolkit2/PTIEP, 11R Last edited by flommer; 11-11-2009 at 11:33 AM. Reason: changed exporting to consolidating in the first line |
#7
|
|||
|
|||
Re: Consolidate Muted Midi Region = Deleted Midi Events
The same reason you consolidate audio, flommer.
filosofem |
#8
|
|||
|
|||
Re: Consolidate Muted Midi Region = Deleted Midi Events
The reasons for consolidating audio, as far as I know would be:
To simplify.. To create a single region that starts at 0 to ease importing into a new session or different DAW... I can understand the first, as far as MIDI goes.. In this case, I guess yes, if you have a MIDI region muted it means you don't need it's notes.. The second, however, seems unnecessary because when exporting a MIDI track, it automatically starts at zero and "consolidates" to a single MIDI "region".. If you see what I mean. Am I leaving something out?
__________________
MacPro3ghz, 6GB, 10.7.5, PT10.3.2, Digi002 factory/toolkit2/PTIEP, 11R |
#9
|
|||
|
|||
Re: Consolidate Muted Midi Region = Deleted Midi Events
For my purposes I am creating midis that line up EXACTLY with wav files. When I export midi files the midi file will begin from the first region. If my region begins 3 seconds in then the first 3 seconds of silence will not be retained in the export UNLESS I consolidate the region to include the 3 second silence.
As far as retaining channel info - I did the same thing with my drums and I got an organ sound. Are you saying that I should assign my midi drums track to a "Predefined" channel 10? A Digi port? My Keystation 61? I'm not really using sounds, this is purely visual editing so playback is not that important. However I could see myself wanting to monitor a melody with Mini Grand but assigning it to channel 7. How would this be accomplished?
__________________
2.8 Ghz (8-Core) Mac Pro 8 Gigs Ram PTLE 8.0 |
#10
|
|||
|
|||
Re: Consolidate Muted Midi Region = Deleted Midi Events
Quote:
Quote:
Assign the output to prefefined port 2 > CH10 (or similar), then right-click and choose MiniGrand CH 1. This assigns the MIDI output to 2 different destinations and it did retain CH 10 as the output when playing in QT. I'm not sure how this would go down with and INSt track.. And I'm guessing that you need to assign the CH10 output first...
__________________
MacPro3ghz, 6GB, 10.7.5, PT10.3.2, Digi002 factory/toolkit2/PTIEP, 11R |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
MIDI Volume or Velocity Change results in part muted MIDI sound | gavriil1 | Pro Tools 10 | 2 | 07-01-2013 10:23 AM |
Randomise MIDI events | crazy_ow | Pro Tools TDM Systems (Mac) | 0 | 06-11-2013 11:37 AM |
How To Get Rid Of Unwanted Midi Events? | Stixntrixx | MIDI | 2 | 09-20-2012 10:40 AM |
Midi note events extended beyond region | DonaldM | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Win) | 4 | 11-19-2007 06:53 PM |
thinned midi events?!!!! | tritonkorg | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Win) | 1 | 03-09-2007 08:08 PM |