BrainModular

Exported VST limitations

2012-08-09T10:56:21+02:00

An alternative to a menu for VST folder for the exported VST,
is that the folder where the Usine VST is-
contains also the .dll for the VST used in the patch.
This is the method that MAX/msp use.
Cheers 8D

Statistics: Posted by nix808 — 09 Aug 2012, 10:56

Exported VST limitations

2012-08-08T19:22:10+02:00

ah thanks for the clarification... i didn't think of trying it that way! anyway, thats really cool.

Statistics: Posted by artificial — 08 Aug 2012, 19:22

Exported VST limitations

2012-08-06T18:56:14+02:00

Hello artificial,

Yes, you missed a small detail.

The window size is exactly the VST size when you export your plug-in. You just have to decide the size before exporting it to have exactly the same on finish.

Best

Statistics: Posted by multiphone — 06 Aug 2012, 18:56

Exported VST limitations

2012-08-06T18:30:23+02:00

maybe I have overseen something, but one thing i would love to see is the possibility to set the vsts window size... at the moment all exported vsts are fullscreen! what do you think about it?

Statistics: Posted by artificial — 06 Aug 2012, 18:30

Exported VST limitations

2012-08-05T19:42:06+02:00

Just checking in to say this function is very necessary for my integration
of SynthMaker and Usine modules,
if I want to share products.
For example-
I want to use the Usine local synchro to clock a MIDI
sequencer that has been built with SM.
For my users, it is not possible to specify the file path of my SM component.
Thanks Senso.
I think a reasonably simple solution is to have a VST folder option for
the exported Usine VSTi.
edit- This problem also occurs in exported .exe s.
hmm, if there was a solution I would be very happy,
because Usine has solved timing issues in 2 projects on my system.
I could then distribute them as products.

Statistics: Posted by nix808 — 05 Aug 2012, 19:42

Exported VST limitations

2011-12-27T16:55:43+02:00

Interesting discussion.
Let me think about this but the exported vst is designed to have the simplest setup as possible, so?

Oh, and being able to export a VST with multi i/o would be a big plus! Autodect how many inputs/ outputs are active in the workspace and apply it to the VST when exporting.

Export with Easine does!

Also if each exported VST could share a common data folder would be nice as it gets cluttered and uses a lot of drive space with each VST creating it's own.

It's not the background idea of the exportation: be independent.

Statistics: Posted by senso — 27 Dec 2011, 15:55

Exported VST limitations

2011-12-20T00:59:21+02:00

Oh, and being able to export a VST with multi i/o would be a big plus! Autodect how many inputs/ outputs are active in the workspace and apply it to the VST when exporting.

Also if each exported VST could share a common data folder would be nice as it gets cluttered and uses a lot of drive space with each VST creating it's own.

Statistics: Posted by gurulogic — 19 Dec 2011, 23:59

Exported VST limitations

2011-12-19T11:23:56+02:00

I am testing the exported VST function as a solution for a single VST plugin preset manager / loader however neither of these have much potential at the moment as the exported VST relies on the path to the hosted VST being in the exact same file path it was when the VST
was exported so any system changes could be catastophic to any saved work and also the loadpatch module is unable to work from the exported VST so I am unable to use the Usine VST as a VST loader.
It would be nice if the exported VST could still have the VST and Usine Library folder paths setup option available spo that the exported VST could be a usable VST host and also be able to load predetermined patches.

Statistics: Posted by gurulogic — 19 Dec 2011, 10:23

Exported VST limitations

2012-08-09T10:56:21+02:00

Statistics: Posted by nix808 — 09 Aug 2012, 10:56

Exported VST limitations

2012-08-08T19:22:10+02:00

ah thanks for the clarification... i didn't think of trying it that way! anyway, thats really cool.

Statistics: Posted by artificial — 08 Aug 2012, 19:22

Exported VST limitations

2012-08-06T18:56:14+02:00

Statistics: Posted by multiphone — 06 Aug 2012, 18:56

Exported VST limitations

2012-08-06T18:30:23+02:00

maybe I have overseen something, but one thing i would love to see is the possibility to set the vsts window size... at the moment all exported vsts are fullscreen! what do you think about it?

Statistics: Posted by artificial — 06 Aug 2012, 18:30

Exported VST limitations

2012-08-05T19:42:06+02:00

Statistics: Posted by nix808 — 05 Aug 2012, 19:42

Exported VST limitations

2011-12-27T16:55:43+02:00

Interesting discussion.
Let me think about this but the exported vst is designed to have the simplest setup as possible, so?

Oh, and being able to export a VST with multi i/o would be a big plus! Autodect how many inputs/ outputs are active in the workspace and apply it to the VST when exporting.

Export with Easine does!

Also if each exported VST could share a common data folder would be nice as it gets cluttered and uses a lot of drive space with each VST creating it's own.

It's not the background idea of the exportation: be independent.

Statistics: Posted by senso — 27 Dec 2011, 15:55

Exported VST limitations

2011-12-20T00:59:21+02:00

Statistics: Posted by gurulogic — 19 Dec 2011, 23:59

Exported VST limitations

2011-12-19T11:23:56+02:00

Statistics: Posted by gurulogic — 19 Dec 2011, 10:23