gcolbert

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

Glen - You're right, the PRV is a bug.  But so is the inspector.  I just did an experiment.  I opened two projects and, with the inspector open, I started clicking on clips.  The first time, the first clip I clicked on was not recognized by the inspector, but the second one was.  After that, most but not all, subsequent clicks activated the clips in the inspector.  Not bad.  Erratic, but not horrible.  But on the second project I opened the inspector didn't recognize the selected clip until I'd clicked on four different clips.  That's just buggy.  That's not a design function.
 
I read the user and reference docs.  There isn't that much on the inspector but the overriding implication is that when you've got a clip selected, it should also be selected in the inspector.  It's not.  Not always.  Not even usually.  It takes extra clicking around to get the clip to show up in the inspector.  That's a bug.
 
Even if you don't want to call these bugs, whatever they are is constantly naggingly annoying!
 
Peace,
 
Ian
PS - Have you ever tried to time stretch an audio clip from the inspector?  That process is even more buggy IMO that the above 2 examples.

John


  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.

Take lanes were a result of feature requests as an improvement over layers
Hell, the entire X series was developed as a result of users being asked what they wanted - a shiny new interface or more plugins/vsti's etc

The World was created in 6 days -
Sonar continues to be "Evolution" and RIGHTLY SO :-)

Make MUSIC...

rabeach


It is very possible I don't understand what you are trying to accomplish. When i select a clip I have to double click the midi clip at the top of the clip; where I see a cross. It opens every time at the now time in the prv and opens every time in the inspector. If I single click it, it does not. I feel I should be able to single click the clip but it is not a deal breaker for me. If you don't see this behavior I have no explanation as to why. It certainly would be convenient to single click it. 

If I may mention...

This bugs me too, but it's not that the PRV doesn't open to the now time... It's that the now time is not always moved to where you think it will be... You have to make sure you're clicking in the right part of the clip so that now time is adjusted... In the upper portion of the clip it (the clip) gets selected but the now time doesn't change.... So you must be more careful of where you're clicking to get it to open where you want... It's driving me nuts a lot of the time... <sigh>...

Keni

Ian Ferrin


rabeach - my inspector clip selection grievances are mostly w/ audio clips. 

Re the PRV, I'm glad it works for you.  For me, when I double click a midi clip, PRV opens to the beginning of the clip every time.  100%.  No exceptions.  At least three others in another thread I had about just this behavior reported the exact same thing.  It takes an additional start and stop, or scrolling or... I think there's other ways to get it to the now time.  But they're all work arounds for many of us.

Anyway, glad it works for you.  It certainly doesn't for me.

Peace,

Ian

Okay I understand now. The same thing happens here. A vertical red line indicates the now time. I can see that this would be an issue with a large midi file. It certainly could/should be implemented better.