phineus

Simple question, hopefully simple answer:

I save my Max patch as .mxb and post it. Now someone downloads it to a Mac and it won't open. This is a collaborative project and so this really needs to not happen. Any suggestions appreciated!

I save my Max patch as .mxb and post it.  Now someone downloads it to a Mac and it won't open.  This is a collaborative project and so this really needs to not happen.  Any suggestions appreciated!

cant-open-mxb-saved-on-xp-on-a-mac

You might try zipping the file before sending it, or how about just copy/paste the whole patch into your email to your collaborator (like when poeple post patches here)?

I have been sending .pat versions embedded in e-mails so people can work on Macs, but I want to post the files on the web. I guess i have to zip them. I'll try that and see if it helps. Any idea why this happens? Isn't it just a binary file? Are they saved differently from one platform to the other?

I have been sending .pat versions embedded in e-mails so people can work on Macs, but I want to post the files on the web.  I guess i have to zip them.  I'll try that and see if it helps.  Any idea why this happens?  Isn't it just a binary file?  Are they saved differently from one platform to the other?


I think it may be a cross platform thing. Sometimes I have to zip files on my mac for my 3d programs to read over in windowsland. I don't think binary files should be effected, but they are sometimes. I know carriage returns are different b/t win/mac/unix, I send files zipped, since it usually works better. Maybe something gets changed when uploading or something. shrug.

I think it may be a cross platform thing.  Sometimes I have to zip files on my mac for my 3d programs to read over in windowsland.  I don't think binary files should be effected, but they are sometimes.  I know carriage returns are different b/t win/mac/unix, I send files zipped, since it usually works better.  Maybe something gets changed when uploading or something.  shrug.


> I have been sending .pat versions embedded in e-mails so people can

> work on Macs, but I want to post the files on the web. I guess i

> have to zip them. I'll try that and see if it helps. Any idea why

> this happens? Isn't it just a binary file? Are they saved

> differently from one platform to the other?

I have this problem all the time if someone posts a patch as attachment 

instead of pasting the patch as text. It seems that the files get 

corrupted on the way, don't know if its the providers or the programs 

This is independent on the platform on which it was made by the way...

phineus schrieb:
> I have been sending .pat versions embedded in e-mails so people can
> work on Macs, but I want to post the files on the web.  I guess i
> have to zip them.  I'll try that and see if it helps.  Any idea why
> this happens?  Isn't it just a binary file?  Are they saved
> differently from one platform to the other? 

I have this problem all the time if someone posts a patch as attachment 
instead of pasting the patch as text. It seems that the files get 
corrupted on the way, don't know if its the providers or the programs 
which do that...
This is independent on the platform on which it was made by the way...

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

Quote: phineus wrote on Tue, 08 January 2008 23:43

----------------------------------------------------

> I have been sending .pat versions embedded in e-mails so people can work on Macs, but I want to post the files on the web. I guess i have to zip them. I'll try that and see if it helps. Any idea why this happens? Isn't it just a binary file? Are they saved differently from one platform to the other?

There a several things that can go wrong in file exchange.

Most file exchanges that work reliably do so because there is a registered MIME Type (and a mapping from the filename suffix to that type) that identifies whether file transfer should be binary or ASCII. AFAIK there is no MIME type for Max patches, nor is .mxb a recognized suffix. OTOH, .pat is a recognized suffix, but for Photoshop patterns.-( So not much help with patches. (Except that at least Photoshop patterns are binary. I think.)

All this stuff is configurable on an HTTP Server, so if you administer your server you could set it up to handle Max patches correctly.

Nevertheless, .zipping is probably the easiest and most reliable approach. As a side effect, .zipping can compress Max patches pretty significantly (although they're not usually that big to start with). FWIW, I mostly use .zip for patches on my site.

Quote: phineus wrote on Tue, 08 January 2008 23:43
----------------------------------------------------
> I have been sending .pat versions embedded in e-mails so people can work on Macs, but I want to post the files on the web.  I guess i have to zip them.  I'll try that and see if it helps.  Any idea why this happens?  Isn't it just a binary file?  Are they saved differently from one platform to the other?
----------------------------------------------------

Can't open .mxb saved on XP on a Mac