Badges [ 7 ] [-]
Memberships [ 1 ] [+]
Activity Stream [+]
Ideas Contributed [ 25 ] [+]
Improve easy-of-use when moving or copying a plug-in from a track to another with a different number of channels: - if the destination track have fewer channels, automatically convert the plug-in format, for example: - when moving from a stereo to a mono track, convert "multichannel" to "mono" or "multi-mono" to "mono" (in this case keep Left settings, drop right settings -- or even ask which channel settings to keep) ...more »
Add these options when right-clicking a track or a selection of multiple tracks:
- Add to Group > [show group list, highlighting groups already assigned to the track(s)];
- Remove from Group > [show groups currently assigned to this track] – this is greyed out if the track(s) hasn't been assigned to any group.
The video window occasionally goes on background if it's resized. The only workaround to make it appear again is unmaximizing the Pro Tools main window, moving it until the video appears behind, clicking on the video to bring it back on top, and then maximizing the Pro Tools main window again.
Add this option in Preferences: "Save and recall session-related playback engine settings" so that session-related engine settings such as Disk cache size, Video engine enable/disable are loaded and saved as a session-specific setting. More general or unrelated settings such as Playback device, Ignore errors during playback/record, Dynamic plug-in processing would not be loaded. This would help since: - the optimal ...more »
Several marker lanes would be very useful to organize and discern different sets and type of markers. A specific marker lane (like the "arrangement track" in Logic) can be used to delimitate song sections (verse, chorus, bridge, etc) and can have specific characteristics: markers in this lane should be contiguous time ranges and their boundaries should be draggable; they should be renamed by double-clicking the range. ...more »
Midi continuous controllers (CC) are not correctly read in Pro Tools 12.7. When different parts of the timeline are played back with different CC values, these values are updated only if breakpoints are encountered. As a result, when playing back a different position with different CC values, these values will be read and updated only when a redundant breakpoint is placed or if some CC automation is encountered through ...more »
When the Click II plug-in is present in a session, random CPU spikes occur, even if it averages at 0-1%. This cause frequent and systematic interruptions during both recording and playback.
The problem disappears when removing it or making the click track inactive.
Observed on Pro Tools 12.5 running on Windows 10 build 10586.
This option could be added in the Open session dialog as a checkbox. While selected, the session is opened with all plug-ins in inactive state. This may be desirable to have a quick look to the session content without waiting minutes to have the plug-ins loaded. It would be a good idea to mark the session state as "opened with disabled plugins" somewhere and give the user the possibility, when closing the session, ...more »
It seems that the Pro Tools interface still does not scale on Windows when setting a 125% scaling or greater. This makes it almost unusable on high display density displays.
Since track name boxes are now larger in the Edit view - and it is possible to assign longer names without having them clipped - the font width could stretch accordingly in the Mix view, when necessary, to accommodate the extra text length now available.
Clip gain value is normally shown in the left-lower corner of each clip. This happens when no clip gain breakpoints are present in the audio clip; otherwise, no value is shown.
Unfortunately, any value is shown in Windows systems in any case.
I observed this in Windows 7, 8, 10; Pro Tools 10, 11 (I have not tested PT12 yet).
When a real-time Bounce to Disk ends prematurely because of any error (90% of the cases are CPU spikes that stop it in random points), don't delete it, letting the user running another bounce from the point it stopped! Realtime bounces are still needed when passing through analog hardware. I'm using Pro Tools since 2004, and since then I had the problem of bounces stopping randomly; so I find myself running smaller, ...more »