musikman1

Chappel, thank you! 😎 I had a feeling it was just somewhere else! When I looked it up online CW Documentation I didn't find it there. Glad it's still around, very handy tool!

I haven't had to use it in a long time, until today. Used to be able to highlight an audio clip and attach a gain envelope by going to Process/Apply Effect/Gain Envelope, but I see that option is changed to just "Gain", and a dialog box pops up instead, which seems to only able to effect the entire clip, or whatever portion of the clip you highlight. That does me no good if I want to create a gradual gain curve up or down. It was a good alternative option instead of having to record automation. I used to be able to insert a gain envelope and see a gain line with nodules across the clip (similar to how an EQ looks), and you could add nodules and increase or decrease gain, or create a gain curve in any area of the clip by dragging up or down on the nodules. Handy little tool for certain situations. Did they do away with that, or is there another way to access that now? I also tried the right click menu, but didn't see anything there either. Thanks! MM

Thanks for the replies. RBH, some of my older tracks were stereo, some were mono, so I've been going on case by case basis, but I understand what you're saying. There's not much I can do about panning the tracks that were recorded in stereo, but a lot of those were keyboard/synth tracks. Back then I was just starting out learning the guitar, so I wasn't really good enough to record a lot of my own guitar tracks. I'm a keyboard player primarily. lapasoa, I see what you're talking about, but apparantly I'm not using it.....what's the difference between the Send panel in the Console View, and the Output in the Track View? I'm asking because right now for example I have all the Acoustic Guitar tracks' Outputs routing to the Ac Guitar Sub buss, and that Ac Guitar Sub buss routed to the Master buss, and for panning I'm just using the Pan slider in the Track view. The Send panel section in the Console View is grayed out right now because I haven't entered any destination, so I guess I'm bypassing that option the way I have it set up. I guess what I'm trying to say is, wouldn't each method of panning accomplish the same thing, whether I'm using the Pan slider in the track view, or the Pan knob in the console's Send section? DeeringAmps, thanks for mentioning the FX, I had not thought about the FX may be causing the ghosting at the center, I'll check that by soloing, good idea.

Hi Friends, I have been going through some of my older projects that have been recorded on older versions of Sonar/Cakewalk, and were saved as bun files. They are loading into Bandlab as project files just fine, no issues there. I wasn't in the habit of using sub busses very often back then, so I've been re-working the routing of the tracks, giving each instrument a color theme, and setting up submixes/busses for each instrument, in an effort to better organize and have more control over the mixes. This has worked out good so far. So if my project has 4 Acoustic Guitar tracks, I would set each to route to the Acoustic Guitar sub buss I have just added, which in turn routes to the Master output buss. I'm no expert engineer by any stretch, but after watching a few Cakewalk YT videos, as far as I know, this is the standard basic setup that will get the job done, and certainly more efficiently than the way I used to set up my mix. I've also begun to move my FX from the main tracks to the sub buss, as long as the FX is the same for all the tracks in question. What I've noticed in the process, is if say all the Acoustic Guitar tracks are panned differently, let's say two are panned at 9 o'clock, and two are panned at 3 o'clock, when they are sent to the Acoustic Guitar sub buss, the panning transfers ok, but if the sub buss is panned at center, I also seem to be hearing all four tracks "to some small degree" in the center of my mix. Now I don't know if I just think I'm hearing it that way or if it's just a result of how everything is panned, or if it's because the sub buss is panned center. So I was wondering if this is typically the best way to maintain the pan settings of the original tracks now that I'm routing them to a sub buss. If anyone has suggestions for setting things up a different way that might work better, I'm open to hearing your thoughts.......or if I'm actually going about this the wrong way, then please let me know where I'm off. Much appreciated, will check back later. Thank you! MM

Hey Nigel, thanks for the information. I have a full version, but according to what you're saying about needing 64bit, I'll need to upgrade. For now I could just record tracks in R5 and export the wav for import to Cakewalk. Not the same as rewire, but it will suffice in some situations for now until I can upgrade.

Hi, anyone have a line on where I can get information on how to setup Propellerhead Reason to record tracks within Cakewalk? For some reason my searches only turn up info on upgrading to the most current version of Reason, and the rewire info I found seemed to be for old versions of Sonar, not Bandlab. I have a much older version of Reason (5), but I believe it can still be done. I had done it years ago, but my memory of the procedure has since faded. Just looking for some basic info would be helpful for me to learn how to set it up again so that I can record tracks using Reason's sounds and modules, and make it sync to Cakewalk project tempo for any drums or percussion tracks. Thanks in advance, much appreciated. MM

I understand, thanks again. Guess I'll have to go through and determine if I still have any VST2 plugins. I think I remember seeing a few that have the option of being used as either VST2 or VST3. If I remember correctly, I think in certain plugins' window there's a dropdown list where you can choose to use it as either 2 or 3, I could be mistaken.

Thanks for that info, so can VST2 plugs be used at all? If they need to be moved out of the VST3 folder, just need to be placed in a separate folder, then the scanner will pick them up once that folder is added to the scan list, correct?

Hey scook, thanks, appreciate the quick answer. Have you found the newest version to be stable in general?

Hi, Do I need to first uninstall/remove my old version of CW Bandlab before installing the newest updated 2020 version, or does the new version install like a "patch" over the older version? Also, has the newest version been proven to be stable? I have some older Sonar bundle files that I can load into Sonar Platinum just fine, and once converted to project files, they seem to open in CW Bandlab pretty well. Just want to make sure I'm not going to be dealing with any issues after installing the new version, because I haven't yet finished converting all the bun files. Thanks, any help appreciated.

This topic is from the old Cakewalk/Sonar forum. I purchased IK Multimedia's T-Racks Leslie plugin, and to my surprise the Leslie's slow/fast Rotary switch did not automatically work with my MIDI Controller's ModWheel. Later in the old thread you will see a workaround that will get things going in case anyone here has this plugin and is experiencing the same issue. Simeon said he will eventually post an updated video for this workaround. Thanks to all who helped me get this going, and IK Multimedia Support has been notified of the issue. Whether or not they are going to put out a fix for it remains to be seen, but at least they are aware of it. Here is the link to the thread in the old Cakewalk Forum: http://forum.cakewalk.com/TRacks-Leslie-plugin-not-working-with-my-controllers-ModWheel-m3807697.aspx

Thanks Larry, just read the thread. Haven't tried it yet, but next time I need to do that, which will likely be in the near future, I'll give that a try, as most tracks in my project are audio. I'll have to go through and read it again though, because just reading through it for the first time it's a little confusing, but the steps seem to be fairly simple to do, and it obviously has been proven to work. Thanks again, much appreciated.

Thanks guys, I will try these suggestions and post result. Update: Ok, I tried dragging the clip into the timeline, and Melodyne did take over and went through its analysis of the clip and changed it. I think the problem is that the guitar I recorded wasn't close enough to perfect timing, there were also parts of it where I had make a couple of performance errors, which probably threw the overall timing out of sync with the metronome I used. The process did accomplish something though, it made the guitar clip line up timing-wise to the drum loop, however, the project tempo got changed quite a ways off from the original guitar clip tempo of 89.89, it got changed to a much slower tempo of 77.66. Drums and guitar are synced much better though, even with the tempo being slower. At least I can hear if this particular drum loop will be suitable for this guitar rhythm, and if not I can audition others, which is what I'm going for in the end anyhow. I'm wondering if now that Melodyne has adjusted the guitar clip, maybe I can speed up the project tempo and somehow get the guitar clip to respond back up to around 90.00bpm? Gonna give it a try, I know one way might be to enable looping for that clip, not sure what that result will be yet though, since the performance errors may throw any type of audio quantizing off a bit..

Hi, trying to do something simple here, but haven't needed to do it in awhile, and haven't yet had an occasion to try this in Sonar Platinum, and can't seem to get it to work. I was away from my PC so I recorded a basic rhythm with my acoustic guitar along with a metronome click into my voice recorder of my phone, then emailed the MP3 to myself so I could get it onto my PC and import it into a track in Sonar Platinum. What I want to do is set my project tempo to "roughly" match the tempo of the rhythm guitar clip, then audition some drum loops to find a drum beat that suits the guitar rhythm, and it doesn't have to be perfect because for now I just want to find a good match for it so I can make a drum track to practice that guitar rhythm to. (Eventually I'll re-record both drums and guitar for an original song). The empty project tempo began at 95bpm when I first imported the guitar mp3 to a track. I double clicked the guitar clip and checked to see that Sonar indicates the clip's original tempo to be 89.893 bpm. In past versions of Sonar, normally I would just adjust my project tempo accordingly, in this case to 89.893 to match the clip. Then I would insert a drum loop from my library into another track and the drum loop (groove style clip) would automatically snap and align to the project tempo, this would get both tracks at least close to the same tempo. For some reason this is not happening as I remember it. What I have is the guitar clip sounding obviously slower than the drum loop. I know the drum loop is conforming to match the project tempo changes, because I tested that by increasing the tempo to a very fast setting, and the drum loop follows. To my way of thinking, if I set the project to match the guitar clip's original tempo at 89.893, then drop in a drum groove clip to an empty track, they should both sound like they're playing at least relatively close to the same tempo, even if it's not exact. Is there now a setting for tempo for each individual track or something I'm missing here? Any takers on this one? Thanks in advance.

Thanks, I was wondering if I should just keep the original version for now, seeing as how I've been reading there have been some issues with the recent update. Think it's worth updating?...have to think which is the lesser of two evils, keeping the original, or updating to a possibly buggy new version?

I got an email about a patch, anyone know if this patch is also for free version that came with Sonar Platinum, or is it only for users who have purchased the full version?