Waves Shell Crashing Sonar

Author
Post
Essentials Only Full Version
brconflict
Max Output Level: -56.5 dBFS
  • Total Posts : 1891
  • Joined: 2012/10/05 21:28:30
  • Status: offline
2013/03/07 15:40:19 (permalink)

Waves Shell Crashing Sonar

Anyone else having repeatable issues with Waves plug-ins crashing Sonar? I know Cakewalk has seen the crash reports, but I have no way of knowing if they've identified what the issue is. Waves says that there could be an instance of 32-Bit WaveShell found by Sonar (a typical cause), but in my case, there are no 32-Bit WaveShell installs.

Brian
 
Sonar Platinum, Steinberg Wavelab Pro 9, MOTU 24CoreIO w/ low-slew OP-AMP mods and BLA external clock, True P8, Audient ASP008, API 512c, Chandler Germ500, Summit 2ba-221, GAP Pre-73, Peluso 22251, Peluso 2247LE, Mackie HR824, Polk Audio SRS-SDA 2.3tl w/upgraded Soniccraft crossovers and Goertz cables, powered by Pass-X350. All wiring Star-Quad XLR or Monster Cable. Power by Monster Power Signature AVS2000 voltage stabilizer and Signature Pro Power 5100 PowerCenter on a 20A isolation shielded circuit.
#1

3 Replies Related Threads
    bz2838
    Max Output Level: -83 dBFS
    • Total Posts : 366
    • Joined: 2010/10/16 14:44:50
    • Status: offline
    Re:Waves Shell Crashing Sonar 2013/03/07 15:58:55 (permalink)
        Never had that problem with waves plugs, use them all the time

    Purrrfect Audio:  Intel i7 7700k (Kabylake), 32Gig DDR4/2133, Windows 10x64 Pro, USB RME Babyface, Sonar Platinum Current
    #2
    brconflict
    Max Output Level: -56.5 dBFS
    • Total Posts : 1891
    • Joined: 2012/10/05 21:28:30
    • Status: offline
    Re:Waves Shell Crashing Sonar 2013/03/07 16:04:54 (permalink)
    When Waves updated the Shell from 9.0 to 9.2, and I added the API bundle, Sonar held the version 9.0 hostage to all my sessions, since it was looking for VERY specific plug-in versions (sees 9.0 and 9.2 WaveShell as different plug-ins), so the complete disaster that was the upgrade sought some extra procedures from Waves to clean up - Followed by many, many hours of manual Sonar session recovery has be suspect that there's still something wrong with either one.  All of this because Sonar didn't see the higher version of Waves plug-ins as the same plug-ins. 

    Maybe it's how they treat competition...

    Brian
     
    Sonar Platinum, Steinberg Wavelab Pro 9, MOTU 24CoreIO w/ low-slew OP-AMP mods and BLA external clock, True P8, Audient ASP008, API 512c, Chandler Germ500, Summit 2ba-221, GAP Pre-73, Peluso 22251, Peluso 2247LE, Mackie HR824, Polk Audio SRS-SDA 2.3tl w/upgraded Soniccraft crossovers and Goertz cables, powered by Pass-X350. All wiring Star-Quad XLR or Monster Cable. Power by Monster Power Signature AVS2000 voltage stabilizer and Signature Pro Power 5100 PowerCenter on a 20A isolation shielded circuit.
    #3
    Jimbo21
    Max Output Level: -77 dBFS
    • Total Posts : 696
    • Joined: 2010/02/08 19:35:48
    • Status: offline
    Re:Waves Shell Crashing Sonar 2013/03/07 16:41:59 (permalink)
    I've had similar problems when adding new plugins in that I get the "waveshell 9.0 or 9.2" etc. can't be found message when starting Sonar. I recently bought Waves Tune and only installed that from the previous full download (using the computer offline method) and Sonar started loading all the Waves plugs as 32bit instead of 64 and would not save or close Sonar. I finally figured out that I needed to get the latest download from waves because that is the version the license is (I guess that's why) on the flash drive. Once I reinstalled all plugs and everything is working as it should for now. I would try reinstalling everything fresh if you haven't yet and then going to preferences and rescanning all plugs.

    Dell XPS 8700 i7 4770 3.4GHZ, Windows 7 64bit, 8gb Ram, Focurite 18i6, Sonar Platinum
     
    https://soundcloud.com/jimmy-james-and-the-blue
    #4
    Jump to:
    © 2025 APG vNext Commercial Version 5.1