Lord Tim

That's coming up as an error too: Looks like a 500/502/503 server error.

Weird... obviously not typical behaviour. If you do a VST scan (go to Preferences > File > VST Settings, press the SCAN button), do they appear then? What happens if you check Rescan Failed Plugins? It's possible some Windows update has damaged some libraries too. Have a look here:

I always found the drums pre-1983 to be pretty flat sounding myself, even if they had a lot of room mic in the mix. Then it was nothing but loud overheads (for heavy rock / metal anyway) and now it's very.... triggered. it's so tight that the excitement is kind of squashed out of it a bit. A lot of modern prog suffers from that for sure, unless they're deliberately going for a retro sound.

It *shouldn't* but there are some cases where things can corrupt over time and add up. I'm going to be a hypocrite and say "try to avoid using TTS-1" just for that reason alone, although I still tend to use it despite the risks. Apparently if this is the first plugin inserted into your project, it tends to work correctly and the speculation is that under the hood there's some old 32 bit code that's wrapped in a 64 bit container that's not playing nice. I personally haven't had TTS-1 corrupt a project at all (and certainly not the file system), but it's definitely made them crash more. Useable sounds, but use at your own risk, basically.

TTS-1 is crash-prone, unfortunately. This is old Roland code that the Bakers have no access to inside of the plugin. I'd almost certainly say the crashes will go away if you take that out (or bounce that down to audio, and remove the effect). My system is super stable but I can almost count on TTS-1 to crash it fairly regularly when I use it.

Definitely not normal, I do this all the time. What effects have you got in your project? Are you getting a crash log?

Yep, same! By the sounds of it, it's going to be a facsimile of the current interface, more or less, so it still feels familiar, but throw that on a 720p screen and everything will shrink, or a 5k screen and everything will scale up properly. How awesome would it be if you're out gigging with a 12" laptop screen and all of your UI elements fit well? Genuinely useful! It wouldn't surprise me if there was some refining to keep the experience consistent between Sonar and Next though, just to make it comfortable for people to jump between apps, but I don't think there'll be a lot of stuff in there to make people freak out. (Watch me be wrong now ?)

I mean, it makes sense for me to do that even if I got nothing more than a "supported CbB" going forward. I work super fast in Cakewalk, my studio is built around it, all of my legacy projects are in it... yes, I could move to other software but most (all?) other software on this level is paid anyway so it makes no sense to go anywhere else for me. But I think we all saw the Bakers in the "Clunky" thread I made a while back. They're listening, and I think Sonar will deliver.

From what I understand, this new scalable interface is like a year's worth of update alone, even if nothing else was added. I know that doesn't sound particularly sexy or groundbreaking to differentiate it from CbB but the ramifications of this going forward is huge. But I'd be super surprised if there wasn't a heap of other stuff being done aside from that too.

Not typical, but sometimes this can happen if your Picture Cache is full. Try this: close down Cakewalk, and navigate to your Picture Cache folder - typically that will be in C:\Cakewalk Projects\Picture Cache although you'll be able to find out exactly where by going into Cakewalk's Preferences > File > Audio Data and looking for the path there. When you're in the Picture Cache folder, just delete everything in it. When you load your project next, it'll take a while to rebuild all of the waveform pictures, but this should prevent this from happening again for a good long while. That said, the bit about the bar disappearing is an interesting thing too. Can you show a screenshot of what you're seeing? It's possible a clip could have gotten muted and Display Muted Tracks in Parent Track in the View menu in Cakewalk has been deselected.

This is a "my car won't go, what's wrong with it" kind of question, unfortunately. We have no idea why without any more information. Check out John's excellent video first to see if something in there might help. If there's no joy, explain to us what you mean by "can't record anymore" - do you mean Cakewalk won't open, or you can't select the record button, or when you try to record it doesn't move or it does move you're not getting any audio... etc. The more information you can share about what you're trying to do, and what you're seeing the better. Screenshots of your main window (especially showing the Control Bar at the top of the screen) and your Preferences > Audio pages would likely be useful too. There's always a chance there's some issue outside of Cakewalk as well, but let's work down from John's video and see how far we get.

Yeah, there's definitely a good argument for some interfaces having some kind of pad in between the instrument and the device (the first gen Scarlett 2i2 devices were notorious for clipping with active instruments plugged in - that was fixed with 2nd gen onwards), but I think you'd have to really be pushing things pretty damn hard to actually do any damage. Certainly possible, but very unlikely. But yeah, there's nothing wrong with throwing the DI in front if you do need to pad the signal, but if you can avoid it, I'd say that'll give you a cleaner signal.

I'd argue that if a device is so sensitive to a line level signal that it could need repairing is best suited for a nearby bin...! I'd also argue that knowledge base article is kind of ridiculous and the results would be nowhere near as extreme as that.

So long as the levels are OK, there's no reason you can't run the XLR out of your mic pre into the XLR ins on the front of the Audiobox. These interfaces don't have specific mic/line/inst selection or pad switches, so I'd assume that they've got a pretty huge range on the input gain knobs. I'd try it and if it still clips then sure, nothing wrong with throwing a DI in the way and using the pad on that to get the levels down, but try the gain knob at its lowest settings first - the less stuff in the way of the chain, the better.

Do not use Bandlab Assistant. This is a very old thread that you've replied to and this has long since been changed over to using the Cakewalk Installer. https://www.bandlab.com/products/cakewalk Except for a couple of specific cases, there's no need to use Bandlab Assistant and it can be safely uninstalled.

Start a new thread in the main forum rather than this FAQ section: https://discuss.cakewalk.com/index.php?/forum/2-cakewalk-by-bandlab/ Then provide as much information as you can as to what you've done so far. As it is, we're not even sure what product you're talking about or how you're trying to install things. What you're describing isn't typical.

Ah, that's important information that discounts pretty much every suggestion in this thread so far! Are you doing any work on these clips (or any source files they're derived from) outside of CbB at all?

If you can get a screen recording of your workflow when copying and pasting a clip, I think that would help solve this pretty fast (or uncover a bug)

Until we have a proper Import Mix function, that would drive me mad trying to get consistency across each song! Haha! For me, it's worth the trade-off in being unweildy having everything together for the convenience of being able to make global adjustments. But it really does show the end justifies the means - if the process works well for you, then it's the right way.

I'm wondering if this has something to do with Broadcast WAV files? What are you seeing in Preferences > File > Audio Data? Mine looks like this: If you have ticks in any of the Broadcast Wave options, take them out and see if that helps. I don't see how this could be affecting clips that have been copied and pasted in-project but it certainly would do for anything dragged in or imported.

What I tend to do is do it all in the one project so if this is all the same show, you have an overall sound for it all. For the tracks that are common to each song, keep them as their own thing and automate when it comes to mix time. For the tracks that are different to each song, put them on their own tracks (so even if it's Stage Right Guitar, there's no need to be forced to use just a single Stage Right Guitar track, you can split that up per-song to different tracks if you like). Yes, this does add extra tracks to a project but it makes management way easier later. Folders and sub-folders are your friends here. The best thing about doing it all in one project is you can do common effects for everything (eg: room sweetening, reverb, etc.) and balance the mix so it all sounds consistent from song to song. Doing them all in different projects makes it quite a bit more challenging.

Have you got snap on and set to Snap By instead of Snap To? How are you selecting the clips when copying? If you're doing a time range, you might actually be selecting some blank space before the clip itself and it's inadvertently pasting that in and shifting the pasted clip down after that.

Give support a yell - support@cakewalk.com They've managed to restore old accounts. You should be able to get the latest version of Cakewalk Command Center and download all of your old purchased items from there. Bear in mind that because everything is being shifted around a bit to cater for the new product line coming, some domain names have changed so if you have the old CCC then you'll need to grab the new one from HERE for it to work. But yeah, if you can't log in to that, shoot support a message.

I'm not really sure there even is any new stuff to talk about, honestly. From everything I've seen posted they're still at work on the upcoming products and there's some logistics to get past for the CbB stuff. Seeing Mark mention the back-end stuff, I wonder if that's got something to do with people testing Next out taking a while to get happening? It sounds like there's going to be some kind of public/semi-public beta for it, rather than the closed internal testing they've had so far (just speculating here, no insider knowledge on that either way)

Mark mentioned in a thread the other day that everything was more or less baked for the next CbB update but they're waiting on some server side stuff to be completed by a different Bandlab team. It sounds like everyone is keen to push this out