Sonar 7: First Impressions / Bug Report

Hey guys!

I've been playing with Sonar 7 a little throught the weekend and all afternoon today. I must say this is a very cool release and has a lot of nice features but, as expected from a x.0 release, there are some issues I've encountered during my testing of Sonar 7. I will outline the problems I've found so far but please feel free to post your findings as well so that others can test and try to replicate these bugs if possible. The more testing we do the more stable Sonar 7 will be. So this is our chance to improve it. Here I go with my findings:


1- The Step Sequencer: As we all know, this is one of the key features of Sonar 7 and specially for those who work mostly with MIDI. It is very nice indeed but it's also a major CPU hog (or is it my system?). Just having one instance of SS was enough to slow down my system. Whenever I tried to input notes in the Step Sequencer it would take a few ms to show the changes. Playback is not very smooth either, specially when first hitting the Play button. Have you guys noticed this?

2 - LP-64 Mastering EQ and Multiband Compressor: These two are a very nice addition to the Cakewalk plugin library but, again, major CPU hogs. It seems Cakewalk is developing for Quad-Core systems nowadays . But seriously, I really liked the sound of these two plugs but I'm currently unable to use them . Cakewalk knows and has confrimed this issue so I hope it gets fixed soon.

3 - Hardware Inserts: NICE!!! This is something I didn't expect to see but I'm glad it came out in S7. I was really enjoying hearing my HW FX unit through a vocal track and messing with different settings. I even froze my tracks (in real time of course) and was very please with the results. It's very easy to set up, so easy that it makes me wonder what took them so long to implement this. The only problem I encountered was the Audio Engine Stopped message while switching from one computer to the other via a KVM switch while audio was playing back. Actually, there was something else...but I suspect it was my HW-FX unit's fault. Everytime I turned the input knob on my HW unit the input meter on it would jump to the clipping point. I have to admit that I haven't use this in a WHILE so it was probably due to dirty pots. I'll experiment with this some more.

4 - MIDI Tools: Another nice feature of Sonar 7. I was able to very quickly customize the new Smart MIDI tools to do what I wanted it to do because I only spent time customizing one . With all the cool features I added to that one button I had almost everything covered. I could probably figure out a way to use just ONE tool for everything, and I will. There are some crazy drawings features that were added but I need to experiment more with them. For example, there's an option where you can paint notes/controllers linearly. The only problem with it is that it makes strange noises and might even make your audio engine stop if you draw notes really fast.

5 - Sidechaining: A much needed feature, for me at least. I found it to be really cool and easy to setup. Cakewalk just knows how to make things....well....a Cakewalk. I tried it on a couple of tracks and it was very nice. The only thing bad I have to say about this new feature is that it might've introduced a new bug. This bug was first reported by Eric Hansen (a.k.a. Hansenhaus) and you can find all the details in this thread: http://forum.cakewalk.com/tm.asp?m=1163503 It is a reproducible one too.

6 - V-Vocal Pitch to MIDI: Great idea, but it's still not there yet. I tried it with different vocal and instrumental tracks and it just didn't do a good job translating any of them. The results were mediocre at best. The MIDI file would come out sounding different on a lot of parts. It also seemed like it was not able to translate the timing all that well either. For example, I created a V-Vocal clip on an entire ~2 min project of a cello line and converted it to MIDI notes. Somewhere along the song the MIDI file and the source track would be completely out of sync with each other. It was like the MIDI file had shrunk. Again, a nice idea but still needs a lot of work.

7 - ACT: Yeah, I know. This is not new to most of you guys but it is to me . This is not as intuitive as the other features of Sonar but it wasn't to bad to figure out either. Once you start playing with it you get the hang of how eveything works. The key point is not confusing MIDI Learn with ACT Learn which are two different things. Once you get that, everything becomes clearer. The only caveat I'm having with this is due to learning how to program things on my MIDI controller. I have figured out how to program everything but the buttons of my MIDI controller. I will mess with this some more. I really like this feature though....very awesome!

8 - Audio Snap: Haven't had time to mess with this one yet.

9 - Other Stuff: I loved ALL the new Synths that came with Sonar 7. I was not very impressed with Boost 11 though, but maybe I'll like it later on....I don't know. There are some little features that didn't make the Sonar 7 new feature list but one of my favorites is the ability to convert an audio track to Stereo or Mono just by right-clicking and selecting the option from the list (depending on the track of course). It makes things so much easier than having to go into the Bounce to Track menu. There are other ones but I can't remember them now. There's still a lot of playing pending with Sonar 7 as this is only the first week.



Anyways, I hope you guys can find other stuff that needs fixing in the upcoming patches. Please try replicating or trying the things I've done as to compare results. It would make things much easier to find the culprits for all of us.


Take care guys!

thanks for this! How do you find the audio engine efficiency and reliability in general? Did you upgrade from 5 or 6? I don't have sonar7 yet so i can't help with verifying any of the issues.

Nice initial review! Just wondering what computer hardware you are using with Sonar 7?

Jose,

Great review! Thanks for taking the time to do this this time around.

ORIGINAL: Duojet

thanks for this! How do you find the audio engine efficiency and reliability in general? Did you upgrade from 5 or 6? I don't have sonar7 yet so i can't help with verifying any of the issues.

So far the audio engine has been very smooth. I come from V5 and all the projects that were created there play fine in Sonar 7. The only problem I've had, as far as smooth playback goes, is when using the Step Sequencer and the new Mastering plugs. Using the SS has caused me Dropouts while changing a band in both Mastering plugins produces glitches in the audio. The latter has been confirmed by forum member Eratu as well as Cakewalk, so they know about this one.

Like I said, these two plugs sound really good but they're not usable right now because you kinda have to guess how things will sound. You move a band, it starts glitching and then stops when you release it so you don't get to hear how moving the band affects the sound until you stop moving it, and THEN you hear the change (but not what happens while you move 'em). I hope that makes sense. Peace!

ORIGINAL: saporta

Nice initial review! Just wondering what computer hardware you are using with Sonar 7?

Sure, my bad. Read my signature.

ORIGINAL: LionSound

Jose,

Great review! Thanks for taking the time to do this this time around.

Yeah, you got it . It has been real fun going through all these features and I still have more ground to cover. The change from S5 to S7 is amazing! I don't know what else I could want after it becomes more stable in version 7.2. Then again, there's always something right? .

Take care Lion!

I experienced two minor bugs that may be related to the fact that I went from version 5 to version 7, or possibly that I upgraded from Power Studio to Producer.

1. The Sonitus plugs were not updated, so that sidechaining didn't work with the gate and compressor. Had to delete them and re-install. This is because the previous Sonitus DLLs inexplicably had higher version numbers than the ones that shipped with S7.

2. Clicking on the "Manual" button on the VC-64 does not bring up the documentation. It is trying to open a nonexistent registry key, perhaps one that would have been created already had I previously installed version 6.

Hey bitflipper,

I also upgraded from V5 (which I still have installed) to V7 but I didn't encounter any of these bugs. I think the problem for you was installing S7 on top of S5 which Cakewalk recommends against. The way I did it when installing S7 was to slightly modify the default install path by adding a " 7" at the end to the "Cakewalk" folder. So I ended up with old regular "Cakewalk" folder plus a new "Cakewalk 7" one. Then I went into the plugin manager and included the old VST plugin folder path so that my non-Cakewalk plugins would be added to the list of S7 plugs. Sonar did a great job selecting the plugins as it didn't repeat the ones that were already listed, it just included the ones that were different.

The VC-64 does open the manual when I press the "Manual" button to bring it up by the way.

Sorry about this inconvenience.

Take care!

Nice work, Jose. Thank you.

Nice review.

I have not been able to use S7 for mixing because of a major problem I'm having with soloing busses. You can read about it here:

http://forum.cakewalk.com/tm.asp?m=1163503

Other users are experiencing the same problem but have been able to get around it sometimes. Unfortunately I cannot. I brought it to Noel's attention but he could not reproduce it on his end. I don't know if he has found anything since. Hopefully he has.

I found the LP 64 Mastering EQ annoying to work with. Maybe it's just my system but when I adjust the EQ the sound getts stuttery and fades out until I stop adjusting it. Then it can take a second to get back to normal once I stop adjutsing it. Does that happen to anyone else?

I found Boost 11 pretty cool. I liked the real time display of the limiting but not entirely sold on it.

Bit Flipper, good find on the Sonitus plugs missing the side chain. I'm sure that will drive a few people nuts. I installed over 5 and 6 so I'm going to check mine right now.

I havent tried a lot of the new MIDI features yet. I don't do MIDI programming on a regular basis but when I finally do I will explore the new stuff.

Eric

I think the problem for you was installing S7 on top of S5 which Cakewalk recommends against.

Actually, what they recommend against is installing the new rev in the same directory as the old one. The readme does not recommend uninstalling the old version first. It indicates that S7 would install in a new directory by default, allowing S5 and S7 to coexist. And in fact, SONAR did install in a new directory. But not the Sonitus plugins, unfortunately, which were/are in c:\program files\cakewalk\shared plugins.

This would normally not be an issue, but curiously the old plugs had an internal version number of 13.5.0.267 while the new ones were version 3.3.3.163. Most installers will not overwrite a newer version with an older one, so the files were never replaced.

The VC-64 "Manual" button issue does not apply to most installations for some reason. But for me it definitely does not work, and when I monitor it with regmon, it indicates that the VC-64 was attempting to read a registry key (HKLM\Software\Kjaerhus Audio\VC-64) that does not exist. If you wouldn't mind, Jose, could you check your system and see if that key exists?

ORIGINAL: Jose7822

The Step Sequencer: As we all know, this is one of the key features of Sonar 7 and specially for those who work mostly with MIDI. It is very nice indeed but it's also a major CPU hog (or is it my system?). Just having one instance of SS was enough to slow down my system. Whenever I tried to input notes in the Step Sequencer it would take a few ms to show the changes. Playback is not very smooth either, specially when first hitting the Play button. Have you guys noticed this?

This is troubling to hear. Is anyone else experiencing this type of behavior with the Step Sequencer?

Bitflipper, Sonitus plugins at version 13 smell a lot like an old versioning (13.x is maybe SONAR 4.x)?

If so, users that have or had SONAR 4 installed won't see their Sonitus plugins updated correctly unless they delete or remove them prior to S7 installing.

That could be quite a serious issue, hope some baker chime in and note down the problem.

- Mario

ORIGINAL: bitflipper

1. The Sonitus plugs were not updated, so that sidechaining didn't work with the gate and compressor. Had to delete them and re-install. This is because the previous Sonitus DLLs inexplicably had higher version numbers than the ones that shipped with S7.

This is quite a scary one for me.
I haven't checked nor have I tried to use the sidechaining yet...
I'll check what happened to me, upgrading from 6, when I get home.

I suppose a re-install would be required and the Sonitus loaded to a seperate folder?

No - a re-install to a new spot isn't required. You can use regsrv to update the correct drivers. Check Noel's response in Bitflipper's original thread.

Ciao,

Q.

ORIGINAL: Twigman
I suppose a re-install would be required and the Sonitus loaded to a seperate folder?

Just move away (or delete) all files which name begins with Sonitus in the "Cakewalk\Shared Plugins" folder and repeat Sonitus install.

That should do, without having to reinstall the whole app.
Mario

Hey Jose,

Great comments! I agree with just about everything, but haven't confirmed the sidechaining/bus bug (no time to do it yet) and V-Vocal pitch to midi yet. I will admit I was disappointed in the new LP mastering plugins -- not the sound quality, as I mentioned in another thread-- but the fact that they currently only work in one state. Any updates to parameters causes a state reset which causes gapping/glitches. So basically it is useless to try to automate them. And very difficult to really use them like I use other plugins, tweaking and listening for the subtle differences as I change parameters... the gapping/glitching really takes away from the experience. But Cakewalk said they will fix all that, hopefully soon. For some people who don't mind the gapping, they'll be great now.

I also noticed some strange, non-reproducible behavior with the step sequencer, weird lagging, inconsistent glitching, timing issues, but I believe it may have been caused by some third-party plugins. Not sure yet. When I created a NEW project and used only Cakewalk plugins it worked fine, as advertised. So perhaps with some more testing with third-party plugins we can find some areas where Cakewalk can improve its performance, or maybe it's 100% a third-party plugin fault. Or maybe there is some bug in there...

I have also been testing things out quite a bit in Sonar x64 under Vista x64. And while I did find that there were improvements in performance for me (thanks, Cakewalk!) it still is not quite up to XP32's level of stability, performance and just overall usability. BitBridge HAS been improved somewhat (thanks, Cakewalk!) but further testing is needed. I also might have discovered a bug with PSYN II in Sonar 7 x64.... something really strange was happening to me last night where some patches were not sounding correct -- they sounded different under x64 than in normal Sonar x86 in Win XP. This was very disconcerting and at this point I have NO idea what the cause the problem is... could be anything. But I'm not happy about it. Anyway, just another little negative about moving to Vista x64... unpleasant surprises that are starting to stack up and I'm getting to the point of taking a LONG break from testing and pushing Vista x64 and Sonar x64. At least untul SP1 is released and some patches to Sonar 7 and some driver updates. More and more I am coming to the strong conclusion that it just is not ready for prime-time, in my opinion. You know I've spent a lot of effort on it. Trying to get really great low-latency performance out of Vista x64 is like pulling teeth at this point. Set the latency really high (which is not my way of working) and it is passably usable.

But other than that, I've been very impressed with Sonar 7 so far! On the Windows XP "normal" side of things, it has been performing really well, and feels solid and consistent already. An impressive ".0" release in my opinion. The MIDI tools are excellent. I had forgotten how nice it was to have multiple controller lanes in the PRV. I didn't realize how much I missed this from Cubase. The customizable PRV tool is really a great idea, and I haven't figured out yet how I want to take advantage of what it can do. It is Sonar's new "power feature" in my opinion. Every once in a while a feature comes a long that all other DAWs will emulate. This is one of them. I also like the microscope MIDI tool, colored velocity indicators, MIDI metering, note-overlap indication, and another totally obvious and simple feature -- moving controller data with notes! Good grief, how obvious is that? Finally! So Sonar makes all that MIDI editing work much better than before, and I really feel I can get into MIDI just as well I did back in my Cubase days, and then some. Any minor, nagging regrets I may have had switching back to Sonar have been eliminated in this area. I still miss a few little things that Cubase had in terms of MIDI editing (like some simple tools to draw controller values) but I haven't fully explored the customizations I can do yet, and I think it more than compensates for that... there is a draw mode feature so I have to learn more what it can do... it might even be more powerful since it can generate controller values according to the grid spacing, I believe. Anyway, for all that MIDI stuff by itself, this upgrade has been worth it to me.

Hi Jose,

Thanks for the review.

I'm particularly interested in the CPU hog comments.
Can you post the specs of the machine you ran it on?
That way we can get an idea of how it would run on
other machines.

Thanks!

Eric.

ORIGINAL: bitflipper

I think the problem for you was installing S7 on top of S5 which Cakewalk recommends against.

Actually, what they recommend against is installing the new rev in the same directory as the old one. The readme does not recommend uninstalling the old version first. It indicates that S7 would install in a new directory by default, allowing S5 and S7 to coexist. And in fact, SONAR did install in a new directory. But not the Sonitus plugins, unfortunately, which were/are in c:\program files\cakewalk\shared plugins.

This would normally not be an issue, but curiously the old plugs had an internal version number of 13.5.0.267 while the new ones were version 3.3.3.163. Most installers will not overwrite a newer version with an older one, so the files were never replaced.

The VC-64 "Manual" button issue does not apply to most installations for some reason. But for me it definitely does not work, and when I monitor it with regmon, it indicates that the VC-64 was attempting to read a registry key (HKLM\Software\Kjaerhus Audio\VC-64) that does not exist. If you wouldn't mind, Jose, could you check your system and see if that key exists?

Ah! OK, I guess I misunderstood what they meant by install into a separate directory. But, in any case, I have confirmed that the Registry Key for VC-64 does exist on my system. If you want to create it manually follow this steps:

1 - Create the Reg Key "HKLM\Software\Kjaerhus Audio\VC-64".

2 - Right-click "VC-64" and create a new "String Value".

3 - Modify the new string value by writing "Manual" under Value name and the location of the VC-64 manual under Value data. It should be locate in:

C:\Program Files\Cakewalk\Vstplugins\VintageChannel\vintagechannel.chm

4 - Click "OK" and you're done.


HTH.

Thanks, Jose. That did the trick.

Eratu,

Thanks! I am more inspired about Sonar than ever before and it's all because of you . Like I've said in the past, we need more people like you in this forum. There are a few others, including those who have responded to this review, who also inspire me to make Sonar the best app ever.

But, anywho, what you have described while using the Step Sequencer is exactly what I'm talking about. I don't recall using 3rd party plugins while I tested it so I will try it once more to confirm this. On top of the weird "lagging, inconsistent glitching, timing issues" you describe I've also experienced Dropouts in some ocations. I think this was even at 512 buffers and my CPU meter in Task Manager was hovering at 60%, even though Sonar was only reporting around 15% CPU usage on each core. It's kinda like the Audio is behind what I see beeing displayed...very wierd.

I haven't even installed Sonar x64 yet. I might do that this weekend since I need to get some work done and stop playing around with Sonar 7 so much. But I've found it to be very stable appart from the few things I've encountered. We just need to keep at it so that Cakewalk can iron all these things out. Thanks again bro, later!


Eric,

I had already linked your thread about that bug under Side Chainning since I think it was introduced by this new feature. Thank you for posting this again though as it is very important that people are aware of it. I'm on the same boat as you with that bug since I haven't found a way to get rid of it and I can reproduce it 100% of the time with the same results.

A similar thing to what you're experiencing happens to me with the new Mastering plugs, except I don't hear a fading in or out. However, I do hear glitching/gapping audio until I release the EQ or Compressor band and it immediately plays fine.

As far as the Smart MIDI Tools, you need to try them out even if you don't work with MIDI that much. You will after you see what they can do. They're wicked cool.

Take care!


Now, the other Eric (ericyeoman) ,

I've included my signature, which has my specs, in post #6. But I'll include it here again, here it is :

Jose,

I read your review and by the time I was reading the the responses I sort of forgot you mentioned my thread. Sorry about that. But you are right, it doesn't hurt to have that posted again.

Thanks again for your review and deication to helping users on the frorum.

Eric

Oh by the way, my side chaining is working. But I only had S6 installed before 7. I mentioned having S5 and 6 instaleld earlier but I was thinking about my old machine.

Side chaining is so cool. To me, probably worth the price of admision alone.

Hi Jose

I read your comments about the step sequencer and I agree with you. I didn't have the confidence to ask about this 'problem' as I assumed it was an issue with my PC setup. My first attempts mad keen attempts with the step sequencer resulted in the PC freezing !

It seems to work okay as long as you don't 'push it' too hard :)

Cheers

Is it normal for a POST fader SEND to be louder than the main [Dry] OUTPUT?

ORIGINAL: popstar

Hi Jose

I read your comments about the step sequencer and I agree with you. I didn't have the confidence to ask about this 'problem' as I assumed it was an issue with my PC setup. My first attempts mad keen attempts with the step sequencer resulted in the PC freezing !

It seems to work okay as long as you don't 'push it' too hard :)

Cheers

Yes it does. It's great but I guess my system won't be able to cope with another version of Sonar if this keeps up.


I've made another discovery by the way. It seems that what eats all the CPU cycles is having the Step Sequencer window opened. Once I close the window the CPU level in Task Manager goes down considerably. So if any one can confirm this just follow these steps:


1- Open Session Drummer 2 and route it's output to the Session Drummer 2 drum map.

2- Click on the Step Sequencer icon to open it and start creating a beat. Then, play the beat from inside the SS not Sonar.

3- Open the Task Manager to check the CPU level. Compare this to Sonar's CPU level (way different no?).

4- Now close the Step Sequencer window but leave the Task Manager open.

5- Compare the CPU levels again. Did you see the change in CPU usage in TM?


Thanks a lot!

Hi Jose,

Very interesting, it went from 40% down to 8%.
(This was in the Task Manager as opposed to the CPU usage view inside Sonar 7 PE as you suggested)

Cheers

ORIGINAL: popstar

Hi Jose,

Very interesting, it went from 40% down to 8%.
(This was in the Task Manager as opposed to the CPU usage view inside Sonar 7 PE as you suggested)

Cheers

Awesome!

Thanks for taking the time to do this. I will be sending a report about this to Cakewalk, please do the same by filling out the form found here: http://www.cakewalk.com/Support/ProblemReporter/ This will help them correct the problem ASAP.

Take care!


EDIT: Feel free to include the steps I've provided.

For all those having Step Sequencer CPU Hogging troubles, make sure CPU Conservation mode is not turned on. I upgraded from 6PE to 7PE and it was turned on by default, making the step sequencer very unusable because of lag and the such. Press the "Pause" key on the keyboard to toggle between the CPU conservation mode.

ORIGINAL: eternal85

For all those having Step Sequencer CPU Hogging troubles, make sure CPU Conservation mode is not turned on. I upgraded from 6PE to 7PE and it was turned on by default, making the step sequencer very unusable because of lag and the such. Press the "Pause" key on the keyboard to toggle between the CPU conservation mode.

Definitely not using CPU conservation mode. Have you tried the step I've provided? Did TM show a higher CPU reading when the Step Sequencer window was opened as opposed to it being closed? Just wondering if you're experiencing a different behaviour.

Take care!

I finally got things up and running on Vista 64 this morning and it works pretty well. Even the Bit Bridge does a nice job of reading my XP32 libs like VSL Vienna SE. I'm going to load EWQLSO and Symphonic Choirs when I get home today to see how they fare.

I have noticed on both X64 and XP32 systems (I dual boot) that on Sonar 7, there's the occasionally glitch in the audio stream. It sounds like a tick or something. Very brief and I don't hear it when I mixdown to wav file. Just wanted to pass that on.

Really happy to have Session Drummer 2. Those drum sounds are GREAT. Love the ride cymbals in particular. The toms have a nice resonance to them as well.

No problems using the step sequencer here. Minor CPU usage (like 5-10%) when active. Im running 32-bit WindowsXP w/ all updates... dual core AMD 2.2GHz and 1.5G RAM. Maybe our systems are different enough to cause the SS to behave differently...

No issues here either - core2duo with Layla3g and 2gb Ram. Only have issues (Vista) if I lower the latency below 5ms. Haven't loaded stuff up on the XP side yet.

Minor detail but color presets only show up to Sonar 5, no 6 or even worse 7 color presets. Maybe a reboot is called for

Gerry

Dr. Mac and Blades,

Did you guys leave the sequence playing while checking the Task Manager? Leave the Step Sequencer window open while it plays the sequence and look at the TM, then close the Step Sequencer window without closing TM. Are you guys not seeing the big jump in CPU usage?


Gerry,

I think that's how it came from factory as it only shows up to Sonar 5 for me too.

ORIGINAL: Jose7822

Dr. Mac and Blades,

Did you guys leave the sequence playing while checking the Task Manager? Leave the Step Sequencer window open while it plays the sequence and look at the TM, then close the Step Sequencer window without closing TM. Are you guys not seeing the big jump in CPU usage?


Gerry,

I think that's how it came from factory as it only shows up to Sonar 5 for me too.

Thanks Jose, yes those LP 64's sure pump up the CPU just like the VC 64 does,; makes freezing a must for me. Haven't used the step sequencer yet and not sure I ever will.

Disappointed about no presets on the LP 64's because they are handy for giving you a guide line which you can then tweak from.

I haven't had much time to do anything meaningful but two things were obvious right away:

1) I can run in multi-processor mode now and no clicks or pops. I'm almost afraid to say it out loud but I checked performance using a large project that would have brought V6 to it's knees and it worked perfectly. Time will tell. I've been living with this problem for so long who knows. If the problem returns I'll say something but for now it looks really promising. Thanks for that!

2) The overall stability of the main work area (GUI) seems improved. The clips don't jitter and jiggle as much when you slip edit the ends. Almost seems perfect. Yeah!!!!

Everything else seems to be working pretty much as expected. I'll run a session with it tonite and see how things go. In terms of just the general audio portion of the program, there don't seem to be too many changes or surprises. Shoudl be an easy upgrade for me. Hope it is for you all too.

Thanks Cake!

I just confirmed a bug with Eric, another roomie over the phone. When you have a track with 2 sends on it and you solo one of the bus'es, nothing is heard and no meters move. After deleting one of the sends, the problem goes away.
Cj

ORIGINAL: krizrox

I haven't had much time to do anything meaningful but two things were obvious right away:

1) I can run in multi-processor mode now and no clicks or pops. I'm almost afraid to say it out loud but I checked performance using a large project that would have brought V6 to it's knees and it worked perfectly. Time will tell. I've been living with this problem for so long who knows. If the problem returns I'll say something but for now it looks really promising. Thanks for that!

2) The overall stability of the main work area (GUI) seems improved. The clips don't jitter and jiggle as much when you slip edit the ends. Almost seems perfect. Yeah!!!!

Everything else seems to be working pretty much as expected. I'll run a session with it tonite and see how things go. In terms of just the general audio portion of the program, there don't seem to be too many changes or surprises. Shoudl be an easy upgrade for me. Hope it is for you all too.

Thanks Cake!

Larry,

Could you please try this little test shown below and let me know your results?

----------

I start a new project in Sonar 7 by going to file/new and opening the 16 track template that comes with Sonar.

I import an audio file onto track one.

I route the output of track one to Subgroup One.

When I solo Subgroup One I don't hear anything and all the meters go blank.

If I just solo the Effect Send One bus I hear audio but the meter on track one goes blank.

If I solo Effect Send One at the same time Subgroup One is soloed I then hear audio on both soloed busses and the meters remain active.

If I completely delete the Effect Send One on track one I can hear sound on subgroup 1 when it is soloed. The moment I put it back on the track Subgroup One has no sound when soloed.

This is the best I can describe the problem. As I mentioned above, I can reproduce this over and over. I hope this can be confirmed. Otherwise something is screwed up with my installation of S7.

Thanks agian for your help.

Eric

Eric,

I don't think there's anything wrong with your setup cause I've confrimed this as well. I, like you, can reproduce it 100% of the time too. I've sent an error report to Cakewalk on this matter.

CJ,

Thanks for the info. I would also recomend you too write an error report to Cakewalk so that this issues gets resolved as soon as possible.


Take care both!

ORIGINAL: Hansenhaus

ORIGINAL: krizrox

I haven't had much time to do anything meaningful but two things were obvious right away:

1) I can run in multi-processor mode now and no clicks or pops. I'm almost afraid to say it out loud but I checked performance using a large project that would have brought V6 to it's knees and it worked perfectly. Time will tell. I've been living with this problem for so long who knows. If the problem returns I'll say something but for now it looks really promising. Thanks for that!

2) The overall stability of the main work area (GUI) seems improved. The clips don't jitter and jiggle as much when you slip edit the ends. Almost seems perfect. Yeah!!!!

Everything else seems to be working pretty much as expected. I'll run a session with it tonite and see how things go. In terms of just the general audio portion of the program, there don't seem to be too many changes or surprises. Shoudl be an easy upgrade for me. Hope it is for you all too.

Thanks Cake!

Larry,

Could you please try this little test shown below and let me know your results?

----------

I start a new project in Sonar 7 by going to file/new and opening the 16 track template that comes with Sonar.

I import an audio file onto track one.

I route the output of track one to Subgroup One.

When I solo Subgroup One I don't hear anything and all the meters go blank.

If I just solo the Effect Send One bus I hear audio but the meter on track one goes blank.

If I solo Effect Send One at the same time Subgroup One is soloed I then hear audio on both soloed busses and the meters remain active.

If I completely delete the Effect Send One on track one I can hear sound on subgroup 1 when it is soloed. The moment I put it back on the track Subgroup One has no sound when soloed.

This is the best I can describe the problem. As I mentioned above, I can reproduce this over and over. I hope this can be confirmed. Otherwise something is screwed up with my installation of S7.

Thanks agian for your help.

Eric

Yeah - I thought I saw someone else mention the same thing. I'll test this tomorrow but I have a feeling you've found a legit bug. I realize it's a bug and it probably affects a lot of people but it doesn't affect me as I never subgroup in Sonar. I use Creamware Scope to do all my mixing and signal routing and whatnot.

ORIGINAL: krizrox

I haven't had much time to do anything meaningful but two things were obvious right away:

1) I can run in multi-processor mode now and no clicks or pops. I'm almost afraid to say it out loud but I checked performance using a large project that would have brought V6 to it's knees and it worked perfectly. Time will tell. I've been living with this problem for so long who knows. If the problem returns I'll say something but for now it looks really promising. Thanks for that!

2) The overall stability of the main work area (GUI) seems improved. The clips don't jitter and jiggle as much when you slip edit the ends. Almost seems perfect. Yeah!!!!

Everything else seems to be working pretty much as expected. I'll run a session with it tonite and see how things go. In terms of just the general audio portion of the program, there don't seem to be too many changes or surprises. Shoudl be an easy upgrade for me. Hope it is for you all too.

Thanks Cake!

wow. this is exactly the news i have been looking for. if you get a chance to expand that would be great. would be interesting to hear from cakewalk if any changes were made that might cause this.

ORIGINAL: Jose7822

I've made another discovery by the way. It seems that what eats all the CPU cycles is having the Step Sequencer window opened. Once I close the window the CPU level in Task Manager goes down considerably. So if any one can confirm this just follow these steps:


1- Open Session Drummer 2 and route it's output to the Session Drummer 2 drum map.

2- Click on the Step Sequencer icon to open it and start creating a beat. Then, play the beat from inside the SS not Sonar.

3- Open the Task Manager to check the CPU level. Compare this to Sonar's CPU level (way different no?).

4- Now close the Step Sequencer window but leave the Task Manager open.

5- Compare the CPU levels again. Did you see the change in CPU usage in TM?


Thanks a lot!

Jose,

You are disgustingly correct. I just did your test, and Sonar's CPU meter does not display the HUGE CPU hit that an open Step Sequencer causes. If you minimize or close the SS window, then CPU levels drop back to normal levels. But when it is open, it is sucking up a vastly disproportional amount of CPU than it ever should. Amazingly, when I hit the "PAUSE" button to limit the screen redraws, then the SS doesn't draw as much CPU power again.

Now, I'll add that on my C2D CPU I can't notice the CPU hit at all if I am not using very many plugins. However, if I have a lot of plugins running, then this huge hit of the SS comes into play and it causes the weird behavior I was describing before, that you also had described. So basically, everything is fine until you are close to the CPU limits of your computer... and then opening the SS window causes all sorts of junk to happen since it goes beyond the CPU limits... and none of that is reported properly in the Sonar CPU meter.

Anyway, this is clearly a VERY unoptimized feature, and as cool as it is, I think this level of CPU use has got to constitute a bug, don't you? At a bare minimum, the CPU usage of SS should be included within the total Sonar CPU meter.... But overall, it's ridiculous how much CPU the interface takes.

Also, just to clarify on your instructions...

Step 1) should read "Open Step Sequencer..." not "Open Session Drummer..." to route its output to the Session Drummer 2 drum map. But technically even step 1 isn't needed to connect to Session Drummer since you can basically prove this with any plugin. I just verified this with z3ta, for example.

All you need to do is just insert any softsynth and then open SS, and then follow your steps.

Great job discovering that... have you had a chance to report that to Cakewalk yet?

ORIGINAL: Duojet

ORIGINAL: krizrox

I haven't had much time to do anything meaningful but two things were obvious right away:

1) I can run in multi-processor mode now and no clicks or pops. I'm almost afraid to say it out loud but I checked performance using a large project that would have brought V6 to it's knees and it worked perfectly. Time will tell. I've been living with this problem for so long who knows. If the problem returns I'll say something but for now it looks really promising. Thanks for that!

2) The overall stability of the main work area (GUI) seems improved. The clips don't jitter and jiggle as much when you slip edit the ends. Almost seems perfect. Yeah!!!!

Everything else seems to be working pretty much as expected. I'll run a session with it tonite and see how things go. In terms of just the general audio portion of the program, there don't seem to be too many changes or surprises. Shoudl be an easy upgrade for me. Hope it is for you all too.

Thanks Cake!

wow. this is exactly the news i have been looking for. if you get a chance to expand that would be great. would be interesting to hear from cakewalk if any changes were made that might cause this.

As I said, I didn't have much time to fool around but the quick test I performed already shows improvement. The project I used was pushing 100 tracks of audio and in V6 would have started popping just by pressing play (with MP support enabled). The project played flawlessly in V7. In fact, I tried to make it hiccup by resizing windows and doing various other things and nothing. Nada. Clean as a whistle. I'm keeping my fingers crossed but it really does seem like they have imrpoved the stability of the program. If I remember correctly, they changed something to do with screen redraws (I'll have to go look again to confirm) but there was some mention of something to do with stability improvement so this might be the ticket. I'll have better news to report in after a couple of sessions.

Has anybody mentioned the clicks and audio stuttering that occur when adjusting parameters on the LP64 plug ins?
For instance, when I insert a node into the eq, then start to adjust it, every time I grab it with the mouse, the audio clicks and stutters until I release the node, then the audio resumes normally.

Does the same thing in the Multiband Compressor.

ORIGINAL: rscain



Has anybody mentioned the clicks and audio stuttering that occur when adjusting parameters on the LP64 plug ins?
For instance, when I insert a node into the eq, then start to adjust it, every time I grab it with the mouse, the audio clicks and stutters until I release the node, then the audio resumes normally.

Does the same thing in the Multiband Compressor.

Yes, this is a known issue and Noel said they will work on improving the performance of the plugin... it has to do with the fact that the plugin is very CPU-intensive and has to reset its state every time a parameter changes... or something like that. Anyway, make sure you add your voice to the chorus of people who want this improved by submitting a bug report or feature request... not sure what they will consider it. As for me, I consider it a bug. Anything that hogs that much CPU to cause state change glitches is a bug these days, in my humble opinion.

ORIGINAL: eratu

ORIGINAL: rscain



Has anybody mentioned the clicks and audio stuttering that occur when adjusting parameters on the LP64 plug ins?
For instance, when I insert a node into the eq, then start to adjust it, every time I grab it with the mouse, the audio clicks and stutters until I release the node, then the audio resumes normally.

Does the same thing in the Multiband Compressor.

Yes, this is a known issue and Noel said they will work on improving the performance of the plugin... it has to do with the fact that the plugin is very CPU-intensive and has to reset its state every time a parameter changes... or something like that. Anyway, make sure you add your voice to the chorus of people who want this improved by submitting a bug report or feature request... not sure what they will consider it. As for me, I consider it a bug. Anything that hogs that much CPU to cause state change glitches is a bug these days, in my humble opinion.

Man! They are cpu hogs! I tried them out on a track I was mastering, I usually use Ozone 3, which when mastering a track usually puts my cpu usage at about 6%.

With the new ones it was in the 30s!!!!

ZOW!!

Eratu,

Thanks a bunch for confirming this. So far 3 people have seen this behaviour so it's gotta be a bug. I guess it was more obvious in my case due to my old Pentium D which could barely hang with just one instance of SS. It sometimes glitches the sound and the video feedback laggs behind the audio, depending on how complex the rhythm is. This is what prompted me to experiment some more with it to see what I could find.

I have informed Cakewalk about everything I've found so far, which includes another anomaly with KVM switches. For some reason, when I swicth computers using my KVM switch while audio is playing in Sonar the Audio Engine Stops playback. So again, if anyone can confirm this that would be awesome.

By the way, the steps provided by me earlier were merely one way to replicate what I was experiencing. But you are correct in saying that it doesn't have to be this way as long as there's a synth inserted in Sonar. The part about routing SD2 MIDI output to the SD2 drum map is not a necesary step but I included it anyways because it then shows the names of the drums in the Step Sequencer window (which just makes it easier to program drums for the experiment). But again, this is not necesary and can be reproduced with any synth as you have discovered.


Take care


Rscain,

This was one of the things I had encountered which I described in the beginning of this thread. Another finding is that there are no factory presets for either the LP-64 Compressor or the EQ which supposedly you can load by following these steps: http://www.cakewalk.com/support/kb/kb20070918.asp The problem with this is that only one preset loads instead of a bank of presets. I have reported this too but it wouldn't hurt if you did the same and mentioned the glitching you're experiencing when using these new plugs as well. You can do that by filling out this form:

http://www.cakewalk.com/Support/ProblemReporter/


Thanks!

double post....sorry.

Sonar 7 running well on a dual-processor, dual-core (4 cores) Xeon system (Dell Precision Workstation 690) with an RME FireFace 800.

I thought I was having issues, but everything is happy!

Sorry to hear about your troubles Qucifer. Seems strange that you are having the same problems I was with V6.

I installed V7 into a clean OS (I used Ghost to make myself a backup of my recording partition with everything installed and tweaked except Sonar). Maybe - as a last resort - try installing Sonar into a clean installation of your OS. See if that works.

Also you can use V6 and V7 side by side - no problem there.

btw - I just finished a two hour session and everything worked perfectly. No pops or clicks at all.

PS - I see you changed your story - cool - glad to hear it's working OK for you.

ORIGINAL: Qucifer

What is Cakewalk's policy with licenses for previous versions. Now that I've registered 7, am I no longer entitled to use my license fo 6?

You own the rights to use each registered version for as long as you live.

I'm kinda seeing the same issues as you but maybe not as frequently. Just make sure that you have configured S7 exactly as you have S6.


EDIT: Good for you Qucifer. I'm glad it's working for you now. Take care!

I'm embarrassed to admit that I did have a buffer size setting different between the two installations. Now, with that sorted out, everything appears to be comparable.

When I started out with issues, I headed here to see if others were experiencing anything similar. Sorry for jumping the gun! :-)

So the Cakewalk folks don't mind if I run older versions simultaneously with new versions? I know other vendors annul licenses for previous versions once an upgrade has been made.

ORIGINAL: Qucifer

So the Cakewalk folks don't mind if I run older versions simultaneously with new versions? I know other vendors annul licenses for previous versions once an upgrade has been made.

No. They actually encourage you to have both installations until things are stable again in the new version. Then you can proceed to delete the older version if desired. Just make sure you have everything you need backed-up before doing this (like color schemes, plugin settings, instrument definitions, etc).

ORIGINAL: Qucifer

So the Cakewalk folks don't mind if I run older versions simultaneously with new versions? I know other vendors annul licenses for previous versions once an upgrade has been made.

I've never heard of that.

In any case, the limitation with Cake is that you can't resell your program.

The wierdest thing is happening now after installing Sonar 7 PE on Vista (32 bit).

The GUI's in DimPro, DimLE, SD2 and DropZone are no longer giving real-time feedback in the controls.
For example turning a pot does not visually change until the mouse is released. The tooltip that appears above the control does give feedback however, as does moving the control with a control surface.
Rapture, RaptureLE and other instruments are all OK.

I decided to keep both Sonar 6 and 7 on my XP and Vista x64 partitions, but wanted a fresh install on Vista 32. I uninstalled Sonar 6, removed shared folders and registry keys, then installed 7, and the problem appeared.
On Vista 32, I had no problems previously with DimPro or SD2.

It seems Sonar 7 has possibly updated some shared library somewhere. The problem also occurs if I use these instruments in another host (I tried them in Kore, and in Plogue Bidule).

Looks like a return to XP for now. Any ideas / similar problems anyone?

Hey Guys,
Thanks for the insight on the Step Sequencer. This is the main reason I made the upgrade. I always liked this in Reason.

later,
Chipstar

After importing a project into sonar 7 which was originaly recorded in Sonar 6, 7 failed to accept the VC 64 plug ins on that project. it loaded the project and although the VC 64 could be seen it the FX box it could not be opened and even stranger it willl not allow me to open the plug in manager to rescan it.

I'm now going for a reboot, anyone else had this problem. I won't report it yet just in case I am quietly going mad.

Most strange on the reboot the VC 64 is showing as being a missing plug in and the Plug In Manager has still dissappeared. **** why did I remove 6, OK any ideas you folks?