# cccombiner

Combines GstVideoCaptionMeta with video input stream

## Hierarchy

    GObject
        ╰──GInitiallyUnowned
            ╰──GstObject
                ╰──GstElement
                    ╰──GstAggregator
                        ╰──cccombiner

## Factory details

Authors: – Sebastian Dröge <sebastian></sebastian>

Classification: – `Filter`

Rank – none

Plugin – closedcaption

Package – GStreamer Bad Plug-ins

## Pad Templates

### `caption`

    closedcaption/x-cea-608:
             format: { raw, s334-1a }
    closedcaption/x-cea-708:
             format: { cc_data, cdp }

Presence – request

Direction – sink

Object type – GstAggregatorPad

### `sink`

    ANY

Presence – always

Direction – sink

Object type – GstAggregatorPad

### `src`

    ANY

Presence – always

Direction – src

Object type – GstAggregatorPad

## Properties

### max-scheduled

    “max-scheduled” guint

Controls the number of scheduled buffers after which the element will start dropping old buffers from its internal queues. See schedule.

Flags : Read / Write

Default value : 30

Since : 1.20

### output-padding

    “output-padding” gboolean

When schedule is TRUE, this property controls whether the output closed caption meta stream will be padded.

Flags : Read / Write

Default value : true

Since : 1.22

### schedule

    “schedule” gboolean

Controls whether caption buffers should be smoothly scheduled in order to have exactly one per output video buffer.

This can involve rewriting input captions, for example when the input is CDP sequence counters are rewritten, time codes are dropped and potentially re-injected if the input video frame had a time code meta.

Caption buffers may also get split up in order to assign captions to the correct field when the input is interlaced.

This can also imply that the input will drift from synchronization, when there isn't enough padding in the input stream to catch up. In that case the element will start dropping old caption buffers once the number of buffers in its internal queue reaches max-scheduled.

When this is set to FALSE, the behaviour of this element is essentially that of a funnel.

Flags : Read / Write

Default value : true

Since : 1.20

The results of the search are