[CM] CLM 3 - rmsenv bugs and clm-print openmcl

Tue, 15 May 2007 15:28:33 +0100

This is a multi-part message in MIME format.

------_=_NextPart_001_01C796FD.50F6BB07
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Greetings,

After being out of CM/CLM loop for a while, I'm trying to get my PICACS =
code (built in CM and CLM) working with  CM 2.10 and the CLM3 packaged =
with that.=20

I've found the my instrument rmsenv.ins (which is also packaged up with =
CLM3) no longer works. It returns a list of 0.0's regardless of what =
audio file I throw at it.

I'd debug it, but unfortunately it seems that CLM-PRINT is no longer =
working, at least here under Mac OS 10.4, with the OpenMCL used in CM =
2.10.

So, is there a solution for clm-print on openMCL, another way I could =
get debugging data from within the run loop, and/or an obvious =
identification of what has gone wrong in rmsenv.ins in the move to CLM3?

Thanks,
-=3DBret Battey

------_=_NextPart_001_01C796FD.50F6BB07
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7638.1">
<TITLE>CLM 3 - rmsenv bugs and clm-print openmcl</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>Greetings,<BR>
<BR>
After being out of CM/CLM loop for a while, I'm trying to get my PICACS =
code (built in CM and CLM) working with&nbsp; CM 2.10 and the CLM3 =
packaged with that.<BR>
<BR>
I've found the my instrument rmsenv.ins (which is also packaged up with =
CLM3) no longer works. It returns a list of 0.0's regardless of what =
audio file I throw at it.<BR>
<BR>
I'd debug it, but unfortunately it seems that CLM-PRINT is no longer =
working, at least here under Mac OS 10.4, with the OpenMCL used in CM =
2.10.<BR>
<BR>
So, is there a solution for clm-print on openMCL, another way I could =
get debugging data from within the run loop, and/or an obvious =
identification of what has gone wrong in rmsenv.ins in the move to =
CLM3?<BR>
<BR>
Thanks,<BR>
-=3DBret Battey<BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C796FD.50F6BB07--