Hello everyone.

Based on the experience I've had to revise the amplitude levels of a file
generated by an quadraphonic orchestra csd (generated after the "Render to
file" or "Perform Real-Time to File").

But, and this is where I would like some advice, intervention leveling
amplitude is quite rough in fact often is based on "observation" of the
direct amplitude profile (for example, seen in a waveform editor), or worse,
as heard by controlling the result in short, the methodology is often not
very scientific.

Instead I would opt for the latter.
I already love to do it from within the orchestra csound (making a "control"
numerical amplitude).
In short, how could I act on the code to get a more scientific:
/• look at the profile amplitude;
• identify the amplitude peaks;
• make a statistical profile of the numerical scale;
• act accordingly?/

thanks,

e

--
View this message in context: http://csound.1045644.n5.nabble.com/amplitude-control-tp4861887p4861887.html
Sent from the Csound - General mailing list archive at Nabble.com.


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

What I do is normalize the output soundfile after Csound has finished
rendering. I use sox and specify a peak amplitude of -3 dbfs. I have a
script that does this automatically for every rendering I do, and it
also creates a CD audio copy of the file and an mp3 copy of the file.

You can see the code in the Silencio.lua file in google code.

Regards,
Mike

On Sun, Oct 2, 2011 at 9:45 AM, Enrico Francioni
 wrote:
>
> Hello everyone.
>
> Based on the experience I've had to revise the amplitude levels of a file
> generated by an quadraphonic orchestra csd (generated after the "Render to
> file" or "Perform Real-Time to File").
>
> But, and this is where I would like some advice, intervention leveling
> amplitude is quite rough in fact often is based on "observation" of the
> direct amplitude profile (for example, seen in a waveform editor), or worse,
> as heard by controlling the result in short, the methodology is often not
> very scientific.
>
> Instead I would opt for the latter.
> I already love to do it from within the orchestra csound (making a "control"
> numerical amplitude).
> In short, how could I act on the code to get a more scientific:
> /• look at the profile amplitude;
> • identify the amplitude peaks;
> • make a statistical profile of the numerical scale;
> • act accordingly?/
>
> thanks,
>
> e
>
> --
> View this message in context: http://csound.1045644.n5.nabble.com/amplitude-control-tp4861887p4861887.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
> Send bugs reports to the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>



-- 
Michael Gogins
Irreducible Productions
http://www.michael-gogins.com
Michael dot Gogins at gmail dot com


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

I suspect my way of working is not to many people's taste but I write the
.csd file with a global variable multiplying each output.  I then render
to disk in floating format, run the scale utility and that reports the
value of the global variable that gives zero headroom.

never finished scripting it but it is part of my Makefile for a piece

==John ff

> What I do is normalize the output soundfile after Csound has finished
> rendering. I use sox and specify a peak amplitude of -3 dbfs. I have a
> script that does this automatically for every rendering I do, and it
> also creates a CD audio copy of the file and an mp3 copy of the file.
>
> You can see the code in the Silencio.lua file in google code.
>
> Regards,
> Mike
>
> On Sun, Oct 2, 2011 at 9:45 AM, Enrico Francioni
>  wrote:
>>
>> Hello everyone.
>>
>> Based on the experience I've had to revise the amplitude levels of a
>> file
>> generated by an quadraphonic orchestra csd (generated after the "Render
>> to
>> file" or "Perform Real-Time to File").
>>
>> But, and this is where I would like some advice, intervention leveling
>> amplitude is quite rough in fact often is based on "observation" of the
>> direct amplitude profile (for example, seen in a waveform editor), or
>> worse,
>> as heard by controlling the result in short, the methodology is often
>> not
>> very scientific.
>>
>> Instead I would opt for the latter.
>> I already love to do it from within the orchestra csound (making a
>> "control"
>> numerical amplitude).
>> In short, how could I act on the code to get a more scientific:
>> /• look at the profile amplitude;
>> • identify the amplitude peaks;
>> • make a statistical profile of the numerical scale;
>> • act accordingly?/
>>
>> thanks,
>>
>> e
>>
>> --
>> View this message in context:
>> http://csound.1045644.n5.nabble.com/amplitude-control-tp4861887p4861887.html
>> Sent from the Csound - General mailing list archive at Nabble.com.
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>>
>
>
>
> --
> Michael Gogins
> Irreducible Productions
> http://www.michael-gogins.com
> Michael dot Gogins at gmail dot com
>
>
> Send bugs reports to the Sourceforge bug tracker
>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>
>
>
>




Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

perhaps with /clip/?

e

--
View this message in context: http://csound.1045644.n5.nabble.com/amplitude-control-tp4861887p4862492.html
Sent from the Csound - General mailing list archive at Nabble.com.


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"