bkshepard

Is there a difference in the way a standalone is built on an Intel Mac versus a PPC Mac? I have a patcher that I am trying to build as a standalone. The Max/MSP patcher works just fine on either of my two machines. However, if I build the standalone on my Intel Powerbook (2.4 GHz Intel Core 2 Duo, 10.5.6), and try to run it on my PPC (Dual 1GHz PPC G4, 10.4.11) the program loads fine, but the audio is just a bunch of pops and clicks.

If I reverse the process and build on the PPC, it seems to work fine on the Intel. Both machines have the same versions of MaxMSP and MaxMSP Runtime (5.0.6).

Additionally, after attempting to run the Intel-built app on my PPC, the audio driver for MaxMSP remains kaput until I reboot. Even if I launch a very simple patch with the MaxMSP application, the audio continues to be pops and clicks until I restart.

I don't know if it's related, but I'm using a MOTU 896HD with the G4, and a M-Audio FireWire 410 with the Intel.

Is there a difference in the way a standalone is built on an Intel Mac versus a PPC Mac?  I have a patcher that I am trying to build as a standalone.  The Max/MSP patcher works just fine on either of my two machines.  However, if I build the standalone on my Intel Powerbook (2.4 GHz Intel Core 2 Duo, 10.5.6), and try to run it on my PPC (Dual 1GHz PPC G4, 10.4.11) the program loads fine, but the audio is just a bunch of pops and clicks.

If I reverse the process and build on the PPC, it seems to work fine on the Intel.  Both machines have the same versions of MaxMSP and MaxMSP Runtime (5.0.6).

Additionally, after attempting to run the Intel-built app on my PPC, the audio driver for MaxMSP remains kaput until I reboot.  Even if I launch a very simple patch with the MaxMSP application, the audio continues to be pops and clicks until I restart.

I don't know if it's related, but I'm using a MOTU 896HD with the G4, and a M-Audio FireWire 410 with the Intel.


intel-built-vs-ppc-built-standalone

After doing a bit of further digging, this may be a problem with Tap.Tools. I'm still checking...

After doing a bit of further digging, this may be a problem with Tap.Tools.  I'm still checking...


Intel-built vs. PPC-built Standalone