Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • gst-plugins-base gst-plugins-base
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 645
    • Issues 645
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 88
    • Merge requests 88
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GStreamer
  • gst-plugins-basegst-plugins-base
  • Issues
  • #778

Closed
Open
Created Jun 22, 2020 by Sebastian Dröge@slomo🍵Owner0 of 1 task completed0/1 task

audio/videodecoder: Reconsider max-errors default value

The following discussion from !720 (merged) should be addressed:

  • @ndufresne started a discussion: (+1 comment)

    Overtime, this internal feature has cause a lot more harm then good. At least in live pipeline, giving up rather then skipping is always the wrong choice, so it's nice that it can be configured through properties too, but shall we reconsider the default value ?

Assignee
Assign to
Time tracking