Fw: Re: [CM] CLM and file sizes?

Joseph Anderson J.Anderson@hull.ac.uk
Mon, 13 Nov 2006 11:09:32 -0000

content-class: urn:content-classes:message
Content-Type: text/plain;
Content-Transfer-Encoding: quoted-printable


My problem is that I'm trying to get a 26 minute 4 channel file at =
88.2kHz into a form that can be used with Nuendo.

Due to this 32-bit size field, it looks like I'm going to have to use a =
split files. Not the most convenient! Thanks for the help.


-----Original Message-----
From:	cmdist-admin@ccrma.Stanford.EDU on behalf of Fernando =
Sent:	Fri 11/10/2006 11:33 PM
To:	Bill Schottstaedt
Cc:	cmdist@ccrma.Stanford.EDU
Subject:	Re: Fw: Re: [CM] CLM and file sizes?

On Fri, 2006-11-10 at 13:52 -0800, Bill Schottstaedt wrote:
> I think the problem is that AIFC and wave headers have 32-bit size =
> whereas Next-style headers ignore the size field if it is obviously =
> I got the same bug you reported writing an AIFC file, but I've written
> a 7 hour 2-channel 44KHz file (4.23 GBytes) using mus-next as the
> header type.  So it's a bug in sndlib, not OSX.  I'm not sure there's
> a real solution for the AIFC/RIFF cases -- if I limit the written size =
> 31 bits, you can probably get all the data, but most programs won't =
> it.

I think there's a "w64" format that goes above the 2G limit of wav
files. Timemachine uses it by default (through libsndfile, I think), and
Ardour is going to use it in its new 2.x version, otherwise length of
recording time available for high sampling rates becomes unacceptably

-- Fernando

Cmdist mailing list

Content-Disposition: inline

To view the terms under which this email is distributed, please go to http://www.hull.ac.uk/legal/email_disclaimer.html