Ticket #73 (closed enhancement: fixed)

Opened 2 years ago

Last modified 2 months ago

RTP Receive default sink

Reported by: s2156945 Assigned to: lennart
Priority: normal Milestone:
Component: module-rtp-* Severity: minor
Keywords: rtp module-rtp-recv Cc: pulse@wood.id.au

Description

module-rtp-recv can only connect new received streams to the default sink.

This makes it difficult to automatically route different RTP streams to different sinks.

Change History

04/02/07 07:39:59 changed by s2156945

  • cc set to pulse@wood.id.au.

05/23/07 02:32:28 changed by lennart

  • status changed from new to assigned.

I am sorry. I don't fully understand?

What exactly are you requesting? That we allow you the specify a table on the configuration line that allows to map certain source ip addresses to certain sinks?

I am not sure if this would be a good idea. If you want to do this I recommed using different port numbers or multicasts groups for each device.

05/23/07 03:54:52 changed by s2156945

I am using different multicast addresses:

Receiving device has 2 instances of module-rtp-recv loaded with different sap-addresses.

2 Sending devices send 1 rtp stream each to separate sap-addresses.

The module-rtp-recv connects to the default sink on reception of an rtp stream.

What I want to do is be able to set the default sink of of each module-rtp-recv, so that rtp stream (from device A) to 1st module-rtp-recv goes to sink A, and rtp stream (from device B) to 2nd module-rtp-recv goes to sink B.

Currently I acheive this by sending stereo RTP streams from both device A and B with 1 channel muted at each sending device.

These streams are mixed at the receiving device giving separate channels.

cheers, Woody

10/01/08 04:26:03 changed by lennart

  • status changed from assigned to closed.
  • resolution set to fixed.

module-rtp-recv.c has the "sink=" parameter for this.

10/01/08 04:59:55 changed by s2156945

Hmm, looks like the sink option has been there the whole time - wish I'd seen it a year ago :-)