I suspect that you are right that Sonar disables FL Studio but then again there may be a way to go around all that.
I'm not sure what you're trying to show me, that's just a Google search. Sonar allows you to give a plugin keyboard focus but that doesn't work in FL's case.
Either way FL is running inside of Sonar, so Sonar determines whether it gets access to the keyboard. Other then that working them together is a dream having the best of both worlds,mostly I'll do some work in fl studio getting all the setup stuff and some of the idea for the track started in fl then open fl as vsti in sonar and go from there,this seems to work the best because as I've said sonar will take a lot of the hot key functions away and starting fl in sonar empty y it youill see what I mean.fl shines at midi programming but falls short in a lot of audio editing areas not that it can't just sonar dose in two clicks what fl takes 8 clicks,in some cases automation is also easier in sonar for similar reasons yet fl automation is hands down the more flexible but can become very disorganized if your not careful about your color coding and or naming everything as you go.automation is really purely situational depending on what you need.įidelityMusic I have two monitors myself, but that's not any different from using one monitor and locking a program to one half and the other program to another half. Fl studio is much better used as a vsti more stable and Easier to get things routed,downsides include no routing audio from sonar to fl studio and many of the keyboard keys are given to sonar "only" so if your accustomed to using hot keys in fl studio for speed this will probably become a issue fast.
0 kommentar(er)
