Pragi
And to say it clear,
imo the Reaper ui is really ugly, the workflow a desaster.
If the Reaper ui and workflow fits your needs better, congratulations,
but why you are arguing in the Cakewalk forum about Reaper ?
Since years I read "this UI is ugly", "that DAW is the best", "that is a disaster". And not in the context of one particular DAW. Open S1/Reaper/Cubase/Ableton friendly forum, and you see all the same statements, just with exchanged DAW names. That has prevented me to look around before.
Sonar/CbB has strong points compare to other DAWs. Some are in functionality, some are deep inside the concept. Discussing that and using advantages to "spread the word" can be informative and convincing for people.
F.e (NOT a complete list), in Sonar/CbB it is possible to:
+ have track inspector and console view at the same time
+ see FX list in the track view
+ see what your Surface control with WAI
+ combine loops in Matrix
+ edit and save loops
+ export program changes from MIDI track control into MIDI file
+ use project/marker pitches to auto-adjust groove clip pitch
+ use musical and absolute markers at the same time
+ sync program selection with key names in PRV (combined Ins files)
+ use ARA integration
+ use ProChannel concept
+ enjoy sample accurate fixed project rate positioning
All that is in the range from "workaround", throw "not yet" up to "not possible" in Reaper.
But the following make no big sense:
= when 2 interfaces use the same concept of comprizable animated bitmaps, declaring one of them as "ugly" and other as "perfect"
= compare 2 DAWs with identical general workflow and just say one is "a desaster".
And claiming known strong sides of another DAW is counterproductive:
- stability
- performance
If you see my points as "trolling", sorry.