is this possible in cubase ?

Discussion in 'Working with Sound' started by wouala woualouf, Apr 22, 2019.

  1. wouala woualouf

    wouala woualouf Platinum Record

    Joined:
    Jul 28, 2015
    Messages:
    297
    Likes Received:
    240
    Hey guys,
    I was wondering, there are vst instruments, where we can buy commercial libraries, and they are kind of linked to the user and his credentials.

    An example, when we buy a synthmaster soundbank from kv33audio, that could be made by a top audio designer Agusrugur Mitrufgloglu, the web script checkes our name/email/etc and links that soundbank to our name.
    If save each preset from the back, and give it to another user, when he is going to import/use the file, the 'synth' will know that patch comes from user#54556, ME...

    The same as, let's say, avenger. When you buy a commercial soundbank ( looks like 90% of the avenger concept was making an economy based on those soundbank purchases..just like the microtransactions in videogames), you will have like a serial number, a license, to allow you to import the soundbank and use it. Of course, you ain't be able to save that commercial soundbank, as separate presets, one by one, and then give them to a friend.

    NOW,
    This is where i find myself scratching my head.
    In Cubase (and probably other daws), when we open a vst plugin or instrument, we can easily save the current preset, patch, etc, as a .fxp file to a place on the hard drive. We can even save the entire bank, as a .fxb file.
    These files were created a very long time ago, and became a standard, that would allow different daws from different systems to use the same files with the same settings.

    In cubase, there even are 2 possible keys to assign windows shortcuts, for 'load next preset' or 'load previous preset'. With that, you might be able to use your midi keyboard, normally, and use the last 2 keys on the far left to load the previous or next preset. Instead of playing, stop playing, grab the mouse, try to aim the 2 microscopic pixels of the 'next preset' button, on your 1440p/1920p monitor, start playing, stop, try to load another preset....instead of doing all that, we can simoly press C2 or D2 (or c1.. or c0), to load the previous or next preset !

    So, back to cubase.
    WHAT IF, you load a preset from that purchased avenger expansion library, even tweak a few things, and then EXPORT/SAVE AS .fxp file ? And you repeat the same operation with the remaining 1xx files.

    Now, you go to a friends computer, who got cubase and avenger correctly installed.
    He creates a new track, avenger, and now, he clicks on the small cubase button, to import/load a .fxp file, locates it, and loades it. Bam.

    What is it going to happen ? Will avenger be able to perfectly load a sound that originally comes from an encrypted/serial number commercial soundbank...?
    Because when we load a patch from that encrypted commercial avenger library, and we just move a couple of knobs 1%, when we try to save that file as a .fxp, there must be no way to avenger or cubase to say 'heyy, little mofo, we just detected the file you are trying to save as .fxp belongs to a 69 dollars avenger expansion..so cubase won't let you do it'....

    what do you think about that ?
     
  2.  
  3. oldskoolproductions

    oldskoolproductions Producer

    Joined:
    Sep 8, 2013
    Messages:
    146
    Likes Received:
    76
    Very Interesting.

    I used to spend a lot of time years ago saving VST3 patches to .fxp in Cubase.

    the .fxp file points to the actual preset in the preset directory of of your vst.

    So if you save a preset from lets say... Massive as a .fxp file.. and the then delete the original Massive .nsmv file. Then you will not be able to load the preset.

    But.... If you and your friend had identical sound packs and expansions... Then you sound be able to make tweaks to those patch and they should show up.

    If your too computers were identically cloned and the presets were in the same directories...

    I could be wrong , but I think i'm pretty sure on this one.

    Cheers,
     
  4. Olymoon

    Olymoon MODERATOR Staff Member

    Joined:
    Jan 31, 2012
    Messages:
    5,813
    Likes Received:
    4,459
    Best way to know would be to try this with a member here who fits the requirements for the experiment.
    Have Cubase and Avenger.
    Send him a fxp, and see what happens.

    Side note: this thread does not belong to soundgear section which is hardware oriented.
    I'm moving it to "working with sound" as this trick could work with any DAW that uses fxp, fxb, formats, and it will have more visibility.
     
  5. wouala woualouf

    wouala woualouf Platinum Record

    Joined:
    Jul 28, 2015
    Messages:
    297
    Likes Received:
    240
    Thanks for moving the thread, i never know where exactly i should be creating it.
     
  6. wouala woualouf

    wouala woualouf Platinum Record

    Joined:
    Jul 28, 2015
    Messages:
    297
    Likes Received:
    240



    Are you sure the original files must be present ?

    just look at sylenth1: let's say you buy a soundbank with 128 patches. What you get is 128 .fxp files, for the separate presets, and 1 .fxb , for the entire bank.

    You can send the .fxb file number 77, to 10 different Cubase users who have sylenth1 installed as well, when they instanciate sylenth1, it has an empty preset, i think, and then, instead of browsing the files or banks directly from the plugin GUI, if you go to the cubase window, click on the menu 'load .fxp file', now, cubase shoukd read ALL the values inside the .fxp file.... and should send them to the plug-in. .. just like if we were sending 100 or 150 midi messages, or turning 100 knobs or buttons, on a midi controller..

    because the fxp file contains all the components that can be used, sliders, knobs, buttons, switches, etc, along ALL the values for each one of the components, it simply send the values to the plug-in, and the plug-in set the values accordingly.

    Now, imagine you are in avenger, and you use the preset number 7, that came with a pop library, that you bought, installed, entered the s/n, and unlocked it. Let's assume the file 7 doesn't use any external additional sample file.

    now, if we save avenger as a .fxp file, normally, we are taking a snapshot of all the settings and values that the file 7 as.
    by exporting it, the function that creates the .fxp has no idea that file came from an encrypted library. For the function, it's just 00-127 values, on/off states, filter type 3 out of 10, etc etc.

    Now, we send that file to a different guy who has avenger. He loads avenger, it loads a default file.
    now, he goes to the cubase window menu, load .fxp file, and bam, cubase sends to avenger a few hundreds of values, and the plugin receives those values, and move all the knobs, switches, sliders, etc etc, according to the values.

    Now, avenger should be making the same sound as the one where the library got imported to, and decrypted /unlocked.

    this is my crazy theory... probably it doesn't work, because theexpansion was encrypted, had to be imported. ..BUT... it COULD WORK...:)
     
Loading...
Loading...