[CM] Re: CM.app (OS X) on intel creating unplayable files

[Rick Taube]

oop sorry I havent had any time at all to poke at this in the past  
three days!
THe way its SUPPOSED to work is that CM.app doesnt build CLM until  
its loaded. So all.lisp should be calling configure as normal.  So  
maybe i have a stale file in clm-3/ from when I compiled the app on  
ppc/darwin??

the problem is that i dont have an intel box to see what is going  
wrong. But i THINK i tested to make sure that fm-violin tooted 440  
before i packaged the app. if not my apologies.

On Feb 8, 2007, at 2:24 PM, Bill Schottstaedt wrote:

>> 	test.aiff, aiff header: chunks confused at 67108884can't play  
>> test.aiff (header type: AIFC?)
>> Could this be some kind of byte-ordering problem?
>
> Yes -- 67108884 is big-endian 4.  The problem, I think, is that mus- 
> config.h
> is packaged pre-built in CM.app, and it comes from a big-endian  
> machine.
> I might be able to create a little endian version, but ideally this  
> file should
> be written when CLM builds itself (apparently when you first fire  
> up the
> application?) -- I don't actually know how these things work on a Mac.
> Perhaps it would fix it to leave mus-config.h out (it is built by  
> the configure
> script from mus-config.h.in), and make sure configure gets run at the
> CLM build time.
>
> _______________________________________________
> Cmdist mailing list
> Cmdist@ccrma.stanford.edu
> http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist