I'm actually not fussed if the scrolling issue is deemed a bug or a feature that and recognise that everyone's use case may be different however not being able to scroll a PC without clicking on it is still pants :)

dorism


not being able to scroll a PC without clicking on it is still pants :)

I've said this in other posts on this subject, this works fine for me, that is, as long as my mouse pointer is hovering over a ProChannel, as soon as I scroll, the ProChannel section scrolls, without making it "active."
 
 
Anyway, the most heartening thing about this topic for myself is that some of the Cakwalk chaps have responded. That has to be good?

mmorgan

Are we about to be surprised?? I've had an email from Cakewalk which goes nowhere...but it's from: Cakewalk Forums http://betaforum.cakewalk.com/ Anyone else??

 
"betaforum" So is this a Beta for Sonar or is this a Beta for the Forum?
 
I sincerely hope that Cakewalk is dedicating this to the product and not this forum. I rely on the product the forum is helpful and all but I can live with it's idiosyncracies.
 
Regards,
 

The SONAR team is independent of the forum management group.


Read into that how you'd like 

I can't agree with the notion of function loss in X1/X2. True Notation is far better in Cubase but I think comparing them side by side you'll see how quick Sonar is over Cubase. 

You'll will be back. Oh before I forget enjoy their nice and friendly user forum.

gcolbert


Ian - just because something does not work how you want it to does not make it a bug.  If the feature is working as designed it is not a bug.  Granted, it may have been easier for YOU in another version, but the more features that are added the more complex the GUI becomes.  Possibly if you were opening feature requests instead of bug reports for things that are not bugs the folks at Cakewalk may have something to respond to you with.

Glen

The piano roll doesn't open to the now time.  Getting it there requires an extra start/stop once it's opened.
 
Audio clips mostly aren't activated in the inspector when you click on them.  It takes a couple of extra clicks to get them activated.
 
Have you ever tried time stretching an audio clip from the inspector?  (it CAN be done, but I doubt you'll find the instructions anywhere). 
 
Those are bugs IMO.  I don't think these are designed functions.  I think it's just clunky, sloppy, poorly tested coding.
 
Peace,
 
Ian
 

This forum is pretty good. I've seen some that don't even have users/visitors. People here are pretty responsive to each other. 

Seth Kellogg [Cakewalk
]

dorism


I'm pretty sure the response I'll get from support will be... it's not a bug.... it's a feature

Features are designed a certain way because we think that's going to be the 'best use' for the majority of user cases. We understand this doesn't always fit into everyone's idea about how a feature should work. We're also human and sometimes things get overlooked.

I've been shocked many times on just how different people use our software to build their individual mousetrap. This is why we are always looking for constructive feedback on how we can improve the software and user experiences.

Hi Seth...

Nice to hear from you...

I (and I'm sure many others) understand the dilemma all too well... and as different minds assimilate the same info, different results occur...

I know it's very hard to decide which item is more in demand as well as reasonable... and I know I'm not usually very pleasant about the changes that directly affect me.

Over all I've always believed the Cakewalk team to be very practical and efficient at giving the majority what they want... hence the wonderful community of users with all the varied uses...

When big changes (such as Cakewalk becoming a Roland product) I myself feel a trepidation as I have seen before how the change to such large company control can make/break an already successful product line... (I used to work for the original Soundscape company)...

Then along with the personnel changes, we get what feels to be less communication with the company and an increase in "nervousness"...

So I thank you for joining in the conversation here and helping to re-connect us with our Brothers/Sisters in The Bakery!

Keni

I'm bailing to Cubase.

 
The following is not a slam on Cubase, just my experience:
 
I've been working with Cubase for a few months and while there are many things that make it a fine DAW I consistently find myself at a loss as to why something is done the way it is. I understand that it is what it is and if I want to use it I must adapt to the way it 'thinks'. However I am reminded of when I was first reading Gravity's Rainbow by Thomas Pynchon, I absolutely could not hear the authors 'voice'. Until about the third try and then the book seemed to be 'revealed' to me.
 
Perhaps Cubase will be like that long term but I keep coming back to Sonar because I can understand how it is 'supposed' to work (albeit Track Lanes seem to baffle me). While it may be just because I have more experience with Sonar I don't think that's the case. Moving from 8.5 to the X series was pretty intuitive to me - I got what the design was about immediately and, for me, it was a big improvement .
 
None the less I hope that the Q (as I call it) works out for you, I can vouch that the Staff View is an improvement over Sonar and the video seems to work better also although to be fair I haven't really done much video in Sonar.
 
Regards

I for one do not want this forum to control the direction of sonar. Yes we are a vocal group but represent such a small minority of users. In the past it has led to less than desirable results. P5 as an example. A brilliant idea I immediately got on board and then cakewalk started following the input of the forum and now P5 is no more. :-)

mmorgan

I'm bailing to Cubase.

 
The following is not a slam on Cubase, just my experience:
 
I've been working with Cubase for a few months and while there are many things that make it a fine DAW I consistently find myself at a loss as to why something is done the way it is. I understand that it is what it is and if I want to use it I must adapt to the way it 'thinks'. However I am reminded of when I was first reading Gravity's Rainbow by Thomas Pynchon, I absolutely could not hear the authors 'voice'. Until about the third try and then the book seemed to be 'revealed' to me.
 
Perhaps Cubase will be like that long term but I keep coming back to Sonar because I can understand how it is 'supposed' to work (albeit Track Lanes seem to baffle me). While it may be just because I have more experience with Sonar I don't think that's the case. Moving from 8.5 to the X series was pretty intuitive to me - I got what the design was about immediately and, for me, it was a big improvement .
 
None the less I hope that the Q (as I call it) works out for you, I can vouch that the Staff View is an improvement over Sonar and the video seems to work better also although to be fair I haven't really done much video in Sonar.
 
Regards

I don't want to have to learn a new DAW but I need to compose with notation inside a DAW.

gcolbert Ian - just because something does not work how you want it to does not make it a bug. If the feature is working as designed it is not a bug. Granted, it may have been easier for YOU in another version, but the more features that are added the more complex the GUI becomes. Possibly if you were opening feature requests instead of bug reports for things that are not bugs the folks at Cakewalk may have something to respond to you with. Glen The piano roll doesn't open to the now time. Getting it there requires an extra start/stop once it's opened. Audio clips mostly aren't activated in the inspector when you click on them. It takes a couple of extra clicks to get them activated. Have you ever tried time stretching an audio clip from the inspector? (it CAN be done, but I doubt you'll find the instructions anywhere). Those are bugs IMO. I don't think these are designed functions. I think it's just clunky, sloppy, poorly tested coding.

 
Ian - These are not bugs.  They are even less than features.  They are specifications - or requests for specifications.  The term 'bug' is not open to interpretation.  A bug is when a program does not perform the function that it was written to perform.  If the specifications for selecting an audio clip mean that the user has to click fifteen times it is not a bug if it was written to require a user to click fifteen times.  You should not expect a response from Cakewalk when you report these as bugs - they are not (well the PRV initial view MAY be).
 
Glen

  Ok Here I list some of the features I got via Feature requests 

1 MIDI meters
2 Better Mackie Control support
3 Inline Piano Roll
4 Auto Zoom
5 Susan G got the Pause Key
6 The track Inspector
7 Confidence recording
And a ton of others
The above are my feature requests except the pause key.

rabeach

Also, even though I could have done without them instrument tracks requested by P5 users after it was discontinued.

You could have done us a favor and not reminded us about that one. 

  I can change keys non destructively. Use the Key widget in the track inspector. You can use Key Markers too. 

Now there are a few inadvertent screw ups with global control key + for quick groups. I agree and CW is aware of them.

I found MIDI outs on opened MIDI files can't be global. This is inadvertent and is not meant to be this way.