An error occurred while saving the commentAnonymous commented
Changing the track height by mapping it to a hot Key is completely different than what I have in mind. If you have polywav file with 12 audio tracks and decide you want an L cut, now you have 24 audio tracks plus any music, VO and sound effects. Very very messy and slow.
Take a look at what FCPx is doing. Light years ahead on this particular issue of collapsing and expanding multi track audioAnonymous shared this idea ·
While we are not considering removing this long-requested feature, we hear you on the room for improvement.
Thank you for your feedback
As Wes noted, we are looking at many areas for optimization and have made strides in the last few releases already.
We recognize there are still many areas to improve performance and we are investing in appropriate areas.
Threads that are catch-alls are often non-actionable. Please keep giving us specific feedback on what workflows are slow for you.
Technical solutions may not always be as obvious as some people may be suggesting as the application architecture is often very different than people’s conception.
Short answer. Yes, we want to and will make it faster.