Jump to content

jeffdaniels

Members
  • Posts

    83
  • Joined

  • Last visited

Posts posted by jeffdaniels

  1. 14 hours ago, gunmetal said:

    Independence wasn't showing up for me either and was removed from X3 as well.  I tried a manual reinstall from the Magix v3.5 Independence download and that didn't work - it installed and I could run the offline .exe but no plugins showed up.

    Here's how I fixed it:

    I manually deleted the downloaded installation file under  Documents>Magix downloads>installationsmanager

    I ran Samplitude X4 as an Administrator

    I chose only Independence from the Download Instruments and sounds under the Samplitude Help menu

    The installation download about halfway on the progress meter and then auto-installed in a "Repair" mode - and then everything worked

    I have my sample content on a separate drive so I just pointed to there for the content

    Great, this fix worked for me!

  2. As recommended in the forum, I installed Pro X 4 Suite without uninstalling Pro X 3 Suite. Somehow the Independence PlugIn doesn't show up in the PlugIn Browser and in projects, created with the previous version, containing it as vsti, it is just marked as a missing PlugIn. I tried to remove, install it again with the delivered installer 3.5, adding several paths for vst(i) scanning but it cannot be found in pro x 4 (only 4). Any ideas?

     

    Thanks in advance!

  3. On 11/18/2018 at 10:13 AM, jeffdaniels said:

    Same issue here - how to fix that? I cannot do any ARA melodyne editing anymore in ANY projects. I hope re-installtion of SAM Pro X3 will help.

    This happend after accidently applying ARA Melodyne to all objects in a project - at least the project is working. But it is nasty to open the object editor for 200++ objects end de-select the melodyne effect. Is there an efficient way?

     

    EDIT: a re-scan of VST leads to the possibility to apply melodyne again to objects in other projects. but inside the projects it leads to the attached error.

    Clipboard01.png

    The only way to solve this is to open the "semi-corrupt" project, remove any applied melodyne effects in the object editor (also check in the objects-tab the column "effects"). save the project, close it, apply a VST-PlugIn-Path rescan and then you can work with melodyne again even in the concerned project. in my case, the project is suddenly reacting a bit slower/CPU-spikey - but at least it works.

  4. Same issue here - how to fix that? I cannot do any ARA melodyne editing anymore in ANY projects. I hope re-installtion of SAM Pro X3 will help.

    This happend after accidently applying ARA Melodyne to all objects in a project - at least the project is working. But it is nasty to open the object editor for 200++ objects end de-select the melodyne effect. Is there an efficient way?

     

    EDIT: a re-scan of VST leads to the possibility to apply melodyne again to objects in other projects. but inside the projects it leads to the attached error.

    Clipboard01.png

×
×
  • Create New...