-
Posts
621 -
Joined
-
Last visited
Reputation
333 ExcellentRecent Profile Visitors
1,726 profile views
-
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.
-
HOOK started following Stem Separation Error , Feature Request: Search Plugins by Name and Scaler 2 - works/doesn't work
-
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.
-
-
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.
-
Pending new releases and existing issues. RESOLVED
HOOK replied to Chris Ward's topic in Cakewalk by BandLab
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. -
As sad as I was about issues when I switched to 11 a couple months back, I finally got the machine screaming again. In my opinion, it's very highly likely that my biggest problem with the upgrade was the fact that I changed my bios at the same time and didn't get a couple settings ticked. You're gonna have to make the move sometime. Might as well be now, while you build a new machine.