Any luck getting NI Pro53 to work in Win10
-
- KVRist
- 85 posts since 15 Oct, 2006
Hi,
now i solved my problem with Ableton not working with Scope ASIO on Win 10 (running Ableton in Win8 compatibility mode-it was that simple). now i cannot get the old NI pro 53 to work, not in standalone nor bridged with jbridge . i am aware that NI doesnt support this synth any longer, but it was working fine in Win8. I am not going back for this synth, but it has some nice sounds, so i wonder if there is anyone running it in Win 10 64bit?
dennis
now i solved my problem with Ableton not working with Scope ASIO on Win 10 (running Ableton in Win8 compatibility mode-it was that simple). now i cannot get the old NI pro 53 to work, not in standalone nor bridged with jbridge . i am aware that NI doesnt support this synth any longer, but it was working fine in Win8. I am not going back for this synth, but it has some nice sounds, so i wonder if there is anyone running it in Win 10 64bit?
dennis
- KVRAF
- 2991 posts since 13 Apr, 2008 from Charleston, SC
I am running it right now as we speak in standalone mode in Win10. I do not use jBridge because Cubase x64 has its own bridge which works fine with it. That means I have not tested in Ableton Love. But I might just snage jBridge just to say I did and see if I can get it to work in Ableton.
Will report back, but so far it works just fine in Cubase Pro 8 64 on Win10 64.
Will report back, but so far it works just fine in Cubase Pro 8 64 on Win10 64.
-
- KVRist
- Topic Starter
- 85 posts since 15 Oct, 2006
Thanks for the answer. I tried cubase and fruityloops as well ( too many daws) and i even installed kore 2 to try to load pro 53 without success. Then i tried to install Pro 53 on another computer and on my musiccomputer on the SSD with the fresh Win10 installation, but no success either. I tried different locations in case there is something wrong with the user rights and i tried running the installer and the program in different compatibility modes as administrator.
I see the Pro 53 running in the task manager consuming roughly 15% of the CPU and 6mb memory, but there is no GUI or sound.
How did you get that software running? Did you use the default location for installation? Do you use the compatibility mode?
I see the Pro 53 running in the task manager consuming roughly 15% of the CPU and 6mb memory, but there is no GUI or sound.
How did you get that software running? Did you use the default location for installation? Do you use the compatibility mode?
- KVRAF
- 37549 posts since 14 Sep, 2002 from In teh net
I can understand it not working as a standalone but I can't see why not as a plugin as long as in a 32 bit host. The Mac version still works fine on modern systems (even the standalone). What 32 bit hosts have you tried it in? Sometimes I find Bidule loads older stuff nothing else will.
- KVRAF
- 24462 posts since 7 Jan, 2009 from Croatia
Did you try running the EXE file in Win 7 (or Win XP) compatibility mode?
- KVRAF
- 25849 posts since 20 Jan, 2008 from a star near where you are
The demo file is available for test pilots to check out in Win 10
http://ftp.native-instruments.com/Pro-53/
And pretty good demo limitations, none interrupted sessions of 30 minutes, and when that has run its course you just load it up again to start another 30 min session
http://ftp.native-instruments.com/Pro-53/
And pretty good demo limitations, none interrupted sessions of 30 minutes, and when that has run its course you just load it up again to start another 30 min session
-
- KVRist
- Topic Starter
- 85 posts since 15 Oct, 2006
Hi! Thanks for all the tips.
Now i have tried the following: On a clean Win 10 64bit install i installed FruityLoops 32 bit and Ableton 9,5 32bit, MuLab Mux 32bit and DDMF metaplugin 32bit, i tried to install bidule, but there doesnt seem to be a demolicense available.
I installed the VST and the standalone version of Pro 53 in the VST folder in C://VSTPlugins hoping i have all user rights there. I installed the PRo 53 in Win XP, Win Vista, WIn 7 and Win 8 compatibility mode before each testing (which was a PITA because i run my Win10 testversion from a USB stick and it is sslooowww...)
Anyway same result: Could not get the stand alone version to run and both FruityLoops and Ableton are crashing (or hangig up) when trying to scan the plugin. Same with metaplugin and MUX running inside ableton or FL.
Anyone has any more ideas? If not i just might give up. It is not worth the time any more. I like the HPF option which i dont have in the Arturia Version, but i might get along with that one.
Now i have tried the following: On a clean Win 10 64bit install i installed FruityLoops 32 bit and Ableton 9,5 32bit, MuLab Mux 32bit and DDMF metaplugin 32bit, i tried to install bidule, but there doesnt seem to be a demolicense available.
I installed the VST and the standalone version of Pro 53 in the VST folder in C://VSTPlugins hoping i have all user rights there. I installed the PRo 53 in Win XP, Win Vista, WIn 7 and Win 8 compatibility mode before each testing (which was a PITA because i run my Win10 testversion from a USB stick and it is sslooowww...)
Anyway same result: Could not get the stand alone version to run and both FruityLoops and Ableton are crashing (or hangig up) when trying to scan the plugin. Same with metaplugin and MUX running inside ableton or FL.
Anyone has any more ideas? If not i just might give up. It is not worth the time any more. I like the HPF option which i dont have in the Arturia Version, but i might get along with that one.
- KVRAF
- 11162 posts since 16 Mar, 2003 from Porto - Portugal
I remember to once have problems just because I installed NI plug-ins in a location other than the default one. Did you try to install it in Program Files (x86)/VstPlugIns or whatever is the default location the installer has? Just a blind guess, but who knows?blaubär wrote:Hi! Thanks for all the tips.
Now i have tried the following: On a clean Win 10 64bit install i installed FruityLoops 32 bit and Ableton 9,5 32bit, MuLab Mux 32bit and DDMF metaplugin 32bit, i tried to install bidule, but there doesnt seem to be a demolicense available.
I installed the VST and the standalone version of Pro 53 in the VST folder in C://VSTPlugins hoping i have all user rights there. I installed the PRo 53 in Win XP, Win Vista, WIn 7 and Win 8 compatibility mode before each testing (which was a PITA because i run my Win10 testversion from a USB stick and it is sslooowww...)
Anyway same result: Could not get the stand alone version to run and both FruityLoops and Ableton are crashing (or hangig up) when trying to scan the plugin. Same with metaplugin and MUX running inside ableton or FL.
Anyone has any more ideas? If not i just might give up. It is not worth the time any more. I like the HPF option which i dont have in the Arturia Version, but i might get along with that one.
Fernando (FMR)
- KVRAF
- 25849 posts since 20 Jan, 2008 from a star near where you are
Have you tried to load the VST with SAVI-host, very simple and easy, no installation necessary and will quickly determine if it loads the VSTi or notblaubär wrote:Now i have tried the following: On a clean Win 10 64bit install i installed FruityLoops 32 bit and Ableton 9,5 32bit, MuLab Mux 32bit and DDMF metaplugin 32bit, i tried to install bidule, but there doesnt seem to be a demolicense available.
http://www.hermannseib.com/english/savihost.htm
-
- KVRist
- 132 posts since 16 Dec, 2011
For running the Pro53 as plugin in Ableton Live you'll most likely need to use an older version of Ableton Live (prior to 9.2):blaubär wrote:Now i have tried the following: On a clean Win 10 64bit install i installed FruityLoops 32 bit and Ableton 9,5 32bit
...
Anyway same result: Could not get the stand alone version to run and both FruityLoops and Ableton are crashing (or hangig up) when trying to scan the plugin...
https://www.ableton.com/en/help/article ... ements-92/
-
- KVRist
- 298 posts since 22 Apr, 2008 from Waltham-st-Lawrence.
I am running it fine in Live 9.5, Windows 10 via Jbridge with no problems at all. Pro 53 version 3.0.5.001. Cheers Glynbo.
-
- KVRist
- Topic Starter
- 85 posts since 15 Oct, 2006
No luck with SAVI host either. Tried the x86 version with the unbridged plugin, the x64 with the bridged plugin. I have other bridged 32bit plugins (quadrasid and Dune CM) and they work perfectly with jbridge and the 32bit versions load without a problem in SAVI host. Seems to be just the Pro53
.I used the Pro53 without a problem bridged in Live 9.5 under Win 8.I think there might be a simple solution and there seem to be people running that plugin. BTW i tried it on my Surface Pro 2 as well without any result (also running Win 10)
- KVRAF
- 2991 posts since 13 Apr, 2008 from Charleston, SC
Are you using the last released version of Pro53 (3.0.5.1)? I seem to recall installing an older version first and then updating (maybe even from Pro-52).
But as I said mine works flawlessly.
But as I said mine works flawlessly.
