LinPlug

woodster · Post by **woodster** » Fri Jul 04, 2008 8:52 pm

Hello Peter,

I've tried creating .vstpresets for use in Cubase/Nuendo 4 using CronoX3 and Octopus.
The saving mechanism inside the Meday Bay that Cubase 4 utilises allows me to save a CronoX3/Octopus preset as a .vstpreset,but both products do not respond to an incoming .vstpreset command.
Has Linplug considered supporting .vstpresets, or indeed the new(ish) VST3 protocol?

Cheers

symplectiq · Post by **symplectiq** » Sat Jul 05, 2008 2:07 pm

Unless every host on the planet will support VST3 the answer is no.

woodster · Post by **woodster** » Sun Jul 06, 2008 11:53 am

chaoticz wrote:Unless every host on the planet will support VST3 the answer is no.

Lol, is that an official response from Linplug ?.
It's not as if every host on the planet supports VST2.xx, or AU or RTAS, but they are still platforms that are developed for.

I know the general consensus on VST3 has been lukewarm, but as an end user it would be nice to able to get away from the rather laborious process of choosing sounds using the synths internal preset mechanism, when there are much more convenient methods available.
Anyway it wouldn't take Linplug to develop for VST3 to solve my issue, more just simply supporting the FXP/FXB protocols fully.
Then I could convert them myself at least.
As it is CronoX3 and Octopus, don't act like 99% of other VSTi's in this regard.
Maybe if Linplug are updating to VST 2.4 in the future, you could look at the preset integration with the host software while your there?.

Peter from LinPlug · Post by **Peter from LinPlug** » Mon Jul 07, 2008 7:05 am

We'll consider it, however, usually we got positive feedback on our own mechanism, so it seems not be much demand from our users yet. But we'll see...

woodster · Post by **woodster** » Mon Jul 07, 2008 9:27 am

Peter from LinPlug wrote:We'll consider it, however, usually we got positive feedback on our own mechanism, so it seems not be much demand from our users yet. But we'll see...

Hi Peter,

Many thanks for the reply.

Some of the CronoX3 preset lists are so long it can take an age pressing that tiny triangle to go up and down.
There are the next/previous buttons obviously.
The beauty of Media Bay is its speed and also alowing you to browse ALL of your presets in one go, without having to load banks first.
Both CronoX3 and Octopus don't respond to .vstpresets, even though they are able to created.
Thanks again for your response.

Peter from LinPlug · Post by **Peter from LinPlug** » Mon Jul 07, 2008 9:48 am

Ok, I'll see what we do with Albino 4 in this respect, maybe its something for CronoX and Octopus too then, I',ll have a closer look at this issue.

Thanks for the heads up,

Peter

Cone · Post by **Cone** » Mon Jul 28, 2008 6:30 pm

Peter from LinPlug wrote:Ok, I'll see what we do with Albino 4 in this respect, maybe its something for CronoX and Octopus too then, I',ll have a closer look at this issue.

Well, if you decide to bite the bullet, then please do Audio Unit presets also. I would love to be able to browse the presets of all my LinPlug synths using the Ableton Live browser. (It knows about .aupreset files on the Mac.)

bM3w · Post by **bM3w** » Mon Jul 28, 2008 6:56 pm

Peter from LinPlug wrote:Ok, I'll see what we do with Albino 4 in this respect, maybe its something for CronoX and Octopus too then, I',ll have a closer look at this issue.

Thanks for the heads up,

Peter

Hi Peter, thanks for investigating in this issue. Maybe - once you found out - you can let us know, what the actual problem is without going too deep into the details and secrects of coding

Since months I'm trying to find out about the preset issue in Cubase 4. The main question is if VST3 can be blamed for it (which I doubt) or if it's an incomplete implementation of the VST 2.x protocol as woodster suggests. As a matter of fact there are quite a few other VSTIs with the same/similar issue and all of them have their own preset manager. Unfortunately Steinberg is basically dead quite about it and other developers obviously aren't really interested in fixing. Perhaps they don't completetly understand the full extend of the issue and where it's coming from or they might just don't care.

Thanks,
bM3w

LfmC · Post by **LfmC** » Fri Jun 25, 2010 12:35 pm

Why are Linplug's instruments the only ones who have no option of converting FXP/FXB to vstpreset format in cubase 5? I've tried countless other VSTi's and all of them have this option.
Some VSTi's use their own preset manager, but even N.I. instruments have an option to "convert VST list to vstpresets..." from the dropdown menu and (slow, but working) way of exporting to FXP/FXB from within the VSTi itself.

It may seem like an insignificant thing, but if you used cubase media library, you'd know how practical it was to have all the presets of all vst's categorized, sorted and able to load together with a vst in a single click. Once one get's into it, it's amazing and most VST's support it. A few make it a chore to convert presets, but only Linplug is completely locked with no way of working ATM.

Any plans to fix this soon?

Peter from LinPlug · Post by **Peter from LinPlug** » Fri Jun 25, 2010 1:02 pm

LfmC wrote:Some VSTi's use their own preset manager, but even N.I. instruments have an option to "convert VST list to vstpresets..." from the dropdown menu and (slow, but working) way of exporting to FXP/FXB from within the VSTi itself.

All our presets ARE in fxp format, please check the respective folder (e.g. Alpha 3 Banks/Dance/... all fxp). Octopus for certain reason is an exception.

LfmC · Post by **LfmC** » Fri Jun 25, 2010 1:22 pm

Thanks for the quick reply, Peter.

Here's the thing, I'm not sure how to best explain the problem, so here are the pics from cubase:

This is a screenshot of Discovery, but it's the same for all other VSTi's except linplug's; cubase offers the option to load/save presets, import old format FXP/FXB... and most important thing: the option to convert program list to vstpreset format. This is the only way to convert FXP/FXB to cubase's native .vstpreset format.

Now here's Albino:

As you can see, the option is simply not there. And for once, I think it's not steiberg's fault, as all the other VST's have this option, even the one's who use their own preset management system and don't even use FXP/FXB.

And without this option, there is simply no way whatsoever to use Linplug's VSTi's in cubase mediabay or have their presets imported.

Peter from LinPlug · Post by **Peter from LinPlug** » Fri Jun 25, 2010 1:31 pm

Ah, ok, I see. Hmm, no clue actually,I will try to find out whats cubase expecting from us

Elektrobolt · Post by **Elektrobolt** » Fri Jun 25, 2010 9:52 pm

+1 for the RMV

I'd like VSTPresets AND a VST3 version, please.

Thanks for the support, Peter.

Peter from LinPlug · Post by **Peter from LinPlug** » Mon Jun 28, 2010 6:33 am

I've been checking this and ... as I didnt get much further I got in touch with Steinberg to find out whats actually missing. Together we came to the point where its looking like a bug in Cubase, its now in the bug database of Steinberg and will hopefully be fixed with a future update of Cubase.

LfmC · Post by **LfmC** » Mon Jun 28, 2010 9:09 am

Peter from LinPlug wrote:...its looking like a bug in Cubase

Why am I not suprised..

will hopefully be fixed with a future update of Cubase

There's always wishful thinking

Thanks for investigating, Peter. I can only wish SB takes some pointers from you when it comes to support quality and speed.

LinPlug

KVR Audio

Any plans to support .vstpresets and/or VST3