Hi Denim
I modified the idea a bit, and would call it:
-
Export track properties.
-
Export group properties.
-
Import track properties.
-
Import group properties.
I know this is possible to add it natively, and it would not be complicated at all (except the sons of the group).It is also possible to create a tool that does exactly that. The tool could have several banks to store different configurations. The only thing that would lose the data if it desisntala the tool. For that you could save the preferences.xml file of the tool, or create “something” to easily save it from the tool in a specific folder. This is where the difficulty is (with the api available I think it is not possible to save an xml.).
Exporting or saving all the properties of a track in a table is simple. Then it would be easy to access the data through another “import” button. Saving the properties of a group, with all the tracks and groups of daughters, would be much more complicated. In this case, it would be better to use a song template. But of course, you could not implore a group to your project at any given time.
I would prefer that this matter be native. But if there is no hurry and it is very requested, I am committed to creating the tool myself. I find it very interesting.
…
Anyway, something similar is a tool that inserts you types of tracks and groups. Maybe you like this approach more. Of course it is easier to build it.
Look at this topic:https://forum.renoise.com/t/development-of-vpdpro-orchestral-some-demostrations/48552
By the way, I do not know what style of music you compose. But if I had a concrete list of names for electronic music instruments, well thought out, I could create a tool similar to VPDpro. Orchestral
I have a few saved DSP chains that are in fact just a bunch of hydras with MIDI mappings.
Because (perhaps unbeknownst to many), those mappings are saved along with the DSP chain.
It’s not a full blown track template as you describe it, but goes some of the way. And a tool could “easily” augment this, to add the additional functionality.
You could save all the properties of a track in a table, inside an fixed xml file (preferences.xml).
But, is there any way to save xml files with custom names, through the API, that you can then load into the tool again?
I wonder how you would keep all the properties of the children tracks and children groups within the parent group.
By the way, saving the DSP chains in a tool would also be somewhat complicated. There can be hundreds of parameters.DSP chains should be stored separately, which is already possible.And at least, the properties of the track could be saved through the tool.