No products in the cart.
Seems to have happened after the last Win10 update.
The standalone is working OK but as soon as I add EZK as a VSTi in either of my DAWs it loads the user interface but then crashes whatever DAW it is in leaving no crashlog available as far as I can see.
Initially, the rotary controls on all EZK instruments respond to a mouse, but when I press the browser button, select a MIDI example & click on “play” the DAW immediately crashes leaving nothing but a desktop screen.
I have actually uninstalled and re-downloaded/installed all my EZKs but nothing has changed.
Anyone else witht he same issue? Or anyone have any ideas?
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.
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
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.
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*
2
Thanked by: jamesmcconnon and JohnNo products in the cart.