Bug 86581 - "parecord --fix-rate" doesn't take the assigned rate into account when writing a wav file
Summary: "parecord --fix-rate" doesn't take the assigned rate into account when writin...
Alias: None
Product: PulseAudio
Classification: Unclassified
Component: tools (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: pulseaudio-bugs
QA Contact: pulseaudio-bugs
Keywords: love
Depends on:
Reported: 2014-11-22 15:15 UTC by Tanu Kaskinen
Modified: 2018-07-30 10:01 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Description Tanu Kaskinen 2014-11-22 15:15:50 UTC
"parecord --fix-rate" always creates wav files whose metadata say that the rate is 44.1 kHz, even though the server may assign some different rate to the source output. This happens because the wav file parameters are set before creating the stream.

The same issue probably affects --fix-channels and --fix-format too, but I didn't test that.
Comment 1 Raymond 2014-11-26 08:25:31 UTC
this case is different from paplay

for paplay, the audio file already contain rate and you can specify another rate to provide pitching effect

the rate in capture file should be equal to --rate which default to 44100Hz
Comment 2 GitLab Migration User 2018-07-30 10:01:19 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/173.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.