EZKeys crashing as a VSTi in both Cakewalk and Reaper

EZkeys Help
Viewing 4 replies - 1 through 4 (of 4 total)
  • ivan carling
    Participant

    This gets stranger…. I also reinstalled the drivers for my elderly emu Xboard 61 & tried again.

    After a re-install & restart, I was able to select the grand piano & play it from my Xboard. Until I decided to try another EKX & selected the Dream Machine, which promptly crashed & closed EZKeys up completely, as before. Still cant figure ou thow to get a crash log.

    Interestingly, I then removed the Emu software entirely & selected my Korg NanoPad as the MIDI input device, which worked fine in Addictive keys in Reaper, but not with EZK.  Win10 Pro 64bit latest version, ditto with reaper and the Cakewalk software.


    EZkeys version: 1.2.5
    Operating system: Windows 10
    John
    Moderator

    Hi Ivan,

    since the EZkeys standalone seems to work alright, I would look into if your hosts are actually loading the correct version. Worst case being that your host is loading the 32-bit version in a 64-bit host.
    In the EZkeys 64-bit standalone, you can check the location of the plugin file in the ‘Help’ Menu item Show Plug-In Path.

    Please make sure this is where your host(s) look for the EZkeys plug-in and not in the (x86) path.

     

    BR,
    John

    John Rammelt - Toontrack
    Technical Advisor

    ivan carling
    Participant

    Thanks, John.

    Assuming this is the cause, the mystery deepens, as the whole shebang was working fine a couple of days ago!

    I will check this out though.


    EZkeys version: 1.2.5
    Operating system: Windows 10
    ivan carling
    Participant

    Solved it by uninstalling all my EZK stuff, then doing a search-and-destroy for any older stuff that might have been lying around pre the  Product Manager, then doing a fresh download and reinstall! Everything working just fine in both Cakewalk and Reaper.

     

    FWIW I also found some other plugs that had stopped working & responded to reinstalls, so I suspect thios may have been down to MS updates of W10 arbitrarily changing location pointers, etc., like they do with my default speaker outs every time there is a major update. *sigh*


    EZkeys version: 1.2.5
    Operating system: Windows 10
    • This post was modified 5 years, 11 months ago by ivan carling.

    2

    Thanked by: jamesmcconnon and John
Viewing 4 replies - 1 through 4 (of 4 total)

No products in the cart.

×