From 9a07ce768131c519783a99c98a2fd4058b6265c6 Mon Sep 17 00:00:00 2001 From: Thibault Saunier Date: Thu, 24 Jul 2014 19:03:50 +0200 Subject: [PATCH] tools:validate: Concider seek in PAUSED position being not exact as WARNING In some corner cases in GNL it is totally correct that a position in a seek in paused is not perfectly exact --- tools/ges-validate.c | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/tools/ges-validate.c b/tools/ges-validate.c index 7916d454ec..3064493485 100644 --- a/tools/ges-validate.c +++ b/tools/ges-validate.c @@ -447,6 +447,7 @@ gboolean ges_validate_activate (GstPipeline * pipeline, const gchar * scenario, gboolean * needs_setting_state) { + GstValidateOverride *o; GstValidateRunner *runner = NULL; GstValidateMonitor *monitor = NULL; @@ -523,6 +524,12 @@ ges_validate_activate (GstPipeline * pipeline, const gchar * scenario, set_child_property_mandatory_fields, "Allows to change child property of an object", FALSE); + o = gst_validate_override_new (); + gst_validate_override_change_severity (o, + GST_VALIDATE_ISSUE_ID_EVENT_SEEK_RESULT_POSITION_WRONG, + GST_VALIDATE_REPORT_LEVEL_WARNING); + gst_validate_override_register_by_name ("scenarios", o); + runner = gst_validate_runner_new (); g_signal_connect (runner, "report-added", G_CALLBACK (_validate_report_added_cb), pipeline);