Terry Kelley

If I was the CW developers, I would focus first on professional users and those that have shown they use a large number of the features as much as possible. Among several reasons, I don't see myself being in that group. I started with DOS and bought various versions until Sonar but didn't expect that to have any affect on their decision. Based on what I have seen on this forum, I'd bet we could guess at least 10 people that were selected and rightfully so. My expectations for selection were low. So I've decided to focus on being impatient!

Yes, that plays to my point. The CW developers don't have access to that part of the VST to make it happen. The VST developers need to do something first.

I thought the goal here was to change what preset was default. Where the VST(i) goes "I don't know what to do so I will load this one." Maybe semantics are at play here.

I am wondering how CW could get the VST(i) to load the preset. Seems it would require the VST(i) developersto make some changes. I like the idea but implementing it might need to be pushed in VST4.

I see this periodically with plugins that want to call home or after an automatic update to the plugin. Cherry Audio is notorious for this. I just reinsert the plugin and it's fine.

I think the developers have been clear that there will be plenty of time to use CbB while we decide if Sonar is worth using or moving on. It appears to be an extremely fair offer.

Well I am hurt and will need, oh, a million dollars to feel better. No, only a million dollars will work. No worries, I like your posts. 👍

Boy, you read a lot more into what I wrote than anyone could imagine. LOL. Well, except for our resident Eeyore!

The excitement of a new Sonar version "later in the year" has drifted into being a bit tired of waiting. If I will be compelled to switch to a competitor due to price or a subscription model I would like to get the show on the road. I have been playing with two other DAWs and they would serve me fine if staying with Sonar isn't worth it. But I am a private user, not commercial. Me remaining "faithful" isn't going to help any company. But at the same time I don't want to miss a potentially awesome DAW update. And all of this while I stare at my stack of Cakewalk software starting at the DOS 1.04 version. So I sit here tapping my finger on the desk waiting.

I searched the EZD forum and the answers always jump to a workaround but no solid conclusion on if this should work. And no, RTFM doesn't help. 1. Add an EZD drummer instance to Cakewalk. Within EZD add some drum grooves. 2. Click Add a Song Track and select that track. 3. Add some tamborine grooves to this second track. 4. Hit Play (DAW or EZD.) EZD will only play the selected track, not both. My work around has been to add a new instance to Cakewalk for each EZD instrument (e.g. Percussion.) Just since there is this track sitting there, I alway thought EZD would play them all. It seems to me EZD should play all of the tracks not just the selected track, but NOOOOOOOOOOOOOOOOO!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! It can't. I finally got a direct answer on the TT forum rather than work-arounds. I know the work-arounds : I use them! I was just surprised it won't and decided to make sure I hadn't missed something.

Something I've been doing more and more is to mix the song with whatever effects I want at whatever level I like. Sounds good! Then I turn off all the effects and reset all of the levels. Then start mixing again without the effects (unless it's one recorded on the track itself.) I find that I don't tend to add in the same amounts of compression/limiting and reverb. EQ tends to return to the same levels though. As I am building up the track I just add too many effects at high levels and while I like that mix, shutting them all off and remixing always gives me an improved mix.

I've found that I can usually load a problem project by opening a different project first then load the problem project. Not sure what is happening. Maybe it's moving the problem in memory. But this will usually the load the project and the cause of the crash is one of the last VSTs I loaded so I can delete that and re-save. Loading more than one instance of EZDrummer 3 is often the issue too. That will usually cause problems at some point.

I tried it and they would all consistently open regardless of the workspace but I also confirmed it will close any that are already open when you do it. I think pressing F should close all and allow you to open all at once and get re-sync'd.

Now if I had said that ...

The Cooper Time Cube has a 14ms left channel delay and 16ms right channel delay. This gives a well balanced stereo effect. Welcome to plastic tube delay technology! This is what Greg Lake used often on his voice and guitar. Note the 10k roll-off. The Cooper Time Cube is easily emulated in the Sonitus Delay.

. Beat me by this much!

The natives are restless.

I didn't think "later this year" meant 'late in the year.' I understand and support the need to make both Sonar and Next be the best they can be but this started in June and I think many of us incorrectly assume 'a couple of months.' We were wrong. Oh well.

I've run into this multiple times. Mostly on projects with lots of VSTs. It doesn't happen a lot but enough that I have to deal with it periodically. The solution for me is to open a different project that WILL open without crashing, leave it open and then open the problem project. That seems to work every time. At that point I usually remove the last two VST instruments or effects and re-save it. Then figure out which one is the problem VST. It's almost always an effect but not always the same effect. It's like there is some limit I've hit or I've displeased the VST gods. If I can't figure out the problem VST, I will try freezing tracks to at least make the project usable but I will often have a problem of crashing when unfreezing the tracks if needed later.

Define "soon."

This is starting to feel like the first Windows announcements.

I got the impression (and only an impression) was that Sonar would be the same code and features as CbB but with an interface better supporting the scaling of various elements. No doubt there will be some additional features but what it can do will be based on CbB. So all of these bug fixes matter.

I expect this to be resolved in Sonar with the new interface. One of the developers mentioned that scaling limitations was something they wanted to correct.

We used a pair of Dokorder 7140's with modded capstans to run 15ips. Worked great for what they were. We moved to a pair of synced Sansui 6-tracks. Worked ok with noise reduction but was never going to be pro sounding. Tascam T80-8 was nice but really the same as the Dokorder - just on one transport. Eventually switched to ADATs and then multitrack DAW. I took CbB being free as a gift for the time it's lasted. Can't complain. I do hope Sonar meets my need (function and cost.) If not, there are other options. I am certainly hopefully but I've been fooled before.

I agree. The Sonar/Next announcement in hindsight seems a bit early. I don't think a 4 month+ heads up did anyone any good. But if you want to see it, you gotta wait. So as suggested, I've gone and done other things. When they finally show up I'll take a look.