im no coder,so i dont know how much is possible with the new scripting,but have been using the sampleslicer tool alot(thanks It-Alien)
but was wondering if it would be possible to have a visual of where the sample gets sliced
i have made a shitty picture where you can see what i mean
here it is,not very cosmetic beatifull i know,but hope you get the idea
the only way I can imagine this could be done as of now is by using the loop markers: a timer could be used to move the markers periodically to show the beginning and end of each slice. of course, the real loop markers info should be kept in order to restore it if the slicing does not get confirmed by the user.
do you think that such a solution would be helpful?
Yes. We can at least try it out if this will work or not.
yeah i think that would be nice,as Tom said we can atleast see how it works
ok, I took note of this and will give it a try as soon as possible
thats awesome,thanks
Great!
I guess this leads to a feature request for future versions of the scripting API to allow scripts to perform arbitrary drawing operations in the sample view.
+1, would be wicked to see whats being done, before doing it…
also, could we have the choice of the slices being in new instrument slots, instead of a keymapped 1 instrument per chop? i for one would appreciate being able to unravel loops with sampleslicer to new sampleslots…
Such a slicer would be great!
I need this , since I can’t export from renoise my turntable recorded wav’s into Recycle and am to lazy to chop something renoise manualy into 32 chops.
ps. the already developed tools are great!
Very nice job everybody and Renoise thank you for making scripting possible!
+1
moving the loop markers is possible; the only issue may be doing this with a timer. I didn’t look at it until now. I will try to do it soon
I have made a sketch of the visualization functionality, which seems to work fine. Unfortunately, there is a problem with modal dialogs (see here) so I had to turn this tool into a non-modal dialog; the code then needs more modifications in order to be crash-proof, so I will not publish it officially for now.
please check if it does fulfil your needs.
note: I have decided to use fake selection blocks in order to visualize the slices instead of loop markers. I think this solution is far better and, although the initial selection gets restored if no slicing is done when the dialog closes, it’s anyway more error-proof
when I run that, the selection moves back and forth a bit, then I get:
main.lua:436: ‘invalid selection range. end must be <= start.’
(btw I found it easiest to set start and end to 1 and number_of_frames respectively before setting a selection)
Changing from 4 slices to 16, I got:
[i]"Script ‘C:\Users\plugexpert\AppData\Roaming\Renoise\V2.6.0\Scripts\Tools\com.renoise.SampleSlicer.xrnx\main.lua’ failed in one of its notifiers. The notifier will be disabled to prevent further errors:
std::logic_error: ‘invalid selection range. end must be <= start.’
stack traceback:
[C]: ?
[C]: in function ‘__newindex’
[string “do…”]:22: in function <[string “do…”]:11>
main.lua:436: in function main.lua:410"[/i]
yeah, thanks, already fixed it locally. also, I forgot to say that the mockup does not contain the “Slice” and “Cancel” buttons, but I guess you noticed it already 
also, changing slicing mode to BPM does not work.
apart from this, do you like the way it works?
I like that it visually runs through the sample and gives an indication of where the sample gets cut.
Oh, theres an error in the error message. Fixed 
yeah was wondering about that 
but i like the way it works now,its a good solution you found i think