Rahm

There are a few threads about maxpat vs amxd and how to navigate between the two. (The consensus is that a simple copy/paste is the best way.)

But before I move forward with a kind of hefty patching project I just want to make sure there's no better way to organize my workflow. I ultimately want to be able to run my patch BOTH in standalone Max and also in Live. But it seems laborious and organizationally chaotic to make and save a new amxd every time I want to try the new version of my patch in Live.

Does anyone have advice about how to navigate version control and file organization in this situation?

I've never used github before, but maybe something like that would be worthwhile for me?

There are a few threads about maxpat vs amxd and how to navigate between the two. (The consensus is that a simple copy/paste is the best way.) 

But before I move forward with a kind of hefty patching project I just want to make sure there's no better way to organize my workflow. I ultimately want to be able to run my patch BOTH in standalone Max and also in Live. But it seems laborious and organizationally chaotic to make and save a new amxd every time I want to try the new version of my patch in Live. 

Does anyone have advice about how to navigate version control and file organization in this situation?  

Ahoy.
There are a few threads about maxpat vs amxd and how to navigate between the two. (The consensus is that a simple copy/paste is the be

maxpat-and-amxd-workflow

..maybe all your amxd and your standalone can be "mainly" the same bpatcher both linked to the same maxpat. All the differences between the standalone and the amxd could be in the patch/device outside the shared bpatcher.

If the maxpat in both versions has the same name. It can be a solution. 

Just an idea..
..maybe all your amxd and your standalone can be "mainly"  the same bpatcher both linked to the same maxpat. All the differences between the standalone and the amxd could be in the patch/device outside the shared bpatcher. 

If the maxpat in both versions has the same name. It can be a solution. 


Just inset the patch into the amxd as a bpatcher. That's what you mean right?

Though of course I like to make different version names, so that would mean I'd have to continually update the file referenced in the amxd's bpatcher.

Is it common practice to save an updated patch with the same file name just so that you don't have to update bpatchers that reference it?

Just inset the patch into the amxd as a bpatcher. That's what you mean right? 

Though of course I like to make different version names, so that would mean I'd have to continually update the file referenced in the amxd's bpatcher. 

maxpat and amxd workflow