Action Signals
send-headers
g_signal_emit_by_name (param_0, "send-headers");
ret = param_0.emit ("send-headers")
let ret = param_0.emit ("send-headers");
Parameters:
split-at-running-time
g_signal_emit_by_name (param_0, "split-at-running-time", arg0);
ret = param_0.emit ("split-at-running-time", arg0)
let ret = param_0.emit ("split-at-running-time", arg0);
Parameters:
Properties
chunk-duration
“chunk-duration” guint64
Duration for each FMP4 chunk (default = no chunks)
Flags : Read / Write
Default value : 18446744073709551615
decode-time-offset
“decode-time-offset” gint64
Offset to apply to the decode time in the tfdt box. By default the offset is the running time of the first DTS or earliest PTS of the stream.
This can be used to shift the decoding timeline.
Flags : Read / Write
Default value : 0
Since : plugins-rs-0.14.0
fragment-duration
“fragment-duration” guint64
Duration for each FMP4 fragment in nanoseconds
Flags : Read / Write
Default value : 10000000000
header-update-mode
“header-update-mode” Fmp4mux-header-update-mode *
Mode for updating the header at the end of the stream
Flags : Read / Write
Default value : none (0)
interleave-bytes
“interleave-bytes” guint64
Interleave between streams in bytes
Flags : Read / Write
Default value : 0
interleave-time
“interleave-time” guint64
Interleave between streams in nanoseconds
Flags : Read / Write
Default value : 250000000
manual-split
“manual-split” gboolean
In manual-split=true
mode the chunk-duration
/ fragment-duration
properties are only used for latency reporting. Similarly, the
split-at-running-time
action signal has no effect at all and no automatic
force-keyunit
events are sent.
Instead, providing suitable input for splitting is the job of the application.
The application is supposed to send a (serialized) custom-downstream
event
with a structure named FMP4MuxSplitNow
to signal when fragments or chunks
should be split off. A split will happen between the buffer received right
before the event and the buffer received right after the event.
The event has an optional boolean chunk
field (defaults to false
) to signal
that a chunk should be created instead of a full fragment.
Whenever a fragment should be created then this event should be sent right before the next keyframe. Sending the event at any other time will cause a warning but a full fragment will still be created, just that the next fragment will not start on a keyframe as requested by the application.
Flags : Read / Write
Default value : false
Since : plugins-rs-0.14.0
movie-timescale
“movie-timescale” guint
Timescale to use for the movie (units per second, 0 is automatic)
Flags : Read / Write
Default value : 0
send-force-keyunit
“send-force-keyunit” gboolean
Send force-keyunit events to request keyframes for the start of each fragment. If this is disabled then the application needs to ensure that keyframes are provided at appropriate times.
Flags : Read / Write
Default value : true
Since : plugins-rs-0.14.0
start-fragment-sequence-number
“start-fragment-sequence-number” guint
Initial sequence number to use in the mfhd box.
This is incremented with every fragment by one and stays the same between chunks.
Flags : Read / Write
Default value : 1
Since : plugins-rs-0.14.0
write-edts-mode
“write-edts-mode” Fmp4mux-write-edts-mode *
Mode for writing EDTS, when in auto mode, edts written only for non-live streams.
Flags : Read / Write
Default value : auto (0)
write-mehd
“write-mehd” gboolean
Write movie extends header box with the duration at the end of the stream (needs a header-update-mode enabled)
Flags : Read / Write
Default value : false
write-mfra
“write-mfra” gboolean
Write fragment random access box at the end of the stream
Flags : Read / Write
Default value : false
Named constants
Fmp4mux-header-update-mode
How and when updating of the header (moov
, initialization segment) is allowed.
Members
none
(0) – None
rewrite
(1) – Rewrite
update
(2) – Update
caps
(3) – Caps
Fmp4mux-write-edts-mode
Members
auto
(0) – Auto
always
(1) – Always
never
(2) – Never
The results of the search are