Emergency collective mxf editing
My computer was recently stolen, along with all of the max patches I am using for a museum installation…
However, compiled collectives of all the programs are still extant in .exe and .mxf format. I understand that .mxf is supposed to encrypt the program files so that they can’t be edited and copied, but at this point that’s all I have…
Has anyone been able to successfully extract usable files from the .mxf that can help me out? This project depends on it and my deadline is looming… I understand it’s somewhat dodgy subject matter so if need be please contact me at firstname.lastname@example.org .
I offer payment or kudos or yoga lessons or anything. Without these files my work and this children’s museum are profoundly screwed…
Thanks so much!
On 21 Aug 2008, at 19:23, Noah Keating wrote:
> I understand that .mxf is supposed to encrypt the program files so
> that they can’t be edited and copied, but at this point that’s all I
I don’t think anyone’s ever claimed that collectives are encrypted,
although the format isn’t documented.
If you’re not using any custom externals that you want to extract, and
if your patcher files were in text format (such as JSON in Max 5) then
you could hack the patchers out with something like EMACS.
Nick Rothwell / Cassiel.com Limited
I can open the files in BBedit but what comes through is mostly garbage. There is one section that reads like clean patcher text but when pasted into a new patcher, only brings up one of my externals. I didn’t compile the files as text, I used the command "build collective."
How would you go about "hacking the patcher out"?