The PowerPC version lets you write the file in floats and then automatically
post-normalize to 16 bits.  We assume post-normallization to 100%, but I don't
think it would be too hard to make this settable.
-- 
Mike Berry
mikeb@nmol.com
http://www.nmol.com/users/mikeb

i mentioned this a couple of weeks ago, with no response --
if people would like Dave's feature Mike talks about below,
i could "port" it to be in canonical sources..
 (just needs a few mac->unix file things
and printf instead of progress dialog..)

would just be an option flag,
-matt



On Fri, 21 Aug 1998, Mike Berry wrote:

> The PowerPC version lets you write the file in floats and then automatically
> post-normalize to 16 bits.  We assume post-normallization to 100%, but I don't
> think it would be too hard to make this settable.
> -- 
> Mike Berry
> mikeb@nmol.com
> http://www.nmol.com/users/mikeb
> 
> 
> 

Given the time that I've expended just this evening fighting the
amplitude-containment battle via trial and error on a slow pvoc-based
instrument, I think such a feature would be very worthwhile. 

-=Bret

On Fri, 21 Aug 1998, Matt J. Ingalls wrote:

> 
> i mentioned this a couple of weeks ago, with no response --
> if people would like Dave's feature Mike talks about below,
> i could "port" it to be in canonical sources..
>  (just needs a few mac->unix file things
> and printf instead of progress dialog..)
> 
> would just be an option flag,
> -matt
> 
> 
> 
> On Fri, 21 Aug 1998, Mike Berry wrote:
> 
> > The PowerPC version lets you write the file in floats and then automatically
> > post-normalize to 16 bits.  We assume post-normallization to 100%, but I don't
> > think it would be too hard to make this settable.
> > -- 
> > Mike Berry
> > mikeb@nmol.com
> > http://www.nmol.com/users/mikeb
> > 
> > 
> > 
> 
> 

On Fri, 21 Aug 1998, Matt J. Ingalls wrote:

[snip]
> i mentioned this a couple of weeks ago, with no response --
> if people would like Dave's feature Mike talks about below,
> i could "port" it to be in canonical sources..

it could be a very nice idea...

[snip]
> would just be an option flag,

speaking of which, in 3.484 some funny things happened: a -Q option appeared
in the Mac/Metrowerks version and a -Q option disappeared in the linux/unix
version (I put that back in the linux sources distributed by me and Dave
Phillips). The two -Q options bear no relation to each other, so we're ending
up having incompatible command lines. Is there a good reason for this?
If name space pollution is the problem, we could adopt the gnu getopt package
that allows long names and is free (I would think it would compile on
all platforms).

Nicola

------------------------------------------------------------------------
Nicola Bernardini
E-mail: nicb@axnet.it
 
Re graphics: A picture is worth 10K words -- but only those to describe
the picture.  Hardly any sets of 10K words can be adequately described
with pictures.

hmm yes you did, and i didn't. but i am now. please sir can we have this
feature? complete with option to specify percentage? it would be most
appreciated!

tolve

>i mentioned this a couple of weeks ago, with no response --
>if people would like Dave's feature Mike talks about below,
>i could "port" it to be in canonical sources..
> (just needs a few mac->unix file things
>and printf instead of progress dialog..)
>
>would just be an option flag,
>-matt
>
>
>
>On Fri, 21 Aug 1998, Mike Berry wrote:
>
>> The PowerPC version lets you write the file in floats and then automatically
>> post-normalize to 16 bits.  We assume post-normallization to 100%, but I
>>don't
>> think it would be too hard to make this settable.
>> --
>> Mike Berry
>> mikeb@nmol.com
>> http://www.nmol.com/users/mikeb
>>
>>
>>

i might add that the AIFF-C is supported on all platforms now..
actually, its part of AIFF, but when you select 32-bit floats,
AIFF-C is created, which is basically AIFF file with an extra
info containing max-amp value.

i will take a look into the rescale code today..
(the flag will be -e)


-matt

there's gonna have to be some flags that are platform-specific.
maybe if we agree on what they are
i've had to change mac-specific flags a handful of times to accomodate
new ones.  but now looks like all platforms are #ifdef-d now
(i.e. MAC) so it should be easier..
(could also consolidate flags into one -- like sample-size and
(headers, etc..)

i dont know why the linux flag dissappeared...

-matt

On Sat, 22 Aug 1998, Nicola Bernardini wrote:

> On Fri, 21 Aug 1998, Matt J. Ingalls wrote:
> 
> [snip]
> > i mentioned this a couple of weeks ago, with no response --
> > if people would like Dave's feature Mike talks about below,
> > i could "port" it to be in canonical sources..
> 
> it could be a very nice idea...
> 
> [snip]
> > would just be an option flag,
> 
> speaking of which, in 3.484 some funny things happened: a -Q option appeared
> in the Mac/Metrowerks version and a -Q option disappeared in the linux/unix
> version (I put that back in the linux sources distributed by me and Dave
> Phillips). The two -Q options bear no relation to each other, so we're ending
> up having incompatible command lines. Is there a good reason for this?
> If name space pollution is the problem, we could adopt the gnu getopt package
> that allows long names and is free (I would think it would compile on
> all platforms).
> 
> Nicola
> 
> ------------------------------------------------------------------------
> Nicola Bernardini
> E-mail: nicb@axnet.it
>  
> Re graphics: A picture is worth 10K words -- but only those to describe
> the picture.  Hardly any sets of 10K words can be adequately described
> with pictures.
> 
>