Looks to me like OpenMCL is still PPC only. On Rick's suggestion, I tried a fresh OpenMCL install and the latest CLM3. In this case, clm-print does work, so I was able to narrow down the problem.
I'm using (make-double-float-array) to create a data collection array that is passed into the run loop. Within the run loop, it appears I am succesfully writing values into and reading values from this array. But after the run loop, running a Print on the array returns an array of D0.0's. So it appears the array contents aren't surviving the exit from the run loop. I tried using (make-array) instead -- same result. Same error is occurring with my other instrument that tries to return an envelope: scentroid and autoc. Any other sneaky ways I might be able to succesfully export data from the run loop? -----Original Message----- From: Bill Schottstaedt [mailto:[EMAIL PROTECTED] Sent: Tue 5/15/2007 6:09 PM To: Bret Battey; [email protected] Subject: Re: [CM] CLM 3 - rmsenv bugs and clm-print openmcl > It returns a list of 0.0's regardless of what audio file I throw at it. It works for me in ACL 8.1 in both Linux and OSX -- I don't have openmcl -- does it work on an Intel Mac yet?
