Holy Crap!

GedaBlaq wrote:

JAH wrote:What 'many' of us do care is that it is a platform that is heavily supported by Akai/Numark. And more updates are pending/planned. I suspect the next 2 updates will excite 'many more' people.

16 Part Multi-Timbral + Midi Controller Mode = I'm Good.

That would be great.

Lampdog wrote:I'm reading all of this and it's been forever that PEOPLE need to be responsible for their own sample/program choices before anything else.
These dudes/girls need to stop loading arbitrary **** in the first place. Not to start any controversy but "drink responsibly" comes to mind. Meaning don't just load a million samples and expect any program to "know what you want". Take responsibility as well.

Well said! I don't really get the problem here. If you have a program that contains large wave files on each pad of each pad bank, then of course it will fill up your harddrive when you load this program in 60 beats. But if you take care of what you load in a program or what you need and you have 60 beats you are proud of, then surely you want all the samples in each project file! It's all a matter of organizing yourself which in my opinion no software can be made responsible.

acura wrote:

Lampdog wrote:I'm reading all of this and it's been forever that PEOPLE need to be responsible for their own sample/program choices before anything else.
These dudes/girls need to stop loading arbitrary **** in the first place. Not to start any controversy but "drink responsibly" comes to mind. Meaning don't just load a million samples and expect any program to "know what you want". Take responsibility as well.

Well said! I don't really get the problem here. If you have a program that contains large wave files on each pad of each pad bank, then of course it will fill up your harddrive when you load this program in 60 beats. But if you take care of what you load in a program or what you need and you have 60 beats you are proud of, then surely you want all the samples in each project file! It's all a matter of organizing yourself which in my opinion no software can be made responsible.

I'm with you on taking responsibility for your own samples but for me it's more about the principle of the matter, it's like if you bought a Bruce Lee movie (Enter the Dragon, for ex.) and then you wanted to buy another Bruce Lee movie but you can only find it sold in a combo pack that also contains the first Bruce Lee movie, now you have 2 copies of Enter the Dragon, you can afford it but you don't necessarily want 2 copies of the same thing.
I think the best solution would be to give us the option to do it either way.

I think everyone should have 2 copies of Enter the Dragon

peteblues wrote:I think everyone should have 2 copies of Enter the Dragon

Yeah I guess that was a bad example because I do have 2 copies.

if you push purge with the mpc60 vintage mode turned on.. it should delete everything beyond 26 seconds from the project

DJ Hellfire wrote:

JAH wrote:

DJ Hellfire wrote:

The issue here is that when a sound is assigned to a program, it's considered used by the MPC. This isn't something new to the Ren. This has always been the case with MPCs. So I guess what we need to be asking for is for the Ren to be able to purge sounds from a program that are not used in any sequence.

Should there be a Purge command to delete unused Programs?

I don't think it's necessary. Currently you can just delete the program and purge to get rid of all the sounds for that program. This that you are suggesting would do both in one step, but probably not really pertinent.

Note that the MPC 4000 has a 'Delete All Programs', 'Purge Unused Programs', and 'Delete Tagged Program' commands. I am kinda partial to adding

Jonespnice1 wrote:

peteblues wrote:We're looking into the option of saving the samples or leaving them at the original location. If we do that, we can't purge samples from the file system, because there's no way of knowing whether or not a different project might need them.

I don't know how difficult it is to implement a system that doesn't duplicate samples (so excuse my ignorance) but I'm with InspectahEX on this one, I really hate the fact that I have a bunch of samples duplicated multiple times. Lately I've found myself either using kontakt, Battery, or Maschine (as a plugin) inside of the Ren (for my samples) just so I don't have to have several duplicate samples.

I think there should be 2 options:

1. An option to save self-contained projects with samples as currently implemented

2. Library system like Kontakt, Battery, etc where files are not duplicated...where if you move the library or something gets deleted from the library by accident, your projects won't load properly.

peteblues wrote:
We're looking into the option of saving the samples or leaving them at the original location. If we do that, we can't purge samples from the file system, because there's no way of knowing whether or not a different project might need them.

I think this is really the only simple way to go for guys that like to load a lot of kits and don't want them all duplicated. For me, I'll be sticking to the current method of saving as I don't want any missing samples breaking multiple projects.

One thing I do think is needed though is the ability to save projects without samples. This way I can have different versions of a project that all reference the same samples folder. So I can, for example, have 3 different mixes of the same project without having to save the samples for each different project version.

DJ Hellfire wrote:

peteblues wrote:
We're looking into the option of saving the samples or leaving them at the original location. If we do that, we can't purge samples from the file system, because there's no way of knowing whether or not a different project might need them.

I think this is really the only simple way to go for guys that like to load a lot of kits and don't want them all duplicated. For me, I'll be sticking to the current method of saving as I don't want any missing samples breaking multiple projects.

One thing I do think is needed though is the ability to save projects without samples. This way I can have different versions of a project that all reference the same samples folder. So I can, for example, have 3 different mixes of the same project without having to save the samples for each different project version.

that's what I meant with option of saving the samples

peteblues wrote:

DJ Hellfire wrote:

peteblues wrote:
We're looking into the option of saving the samples or leaving them at the original location. If we do that, we can't purge samples from the file system, because there's no way of knowing whether or not a different project might need them.

I think this is really the only simple way to go for guys that like to load a lot of kits and don't want them all duplicated. For me, I'll be sticking to the current method of saving as I don't want any missing samples breaking multiple projects.

One thing I do think is needed though is the ability to save projects without samples. This way I can have different versions of a project that all reference the same samples folder. So I can, for example, have 3 different mixes of the same project without having to save the samples for each different project version.

that's what I meant with option of saving the samples

Yeah, true! I didn't realize the feature would serve more than one purpose.

I like current way as i am used to it and I understand why it's so.

Yes it could save a config file that points to the original sample in some other location, but someone gonna edit, move, or delete the original file(s) and complain that all their songs are broken.

Will this work to save space when you often use the same sample(s), kit(s) and such... Instead of always creating a new folder for every project/song, create 1 project/song folder and dump new songs there (dif project names of course) and choose not to overwrite samples of same name.

I can't be only one that remembers waiting 3-4 minutes and writing saves to 2-5 floppy disks for 1 song back in the day. It forced creative saving and sampling such as using almost too tiny samples at 'double speed' and no stereo files.

I understand both sides but I will take the space hit cause I like organization and disk space is much cheaper and more abundant than many of us remember.

MPCTNT wrote:Will this work to save space when you often use the same sample(s), kit(s) and such... Instead of always creating a new folder for every project/song, create 1 project/song folder and dump new songs there (dif project names of course) and choose not to overwrite samples of same name.

Can you explain what you mean here? Because I don't think that method works to save space. If you save all your projects to one folder, it will still create a project file with a dedicated folder full of content specific to that project file.

JAH wrote:

MPCTNT wrote:Will this work to save space when you often use the same sample(s), kit(s) and such... Instead of always creating a new folder for every project/song, create 1 project/song folder and dump new songs there (dif project names of course) and choose not to overwrite samples of same name.

Can you explain what you mean here? Because I don't think that method works to save space. If you save all your projects to one folder, it will still create a project file with a dedicated folder full of content specific to that project file.

Sorry JAH. You know I am getting my Ren but I am not sure how file saves work. Going by 5k. When you go into a folder to "save entire", you haev option to create new folder or not. If you dont, all files get dumped in root of current location. you can save multiple song to same location/directory. If they share same files, they will only be there once....

I sitting beside me 5K now, let me verify that. (I always create new folders so want to make sure) I have 1.5TB drive in my 5k and when I move to ren I will have a couple 2TB drives in the desktop I'm going to build and can always add external storage, where where I cannot currently

JAH wrote:

MPCTNT wrote:Will this work to save space when you often use the same sample(s), kit(s) and such... Instead of always creating a new folder for every project/song, create 1 project/song folder and dump new songs there (dif project names of course) and choose not to overwrite samples of same name.

Can you explain what you mean here? Because I don't think that method works to save space. If you save all your projects to one folder, it will still create a project file with a dedicated folder full of content specific to that project file.

Jah, he's talking about the same thing I mentioned on page 2:

DJ Hellfire wrote:If a Ren user didn't want duplicate sounds, one can simply just save all projects and samples in a single folder. That way, you'll have all your different projects in the folder that all reference the same sounds in that same folder. And there would be no duplicates of samples!