Bristol_Jonesey

I'm thinking I might have to upgrade to 5, but does it work inside Windows 10 & 11?

Forgot to mention, this is Melodyne Editor, if that makes a difference

The VST2 path contains the file Melodyne.dll The VST3 path cotains the file Melodyne.vst3 Plugin manager is set to scan both (I can see them being accessed in the toast box) but not showing up in Region Fx

Hi all I've decided to install Meolodyne 4 on my laptop I've downloaded and installed it, run the stand alone player and activated it. The standalone player runs ok. I Rescanned the paths in plugin manager but it's not showing up in Region Fx. All I see is Drum Replacer & VocalSync. I can see it scanning the Melodyne dll but no joy. Any idea what is going on? Thanks

Nice. Just caved in and bought it

Well that's not your call to make. The bakers will decide what is right for them AND for the user base.

Best comment yet

Doubtful. It would probably break 😁

Export depth has nothing to do with recording bit depth. You should ideally have the latter set to 24 bit, not 16 32bit for exporting is fine

That might suit you but it won't suit a lot of people Of course, it could easily be both, but no doubt some will still find something to whinge about

Yep. It's still there in CbB

Totally agree with this. Why on earth he disagrees is beyond me

And you need to uninstall ASIO4ALL. Get rid of it completely, including any registry entries

Pretty sure this is how envelope selection has always worked

It's scary how you believe this with over 6.1k posts on this forum.

Keni, what happens if you first freeze the vst, then move the generated clip(s) and then unfreeze? My only concern would be if unfreezing the vst causes the midi to return to its original time

Have you got this checked under Options

Ripple Edit should do it.

Minor correction - the VX64 IS included in CbB, it's just hidden by default. Goto the Utilities > Cakewalk Plugin manager and hit "Show Excluded" But it's hidden for a reason and may well cause instabilities on your system

I certainly don't feel that way. I got over the Gibson debacle the day after they announced their intention to throw us to the wolves, fully prepared to stick with Splat or move to a new platform if it no longer worked. Which of course never happened. Certainly Bandlab don't owe us anything, thy can only be commended up to this point.

Nobody can say for sure what will happen with YOUR system. Every user case is different to the next. But I updated to the EA on the first day it was available and haven't noticed a single thing wrong with it. You WILL need to update it at some point because the existing servers which CbB use to refresh your activation will no longer be online. The way I see it, you have a choice of 4 courses of action: Update to the final release and use that. This will mean no more updates or bug fixes Upgrade to Sonar when it becomes available Revert to using X2/X3/Platinum Don't do any of the above and stop using it after a period of (max) 6 months.

Yes we can, but you can't assume the same about the bean counters at Bandlab. They could well be getting twitchy about CbB being an endless drain on their resources.

What are "release approaches"? I've read all the release notes that accompany every update, and they always list the bugs which have been fixed. Are you saying they list the ones that haven't been fixed? If not your post and general stance on this matter is nonsensical

I was using the Sat Nav to guide me to a location I'd not been to before. It took me somewhere completely different to the UK post code I'd (accurately) typed in.

Do you have a list of these "numerous bugs"?