validation errors

[Mikl]

Hello,

I am recording video like this
 video: appsrc ! 'video/x-raw-rgb,width=800,height=600,framerate=24/1' ! jpegenc ! matroskamux ! filesink
  2 subtitles truks: appsrc ! '"text/x-raw' ! matroskamux ! filesink
Before stop pipeline i am sending EOS:
gst_element_send_event(_pipeline, gst_event_new_eos());
Also trying to send event to close segment, but don`t see it on the bus

Video can be played in VLS, but not in, standard for Windows, Windows Media Player
Also i can not play video
gst-launch-1.0 filesrc location=C:\\test\\test.mkv ! matroskademux name=mux mux.video_0! jpegdec ! autovideosink

Bu running validation i have some information about file.

Can you explain me please, what all this errors means?

gst-launch-1.0 filesrc location=C:\\Video\\test.mkv ! matroskademux name=mux mux.video_0! jpegdec ! autovideosink
Setting pipeline to PAUSED ...
Pipeline is PREROLLING ...
ERROR: from element /GstPipeline:pipeline0/GstMatroskaDemux:mux: Internal data s
tream error.
Additional debug info:
matroska-demux.c(4759): gst_matroska_demux_loop (): /GstPipeline:pipeline0/GstMa
troskaDemux:mux:
streaming stopped, reason not-negotiated (-4)
ERROR: pipeline doesn't want to preroll.
Setting pipeline to NULL ...
Freeing pipeline ...

C:\gstreamer\1.0\x86\bin>gst-validate-1.0 filesrc location=C:\\Video\\test.mkv ! matroskademux name=mux mux.video_0! jpegdec ! autovideosink
WARNING: no real random source present!
Starting pipeline
Pipeline started
   warning : EOS received without segment event before
             Detected on <jpegdec0:src>
             Description : A segment event should always be sent before data flo
w EOS being some kind of data flow, there is no exception in that regard

     issue : EOS events that are part of the same pipeline 'operation' should ha
ve the same seqnum
             Detected on <mux:video_0>
             Detected on <jpegdec0:sink>
             Description : when events/messages are created from another event/m
essage, they should have their seqnums set to the original event/message seqnum

  critical : We got an ERROR message on the bus
             Detected on <pipeline0>



==== Got criticals, Return value set to 18 ====
     Critical error Got error: Internal data stream error. -- Debug message: mat
roska-demux.c(4759): gst_matroska_demux_loop (): /GstPipeline:pipeline0/GstMatro
skaDemux:mux:
streaming stopped, reason not-negotiated (-4)

Issues found: 3
Returning 18 as error where found
=======> Test FAILED (Return value: 18)

[rachelgomez161999]

Validation errors can occur when you submit a form or document that does not meet certain requirements or criteria set by the system or application. Here are some tips to help you fix validation errors:

Understand the error message: Carefully read the error message to understand what went wrong. Sometimes the error message may provide specific instructions on how to fix the problem.

Check the required fields: Ensure that all required fields are filled out with valid data. Required fields are marked with an asterisk or a red indicator.

Check formatting: Check that you have followed the formatting rules for the input fields, such as date formats, phone numbers, and email addresses.

Check for typos: Look for spelling errors or typos in the input fields. These can cause validation errors if the system cannot recognize the input.

Try different options: If the error message indicates that the input is not valid, try different options or values until the error is resolved.

Clear your cache and cookies: Sometimes validation errors can be caused by outdated data stored in your browser's cache and cookies. Clearing your cache and cookies can help to resolve these errors.

Contact support: If you are unable to resolve the validation error, contact the support team or the website administrator for assistance.

By following these tips, you should be able to fix most validation errors and submit your form or document successfully.

Regards,
Rachel Gomez