The Api Wishlist Thread

a method for toggling Instrument Properties (below the Instrument Box)
a method for closing Disk Browser and instead having the Instrument Box take up the whole vertical space.

a method for resizing Disk Browser / Instrument Box sizes

and for turning these instrument properties things on/off
Screenshot 2024-04-30 at 16.26.25

EDIT:

Automation stuff:

  • a method for selecting a device within the Track Automation List
  • a method for selecting a parameter within the device within the Track Automation List.

We can already do this with Track DSP (well at least the device selection), just missing it from the Automation List.

This would be pretty magical. I have a script that would really benefit from this.

EDIT:

-- When true, the middle frame views (like the pattern editor) will
-- stay focused unless alt or middle mouse is clicked.
renoise.app().window.lock_keyboard_focus
  -> [boolean]

while this exists, give the same lock keyboard focus for Track Automation. or a way to make the Track Automation focused, maybe not even lock.

Import of Keybindings.xml

Importing Keybindings.xml is a standard feature.
It would actually be very helpful if this could be done with the API.
The only argument required might be the file path.

Renoise has a problem that the key operation system tends to be complex.
For example, if it were possible to import Keybindings.xml by key bindings, it would be possible to change the key bindings set at the same time as switching to the pattern editor, mixer, sample editor, etc., like vim in the editor.

Other application possibilities should be quite wide.
If someone created a key binding set so that Renoise can use a simple operation system like Dirtywave M8, it would also be easy to switch to it.
Even simple additions to functionality have a wide range of applicability, and I believe the impact that can be brought to Renoise through extensions will be very significant.

@taktik Sorry to ping you and make a brazen request. I hope you will consider it. My guess is that it should be relatively hassle-free. Sorry if I am wrong.

I am discussing with @esaruoho in this way in anticipation of those.

1 Like
renoise.song().phrase_selected_line_index
renoise.song().phrase_selected_note_column_index
renoise.song().phrase_selected_effect_column_index
1 Like

need a way of finding out which modulation am in - i.e. Volume, Panning, Pitch, Cutoff, Resonance, Drive

A fully working, full feature XML lib would be very cool, with support for attributes, searching, just like mentioned here. Or an extension of the Document API with attributes and searching…

renoise.song().phrases[].color_blend
renoise.song().selected_phrase.color_blend
renoise.song().scopes[renoise.song().selected_track_index].color_blend

and

renoise.app():load_keybindings("path/to/keybindings.xml")
renoise.app():save_keybindings("path/to/keybindings.xml")
renoise.app():reset_keybindings
renoise.app().clipboards[].paste
renoise.app().clipboards[].copy

so basically a method of using the API to provide content to the pattern iterator

EDIT:
Sample Navigator keybindings. currently not available for binding.

EDIT2:

renoise.song().selected_sample.sample_buffer.selection_range.play

this would play the selection_range

Selecting Sync Format

Add API to select the following sync format

  • Internal
  • MIDI Clock
  • Ableton Link
  • Jack Transport
    image
1 Like

Sample Playback

To automatically play samples after rendering, for example.
Pressing Enter in the sample editor will play it, but I would like to do that with the API.

Screencast:

Retrieving selected text

It would be useful to be able to reuse selected text within the text editor.

add initial_path to all prompt_for_filename etc - so you can set where it should go

renoise.app():prompt_for_filename_to_read({"*.XRNI"}, "Dialog", initial_path)