FaSTTUBe/GST-Tensordecoder-ov_ep
37
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

validate: don't override max-latency if config contains multiple structs

Browse Source 
gst_validate_utils_get_clocktime() is resetting the value if it's not
present in the struct so we were overriding it on the next iterations.
This commit is contained in:
Guillaume Desmottes 2019-02-07 17:34:56 +01:00 committed by Thibault Saunier
parent da22878a5f
commit 3ebc26e265
1 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
validate/gst/validate/gst-validate-scenario.c
View File

@ -3306,8 +3306,12 @@ _load_scenario_file (GstValidateScenario * scenario,
/* max-latency and max-dropped can be overriden using config */
for (config = gst_validate_plugin_get_config (NULL); config;
config = g_list_next (config)) {
GstClockTime max_latency;
gst_validate_utils_get_clocktime (config->data, "max-latency",
&priv->max_latency);
&max_latency);
if (GST_CLOCK_TIME_IS_VALID (max_latency))
priv->max_latency = max_latency;
gst_structure_get_int (config->data, "max-dropped", &priv->max_dropped);
}