Starise
To say " I don't miss Sonar" is probably a given no matter what you decide to do. If a person makes their mind up to use something else, they will no longer be concentrating on what they had before and they will use what they have.
Currently I run several instances of 4 different programming editors. And that is my usual working environment
Yes, BUT- Are you making music and tracking? Are you a musician? Programmer?
How many musicians develop 4 different programs in parallel?
I am a programmer. And I have no problem to work with different editors and so with different shortcuts, menus, compilation and run options.
I mean (pro) musicians also can use several DAWs (and according to this forum, some do).
I don't understand the comment " how far daws have come" when comparing Studio One to Sonar.
For that you have to try them..
@ Azslow3, I have the most recent copy of Studio One 3 professional. So I have tried them both.
I do not have S1. My DAW of choice is "far" in many aspects. Reading this forum, I assume S1 is also "far" (but owners keep most details in "secret")
There is DAW with weekly updates, some are significant and there can be intermediate updates with fixes. Report real bug - get it fixed next day.
Sonar has some advantages in the work-flow and offered functions (f.e. see the comparison I have mentioned before). But the list of functions it does not have compare to other is also not empty.
@Azslow3, I think there is a slight translation error here. If I understand this statement, which I think is saying that Sonar also leaves much to be desired.What do you want it to do that it doesn't do?
I want it react faster, replace MIDI engine with something "modern", make API working with features introduced in the last 10 yeas. But from everything else, I most tired by its endless list of MIDI related bugs (from input devices, throw timing up to control surfaces API). Also I have a philosophical wish my DAW is accessible.
Try to start some "other" DAW on old computer and then again Sonar. The difference in performance will be obvious.
Also working with Sonar, I have learned never modify the project structure while transport is not stopped. In "other DAW" I can make new project, press "Play"/"Record" and build the whole project without completely stopping it(add tracks, FXes, Synthes, record parts, etc.). I will call that a "stress test" for gapless audio engine.
(do not try to enable "allow record arm with working transport" in Sonar, there was a thread about that... you can get your SSD filled quickly )
I think this is a great feature to have. I would ask, how many things does the average user do at once?
To make it clear. For me, any DAW is just a hobby "music instrument". When I play my DP, I do not have to think "before I switch to EP I should not forget to stop accompaniment and release all keys, otherwise it will crash or get notes stuck". I want the same from the DAW, drop new synth or effect without thinking much about technical details, preferably from controller. I am 2m away from the keyboard when I sit near my keys/drums/guitars, I do not even see the monitor (so I have some benefits from accessibility, when married with controller).
At work, I was sometimes loading everything I need into 100GB RAM disk (on 128GB RAM server... SSDs have solved the problem), waiting 5min till the program compiles after small change is absolute "no go". So the DAW reaction speed has value for me.
I would not mix "work arounds" and alternative ways. The first is lengthy replacement for something not working. The second is different approach.
You can cut it any way you want. If I have a client and they nave an Mp4 track I need to find a work around in Studio One. So neither is immune to it.
Not that I need it, but from what I know, my DAW of choice support any format... And if something is not yet supported, it is easy to add (yes, I am a programmer... it was not supporting Sonar projects, so I have added that
)
My answer for using Sonar is simple really. I know how to do everything in it in half the time it would take me to do it in something else. As long as it is kept the way it is I see no reason to change that. After resizing a few graphic blocks around on two monitors I have it the way I like it, usually with console view on the second monitor.One keystroke hides all the things I don't need to see while mixing. It doesn't get any better than that for me in mixing really. I have typical plug in chains. No need for me to drag in anything while it runs.
When I was switching from Borland development environment.... oh that was hard... nothing worked the way it SHOULD, not even simple Copy/Paste!
First run of "vi" under BSD... how to EXIT this black screen??
Windows on 8086... why someone can consider to wait 2 minutes for some dumb graphics?
I mean changing modern DAWs is not so hard