I would also like this feature very much. Could those keybindings be implemented with LUA scripting?
This topic is from 7 years ago. I do not know if anything has progressed since then. But what I do know, is that to do this through scripting, it is necessary to build the functions from scratch.
For example, if you want to transpose X note (D#5), a V value (12, a octave) from note column C (3) into pattern P (2), you must create a specific function for it. Then, that function can be triggered from a button, or from a specific keyboard command, or from an access within a Renoise drop-down list.And so with each and every one of the functions.
Through scripting, and according to the available API and the LUA language, you can do many things, but you have to build them.For example, in the following link you have a function that exactly mimics the jump of the Renoise step lenght, to navigate up or down:https://forum.renoise.com/t/improve-shortcuts-jump-to-0-16-32-48/49198
That same function, possibly can be written in another way. But it is necessary to create it, and then ādo somethingā to be able to execute itā¦
This topic is from 7 years ago. I do not know if anything has progressed since then. But what I do know, is that to do this through scripting, it is necessary to build the functions from scratch.
Thank you for your reply. I would like to create keyboard shortcuts to set quickly different content masks. Would it be achievable without having to get too deeply in scripting?
Thank you for your reply. I would like to create keyboard shortcuts to set quickly different content masks. Would it be achievable without having to get too deeply in scripting?
Could you give a concrete example of what do you mean with āset quickly different content masksā?
Could you give a concrete example of what do you mean with āset quickly different content masksā?
For instance, a shortcut to select the volume column only. Another one to select just the delay column, etc. I use those two masks A LOT and it would save me both time and wrist pain if I didnāt have to use the mouse every time I need them.
For instance, a shortcut to select the volume column only. Another one to select just the delay column, etc. I use those two masks A LOT and it would save me both time and wrist pain if I didnāt have to use the mouse every time I need them.
Apparently, since 2011 this property has been requested to be observable, not read only:
-- The currently edited sub column type within the selected note/effect column.
renoise.song().selected_sub_column_type
-> [read-only, enum = SUB_COLUMN]
renoise.Song.SUB_COLUMN_NOTE
renoise.Song.SUB_COLUMN_INSTRUMENT
renoise.Song.SUB_COLUMN_VOLUME
renoise.Song.SUB_COLUMN_PANNING
renoise.Song.SUB_COLUMN_DELAY
renoise.Song.SUB_COLUMN_SAMPLE_EFFECT_NUMBER
renoise.Song.SUB_COLUMN_SAMPLE_EFFECT_AMOUNT
renoise.Song.SUB_COLUMN_EFFECT_NUMBER
renoise.Song.SUB_COLUMN_EFFECT_AMOUNT
Ifrenoise.song().selected_sub_column_type were accessible, it would be very simple in a tool to direct the cursor in a specific sub-column, and therefore, assign a specific keyboard command.
Personally, I built myself for my own use VPDpro tool, which allows you to insert parameters in each subcolumn without needing the cursor to be in it.
Ifrenoise.song().selected_sub_column_type were accessible, it would be very simple in a tool to direct the cursor in a specific sub-column, and therefore, assign a specific keyboard command.
Thank you for looking into the matter. I think I have found an easier solution that seems working well : using a macro recording tool.