Retrigger behaviour at high LPB?

I like to use the retrigger command a lot for creating granular/glitch sounding drums. I find it works great at low-to-mid LPB around 4 to 8. The retrigger lasts for a nice amount of time, not stopping too early or lasting too long. But once these setting start to increase the command doesn’t seem to be of much use anymore. The length of the retrigger is often too fast to be noticeable, or has no effect. I work with pattern lengths of 192 and a LPB of 24 because I prefer high resolution for subdividing beats, and so I presume the change of behaviour has to do with the increased resolution?

Is it that the trigger get cut off sooner because it only lasts for 1/24 of the a quarter note beat, rather than 1/4 of a quarter beat?

Is there any way to make the retrigger behave the same way at 24 LPB, as it does at 4 LPB?

i looked a bit at it with my non-existent knowledge and didn’t find anything, but my answer would be that in such a resolution you should be able to get the same effect by simply creating notes ?

I think retrigger commands are linked with tpl (=ticks per line)

  • Ticks Per Line: Changes the internal event rate for Renoise, stating how many ticks make up a horizontal line in thePattern Editor. This applies to Sample Effects like re-triggers or volume gates, and also to meta devices like the LFO device, which will use this to determine how often values are updated. This rate also affects automation interpolation, i.e. how often line values are smoothed for playback. In general, the default value of 12 is just fine and makes musical sense (it is divisible by 2, 3 and 4). If you need even higher resolution, you could try a value of 16. Lower values may make your sounds and automation a bit more “rough”, which could be useful if that’s what you’re after. To adjust the Ticks Per Line as the song is playing, you can use theEffect CommandZKxx, wherexxis the new TPL in hexadecimal. This can also beAutomatedon theMaster Track.

http://tutorials.renoise.com/wiki/Song_Settings

You could try altering the tpl using the above mentioned pattern commands and see if you can get more juice out of yer retriggers at high bpm/lpb values. But like you mention at those settings you can simply program the retriggers inserting note events.

i looked a bit at it with my non-existent knowledge and didn’t find anything, but my answer would be that in such a resolution you should be able to get the same effect by simply creating notes ?

Yeah I do often stack notes on top of each other to get the same effect, and use it in conjunction with Uxx or Dxx command to alter the pitch. It’s just retriggering seems to give of a sharper, smoother pitch than stacking. In that file I uploaded if I use retrigger of R11 on the hats at a 4 LPB setting it gives off very sharp smooth pitch, but when I try to replicate it at 24 LPB using stacked notes with UF0 the result isn’t the same. It’s actually lower, it’s seems like because the notes are triggering faster due to the UF0 command that a brief silence gets introduced to between the notes, whereas with the retrigger that doesn’t seem to happen.

You could try altering the tpl using the above mentioned pattern commands and see if you can get more juice out of yer retriggers at high bpm/lpb values. But like you mention at those settings you can simply program the retriggers inserting note events.

Ah ok, I didn’t actually know about this. I’ll try test it out and see. Thanks Danoise.

I’m kinda abandoning the idea of the retrigger command now anyway. I was relying on it too much for mangling drum sounds. I’ve been mangling em all up manually now with processing, and chop/copy/paste method instead of being a lazy sh*t and using the retrigger all the time. More controlled.

Thanks for the replies anyway lads.

Much appreciated :slight_smile:

Thanks Danoise.

I’m all over the place on this forum, but this time it’s undeserved :slight_smile:

I’m all over the place on this forum, but this time it’s undeserved :slight_smile:

Crap :lol: What is wrong with me today. Im so unfocused. Too little sleep & too much coffee. Thank you Djeroek :), apologies for the name mistake haha