I’m a new user of Renoise. Have to say it is really a breath of fresh air! I Really am enjoying it.
Question - since I learn a lot by reverse-engineering the demo songs that were supplied, It would be great if I could hover the mouse button over the sample and pattern command columns, in order to see, at a glance, what commands were used for a particular effect.
If you carefully inspect the status bar while typing them, you get hints about the command that you are currently inserting.
If there is more info that you could use then posted, perhaps that can simply be added.
Not for hint tooltips. Tools can monitor user input on effect columns and provide dialogs when stuff is being inputted, but this removes keyboard focus from the pattern editor and that is annoying as hell. They can also send the info to the status bar instead, but frankly Renoise already does that part for sample effect commands.
You know you can right click any automatable DSP parameter and it will create a pattern command for it?
When the command is written you can go to it in the pattern, write one of the numbers or letters in the command and it will tell you what it does in the status bar.
I think it would be nice to see the same info by just selecting the single command as well though, or by hoovering above it like suggested.
Yes I realize that. My point was that after you have done that, the hover thing would make it easier to see what these commands are doing. If you have multiple dsp commands in a track it can get a little hairy.
You could try this script for starters (updated):Attachment 4620 not found.
It is an initial start (does all sample and global commands) and needs some fine-tuning on the panning and mixer volume adjustment representation, anyone feeling to add support for DSP effects and vol/pan/del column effects, feel free to add what you can and repost.I also forgot to add some basic arpeggio table, but frankly, who is still gonna use the arpeggio command?
Simply hover the script over Renoise and drop on it, then it installs automatically.
You might need to “reload all scripts” to trigger it the first time, but i have not added any options to start or stop the script. (if you want to stop it, disable it in the tool-browser)
Hey, cool idea for a script. When “parking” the cursor on top of a command it does interfere with other status messages, though - making it impossible to read other messages printed to the status bar.
Perhaps it would be nicer to output the message just once?
For a native implementation, it could perhaps make sense if mousing over a command would display the message as a tooltip, while using the keyboard to navigate the pattern would display a status message (to avoid cluttering the interface).
It was just a very quick and dirty solution, i perhaps could use the line-notifier instead so that the statusbar only gets updated when typing the command.
More or less overruling the native message. But in that regard, there is space enough to embed that kind of behavior natively, also brings down the steep learning curve for the hex-ignorant folks.
I’m not sure if i want to see tooltips all over the place. They also don’t always disappear in some cases. Then i rather go for the extension of the native status-bar message info using the (improved) trickery i stuffed in that script.