Nice work Cie, still some lag on heavy songs though definitely feeling that optimization 
, good job, only thing left for me to suggest is to have page’s update, auto scroll in the tool while playing a song 
@kopias: great, thank you for testing and the request. 
@Djeroek: this is great Nice feature request, will add it to my todo list. This should be then optional (to be set on/off).
I’ve bought Lauflicht without prior testing and tried to use it recently. Found out that it forces me to use separate tracks, which is not good if you’re using drumkit instruments with FX on (see this «bug» thread). I’d love to see it to be capable of putting notes to multiple note columns of a track. Otherwise it forces me to use not one balanced drumkit with FX chains, but multiple drum instruments (which is no-go for me personally).
I have made the new version 3.11 public, There was also another fix. Please refer to the first post:
https://forum.renoise.com/t/new-tool-3-0-step-sequencer-3/38153
…only thing left for me to suggest is to have page’s update, auto scroll in the tool while playing a song
@Djeroek: this is great
Nice feature request, will add it to my todo list. This should be then optional (to be set on/off).
Cool! Now that the updating of new pattern data on pattern change is improved even further, can you also add auto-updating of pages when playing a song? (when edit-step is 1 for example). Would be great
Cool! Now that the updating of new pattern data on pattern change is improved even further, can you also add auto-updating of pages when playing a song? (when edit-step is 1 for example). Would be great
I have created a new beta, this should include the new feature “autoscroll pages”. Please see first post.
https://forum.renoise.com/t/new-tool-3-0-step-sequencer-3/38153
It would be nice if you could test it…
It would be nice if you could test it…
Yo! Thanks for the option.
Been able to crash Renoise and have made a thread here;https://forum.renoise.com/t/lauflicht-tool-renoise-crash/42659
This is really cool, somehow didn’t give it a try before now and I love it! I’ve noticed something weird though, if you add more than one line of pattern fx in the control section you must manually expand the track/add columns with the + symbol for those extra patternfx to work. I suppose the obvious request would be to add the extra columns to the track automatically when you add some data to extra rows in the control section.
thanks for making this tool!! 
Hi all,
I bought a dead Launchpad from that auction site. It turned out that the PIC microcontroller had ceased to function, probably due to some tampering with the USB socket - it ran enough for me to scope the signals so I could work out how it clocked out the LED information, and clocked in the keys -well, kind of since all the original CPU at that point was doing was provide clocks. I used the Launchpad MIDI spec to write the code for my own replacement Atmel controller, andit works! Well, it works in Duplex since that allows me to assign aUSB midi port I/O, and all the keys work, and the LEDs light the correct colours.
Lauflicht doesn’t want to play though - I guesssince youuse the deviceIDs to find the Launchpads. Would it be divulging a huge secret to say what vendor and device IDs you look for when Lauflicht initialises to find connected Launchpads?
Running on Linux x64.
**Update: I think that the Linux driver for the original Launchpad, to make it a compliant USB MIDI device uses 1235 and 000e … I will have a go at copying those data and see what happens …
Lauflicht doesn’t want to play though - I guesssince youuse the deviceIDs to find the Launchpads. Would it be divulging a huge secret to say what vendor and device IDs you look for when Lauflicht initialises to find connected Launchpads?
Not at all 
I am usingrenoise.Midi.available_input_devices() to get a list of all available input devices, Renoise detects. Then I check if the list has an element which contains the string ‘Launchpad’ . As every Launchpad (S, Mini, Classic) uses this string as part of its midi name. Then I am creating an midi output device with the element that contained ‘Launchpad’ and sending midi messages to that device.
Ahah! I changed the product string to ‘Arcore Launchpad’ and it works. Actually it works so well that it’s uncovered a small bug - I found that my code for the replacement launchpad failed to interpret CC 0 0 as ‘clear LEDs’ … confused me for a while but all working now.
Thanks for the advice … might just have to rustle together some pocket money to buy it now !
Hi, does this tool supportsNOVATION Launchpad Mini MK2?
Hi, does this tool supportsNOVATION Launchpad Mini MK2?
Hi Akiz,
yes it should also work with the Launchpad Mini MK2
Yeah, i ve already bought it, great tool. + live dive
To be honest, is there any daw with similar Launchpad posibilities?
Yeah, i ve already bought it, great tool.
To be honest, is there any daw with similar Launchpad posibilities?
Great, thank you very much for your support!
To be honest, maybe there is one, but it is not a DAW that could compete with Renoise!
I have heard that Ableton Live has good Launchpad support, for me personally not an option.
Ive bought both Stepsequencer and Live dive
now the both tools are buggy
I understand that i cant use both tools together at the same time
but it seems that they cant be switched in proper way (without disabling the tool via tool browser),
there is problem with remapping.
Need support here, thank you :]
(Maybe somethign like “run” tickbox on bothtools like duplex has would help?)
What is the status of this tool as it doesn’t seem to be available anymore from the official site. Does it work with the latest Renoise version. Any advice is appreciated.
Any plans to update this for latest renoise?
1 Like
yeah a quick fix in the main lua would help…
“bad header”