Keybindable, perhaps… but midimappable?
+1
+1 on keybindable expand+shrink
and slightly quieter: +1 on keybindable advanced edit parameters
1 Like
+1 here too.
1 Like
at least advanced editing shrink/expand keybindable would be awesome…
previous +1’s from various users: Expand/Shrink in Advanced Pattern Editing Commands
what would nudge-selection do? i’m interested.
I think the first thing I would try doing is linking an LFO Meta with a squareform to the AE’s Notes>>>Transpose>>>+12/-12 with Track In Pattern selected.
I would also probably get Renoise extremely process intensive linking another LFO Meta to Interpolation Types & also Instruments.
The Pattern Editor would look Sentient.
well, yeah i guess… there are always some interesting things which could be done, when it comes to regular tracker features becoming midimappable… however, even keybinding of advanced edit features would be wonnerful
+1
flip, shrink, expand, toggling of mix paste mode, as well as an option to change selection to current instrument all deserve to be key-bound.
If they don’t deserve to have default bindings, they should at least be user assignable. Give us the power!
Hello taktik. Here is an example why this is useful very often.
By giving us shortcuts for Expand/Shrink selection, expand/shrink column, expand/shrink track, and Expand/Shrink pattern, you’re giving us a great deal better control over pattern data contents. And especially for those people who use Renoise live.
A very common edit for me in IT/ST is copy selection/track/pattern > double/halve length > mix-paste from clipboard at some interval; just to hear what the variation sounds like. This is especially interesting when working at BPMs like 180 which can also work at 90 and 120 BPM.
Also, maybe there are some renoise users with physical or neurological conditions which prohibit mouse/touchpad usage.
I would also like to have the transpose buttons midi-mappable.
I would also like this feature very much. Could those keybindings be implemented with LUA scripting?
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.
VPDpro:https://forum.renoise.com/t/development-of-vpdpro-chordpad-some-demostrations/48619
1 Like
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.
Can you be more specific as to what kind of macro recording tool you use, and for what, please?