I can make Renoise crash by using your newest update and a particular song where I loop 2 patterns, but unfortunately no hints in the log / or script error notice.
As said before, with certain patterns containing a lot of data, during pattern switching from one to the other, there is a delay / visual hick up. In this song, continually looping 2 heavy patterns Renoise crashes. Maybe you/someone can replicate the crash initializing Lauflicht on heavy tracks?
Thank you. The song did not crash Renoise for me, but there is a significant “hick up” each pattern change. As there are 127 rows in the pattern this does not really wonder. As stated above, on each pattern change the new notes have to be loaded, what requires the parsing of the pattern and do some internal tool stuff. However, it seems to be a perfomance problem when using very “heavy” songs with large patternsizes; I try to figure out at which point it hangs and how to improve it; maybe the devs can give me some hints then.
Thanks for the info, I think its best for me to use the tool fresh from the start, then to re-juggle existing songs, which often use +112 line patterns.
Well the bottleneck was not really the length of the patterns, but the heavy use of multisamples. Anyway I have tried to solve this and I think the solution made a big performance improvement on pattern change/pattern reload. Could you please try with the song which Renoise crashed? And please could you tell me how much delay you have (in pattern lines) on pattern change. I have now 6-7 pattern lines delay currently in the last two patterns.
v.1.87 for 32 bit:
performance improvement on loading a pattern into sequencer/pattern change
Gotta post again how awesome the Launchpad edition is !
After some hours of testing I can say that 1.5 runs pretty stable over here.
As long as you don’t create a 9th track by accident everything runs smooth,
when sequencing my funky drums.
Future suggestion:
Somebody already wrote, that it would be dope to adjust the default matrixcontrollers and save them as presets.
It’s hard to find the right steps on your knobcontroller hardware when you are
inside the matrix editor and want to adjust a specific controller@ a specific step.
Now, since I activate “notecolumn1>Notes” on the first matrix line,
it’s much easier to orientate and edit the controllers in line 2-xy and find the active steps easily…
Another lauflicht with the active tracksteps in the matrix section grid would do the job as well…
Indeed. Also you could have some predefined presets like “random”, “line up”, “line down” or something like that, which generates some values for a parameter line of the matrix.
But this seems to be quite time-consuming to code, so not in the near future but with another major version increase.
Good point.
Unfortunately you can not adjust the (background-)color of a gui-controller like a value-field. So you could color every fourth value-field or so.
But yes another headline with the active tracksteps would be possible I think, at least a lauflicht-like button row with every fourth step colored (and step-nr as text).
is now implemented.
It is like the original “Lauflicht” button-bar, with two additional features: Each button is labeled with the current note value of the corresponding step; each button is clickable and sets/unsets a note.