Helpful ReplyAmplitube 4.5 causing issue after in SPLAT after upgrade

Author
Post
Essentials Only Full Version
hockeyjx
Max Output Level: -74 dBFS
  • Total Posts : 839
  • Joined: 2003/12/09 18:36:28
  • Status: offline
2018/04/29 03:30:08 (permalink)

Amplitube 4.5 causing issue after in SPLAT after upgrade

Anyone else see this issue after upgrading Amplitube 4.5 on the pre-Bandlab SPLAT?

Intel i7 950 Proc, Asus Sabertooth x58 MB, 2 Crucial 128GB SSDs and Seagate 1TBGB drive, 12GB Corsair 1600mhz 8-8-8-24 Memory, Nvidia GeForece 8400 Dual Monitor vid card
Cooler Master Silent Pro 700w Power Supply, Cooler Master Sileo 500

Win 7 64 bit, SPlat 64-bit, Komplete 10 Ultimate, AmpliTube3 and AD2

Tascam FW-1884 and AKAI MPK-49
#1
List Solutions Only

2 Replies Related Threads
    hockeyjx
    Max Output Level: -74 dBFS
    • Total Posts : 839
    • Joined: 2003/12/09 18:36:28
    • Status: offline
    Re: Amplitube 4.5 causing issue after in SPLAT after upgrade 2018/04/29 03:56:17 (permalink)
    To be clear, when SPLAT is scanning the plugin, it finds an error with Amplitube 4, and I have to disable it.

    Intel i7 950 Proc, Asus Sabertooth x58 MB, 2 Crucial 128GB SSDs and Seagate 1TBGB drive, 12GB Corsair 1600mhz 8-8-8-24 Memory, Nvidia GeForece 8400 Dual Monitor vid card
    Cooler Master Silent Pro 700w Power Supply, Cooler Master Sileo 500

    Win 7 64 bit, SPlat 64-bit, Komplete 10 Ultimate, AmpliTube3 and AD2

    Tascam FW-1884 and AKAI MPK-49
    #2
    scook
    Forum Host
    • Total Posts : 24146
    • Joined: 2005/07/27 13:43:57
    • Location: TX
    • Status: offline
    Re: Amplitube 4.5 causing issue after in SPLAT after upgrade 2018/04/29 04:15:08 (permalink) ☄ Helpfulby Noel Borthwick [Cakewalk] 2018/04/29 13:36:09
    Does the message have an option to enable the plug-in? If so, you may want to select that option. Often plug-ins before the one throwing the error corrupt memory causing problems for the scanner. I occasionally see errors like this and have never had a problem enabling the offending plug-in (esp. commercial plug-ins).
     
    You may also recover the plug-in by running a manual scan with "Recan Failed Plug-ins" enabled from Preferences > File > VST Settings.Once the scan completes, make sure to restore scan method from the drop down and disable "Rescan Failed Plug-ins."
    #3
    Jump to:
    © 2024 APG vNext Commercial Version 5.1