DSP Robotics Support

Hi gang,

Not sure why I didn't just post this here sooner - I'm from the OSM days (and still use SM as I have too many half done projects that rely on other OSM's to learn from and... blah - anyway) - I'm wrapping up a new multi-sampler and have just spent the last week banging my head trying to figure out how to add the 'save' function for chosen folders/samples.

So people can simply ::
open their daw,
> open the vst,
> choose a folder of samples, make a song...
> Save/close and reopen their project file in their DAW - and the users samples are now there (where currently you have to reselect samples for every instance of it).

Think I've pretty much read the entire forum front to back now for a ton of keyword searches and tried a good 20+ OSM's to see if anyone has done this yet above and beyond trying to fudge it myself and alter others save commands for other stuff... (I realize there may be differences when loading many instances of the vst and choosing different folder locations for each etc so I'm trying file name saves, folder name saves, and frankly a bunch of stuff outside of my understanding..)

The base multi-sampler I use is the bottom 'multi' one on this page :: http://www.synthmaker.co.uk/dokuwiki/do ... per_player

Link to OSM:: http://www.synthmaker.co.uk/dokuwiki/li ... r_v1.1.osm

I've found instances of this where it will save the file but it's not a multi-sample version and has been tweaked beyond my understanding as well

I'd be willing to pay someone to create a save function for me on the above OSM in the wiki so I can stop trying to figure out one function and keep motoring on the project or if it's literally a 5minute fix and you can get an OSM over to me I'm willing to come over and cook you breakfast tomorrow

Or if someone has already done this or has an existing OSM they can point me to it would be greatly appreciated - I'd imagine I'm not the first that has noticed this in their DAW and it's limiting both workflow and creativity on re-opened projects having to route everything each time (and I know if I release this again people will complain about it again even though it's free lol).

Many thanks!!

EDIT: I should add that I've been trying both with samples included in the .dll and with cleared samples as well as source/file strings. Ideally I'd like to release the vst with some samples embedded in it (check) and still give the user the ability to change the folder it defaults to should they save a new one (with either a button for 'back to default sounds' or simply list the samples from the new folder after/before/with the built in ones) - on each instance of it (so they load the vst four times - and have different folders selected for each). Hope I explained that right.

There is a "preset string" primitive which let you save up to 255char string. You may try to add that after the path selector, so it will save/load with your plugin and trigger reloading after schematic load. You will need to have a preset manager in the schematic to work.

Hi KG, thank you for your response.

Are you saying that this is for reopening in a VST or just in SM - or both?

I've located and tried a few combinations with the preset string - no luck

I've made a quick OSM file with a preset manager and all three variations of modules I've tried (shown on the bottom of the jpg attached too) various combinations with - if anyone would be kind enough to tie this together it would be greatly appreciated and I'll show a token of my appreciation to your paypal and hopefully others will benefit from this.

Fingers crossed and thank you in advance!

Well, with a few modifications it's working in here. I used the string preset primitive to both save the path and trigger the sample loading. Formerly the sample loading was triggered by the dialog primitive - I have changed that so the dialog OK "sample and holds" the path that it outputs. That goes to the path/name separator and the path now goes to string preset. Output of string preset then puts the path to the part that loads the samples and also triggers it.

Try it on your machine if it works and let me know.

Going to try it now - if it works as intended I can't believe how fast you did it and feel like I just wasted a week - rather bipolar feeling of happiness meets defeat.

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Success.

KG THANK YOU SOOOO MUCH! Ummmmm :: Are you single?! Nobody has made me this happy this fast in a long time!

haha.

Do you have a paypal account you can PM me so that I can show you my gratitude?!

I just loaded up two instances of it in cubase with different folders for each instance and sure enough once re-opened the samples are there and correct for each instance.

This means a lot to me - I can continue and finish the darn thing now (3months!) so thank you again it was a few minutes of your time but is priceless to me and mine.

NC.

ncmedia wrote:!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Success.

KG THANK YOU SOOOO MUCH! Ummmmm :: Are you single?! Nobody has made me this happy this fast in a long time!

haha.

Do you have a paypal account you can PM me so that I can show you my gratitude?!

I just loaded up two instances of it in cubase with different folders for each instance and sure enough once re-opened the samples are there and correct for each instance.

This means a lot to me - I can continue and finish the darn thing now (3months!) so thank you again it was a few minutes of your time but is priceless to me and mine.

NC.

No biggie being glad to help. No need to show gratitude, your hapiness is the satisfaction on it's own

You're a class act Mr.KG - thank you again and again

While I have you here and the pro level you seem to be at - may I ask you some randoms?

1. Preset manager has always been kinda quirky. This time I'm having trouble making cubase simply automate program changes. It changes some of the knob/slider positions (only after I edit them myself on first pass of automation) but won't change the preset name/number settings. Is this a host specific issue? A SM/FS issue? Something I'm doing wrong with the way I'm setting it up? I've even tried giving the preset manager a preset setup of its own lol along with the buttons inside it that toggle forward/backward to no avail just wonky results and some random knobs recognizing the change.

2. Automation itself - in this schematic - there are presets for the three toggles (loop/follow/rev) yet my automation won't remember them but remembers everything else (sans preset changes). When/how/why do some presets work so seemlessly and when/why do some act so random? i.e. in an older version of cubase, each time I rename a few presets in SM to see if they'll be recognized in cubases preset list it generates - randomly they start hiding/showing but won't ever show 'all' of them. I make sure to give each unique names and try to stick to standard naming conventions. Then I open the VST in a newer version of cubase and ALL are listed plus a few I didn't notice lol and all work (except the preset manager and above three toggles those are a bieatch).

An unforeseen side-effect - still exploring ::

Now when I change program presets, it doesn't simply allow me to select a different sound from the folder I'm in by default - it forces me to reselect a folder (if I try to select anything from the dropdown it won't show the wave file or actually select anything - which can be neat as I can now select different folders of samples to have on different program presets. So for now I've made 4 presets, each with its own folder (instead of having to load the vst four times for certain simpler applications to the sounds).

This brings up a few scenario's ::

If I select many folders - it populates the list and puts the newest sounds first vs jumbling them together - cool. However now I must remember which set I imported for which program incase I want to span something from within that presets folder. Example - I'm on preset 2 - I use a different folder than preset 1 - when I go to the dropdown it has all the samples from all folders, I must choose only sounds from folder set #2 otherwise it blanks it out.

When I change presets, it now takes a bit of time to load the location for each preset vs knowing it's in that folder already.

I thought this would be amazing re changing presets with automation but that goes back to my previous post, now when I automate a preset program change it just crashes my daw (I assume it just can't keep up with the folder changes in real time).

So I might release two versions, one with preloaded samples and no save function so they can easily use the presets on the fly with no lag when changing instruments quickly on multiple instances - and one with the current settings so people can import their own with a caution/disclaimer re the above (or further investigation might bring up new solutions/ways to maximize all the options and side-effects here).

Cheers though this is perfect already just exploring what happens when I use this as an end user will assume they can...

Thoughts?

EDIT: Interesting, I managed to get programs to change on automation a few times before crashing - it changes the kit/folder and plays those sounds in the midi triggers in my daw, however visually it doesn't show the change in preset manager.

Also interesting is that I can have different automation recorded on each preset. So I'm looping a simple 4 bar beat I made with the vst, and as I change presets and automate things they get recorded seperately despite being on the same track looping - hard to explain but randomly cools.

And finally - if I select a folder with 10 sounds, and some are short some are long (say 1sec to 10sec), if I then select a short sample as the main sample and I don't span - all the samples will only play for the length of the chosen main sample, cutting many off. Might have to simply inform users to always select the longest sound as their main sample if they are not spanning but using the folder as a kit - which I guess they can do by sorting files by size before importing so they know which is longest... so many little tweaks now lol.

EDIT 2: I've now tried to strip the preset manager, tried different preset managers (from other osm's, from toolbox, etc), and tried some variations on how they are setup by default. Each one gives me different reactions in my DAW. The joys of "I have no idea why this is working" and "I have no idea why this is NOT working" alternating in my day is a lolercoaster . Preset manager is all kinds of random.

Yeah, the preset manager is a never-ending mystery. Its functionality and communication with DAW is fallows:

The preset manager lists its parameters (parameter primitives in the schematic). It creates parameter inputs for your DAW to automate them and also parameter outputs, which notify your daw about the current value of that parameter.

When you turn a knob/move slider the preset parameter prim receives this value, sends it to preset manager and he sends this new value to your DAW. When you save your project in your DAW the DAW also saves these last values.

When you automate a parameter in your DAW, the DAW transmits the new values to preset manager and the preset manager transmits them to respective preset parameter prims. The preset parameter prim sends the new value via green along with the new value.

When you load previously saved project, your DAW first loads the plugin. Once the plugin is loaded it sends in the values of all parameters (like if it was an automation) to preset manager. The preset manager then transmits those values to respective preset parameter prims, which send the value as green data.

Preset manager preset-saving ability is completely separate form your DAW. When you load a preset in a PM, he loads the values, sends them to respective preset parameter prims and also sends the new values to your DAW (sort of like if you moved all knobs at once).

When you load a preset in your DAW, it transmits the values to the preset manager as if all values changed via automation at the same time. The preset manager then sends those values to preset parameter prims.

Now I'm not sure what may happen when you try to automate the preset loading of your preset manager. Because in order to automate it, you need to list the preset parameter that automates it. However, this parameter will also load with the new preset itself. An infinite trigger loop should happen, where a parameter automates the PM loading new preset, triggering itself and loading another. FS somehow prevents this loop, but it is unclear what values get loaded for preset parameters, especially the one that automates the loading.

This would require further testing. However you may have multiple preset managers in your schematic. So theoretically you may use one with a single parameter to automate the preset loading of the other one which holds all other preset parameters.

It is really question beyond my expertize. I never really played with this, so I unfortunately can't provide examples and guidance in this matter.