This is awesome. Thank you!
If I have playback running and I use step up or down command, I get this error (screenshot.) It seems to work perfectly when playback isn’t running.
This is awesome. Thank you!
If I have playback running and I use step up or down command, I get this error (screenshot.) It seems to work perfectly when playback isn’t running.
Thanks for letting me know @tumult, this feature shouldn’t even be there, was just testing it to see how viable it would be to trigger the line while stepping like in other trackers.
The above crash is fixed and this optional feature is hidden as a toggle in the settings (trigger line inside pattern
).
What it does is it triggers the pattern at the position you are stepping at so you can hear what you are changing, it is nice for one shot samples but looping ones will just keep playing which is not so good, so this is disabled by default.
Oh btw, anyone who had this tool installed before the new Renoise version, you might want to uninstall the tool through the Tool Browser as I changed its Id to match my actual domain (and the Id for all my other tools), otherwise you could have this tool installed twice.
The new version has
com.unlessgames.val...
instead ofcom.unless.val...
.
Sorry for this inconvenience, won’t happen again! This tool was my first and I didn’t know…
Ho do you assign keybindings ?
I can’t find any of the tools inside renoise keybindings menu
@gentleclockdivider
here they are
name = "Pattern Editor:Column Operations:Step value up",
name = "Pattern Editor:Column Operations:Step value down",
name = "Pattern Editor:Column Operations:Step value up (by 16)",
name = "Pattern Editor:Column Operations:Step value down (by 16)",
name = "Pattern Editor:Tools:Toggle relative mode (value stepper)",
name = "Phrase Editor:Column Operations:Step value up",
name = "Phrase Editor:Column Operations:Step value down",
name = "Phrase Editor:Column Operations:Step value up (by 16)",
name = "Phrase Editor:Column Operations:Step value down (by 16)",
name = "Phrase Editor:Tools:Toggle relative mode (value stepper)",
yeah but it’d be neat if this had a more discoverable naming convention. like i don’t know - maybe
Pattern Editor:Value Stepper:<name of feature>
Phrase Editor:Value Stepper:<name of feature>
?
Thanks !
Probably could be better named, but I don’t want to change this now since the keys would stop working for people who already have the tool and they’d have to reassign bindings, maybe it’s not a big deal though, idk.
If its only those few I think you can get away with it… friendly enough folks around here I’d say!
esa on the other hand changing all his shortcuts might raise a few eybrows though!
oh, i try to keep the shortcut naming convention changes pretty minimal, and tell people when they are changed/renamed for better discoverability
btw, @unless you could solve this by maintaining two sets of shortcuts, the original ones and then the Global:Value Stepper:Function Name
ones. but i guess that could be considered tedious, too.
Two shortcuts to the same action would be confusing and bloat.
@gentleclockdivider I assume you’ve meant to send this reply to me here?
If so, the keybindings should be inside Phrase Editor / Column Operations
. Maybe you are using an older version? You can verify this by selecting com.unlesssgames.value_stepper
inside Tools / Tool Browser where it should say V0.6
in the information at the bottom half of the window (note, if you have a previous install with id com.unless.value_stepper
you should uninstall that one)
Esaruoho already helped me out
But thanks , anyway
Glad it’s solved but I meant the off-topic new comment from an hour ago under the unrelated thread (Failed to access the Backstage and download Renoise - #4 by gentleclockdivider), which probably should be removed?
Thank you for perfecting this! now FX column works too , agree, should be native.
Cheers! btw FX columns were working since the beginning, the latest addition is the same actions being possible in the Phrase Editor.
Oh I was talking about earlier tools and scripts attempting this same concept, I suppose it’s a new API because I never even seen it listed under column operations.
Ah ok, yeah I’ve tried to apply the same concept for every kind of value. Let me know if something is missing though!
Doing it in the Phrase Editor was possible thanks to the new API in 3.5, if you meant that.