Re: Re: VSTPlugin v0.5 pre-release!

> Is Reapers chunk data, itself just a vstpreset file?

Can you specifiy what you mean by “Reapers chunk data“?

Anyway, the plugin state is a binary blob and the proper way to share it between different hosts is to save it as a .vstpreset file. Reaper allows you to do that.

Am 3. Mai 2021, 01:43, um 01:43, [email protected] schrieb:
>I’m generating a whole RPP project file with music in the chunk data of
>a
>piano roll vst3.
>
>Each generation is it’s own composition. I’m trying to work
>programmatically with rapid iteration.
>
>Is Reapers chunk data, itself just a vstpreset file? I thought they
>were
>different, but maybe not so in VST3?
>
>The base64 is encoding a simple json string.
>
>I haven’t tried to hack around with vstpresets yet.
>
>Doesn’t every DAW have to field this chunk data? It’s a plug-in dev
>side
>interface right?
>
>On Sun, May 2, 2021 at 3:42 PM <[email protected]> wrote:
>
>> >> Currently I'm encoding the base64 directly in a Reaper project
>file,
>> > There is no base64 involved in VST3 preset files...
>> Ok, I guess you were referring to Reaper preset library files
>(*.RPL),
>> which indeed encode the chunk data as base64 to save it in a human
>> readable text format.
>>
>> However, *.RPL is specific to Reaper. For interoperability with other
>> hosts, you have to import/export *.vstpreset files.
>>
>> BTW, VST3 presets have well defined locations, so if you export a
>> *.vstpreset file in Reaper (to the suggested location), it will show
>up
>> in SC, and vice versa. Generally, always use
>> VSTPluginController.savePreset/loadPreset, unless you really need to
>> store the presets at non-standard locations (e.g. alongside your
>project
>> for distribution).
>>
>> Christof
>>
>> On 03.05.2021 00:16, [email protected] wrote:
>> > Hi,
>> >
>> >> How do I pass chunk data to a windows vst3?
>> > Have a look at the "Presets", "Preset Files" and "Preset Data"
>sections
>> > in the VSTPluginController help file.
>> >
>> >> Currently I'm encoding the base64 directly in a Reaper project
>file,
>> > There is no base64 involved in VST3 preset files...
>> >
>> > Christof
>> >
>> > On 02.05.2021 18:59, [email protected] wrote:
>> >> How do I pass chunk data to a windows vst3?
>> >>
>> >> Currently I'm encoding the base64 directly in a Reaper project
>file,
>> >> but I want to get everything in SC.
>> >>
>> >> Can VSTPlugin for SC do this?
>> >>
>> >> On Tue, Apr 27, 2021 at 5:51 AM <[email protected]> wrote:
>> >>> Here is VSTPlugin v0.5-test3:
>> >>> https://git.iem.at/pd/vstplugin/-/releases/v0.5-test3
>> >>>
>> >>> I've fixed a couple of regressions and improved the multibus
>handling.
>> >>>
>> >>> Please test and report any issues!
>> >>>
>> >>> This should be the last test release before the final release.
>> >>>
>> >>> Cheers,
>> >>>
>> >>> Christof
>> >>>
>> >>> On 18.04.2021 01:36, Christof Ressi wrote:
>> >>>
>> >>> Hi,
>> >>>
>> >>> here is a pre-release for VSTPlugin v0.5 - a SuperCollider
>extension
>> >>> torun VST2 and VST3 plugins.
>> >>>
>> >>> You can download it here:
>> >>> https://git.iem.at/pd/vstplugin/-/releases/v0.5-test1
>> >>>
>> >>> ---
>> >>>
>> >>> The most important changes:
>> >>>
>> >>> * JITLib integration: add VSTPluginNodeProxyController class and
>> >>> some NodeProxy roles (\vst, \vstFilter and \vstDef)
>> >>>
>> >>> * VST3: support for multiple input/output busses (see
>VSTPlugin.ar)
>> >>>
>> >>> * VSTPluginDesc: add 'inputs' and 'outputs' members containing
>the
>> >>> input/output bus info (name, type, channels)
>> >>>
>> >>> * VST3: fixed possible wrong channel count (regression introduced
>in
>> >>> v0.4)
>> >>>
>> >>> * Linux: allow to run 32-bit and 64-bit Windows plugins (via
>Wine)
>> >>>
>> >>> * Linux: fix non-functional VST3 editor
>> >>>
>> >>> * some thread-safety improvements which fix occasional crashes
>with
>> >>> NI plugins (and possibly others)
>> >>>
>> >>> ***WARNING*** This release contains certain breaking changes in
>the
>> >>> UGen implementation (see changelog). Users of sclang are not
>> >>> affected, but existing alternative clients have to be updated!
>> >>>
>> >>> The full changelog is here:
>> >>> https://git.iem.at/pd/vstplugin/-/releases/v0.5-test1
>> >>>
>> >>> ---
>> >>>
>> >>> Beside trying out the new features, it would be very appreciated
>if
>> >>> youcould test it with your existing projects and check if nothing
>is
>> >>> broken.
>> >>>
>> >>> If you find any issues, please file a bug report here:
>> >>> https://git.iem.at/pd/vstplugin/-/issues
>> >>>
>> >>>
>> >>> Have fun!
>> >>>
>> >>> Christof
>> >>>
>> >>>
>> >> _______________________________________________
>> >> sc-users mailing list
>> >>
>> >> info (subscription, etc.):
>> >>
>>
>http://www.birmingham.ac.uk/facilities/ea-studios/research/supercollider/mailinglist.aspx
>> >> archive: http://www.listarc.bham.ac.uk/marchives/sc-users/
>> >> search: http://www.listarc.bham.ac.uk/lists/sc-users/search/
>> >
>> > _______________________________________________
>> > sc-users mailing list
>> >
>> > info (subscription, etc.):
>> >
>>
>http://www.birmingham.ac.uk/facilities/ea-studios/research/supercollider/mailinglist.aspx
>> > archive: http://www.listarc.bham.ac.uk/marchives/sc-users/
>> > search: http://www.listarc.bham.ac.uk/lists/sc-users/search/
>>
>> _______________________________________________
>> sc-users mailing list
>>
>> info (subscription, etc.):
>>
>http://www.birmingham.ac.uk/facilities/ea-studios/research/supercollider/mailinglist.aspx
>> archive: http://www.listarc.bham.ac.uk/marchives/sc-users/
>> search: http://www.listarc.bham.ac.uk/lists/sc-users/search/
>>