User patch format question, and an idea :)

Official support for: mutools.com
RELATED
PRODUCTS

Post

One of the great things about Mulab is that it is so small and that it is all in one folder that you can take with you on a USB pen drive. However, I just bought Retrologue, which is a great synth, but unfortunately it uses eLicenser and its patch manager does not allow me to save presets where I want, forcing me to use a specific folder on my computer.

This has made me wonder: When I use Mulab's own patch saving feature, do the resulting FXP patches include all Retrologue parameters and in a correct fashion? I am asking because the guy from Steinberg told me they abandoned that format years ago on their own synths and use VST3 instead these days. I suppose they did not do that for fun, but because the new format is somehow superior.



Apart from this simple question, this whole matter of licensing and lack of path flexibility has made me think if an offline mode were not a good idea.
People using several synths, huge sample libraries and other plugins that depend on eLicenser and similar systems based on a specific computer will probably have difficulty taking their Mulab projects with them and using them on the way or on somebody else's computer because when they open a project, they might be missing all kinds of tracks because the corresponding VSTs are no longer available.

So how about an Offline button? :) When you click it, Mulab checks the current project for dependencies on dll's, patches etc. outside the user-defined Offline environment (that you have on or will copy to your USB pen drive) and tells you the issues. And for those tracks' plugins you can specify offline substitute plugins :D So for instance I could specify that in offline mode Mulab will use, say, Charlatan or some other freeware synth instead of Retrologue. It would look for a Charlatan patch of the same name as the one from Retrologue. This way the user would not be confused as he could create a simple "lush_strings" preset for the offline synth as well (ignoring the fact that the sound might be much less lush on Charlatan).
When saving a project, the offline mode could also offer the possibilty of mixing down all tracks requiring online plugins to corresponding audio tracks and saving them in addition to the existing Midi tracks. This would make sense for instance for more complex tracks, like drums and percussion or arps.

And when you are back on your own computer again, you simply switch the project to online and use the sounds of Arturia, Steinberg and similar plugins again :) And it would check for all things that were added while offline, including patches so that you can recreate them on your online synths.

Just an idea :)

Post

fluffy_little_something wrote:When I use Mulab's own patch saving feature, do the resulting FXP patches include all Retrologue parameters and in a correct fashion?
Depends on the VST plugin, but i woud expect all relevant data is included, just like you save a FXP from the VST itself.

Post

mutools wrote:
fluffy_little_something wrote:When I use Mulab's own patch saving feature, do the resulting FXP patches include all Retrologue parameters and in a correct fashion?
Depends on the VST plugin, but i woud expect all relevant data is included, just like you save a FXP from the VST itself.
Once I get my license, I suppose I will have to create a specific patch, save it in both formats, load it in two instances and compare the result parameter by parameter.

Post

i think that is a silly idea. i mean, are you expecting jo to code a mechanism that saves you from doing leg work related to your own little problems? you really do want it all simply handed to you! in this light your attack on my website seems a little more in perspective. what wishful drivel you spout! you are in a dream world. :roll: :hihi:

Post

Could be useful if a log could be made to list the VST's and patches used for future reference.
- PolyHostInterface - VST2/3 Plugin chainer

- For curious minds... -

Post

sounds useless, seriously. like, who is gonna sit there and do all that nerd work? like, thats what we need, more hidden useless features for lazy bastards who cant afford to keep their synths together.

Post

Sorry MUTED!
- PolyHostInterface - VST2/3 Plugin chainer

- For curious minds... -

Post

> DiGiT < wrote:i think that is a silly idea. i mean, are you expecting jo to code a mechanism that saves you from doing leg work related to your own little problems? you really do want it all simply handed to you! in this light your attack on my website seems a little more in perspective. what wishful drivel you spout! you are in a dream world. :roll: :hihi:
Seriously man lay off. Just because we're not fanatic about your site doesn't mean you have to be pessimistic to us.

I'm 50/50 on this. On one hand I get that it would be nice to have an "offline" state to keep your projects going wherever you need them to. On the other hand, I think that's the VST devs job to fix. Elicenser and things related are annoying. It would be best to have a serial code (though I see how it can be insecure).
Software portfolio
M.N.I.E - soon to be my musical portfolio
Hey, I'm Eurydice(Izzy for short) - she/her :hug:

Post

Actually I forgot there's VSTNotes and the like! But maybe something like this could be built into MuLab? No doubt time will come when VSTNotes won't be compatible?
- PolyHostInterface - VST2/3 Plugin chainer

- For curious minds... -

Post

seriously what? i hate the idea. what? im not allowed to shit on an idea i dont like? seriously, YOU shove off. oh and get your useless posts off of my site you wanker.

Post

Best thing to do dakkra is mute the mofo! :hihi:
- PolyHostInterface - VST2/3 Plugin chainer

- For curious minds... -

Post

haha wankers, the lot of ya :hihi:

Post

dakkra wrote:I'm 50/50 on this. On one hand I get that it would be nice to have an "offline" state to keep your projects going wherever you need them to. On the other hand, I think that's the VST devs job to fix. Elicenser and things related are annoying. It would be best to have a serial code (though I see how it can be insecure).
Yes, but I'm afraid the trend will go in the other direction, not least because of the EU ruling on license transfers. That will make companies become even more interested in such complex license systems.

It was just an idea. I myself am a freelancer, I work from home, so I use Mulab only at home, so no problem, but I thought more mobile people might face such problems...

I remember when TAL launched U-NO-LX 2. The projects where I had used the first version did not recognize the new version. That gave me an idea of how annoying it must be to have missing tracks in old projects...
Last edited by fluffy_little_something on Tue Mar 26, 2013 5:54 pm, edited 2 times in total.

Post

yeah well it was a SILLY idea.

Post

Isn't there a way to make it mobile though?
- PolyHostInterface - VST2/3 Plugin chainer

- For curious minds... -

Post Reply

Return to “MuTools”