Softube Modular

VST, AU, AAX, CLAP, etc. Plugin Virtual Instruments Discussion
Post Reply New Topic
RELATED
PRODUCTS
Softube Modular

Post

For the couple of people who were asking about my sound library, you can find it in Soundware.

http://www.kvraudio.com/forum/viewtopic ... 6#p6524976

Post

Okay, I don't know if anybody else is having problems but Softube Modular not having its own internal browser is presenting problems for some DAWs.

In Cubase, you can simply type the folder name in the search box and it will list all the presets in that folder. No problem.

However, in MuLab, I can't find any way of doing this and can't access any presets in the sub folder I created.

I have yet to test this in Reaper but will do so shortly.

Yeah, not having its own browser is turning into a real PITA.

Post

So Softube needs to add a patch browser so you can make money selling soundbanks? Don't think so.

Post

It needs to add a patch browser to make it fully compatible with all DAWs and platforms. Also I presume Wag's patches are in fxp format so not compatible with Logic and AU? If they had a browser they could use a universal patch format instead of relying on the host which is not an optimal solution given the broad range of plugins types most hosts support these days.

Post

I'd like to see it get a patch browser of its own too - it feels unfinished as is.

Post

Reefius wrote:So Softube needs to add a patch browser so you can make money selling soundbanks? Don't think so.
No, it needs a patch browser because it's a PITA to use the way it is.

Post

aMUSEd wrote:It needs to add a patch browser to make it fully compatible with all DAWs and platforms. Also I presume Wag's patches are in fxp format so not compatible with Logic and AU? If they had a browser they could use a universal patch format instead of relying on the host which is not an optimal solution given the broad range of plugins types most hosts support these days.
You could still keep the fxp files as long as the plugin has a built-in browser within all plugin formats.

Waldorf synths like e.g. Largo and PPG Wave 3.V and also the Tone2 synths use fxp files too but they got a built-in browser so those fxp files work in all formats (e.g. VST2, VST3, AU, AAX).

With Waldorf Edition 2 there is still a comparavble problem like now in Softtube Modular (while there you could import fxp/fxb files to the VST3 an AAX plugins by drag & drop from the file browser of your OS and then re-save them).
The new NKS implementation somehow added a common patch format that works in all plugin formats (also as the Komplete Kontrol and Maschine 2 plugins are available as plugins in all formats) but hopefully a future update of those WE 2 plugins also will include at least a simple load/save feature for fxp/fxb or even a full browser.


BTW Bitwig Studio does not seem to allow loading fxp and fxb files with the host yet. To use the Waldorf Edition 2 patches there i imported the files by drag & drop to the VST2 plugin and re-saved in Bitwig Studio's own format (while those files always include a full bank and not just a single patch, comparable to the dedicated VST3 and AAX presets formats).
Ingo Weidner
Win 10 Home 64-bit / mobile i7-7700HQ 2.8 GHz / 16GB RAM //
Live 10 Suite / Cubase Pro 9.5 / Pro Tools Ultimate 2021 // NI Komplete Kontrol S61 Mk1

Post

Reefius wrote:So Softube needs to add a patch browser so you can make money selling soundbanks? Don't think so.
Have you been in coma? Did you actually tried to use it? Quite a lot of people brag about lack of proper preset browser in Modular. Not just at this forum.

Yes softube need to add patch browser like every other decent synth developer. We think so.

Post

kmonkey wrote:
Reefius wrote:So Softube needs to add a patch browser so you can make money selling soundbanks? Don't think so.
Have you been in coma? Did you actually tried to use it? Quite a lot of people brag about lack of proper preset browser in Modular. Not just at this forum.

Yes softube need to add patch browser like every other decent synth developer. We think so.
Ignore him. He's just being an ass.

Par for the course around here.

Post

BUT internal preset browsers, don't solve the issue for some of us....

I use a Push 2, so using the standard VST patches means I can browse them, rather than having to use the mouse/keyboard. the patches therefore 'appear' integrated.
yeah, its not perfect, but its better than nothing.

Until,we get a standardised API for browsing (like NKS, but open to all DAWs/Controllers), Im not a fan of internal browsers, regardless of the extra features they provide, because they lack this integration.

(and whilst I feel the pain of sound designers, having to support VST/AU etc formats... as an end-user I tend to only use one format, so can save my own patches in one format without issue)

as always, there are different sides to all 'arguments'

Post

Or the developers could do like Oddity 2 and have both tied together - best of both worlds.

Post

Okay, any Live users here? Before I go crazy trying to find a way to fix this (I'm thinking I'm SOL) is there a way to convert or save fxb format presets so that they are compatible in Live?

I don't have LIve, but if there is a way to do this, I'll download the demo (if one exists) and do the conversion, even if I have to do it one patch at a time.

If not, I'm going to have to specifically put on the sale page that this library does not work in Live, even though I've already put it's in vstpreset and fxb format ONLY.

But I should know from experience that some people don't read sales pages.

Post

I use live - when I use Live's built in save/load, it's saving as .fxb files.

Post

I've attached a patch I saved in live, in case that helps.
You do not have the required permissions to view the files attached to this post.

Post

Ingonator wrote:
aMUSEd wrote:It needs to add a patch browser to make it fully compatible with all DAWs and platforms. Also I presume Wag's patches are in fxp format so not compatible with Logic and AU? If they had a browser they could use a universal patch format instead of relying on the host which is not an optimal solution given the broad range of plugins types most hosts support these days.
You could still keep the fxp files as long as the plugin has a built-in browser within all plugin formats.
Yes, if there was a built in browser it could be in any format and it would load in any host, Linplug also uses fxp, so do several others, but they don't assume the host is going to take responsibility for preset management because these days you just can't rely on hosts to do that. It's not like the old days when there was just fxp/b and the hosts did this, these days there are multiple formats and some hosts do not support all plugin formats, and even less support all their plugins preset formats (not talking about proprietary formats here, just the standard formats that are part of each plugin format spec - fxp for VST 2, AUpresets for AU plugins and vstpresets for VST3 plugins). For example Tracktion and Reaper support all 3 plugin formats but support for AU and VST3 plugin presets is incomplete, Bitwig still can't even save fxp presets despite it only supporting VST2, Live doesn't properly support AU presets, Logic only supports AU, and so on.

Softube are living in the past - their approach was reasonable for their previous plugins because they were mostly mastering type fx and those generally don't need lots of presets, but for an instrument or creative fx plugin that is a basic requirement and they should have considered that.

Post Reply

Return to “Instruments”