You may also have some VST folder around - Ableton live cant understand them either, but either way - make sure the VST3 version are separate. If you have installed Cubase, or have VST version of plugins, then you might have some other VST folder as well in various semi-random locations.Ībleton live can only load 32 bit plugin, not 64 bit plugins (unless you use something like jbridge - in which case that is responsible for them). Notice its in the 64 bit programme files, not the x86 32 bit programme files. The new 64 bit VST2.x plugin folder might be at The old 32 bit with VST2.x plugins probably atĬ:\Program Files (x86)\Steinberg\VSTplugins Normally you should end up with two VSTPlugins folders: Live is a 32 bit application and being an IT person you know a process is either 32 bit or 64 bit with neither able to execute the others code. 64 bit plugins will not load in Live at all. I'm just suprised at how long the 64bit platform has been available, that there hasn't been more progress. On an upside ( for geeky joy ) I loaded 113 VST instances ( copy and pasted ) running a their own sequences and the CPU load was 63% ) Looks like the installers are determining the OS is 64bit and installing them as such, but Live doesn't handle them.Īlso any tips as it sounds like you've had some issues yourself. Looks like that may be the way forward for the instruments that don't require a registry entry. Work around for SOnic charge stuff is to use the original VST dll's from my XP build ( hence the compatability question ). The 64bit sylenth1 works with cubase but not Live, I've got around this with copying in the 32bit version. I've worked in IT for a number of years now and experience tells me this is a 64/32 bit thing rather than OS or drivers. New Processor, Motherboard, memory, power supply and case. Maybe they might license that tech in from someone who who has already done some bug fixing etc (jbridge perhaps?) rather than inflicting another flakey bridge on us. I dont suppose ableton will fair any better and if anything the other companies will be a year ahead in bug fixing their process bridges. In the end I moved off windows to a Mac/OSX and its massively more stable for me with the plugins, other software and gear I use - the only exception i latest Virus TI drivers or firmware seems to be a bit crap.Īs far live being 64 bit - Ive used 64 bit versions of cubase 6 and logic 9 - in both cases I gave up and went back to the 32 bit versions - mainly because the bridges for 32 bit plugins were still too unrelaible, though 64 bit plugins seemed fine. Similar if building a machine - worked on old machine - does work on new one - I might first suspect the machine build and/or OS install. When I have seen live go to hell moving to 64 bit - it was down to audio interface drivers or some other driver - ie nothing to do with Live. In general, use on 64 bit windows is far better due to windows potentially making much more memory available to Live. ![]() Same can be said of the plugins I have as well when used with Live. ![]() Live certainly seems to have issues for me on Windows 7/64, but no more than on any other version of windows (32 or 64 bit) I have used it on (caveat: given known reliable audio interface and other drivers). Which plugins, which audio interface and what was your previous machine? Is this one a custom build? and which version of live and anything that might be of use.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |