A couple issues I noticed right off the bat in 8.5.1 64-bit:

1.  If I play a project, it doesn't stop automatically at the end of the song.  It just keeps going off into infinity until I hit the stop button.

2.  In track view during playback, if I'm adjusting levels, pan, whatever, in the track pane, sometimes the real-time motion/progress of the clip pane stalls out.  If I click anywhere in the clip pane, it will jump ahead in the project to the point that is actually playing back at that time.


Perhaps these are settings issues on my end, but I've never had to mess with these particular issues with any version of Sonar.

Thanks Cakewalk doods.

Cool.  Thanks.

That helps with my first issue.  Still have the second.

Also, where is the Studioverb2?  It's (the only one) missing from my plug-ins list.  Called something different?  Located somewhere else?

Danny Danzi

Johnny5078


I am finding the samples from Ezdrummer are taking much longer to load under the 8.5.1 version.   It works but it takes a long time.  Has anyone else noticed this?

John

It's always been slow for me John. I've been told the reason for that is due to me running 24/48 and the EZD samples are not the same so it converts or something as it's loading up. Since day 1 it's always been a long load time for me though....and I have a pretty quick system.

Thanks for the reply when I get to that  PC later I am going to give it another try.  Maybe it was the same under 8.0 for me too and I just wasn't paying attention.  

DarinBad


Step Sequencer 2:
 
Load a VSTi (Such as Session Drummer). Open the step sequencer. Write some notes and click to open the velocity lane. You can adjust the velocity of the individual notes by holding the Shift key and clicking on the velocity meter for the note in the lane. This works as expected. Now, add four more beats to the pattern (One measure now becomes two measures). Write some more notes on the new beats. Now, try to adjust the velocity as before, using the Shift+Click on the meters of the new notes. It won't work. You have to close the step sequencer for that pattern and (from what I can tell) write a new step sequencer pattern, then go back to the original pattern, and it will work as expected. Maybe you don't have to start a new pattern before going back to the original, I'm not sure about that... I do know that you have to 'refresh' the original pattern in some way though, and starting a new pattern and going back to the original seemed to do the trick for me, consistantly. It's not a show-stopper, but a nuisence for sure.
 
The Bakers did a fantastic job on the new version of the Step Sequencer. It just has a few little niggles to be ironed out. Nicely done. Especially the swing feature for individual notes, which is great for Hi-Hats. I love programming drums on this thing.

You're right about this, but there's no need to hold the SHIFT key in order to edit velocities.  Just drag the cursor as needed to change them.  Another thing I noticed is that, if you leave the controller's lane opened, then close/re-open the Step Sequencer, the velocities will disappear.  You have to toggle their view state in order to see them again.  I'll be reporting this to Cakewalk.  Thanks for informing us :-)
 
Take care!

More Audiosnap stuff.  Despite the Audiosnap Palette taking up at least as much screen space, it has less functionality.  "Add transients to pool" has been relegated to a context menu command (or a function key command). The "quantise to pool" command has also gone from the palette.  It is now a multiple-click sequence involving the new Transient Tool and deeply-nested context menu items.  A workflow PITA.

Worst of all, the context menu does not appear if the target clip is MIDI, so you cannot "quantise to pool" for a MIDI clip by any means that I can find, other than "copy to clipboard" on the audio clip, then select the MIDI clip, then go through the Groove Quantise dialogue for the MIDI clip.  As I prefer to use Audiosnap on short clips (for more control) these changes add up to a very clumsy and slow workflow.  This is especially disappointing when the functionality was there and has been removed.

Moan, moan, moan

Edit - I guess there's a philosophical view that what I've described is not a bug (as it works as described in the documentation), but since it is something that performs worse than before, I think that it belongs here.

I've looked into this Matrix and it's seems to be memory related. When you first load it and have it set to the start from the beginning, it can start anywhere. They were all starting at 8 o'clock on this latest one. Then it cleared itself and was normal. This has happened many times. Similarly, if you have it set to play from Now, it can start at the beginning all the time and then settles. I've not found a pattern as to how it clears itself or why sometimes it doesn't work how it should.

I looked at the update and noticed some things that are still affected

• The first MIDI note of a cell would sometimes not play when triggered
• Audio glitches could sometimes occur when quickly triggering MIDI clips within the same row
• Matrix view would sometimes lose MIDI learn assignments after swapping MIDI hardware

I opened Beatscape and it went haywire and starts from anywhere  - closed it, it went ok. I opened Superior Drummer - it went haywire  - closed it it went ok = opened Dim pro it went Haywire  - closed it, it went ok. In fact, opening any soft synth throws it out of whack on mine.

That's the common denominator and why the Matrix doesn't function properly on my PC. If any soft synth is opened it goes out of whack. There are a few other foibles but that's the main one. Great! i can't have other things open.

@ Strinkinglyhandsome1,

I'll try to play with the Matrix some more later tonight (much later actually).  But I'm gonna try to replicate the issues you have described.


@ Seriousfun,

There's two easy ways of opening the Audio Snap palette:

1- Select a clip (or groups of clips) and press F12.

2- Click the new Transient Tool and then click on any audio clip.


Remember, Audio Snap won't open on MIDI clips (though you can right-click a MIDI clip and open it that way).


HTH

I posted this in its own thread. I post it here to be in compliance with the spirit of the thread. Which is a good one.

I have not done as much testing as I should but off hand I have found Ozone 4.03 is not working as well as it does in Sonar 8.3.1. Changing things in Ozone causes distortion and a slow down of the audio. I think due to a sample rate screw up. This I don't believe is a Ozone problem but a Sonar audio engine issue.

I took the same test song and played it in both 8.5.1 and 8.3.1. No issues in 8.3.1 but severe issues in 8.5.1. A stop and start will fix the problem but that is not needed in 8.3.1 temporarily until one does another parameter change.

Ozone has no problem what so ever in 8.3.1. Nor has any Ozone ever had a problem in any version of Sonar that I have used ever since I bought Ozone when it was DX only.

Edit this was solved. Its due to the new delay compensation in Sonar and Ozone 4. All you need do is turn off the delay compensation in Ozone. The solution came from Eric (Hansenhaus).

Strinkinglyhandsome1,

So I was finally able to check the Matrix out again but I didn't find anything out of the ordinary.  On the contrary, everything performed very reliably I must say.  It took me a bit of experimenting to learn what each symbol means (though I'm still now sure what 'Latch Mode' does). 

Anyways, the first button called 'Global Loop Mode', when it looks like this (--->) means that the loop plays once.  When you select the other option and its lit, the loop just keeps looping.  The next button is 'Latch Mode', but I still haven't figured out its use (will read about it later I guess).  Next is the 'Retrigger Mode' button.  When lit, you can retrigger the loop everytime you hit a key on you MIDI controller, but the 'Global Loop' button needs to be lit as well.  When not lit, pressing a key will enable the loop and pressing the same key again disables it.  Finally, the 'Cell Start' button.  This is the one that's been fooling around with ya :-P.  When lit (|--->), the loop starts from the beginning (on note 1 of the loop).  When not lit (...-->), the loop will not necesarily start from note 1 (which is why you sometimes don't hear the first note in the MIDI loop).  I'm assuming this happens because the Matrix is going by its own internal clock when the Cell Start button is not lit.

Furthermore, I MIDI learned a full octave on my MIDI controller and started triggering columns left and right (as fast as I can) without a single glitch.  I don't have other MIDI hardware, except the Alpha Track, so I couldn't test the MIDI learn assignment deal.  Proceeded to open up SD3 and Dimension Pro while triggering loop patterns on the Matrix without a hicup.  Like I said, eveything performed very reliably no matter how much I abussed it.  I'm doing all this using a Core 2 Quad system (Q9400) with 8GB of RAM, RME FF400 and Sonar 8.5.1 x64 under Vista64 (don't know if this matters but just in case).

Take care!

Hey Jose - could you put up a screen picture please of how it is when you just want it to play back from the beginning each time.

That's what I use with Ableton and all I will use with this.

Thanks.

Jose7822


I'm really starting to think its indeed user error.  Try this:

I've never been so insulted in all my life :)
Cheers. I will experiment vigorously.

I guess you were serious. 

In that case, I must apologize since I didn't mean to insult you.  You said you didn't mind it being user error which is why I said that that's probably what it was.  But that was meant to make you feel better, not worse.  Anyways, my bad.  I really want to help you out and was waiting on you to try the steps I gave you.  It's up to you though.

Take care!

Willy Jones [Cakewalk
]

Greetings Everyone,

SONAR 8.5 has been added to the feature request and Windows 7 has been added to the problem report form. 

I know I often sound like a broken record on this topic, but please please please be sure you are telling us about any issues you find or features you would like to see there as well.  It is the only way to be 100% sure that we are aware of it.

Problem Report Form

Feature Request Form

Thanks,

The problem with this is it doesn't work. I did the following:

• Spent time researching a bug in detail
  
• Wrote a plugin that specifically makes it easy to isolate the bug
  
• Took screenshots of SONAR that details the bug in action
  
• Posted a detailed resport on a website
  
• Included the plugin that exposes the bug
  
• Included the source code of the plugin that exposes the bug
  
• Included a project bundle file that can be opened in SONAR to easily reproduce the bug
  
• Filed a bug report on 2/24/09 with ref # CWBRN-1336. 
  

 
So what happens 7 months later?  I find that the bug is still present in SONAR 8.5.1, and SONAR is still incapable of doing basic MIDI routing.
 
So, someone from Cakewalk please tell me why anyone should bother filing bugs. I'm certainly done wasting my time doing it.

strikinglyhandsome1


No, I was joking!!! I was out doing the garden!

I never take forums or music serious.

Keep up the good work and cheers for looking into it.

Phew!!!
 
Glad you didn't take it the wrong way.  I didn't hear back from you, even though it showed you were still online, so I got worried.
 
Anyways, have a good one handsome dude :-)

SilkTone

Willy Jones [Cakewalk
]

Greetings Everyone,

SONAR 8.5 has been added to the feature request and Windows 7 has been added to the problem report form. 

I know I often sound like a broken record on this topic, but please please please be sure you are telling us about any issues you find or features you would like to see there as well.  It is the only way to be 100% sure that we are aware of it.

Problem Report Form

Feature Request Form

Thanks,

The problem with this is it doesn't work. I did the following:

• Spent time researching a bug in detail
• Wrote a plugin that specifically makes it easy to isolate the bug
• Took screenshots of SONAR that details the bug in action
• Posted a detailed resport on a website
• Included the plugin that exposes the bug
• Included the source code of the plugin that exposes the bug
• Included a project bundle file that can be opened in SONAR to easily reproduce the bug
• Filed a bug report on 2/24/09 with ref # CWBRN-1336. 

 
So what happens 7 months later?  I find that the bug is still present in SONAR 8.5.1, and SONAR is still incapable of doing basic MIDI routing.
 
So, someone from Cakewalk please tell me why anyone should bother filing bugs. I'm certainly done wasting my time doing it.

 
Wow!
 
That's a very nicely detailed bug report right there.  I'll send all this info to them again just in case they missed it the first time.
 
Thanks for providing this SilkTone!