I hadn’t thought of that… because I’m that type of geek who likes to have an instrument for every sample, the theory being the maximum tweaking of each sound.
But I think it’s possible to assume that it’s the current instrument and the sample that was triggered already in the track… because other pattern effects get by without an explicit declaration of the current sample in a multi-sample instrument- the values are in memory already. The problem could be that the engine currently doesn’t store those values in a place where pattern effects can peek while they are executing. Yet. renoise must become self-aware …
I’m dreaming here.
the 256 value thing can be overcome by defining a position ‘glide’ instead of a fixed position. the effect i’m thinking of isn’t interesting unless the loop point is moving and besides, the user already has precise control over loop points if they are to remain the same.
so i was thinking maybe add to the B’s:
0B02 - current sample loop off
0B03 - current sample forward loop on
0B04 - current sample reverse loop on
0B05 - current sample ping-pong loop on
0Lxy for the current sample loop start point
0Qxy for the current sample loop end point (or something)
x0 - restore saved loop positions / loop type
x1 - save loop positions / loop type
x2 - forwards linear glide (y + y) samples in (direction) per tick
x3 - forwards exponential glide (y to the y) samples in (direction) per tick
x4 - forwards square root glide (y / y) samples in (direction) per tick
x5 - … your favorite math here
x6 - forwards linear glide (y + y) samples in (direction) per tick
x7 - forwards exponential glide (y to the y) samples in (direction) per tick
x8 - forwards square root glide (y / y) samples in (direction) per tick
x9 - … your favorite math here
y0 - 1
y1 - 2
y2 - 4
y3 - 8
y4 - 16
y5 - 32
y6 - 64
y7 - 128
y8 - 256
y9 - 512
…because the commands can be stacked 4 high in renoise, which rules the universe, it may be possible to save the user defined loop points, define a glide and begin modifying the loop all within one row. it should also be possible to stop and restore the old info on one row.
and as a catch-all, i propose that if another sample in that track begins playback, all loop-gliding operations should cease… in case they haven’t already been properly stopped by some other condition.
sorry to keep using the word ‘glide’ … there has got to be a better word for this meme…
Renoise rocks! and i’m happy with 09xx and the b’s and the bonus effects columns and of course 0Exx … for now I especially like draw mode in Renoise 1.9.1 for linux, it reminds me of the softsynth in aegis sonix… an ancient sound app for the Amiga…