Bug 68107 - A glitch due to another stream starting to play when recording from a single sink input
Summary: A glitch due to another stream starting to play when recording from a single ...
Status: RESOLVED MOVED
Alias: None
Product: PulseAudio
Classification: Unclassified
Component: core (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: pulseaudio-bugs
QA Contact: pulseaudio-bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-14 13:54 UTC by Tanu Kaskinen
Modified: 2018-07-30 10:15 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Tanu Kaskinen 2013-08-14 13:54:04 UTC
Steps to reproduce:

1. paplay some_file.ogg (the file should be long enough to be able to do the next steps while paplay is running)

2. Check the sink input index of paplay. Here we'll assume that it's 0.

3. parecord --monitor-stream=0 test.wav

4. paplay some_other_file.ogg

5. Stop parecord, and then you can stop the paplay instances too.

6. paplay test.wav


Expected results:

test.wav contains audio from some_file.ogg without glitches.


Actual results:

test.wav contains audio from some_file.ogg, but with a glitch (pause, some repeated audio) at the moment when some_other_file.ogg started to play.


Tested with an alsa sink (support for sink rewinding is likely to be important).
Comment 1 Tanu Kaskinen 2013-11-23 06:29:21 UTC
The root cause is probably the same as in the bug reported here: http://thread.gmane.org/gmane.comp.audio.pulseaudio.general/18911

So, monitor source rewinding appears to be broken in general.
Comment 2 GitLab Migration User 2018-07-30 10:15:36 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/304.


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.