Larry Jones

@Clovis Ramsay I asked the question because earlier in this thread @bitflipper commented that the ADHD Leveling Tool might be a 32-bit app, even though it's advertised as 64-bit. Nothing to do with Cakewalk or the CA-2A.

Just curious - what makes you suspect that? The download is an installer, and when I ran it, it gave me five choices of what to install: AAX 64-bit VST 64-bit VST 32-bit VST 32-bit VST Yes, you read that right. There are two 64-bit VST options and two 32-bit VST options. I chose the 64-bit option and on the next screen the mystery was solved: One of the 64-bit choices went into the default VST2 folder and the other one went into the default VST3 folder. I assumed this was accurate nomenclature. Wouldn't it be some kind of developer malpractice not to disclose the bitbridged thing, especially if you are also offering a 32-bit option?

You could select all the tracks and drag them left (over the blank area) to wherever you want them to start.

Thanks for this tip! I had no idea.

Nice work, Johnny!

I'm having trouble picturing how you're working with CbB (Cakewalk by Bandlab). Are you drawing notes in the Piano Roll View (PRV)? If so you must have already inserted a virtual instrument or you would not be hearing your notes. And if you've got a virtual instrument loaded, the control pane to the left of the timeline is where automation happens (or in the console view, I guess). I'm not an expert, so I'll defer to others here, but there's an 1,800-page PDF manual you can download. Here's a section on MIDI automation. The full manual can be downloaded from a link at the top of this page: Reference Guide PDF. Best of luck!

If your problem is re-activation, that only happens once every six months, and takes a few minutes, depending on your internet speed. The downloads you mention might be updates, which are roughly monthly and almost always improve the product. What are your specific issues?

Thanks!

I meant "What does "EA" mean?

EA?

If that's the obstacle to a successful Update, shouldn't it be included as the first part of the Update?

Here's a kooky story for you, @John Vere: A few days ago -- probably after the same Windows Update that caused your problem -- my DAW wouldn't load Windows. I restarted it to no avail. Total black screen all the way through the boot process. I recalled reading somewhere that if you interrupt the boot process by shutting off the machine three consecutive times before it completes, it will go into the BIOS. I tried that, and nothing. I left it running with the black screen up. A half hour later I glanced over at it and it was restarting on its own! I'm sorry I can't give the exact details of what happened next, but the "error" message said something to the effect of "This Windows Update failed (and it was probably your fault) so we have rolled back the Update and restarted your PC. We'll try the update again in 30 days, after we have figured out what went wrong." The machine started up, loaded Windows, and everything is working. If I had not walked away from it while it was on, if I had decided to try and "fix" it myself, I would never have known an update could do that.

This is almost for sure what's happening. @RICHARD HUTCHINS If you want to add cymbal crashes of long duration, I suggest you use a new instance of AD2. The drums in the main instance will always chop off your crashes.

Original post or original poster. The first post in a thread, or the person who posted it. This is not Cakewalk specific. I charge extra for consulting on general internet shorthand. ? At this point I think you have enough information to accomplish what you want to do. I suggest you make a safety copy of your project and try out some of the advice you've gotten. You'll find a way, and you'll learn more from doing than you will by reading. Good luck!

This is in direct response to the original question on that thread. The numbers are meant to work for the OP. Later in the thread it's explained how this method works, what the numbers mean and how you could change them to suit your specific situation. It does work, BTW.

There's a thread here on the legacy SONAR forum that discusses how to do this. This is the specific reply, but there is more information if you keep reading. The stretching algorithms in Cakewalk have been improved since that particular discussion took place, and in my opinion your results (audio quality) will be acceptable, maybe undetectable. Before you start, look in Preferences and set to the highest quality,and keep in mind that until you render your modified tracks you'll be hearing only a preview. The final render will be higher quality. I hope this helps. I know what it's like to get far down the road and for whatever reason decide that the tempo is wrong. Maybe along the way you've added instruments or changed the lyrics or something that makes the original tempo not work. And you might still be working on the track, so you don't want to mix it down and change tempos on the stereo mixdown. There is another method of changing the tempo of an entire multitrack project, but I rarely use it and can't put my finger on it right now. I'll follow this thread to see how you're doing. I saved the technique somewhere and I'll look for it. EDIT: OK, I found the other method. It's in Craig Anderton's Sound on Sound column from December 2018. The column contains more info than you need, but the tempo change stuff is there, too. One caveat: When he says "slip-stretch" in Step 1, he means "slip-edit." Good luck! And thanks, @Craig Anderton!

Sorry, Erik, I didn't realize I was in the Feedback forum. I stumbled on your excellent rant by accident when I searched for "Studio One 5." I crossgraded to S1-3 back when it looked like Cakewalk was gone forever, and Presonus offered a great deal. I'm sure I wasn't the only one, but before I really got into S1, Cakewalk was revived and I haven't used it much since then. I have upgraded to version 4 and now I see they have another great deal on version 5, so I thought I'd see if there were any CbB users with something to say on the subject. I definitely had more fun reading your post above, though. All that said, I can imagine the bakers' responses to someone who wants better drum map implementation: We only have time and resources to do the things that most of our users want. You can program MIDI drums in the plugin GUI, so you don't need an effective drum map. It would require reprogramming the entire Piano Roll View. [Insert other arcane technical objection(s) here.] I love CbB and will always be grateful to Bandlab for saving it and employing the bakers to improve it. But once bitten, twice shy, and I'm keeping Studio One installed and updated, just in case.

Always enjoy reading about your Adventures in Drum Maps, @Starship Krupa I keep thinking I should learn how they work and how to create them, but I've seen (at least) two posts from you on the subject, and then I think better of it. Have you tried to hound the bakers about this situation? The rest of us would be grateful if you could talk them into producing a workable solution.

Should be noted the MIDI note is not actually colored like that. The colors represent functional areas.

John was trying to help. No need to be rude.

@John Maar - Ha! I've had the Dim Pro Expansion Packs installed for years, but I never noticed the Virtual B3, since there is a whole "Organ" section listed in the presets. As a non-keyboard player, my organ needs are meager, and these sounds are more than adequate for me. Thanks for the tip!

@David McMillen - Since you say you're a newbie, I highly recommend you start with SI-Drums, which comes with CbB (separate I think, but free). Mess around with it to get an idea of how MIDI drums work. When you're ready you can buy or try some of the drum programs mentioned by the others in this thread. Be aware that MIDI drums consist of two major parts: the drums themselves (samples), and the MIDI "instructions" which tell the samples what, when and how to play. The MIDI parts can be store-bought loops, or you can create them with a keyboard MIDI controller. Most MIDI drum packages come with both drums and loops, and if you don't understand drum maps, use them together instead of purchasing separately. Good luck!

@Blogospherianman @twelvetone; @reginaldStjohn @tonemangler Thanks guys. I'm still struggling with this bass track. Every time I listen I hear another timing problem. I used Melodyne to quantize the whole track (in bite-size sections), and that worked OK in a general way, but it left some sloppiness. So I went back to transient-stretching with Audiosnap and I'm in the process of manually tightening it up. If it weren't for Covid we'd just get together and do it over until we got it right, and in the end it would be better than what we're gonna end up with this way. But that's life and death in the new millennium.

I found some anomalies in Melodyne's behavior, too, but it definitely works better for this that Audiosnap. Thanks!