Lord Tim

The other thing is what you actually have running in your projects too. If you have 5 instances of Sonitus EQ and it's dropping out, that's not good. If you have 50 instances of Ozone in your project then... yeah, good luck getting that to play on anything in the next 10 years. We need to know a little more about your computer (how much RAM, is it a SSD drive, what kind and how fast is your CPU, etc), if you're using the proper ASIO drivers for your interface, and what you typically have running in your problem projects or we're all just guessing with our suggestions.

First of all, this is a peer-to-peer forum that the developers sometimes drop in to reply, but it's not a given. If you want direct technical support, you'll want to be signed into your Bandlab account and head here: https://help.cakewalk.com/hc/en-us/requests/new As users, we can usually help out with a lot of issues though, but you haven't given us anything to go on. What are your computer specs? What audio interface are you using? What version of Windows? Has there been a recent update? Are there any new or updated plugins in your projects? Cakewalk being laggy and refusing to open projects isn't a widespread issue at all or the forums would be going nuts about it, so there's got to be something particular to your system that's either causing the issue, or exposing an issue in Cakewalk that the great majority of people aren't seeing. The more info you can give us, the more help we can give you if you want to seek help from here rather than Support.

Yeah, I'll echo the other comments here. What's the goal for this? When I write drums and I know I want it to be realistic, I'll go to great lengths to make sure it's playable (even if it's got to be a world class drummer that does it), I'll write in variations of where the drum is being hit, velocity for both right and left hands, nudge notes to make it realistic as far as when a drummer would be able to get to the hit from going around the kit and all of that stuff - the parts are actually usually not that difficult but the tweaking to make it sound real, and then the subsequent mixing of splitting each instrument out to its own discrete track to process it like an acoustic drum can really take ages, but it makes all the difference to how real it sounds in the end. However... that's not the only way to approach drums. I'm an 80s kid, so I'm happily at home with a LinnDrum or 808 playing absolutely impossible stuff, that's just not meant to sound real. Does it work for the song? Yes. Then it's correct. That's basically it. And often, I'll layer a lot of my "dude you spent way to long making that stuff sound real" drums with very obviously programmed stuff because I like how it sounds together. There's also no rule to say that you can't use a basic drum VST that you're running MIDI loops into it or your own basic patterns in your songs. If you're personally trying to go for realism and it's falling short, then sure - there's areas you can "improve" but if you like how it all sounds despite it not being "real" then... ehh... it's good. This is art at the end of the day and is subjective. If you like it, then that's the answer: it's the correct part for you. EDIT: If you *do* want to get your programming chops up, have a look at Scott's course here: https://spectredigital.com/product/metal-drum-programming-mastery/ It's metal oriented but metal is one of the hardest styles to get sounding realistic because rolls especially sound absolutely terrible programmed unless you really know what you're doing, and you can apply this knowledge to any rock or pop style.

Ah, easy done then! But yeah, it's in the Inspector now, which makes a lot more sense than having it down in the multidock, I reckon.

Save the project as a MIDI file, and export any audio tracks separately. Pretty much every DAW can open a .mid, so get the recipient to open that first which will import the tempo map and then import in any exported audio tracks after that, which should line up with the MIDI tempo map. Edit: Sorry, for the second part of your question there, the Tempo Map has now moved to the Inspector pane. Go to Views > Tempo (or do Alt+Shift+5) and that'll get you right there. But doing the MIDI file export is a much faster way to get a tempo map into another DAW.

I get that but it's still an extra step that could be solved with a bit of logic, IMO. Not a big deal in the scheme of things, but all of those little pauses add up over the course of a big project.

Actually that's a good point, zooming in on say the middle few lanes of a 20 stacked track would make my "scroll the overview out of view" thing kind of redundant. That said, I'd go for that in view and collapsed over "HAVE YOUR OVERVIEW TRACK!!! plus also the stuff you actually wanted to look at" like we have now any day.

My vote with that is to either keep that minimised and make it editable, or scroll it off view entirely. But yes, as it currently is, having half of your screen taken up with the overview track when you zoom in is really not at all useful.

Yep, you can even rebuild entire projects by selecting all of the tracks and saving it as a track template. Super handy for getting a starting point for a whole album project so you already have your bus effects, synths, amp sims, etc set up and ready to tweak or change as needed for the next song.

Yeah, apologies - I think I misunderstood the issue in the OP. So the idea was you were planning to do the Audio to MIDI conversion on a track, but instead of just that one track converting, you're saying the entire project is doing it?

OK, that's pretty weird. How did you hook the Keylab in exactly? It's possible you have a corrupt entry in a config file if you did any manual editing.

Yeah, that's very possible - have a look up at your Transport module on the Control Bar. If it's converting the sample rate, you'll see a little progress bar appear, however it should be saying something like "Converting Sample Rate" rather than just "Importing" for a WAV file. Videos are a different beast entirely because it really depends on the audio codec contained within, so it's likely that'll just say "Importing."

This is actually how it works - it converts audio to MIDI when you drag an audio track to a MIDI track. It's great for turning melodies into MIDI notes for triggering softsynths. What's the reason that you're doing this rather than just dragging it to another audio track?

Importing is as fast as always here, so it's not a general thing. If you temporarily disable your antivirus (even the in-built Windows Defender), does that make a difference? It might be aggressively scanning any accessed files and slowing things down.

Is this the page you're on in Cakewalk Preferences? There's definitely both an OK and Apply button at the bottom:

Command Center is really only for legacy products that existed before Cakewalk by Bandlab. If you didn't have an account back then, you won't be able to create one. To get the current demo projects in CbB, go to Help > Check for Updates and it should give you the option of downloading additional stuff, including demo projects. There's one in particular that I contributed called "Time to Fly" that also comes with a fairly sizeable PDF file explaining everything to do with the project, so it's good for learning the app (at least one way of using it). I'd also recommend checking out the Tutorials forum too: https://discuss.cakewalk.com/index.php?/forum/35-tutorials/ The Owners Manual Tutorials in particular are super comprehensive for getting you comfortable with CbB.

Press the Scroll Lock key on your keyboard - that should do it.

Try it out when you can, though - it's never a bad thing to have more eyes on a problem to make sure it's fixed completely!

Just tested the EA then - all appears to be working correctly now

I haven't had a chance to try this out yet to see if it's solved the issues I came across but see how you go with this, @GreenLight https://discuss.cakewalk.com/index.php?/topic/48070-cakewalk-202206-update-1-early-access/

Nah, it's really the vertical height that makes the difference - it's a 49" 32:9 monitor, basically 2x 27" 16:9 monitors joined together into one really wide one, so if people like a 1440p 27" monitor at 100% then this would look the same, just extending out on either side. But like I said, it's definitely personal preference. 100% scaling feels just right to my eyes but might be too small for others.

I'm using 5120x1440 as my main monitor, basically a very wide version of the one in the OP and at 100% it's all good for me, but it's definitely personal preference for sure. I did have an ultrawide with a 1080 high instead of 1440 and it felt way too big for me and not nearly enough stuff vertically for my liking.

It's a fun exercise to do if nothing else! I did some null tests between DAWs a while back and one big gotcha will be pan laws once you get to that point. Everything nulled until I started panning, and sometimes it was difficult to find something similar enough to make them match exactly. Engine performance, or even the way each DAW works with plugins aside, if you end up with anything radically different (better or worse) in any DAW, I'd look there first.

This usually happens when something else has taken control of the audio driver. What else have you got running on your system? It might be the case of even something like Chrome running in the background which is trying to play something at a different sample rate than Cakewalk.

Interesting. Yeah, I was the guy who reported the broken move to folder thing and it looked like it was fixed. But there's definitely something funky still going on that I'm able to reproduce now that I'm trying a few tests, even more so than what you're seeing. Let me hunt down a dev and chase up our last chat.