I dind't understand it too!
 
By the way, I took a short view to Studio One the last days and I must say, that the workflow and the possibilities in Sonar are yet better at this time. Of course, Studio One is very young in comparrison with other daw's. Therefore it is really good and has some nice features. I think with the upcoming version 3 it will get closer to the established daw's.
 
So Cakewalk, use your experience and bring sonar to the front - listen to the users, don't ignore them.
 
Timo

Timo Finkbeiner
Therefore it is really good and has some nice features. 

I think it's very personal what you experience with a certain setup of features.
 
For me, using daw as a tape machine basically - just to hold clips and plugin effects - most of new features in sonar is of no value to me, stretching, audiosnap, vocalsnap etc. Stretching I can imagine what it's for, but the rest I have no idea.
 
Started to use more external midi gear - I was really in for a ride with StudioOne. The amount of settings you were to do on each track and setup the ports to allow controllers to be recorded - my god, what were they thinking. Don't think you can arm for record and it would record whatever came on midi in - no, no. Unless you had echo on, it would not accept anything but midi notes and destination port, a VSTi or midi port - had to be setup properly or nothing accepted. As I understand devs of S1 came from Steinberg and still they neglect things that work well in Cubase - and created a monster of S1.
 
Presonus bought Notion - and that will probably be well integrated into S1 - and that is probably the main difference to upcoming S1 v3.
 
On Cockos forum there have been screeming about notation for years, and now it seems R5 is to make it happend.
 
So look up Cakewalk Sonar, if neglecting notation for much longer...

Taking drum lessons, and learning to read drum score I really becake aware of weakness of daw implementation - both on notation and metronome as such. If using 100 tempo on external click or external metronome - you should really be able to set tempo to 100 in daw also. 
 

Hello,
 
maybe because of my other native language, I didn't really understand if you like S1 and its features now or not. Do you like it or do you like Sonar more?
 
Of course it is my personal experience what I've done the last days with S1. Everybody has it's own workflow and something is better in this daw and others in another daw. I learned Studio One to love the last days. But something I miss in S1 is the Groove Clip or Loop (as it is called in Samplitude). In S1 you have to duplicate a clip as often you want. There you have to choose if the Clips should belong to each other or not. But if they belong to each other, I dind't found a way to seperate them. Only with cut and paste. For this sonar has a better feature with the Groove Clips, where you have to select the clip, choose Groove Clip and pull it with the mouse as long as you want.

But as I mentioned above, it is only my short experience with S1 and I know my workflow with Sonar for years. So it is not really fair to compare both daw's after a short time of working with S1. I will keep looking to S1 and what will happen to the upcoming next version. Maybe than I decide to take the other train this time.

By the way, Sonar has got a lot of features I also don't use in general, but sometimes it is just good to know, what you can do if day is coming when you need it. So People who don't need Notation at the moment, maybe the day is coming when you will be happy to have a good notation within Sonar.
 
Timo

Timo Finkbeiner
 
maybe because of my other native language, I didn't really understand if you like S1 and its features now or not. Do you like it or do you like Sonar more?
 
 

I like Sonar more. It was a showstopper in Sonar X3, Metaplugin not working for some plugins, that made me go for S1 on a campaign. But Sonar 21.x fixed that. Metaplugin(3rd party http://ddmf.eu) is the one plugin that fixes many routing limitations in Sonar, for me, so very important.
 
A few things in S1 that I like are that you can place a bus inside a folder. Nice to keep things together.
Their approach to visibility of tracks/busses I like better than the menu stuff in Sonar.
Also a project or performance monitor showing used pdc, as I remember it. 
 
Other things I like Sonar solution better are multi out VST instruments. In Sonar you've got both simple instrument tracks or based on synthrack and many midi tracks - selectable. And you've got all multi outs inside a folder in Track View as well. S1 only show second and further outs in mixer view.
 
Freeze is in Sonar superior to anything I saw.
 
And for a long time, Sonar intergration of Staff View is pretty good(so at least some of comment is on topic). Just needs an update and some love...
 
And over all is the time S1 v3 has taken tells me it's not as successful as Presonus expected. If it shows up with VCA Groups, Notation ala Notion integrated - it's understandable, otherwise not.
 
I also like bugtracker in Sonar, how you get informed that a CWBRNO is updated in status etc.
And last, but not least, I like the feel of this membership and possibly monthly updates with fixes and stuff all year round. Presonus only got a forum, they say they read - but you really have no idea or confirmations on anything. Cakewalk is more targeted to dialog with userbase - and that makes a big difference to me. And this change in approach is also what I consider reason for improvements in stability the last years.

Hello,
 
ok thank you. Now I understand your opinion.
I am from Germany, so my english is as it is - but surely not so good for understanding everything in the forum.
Sometimes I have to look in a dictionairy for finding the right words.
 
Timo

WOW! A couple crumbs from the bakers.
 
Tracks are now listed numerically in the Staff View
 
Staff View Track Pane no longer forgets picked tracks when changing screensets
 
Definitely on the top of my "fix list". Not.
Well, at least they looked at it.

jatoth
WOW! A couple crumbs from the bakers.
 Tracks are now listed numerically in the Staff View
 
Staff View Track Pane no longer forgets picked tracks when changing screensets
 
Definitely on the top of my "fix list". Not.
Well, at least they looked at it.

Optimistically I think it's a lot more than that. The midi enhancements - distinct note on/note off messages - would be necessary to fix some of the notation issues - rests in tuplets for example. IMO, There's more brewing in this area than bug fixes.

Keep hope alive.

Brando

jatoth
WOW! A couple crumbs from the bakers.
 Tracks are now listed numerically in the Staff View
 
Staff View Track Pane no longer forgets picked tracks when changing screensets
 
Definitely on the top of my "fix list". Not.
Well, at least they looked at it.

Optimistically I think it's a lot more than that. The midi enhancements - distinct note on/note off messages - would be necessary to fix some of the notation issues - rests in tuplets for example. IMO, There's more brewing in this area than bug fixes.

It would be so funny if they inadvertently fixed the tuplet issues when fixing soming in PRV.

Kamikaze

Brando

jatoth
WOW! A couple crumbs from the bakers.
Tracks are now listed numerically in the Staff View

Staff View Track Pane no longer forgets picked tracks when changing screensets

Definitely on the top of my "fix list". Not.
Well, at least they looked at it.

Optimistically I think it's a lot more than that. The midi enhancements - distinct note on/note off messages - would be necessary to fix some of the notation issues - rests in tuplets for example. IMO, There's more brewing in this area than bug fixes.

It would be so funny if they inadvertently fixed the tuplet issues when fixing soming in PRV.

I don't believe it would be inadvertent - The root cause for Cake's reluctance to fix the Staff view is that the problem is deep rooted in the heart of their MIDI code - it isn't that they don't like or have no use for Staff View. The fact that they are fixing MIDI issues that are at the heart of how CAKE has always interpreted MIDI on and off note messages says to me they are getting more serious about tackling the issue - their approach is to fix some things without breaking everything else, which I believe is the right way to approach it.
A big reason (maybe/likely not the only reason) for Cake's inability to display and manipulate tuplets correctly is due to the fact that Cake previously did not manage discrete note-on and note-off messages for each midi note.
I'm not saying that this fixes the issue - just that it resolves one of the factors precluding correct handling in that particular issue.