FL is terrible for audio though so Reaper's a welcome change with vocals for me. I used some, but I wasn't crazy like some other people that I've seen. That being said, I didn't use a whole bunch of automation in FL.
If I can set things up so that it's faster than the base model then great. I look at what is providing me with the most efficiency rather than the perfect efficiency therefore, it's okay for some things like automation aren't perfect.
Cubase 9 pro vs mixcraft software#
It's not going to be out there, as it is with software in many different fields and not just with music. That being said, what I will say is I don't feel it's about finding the perfect DAW. Personally, I haven't worked a lot with automations in Reaper yet so I don't really know enough to comment on that part. I've found there are things I can do in Reaper that I can't do in other DAWs as well though. Studio One is my benchmark for this, Cubase is second. For an action so basic and so used, it should be as easy as it can get.
I vowed to only take a look at it again when they implement a similar system the the described above. No DAW is perfect, but that's what stopped me from using Reaper.
Cubase 9 pro vs mixcraft Patch#
That's when you start to think, is this DAW helping me, or am I trying to force myself to work against the rules of the DAW? I truly appreciate juliansader's work, but they try to patch something that I believe the DAW should have natively, and implemented consistently. I have to remember two completely different workflows for what should've been consistent in between the two.
Cubase 9 pro vs mixcraft update#
I have to remember to update the scripts. I have to remember that I can't force my mouse outside of the CC lane, because that terminates the script (though he is working on it). I have to remember the difference between automation and CCs. Have to map them to different keystrokes (I have used five of those scripts, so that's five (!) different buttons for what is one in the other DAWs). You have to download all kinds of different scripts for different operations. Even worse, I can't have the same workflow with CCs. Instead of two actions, of which one is a simple keystroke that you have to remember for both automation and CCs, you have to remember three for automation alone. But when that is the number one thing you do almost every time, it becomes worse. That's three steps instead of two by selecting and pressing T (which is how I have set it up in Studio One).
Can I compress automation in Reaper? Yup, but you need to change the automation to an automation item, then go into a menu (or map it to a button), then change the amplitude value with a slider. Yes, you can do that with automation, but the workflow is different, and frankly way more difficult. Except they only work on CCs, not on automation. Yes, you have juliansader's scripts for that in Reaper. One example is transforming CCs or automation in Studio One or Cubase for example. That is until you find workflows in other DAWs that are simply not possible in Reaper, workflows which can be approximated but it feels like trying to hammer in a tiny nail with a sledgehammer.
0 kommentar(er)
