Preset Managing system V0.9.5 now with unlimited folders!!
Archive · 200877 old posts
From the original SynthMaker forum (2004–2014), with its members’ names and dates.
exonerate ·
I've developed a new way of dealing with presets in SM, that doesn't use the preset manger (well it's still there it has to be but doesn't contain any presets 😉 )
NAS came up with the original idea for this, basically the presets are stored in folders on your hardrive, and they show up in a drop down menu, each submenu is a folder, which are basically your banks, you can have up to 24 banks more can be added, the number of presets in each bank is dynamic and unlimited I wanted the number of banks to be unlimited also but I had a hard time working that one out, it didn't seem possible.
Anyway to get it working you need to create a folder next to your plugin called "Presets", then you can create some folders within the 'Presets' folder these will be your banks, (you can create folder while your in the plugin by clicking 'management' , then you will need to click scan for the new folders to show).
Then just save your presets to the folders, the presets will automatically show in the drop menu after saving, you only need to scan after doing something in the Preset folder(adding more folders ect..)
**Edit** the latest version is now on the wiki Here....]
Cheers 😉
Exo
sunsynth ·
Great exo,
will check it soon 🙂
Walter
Acrobat ·
that's how Alieno settings work, but you've gone much further, I guess...great! 😀
aliasant ·
Nice work.
This would solve my problems trying to create banks.
Gonna test soon.
peterv ·
Exo,
Great work that possible could become very handy for me!
Thanks!
infuzion ·
I was thinking about the text-presets approach to work around Preference-lag & a easy way to add cut & paste presets. Glad you beat me to it exo 😇 Does this version save entire banks or single patches?
Being concerned about live usage in Live, I do have these hesitations:
* HD space it would take (many use laptops, partitions, or using flash-drives), since a 1k file can take 16k, & I'm guessing a single synth using this system.
* CPU lag/audio hiccup caused by accessing the HD (not a big deal when composing, but in live usage a synth may be reused several times with different patches)
Could someone help me with my laziness & upload some patches please? 🙂
Acrobat ·
infuzion wrote: * CPU lag/audio hiccup caused by accessing the HD (not a big deal when composing, but in live usage a synth may be reused several times with different patches)
I wouldn't worry at all about space, but HD access is a point to take in serious consideration...
Nu Audio Science ·
If you seriously think loading a .txt file is going to tax your HD you need a new HD simple as that
I tested this on a very old laptop and never had a single problem
Why and how could you possibly save an entire bank ?
That whole sentence doesn't make any sense at all
Each sub folder can have unlimited presets in it so each bank can have unlimited presets
No bank is ever loaded into the plugin just a single preset
I know it's different to the way you guys are used to working but once you get used to it this is the way to work believe me
Hope that helps anyway
NAS
Nu Audio Science ·
If you seriously think loading a .txt file is going to tax your HD you need a new HD simple as that
I tested this on a very old laptop and never had a single problem
Why and how could you possibly save an entire bank ?
That whole sentence doesn't make any sense at all
Each sub folder can have unlimited presets in it so each bank can have unlimited presets
No bank is ever loaded into the plugin just a single preset
I know it's different to the way you guys are used to working but once you get used to it this is the way to work believe me
Hope that helps anyway
NAS
infuzion ·
Nu Audio Science wrote: If you seriously think loading a .txt file is going to tax your HD you need a new HD simple as that
I tested this on a very old laptop and never had a single problem
Why and how could you possibly save an entire bank ?
1) Obviously you never used Ableton Live on a laptop with a set of 20 30-100Mb WAVs (full remixes), + reading in more sound samples, while recording the session, & still having to avoid audio hiccups. As I change out songs, I also change out presets for the drumkit & effects. Having to read even more files (which will make the HD read head hop around more) will risk more audio dropouts, which I don't need in front of 1000+ people.
2) Obviously you never saw the bool input of Preset Text File: "False = All programs". But, I'm not sure if exo actually sends a full bank or just 1 patch at a time.
Nu Audio Science ·
There is no full bank infuzion that is what i tried to explain
It is a per preset management system, It doesn't have a bank full of presets in memory, It reads them dynamically
On the HD reading issue well you didn't explain you just said you were worried about reading txt files which didn't make sense
Sorry for the crossed lines
NAS
exonerate ·
Yeah there is only ever one preset loaded at a time, I store all the file paths in a string array, then index this array to load the correct preset.
So on every preset change you are reading from the hard drive, which does make the audio drop out for a split second, but the SM preset manager does this anyway.
I have a very big synth with lots of params, I tested this preset manager with it, and changing preset makes the audio drop out for about half a second max, the presets in this synth are 250kbs thats per preset not a bank.
The advantage of this system is in not having to load banks, you only ever load a single preset, and you can organize them from the windows folder system, so you have copy and paste ect...
Cheers 😉
Exo
infuzion ·
exonerate wrote: So on every preset change you are reading from the hard drive, which does make the audio drop out for a split second, but the SM preset manager does this anyway.
For my purposes (& many who use Live) this cannot happen, since a DJ mix is essentially a 30-120 minute song, & no drop outs are allowed. To fix the preset-lag bug, I was thinking of making smaller banks, so there would be less chance of lag/maxing CPU but no accessing the HD.
--
I do think we're pushing SM past their originally intended limits, because I don't think arrays were in the original plan, let alone so many huge arrays. But if can't make lag & drop-out free synths, I'll have to give up SM, since I think there is a saturation of smaller synths, most of which are free or cheap shareware.
Nu Audio Science ·
No disrespect but Live Isn't DJin
Thats no disrespect to you or anyone else who uses Live in that way
I've been a DJ for twenty years or so and i am a turntablist by nature
Using Live or any other platform in that way has nothing to do with the term DJ
That being said i can see where your coming from with what you want and i can see where the lag is a killer in that situation 😉
NAS
Acrobat ·
Nu Audio Science wrote: i am a turntablist by nature
NAS
A race near to extinction that must be protected by WWF.. 😉
Nu Audio Science ·
Were not goin extinct
Were the last salvation of mankind 😉
NAS
Acrobat ·
Nu Audio Science wrote: Were not goin extinct
Were the last salvation of mankind 😉
NAS
Yeah I imagine the last party where hoards of CDJ-ists are scattered to the ground, beaten by the alien-hologram-cubes-spinners and and one of you raisin over'em all and proudly save our planet from invasion!
dskm ·
great works 🙂
we can use in our projects?
exonerate ·
dskm wrote: great works 🙂
we can use in our projects?
Yes of course 🙂
Please make sure you give it a good test first before releasing anything with it in, If you find any issues please report them here.
cheers 😉
Exo
aliasant ·
exo.
I just have to say it.
GREAT WORK!.
Love this.
exonerate ·
Just updated to version 0.7.
Made it so its a bit easier to mod the look ect....
Cheers 😉
Exo
aliasant ·
If its ok with you, Exo, this will go into my Inerthia plugin.
infuzion ·
Thanks exo!
Has anyone tried to make copy/paste from this yet please?
aliasant ·
Im trying hard to understand how this goodie works but its hard.
What I want to do is add more subfolders in the main folders.
Folders like this.
Bank 1:
Vocals
Drums
Guitars
Bank 2:
Robert DeNiros Violins
Robert DeNiros Harp
And so on.
This would be a great system. You could name the different folders after the different tracks your working on or artists your recording... Very easy to manage.
The copy and paste would also be nice.
aliasant ·
I have found a small bug in this but Im not sure if the problem is in this preset manager or in SM.
Problem is that I cant use a to deep location for the Preset Folder
Im trying this:
C:\Program Files\VstPlugins\theOuthouse\Inerthia-Presets\
That doesnt work. Its all ok in SM but as a VST it cant scan, manage or find anything.
If I change the location to this:
C:\Program Files\VstPlugins\Inerthia-Presets\
It works. I have no idea what causes this but its a little bit annoying.
It prevents me from placing the Presets were I want them. 🙁
aliasant ·
Found another bug.
In my Presets folder I have 9 Subfolders, named Bank 1, Bank 2 and so on.
In the first Bank I have 15 Presets.
In the last folder I have 4 Presets.
The others are empty.
When I use the arrows to skip thru the presets I only get to bank 6. Then it stops. That is file number 18.
The counter stops at 18 and the selector at 28.
If I select the first preset in the last folder it still says 18 and 28.
So when i click the back arrow i bounce back to folder 6.
Cant figure out why thoug. To dumb for that 🙂
Edit: I see now that you have already understood the problem here.
Need to count the number of files in each folder?
Acrobat ·
aliasant wrote: Found another bug.
In my Presets folder I have 9 Subfolders, named Bank 1, Bank 2 and so on.
In the first Bank I have 15 Presets.
In the last folder I have 4 Presets.
The others are empty.
When I use the arrows to skip thru the presets I only get to bank 6. Then it stops. That is file number 18.
The counter stops at 18 and the selector at 28.
If I select the first preset in the last folder it still says 18 and 28.
So when i click the back arrow i bounce back to folder 6.
Cant figure out why thoug. To dumb for that 🙂
Edit: I see now that you have already understood the problem here.
Need to count the number of files in each folder?
Aliasant, scroll a bit lower in the main module, Exo placed some unlinked primitives with relative suggestions, maybe those have to be used for your issue...?
exonerate ·
Thanks for the suggestions and bug reports aliasant 🙂
And so on.
This would be a great system. You could name the different folders after the different tracks your working on or artists your recording... Very easy to manage.
This is a great idea, but out of the scope of this implementation and I think currently not possible in SM, well it can be done but it would be very inflexible and complex, currently you can have 24 folders, now if you could have folders within these folders you'd need to set a limit for the folders you can have so if in each folder you could have another 24 folders then you would need 576 of the 'search' modules, and thats just for one level down.
SM does need a file browser though but the complexity to make such a thing makes be think that something like this really needs to be added as specialised primitves by the devs IMHO.
======================
The deep location problem I'll have a look at, should be something I can fix.
When I use the arrows to skip thru the presets I only get to bank 6. Then it stops. That is file number 18.
The counter stops at 18 and the selector at 28.
If I select the first preset in the last folder it still says 18 and 28.
So when i click the back arrow i bounce back to folder 6
Yes I know whats happening here, Its the empty folders that are the problem, if you put at least one preset in each folder this shouldn't happen.
The problem is that the banks show in the drop down even when they are empty this means they become a selectable index, Basically I think the only way to deal with this is if the folder is empty I'll have to stop it showing in the drop down, which is not ideal, but all the banks will still show in the 'save In / As' drop down, so when you save you can select the empty bank, save to that and then it will show in the preset drop down.
cheers 😉
Exo
exonerate ·
Acrobat wrote:
aliasant wrote: Found another bug.
In my Presets folder I have 9 Subfolders, named Bank 1, Bank 2 and so on.
In the first Bank I have 15 Presets.
In the last folder I have 4 Presets.
The others are empty.
When I use the arrows to skip thru the presets I only get to bank 6. Then it stops. That is file number 18.
The counter stops at 18 and the selector at 28.
If I select the first preset in the last folder it still says 18 and 28.
So when i click the back arrow i bounce back to folder 6.
Cant figure out why thoug. To dumb for that 🙂
Edit: I see now that you have already understood the problem here.
Need to count the number of files in each folder?
Aliasant, scroll a bit lower in the main module, Exo placed some unlinked primitives with relative suggestions, maybe those have to be used for your issue...?
Oh no take no notice of them, They were for something else but i found a better way, I forgot they were there. 😊
aliasant ·
Great Exo.
Pitty we cant have the folder in folder thing =( Guess we just have to live with that for a little while... until Jorge has time to write a primitive.
Found another problem now concerning my radiobuttons.
They dont work with the new presetmanager.
I will mail you a scheme so you can have a look if you have time.
exonerate ·
Updated to V0.7.1.
Fixed the issue with empty folders in the drop down, now what happens is only folders containing files show in the drop down.
All folders show in the save selector so you can save to an empty folder and then that folder will automatically show in the drop down. 🙂
@aliasant I checked the radio button osm you sent me and it seems to work fine here, only did a quick test though but I didn't notice an issue.
Also with the location issue, it works here even on really deep locations, make sure the VST is next to the Inertia-Presets folder, I'm guessing you must of forgot to move the VST when changing the location of the preset folder?
Cheers 😉
Exo
aliasant ·
Doublepost!
aliasant ·
exonerate wrote: Updated to V0.7.1.
Fixed the issue with empty folders in the drop down, now what happens is only folders containing files show in the drop down.
All folders show in the save selector so you can save to an empty folder and then that folder will automatically show in the drop down. 🙂
@aliasant I checked the radio button osm you sent me and it seems to work fine here, only did a quick test though but I didn't notice an issue.
Also with the location issue, it works here even on really deep locations, make sure the VST is next to the Inertia-Presets folder, I'm guessing you must of forgot to move the VST when changing the location of the preset folder?
Cheers 😉
Exo
sheisse.
The radiobuttons doesnt remember its settings here and often both button 1 and 2 are selected at the same time and only way out of that is to click button 3. Nothing happens when I click at 1 or 2.
Very strange. I think maybe I have a slightly modified SM that Malc gave me. I should try to reinstall the 1.09 release again.
About the depth problem. I have the presets folder next to the plug. Double and tripple checked that. Another strange one. I will update this IF reinstalling SM helps.
Update 1: Duh. The login at SM website is down so I cant get the installer for SM. Is there another place to get it from?
sunsynth ·
Hi aliasant,
sheisse.
Don't give up so fast 😉
Give me a link 2 your radiobuttons plus Preset-manager.OSM and i will try 2 help!
SUNsynth
aliasant ·
sunsynth wrote: Hi aliasant,
sheisse.
Don't give up so fast 😉
Give me a link 2 your radiobuttons plus Preset-manager.OSM and i will try 2 help!
If you see the 1st path* the preset name is 'test3' aso...
...if you press a preset up/down-button
SUNsynth
Hmm, this thingy needs a preset-change detector and autosave
(4 a standalone version)
The radiobuttons still aint working. Are they working correct for you sunsynth?
Something I think would be nice is to have a small button to save the current preset with a single click. Not sure I would like autosave.
Nice to be able to play around with a preset and knowing that you have the original preset left untouched until you press that save button.
Update: There is something wrong with the naming of the preset folder.
Testing 0.71 now and when I hit properties, click in the "Name of preset folder" and start typing the box move up and left. When I click enter to finish the typing only the first letter is left in that edit box.
Odd. Is this just happening to me? If so I must get a copy of Synthmaker Installer. It has to be the quick fix that Malc gave me for another thing.
Acrobat ·
aliasant wrote: Something I think would be nice is to have a small button to save the current preset with a single click. Not sure I would like autosave.
Nice to be able to play around with a preset and knowing that you have the original preset left untouched until you press that save button.
I like the idea! Works like old hardware synths that had an edit buffer, typically with a "*" appended after the name of the patch.. 😀
sunsynth ·
Hi,
@aliasant:
The radiobuttons still aint working. Are they working correct for you sunsynth?
The Buttons are working (because it's my idea 2 add the flipper:) but the PM has a bug...
The save button exists in my own PM build from scratch...
Exo can add it easily or I do it if he/you want it...!
@exo: Please have a look (or 2) @ the droplist... 😉
SUNsynth
P.S. The autosave is only good 4 my standalone effect-chainer...
If the user change the original preset so it's good 4 him and switch back and forth and his changes are gone... he will be unhappy with this scenario
aliasant ·
sunsynth wrote: Hi,
@aliasant:
The radiobuttons still aint working. Are they working correct for you sunsynth?
The Buttons are working (because it's my idea 2 add the flipper:) but the PM has a bug...
The save button exists in my own PM build from scratch...
Exo can add it easily or I do it if he/you want it...!
@exo: Please have a look (or 2) @ the droplist... 😉
SUNsynth
P.S. The autosave is only good 4 my standalone effect-chainer...
If the user change the original preset so it's good 4 him and switch back and forth and his changes are gone... he will be unhappy with this scenario
Ok. You say the radio buttons in the osm you downloaded works?
Shit. They dont for me. Not at all.
Edit: Scratch that. Yes The buttons are working but the PM isnt. I tried the buttons with the standard preset manager and works perfectly.
I Hope Malc can mail me the SM installer so I can get the real version of synthmaker. Something must be wrong here.
Edit this one too! I got the real SM from Malc and of course that didnt do any difference since there was no real problem as I said above. Just some minor confusion from my part. Sorry bout that.
About acrobats "edit Buffer". Yes That is as it should work.
With a compare button as well.
EXO ! Listen up !!!! Attention...........hut!
We need a save button + a compare button Is that possible?
aliasant ·
Im loosing hair now.
Have been trying to make this work but if I fix one thing I manage to break something else.
I started with this. When I click save as/ in I wanted it to by default display the name of the current preset. That way it would be easy to just put A 2 after or maybe overwrite the old one by just leaving the name as it is and press enter. Seemd simple enough but something got screwed up.
I also placed a quicksave button and a recall button. That actually works as its supposed. quicksave just saves the current changes to the preset, overwriting the old one. Recall reloads the current preset with its original settings.
Havnt dared to try and make a compare thing yet. If I cant fix the small problems I have now how could I ever fix that compare thing......
I hope someone else has better luck or more likely a bigger brain...
exonerate ·
Ok, just updated to version 0.7.5.
*fixed the bug with the naming folder in the properties.
*fixed some issues with the load selector.
*The current preset name now shows when you click save in / as.
*Added save and recall buttons.
--------------------------
@aliasant the radio buttons are working here correctly after saving a preset, when first loading your osm two of them are lit and you have to click the bottom button, but it doesn't do that again after saving a preset.
The compare function I'll have to look at but I'm not sure if it's possible we have no access to memory for this kind of stuff, you cannot even access the preset data from within SM you have to save it to text file first.
So for that to work i think you'd have to save the preset to text file with every parameter change, maybe every mouse up, but that method could not be built into this preset manager you would have to set your controls up to trigger a preset save on every mouse up.
Of course there maybe be another way, but ideally we'd have access to memory, store the current 'P' data in memory and then just switch between a preset and the data in memory.
cheers 😉
Exo
exonerate ·
update to version 0.7.7 🙂
Just fixed a few minor things really.
cheers 😉
Exo
aliasant ·
exonerate wrote: Ok, just updated to version 0.7.5.
*fixed the bug with the naming folder in the properties.
*fixed some issues with the load selector.
*The current preset name now shows when you click save in / as.
*Added save and recall buttons.
--------------------------
@aliasant the radio buttons are working here correctly after saving a preset, when first loading your osm two of them are lit and you have to click the bottom button, but it doesn't do that again after saving a preset.
The compare function I'll have to look at but I'm not sure if it's possible we have no access to memory for this kind of stuff, you cannot even access the preset data from within SM you have to save it to text file first.
So for that to work i think you'd have to save the preset to text file with every parameter change, maybe every mouse up, but that method could not be built into this preset manager you would have to set your controls up to trigger a preset save on every mouse up.
Of course there maybe be another way, but ideally we'd have access to memory, store the current 'P' data in memory and then just switch between a preset and the data in memory.
cheers 😉
Exo
You are the MAN!
About my radiobuttons. If I understand you right all I need to do is open and save all my presets once for them to work properly?
About the compare thing.
I figured that much. Maybe we should ask for a primitive that lets us see the float data of the current preset? That would make it easy to do compare and also copy and paste. And probably many other things as well. Right? It would have to be some small memory thing that we can update whenever anything in the data changes...
Great about all the other updates. Have to check this one out.
aliasant ·
exonerate wrote: Ok, just updated to version 0.7.5.
*fixed the bug with the naming folder in the properties.
*fixed some issues with the load selector.
*The current preset name now shows when you click save in / as.
*Added save and recall buttons.
--------------------------
@aliasant the radio buttons are working here correctly after saving a preset, when first loading your osm two of them are lit and you have to click the bottom button, but it doesn't do that again after saving a preset.
The compare function I'll have to look at but I'm not sure if it's possible we have no access to memory for this kind of stuff, you cannot even access the preset data from within SM you have to save it to text file first.
So for that to work i think you'd have to save the preset to text file with every parameter change, maybe every mouse up, but that method could not be built into this preset manager you would have to set your controls up to trigger a preset save on every mouse up.
Of course there maybe be another way, but ideally we'd have access to memory, store the current 'P' data in memory and then just switch between a preset and the data in memory.
cheers 😉
Exo
You are the MAN!
About my radiobuttons. If I understand you right all I need to do is open and save all my presets once for them to work properly?
About the compare thing.
I figured that much. Maybe we should ask for a primitive that lets us see the float data of the current preset? That would make it easy to do compare and also copy and paste. And probably many other things as well. Right? It would have to be some small memory thing that we can update whenever anything in the data changes...
Great about all the other updates. Have to check this one out.
aliasant ·
Everything seems to work great now. Except the radiobuttons....
I made a .osm with 2 radiobuttons and the latest build of the PM.
I also wrote some instructions on how to recreate the bug.
Please test it.
exonerate ·
Update to version 0.8 🙂
Added a Random preset button.
Added a compare switch. 🙂
The compare was actually very easy, let me know if it works like you think it should!
For the random preset and the compare function I'm using a txt file called 'buffer.txt' that I read and save to for both the random and compare, the text file gets put next to the VST.
------------------------
@aliasant I tested your file again and I could recreate the problems, it seems though that the issue was that preset names are the same in each 'set' of radiobuttons, in the second set I put a 2 after each preset name and then saved some presets, this seems to fix it.
But I don't get then how they worked with the standard preset manager 😕
cheers 😉
Exo
Nu Audio Science ·
Notice
To compare presets load a preset then flick the switch and load another preset
To compare a preset to a modified preset load the preset and flick the switch, Now flick the switch again and mess with the preset
When you click the switch now it will be the original preset and click it again to go to the modified preset 😉
NAS
chironex ·
PM me when this thing is out of beta, it looks awesome 😮
aliasant ·
chironex wrote: PM me when this thing is out of beta, it looks awesome 😮
right
aliasant ·
Nu Audio Science wrote: Notice
To compare presets load a preset then flick the switch and load another preset
To compare a preset to a modified preset load the preset and flick the switch, Now flick the switch again and mess with the preset
When you click the switch now it will be the original preset and click it again to go to the modified preset 😉
NAS
Not sure I like the compare function. A bit hard to understand.
Gonna try to make it a bit simpler but this green stuff is hard on my head.
I think I solved a bug with the save as/ in button. The highlight was always on. I connected the left mouse down trig to the off as well as the on and that fixed it.
Also. After a save as is made that new preset cant be found. Not until you make a new scan, so I fixed that too. I dont want to upload mine since I have taken out some graphics. But if anyone wants to have a look, just msg me.
About the Random function. Didnt get that to work at all. ( In Inerthia )
Maybe its my knobs or is there something that needs to be done to make this work?.
MichaelBenjamin ·
this preset manager is a very good idea.
but when i tested the unmodified exported demo setup 0.7.7 with some saved presets, the host (energy xt 1.41 and samplitude9) completely freezes up after some preset switching.
you can recreate this maybe:
just save a bunch of presets, then export vst, then load in host, then switch back and fourth through presets, and then randomly but certainly after a minute or two the host locks up. i have no idea why this could happen, maybe you got more knowledge to trace this back.
ill test the 0.8 tomorrow
greetings
michael
electrogear ·
chironex wrote: PM me when this thing is out of beta, it looks awesome 😮
Or you could stop being a cheeky git and come back yourself to check 😉
aliasant ·
I found something that isnt all that great.
I had a song were I used a lot of Inerthias with the new preset manager.
Works almost perfect.
Then today I updated the VSt to a new version and when I load that song all instances of the plugin is set to the default preset. The one I had when bouncing the vst from SM.
Oops.
Maybe the Old Preset Manager has to be involved somehow to prevent that?
Imagine a user getting his latest update of his favorite plugin. Loads it in to his latest project and all instances of that plugin is set to Default.....
I would be pretty pissed 😉
MichaelBenjamin ·
unfortunately, the 0.8 version too, freezes the host after some (~20-40 times) preset switching... i just tested it with the included demo synth. any ideas what could be the problem?
MyCo ·
The freezing doesn't deppend on any host. It also freezes S|M... but it's hard to recreate the problem
MichaelBenjamin ·
ok, i tested again with exonerates preset manager inside sm 1.0.9 and after 500 times switching presets back and fourth and pressing midi notes inbetween like a madman i can only report that it works fine inside SM.
a quick test as exported vsti freezed energy xt again after some 30 secs even without any midi input.
i now searched the forum and it seems the preset switching crashing the host was/is an issue with the preset manager in general, especially with ableton live. in one thread malc said it would be fixed in 1.0.8, but no definite solution was posted in the several 5-10 threads. also the exact cause seems to be unknown.
any more information on this?
the whole preset managing at this point is utterly useless with this kind of host freezing feature... should be a priority for the devs.
besides i really like the textfile implementation of exonerate and it got me back on the idea of implementing presets, but now this again..
maybe i will test it with the stock preset manager of 1.0.9 later but at the moment im fed up with preset switching..
MichaelBenjamin ·
i couldnt let it go:
so i loaded up the textfiles created with exonerates preset manager into the stock manager one by one, exported the vsti, and switched presets again in the host.
results after countless preset switching:
the 1.0.9 stock preset manager does not have this freezing issue.
so what is the difference between the two preset systems that cause the freeze?
exonerate, maybe you used some pre 1.0.8 module? or is it the disk access which somehow screws up the asio and takes the host with it?
maybe a workaround could be to load all the preset files to ram at startup, and if you save presets, they wont appear untill a global refresh on user input.
MyCo ·
It crashed my S|M 3 times til now... and I'm close to the point where I can tell you how to reproduce the problem
MichaelBenjamin ·
hmm strange, inside sm it worked for me without a single crash.
i just tried to replace the dummy manager primitive with the one from the stock presetmanager, no success
infuzion ·
MyCo wrote: It crashed my S|M 3 times til now... and I'm close to the point where I can tell you how to reproduce the problem
Seems I have more crashes if Float Arrays are involved.
aliasant ·
Another bug thing.
If I do a save as/ in the save will be done even if I try to bail out by pressing escape or just clicking outside the button area
Shouldnt the trigger to do the save only be sent if I press Return or Enter?
Edit: I caused this "bug" myself by "fixing" the save as button. At least I think so. not sure.
Ill quote myself:I think I solved a bug with the save as/ in button. The highlight was always on. I connected the left mouse down trig to the off as well as the on and that fixed it.
exonerate ·
aliasant wrote: Another bug thing.
If I do a save as/ in the save will be done even if I try to bail out by pressing escape or just clicking outside the button area
Shouldnt the trigger to do the save only be sent if I press Return or Enter?
Edit: I caused this "bug" myself by "fixing" the save as button. At least I think so. not sure.
Ill quote myself:I think I solved a bug with the save as/ in button. The highlight was always on. I connected the left mouse down trig to the off as well as the on and that fixed it.
No it did that anyway, I think i tried to stop clicking outside from saving but I don't think it was so simple, I'll have a look at that again.
Regarding the host locking up I can recreate this in eXT2. but only when changing preset extremely fast with the arrow buttons. My guess is it probably is to do with accessing the hardrive.
Sounds like one for the SM dev's, I guess I'm using the Preset text primitive in a way it wasn't designed for, maybe it just needs some 'fail safe' code when loading presets very fast.
The random button does the same, that actually saves and then loads straight after.
I'll make a report in the bug forum.
===edit === actually I cannot for the life in me get FL studio to do it, It doesn't do it in SM, So maybe this is an eXT2 bug? wouldn't surprise me 🙂
cheers 😉
Exo
aliasant ·
===edit === actually I cannot for the life in me get FL studio to do it, It doesn't do it in SM, So maybe this is an eXT2 bug? wouldn't surprise me 🙂
cheers 😉
I had the crash while doing fast preset switching in Reaper and yes. It is probably something about accessing the drive/system to fast.
Maybe there could be a built in timer to prevent fast switching ?
UPDATE: Had a report from a guy beta testing Inerthia.
Cubase SX3 freezes up when switching presets to fast.
This is what he wrote:
Changing presets on the fly in Cubase SX3 with a project that is eating a lot of CPU (even on a 4core) and running at 5ms latency is not reliable. It is likely to freeze SX3 and require stopping SX3 via the task manager. This however is all that is necessary and no reboot is needed. One can just restart SX3.
infuzion ·
aliasant wrote: I had the crash while doing fast preset switching in Reaper and yes. It is probably something about accessing the drive/system to fast.
Maybe there could be a built in timer to prevent fast switching ?
It seems everytime I mess with arrays in SM, I am at a higher risk of crashing SM.
exonerate ·
Ok the Freezing up thing is fixed 🙂
Update to version 0.9....
Changes..
Fixed an issue with the drop down selector not showing the correct name of the preset when reloading a project in the host.
The display now shows the preset name after saving in /as.
Removed the random and compare features. (I wasn't happy with either of the implementations, they where both an afterthought, They'll most likely come back, but for now the focus is on getting this thing completely bug free and to a high standard.)
----------------------
This version should be usable now all big bugs should be fixed.
The next step now is to refactor the whole thing to make it easier for people to mod and add there own graphics, also optimizing. These tasks will no doubt bring some bugs back with them, so I'd class 0.9 as a 'stable' release the next stable release will be version 1.
Cheers 😉
Exo
exonerate ·
Ok one thing thats been doing my head in a bit about this preset thing is the 24 folder limit, I don't like limits.......because errmm there limiting. 🙂
So I have a new version with unlimited folders 😀
Was actually very easy to do, I'm not sure why I thought it was hard, I guess I was looking at it from the wrong angle.
Anyway you can get version 0.9.5 here....
http://www.box.net/shared/n1751igoww
I've tidied it up and done some refactoring, theres now a module at the top level with the GUI stuff in so you can easily modify it and add your own ect...
The file size and memory use of the preset manager should have gone down a lot, before there was 24 'folder find' primitives now theres only 2, the unlimited folder thing has made it more lean and mean. 🙂
Of course because of all the changes it possible some bugs have come back or new ones have emerged, I've tested it quite a lot in my host and everything seems fine, but no doubt I've missed some things.
Cheers 😉
Exo
exonerate ·
I fixed a little mistake, the 'scan folder' button wasn't working, I fixed that and just uploaded over the same file.
So just download version 0.9.5 again for the fix.
Cheers 😉
Exo
MichaelBenjamin ·
thumbs up!
this preset manager is very good and it works now without freezing:)
thank you exonerate, you will not be forgotten.
exonerate ·
I've gone and updated this to version one now, 😀 and added it to the wiki......
Here....
Made it look a bit slicker, by tweaking the properties. 🙂
changes...
Added an option to allow the end user of the plugin to select where the preset folder is, which means they can put it where ever they like after downloading. It will ask for the preset folder location once on the first plugin load, the location is saved to a text file next to the plugin. Of course this is an option in the properties panel which can be turned on or off. 🙂
Cheers 😉
Exo
stw ·
Did anyone test that in 1.1.7?
I'm getting all kind of wired misbehaviours in my actual project. And before wasting several hours of bug hunting i'd like to know if others run into problems with that too?
aliasant ·
stw wrote: Did anyone test that in 1.1.7?
I'm getting all kind of wired misbehaviours in my actual project. And before wasting several hours of bug hunting i'd like to know if others run into problems with that too?
I use a custom version of this but I have changed things and probably caused new/fixed old bugs. It works for me though.
One problem might be that we used to have some extra invisible characters in strings that we removed manually in several places and if that isnt necessary anymore I think we are removing characers that shouldnt be removed... blablabla.. More coffe.....
It needs a look thru all modules for sure bu it does work and its very handy to have the same presets for .exes and vsts and what nots. Also nice to manually be able to create folders/banks for presets and all other benefits we get from actually being able to organize our presets..
exonerate ·
stw wrote: Did anyone test that in 1.1.7?
I'm getting all kind of wired misbehaviours in my actual project. And before wasting several hours of bug hunting i'd like to know if others run into problems with that too?
What kind of stuff is happening?
Aliasant wrote: One problem might be that we used to have some extra invisible characters in strings that we removed manually in several places and if that isnt necessary anymore I think we are removing characers that shouldnt be removed.
Yeah i remember that problem pretty sure i fixed that though.
Cheers 😉
Exo
aliasant ·
exonerate wrote:
stw wrote: Did anyone test that in 1.1.7?
I'm getting all kind of wired misbehaviours in my actual project. And before wasting several hours of bug hunting i'd like to know if others run into problems with that too?
What kind of stuff is happening?
Aliasant wrote: One problem might be that we used to have some extra invisible characters in strings that we removed manually in several places and if that isnt necessary anymore I think we are removing characers that shouldnt be removed.
Yeah i remember that problem pretty sure i fixed that though.
Cheers 😉
Exo
Yes. You might have.
I dont think Im using your latest since my own was so nested into my projects and working but there might be other similar problems since the latest updates/bugfixes really did change some things.
I think maybe triggers and strings might have changed?
stw ·
exonerate wrote: What kind of stuff is happening?
After trying some more it seems to work ok. I guess i misunderstood some functions. I think i'll tweak it a bit to fit my needs. But anyway it saves a lot of work! 😉 So some late thanks for that.
Nu Audio Science ·
No longer works in SM 2
stw ·
Nu Audio Science wrote: No longer works in SM 2
works fine with SM 2! What kind of trouble do you have?
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker