Hi @taktik ,
is there a way to convert a Renoise instrument to active_preset_data for Redux? Is there documentation about the vstpreset structure of Redux?
The preset data is raw binary data of a Renoise XRNI instrument. Nothing more, nothing less.
Woa! nice, I will try that then hehe
So for reference, by raw binary data of a Renoise XRNI instrument you mean the instrument XML raw binary encoded or so? Could you give me some more details or some basic example? Or should I just test around with Redux?
Ah, and can you use Redux as an VST3 fx, too? This for replacing Renoise internal fx in an 1:1 manner …
This is for a possible DAWProject exporter tool?
The CDATA stuff is Renoise specific. You need to follow the DAWProject specs. Maybe you can use a FileReference here too.
Yes, structure/preset data export already works, now I am on the actual note data…
The DAWproject specs seem to be not that final state yet… It seems to be a bit wild currently.
There are some inconsistencies, and each of the three DAWs (Bitwig, Studio One, Cubase 14) does the export slightly different. There are also a lot of redundancies. So after I’ve done the export, I will try to suggest changes for a v1.1 spec. Hopefully someone will read it.
The idea was to convert a plain Renoise instrument to a Redux VST3 instance while export.
Simply save the instrument and load it in Redux then.
Can I trigger instrument loading in Redux via Renoise scripting? So you are saying that I should not convert the instrument preset data into an vstpreset data? Maybe I am misunderstanding you 
I need vstpreset data for Redux, that was the idea. So the exported song loads all vanilla Renoise instruments as Redux instruments.
I see some zip? compressed Instrument.xml… So theoretically (I assume not) I could bin replace starting from “PK”?
1 Like
Ah, and I have to byte rotate for example the chunk list offset, e.g. here from 16 09 0A 00 (at 0x28) to 00 0A 09 16 (because there actually starts the “List” identifier)… What is this rotation type called, little endian 32 bit?
The class id is a static data per plugin, correct? Oh ok, it’s the plugin id. I am curious how this will work… Later need to convert macro control automation to the plugin automation, assuming that it is exposing the exact same macros.
@taktik I can also place Redux VST3 as an effect into the dsp lane:
What’s missing to make it work as an dsp fx wrapper only here? Are here still development changes required, e.g. VST3 polymorphism support? Or should this already work by using the line-input device or so?
AFAIK more recent VST3 synths can also load as fx, and then also can act as FX. I forgot which plugin already can do this… Might need support for the “correct input pins” by the DAW, too…