HOOK

This? I couldn't work without it...🤣

I did request this a couple weeks back in the feedback forum. Crickets on the topic. Workflow is a funny thing. I'm sure we all do it differently...and I can't stand having the console buried under the track view. So I break it out and run a second monitor with the docker and console view visible most times. And CV is where I, long ago, developed a habit of right-clicking and adding plugins...so to search and drag all the way from the search bar in the browser is literally like 45 inches...lol. I know. First-world problems.

The Alesis brain has a USB output for the MIDI data. I've never had to load a driver. Perhaps there's a driver loading from Windows...but I don't know. Sonar just seems to pick it up as a MIDI device. I never use the sounds on the Alesis brain for anything at all. I just made sure the kit was close enough I can get a phone feed from Sonar via my interface. The hardest part to get your head around is building the drum map. I'm literally a MIDI moron and I figured it out with a couple YouTube videos. But once you've done that it's off to the races any time you want.

When I downsized and stopped selling my time a few years ago, I ended up at home without a space to do live drums. I'd surrounded myself with great drummers over those years so I never really thought about midi drums. But when I started writing again on my own I quickly found that doing drums manually was tiresome, and frankly, I couldn't get the groove right without actually playing it. Then I actually had a good conversation with an honest sales guy at GC and he convinced me that, since I wouldn't be gigging with it, the Nitro kit would probably do everything I needed to do - and that I didn't need to spend more. And the savings allowed me to get the expansion kit so that I could have three cymbal pads and an extra double zone drum pad. I use the extra drum pad for ride cymbal so I can use one of the zones for ride bell. I use the Slate Drums. Tiny footprint. HUGE sounds. Really cool. Honestly, for my writing, this is the best money I've spent in a couple decades. As far as sensitivity goes, it's just basic business to go in and do a bunch of manual edits to velocity...it's really no big deal. In fact, it's mostly a thing I do while mixing. Also...if you go this route, you'll undoubtedly need some way to bring this tiny kit up to a height that can be played by a normal size human...lol. If you look at my pic you can see the couch risers I bought at Home Depot...or Lowes....or Amazon. Not sure where. They work great for that.

ahhh...the dreaded ASIO4ALL driver.

N - looks like a pre-defined accelerator "Snap Toggle Extended" according to the key bindings. And I don't think you can reassign those. The only thing you can do with those is assign "do nothing" get rid of it. I could be wrong. But I don't think that is an option you can assign to any key you want.

Sorry to be so pesky.

Better....ish, I suppose. Here's the problem I have with it. What you did to the Dark scheme looks fantastic to me - a very light gray. But I'm also sure others don't like it. However....I can't use Dark scheme because the color of the "split" line when I split a clip. It matches the background color of a clip too closely. And, while I can see the vertical lines much better in Tungsten Classic with the new change, what I used (and prefer) in CbB was a gray just slightly lighter than the background. So I'm batting about zero here...🤣 So...you know. Overall, I don't understand the resistance to user modifications for time ruler numbers, grid lines, ellipses and default background colors for clips. I believe that user setting options on those simple parameters would make the color schemes you're offering go a lot further for us out here in the real world. I know. My favorite saying at my day job is ....this job would be great if it weren't for those pesky customers!

Agreed. For me, it has been real detriment to my particular work flow on the creative side as well.

Yes. The inability to simply change the shade of the vertical grid lines has been a real challenge for me and I'll never understand why this option was deleted and abandoned. I've had to learn to live without them. As for the suspected VST problem you'll want to contact @Noel Borthwick and probably hook him up with a copy of that project so he can figure out why it's doing that. They're usually pretty quick to find a solution.

The only shortcut I know of is UNDO...but at a certain point, that's way too far back-in-time to make sense.

No...you're right. It's a little flaky. I don't know how it acted before 6. But it seems to want to pick its own preset sometimes and not let go of it. As in...harmonies get moved to match pitch of the guide sometimes, etc.

Since it's on sale right now, I've downloaded the demo for this plugin and I find it to be hit-or-miss when it comes to working properly. Sometimes it just doesn't ever process the adjustments. Melodyne ARA workflow is basically flawless on the same system. EDIT: That was all user error from what I can tell. Watched a few vids and did some reading. Actually working very well for me now.

Would be nice to have that option at the top of the menu when you right-click at the FX bin or hit the + to add a plugin. I'm talking, specifically here: I know we can search from the browser. But that can be a long stretch to drag back to where I want it sometimes.

Page 419 of the CbB Reference Guide covers this. https://bandlab.github.io/cakewalk/docs/Cakewalk Reference Guide.pdf

Looks to me like there's not a default key command for auto xfade. You'd have to assign it under Preferences/Keyboard Shortcuts. Search for Crossfades and it's the second of 3 options that come up.

Yeah...that's what I'm seeing.

Does anyone who uses Scaler find that it's 100% reliable in Sonar, or do you - like I - find that it's hit or miss? As in...sometimes it works and other times it just stops working for no particular reason?

I think that's the lesson learned here. I only use Next for the stem separation. So no reason to not have it set for 44.1 to avoid this issue in the future. It's not like I USE the separations for anything other than to pick out parts and learn them.

Sure...but it really was just opened up and the song was dropped in explicitly to do the stem seps. NOTE: While I was packing up this zip, I noticed it was quite large. Seems that Next imported the 4.81mb MP3 file and converted it to a .wav which is 153mb. I keep audio settings on Sonar and Next at 96/24. So perhaps it's blown up because it was converted to .wav at 96/24 when I dropped it into the project? Weird though. I swear I've done this before with the same settings. https://www.dropbox.com/scl/fi/ih0jea0rh4xlz9me1trqw/Stem-separation-problem.zip?rlkey=s0ojkibvpico15wqom06rjfqf&st=i09jbpel&dl=0

I mean...it's only a 3:30 song. That should be nowhere near 100mb at 44.1/16 as a .wav. But out of curiosity, it did perform as intended when I converted to .wav previous to trying to create stems. So perhaps .mp3 sends it off the deep end. Thanks for the thoughts...it helped solve the issue.

I keep getting this error prompt: But my file size before I drop into Next is this:

John...I had a similar issue a couple weeks back when I wiped a machine and went with a clean re-install...and what I found was that a bunch of my licenses were listed under "Cloud" in iLok. All I had to do was drag and drop those onto my physical iLok 1 and all my problems went away. No idea if this helps, but I figured I'd throw it out there. Good luck.

You haven't "missed it" because no one ever gets specific with what to do with the results. After you run the program for a few minutes you can click on each of these tabs to see what it's telling you. Green doesn't necessarily mean it's time to move on. You can still use it to tweak processes to improve overall DPC latency spiking. Stats will give you the headlines. Processes will give you an idea of what's running in the background. Drivers will show you all the drivers and which are running the highest ISR, DPC counts and the highest executions in ms. It'll tell you the company that the driver belongs to, etc. CPU will tell you which CPU(s) is(are) getting hit the hardest with DPC latency and which driver is causing it. You can then search those drivers and processes online to see what exactly they do, etc, and if there is anything you can do to alleviate the problem. Maybe you can just shut off a process...maybe you can't. Maybe you can make sure that process doesn't run on the same core you're running audio on, etc. Maybe it helps you figure out what to change in the bios. Once you try a fix, you can run LatencyMon again and compare where you were to where you are now. You really can chase down problematic drivers and processes that are causing latency spikes. Just takes time.

@Alan Bachman - Check your PM.