madoues
pbognar
Logic would dictate that the Staph View code is un-maintainable for either technological or legal reasons, otherwise the bakers would have relegated one of their devs (the one who drew the short straw) to sit in the corner and throw us a small bone every once in a while, so that it could be said that the SV has been improved.
I would be happy with just some small improvements (tied triplet handling with leading or embedded rests, note value buttons, etc.) But this is not going to happen through development (see above). Cubasically, Cakewalk may feel that today's digital performers do not need pro tools for MIDI editing in a notation environment.
I have a notion that an improved SV will only be realized through acquisition.
I feel the same way. It seems that we who wish for SV improvements are the minority. However, many of us don't need a full blown notation program. It would be nice to see even the smallest of improvements now and again. If there had been just one fix or minor new feature to the SV every year, we would have something that is quite workable by now.
I have not been upgrading every year for a while now, mainly because there is no improvements in SV. I wouldn't really need to upgrade at all I suppose, but then there is always another carrot in new features that makes me eventually upgrade.
Dan
I don't have to tell you that my post was quite tongue in cheek, but my opinion was very real.
However, if you read some of jsg's posts, he spends almost all his time in Staff View, and has found some minor SV improvements in X3, and has found work-arounds for almost all of the long standing Sonar SV limitations. I have to give him credit for that. He should publish a Sonar SV Survival Guide.
He seems to come to the rescue whenever someone has an SV issue, so if you have a specific problem, post it.
In the meantime, it would be nice if Cakwalk could continue to throw us notation MIDI editors a bone here and there, until if -or- when the Bakers decide to implement an SV make-over in a future release. Personally, I could use:
1) an aim assistant (like large cross-hairs) for inserting new notes (not sure, but I believe Cubase might have something like this)
2) the ability to see the PRV right above the corresponding track's staff view for verifying MIDI durations (I think this exists in Samplitude, and a variation exists in Mixcraft)
3) the ability to have chords on the staff re-sound each time you change a note within the chord (this the default behavior in Logic)
Until then, you should do what is right for you.