Dragging the .xrnx from the github link above doesn’t seem to do anything here when trying to install in Renoise. Dunno if I’m doing something wrong on my end or there is something else going on?
edit;
using Renoise internal tool updater I’ve been able to update to version 2.0
A big win would be giving these talented scripters more powers so they don’t have hack their way around “problems”, like with the invisible xy pad hack to move stuff around.
Great work mate. All mousefunctions are working, but the notemoving is sluggish for me. Mouse warping i have off. Dont know where the problem is. Renoise CPU was 2-3 % but i dont know if script CPU Consumtion is showed in Renoise CPU view.
My System → Intel Sandybridge I7 2600K @ 4 x 4,3 GHz, 16 GB Ram, Samsung 850 SSD
I dont know the internas of you hack, but i noticed that you between the drag status permanently syncronize the Notstatus with the Renoise Notecolumns. Maybe it could be more performant, if you stops this at start notedragging and restart it after droping the note/notes. This had the advantage that CPU consumtion for Changing the NoteList Observables and Repaintings, thats causes further control repaintings maybe, would be stopped.
Or it becomes simply to the limits of API and Control Hacks. I dont know the possibilitys for limiting Rendercycles at your controls u used. But you should use this even if you can where it sensefully.
I keep on testing it and reporting here.
The larger the grid, the slower the rendering of the piano roll. There will certainly still be room for optimization, as this is the first version with extensive mouse support. I’ll will try to improve this more in upcoming versions.
I see. I thought scrolling between patterns. Sometimes we can have notes that continue from one pattern to the the next one. It will be useful to see all context. But it is a hard task I think.