Anderton
 the way I figured out how it worked was by reading the documentation. Then I just used it for about 30 minutes and it all became clear.

I know everyone is different. I could watch a video repeatedly and learn less than reading the doc and a little hands on testing. Sometimes the process is reversed, little hands on first then read what I really should be doing.

scook
I know everyone is different. I could watch a video repeatedly and learn less than reading the doc and a little hands on testing...

 
In theory I like instructional videos, but in practice I always find them disappointing. Usually there is a lot of preamble and introduction where they waste time telling you stuff that you already know or talking about how great it is. And when they finally get to the vital part that you want to focus on, they gloss over it in about 3 seconds. You replay the important part hoping to see something you missed the first time. But no, you still can't tell what the guy just clicked on.

Are you guys going to do the same transform tool for audio? That would be interesting.

Kev999

scook
I know everyone is different. I could watch a video repeatedly and learn less than reading the doc and a little hands on testing...

 
In theory I like instructional videos, but in practice I always find them disappointing. Usually there is a lot of preample and introduction where they waste time telling you stuff that you already know or talking about how great it is. And when they finally get to the vital part that you want to focus on, they gloss over it in about 3 seconds. You replay the important part hoping to see something you missed the first time. But no, you still can't tell what the guy just clicked on.

I think it depends on the user's knowledge.  For instance with Sonar I read then play with the dials, sliders etc.  I go to extremes just to see what happens.  Note that I have used Cakewalk's software for years.
 
But as a just starting photographer I use videos for my software.  I'm trying to get the basics down as well as learn what the software can do and the vids are great for that.  YMMV

Can not Sonar update / re-install if Visual C++ Runtime 2017 is installed?
 
Hello,
 
I'm Sonar Platinum and MS Visual Studio 2017 user.
Recently, i have installed VS2017 (After uninstalled VS2015)
I cannot update Sonar from Command Center after VS2017 installed.
Sonar installer has succeeded copying Sonar's files. But final phase, installing has failed. In particular, failed VS2015 runtime installing.
 
From VS2015 Runtime installer's log:
"Error 0x80070666: Cannot install a product when a newer version is installed."
 
NOTE:
Both vc2015 and vc2017 share the same major version number, 14.x and shares the same registry keys.
 
Nobody has same problem?
Thanks,
 

Hello razuu, and welcome to the forum.
 
You should post this as a separate thread in the main topic area to get some attention from other users.  Sorry I cannot help you.
 
Also post in the problem reports as well.
 
Good luck  

I think you are missing marketing opportunities by not having video blurbs about new features. Worth adding someone to the payroll imho it would pay for itself.

FCCfirstclass
Hello razuu, and welcome to the forum.
 
You should post this as a separate thread in the main topic area to get some attention from other users.  Sorry I cannot help you.
 
Also post in the problem reports as well.
 
Good luck  

Hello FCCfirstclass,
 
Oh, I overlooked it that existence of the Problem Reports page.
I will post it to the problem reports.
 
Thank you. 

Hill62
I think you are missing marketing opportunities by not having video blurbs about new features. Worth adding someone to the payroll imho it would pay for itself.

Go to the Cakewalk YouTube channel. 
 
 

SquireBum
In SONAR [2017.04] the the visibility of tracks in the Track View affects the visibility of tracks in the Piano Roll View (PRV) Track Pane.
 
For example, if I have MIDI tracks containing key switches in a folder and I collapse the folder in the Track View, I can no longer view or edit the key switch tracks in the PRV.  Also, if a track is hidden using the Track View Track Manager, then it is not available for viewing and editing in the PRV.
 
In all past versions of SONAR the ability to view and edit a track in the PRV was independent of the Track View visibility.
 
Is this new behavior by design or was it an unintended change that occurred during PRV re-design?
 
If this new behavior is by design, then the filter functionality in the PRV Track Pane seems redundant, since the filtering capability is already occurring in the Track View.  IMHO, PRV track visibility should be controlled by the PRV options and the Track Pane filter, not the Track View track visibility.
 
Thanks,
-- Ron

I totally agree.
These filters need to be isolated form each other.
This current behavior kills the possibility of the detailed control that is had in pre 2017.04 and ours a deal breaker for me.

Staying with 2017.01 unless this changes.

Thanks for the good description Ron!