Monitoring and Pulseaudio accuracy

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi all,

I have pulseaudio running on Ubuntu and send the sound digitally to a
set of High end digital speakers. Since it is Hi-Fi, the work I'm
doing involves ensuring wherever possible that the digital bits are
not disturbed by the software systems the value is passing through -
unless it has to be when the softphone rings.

I did a simple test using pacat and parecord on the sink Monitor with
a set of float32le tones representing a simple log sweep through the
frequency range. Volumes were set to 100% across the entire chain. Yet
when I checked the float values, they had been perturbed by a small
amount.

That got me thinking. Can pulseaudio maintain a 'clean path'
throughout the entire software chain?

I'm presuming that some sort of rounding or conversion internally has
altered the float32le. Is there a representation that would be more
likely to come through 'clean'?

Additionally when I was doing a parec on the Monitor and used the
'float32ne' format it seemed to come out Big Endian on an Intel
machine, which surprised me a little. Is that a bug or did I miss
something?

Thanks

-- 
Neil Wilson



[Index of Archives]     [Linux Audio Users]     [AMD Graphics]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux