Hey FBB . . . it seems everyone uses SONAR different for their needs, you may never use SV, but some of us need it to be better. I especially like that SONAR has so many different tools, that users of the software can adapt their unique methods to utilize it any way they chose. I think this thread was started in the spirit of making SV better, and more than it currently is. I think I use it more than your precious screensets.

Made this bad quality vid in another thread  to show the 'silly' snap settings made in x1d.
http://www.youtube.com/wa...e=youtube_gdata_player

noynekker


Hey FBB . . . it seems everyone uses SONAR different for their needs, you may never use SV, but some of us need it to be better. I especially like that SONAR has so many different tools, that users of the software can adapt their unique methods to utilize it any way they chose. I think this thread was started in the spirit of making SV better, and more than it currently is. I think I use it more than your precious screensets.

Hence I've added my support for a revamp to this thread..........

FastBikerBoy


@jsg - Have you thought about writing up a feature request/bug report and then starting a thread here asking for others to support it?

CW have said that they take improvements/fixes on a priority base of which user request is part. As I've said I rarely use the SV so it doesn't directly affect me and as a result I can't be bothered to write up bug reports/feature requests for it. However if someone else does the leg work, i.e. give me something I can cut & paste in then I'll support it.

I tried something similar with a PC module idea that RogerH had and I got plenty of support there. Of course whether it has had any effect I guess time will tell, but you can either complain endlessly on here about it or try and do something about it & then complain on here.

Just a thought...........

I've done that, every bug I mention on this forum has been forwarded to CW through the Problem Reporter.  No sense in complaining without doing that.   I was even in Boston last year and brought it up when I went to the Cakewalk offices for a visit.  And, about 5 years ago Cakewalk called me to ask me specific questions as to what they can do to improve the staff view.   So, I really don't get it.  They just don't seem interested in the SV particularly and most of the big improvements have been in the audio section of the DAW rather than MIDI.  
 
JG
www.jerrygerber.com
 

I urge everyone on this forum who uses and/or cares about the staff view to fill out the problem reporter on the support section regarding the bugs you're finding in X1d and also to write Cakewalk and tell them that the SV is extremely important to you and that you feel a fully professional DAW does not neglect this aspect of the program.

Thanks!

Jerry Gerber
www.jerrygerber.com

jsg


I urge everyone on this forum who uses and/or cares about the staff view to fill out the problem reporter on the support section regarding the bugs you're finding in X1d and also to write Cakewalk and tell them that the SV is extremely important to you and that you feel a fully professional DAW does not neglect this aspect of the program.

Thanks!

Jerry Gerber
www.jerrygerber.com

Agreed - this is very important everyone.  If we want to the Staff View to be fixed or enhanced in any way, we're going to have to get off of our collective butts and actually report the problem or feature request.
 
http://www.cakewalk.com/Support/contact/default.aspx
 
I would imagine that functionality which has degraded would definitely fall into the problem reporter bucket.
 
Long standing problems which never worked right from the very beginning would have to be reported as a feature request.  These might be things like issues with the handling of tied triplets - eg. not being able to start a tied group of triplets with a rest or not being able to have a rest in the middle of a tied group of triplets would have to be reported as a feature request.
 
Maybe we could collect a list of clear wording for these problems / requests so it would be eaiser for people to paste in the issue.
 
 

Maybe we could collect a list of clear wording for these problems / requests so it would be eaiser for people to paste in the issue

Exactly what I was suggesting in post #37 & #39. Raising support rule no. 1 - Make it easy for people to support you.

Hand raised here!  How long to I have to keep it raised?  It's getting kind of tired.

I don't actually have any problems to report about the Staff view, works fine for my methods (has for years) but I would like to see some new features added regarding musical composition, such as: : : :  note editing, pattern macros, use of color, better drum mapping, more intuitive lyric input and selection filters, ability to nudge notes . . .
There's a lot of talk here in this thread, but I haven't seen many new ideas or new features that could be implemented into the Staff View. If Cakewalk is going to do something with it, we need to give them some specific new ideas of how Staff View could actually be better . . .

I work mostly in the PRV, but I also use the staff view.

I find the staff view very useful when I want an overview over several tracks, so an improved staff view is welcome.


BTW, I still use Sonar 8.3.1

Elffin


Didn't John collect Staff view users requests for 8.5.3? A topic called an open letter to Cakewalk or something...
http://forum.cakewalk.com/tm.aspx?m=1743654&high=Staff+view

What I would like Cakewalk to do is to just announce - we have no intention of improving staff view so we can move on to pastures new.

Cakewalk doesn't owe us anything and we don't owe them either..

Made a search using keyword 'staff view' on these forums...

http://forum.cakewalk.com/search.aspx?searchid=548235&high=Staff%20view Pretty long read.... Wonder how many of them are still Sonar users?

I didn't realize that "open letter" was so old.  I guess my suggestion would be to collect bugs and feature requests in this thread, for the purpose of allowing those who want to submit a bug report -or- feature request, to be able articulate the problem in a concise and consistent manner.
 
The thing which is new is that there are 3 areas of functionality:
 
1) Something which hasn't worked from day, eg. the handling of tied tuplets (should be a Bug, but I suspect Cakewalk would see it as a Feature Request)
 
2) Something which worked in a previous version but is now broken, eg. the missing duration icons which could once be clicked on to affect the duration of what was about to be entered (Bug).
 
3) Some new functionality which would improve the Staff View, eg. being able to click and/or drag a note within a chord and have the chord sound each time the note was raised or lowered in pitch. (Feature Request)
 
Cakewalk will never admit that they are never going to improve the staff view - why?
 
a)  It's not good marketing.  If there are no plans to improve it, whey tell customers, if they can keep them hoping, they might continue to upgrade.
 
b)  Maybe improvements are in the pipeline, but it is such a large undertaking, that it won't happen for a few integer releases.
 
c)  Maybe there really is a plan to buy existing notation functionality and a juinor version of that will end up in X1. 
  
One more thing - as we saw, a long open letter will do nothing.  We need to fill out bug reports and feature requests.  
 

Hand up to this.  I also use other software and import/ export MIDI, but it's a pain.
 
Love Sonar, but think it's overdue to bring SV in line with it's other excellent features.

there's been at least one post about how weird SNAP works on X1 when on staff view, here it's far worst that in previous versions. I never use Sonar for printing scores (I go fro Encore or Finale for that) but it's fundamental as a sequencer when arranging scores (sequencing). It just doesn't make it for me know.

Does lyric view still exist in X1? When they introduced clips they broke the functionality of lyrics view and staff view in a way that created nasty corruption of the project which can not be undone - but you'll never see Cakewalk admit this. When I was trying to do university assignments I contacted support and was given no help at all except a vague promise they would improve it. Never once did they tell me the work around, simply make sure your midi track is a single clip, ie repeatedly bounce to clip. I have Sonar PE 8.3 and I've decided Cakewalk will not get one more cent (yen actually) from me until they fix it properly.

There are lots of functions of Sonar I never use, I don't complain, I'm sure others find them useful. And I have Finale. I'd be happy if Cakewalk fix the existing bugs and make some minor improvements and some decent printing options (eg print a measure range).

Seen Cubase? Wow that's amazing.

Well, I took a look at the old "bumped" thread where I last posted...

Hands are up in the air, but it has become fairly clear that Sonar is moving in a direction contrary to what I need.

As has been said many times, having usable notation and being able to print final output are two different functions.

It might also be worth remembering that in many types of music being able to read notation is not necessary while in other types of music being able to read music is an absolute prerequisite.  Sonar is geared for the former, not the latter.

Unfortunately, sometimes those in the "former" camp, do not understand that there are very valid musical reasons to be in the "latter" camp (which does not negate the value of the music of those in the "former" camp).