Feature #2035

Save sequence number on a per-participant basis

Added by C. Leichsenring almost 10 years ago. Updated almost 10 years ago.

Status:RejectedStart date:09/30/2014
Priority:NormalDue date:
Assignee:C. Leichsenring% Done:

0%

Category:-
Target version:-

Description

Currently, only one rsbaudiosink can ever output sound on any given rsbaudiosrc. Terminating the first informer and restarting it will result in the packets being more-or-less silently dropped with a "sequence number skip" message. The proposed fix is to store one previous sequence number variable per participant ID in a hash table.

History

#1 Updated by C. Leichsenring almost 10 years ago

  • Status changed from New to Rejected

Seems to be unnecessary after all because the error lies elsewhere. The gstreamer timestamps aren't reset accurately enough but Jan has a patch that might fix this. There could still be issues with the gstreamer pipeline itself when there isn't any input at all for a while. In that case we might have to implement a silence default output to prevent the buffer from underrunning.

Also available in: Atom PDF