John Vere

I’ve never noticed that. I have worked at 256 for years now. I never have to change the settings. I only had trouble at that setting with a Motu interface. It would sometimes bonk out. But like I said I only open short phrases. And I render immediately.

That’s funny I was just sending those links and you guys posted. Thanks Here’s the whole playlist which will walk you through everything you need to know to get started.

This is what happens when sample rates are different. Choose a sample rate 44.1 or 48 and set all apps to use that. Even set this in Windows settings.

There’s at least 10 threads here with this topic and instructions please just look at the most recent threads

What Greg said. You open the vocal clip as a regional effect. Works best with short clips around 4 to 8 measures. When done always render or you are loading up your CPU as it has to process in real time. Therefore the audio issues.

Loopback is definitely a new thing on interfaces and it’s only a handful that will have it. The Zoom AMS 22 @$80 is the least expensive then the Steinberg UR12. I have it with my Motu M4 and my Zoom L8 and it gets used a lot. In the past the easiest way was simply creating a Loopback using short patch cables from out to in. I had 3/4 outputs but windows can’t access these. So you need to use 1/2 . You use headphones to monitor. Just don’t turn on input echo when recording. And another option is lots of app’s like OBS or I think even Audacity can record directly from the internet. Cakewalk can’t without loopback. I know I used Gold Wave the other day to record a song I was wanting to learn on my office computer that only has Realtek. Only some Realtek cards have Loopback or sometimes called “ What you Hear”

You open its location in the VST folder and right click then choose more options ( w11 ) and then use create shortcut But what you can do as well is keep the project open and after the export open the location dialogue from the blue toast and then open You Lean in Cakewalk and drag and drop from the export folder. I do this on my Laptop but on my main computer I have the Desktop shortcut on my second monitor and the system tray.

The drag and drop reading is the most accurate and in my experience is very accurate. I have a bunch of other analyzing tools and they all seem to agree on the loudness but You Lean will catch true peaks none of the others catch. I first thought it was just being inaccurate but I read the info on his web site which explains why it catches those peak at a per sample level. The others are just averaging it out. They would never be audible but I found it was great way to test brickwall limiters. The Loud Max and Boost11 won the shoot out of 15 free BW limiters. Any way back to real time VS drag and drop Real-time readings give you only a ballpark and you have to play the whole song. And as I said in the other thread- make sure the YL meter is the very last thing in the Master bus effect bin. The master fader has to be at unity. Mute the master to double check nothing is bypassing it. I would test the integrity of MP3 by exporting as a Wave file. Then compare it to the MP3 version.

Mix recall can be used between projects that share the same track layout. So a live recording is a perfect situation. 1. Get the first song sounding the way you want it and save as a Mix scene. 2.Open song 2 3. Open the mix scenes folder of song 1 in the browser and drag and drop the saved scene into project two. 4. All the settings and effects you used in song 1 will populate song two. 5. Repeat for each song. I made a tutorial last year about all this but I think I deleted it as it only got a couple of views. Not many people record bands anymore.

The only way to get the delay caused by latency down is to be able to run at a lower buffer. Generally under 128 becomes less noticeable if your interface drivers are also capable of lower latency. Every driver is a little different and the lower price interfaces will often have slightly worse performance.RME is one of the few brands that seems to have better performance. Example your Focusrite probably has around 12 ms of RTL at a buffer of 128. When an RME might have 8ms at the same buffer. Almost any interface can be made to get as low as a 32 ms buffer but only on a very high end system. And then only if the project is stripped clean of process hungry plug ins. About all you can try is to freeze all your synths and bypass all your effects except the guitar sim while tracking and try a lower buffer. You should be able to use 128 with a Focusrite..

That’s the thing, I read about people issues daily and it always comes back to it’s not an issue with Cakewalk, It’s almost always something caused by a plug in or computer , hardware issues For sure it still has a few weird little bugs but those are so on the very fringe of what the majority of users would even be aware of. I spend a lot of time working in Cakewalk and last time I had a crash was 100 % because of a plug in. I have never had any issues ever outside of plug in issues. The latest version of Cakewalk is BETTER than the last version because they fixed the bugs they were aware of. The rest we are told will be addressed with Sonar. And as we speak there’s an army of people swatting any bugs that they find there. So holding out on the last release is only based on miss information you have gathered. I’m also in the middle of dozens of important projects and I updated to make sure I was using the BEST version. Having backup copies of all my projects is more important than thinking upgrading software is dangerous .

When @Sistine gets the activation notification they will have to either install the latest version or abandon Cakewalk. This was made very clear to us. You are on borrowed time. Retuning to Sonar is a better option than learning a new DAW but it’s on thin ice too. It requires that Command Center can be accessed to install. You still need to be on line. It’s offline system is long gone. Staff have said that for sure off line activation for Cakewalk would be reinstated but it was a very low priority as it only matters to a handful of people. And I would guess that once Sonar is up and running there will obviously be a new Command Center type product manager where they will hopefully transfer over our legacy products. But they are legally not obligated to do that. There will definitely be a change to how things work.

There’s a tool called the Plug in Doctor that I played around with a year ago. It was free to use in a limited way but I’m too dumb to interpret its readings. I would think lots of folks probably could though.

I have recorded dozens of live gigs. I create a project that is set up with everything and before the session or gig I save a dozen or more inside the same folder. Each has a sequential name or number. These will populate the start screen recent list. At a gig I don’t have time to fuss so I open a bunch and minimize to the bottom. They are all set to record. I usually record 6 songs or more in a row or a whole set. It’s easy to break these up later back at the studio. If it’s was a session I’d have time to use individual projects. So I just have to open them from the start screen. If we have a set list then they are already named. They open super fast because I don’t put any effects on them. I do the later using the mix recall trick. So the routine is finish recording a song then close to save. Open next song which is all ready to go. 20-60 seconds between songs. Basically the trick is the preparation before hand. Then to not use templates but individual projects that are named and armed and ready. They can each have there own folder and audio folder or use a shared folder and audio folder to start with and be “saved as “ later to clean things up.

It’s always a plug in! be it instrument or an effect. Some are what we call light load some are heavy. I personally avoid the ones that are heavy. Actually I’ve never had issues with TH3. I’m not sure where it stands. It would be cool if someone has made a chart showing all the common plug ins and how they score load wise.

I submitted the NDA a month or so ago and I got an e mail thanking me for submitting it. It said I would be contacted with further information about access to the software. Nothing since.

Did you try dragging the track to the time line? I do this a lot and now with Next I can extract the drums as a separate stem so the tempo map is very solid. Audio snap never worked for me. To much fussing and it’s still wrong.

I asked because I was thinking there might be an actual different driver for the Solo and possibly the driver for the 2i2 was still installed and causing the issue. But I see they now use the Control panel to install the drivers. That message tells you that there’s a sample rate conflict between 2 programs being open. So double check that both Sonar and Guitar Rig are using same sample rate. In my video where I show you how to set up Windows sound settings you’ll see I uncheck the box that allows the device exclusive control. I find this allowed me to run multiple music apps at same time. But they all have to be set with sample rate matching. And nothing wrong with using Sonar Artist. I would think twice about starting to use Cakewalk by Bandlab at this point in time because it has now been discontinued. It will soon be replaced by Sonar again. And guess what. From what the staff have said it seems they will bring back versions like Artists again. So I would just watch and wait. I’m with you on why bloat the software with features you don’t need. I still have Sonar Home Studio installed and only feature missing is the regional effects. But I can record audio and midi and use any instrument or effects I want including Melodyne. So I’m hoping they return to having the different versions option at those same price points.

You have so many things going on that will cause you grief that I hate to depress you with them. In the wise words of ?? I forgot who. But. “ Keep it Simple “ Or was that “It’s 5 oClock Somewhere “??

If you look in the normal forum for this there’s dozens of threads of this topic.

All 3 you mentioned are well known as being CPU intensive. How can this thread be 3 pages long and this was not obvious? Either we are not being very helpful or you are not focusing on troubleshooting methodically but as I say.” It’s always a plug in! “.

And you installed and are using the Focusrite ASIO drivers that are for the Solo?

Edit- Better instructions below.

It’s always a plug in