This is uber-big!
Useful to me beyond explanation.
thanks man, really!
tL.
Got this error;
‘C:\Users\plugexpert\AppData\Roaming\Renoise\V3.0.1\Scripts\Tools\com.afta8.RenderAndSlice.xrnx\main.lua’ failed in one of its notifiers.
Please contact the author (afta8 | fathand@gmail.com ) for assistance…
main.lua:150: attempt to index field ‘?’ (a nil value)
stack traceback:
main.lua:150: in function ‘write_notes’
main.lua:252: in function ‘notes_to_slices’
main.lua:334: in function main.lua:292
trying to render a track with 2 command rows, 120 line pattern length, though it rendered without problems before in the same song. There is a rendered sample result, but it isn’t sliced and put in a the render & slice track.
If I delete the (previously created) render & slice track and try again, it does render & slice correctly without this error notice appearing.
… I wanted to say that i´ve needed this for a long time and i thank you so much but then i´ve realized that it doesnt work for matrix editor but pattern editor. But it is still cool 
Thank you!
Updated to v0.7
Added option to create phrases from pattern data, see the tools menu to make the setting (on by default)
With this option set, the rendering and slicing will happen as usual, however for each note where a slice would usually be triggered it will trigger a phrase which starts with that slice note but then goes on to play the rest of the pattern data from there.
I could explain it better but just try it out and look at the phrase data and this will make more sense.
See first post for the file.
very interesting tool & nice demo. will def try this out somehow
Updated to v0.7
this tool is so good! 
…can’t wait for the new Renoise to drop so my disneyland magic feature request can make it inside the tool. An option to render and replace the source selection, automatically muting used dsp track fx for the duration of the selection so it’ll be a seamless transition from original to bounced. Afaik currently not really possible without workaround hacks, not having the active/bypassed parameter available to control through lua,
It seems i never need to worry about tools and features because afta8 has already made a tool for it. 
I have a suggestion to make this even more useful (or maybe for another tool): When i autoslice a sample the beats are all over the place and it’s hopelessly tedious to try and fit those slices into a pattern. If there was a function that distributes the already sliced sample to a pattern so that it plays like the original, it would be a lot more convenient.
If there was a function that distributes the already sliced sample to a pattern so that it plays like the original
Check out my Slices to Pattern tool. Link in my sig below.
Check out my Slices to Pattern tool. Link in my sig below.
Great!
I actually already had a like on your tool, but i must have forgotten about it.
Thanks dblue!
@afta8: you are the boss. Thank you so much for all of the awesome tools and functionality you add to an already great program!!!
Thanks @hexeye; your comment has made day 
This one isn’t auto updated correctly in 3.1 because of changes under the hood I guess, but you can manually update the manifest to 5 in the scripting terminal to get it working somewhat.
Although I get a result using the tool, the terminal gives the following notice;
*** std::runtime_error: ‘internal error. failed to resolve a phrase mapping for a phrase.’
*** stack traceback:
*** [C]: ?
*** [C]: in function ‘__index’
*** [string “do…”]:37: in function <[string “do…”]:35>
*** main.lua:215: in function ‘notes_to_slices’
*** main.lua:334: in function main.lua:292
Would be great to have this tool in full effect for 3.1 
, even better after some pimping now that this is addressed;https://forum.renoise.com/t/how-to-write-device-active-bypass-state-to-automation/43116 ? 
For now, disable the ‘Write phrases to instrument’ setting in the tools menu, this will stop the error message coming up. The way phrases are done seems to have been overhauled so need to get my head around all that, maybe change the way it is done given new features etc…
And yes extra pimping is also on the cards
really interesting, great way of getting deeper and deeper in the resampling… thank you!
hope the write to phrases functino will come up and running in 3.x soon : )
I’ve been thinking about this excellent tool and how I often use it along side some others such as the ‘easy tune’ and the slices to Midi tool.
I wonder if it would be possible to have the tool analyse the fundamental of a given slice, tune it to C and, when putting it in place on the pattern, assign the correct note to the slice.
Maybe it could also autoloop the slices (like a ReCycle kind of thing) and build a multisampled instrument as an option.
I imagine this working with material that is originally an imported loop as well.
So basically you’d start with a loop from a library or wherever but end up with a carbon copy of the loop in place with all its slices broken out and represented as the correct notes for the original pitch, but each of them would now be a sustaining instrument in its own right.
Packaging all of this into a parent instrument would be essential to keep the number of instrument slots used rational
Would need to be optional for percussion stuff where it’s maybe less useful.
I think this would be an allmighty tool not just for freezing VSTi but also reworking prerecorded loops. A bit like Melodyne (but not quite, of course).
Great tool!
1 Like
Is there a version of this that works for 3.1 ? or an alternate tool that provides this functionality?
Maybe just a tiny modification is needed? But shhhhh don’t tell anyone 
where is the tool?
not it, but you could try this. seems like comparable functionality?
1 Like