Page 1 of 1
Have you had any troubles with 64 bit wrappers?
Posted: Sat Sep 20, 2014 12:43 am
by Perfect Human Interface
Just a simple inquiry: have you tested any of your Flowstone VST exports in existing 64 bit wrappers and have you run into any issues doing so?
Of course many people already use 64 bit DAWs, but some of those DAWs also contain their own 32 bit wrappers (and I believe others are available from other parties?). So I'm hoping to find out if people have had good or bad experiences with any of these wrappers.
Re: Have you had any troubles with 64 bit wrappers?
Posted: Sun Sep 21, 2014 10:31 am
by CoreStylerz
Perfect Human Interface wrote:Just a simple inquiry: have you tested any of your Flowstone VST exports in existing 64 bit wrappers and have you run into any issues doing so?
Of course many people already use 64 bit DAWs, but some of those DAWs also contain their own 32 bit wrappers (and I believe others are available from other parties?). So I'm hoping to find out if people have had good or bad experiences with any of these wrappers.
I've tried all my plugs with Cockos reaper bridge (auto) and they works very well. Dominus i'ts just a little slower and sometimes it crackles (when changing patch) but are very usable.
Fl studio wrapping works just cool.
The problem on the marketing side is just there's a stigma to non-native 64 bit plugins.
Many people will avoid them. I receiving weekly request for 64 bit plugins.
Re: Have you had any troubles with 64 bit wrappers?
Posted: Sun Sep 21, 2014 10:36 am
by kortezzzz
Tried my synths on reaper 64bit, cubase5 (with a jbridge), studio one2 (with a jbridge), bitwig studio (which works as 64bit by default on 64bit OS, but still loads 32bit plugins that operate with the limitation of 3.25gb ram). Best results on reaper; It probably has the best built-in bridge and it's cpu meter shows the the best performances compared the other DAWs I mentioned. On cubase, works fine but sometimes I get few small cpu spikes when moving the gui or when switching presets. studio one2 showed the worst performances so far and I got spikes from it very often.
On bitwig, everything worked Ok, but small spikes occur when the gui called after being hidden.
Seems like if FS gonna move into 64bit world and add proper multicore support, all the cpu\memory problems will be gone with it. So far, most of my bad behavior problems caused by FS gui management and the preset system (on some DAWs).