|
Post by KlangManipulation on Feb 14, 2014 18:35:27 GMT 1
is there anybody who use 1.2x seriously? a few days ago i thought to give it a try but after 15 minutes i was sure its not possible to work with it.
|
|
|
Post by sepoweruser on Feb 14, 2014 21:21:44 GMT 1
I do. Yes, unfortunately it's much more demanding on system ressources because of drop shadows and stuff which imho really isn't necessary at all to have. You really need a modern and powerful machine to work with a complex project, and even then it's extremely slow and sluggish compared to 1.1 ou 1.0. But it's great that 1.2 is available in a 64bit version now and the 64bit version can export to vst3 windows and mac.
In the 64bit version however most subcontrols don't work yet.
|
|
setronic
Synthedit regular
Posts: 293
Posts: 293
|
Post by setronic on Feb 17, 2014 20:34:33 GMT 1
i've loaded it to have a look. feel it messes up the system to have more than 1 version on the PC. like to keep things simple if possible.
i didn't like the property pane open full like that. there's never enough screen space as it is.
would be good to get regular screenshots at each version update.
|
|
tube
New Member
Posts: 8
Posts: 8
|
Post by tube on Feb 17, 2014 20:42:14 GMT 1
Hi i have make several trys to test if SE 1.2 64 is ( a little) stable. But i am can't compile a working 64 bit plugin for Cubase 5.5 . For testing i use here also savihost in 64 bit , but it crashes also on the first synth.dll call. Have send some easy dll with savi 64 bit to Jeff. Also a minimal VSTi , only a oscillator and a VCA don't work after compile. But maybe i do something wrong ??!! What are your experiences with SE 1.2 64 bit ?? So i still use SE 1.1 last stable. No problems all works.... but without 64 bit and oversampling..... Greets
Synthfreak
|
|
|
Post by sepoweruser on Feb 17, 2014 21:50:52 GMT 1
Be aware the 64bit version only compiles to VST3, so no dll (dll is VST2). So you need the VST3 Savihost to load them or another vst3 compatible host like Cubase or Studio One. Also regarding 3rd party modules they need to be in 64bit SDK3 format, otherwise they won't work. And regarding GUI so far only knobs and list entries work, all other subcontrols don't work.
|
|
tube
New Member
Posts: 8
Posts: 8
|
Post by tube on Feb 18, 2014 11:06:47 GMT 1
Hi , i use Cubase 5,5 64 bit , VST 3 . The testsynth crashes Cubase on the first call. Savihost 64 bit can also handle VST 3 . Crashes on the first call also. The tests-ynth was only a oscillator and a knob, not more. I have use the embedded modules in SE 64. So this s hould work in 64 bit. Any ideas ?? Who have made a running 64 bit plug ?? and how ?? Greets
Synthfreak
|
|
|
Post by Rob on Feb 19, 2014 12:26:09 GMT 1
I couldn't even locate the VST created with SE1.2 64bit..need to do another test. For now I just use the 32bit version if I want to build a VST plugin.
|
|
|
Post by sepoweruser on Feb 19, 2014 18:24:06 GMT 1
I couldn't even locate the VST created with SE1.2 64bit Check Edit->Preferences->File Locations->VST Plugins Here you can see the path and you too can change it to whatever location you want in to be
|
|
|
Post by Rob on Feb 20, 2014 11:24:47 GMT 1
Thanks.
|
|
|
Post by sepoweruser on Feb 20, 2014 11:57:09 GMT 1
For me it works well. On "save as vst" synthedit creates a folder named after the plugin name (let's name it "Plugin" - so the folder will be called "Plugin") in the vst plugin destination folder, and within the folder you'll find the vst3 plugin ("Plugin.vst3") as well as the needed external modules. It's different than in se 1.0 and 1.1 where the external modules were extracted to a separate folder. In se 1.2 both the plugin and the external modules reside within the same folder.
|
|
|
Post by Rob on Feb 20, 2014 12:10:17 GMT 1
Nvm, it does work here. I got confused with the 32bit version (doh). Update: After building a VST3 testplugin, Synthedit, Flstudio 11, Renoise and Reaper 64bit don't see the plugin. The plugin is in the correct VST plugins folder, where other 64bit plugins are located and show up in the Host. When I build a 32bit version of the testplugin, it does show up in every Host. Screenshot
|
|
|
Post by sepoweruser on Feb 20, 2014 15:11:18 GMT 1
After building a VST3 testplugin, Synthedit, Flstudio 11, Renoise and Reaper 64bit don't see the plugin. The plugin is in the correct VST plugins folder, where other 64bit plugins are located and show up in the Host. When I build a 32bit version of the testplugin, it does show up in every Host. ScreenshotFor VST3 plugins there's a fixed location which can't be changed or customized. Most VST3 sequencers only can detect VST3 plugins in this folder. In windows it's this folder (for 64bit VST3 plugins only): C:\Program Files\Common Files\VST3 So put your vst3 plugin there (the whole folder including the actual vst3 plugin and the modules) and the vst3 sequencers will see it then. Of course 64bit vst3 sequencers only will see it when it's 64bit too. For 32bit VST3 plugins within 64bit systems it's this folder: C:\Program Files (x86)\Common Files\VST3 Btw, Reaper doesn't support VST3, so it can't load VST3 plugins. As far as I know Renoise too doesn't support VST3. The same for Ableton Live. FL Studio 11 however should support it. So since synthedit offers 64bit plugins only in VST3 format they can't be used by all 64bit sequencers. Host that support VST3 so far are Cubase/Nuendo, Studio One, FL Studio, Sonar, Vienna Ensemble Pro and SaviHost/VST Host. So let's hope the others will follow too soon.
|
|
|
Post by Rob on Feb 20, 2014 16:18:01 GMT 1
Oh ok, didn't know that.. I relocated the plugin, FLstudio now sees the plugin. Thanks.
|
|
|
Post by Rob on Feb 20, 2014 16:24:40 GMT 1
* Plugin built using SE 1.21070 * - Plugin seems to run fine in Savihost. - I keep getting this error in FLstudio while playing a pattern. (I can click it away, but after a short while it returns)
|
|
|
Post by sepoweruser on Feb 21, 2014 12:25:01 GMT 1
As far as I know FL Studio isn't 64bit native yet, so it uses an internal bit-bridge to bridge native 64bit plugins to 32bit. Such bridges often are faulty, and I guess this issue could be caused by the bridge. But I'm not sure. They however seem to work on a native 64bit version of FL Studio and already offer a beta version: www.image-line.com/documents/news.php?entry_id=1361491430If I were you I'd only test the VST3 64bit plugins in real native 64bit hosts which have a VST3 interface, e.g. Cubase, Studio One or Sonar X3.
|
|
|
Post by Rob on Feb 21, 2014 20:40:31 GMT 1
Hmm ic, ah well.. i'll just wait then. Use the 32bit version of SE1.2 much more for now.
|
|
|
Post by KlangManipulation on Feb 22, 2014 2:41:49 GMT 1
there is a FL-Studio 64 beta. so i think this version will load 64bit plugins nativly (but im not sure) i will take a look to it.
EDIT: mmm... i can install the 64 bit beta. if someone send me a test 64bit.dll i will check it.
|
|
|
Post by sepoweruser on Feb 22, 2014 12:53:43 GMT 1
Why don't you simply compile a simple plugin with SE 1.2 64bit? FL Studio can load VST3, so the 64bit beta should be able to load a 64bit VST3 compiled by synthedit.
|
|
|
Post by KlangManipulation on Feb 25, 2014 22:43:08 GMT 1
because i dont use SE1.2 and i cant (dont want) build a plugin because of the crap 1.2GUI btw it was a offer to test a plugin, not to build one. and i am lazy
|
|
|
Post by Mastrcode on Mar 21, 2014 20:58:36 GMT 1
I used SE 1.2 for my last made drum plugin. It worked fine for me and the exported VST also works fine. I exported just in 32 bit, beause i used some of the 32 bit 3rd party modules which are not yet written in 64 bit.
|
|