Experiment: Use Midi Knob To Set Loop Markers

[gstrob]

hi there, i hate to sound like a dope but im new to this renoise…i downloaded the looper and i understand the concept of moving the sliders(end point) around to glitch out the drum loop…but im abit lost on how to link it to the sliders/automation…the sliders move but ther not actually moving the end marker

@It-Alien

voilà,

with this script you will be able to use sliders (then tracking commands, automation or MIDI Control Changes) to modify the sample loop markers position on a sample.

looper script: Attachment 1452 not found.

example song: Attachment 1451 not found.

use the first two sliders of the MidiCcDevice in the master channel to set sample loop start and end.

in any existing song, you have to rename the instrument you want to control as “Looper” and the sample inside it as “Looper destination”. If a MidiCcDevice will not be present in the master track, it will be automatically created, otherwise the first found will be used. (Usually you don’t add any MidiCcDevice to the master track, so it should not be a problem)

[vvoois (vV)]

@gstrob

hi there, i hate to sound like a dope but im new to this renoise…i downloaded the looper and i understand the concept of moving the sliders(end point) around to glitch out the drum loop…but im abit lost on how to link it to the sliders/automation…the sliders move but ther not actually moving the end marker

The script has not been updated for 2.8 yet so yes the sliders move, but a device that has been renamed in the latest Renoise version is being altered.
It doesn’t fire an error, but it doesn’t do anything either.

[It-Alien]

the script has been updated to work in Renoise 2.8: download here

[pleasuretrail]

wow AWESOME!!

however I got this message while messing around with it

std::runtime_error: ‘notifier feedback loop detected. do not change values you are listening to within your notifiers.’
stack traceback:
[C]: ?
[C]: in function ‘__newindex’
[string “do…”]:22: in function <[string “do…”]:11>
main.lua:55: in function ‘set_loop_end’
main.lua:174: in function main.lua:173
[C]: ?
[C]: in function ‘__newindex’
[string “do…”]:22: in function <[string “do…”]:11>
main.lua:30: in function ‘set_loop_start’
main.lua:168: in function main.lua:167

[Morpion]

I’ve had that same message a couple of times too - I think it’s happening when the end point is automated so it ends up before the start point, but I’ve not looked into it in enough detail. (Renoise 2.8 64bit version, Mac 10.6.8.)

[midierror]

@It-Alien

example song: 3147 looper.xrns

It would be really good if this example song had a tooltip on opening to explain how to use it. Every time I want to use this tool I have to come back to the forum to find out how to do it

[dodz]

Just wanted to update that I’m using this in 3.1 and it’s working fine! Awesome!

[DarkCloudsEverywhere]

Is it possible to have 2 looper destinations or more? Love this btw, just discovered it, was really much needed!

[Mr_C (Psynapsex)]

Automating “Sample Start” out of the question since there is no actual start marker?

Can we automate slicer markers?

Real-time cross fading impossible???

[Neuro_No_Neuro]

@taktik This would be handy to have as part of the sampler’s modulation functions via LFO, or otherwise. Currently, this is a lot of work, but it’s exactly what I’ve been trying to construct via devices and failing

[andreaslingard]

Are ppl still using this script for this purpose? I am and it works great, but more than one looper destinattioin would be cool. Any update on this?