Purging or discarding unused samples?

I've been making drum programs on the Ren and I'll load up a whole folder of kick drums (for example) and scan through them until I find the right one. Once I'm done I'm left with a ton of samples I'm not using, is there any quick way to get rid of these?

Nope!

DJ Hellfire wrote:Nope!

So you're saying there's a chance!?!?

Hopefully they add that feature sometime soon... did they have this in the older MPC's?

Am i right in thinking that when you save it doesnt save the items that are not on the pads?

Airyck wrote:

DJ Hellfire wrote:Nope!

So you're saying there's a chance!?!?

Hopefully they add that feature sometime soon... did they have this in the older MPC's?

Yes, this is a feature available on older MPCs

Don Blake wrote:Am i right in thinking that when you save it doesnt save the items that are not on the pads?

It saves all samples, even samples not on pads.

IMAKEMADBEATS wrote:
It saves all samples, even samples not on pads.

And you cant purge.... Wtf lol.

Damn, well I guess I'm done working that way... I'll run out of hard drive space in no time.

and don't forget that it doesn't actually "slice" the samples either... it simply makes multiple copies of the same audio file with different start/end points for each "slice"... so if you chop a sample into 32 parts, it'll have 32 copies of that same full-length sample when you save it... another kick in the hard drive right there.

crossings wrote:and don't forget that it doesn't actually "slice" the samples either... it simply makes multiple copies of the same audio file with different start/end points for each "slice"... so if you chop a sample into 32 parts, it'll have 32 copies of that same full-length sample when you save it... another kick in the hard drive right there.

This is not true at all.
There is a 'Crop' param that is checked by default that creates programs with slices (not the entire sample) like seen on most products that slice to include hardware MPCs. If you uncheck the 'Crop' param than that creates 32 copes of the full-length sample but retains the slice start/end points.

RTFM.

But I certainly co-sign needing a purge command. It is very useful.

So unless the user goes the "destructive" route the result is multiple copies as Hellfire has shown.

moyphee wrote:So unless the user goes the "destructive" route the result is multiple copies as Hellfire has shown.

Yes, non-destructive for some reason creates a full length copy of the original sample for each region you specify in the chop screen. 32 chops = 32 full length copies.

I assume each of these copies contains the meta data markers for just a single chop. JJOSXL simply adds the markers for all 32 chops to the one original sample.

I'm a bit stumped on this one, it would actually seem easier to do it the JJOS way, which I assume is simply a progression of the way a patched phrase file is 'meta-marked' for the individual regions. I'm sure there's a technical reason why they chose this, but I am not aware of it. Maybe Dan Gill can chip in on this one?

moyphee wrote:So unless the user goes the "destructive" route the result is multiple copies as Hellfire has shown.

MPC-Tutor wrote:

moyphee wrote:So unless the user goes the "destructive" route the result is multiple copies as Hellfire has shown.

1. I assume each of these copies contains the meta data markers for just a single chop.

2. JJOSXL simply adds the markers for all 32 chops to the one original sample.

3. I'm sure there's a technical reason why they chose this, but I am not aware of it.

1. Yup, all the start/end markers you set for each chop is there, but beyond those markers is the entire rest of the sample.

2. Maschine does it this way as well! Only con I notice in Maschine is that you cannot use different plugins for each slice, nor can you use different amp envelope or any program editing features separately for each slice. The only thing you can do for each slice individual really gain, attack, decay, and tuning.

3. On the MPC, while it creates a bunch of duplicates of the entire sample, there is more editing flexibility for editing each slice individually. So maybe that was Akai's reasoning for doing it this way.


Maschine's disadvantage doesn't bother me for the way I work, although a few people have complained about it. If I really need a different program edit feature for a slice or two (which I never do), I can simply make a few copies of that pad. This way, on a track where I chopped something into more than 100 pieces, I'll only have a few copies of the entire sample instead of over 100 copies! So this method is definitely preferred!

DJ Hellfire wrote:

MPC-Tutor wrote:

moyphee wrote:So unless the user goes the "destructive" route the result is multiple copies as Hellfire has shown.

1. I assume each of these copies contains the meta data markers for just a single chop.

2. JJOSXL simply adds the markers for all 32 chops to the one original sample.

3. I'm sure there's a technical reason why they chose this, but I am not aware of it.

1. Yup, all the start/end markers you set for each chop is there, but beyond those markers is the entire rest of the sample.

2. Maschine does it this way as well! Only con I notice in Maschine is that you cannot use different plugins for each slice, nor can you use different amp envelope or any program editing features separately for each slice. The only thing you can do for each slice individual really gain, attack, decay, and tuning.

3. On the MPC, while it creates a bunch of duplicates of the entire sample, there is more editing flexibility for editing each slice individually. So maybe that was Akai's reasoning for doing it this way.


Maschine's disadvantage doesn't bother me for the way I work, although a few people have complained about it. If I really need a different program edit feature for a slice or two (which I never do), I can simply make a few copies of that pad. This way, on a track where I chopped something into more than 100 pieces, I'll only have a few copies of the entire sample instead of over 100 copies! So this method is definitely preferred!

1. Why is this a problem? Memory can't be an argument as the Ren has approx 8x more memory than the MPC 4000....30x more memory than the MPC 1000/2500...and 125x more memory than the MPC 3000/2000XL.

2. I see this as a huge disadvantage with Maschine. Why would anyone want to use this when you can't have complete control over your sounds. The JJ OS doesn't have this limitation.

3. Editing flexibility is a plus and its virtually impossible to run out of memory as it has significantly more memory than any MPC or hardware sampler.

Few people complained about Maschine's disadvantage? I would say even fewer people actually use 100 slices that would negatively impact their project size or efficiency the way they work. Or everybody would be using MPCs running the JJ OS which isn't the case.

What is the argument for the implementation of nondestructive chop versus the current implementation of the 'Crop On/Off' function in the Ren? There is nothing too creative about using hundreds of slices where a DJ Premiere (one of the architects of slicing) uses less than 32 slices as that is all an MPC 60 can hold in its memory.

We need some compelling reasons on why Akai should add this function? My only reason is because XX product has it.

Ensoniq ASR-10 (1992 on)/ ASR-X (1997 on).

Sorry to interrupt...