[Somewhat] Sonar crashes with Play 5 insertion...still no memory for midi devices problem

Author
Post
Essentials Only Full Version
eph221
Max Output Level: -28.5 dBFS
  • Total Posts : 4665
  • Joined: 2014/12/22 05:06:50
  • Status: offline
2016/10/29 20:32:08 (permalink)

[Somewhat] Sonar crashes with Play 5 insertion...still no memory for midi devices problem

two different problems.  Sonar sure crashes alot!
post edited by eph221 - 2016/11/01 16:34:10
#1

4 Replies Related Threads
    GuitarGuy
    Max Output Level: -89 dBFS
    • Total Posts : 82
    • Joined: 2003/11/12 02:13:34
    • Location: Carmel Valley, CA
    • Status: offline
    Re: Sonar crashes with Play 5 insertion...still no memory for midi devices problem 2016/10/29 23:29:42 (permalink)
    I installed PLAY 5  just a few weeks ago and have used it successfully with both Sonar 2016.09 and 2016.10 with no crashes.

     
    DAW: StudioCat
    CPU: Intel Core i7, 3.3 GHz
    RAM: 32GB
    OS: Windows 7 Professional, SP1, 64-bit
    Graphics: AMD Radeon HD 5450
    Audio Interface: Lynx AES16e/Lavry Blue
    DSP: UAD2 Solo
    Sonar: Platinum 23.10.0 Build 14 [2017.10] - x64
    Cakewalk by Bandlab: 2018.09 (Build 29 - x64)
    #2
    eph221
    Max Output Level: -28.5 dBFS
    • Total Posts : 4665
    • Joined: 2014/12/22 05:06:50
    • Status: offline
    Re: Sonar crashes with Play 5 insertion...still no memory for midi devices problem 2016/10/29 23:43:28 (permalink)
    I've had nothing but problems with PLAY 5
    #3
    BRainbow
    Max Output Level: -83 dBFS
    • Total Posts : 399
    • Joined: 2004/03/14 01:39:12
    • Location: Honolulu, Hawai'i
    • Status: offline
    Re: Sonar crashes with Play 5 insertion...still no memory for midi devices problem 2016/11/01 04:23:29 (permalink)
    I don't have any problems with Play 5 except the occasional iLok reinstall prompts, but that happened in stand alone with Play 4 as well and sometimes with Melodyne and Autotune.
     
    The MIDI memory thing was a problem for me recently when configuring a Line 6 FBV II foot controller.  I tried the fix suggested elsewhere of deleting all ghost MIDI/Sound devices in Device Manager but that didn't help.  I found I had to open SONAR before I opened any other programs like the FBV controller software.  When I opened SONAR first, I had no further problems. 

    Cakewalk (forever), Two WIN10 64-bit DAWs: home-brew ASRock x299 Taichi / i7 7820x w/ 64GB RAM and ASUS X99A-II / i7-5820K w/ 32GB RAM, ZOOM UAC 8, Mackie ONYX 1640i FW Mixer/Interface, Mackie ONYX 1200F, Avalon U5 PreAmp, NI Komplete 11 Ultimate, EastWest Composer CloudX, Yamaha MOTIF XS8, Ensoniq SD-1 and ESQ-1, Korg M1rEX, Yamaha TX-81Z, Roland D110, Line6 HELIX Rack and Native, POD HD-Pro, POD Farm 2.5, Yamaha NS-10 and Presonus Eris E8 monitors, Yamaha Disklavier Upright Piano, mics, guitars, basses, and the cutest little tambourine.
    #4
    eph221
    Max Output Level: -28.5 dBFS
    • Total Posts : 4665
    • Joined: 2014/12/22 05:06:50
    • Status: offline
    Re: Sonar crashes with Play 5 insertion...still no memory for midi devices problem 2016/11/01 16:33:42 (permalink)
    Ok, thanks for all your replies.  Mike at East West gave me the scoop on the problem.  I was using the 32 bit play instead of the 64 bit.  If you had the 32 bit on your system you might run into this, as the new play installation.exe ONLY installs the 64 bit, i.e. it doesn't get rid of old play iterations!  so if you run into this you need to delete all east west directories (including the hidden* program data* folder) except for your samples.  Then reinstall with the new 64 bit play 5.
     
    As far as the midi thing.  I've already deleted all  the ghost midi ports.  It didn't work.
    #5
    Jump to:
    © 2025 APG vNext Commercial Version 5.1