It still makes me "jump" when the tail end of, for example, a piano chord sounds when I press play.
 
I do think this is a great development.
 
Oh, and I call it Nigel...

So then Cakewalk is an XTC cover band?....

https://youtu.be/gXNhL4J_S00

MIDI note event chase is a welcome addition, will be a big time saver when working on pieces with long notes.
 
However, I won't be able to take advantage of it because the copy-paste bug that occurs in both event list and staff view and has been reported by numerous people, hasn't been fixed.  I cannot understand such a high priority bug being ignored. 
 
In contrast, I just started using MIR convolution reverb for my VSL library.  I found a bug in the demo on Friday.  I reported it on Saturday.  I got a response on Monday that that developers confirmed the bug.  This morning I got a beta with the bug fix.  All in 3 days.  Now there's a software company that really cares about fixing bugs promptly.  If only Cakewalk could react like that...

How many lines of code in the MIR plugin vs. SONAR and all Cakewalk-owned plugins would you guess?

brundlefly
How many lines of code in the MIR plugin vs. SONAR and all Cakewalk-owned plugins would you guess?

I have no idea.  I do know that MIR utilizes over 5000 samples of various halls and rooms, and I know that what is different between the two companies is the concept of service.  I looked over my bug reports to CW and some are 5 years old that have not been fixed.   When I email VSL regarding a question or problem, I always get a response within 24 hours, often much less.   CW might respond to an email 6 weeks after it was written and, as we all know, CW's phone support is pretty much gone.   There's the software, and there's the culture of the people who make the software.  The latter always impacts the former for better or worse. 
 
I don't mean to be critical of such exceptionally talented, hardworking and good people, I know the economic conditions are always a pressure.  But how about just devote 2 or 3 updates only fixing bugs, no new features, no new functionality, just repair what is already there?   I can't be the only person who is saying this, each in our own way.  When I get an update I don't think "wow! what  else can I do with this software", instead I expectantly hope one of the bugs was fixed and new ones were not added.  Sometimes too much is too much.  When a DAW does the following really well, 1) record and edit midi, record and edit audio, handle plugins and is stable and doesn't crash, why not just create another program to do different things?  Making a program so big seems to invite more complexity and more chances of errors.  Please fix the bugs in staff view, the event list and giving MIDI the attention it deserves. 
 
Jerry
 

jsg
There's the software, and there's the culture of the people who make the software.  The latter always impacts the former for better or worse. 

There is also the price and profitability of the software, and how many developers and support personnel can be funded by the available revenue stream. VSL is high-end stuff in a very focused area of the music-production market with what I would guess is a relatively small number of users paying a premium for a premium product. And when something is wrong, it affects all or most users because the feature set is small, and most users use most features with high frequency. And without knowing exact numbers, I think there's no question that the amount of code that VSL has to maintain is nothing like the amount (and complexity) of code that Cakewalk has to contend with.
 
I for one am confident that Cake's lack of responsiveness in certain areas/instances, especially of late, is most likely due to resource constraints rather than to lack of a sufficient culture of service. When resources are limited, everything gets to be about priorities. I think it's pretty clear that the great majority of SONAR users do not spend much, if any, time in the Staff and Event Views, and the number of intensive users of these views is quite small.

brundlefly

jsg
There's the software, and there's the culture of the people who make the software.  The latter always impacts the former for better or worse. 

There is also the price and profitability of the software, and how many developers and support personnel can be funded by the available revenue stream. VSL is high-end stuff in a very focused area of the music-production market with what I would guess is a relatively small number of users paying a premium for a premium product. And when something is wrong, it affects all or most users because the feature set is small, and most users use most features with high frequency. And without knowing exact numbers, I think there's no question that the amount of code that VSL has to maintain is nothing like the amount (and complexity) of code that Cakewalk has to contend with.
 
I for one am confident that Cake's lack of responsiveness in certain areas/instances, especially of late, is most likely due to resource constraints rather than to lack of a sufficient culture of service. When resources are limited, everything gets to be about priorities. I think it's pretty clear that the great majority of SONAR users do not spend much, if any, time in the Staff and Event Views, and the number of intensive users of these views is quite small.

What evidence is there to say the event list is not used by many users?   I've been using Sonar since 1992 and I have no idea how many users use the event list or not.   We've had plenty of discussions about the staff view, but the event list?  It's not clear at all to me that people are not using it.  If the same paste bug occurs in at least two views, and probably more, I'd think it would be a high priority, since it is not merely a cosmetic bug but clearly affects functionality.
 
 

jsg

brundlefly

jsg
There's the software, and there's the culture of the people who make the software.  The latter always impacts the former for better or worse. 

There is also the price and profitability of the software, and how many developers and support personnel can be funded by the available revenue stream. VSL is high-end stuff in a very focused area of the music-production market with what I would guess is a relatively small number of users paying a premium for a premium product. And when something is wrong, it affects all or most users because the feature set is small, and most users use most features with high frequency. And without knowing exact numbers, I think there's no question that the amount of code that VSL has to maintain is nothing like the amount (and complexity) of code that Cakewalk has to contend with.
 
I for one am confident that Cake's lack of responsiveness in certain areas/instances, especially of late, is most likely due to resource constraints rather than to lack of a sufficient culture of service. When resources are limited, everything gets to be about priorities. I think it's pretty clear that the great majority of SONAR users do not spend much, if any, time in the Staff and Event Views, and the number of intensive users of these views is quite small.

What evidence is there to say the event list is not used by many users?   I've been using Sonar since 1992 and I have no idea how many users use the event list or not.   We've had plenty of discussions about the staff view, but the event list?  It's not clear at all to me that people are not using it.  If the same paste bug occurs in at least two views, and probably more, I'd think it would be a high priority, since it is not merely a cosmetic bug but clearly affects functionality.
 
 

I have only used the event list to find seemingly rouge events. like once.

I use event list frequently and it is always tabbed in the dock as part of my standard template.

jsg
We've had plenty of discussions about the staff view, but the event list?

Exactly my point. Just compare the number of threads and posts about working in the PRV with the number about working in the Event List, and note how few people have mentioned the 'Starting Track Paste' problem or responded to your original post about it.
 
The Event List's heyday was in Cakewalk for DOS. Most users have no interest in working with raw 'data' and typing in values. They want sophisticated, mouse-driven graphical interfaces. Whatever you do, don't suggest anyone use Find/Replace. Even renaming it from 'Interpolate' couldn't save it from the dustbin of MIDI-editing history.