Ticket #244 (closed defect: fixed)

Opened 4 years ago

Last modified 4 years ago

PA_COMMAND_RECORD_STREAM_MOVED missing suspend-flag in tag

Reported by: slicer Owned by: lennart
Milestone: Component: daemon
Keywords: Cc:

Description

Hi,

Pulse 0.9.9 on gutsy.

If I start parec in a shell with parec -d 0 > /dev/null

Then, in pacmd, I do move-source-output XX 2

then parec exits with Connection failure: Protocol error Stream error: Protocol error

move-sink-input works as expected.

I was planning to remove the choice of input/output device from my application (mumble) and let the user just move the stream around with pavucontrol or something similar, but that's a no-go if moving input streams doesn't work :(

Attachments

pulseaudio_fix_record_stream_moved.patch (488 bytes) - added by slicer 4 years ago.
Patch to fix the problem

Change History

Changed 4 years ago by slicer

Patch to fix the problem

Changed 4 years ago by slicer

  • priority changed from normal to high
  • severity changed from normal to major
  • summary changed from move-source-output causes program to fail with "protocol error" to PA_COMMAND_RECORD_STREAM_MOVED missing suspend-flag in tag

The problem seems to be that in some recent version, PA_COMMAND_PLAYBACK_STREAM_MOVED got a suspend flag added to it's tag. The receiving end expects this flag for both playback and record streams. However, the flag was not added to PA_COMMAND_RECORD_STREAM_MOVED meaning the receiver always found a too-short tag.

I've verified that things work now, and I can move source-outputs around. (Which is kind of cool, when will this be added to pavucontrol?)

Changed 4 years ago by lennart

  • status changed from new to closed
  • resolution set to fixed

(In [2181]) properly notify clients about suspended state when moving source output streams. Closes #244. Patch from slicer

Note: See TracTickets for help on using tickets.