I KNOW that if you wanted to mute a part, then ideally you would just cut the region. If I have to be the one to inform you, then you should be upset with your DAW’s developer, and not with me. No matter what design decisions they make, you should be informed. The software or developer should tell you what’s happening. 4.5.1 has much smaller transition time and less noise. Look at Studio One for why this is so important! There are now 3 versions of the software that will render your project differently if you have automation in the project! 4.1.4 has the (very mildly) noise automation that’s fairly quick. Even if you don’t mind the fades, it should matter that the fades aren’t specified or shown. You should absolutely be concerned if your product does something other than what it shows you for a function as important of automation. I’ve had numerous responses from people saying that would do it another way, or that they’re ok with the fade, or that they’d just edit the clip, or… various things dismissing their product’s inability to show them what it’s doing accurately. I wanted to know if what you see is what you get with fader automation. Probably because I ass-u-me-d that certain aspects of the testing were implicitly obvious. Please join me as I explore these facets and see more about how automation differs between products.īefore we start, it seems that some people didn’t understand the last article.
In the last series I explored DAW fader automation.
Spoiler Alert: Logic, No Sample Accurate Automation
0 kommentar(er)
