Modular software & programmingMaxMSP, Reaktor, Pure Data, Jeskola BUZZ, and other modular programs. Any questions relating to these programs (patching, favorite ensembles) should be posted in this forum.
can this be used under puredata? if so, how can one lay his hands on the original patch? if thats nonsense from a programmers view on things - (because it only works in max, because the patches are no files, whatever), dont be too harsh, i have no clue about max. but i would like to USE it^^
Before using Max/Msp i just geek around with reaktor tweaking other's ensemble
I created one or 2 ensembles but mainly using other's user macros etc
I began using Max on january and after 6-7 days i came up with the slicer!
I really like the straight forward approach of Max and his apparent rawness
The slicer! is still a work in progress though so i think i'm going to share it on a final stage
The feature you do not see on the video is the ability to record the buffer in realtime in sync with the sequencer
this means that it's possible to play from an external instrument and have the buffer recorded and sliced retriged gated etc etc according to prepared presets :-)
on the way to be added also:
- ability to record the result on 8 separate audio track (1 track each slice)
- a synced multifx (created by a friend of mine)
- maybe another buffer cell to record in but we will see
actually before this patch i've learned the use of various object like buffer~ tempo multislider and waveform~
after these basic knowledge i just tried to put them together and see what happened
I know in some way it is similar to modsquad patch on the library but i did not start from there
I started from a feature of waveform~ object that detects the length of a file in the buffer
then i divided the length in 8 parts then rearranged via a multislider
that is the basic idea, from there i came up with 2 types of gate volume pitch and retrig
retrig has been one of the hard part because i made the loop end narrow in relation on how long the file is
so you can have the same behaviour of retrig on whatever buffer length
i don't see how shortening the loop end in relation to the file end would help out with retrig a all.
perhaps look at the [adsr~] object - it comes with a retrig function to prevent clicking in retrigger. perhaps you could assign each sample slice to a voice in poly~, then within the poly~ patch include an adsr~ object to allow for smooth retriggering?
the use of poly~ could also provide the interesting feature of being able to play the slices on top of each other. so, lets say you divide the sample into 16 different sections, but each section could be the length of two sections (or one and half, or 1/4 a section, etc. etc.)
actually with retrig in this case i mean when a sample is looped tight so you have fast triggering of little sample space
it's non properly a retrig but a circular loop whatever..
The reference to the file length in ms is really important to have the same effect with any length
let's say the multislider outputs values from 0 to 127 the loop end point goes from the end of the file to the start of the slice
to narrow the loop , it has to get close to the slice start. this distance (from start slice to end of file) is divided in the same way proportionally using values from 0 to 127
if i keep the retrig value in multislider let's say at 20 and i change the slice used i will listen the same rate of "retrig" no matter which slice i'm playing (the first is the longest the last is the shortest)
i hope it's a little clear
i'm going to have a look to poly~ and adsr~
anyway to smooth the retrig i used an envelope with line~ object that works ok for now
hey if you have any other suggestions, suggest! ;-))
canenero, i think i see what you're saying. you're just pretty much saying that you have to divide the sample up evenly so that your "retrig" (which is not really retriggering the sample, but just looping it) is of the same length no matter the sample you select.
anyways, if you want to see a different approach to sample slicing, here's my beatslicer:
pretty messy, but explore it if you want. i know how it can be kind of awkward trying to find your way around someone else's patch, but i think it might prove interesting to you. makes use of poly~ so that the sample slices can be layered over each other.