marlon brando

I have saved my max patch using "build collective" option and used the "include folder" option in the collective editor.

I can see in my max folder that the pat.build.mxf is now over 15000 KB, so I guess that means that some audio is stored within the patch, (which is good!)

But when im opening the patch, it is silent when the play~ objects that referrs to the samples is triggered.

how-to-include-samples-in-patchcollective

You're not searching the list/forum archives or doing the tutorials, before you ask questions, that's what...

Im doing the tutorials, but this is by far the most complicated music software I have ever used,

I would be very happy if you could help me out,

C`mon, man,
Im doing the tutorials, but this is by far the most complicated music software I have ever used,
I would be very happy if you could help me out,

Is it convenient to save all my patches im working on as collectives?

I really like the idea of my audiofiles being stored within the patch!

Is it convenient to save all my patches im working on as collectives?
I really like the idea of my audiofiles being stored within the patch!

Do any of you save all your work in progress as collectives?

I doubt anyone does. Collectives are mostly useful for giving someone 

a project, or putting it in an installation, or some situation where 

you need to be 100% sure all your bits are in place. Mostly seems 

On Sep 4, 2008, at 3:36, marlon brando wrote:

> Do any of you save all your work in progress as collectives?

I doubt anyone does.  Collectives are mostly useful for giving someone  
a project, or putting it in an installation, or some situation where  
you need to be 100% sure all your bits are in place.  Mostly seems  
like a waste of time to me.

>
> Do any of you save all your work in progress as collectives?
>
>
> Cheers & thanks for helping me out !


On 4 sept. 08, at 09:36, marlon brando wrote:

I don't. Collective are usefull to put all the externals (even the 3rd 

parties one) and patches you need in one single file you can move 

around and give to friends without having to worry about their setup.

Centre de Recherches et de Formation Musicales de Wallonie asbl

>
> Do any of you save all your work in progress as collectives?

I don't. Collective are usefull to put all the externals (even the 3rd  
parties one) and patches you need in one single file you can move  
around and give to friends without having to worry about their setup.

_____________________________
Patrick Delges

Centre de Recherches et de Formation Musicales de Wallonie asbl
http://www.crfmw.be/max


but some situation where I need to be 100% sure all my bits are in place, is when Im organizing my folders, taking backups to external hardrives, moving between my to computers etc.

I have fucked up a hundred times with other programs with this and get "missing samples" to my projects.

That is why I want to build collectives instead of patches.

They tend to grow big, as all audio is included, but I have hard drive space enough to handle this I think

That is why I want to build collectives instead of patches.
They tend to grow big, as all audio is included, but I have hard drive space enough to handle this I think

A Max collective .mxf isn't directly editable once compiled which doesn't really make it suitable for storing your patches in.

For all my max patches I have a folder called Max Patches (inventive huh? ;)) and then for each individual project I have a separate folder within that. I also have a central repository for samples on my hard drive but when I use them in max patches I tend to copy them to that project's folder. Hard disk space being so cheap these days it's not really an issue.

And of course, the most important thing OF ALL! In each project folder I have a backups folder and every time I make a significant change to a patch I save a backup copy, dated and numbered in that folder. Never good to have 1 broken copy of a patch and no idea what broke it.

I know this might seem logical but they're all little things I learnt to do when I was starting out that I'm certain everyone else here had to learn too. It's the sort of thing you can't find in the manual.

(and by the way, to include samples in a collective, either put them in a folder and select add folder when you're writing your build script or add each file individually at the same time).

> I have fucked up a hundred times with other programs with this and

I do it this way, create a path relative to the patch/collective and 

marlon brando schrieb:
> I have fucked up a hundred times with other programs with this and
> get "missing samples" to my projects.

I do it this way, create a path relative to the patch/collective and 
then load each bit into the buffer~:

-- 
Stefan Tiedje------------x-------
--_____-----------|--------------
--(_|_ ----|-----|-----()-------
-- _|_)----|-----()--------------
----------()--------www.ccmix.com


How to include samples in patch/collective ?