Some Fx (like the chorus in a 100 % wet configuration) when activated drop the volume considerably. This poses a problem in keeping the mix consistence in live situations. It would be great to have a level control after each effect so one can compensate this.
I'd love to see the MIDI Event Operations window behavior changed so that the current track selection is active when the window is first opened. I'd like to be able to select a range of notes in the timeline, then open the Operations window to make adjustments to the selection without having to reselect the notes first. With the current behavior the Apply button is grayed out initially and only becomes active for notes ...more »
Compared to ProTools 10 the video engine playback delay is way to big. It is almost a second from hitting space to play.
That`s way to long for a professional HDX system in a professional studio on a new Mac Pro. Pro Tools 10 is instant playback. Really fast and flowing.
Please fix this or give us the option to work with the old quicktime engine when needed. Thanks
Like time stretch on audio for post/film conversions,
it would be lovely to do the same with all regarding automations.
For example stretch all automation within selection to chosen
post/film conversion preset, like 25fps to 24fps.
If you open a session that has a UAD2 plugin, and that plugin cannot be instantiated (say, you've run out of DSP horsepower on the card), then ProTools still thinks that the plugin is active, and applies the delay compensation. But of course, since there really is not a plugin active, the track has now been over-compensated, and thus plays too early. This is with the last iteration of PT 11. I have no clue if it's fixed ...more »
In Edit window a keyboard equivalent of the |< in the lower left corner that shows and hides the Tracks and Groups column on the left side of the edit screen. Same thing for CLIPS column on right side of edit window.
Avid have changed plugin mappings on the artist series controllers with EQIII and Chanel Strip beginning in protools 11 and on, that's all I've personally noticed; this might have happened with other Avid plugins as well! In protools 10 we'd have access to freq/gain/Q all on one page and now in 11 and up Q is only accessible when you hold down the shift key and touch the frequency knob or if your working in plugin flip ...more »
Add an option so you could swap out the Mini-Keyboard in the MIDI editor for the names of the drums. The word "Snare" is much more friendly than just seeing a piano keyboard on the left side of the editing area. Sonar has had this and you can edit and save different "drum maps" as it calls them which are only used for display purposes instead of images of piano keys. This way you can select a different list depending ...more »
Because gain staging is so important and many modern plugins are optimally designed for -18 to -12dBFS, it would be very nice to be able to quickly read from the mixer window the level either leaving or entering each insert position. Certain plugins, especially those used for saturation or eq boosts, can really boost the signal and cause clipping at the next insert I the chain. I frequently use trim plugins in between ...more »
I have a session that I made as a template. It has tracks that are assigned to two busses. If I open the template session, I see the double bussing as expected. When I import tracks from the template session into another session and have the "Output assignment" field checked in the import tracks menu, those tracks appear with only one bus routing path.
Make a complete menu in a vertical rack, with all MIDI windows, integrated and where everything is open and available (no pull-down menus, which make us waste time), especially in the MIDI editor. It would be a huge step forward. The features are there, but we need to facilitate accessibility. Currently, it is as if a carpenter had to open a drawer and close it to select each tool each time.
Currently, if we want to move more than one marker at the same time, copy and paste. We should be able to move more markers together.
It would be great if PT had a command that "shows only audio&midi tracks containing active data" at the cursor/playback position without having to create a custom memory location/group.
Additionally, a "show/hide or delete tracks with no active data" command would be helpful to keep things organized.
Score editor & Notation View both Crash with large sessions containing 512 midi tracks in PT 11. (Screenshot included)
AVID tech support was able to confirm this on their end.
Importing Session data from these large sessions also takes forever.
Also, it would be great if we could see the note names in the MIDI editor.
The Slate team logged this back in March. I'm very disappointed that this issue persists in PT12.1. This bug breaks compatibility with the Slate Raven console.
Products such as the Slate Raven and PreSonus Studio One V3 are demonstrating the potential of touchscreen manipulation of DAWs. The benefits far exceed control surface features. Though physical control surfaces are adequate for transport and fader functions, I have never had a satisfactory experience manipulating plugin parameters. With all the various 3rd party and stock plugins, it is impossible to assign a limited ...more »
It seems the only reason to cap ADC is to cater to the hardware limitations of HDX systems. In 2015 when no other competing DAW has to deal with this headache, why not remove the ADC limit for HD native and vanilla users?
When setting the gird to clips/markers PT will still take markers into account even when they are hidden. Leading to false snap to grid placements.
Please ignore the markers when the marker-track is hidden. Just like when you hide the audio tracks and the clips are not used for the grid.
When the mute button is engaged it currently mutesf the audio at the next zero point crossing (or so it seems). This still causes random pops and clicks and have to be manually checked and really disrupts the console workflow when muting with a controller. PLEASE, allow the user to set options of mute behavior. 1) Normal ... as is. 2) Fade In\Out time of mute. This way one can set the mute to actually fade out the ...more »