Jump to content

Bristol_Jonesey

Members
  • Posts

    947
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Bristol_Jonesey

  1. Email from Celemony support confirms "The problem is the CPU of your new system, as the code structure of Melodyne 4 is not optimized for Intel's new arising 11th and later CPU generation (Melodyne 4 has been discontinued for nearly three years now). Please take a look at our FAQ to get additional information: https://helpcenter.celemony.com/M5/faqs/?qOpen=299 You will need to update to Melodyne 5 as Melodyne 5 got a complete new code overhaul and is also prepared for the new CPU generations arising."
  2. I'm thinking I might have to upgrade to 5, but does it work inside Windows 10 & 11?
  3. Forgot to mention, this is Melodyne Editor, if that makes a difference
  4. 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
  5. 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
  6. Well that's not your call to make. The bakers will decide what is right for them AND for the user base.
  7. 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
  8. 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
  9. Totally agree with this. Why on earth he disagrees is beyond me
  10. And you need to uninstall ASIO4ALL. Get rid of it completely, including any registry entries
  11. It's scary how you believe this with over 6.1k posts on this forum.
  12. 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
  13. 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
  14. 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.
×
×
  • Create New...