12/16/2023 0 Comments Renoise keyboard shortcuts![]() (Well, yeah, that’s a feature… kind of… ok… so I want that one!) And on a recent thread there kinda built up a suggestion to rise up and speak for the keyboard people. So this post is not really about getting new features as such, but only about getting the current features reachable with keyboard. I’ve also done a quick search on the forum and tried to link some relating threads here. So these are issues I’ve come up with when trying to use renoise on a more “2 hands on keyboard” -kind of way. That is of course something to keep in mind. For some (or most?) the 1-1 will probably work just fine. For a 2handsonkeyboard-guy the 1-1 -paradigm brings about constant speed bumps when going about tracking awesome muzaks. That specific tracker being the way it was is not a reason for renoise to be like that too, but because renoise shares very much of the tracker-ness of that program, it certainly is a reason for a lot of frustration for me. These are just notions I’ve made that have root in me having a distant background with Impulse Tracker, which I recall being way more oriented towards the “2 hands on keyboard” -approach. Now I myself came to renoise just recently, with version 2.6, so I’m hardly someone to come up and tell everybody what’s wrong with the program. Probably even “Left hand on keyboard, and Right hand on mouse”, if one considers the placement of the transport-bound modifier keys, which, up until 2.8 (I assume) were not usable as modifiers. It seems to me that renoise is currently designed with a “1 hand on keyboard and 1 hand on mouse” -situation in mind. Or this is more like a collection/discussion/problem-solving post really. I’ve recently bumped into this keyboard issue on a few occasions, and decided to take it up on a suggestion post. ![]() Also thank you for everyone submitting more issues. Though maybe I could setup a really big OSCulator map that covers all possible key commands…hmm, that might work until I can figure something better.UPDATE: Thank you for the fast response on several points in this list while also building up a full new version. ![]() I don’t think I can even do that with OSCulator because it doesn’t have deep enough capability to translate the incoming OSC message into the appropriate key command, its designed more to hard code a map where each incoming OSC message maps to a specific key command. I would prefer to be able to launch the program, have it sit in the menubar as an OSC server that just takes well defined OSC messages and converts them into key commands using rules. I do see this is not entirely straightforward to do directly in O-S-C, perhaps because its using javascript?, not sure…but anyway, in the meantime I could use OSCulator, which I will look into, though I would prefer not to have to use OSCulator and especially I would prefer to not have to setup a specific key command map to load into OSCulator when I want to use it. This also could pose a security threat, however… so I don’t know…but for me at least that would be very much preferable because i want to put all the configuration for a “setup” in one place, not spread out on multiple tools. That way all the rules about which keystroke to send can still be driven from O-S-C by simply having it send the appropriate OSC message that has all the data needed to generate the keystroke. It should be a blind translator that takes the OSC message that should be following some rules…and turns it into a keystroke, without any additional mapping required. What we want to avoid having to do is needing to setup a separate MAP inside this other key sender program. Maybe at some point I will look into trying to create it, at least for OSX. So what would be a good solution for this, would be a simple program that translates OSC commands into keystrokes, using the parameters of the OSC command to determine which keystroke to send.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |