Simple Pianoroll: com.duftetools.SimplePianoroll.xrnx

Thank you so much, it works perfectly.

For all intents and purposes, I just checked, the edit step values for the pattern editor are mapped to CTRL+the accented characters by default, it seems (I never changed them).
image

2 Likes

Thx for testing. Yeah could be possible that Renoise is using scan codes. In the tools api, i only have key name and character. I’ll add some info about AZERTY to the readme, so it will less confusing.

:+1:

New version uploaded 1.8

Shading amount of grid can be changed now.
New highlighting of the whole row during playback, similar like in FL. (can be disabled)
Several bug fixes.

image

  • feature: add little transport buttons (play, loop and stop)
  • feature: add note row highlighting, when note is playing and preview
  • feature: add display support for Qx fx command
  • improve: add AZERTY keyboard mode
  • improve: add shading settings for piano roll
  • changed: remove playing note highlightings, when playback stopped
  • changed: note click audio preview can now be hold
  • fix: default value for display time of key info bar
  • fix: render retrigger effect on line 1 and when note length shorter 1
  • fix: wrong note highlighting, when note was shorten with cut effect
  • fix: broken centering of the grid
  • fix: crash when note instrument value is not valid
6 Likes

Had this issue :confused:

‘C:\Users\myusername\AppData\Roaming\Renoise\V3.2.1\Scripts\Tools\com.duftetools.SimplePianoroll.xrnx’ failed to execute in one of its menu entry functions.

Please contact the author (dufte (toimp)) for assistance…

main.lua:1251: unknown property or function ‘style’. can not assign new properties to an object of type ‘Text’
stack traceback:
[C]: in function ‘_error’
[string “do…”]:15: in function <[string “do…”]:9>
main.lua:1251: in function ‘fillTimeline’
main.lua:2509: in function ‘main_function’
main.lua:2550: in function main.lua:2549

You try the 3.2 build, right?
Could you upgrade to Renoise 3.2.2? It seems there was a bug in 3.2.1: [fixed 3.2.2] Problem API with viewbuilder text: "style" property, not available to change

The best would be to upgrade to 3.3, so you can use the latest version. There are a ton of changes and fixes between 0.7 and 1.8 :slight_smile:

I have a suggestion to you. It is very confusing for me that the window is not painted always in the specified H-Gridsize like defined in preferences.

For explaning my Gridsize is 108 horizontal. I maked a Song with 128 patternlenght and 108 is for me the most comfortable size. After work a few days with this, i reload an old project with only 64 'er patternlenght. And the windows was only half size big. This was so strange that i thought this where a bug in first moment. After some thinking i came on the patternlenght differs causing this. I tried different song with differenf patternlenght and the size of the windows is everytime different when the pattern lenght is under the configured H-Gridsize.

I would prefer if the windows always open with configured gridsize for better ergonimics and overview. if patternlenght is smaler as gridsize value leave the rest unpainted if maybe.

happy tracking :slightly_smiling_face:

1 Like

New version uploaded 1.9

Added hacky scroll wheel support:
scrolling

Detected or selected scale is now visible:
detectscale

Current track with track color is now visible:
currenttrackwithcolor

  • feature: “hacky” scrollwheel support for grid and piano keyboard scrolling
  • feature: add keyboard shortcut page down / up for scrolling vertically
  • feature: show current track name and color above the piano keyboard
  • improved: show current selected or detected scale under the piano keyboard
  • changed: window width will be stable, doesn’t jump between pattern length width’s
  • fix: dont allow to change ghost track to group type
  • fix: several smaller fixes

For download see first post.

7 Likes

Your keyroll Editor becomes better with every version. Great work mate! :slight_smile:

2 Likes

One of the best tools I’ve ever seen a Renoise User add. The fact I can copy, paste, delay, do so much with the editor to transpose as well, see ghost tracks. It’s a complete game changer.

Bless your kind soul for updating it so frequently. Thank you so much for making this, FOR FREE. It’s amazing!

You’re amazing.

3 Likes

The man is a genius!!!Keep up the good work this is a game changer for a lot of people and although i dont like piano rolls i like to have the option available.Thank you

2 Likes

I think i have found a Bug. If i resize patternlength he stretches last Note. Dont sure if this is expected behaviour.

image

After the patternlength change i get this

image

And i have a suggestion too. Can you mark then end of pattern with and blue “E” or something and draw the free windowarea like disabled range. Maybe outhatched or darker or with less saturation painted? This would not looks so empty at smal pattern sizes.

And a Qestion. right direct besides Pianoroll is a 2-3 pixes width viewrange where some half notes (black) will painted white if i set Notes in grid. what means this function?

i mean something in this… not too complex

Unbenannt-1

happy trackin :slight_smile:

1 Like

Yep, you reported this already. Didn’t tackled this, yet.

You mean this?
image
It’s this feature:
image
Can be disabled. I use this, so i can quickly draw fitths for the current selected note.

2 Likes

Hi,

instead of the outhatched area after patternend you could integrate ability of wallpapers/backgroundimage if that is maybe. then we could get such… :grin:

Unbenannt-1

happy tracking :slight_smile:

2 Likes

Ok something more serious now…

…something like in this way. Dont give what on Colors, but it should shows in any way that you are above the bound of pattern.

End of Pattern

What would a very nice option too would a selection of Patternlenght in that windows. before a few days my second monitor was killed by an overload of thunderstorm and moving window to get on original patterlenght changcontrol broke the workflow.

happy tracking :slight_smile:

1 Like

You mean a text field, where you can change the pattern length?

Yes, but i would prefer the same control as original Renoise one. That means a value counter box because of the mouse support. :slight_smile:

Hello!

Some more feature request for this great Renoise-pianoroll. :slight_smile:

It’s able to retrieve the Track Column mute status in playing visualizing? I had realised that the mute status is ignored so far. Would be nice when we can get this function in. At the Moment muted Notes will be displayed as played notes. Here a Screenshot, to explance in detail.

AND TO THE RENOISE DEVELOPERS! WE NEED A COLORATTRIBUTE ON THE NOTE-OBJECT!!! THEN WE COULD ASSIGN DIFFERENT COLORS FOR NOTEGROUPS IN THIS PIANOROLL LIKE IN OTHER DAW’S: DONT KNOW IF YOU READ WITH HERE, BUT I HOPE SO!

Muted Columns

happy tracking :slight_smile:

//EDIT

I have found out that you set the Notes in the order of their creation index in the linear circeling/upswitching Track column index that is not so good choice in my opinion, then the lower c-2 and c-3 notes on every accord play could placed on different Trackcolumns. Thats not good for working. It would be better if you place it always by nearest Note on the appropriate Column. I am aware that this adding mechanism would be not easy to implementing. And i have a Solution to make this very easier. Make a Button “Notesort” in your tool that make this manual by userinteraction or when your Tooldialog window is closing. Even much easier would it be if we had a Color Attribute for instance and we could mark Column Notegroups as we want. Then you only have to check the value of the colorattribute and write all Note with same color to 1 column. Thats it! :slight_smile:

Alternative let me choose the Columnindex of note with switchable buttons at least. Workflow would be so.
i activate button 1 before i set notes with pen. Then i activate button 2 and i set my notes for second TrackColumn. On Notadding you only have to parse this index Value and you have the Trackcolumn, where to add the appropriate note. I hope you understand what great advantage these Columnassignment would had and much easier the entire Columnworkflow would be. :slight_smile:

maybe generally an adding after noteheight from down notes to high notes would be senseful do the thing. Its very late and im not more able to thinking about all cases.

BUT YES I’M SURE, Columns respectively the Column-Index of Track should build the Notegroups in Pianoroll. Then Noteediting outside Pianoroll like with the global Transposing/Note/Instrument assignment controls and so on would be much better

1 Like

This is absolutely lovely work @toimp

I really hope development see the value in this, and offer you to implement it as a view panel

Looking forward to:

  • select multiple notes (RTFM :stuck_out_tongue: )
  • mouse drag
  • grid snap on/off
  • zoom function

:wink:

2 Likes

There are some possibilities:

  1. Rectangle selection, click on one spot, hold shift and click another free spot.
    rectselect

  2. Hold Ctrl and click notes:
    ctrlselect

  3. Hold Ctrl and click on step indicator to do a “column”-selection:
    ctrlstepselect

  4. Hold Ctrl and click on a note in piano keyboard to do a “row”-selection:
    ctrlnoteselect

3 Likes