Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
gst-plugins-bad
gst-plugins-bad
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,023
    • Issues 1,023
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 202
    • Merge Requests 202
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GStreamer
  • gst-plugins-badgst-plugins-bad
  • Issues
  • #1109

Closed
Open
Created Nov 06, 2019 by Pieter Jordaan@rompelstompel

WebRTC recvonly when answering with audio to Chrome/Firefox

When adjusting the gstwebrtc-demo project to allow browser to make the offer, webrtcbin answers with recvonly for audio. This only happens when creating an answer to the browser. When the gstreamer side generates an offer, the browser answers with sendrecv and both sides work.

Here is a pastebin of an audio-only session log (GST_DEBUG="*webrtc*:7"), where the gstreamer side answers to the browser with recvonly. https://pastebin.com/xdWk0ZKA

What is clear from the log is that webrtcbin notices the VP8 and OPUS caps on its sink pads. However, no audio is negotiated to send to the browser.

I have forked the demos here: https://github.com/Climax777/gstwebrtc-demos/tree/recvonlybug in the recvonlybug branch. I've only used the sendrecv demo at this stage since it involves the browser.

Edited Nov 06, 2019 by Pieter Jordaan
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None