sjoens

.

Maybe both top and bottom??? Of course, I'd also want one in the middle too.

Windows 10 recently sabotaged my on-board Soundblaster ASIO so that CbB wouldn't even open until I deleted its ASIO listing in the registry. Before that update it was fine. That's my story anyway. EDIT: New Windows 10 install restored the Soundblaster.

For me, I no longer do but There was a time. Not sure if I had to rename them in the PM itself but I did make it work somehow. Where there's a will... sometimes there's a way.

Have you checked the excluded plugin list in the plug-in manager? Make sure you also check the Show permanently excluded box. Not sure what else to do as Kontakt versions have always been able to coexist.

Renaming is necessary when you have variants of the same version: 5.2, 5.4, 5.6, etc.

What worked for me: install in separate folders & rename each DLL. Kontakt 5 (folder) |-Kontakt 5.dll Kontakt 6 (folder) |-Kontakt 6.dll Add each folder to the search list.

Never noticed before but all my audio interface's inputs & outputs are listed under permanently excluded DirectX Audio Effects (DX)... Onboard Realtek HD also there. Had no idea my interface was DX.

Thanks. I just read this which answered it for me. What's the chance of that?! I never use offset and don't remember hitting the button...

In Console View I'm seeing a "+" after Volume and Pan values. Is this new or did I hit a setting somewhere?

This idea existed in the pre X series but took up screen space. Maybe add a few buttons in the empty menu tab space.

Simplest way: Open 1st project. Drag clips to desktop. Open 2nd project. Drag clips from desktop to a track or blank space below. If many clips in one track: highlight all clips 1st, proceed as above. When dragging, wait for the process bar in Transport module to finish before releasing mouse.

The PE L & PE d check also seems to work on the standalone .exe versions. How did you know what to look for?

Both. I'm sure the Browser is reporting info from the plugin itself. They are also identified in the Cakewalk installers. Or if you have Theme Editor you can also use this: which is color coded to the FX Bin dropdown list. Import it to: Browser | Plug-in Browser | Plug-in Tree Icons

Good point. Unlike Kontakt, you can't have 2 different versions installed.

Upgrade was $99. Now $29 so... end of discussion!

Well then... for $29 I guess I shud jes shutup and upgrade.

I get why Celemony won't fix it as they've moved on, but... seems odd for Intel to break a 64 bit app and leave the 32 bit one alone. Out of 99 scanned plugins, this is the only one failing.

Thanks Noel. Did that a few times already. Just heard from Celemony who said v4 isn't tested or verified on Windows 11. Apparently Intel 10th & 11th gen i7 CPUs are affected. Mine's 12th gen so probably inherited this issue. https://helpcenter.celemony.com/hc-2/faqs/?qOpen=299 At this point my options are use 32 bit Sonar to edit or CbB w/o Melodyne or upgrade to v5 for $99 or fix my Win10 system and use it until it's no longer supported. Upgrading is inevitable! Just curious if anyone else is having this issue?

Just learned from Celemony that 64 bit Melodyne 4 won't work on my new 12th gen Intel i7 laptop. And for some reason CbB doesn't see vvocal on it either. They specifically mention 10th & 11th gen Intel but I suspect every gen to follow will behave the same from now on. Anyone else having issues like this?

Today I get this same message. After several rounds of trying to get 64 bit Melodyne to work in Windows 11, I've discovered the secret to uninstalling Runtime 4.1 and avoiding the message from "HAL" is to uninstall it 1st. HAL only reared his ugly nasty head when I tried to uninstall it after uninstalling Melodyne. I'm still trying to get 64 bit Melodyne to work. The Scanner says it's a known bad vst and skips it. The 32 bit version scans fine.

After invoking VstScan.log it said Melodyne is a "Known bad VST plugin skipped". Hopefully Celemony has a fix.

After several uninstalls/reinstalls I got 32 bit Melodyne to work properly. But 64 bit refuses to work, or even be scanned, at all. CbB stops scanning once Melodyne is reached and never includes it - not even listed in "Show excluded". Something is preventing it from being scanned.

Come to think of it, sometimes they're black, but that might be I'm using a different theme.

This happens to me a lot. Looks like an automation envelope but it never shows up in the Automation Lanes. I never know what I did to invoke it but a series of Undos usually gets rid of it.