Hi!
First draft of presets available on the branch:
Use this link in the package manager:
https://github.com/rorywalsh/CsoundUnity.git#1632e230d95228268226dedec28524384a15f018
or better:
https://github.com/rorywalsh/CsoundUnity.git#feature/presets
Still WIP, not really documented, but I wanted to have some feedback before going on!
Let me know your thoughts!
EDIT: I think there is some issue with combo boxes yet 
EDIT of EDIT: combo boxes should be fixed!
Hi!
Just got a chance to play with it a bit this morning, this is amazing! Combo boxes do look fixed on my end.
One thing that would be a nice addition would be the option to set a custom path to save the scriptable objects to help keep everything organized (as opposed to just saving them in the root of the assets folder.
Another thing that would be nice to have (and I have no idea how reasonable/feasible this is) would be if CsoundUnity could read a .snaps file generated by Cabbage and create CsoundUnityPreset assets based off that. But even without this this implementation is so much help, thank you so much!
There seems to be an issue with building the Unity project when using the version of the package with the preset system - Iâve been getting these two errors when trying to build both for MacOS and Android
Edit: the image turned out too small but the errors say:
Library/PackageCache/com.csound.csoundunity@e484923571/Runtime/CsoundUnity.cs(1579,30): error CS0103: The name âUnityWebRequestâ does not exist in the current context
Library/PackageCache/com.csound.csoundunity@e484923571/Runtime/CsoundUnity.cs(1581,43): error CS0246: The type or namespace name âDownloadHandlerBufferâ could not be found (are you missing a using directive or an assembly reference?)
Thanks for the tests and the suggestions, will fix the build issue soon (should be a missing reference in the asmdefs)
About the custom path, yes! I was thinking of adding it but I didnât have enough time 
About reading the snaps, it shouldnât be too hard, they should be csv I think. The only thing Iâm not sure is if they hold the channel name inside, if not it could be hard to âlinkâ the channels.
Iâll have a look!
The Cabbage snaps are in JSON format, and follow a simple channel:value structure. Should be easy to convert from one to the other. Great work @giovannibedetti
Perfect!
I will add that in, hopefully while at the airport waiting for my flight back to Italy this saturday
Fix for the build issue pushed to feature/presets!
ah yes it will be easy to import Cabbage snaps and also export them from Unity!
{
"test": {
"form": 0.0,
"keyboard2": 60.0,
"att": 0.009999999776482582,
"dec": 0.4000000059604645,
"sus": 0.699999988079071,
"rel": 0.800000011920929,
"filebutton8": 0.0,
"filebutton9": 0.0
}
}@giovannibedetti canât wait for new updates, thank you so much for working on this! One thing I just noticed is that button widgets donât seem to be represented in the presets assets? They show up on the CsoundUnity component but the presets Iâm creating doesnât seem to contemplate channels associated with buttons.
EDIT: the issue Iâve been having with that is that for some instruments Iâm using a button widget paired with a changed opcode to start/stop a continuous sound and it turns out that by changing the preset it unintentionally triggers/untriggers the instrument.
Ah yes that makes sense, since I set all the channels values!
let me add an exception for the buttons.
I will probably push an update to the branch today
EDIT: I pushed an update, not really tested, but it looks good!
Let me know how it goes
Just got a chance to test it, the button exception is working beautifully! Also thanks so much for adding a path to save the preset files!
I just pushed an update to the presets branch, I think weâre getting there!
Now you can choose the save/load folder, and also json presets are listed to be loaded from the editor!
It needs some serious testing, let me know if you find any issue
Unfortunately I cannot add the support for Cabbage snaps easily, because Unity json deserialisation is very basic and it doesnât work with the snaps json format where the keys are the name of the channels.
I have to parse the snaps 
Thatâs a shame. Is it worth looking into using a third party JSON package? Maybe not if you have already written a parser yourself?
Iâm having a look but Iâd like to avoid adding dependencies. I havenât tried to write the parser yet, hopefully it wonât be too hard!
Just sneaked some time to check this out - the option to select which folder to load form is super useful!
EDIT: Everything seems to be working fine with the ScriptableObject presets but the ones I saved as a JSON file donât seem to serialize in the inspector under the Assignable Presets area.
JSONs are meant to be placed in folders that Unity doesnât compile when built, so I am not checking for JSONs that are under the Assets folder. The exception is the StreamingAssets folder, that Unity doesnât compile.
Have a look at https://github.com/rorywalsh/CsoundUnity/blob/6d7465dd3f2d941b6202c45e01a25b4051c028bd/Editor/CsoundUnityEditor.cs#L771
Does it make sense?
If not we can try and think of a solution, for sure there is still some work to be done, for example I havenât tried with a âResourcesâ folder, that could require a custom loading (Resources.Load() => https://docs.unity3d.com/ScriptReference/Resources.Load.html)
Hi Giovanni, sorry for the delay! Ah gotcha - I donât have much experience with JSON files so wasnât aware of that, thanks for the explanation! I can see how using a âResourcesâ folder could be useful to streamline preset management by potentially allowing scriptable objects and JSON presets to live in the same path maybe?
Also, is there a way that JSON presets could be converted into scriptable object presets and vice-versa? Migrating SO between projects has always been messy in my experience, but with a JSON preset I can simply copy the file to another Unity project and it works right away (which would allow me to make a âpreset packâ for an instrument and carry it from project to project). At the same time, SO offer more flexibility to edit them through the inspector and to load them with scripting (since I only need to call CsoundUnity.SetPreset() and pass in a SO as the argument), so it would be useful to convert the presets to SO after importing the JSON files. Not sure if this is too convoluted or if thereâs a simpler solution to this conundrum tho
Hey!
So the latest push I made should allow placing SO and JSONs everywhere, itâs on the same preset branch!
To convert the JSON into a SO you could load the JSON first and then save it as a SO for now, but I will add a method to allow that (maybe a separate Editor Window, since thereâs no point in doing this at runtime, also I think it could make the current CsoundUnity editor more confusing)
Hopefully I will have some time next week to look into this
So it was very quick to add this since all the methods were there already
I decided to add a button for each preset to convert it to JSON or SO.
Not sure what it does to Global presets, but itâs a start 
Same branch: https://github.com/rorywalsh/CsoundUnity.git#feature/presets
I think itâs time I read up on Scriptable Objects. C# is becoming a distant memory to me 