Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • gstreamer gstreamer
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 716
    • Issues 716
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 373
    • Merge requests 373
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GStreamer
  • gstreamergstreamer
  • Issues
  • #408
Closed
Open
Created Jul 10, 2019 by Umedzhon Abdumuminov@umed💩

Why is GstBaseTransformClass::start called before GstBaseTransformClass::set_caps

Hi guys,

We are developing our own plugins and met problem:

Our plugins is inherited from GstBaseTransform. We would like to do initialization of internal objects before starting pipeline, but we have to have configured caps before.

So, we put it in the GstBaseTransformClass::start, but this function is called before GstBaseTransformClass::set_caps.

Is this correct behavior?

If so, how could we do our initialization after caps configuration but before start of pipeline if not in the GstBaseTransformClass::start?

Edited Jul 10, 2019 by Umedzhon Abdumuminov
Assignee
Assign to
Time tracking