I guess there's a math foundation here that would justify the need
for a -1..1 correct signal range...
Is just a convenience.
16bit or 24bit audio files have totally different numbers to represent
the start, middle and end of the same sine wave.
Why would you want Pd to have 0 as one side
Thanks Christof and Lucas for your replies!
> The Amp and the Speaker will just work on "one half" of their normal area.
> (50% of its audio loudness).
>
Exactly, that is the difference I hear in loudness.
> It shouldn't hurt the amp or the speaker as long as you don't try to pump up
> the
I think the DAC/audiobackend/soundcard will accept those values "As is".
The Amp and the Speaker will just work on "one half" of their normal
area. (50% of its audio loudness).
It shouldn't hurt the amp or the speaker as long as you don't try to
pump up the volume. You might break the
Hi,
software like Pd or jack doesn't care because it's not forbidden to send
only positive or even constant values. You might use your DAC to send
control voltages for a modular synthesizer, for example. Most audio
interfaces, however, apply some kind of highpass filter to the outputs
to get
Hi everyone,
I just found out that I have sent signals between 0..1 instead of -1..1 to
[dac] (!!!), and I am wondering... what happens in that case?
Does Pd take care of that in any way?
Or, Is that the job of portaudio/asio/jack?
Or, Is that the job of the audio interface?
Or, nothing happens
Hi list,
Related to the bug report https://github.com/pure-data/pure-data/issues/872
, I wanted to drop some questions about sigmund:
- when using the "-npeak x tracks" settings, the X stands for the maximum
number of tracks, and no more are allowed. Is this the expected behavior?
It's not
