| "Csound is already checking for signals above 0dbfs in
order to display when samples are "out of range," probably
making an optional global limiter trivial to implement"--
True, but it could be useful as a digital signal limiter
in other ways, much like the limiters I use on tracks,
mix downs or audio mastering. Different versions of
an opcode, used and applied in a different way could be
a useful widget.
-Partev :-)
=============================================================
From: Jeff Taylor
Reply-To: csound@lists.bath.ac.uk
To: csound@lists.bath.ac.uk
Subject: [Csnd] Re: Re: Global Limiting
Date: Sun 02/21/10 05:33 AM
Csound is already checking for signals above 0dbfs in order to display when samples are "out of range," probably making an optional global limiter trivial to implement. And consider that the messages are effectively telling the user that the samples have been clipped, and they will be when rendered to file, but when played in real time on some sound cards they clearly have not!
The problem, as I see it, is not that you can potentially make some horrible noises but rather that on some sound cards the signal can be played back at 10 dB higher (if the previous message in this conversation is at all accurate) than 0dbfs before it clips! I use real time output because it makes me significantly more productive, not for real time performance. It may not seem like rendering to a file, opening it in Audacity, then pressing play is much more more time consuming than just pressing "play" in QuteCsound or Blue, but it makes a huge difference to me, especially when I am making revisions and rendering small sections over and over again. I keep levels low enough that a high energy signal isn't going to blow my ears/speakers as long as it is clipped appropriately. The proble
m is they aren't.
Personally, I don't particularly care if the global limiter is implemented as I use the limiter opcode by habit/experience (though it would be a convenience) but I have trouble seeing much of an argument against it, especially since Csound is already checking for samples that are out of range.
--
Electronically,
Jeff Taylor
On Sun, Feb 21, 2010 at 6:22 AM, john ffitch wrote:
I do not want a global limiter. That would interfere with the way I
work. One could argue for an optional one, but we have opcodes for
that and passing all audio through a global and having a single out
point is a better practice
==John ffitch
Sorry for any delay; unplanned I have been away for a week.
Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
_____________________________________________________________
Netscape. Just the Net You Need.
Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound" |