[Solved] Where was the solution for fixing the Melodyne 4 crash?

Author
mettelus
Max Output Level: -22 dBFS
  • Total Posts : 5321
  • Joined: 2005/08/05 03:19:25
  • Location: Maryland, USA
  • Status: offline
2016/02/06 02:56:08 (permalink)

[Solved] Where was the solution for fixing the Melodyne 4 crash?

I run VST scans manually, and after installing another VST I ran a manual scan and the scanner crashed upon reaching Melodyne. Just checked and the Region FX for Melodyne crashed SONAR as well.
 
I tried to install M4's trial, then re-installed Editor 2 over this (after simply uninstalling both), and works fine in standalone mode, but there is an "M4 remnant" on the loose somewhere affecting both SONAR's VST scanner as well as the Region FX. AFAICT the vst3 file was not renamed, and I just ran the Editor 2 installation in "repair" mode to no avail.
 
I remember seeing comments related to this, but cannot find the solution readily. Anyone recall what the "fix" is?
post edited by mettelus - 2016/02/06 03:22:18

ASUS ROG Maximus X Hero (Wi-Fi AC), i7-8700k, 16GB RAM, GTX-1070Ti, Win 10 Pro, Saffire PRO 24 DSP, A-300 PRO, plus numerous gadgets and gizmos that make or manipulate sound in some way.
#1

1 Reply Related Threads

    mettelus
    Max Output Level: -22 dBFS
    • Total Posts : 5321
    • Joined: 2005/08/05 03:19:25
    • Location: Maryland, USA
    • Status: offline
    Re: Where was the solution for fixing the Melodyne 4 crash? 2016/02/06 03:08:40 (permalink)
    The easiest solution actually worked... I simply deleted the C:\Program Files\Common Files\Celemony folder and ran the Editor 2 installer again in "repair" mode and it recreated the directory (with 3 subfolders versus a single vst3 file which was there prior to deletion).

    ASUS ROG Maximus X Hero (Wi-Fi AC), i7-8700k, 16GB RAM, GTX-1070Ti, Win 10 Pro, Saffire PRO 24 DSP, A-300 PRO, plus numerous gadgets and gizmos that make or manipulate sound in some way.
    #2
    Jump to:
    © 2025 APG vNext Commercial Version 5.1