asfmux: Fix typo in property description

s/milisecs/milliseconds/g
This commit is contained in:
rubenrua 2020-03-12 12:13:10 +01:00
parent fb888dada1
commit 6c3f092afc
4 changed files with 4 additions and 4 deletions

View file

@ -843,7 +843,7 @@
"writable": true "writable": true
}, },
"preroll": { "preroll": {
"blurb": "The preroll time (milisecs)", "blurb": "The preroll time (milliseconds)",
"construct": true, "construct": true,
"construct-only": false, "construct-only": false,
"default": "5000", "default": "5000",

View file

@ -242,7 +242,7 @@ gst_asf_mux_class_init (GstAsfMuxClass * klass)
G_PARAM_READWRITE | G_PARAM_CONSTRUCT | G_PARAM_STATIC_STRINGS)); G_PARAM_READWRITE | G_PARAM_CONSTRUCT | G_PARAM_STATIC_STRINGS));
g_object_class_install_property (gobject_class, PROP_PREROLL, g_object_class_install_property (gobject_class, PROP_PREROLL,
g_param_spec_uint64 ("preroll", "Preroll", g_param_spec_uint64 ("preroll", "Preroll",
"The preroll time (milisecs)", "The preroll time (milliseconds)",
0, G_MAXUINT64, 0, G_MAXUINT64,
DEFAULT_PREROLL, DEFAULT_PREROLL,
G_PARAM_READWRITE | G_PARAM_CONSTRUCT | G_PARAM_STATIC_STRINGS)); G_PARAM_READWRITE | G_PARAM_CONSTRUCT | G_PARAM_STATIC_STRINGS));

View file

@ -135,7 +135,7 @@ struct _GstAsfMux
/* same as properties, but those are stored here to be /* same as properties, but those are stored here to be
* used without modification while muxing a single file */ * used without modification while muxing a single file */
guint32 packet_size; guint32 packet_size;
guint64 preroll; /* milisecs */ guint64 preroll; /* milliseconds */
gboolean merge_stream_tags; gboolean merge_stream_tags;
GstClockTime first_ts; GstClockTime first_ts;

View file

@ -537,7 +537,7 @@ retry:
* upstream msdk element sometimes needs to wait for a gst buffer * upstream msdk element sometimes needs to wait for a gst buffer
* to be released in downstream. * to be released in downstream.
* *
* Poll the pool for a maximum of 20 milisecnds. * Poll the pool for a maximum of 20 millisecond.
* *
* FIXME: Is there any better way to handle this case? * FIXME: Is there any better way to handle this case?
*/ */