Samplist Unite and Be Heard :) We Need A Super Slicer

[SampleScience]

Here's a thought.....

Why not do it yourself Mr Bread?

Why expect everything you want handed to you on a plate... and for free?!!

If the libs you mention are so lacking, why not up the ante and present your own..... or are your abilities and ideas as stale as your monicker here?

<FX> ducks </FX>

Steve

He's not critisizing the libraries themselves, he's just questionning the way developers built their applications.

[stale bread]

WOW! Steve, for one I have always really liked your libraries, for two you have no idea what so ever of what i'm talking about or you would not have made that post.
obviously you have something against bread.

[Marco Raaphorst]

I still use ReCycle. Works great. rx2-files are cool, flexible and data-compressed. The best format for loops although time-stretching can be a little better sounding for sustained stuff of course.

[hollowsun]

WOW! Steve, for one I have always really liked your libraries, for two you have no idea what so ever of what i'm talking about or you would not have made that post.

Apologies... obviously grasped the wrong end of the stick. Comments retracted

obviously you have something against bread.

I only like it toasted


Steve

[Pantsdown666]

its become clear that the majority of people designing the slicers aren't folks who really understand 'the samplist' as a musician

heh...

i know you don't keyman_sam, and that is exactly my point. for you it would mean nothing, but for 'samplist
it would be a great feature for an already great app..

hmmmm ... got enough slicers, but where can I buy this ATTITUDE ??

[AllenPOPO]

at this point in time i think it could be easy to implement a "record audio input" option, but that may have problems in a sequencer environment made to do its own recording?

......well what i mean is, if your using cubase...just set up a template project that has audio tracks and use those to "record"....then point (guru,whatever) to these recorded files.....should be simple to set up with a little work....and i believe this is how most coders feel....that why make a vst plug that has recording of audio input designed to be used in....a sequence that ALREADY records audio input....

would like to see some thoughts on that

[stale bread]

why add audio recording 'in' because fo the sample and go work flow. it would stream line the process which is
what computer music applications are for imho. Guru is phenomenal, i just can't spend that much for a sampler that doesn't sample. and Guru is one of the best if not the best out there right now, its a vst and it works stand alone, why would i want to fire up my host/template, record audio and point Guru to where that audio is stored....when....i don't even need my host, i could just open up Guru and get to sampling, chopping, mangling, and playing/?

but in addition to audio rec, if i'm not mistaken Guru needs audio export as well.
something with the features of Guru, Liveslice, and Amg one, would just kill this market, who could resist it. so what do you think a great Slicer needs.

[stale bread]

crosspost from em411:

ejectorset wrote:

im not going to be bother with going to a different site for a discussion but heres what i want:
has to run on os x
have the ability to slice any subdivision and at any tempo.
ie. if i want my file in 17 same-size slices (each one 1/17th of the total file length) or if i want to say it is 133 bpm and i want 1/256 note slices

the big one - midi export with the ability to transpose all of the notes to be the same one.
i do this in bidule, but it would be much easier if recycle or something just had it built in.
let's say you have recorded something (anything) and you want to get just the rhythm (not audio) of it. if you end up with 31 slices, but you want to use that rhythm for just a snare, none of the slicers can do this to my knowledge

[stale bread]

I'd like to see:

slicing of any increments
no less slices than liveslice (256)
reads mp3, rex, ogg,wav,
independant fx for each slice
automatic/manual slice to midi mapping
slice audio export also simoultaneous audio export of multiple slices
export/import of midi files and groove templates
a basic destructive sample editor on a per slice basis with envelopes

[lawapa]

thanks lawapa, i own beatcreator v2, and its very nice but beatcreator doesn't read mp3s, or allow you to slice and map samples to midi notes and sequence them. plus its stand alone app

That sounds like Velocity In P5-2 What you want.

[Sascha Franck]

I wouldn't happen to know whether I'd ever need audio input capabilities, but something like drag and drop straight from your sequencer would be marvelleous. Apparently only possible with eXT. Something like that would be quite some instant gratification, which, I'm almost sure, is the reason people still want audio ins on samplers of all sorts.
However, here's a little "workaround" that I find to work incredibly fine on a whole number of occasions. It's totally obvious as well, yet I don't see much people working like that for whatever reasons:
Have Windows' explorer (or finder, should you be on a Mac) opened, go to the directory you're recording into with your host of choice. In your host, have the sampler/slicer opened. Record, go to explorer and the last file in the list will be what you just recorded, ready to be dragged onto your sampler. No need to search for filenames or whatever. Of course, your sampler has to support drag and drop.Works best with dual monitors.
Yeah, as said, incredibly obvious, but then, I simply don't see many people working like that.

Anyways, what I'm missing the most from the current bunch of slicers is a sensible combination of a great slicing engine (like ReCycle, which IMO is still the best, especially due to it being sizeable) and a drum sampler.
What I'm doing a lot is slicing some stuff, then throwing the slices onto my drum sampler of choice (usually Battery as it allows for manipulation of multiple cells at once, but DR-008 comes in closely second) to replace and manipulate them more thoroughly than any slicer allows for.
This is working rather fine with ReCycle, Phatmatik and MicroDicer along with a proper drumsampler.
But there's several drawbacks, the main thing being that once you find out you need to change something in the "source slicing", you gotta redo it all from the scratch.
In addition, none of the VST slicers allows for even halfway as great slicing control as ReCycle - and the latter won't work in realtime.
So it's a matter of endless app-switching, re-slicing, re-dragging/dropping and finally (annoying as well) re-saving.

GURU is coming pretty close to the idea of combining a slicer and a drum machine, but unfortunately the slicing isn't too hot at all - no manual control and such.
And, for whatever it might be worth, it's got no audio in either (which, btw, should be tough to get realized on a VSTi...).

I wrote down all these ideas quite a long while ago, no need to repeat it all:
http://www.kvraudio.com/forum/viewtopic ... highlight=

[stale bread]

thanks for chiming in sascha, i was hopin you'd drop some science

[OzoneJunkie]

Don't know if these were mentioned:

1. Ability to have overlapping slices. Some slicers: if you have a slice starting at 0:000 and ending at 0:100, then you can't have any additional slices within that time frame

2. Automatation for: start/stop points of the slice, as well as loop type. Allows for tracker style edits...

[Sascha Franck]

1. Ability to have overlapping slices. Some slicers: if you have a slice starting at 0:000 and ending at 0:100, then you can't have any additional slices within that time frame

2. Automatation for: start/stop points of the slice, as well as loop type. Allows for tracker style edits...

Both these issues could be adressed easily in case a drum sampler of some sorts would be implemeted in addition. With those overlapping "slices" (which would then become "pads", "zones" or "cells") would be no deal at all and automating start/end points is allready possible with some samplers as well.

And fwiw, here's another suggestion:
In case you don't need MIDI export/mapping, the plugin in question shouldn't be limited to 127 slices only. Especially important when doing things such as stutter effects, for which the maximum number of slices could easily exceed 127.

Along with that, there should be a mode which Intakt and MicroDicer (not sure about the latter, but I think so) already allow for: "one shot" loops, meaning that the complete "loop" (or whatever you desire) would be triggered by a single keystroke without wasting zones and MIDI keys.
That way you could theoretically map 127 sliced loops all throughout your keyboard range.
In addition, start points of those loops should be controllable via MIDI CCs, so you wouldn't have to trigger the loop all the way from the start each time you press a key.

And of course, anything heading into the "granular" direction would be welcomed as well, but with a proper loop/slice start/end point modulation these things should be no big deals either.

Brrr... I don't even want to remotely think about the endless possibilities of such a thing, if implemented properly.

[AKJ]

thanks lawapa, i own beatcreator v2, and its very nice but beatcreator doesn't read mp3s, or allow you to slice and map samples to midi notes and sequence them. plus its stand alone app

export to midi/sf2 and load it sf2 into your sampler.