Adding persistent (docked) view

bitbear · July 18, 2015, 11:43am

I’ve searched around, read documentation and can’t seem to find any way to add a persistent (docked) view into one of Renoise’s existing views (or whatever they are called). Please let me explain what I want to do: I’d like to add a view that lists of all detected VST plugins in all tracks and that this view is docked at the end of the device chain on the master track or somewhere else where it’s easy to reach.

Ultimately, what I want to do with the plugin is to go through all VST plugins in the song and adjust their "quality, “phase” or “oversample” parameters from minimum to maximum and vice versa. I’m planning on using this to adjust everything to “minimum” or some other usable value while producing and adjust it up to the highest quality before rendering. It would be awesome if my plugin could actually initiate rendering of the song as well so I just had to click one button, but as I understand from these threads, song rendering is not exposed in the API just yet.

Do I have to settle for a dialogue that pops up from the click of a menu item, or is something like this possible? The reason I want a docked view is to see its current state and being able to adjust it quickly.

joule · July 10, 2019, 8:02am

Custom popup windows are all that’s available. No docking. (Bringing it up with a shortcut might be a little more convenient than having to click a menu)
Rendering can be done from the API as seen here:

github.com

renoise/xrnx/blob/1b50e2437f51dd2fe21b8298a6f8f080d2433dcd/Documentation/Renoise.Song.API.lua#L186-L218


-- Start rendering a section of the song or the whole song to a WAV file.
-- Rendering job will be done in the background and the call will return
-- back immediately, but the Renoise GUI will be blocked during rendering. The
-- passed 'rendering_done_callback' function is called as soon as rendering is
-- done, e.g. successfully completed.
-- While rendering, the rendering status can be polled with the song().rendering
-- and song().rendering_progress properties, for example, in idle notifier
-- loops. If starting the rendering process fails (because of file IO errors for
-- example), the render function will return false and the error message is set
-- as the second return value. On success, only a single "true" value is
-- returned. Parameter 'options' is a table with the following fields, all optional:
--
--     options = {
--       start_pos,     -- renoise.SongPos object. by default the song start.
--       end_pos,       -- renoise.SongPos object. by default the song end.
--       sample_rate,   -- one of 22050, 44100, 48000, 88200, 96000, 192000. \
--                      -- by default the players current rate.
--       bit_depth ,    -- number, one of 16, 24 or 32. by default 32.
--       interpolation, -- string, one of 'default', 'precise'. by default default'.
--       priority,      -- string, one "low", "realtime", "high". \

This file has been truncated. show original

The DSP oversampling option isn’t available as a parameter, but you can use the trick of altering the device.active_preset_data xml with some string pattern matching/replacing.

system · July 17, 2019, 2:46pm

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.