Recherche avancée

Médias (2)

Mot : - Tags -/doc2img

Autres articles (73)

  • Personnaliser en ajoutant son logo, sa bannière ou son image de fond

    5 septembre 2013, par

    Certains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;

  • Publier sur MédiaSpip

    13 juin 2013

    Puis-je poster des contenus à partir d’une tablette Ipad ?
    Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir

  • Des sites réalisés avec MediaSPIP

    2 mai 2011, par

    Cette page présente quelques-uns des sites fonctionnant sous MediaSPIP.
    Vous pouvez bien entendu ajouter le votre grâce au formulaire en bas de page.

Sur d’autres sites (8147)

  • How to make Matomo GDPR compliant in 12 steps

    3 avril 2018, par InnoCraft

    Important note : this blog post has been written by digital analysts, not lawyers. The purpose of this article is to briefly show you where Matomo is entering into play within the GDPR process. This work comes from our interpretation of the UK privacy commission : ICO. It cannot be considered as professional legal advice. So as GDPR, this information is subject to change. We strongly advise you to have a look at the different privacy authorities in order to have up to date information.

    The General Data Protection Regulation (EU) 2016/679, also referred to RGPD in French, Datenschutz-Grundverordnung, DS-GVO in German, is a regulation on data protection and privacy for all individuals within the European Union. It concerns organizations worldwide dealing with EU citizens and will come into force on the 25th May 2018.

    The GDPR applies to ‘personal data’ meaning any information relating to an identifiable person who can be directly or indirectly identified in particular by reference to an identifier. It includes cookies, IP addresses, User ID, location, and any other data you may have collected.

    We will list below the 12 steps recommended by the UK privacy commissioner in order to be GDPR compliant and what you need to do for each step.

    The 12 steps of GDPR compliance according to ICO and how it fit with Matomo

    As mentioned in one of our previous blog post about GDPR, if you are not collecting any personal data with Matomo, then you are not concerned about what is written below.

    If you are processing personal data in any way, here are the 12 steps to follow along with some recommendations on how to be GDPR compliant with Matomo :

    1 – Awareness

    Make sure that people within your organization know that you are using Matomo in order to analyze traffic on the website/app. If needed, send them the link to the “What is Matomo ?” page.

    2 – Information you hold

    List all the personal data you are processing with Matomo within your record of processing activities. We are personally using the template provided by ICO which is composed of a set of 30 questions you need to answer regarding your use of Matomo. We have published an article which walks you through the list of questions specifically in the use case of Matomo Analytics. Please be aware that personal data may be also tracked in non-obvious ways for example as part of page URLs or page titles.

    3 – Communicating privacy information

    a – Add a privacy notice

    Add a privacy notice wherever you are using Matomo in order to collect personal data. Please refer to the ICO documentation in order to learn how to write a privacy notice. You can learn more in our article about creating your privacy notice for Matomo Analytics. Make sure that a privacy policy link is always available on your website or app.

    b – Add Matomo to your privacy policy page

    Add Matomo to the list of technologies you are using on your privacy policy page and add all the necessary information to it as requested in the following checklist. To learn more check out our article about Privacy policy.

    4 – Individuals’ rights

    Make sure that your Matomo installation respects all the individuals’ rights. To make it short, you will need to know the features in Matomo that you need to use to respect user rights (right of access, right of rectification, right of erasure…). These features are available starting in Matomo 3.5.0 released on May 8th : GDPR tools for Matomo (User guide).

    5 – Subject access requests

    Make sure that you are able to answer an access request from a data subject for Matomo. For example, when a person would like to access her or his personal data that you have collected about her or him, then you will need to be you able to provide her or him with this information. We recommend you design a process for this like “Who is dealing with it ?” and check that it is working. If you can answer to the nightmare letter, then you are ready. The needed features for this in Matomo will be available soon.

    6 – Lawful basis for processing personal data

    There are different lawful basis you can use under GDPR. It can be either “Legitimate interest” or “Explicit consent”. Do not forget to mention it within your privacy policy page. Read more in our article about lawful basis.

    7 – Consent

    Users should be able to remove their consent at any time. By chance, Matomo is providing a feature in order to do just that : add the opt-out feature to your privacy policy page.
    We are also offering a tool that allows you optionally to require consent before any data is tracked. This will be useful if a person should be only tracked after she or he has given explicit consent to be tracked.

    8 – Children

    If your website or app is targeted for children and you are using Matomo, extra measures will need to be taken. For example you will need to write your privacy policy even more clear and moreover getting parents consent if the child is below 13. As it is a very specific case, we strongly recommend you to follow this link for further information.

    9 – Data breaches

    As you may be collecting personal data with Matomo, you should also check your “data breach procedure” to define if a leak may have consequences on the privacy of the data subject. Please consult ICO’s website for further information.

    10 – Data Protection by Design and Data Protection Impact Assessments

    Ask yourself if you really need to process personal data within Matomo. If the data you are processing within Matomo is sensitive, we strongly recommend you to make a Data Protection Impact Assessment. A software is available from the The open source PIA software helps to carry out data protection impact assessment, by French Privacy Commissioner : CNIL.

    11 – Data Protection Officers

    If you are reading this article and you are the Data Protection Officer (DPO), you will not be concerned by this step. If that’s not the case, your duty is to provide to the DPO (if your business has a DPO) our blog post in order for her or him to ask you questions regarding your use of Matomo. Note that your DPO can also be interested in the different data that Matomo can process : “What data does Matomo track ?” (FAQ).

    12 – International

    Matomo data is hosted wherever you want. So according to the location of the data, you will need to show specific safeguard except for EU. For example regarding the USA, you will have to check if your web hosting platform is registered to the Privacy Shield : privacyshield.gov/list
    Note : our Matomo cloud infrastructure is based in France.

    That’s the end of this blog post. As GDPR is a huge topic, we will release many more blog posts in the upcoming weeks. If there are any Matomo GDPR topic related posts you would like us to write, please feel free to contact us.

    The post How to make Matomo GDPR compliant in 12 steps appeared first on Analytics Platform - Matomo.

  • Thread in Thread

    28 mai 2014, par user3679963

    My company is working for visual effects and we set up an internal shot playback via a browser for our clients. For that we need to upload the video file to a FTP server.

    I want to convert a image sequence to mp4 and upload this file directly after the rendering will finish.

    For that I use :

    • one command prompt to convert
    • one command prompt to get an `md5hash
    • one for uploading the file

    I already achieved that on my local computer, where I just chained os.system('command').

    After recognizing that the program freezes very long with longer image sequences I changed the script to spawn a thread using the os.system chain.
    But on the Render Farm Server this script does not actually work.

    The RenderFarm Server runs Python 2.5

    There are some code examples :

    class CopraUpload(threading.Thread):

       # initializing Thread
       # via super constructor
       def __init__(self):
           threading.Thread.__init__(self)


       # return the size of the
       # created mp4 file
       #
       # @return: the file size in byte
       def _getFileSize(self):


       # creates a random id for organising
       # the server upload used as flag
       #
       # @return: a hash
       def _getHash(self):
               self.fileLoc = str(self.outputfileName + '.mp4')
               self.fileLoc = os.path.normpath(self.fileLoc)
               return str(os.path.getsize(self.fileLoc))

       # integrates the "missing" data for the xml file
       # generated post render from the mp4 file
       def _setPreviewDataToXML(self):
           self.xmlFile = str(self.outputfileName + '_copraUpload.xml')
           self.xmlFile = os.path.normpath(self.xmlFile)

           ett = ET.parse(self.xmlFile)
           root = ett.getroot()
           for child in root.getiterator('preview_size'):
               child.text = self._getFileSize()
           for child in root.getiterator('preview_md5hash'):
               child.text = self._getHash()
           ett.write(self.xmlFile)


       # create a connection to a ftp server
       # and copies the mp4 file and the xml file
       # on the server
       def _uploadToCopra(self):

           os.system(self.uploadCommand)
           #process = Popen(self.uploadCommand)


       # the main function of the program
       # called via start from a Thread Object
       def run(self):

           # the command which will be send to the commando shell
           # for further adjustments see ffmpeg help with ffmpeg.exe -h
           FinalCommand = self.ffmpegLocation + " -r "+ self.framerate + " -i " + self.inputPath + " -an -strict experimental -s hd720 -vcodec libx264 -preset slow -profile:v baseline -level 31 -refs 1 -maxrate 6M -bufsize 10M -vb 6M -threads 0 -g 8 -r " + self.framerate + " " + self.outputfileName + ".mp4 -y"
           FinalCommandList = FinalCommand.split(" ")


           # calling the program
           print "Start ffmpeg convertion"

           outInfo = os.path.normpath("C:\\Users\\sarender\\Desktop\\stdoutFFMPEG.txt")
           outError = os.path.normpath("C:\\Users\\sarender\\Desktop\\stderrFFMPEG.txt")
           stdoutFile = open(outInfo,"w")
           stderrFile = open(outError,"w")

           handle = subp.check_all(FinalCommandList,stdout = stdoutFile,stderr = stderrFile)
           handle.communicate()
           stdoutFile.close()
           stderrFile.close()
           print "Convertion from ffmpeg done"

           # fill the xml file with the missing data
           # - preview file size
           # - preview md5hash
           self._setPreviewDataToXML()
           self._uploadToCopra()
           print "---------------------------------->FINISHED------------------------------------------------------>"


       # Creates a callable Thread for the Copra Upload.
       # start is calling the run method which will start the Uploading

    and the main start :

       if "$(RenderSet.writenode)" == "PREVIEW":
           print "---------------------------------->Initializing Script------------------------------------------------------>"
           process = CopraUpload()
           process.start()

    What happens :

    The script starts after the rendering and ffmpeg converts the image sequence and creates an mp4. But it stops after that. It does not print "Conversion from ffmpeg complet". Just stops the script.

    It actually should create the Thread converting with ffmpeg and wait until it finishes. After it should write some stuff in an xml file and upload both to the server.

    Do I miss something ? Is subprocess within a thread not the way to go ? But I need a Thread because I can not deadlock the render management server.

  • Gstreamer channel reordering failed

    31 octobre 2017, par user972851

    I installed the library essentia which causes my previously working pipeline to crash :

    ** (gst-launch-1.0:22515): CRITICAL **: gst_audio_reorder_channels: assertion 'size % ((info->width * channels) / 8) == 0' failed
    ERROR: from element /GstPipeline:pipeline0/GstRtpL16Depay:rtpl16depay0: Channel reordering failed.
    Additional debug info:
    gstrtpL16depay.c(276): gst_rtp_L16_depay_process (): /GstPipeline:pipeline0/GstRtpL16Depay:rtpl16depay0

    The pipeline looks like this :

    udpsrc port=5000 ! application/x-rtp,media=(string)audio,channels=1, clock-rate=(int)44100,encoding-name=(string)L16,payload=10 ! rtpL16depay ! audioconvert ! tee name=t ! queue ! autoaudiosink sync=false t. ! queue ! appsink name=codesink

    I am using gstreamer 1.0 on Ubuntu 16.04 and (re-)installed the libraries mentioned in the essentia doc :

    build-essential libyaml-dev libfftw3-dev libavcodec-dev libavformat-dev libavutil-dev libavresample-dev python-dev libsamplerate0-dev libtag1-dev
    python-numpy-dev python-numpy python-yaml
    ffmpeg

    The essentia install script finished ’successfully’ even though I cannot find MonoLoader or any other Audioloader.... (so still something wrong with essentia as well, but thats not the main problem !)


    Cleaned out parts of the gstreamer debug log look like this :

    0:00:00.149495849 [334m22515[00m       0xd96a00 [37mDEBUG  [00m [00;01;36m  GST_PLUGIN_LOADING gstplugin.c:1549:gst_plugin_ext_dep_scan_dir_and_match_names:<plugin106>[00m g_dir_open(/dev/v4l2) failed: Error opening directory '/dev/v4l2': No such file or directory
    0:00:00.149807870 [334m22515[00m       0xd96a00 [37mDEBUG  [00m [00;01;36m  GST_PLUGIN_LOADING gstplugin.c:1549:gst_plugin_ext_dep_scan_dir_and_match_names:<plugin223>[00m g_dir_open(/home/xxx/.frei0r-1/lib) failed: Error opening directory '/home/xxx/.frei0r-1/lib': No such file or directory
    0:00:00.149823765 [334m22515[00m       0xd96a00 [37mDEBUG  [00m [00;01;36m  GST_PLUGIN_LOADING gstplugin.c:1549:gst_plugin_ext_dep_scan_dir_and_match_names:<plugin223>[00m g_dir_open(/usr/lib/x86_64-linux-gnu/frei0r-1) failed: Error opening directory '/usr/lib/x86_64-linux-gnu/frei0r-1': No such file or directory
    0:00:00.149836069 [334m22515[00m       0xd96a00 [37mDEBUG  [00m [00;01;36m  GST_PLUGIN_LOADING gstplugin.c:1549:gst_plugin_ext_dep_scan_dir_and_match_names:<plugin223>[00m g_dir_open(/usr/lib/frei0r-1) failed: Error opening directory '/usr/lib/frei0r-1': No such file or directory
    0:00:00.149847527 [334m22515[00m       0xd96a00 [37mDEBUG  [00m [00;01;36m  GST_PLUGIN_LOADING gstplugin.c:1549:gst_plugin_ext_dep_scan_dir_and_match_names:<plugin223>[00m g_dir_open(/usr/local/lib/frei0r-1) failed: Error opening directory '/usr/local/lib/frei0r-1': No such file or directory
    0:00:00.149859202 [334m22515[00m       0xd96a00 [37mDEBUG  [00m [00;01;36m  GST_PLUGIN_LOADING gstplugin.c:1549:gst_plugin_ext_dep_scan_dir_and_match_names:<plugin223>[00m g_dir_open(/usr/lib32/frei0r-1) failed: Error opening directory '/usr/lib32/frei0r-1': No such file or directory
    0:00:00.149870221 [334m22515[00m       0xd96a00 [37mDEBUG  [00m [00;01;36m  GST_PLUGIN_LOADING gstplugin.c:1549:gst_plugin_ext_dep_scan_dir_and_match_names:<plugin223>[00m g_dir_open(/usr/local/lib32/frei0r-1) failed: Error opening directory '/usr/local/lib32/frei0r-1': No such file or directory
    0:00:00.149881462 [334m22515[00m       0xd96a00 [37mDEBUG  [00m [00;01;36m  GST_PLUGIN_LOADING gstplugin.c:1549:gst_plugin_ext_dep_scan_dir_and_match_names:<plugin223>[00m g_dir_open(/usr/lib64/frei0r-1) failed: Error opening directory '/usr/lib64/frei0r-1': No such file or directory
    0:00:00.149893070 [334m22515[00m       0xd96a00 [37mDEBUG  [00m [00;01;36m  GST_PLUGIN_LOADING gstplugin.c:1549:gst_plugin_ext_dep_scan_dir_and_match_names:<plugin223>[00m g_dir_open(/usr/local/lib64/frei0r-1) failed: Error opening directory '/usr/local/lib64/frei0r-1': No such file or directory

    0:00:00.186559327 [334m22515[00m       0xf93a80 [33;01mWARN   [00m [00m         rtpL16depay gstrtpL16depay.c:276:gst_rtp_L16_depay_process:<rtpl16depay0>[00m error: Channel reordering failed.
    0:00:00.186574584 [334m22515[00m       0xf93a80 [37mDEBUG  [00m [00;01;37;41m         GST_MESSAGE gstelement.c:1848:gst_element_message_full:<rtpl16depay0>[00m start
    0:00:00.186589070 [334m22515[00m       0xf93a80 [36mINFO   [00m [00;01;31;47m    GST_ERROR_SYSTEM gstelement.c:1879:gst_element_message_full:<rtpl16depay0>[00m posting message: Channel reordering failed.
    0:00:00.186619665 [334m22515[00m       0xf93a80 [33;01mWARN   [00m [00m           structure gststructure.c:1935:priv_gst_structure_append_to_gstring:[00m No value transform to serialize field 'gerror' of type 'GError'
    0:00:00.186613247 [334m22515[00m       0xf93a80 [37mDEBUG  [00m [00;43m             GST_BUS gstbus.c:311:gst_bus_post:<bus1>[00m [msg 0xfc44c0] posting on bus error message: 0xfc44c0, time 99:99:99.999999999, seq-num 59, element 'rtpl16depay0', GstMessageError, gerror=(GError)NULL, debug=(string)"gstrtpL16depay.c\(276\):\ gst_rtp_L16_depay_process\ \(\):\ /GstPipeline:pipeline0/GstRtpL16Depay:rtpl16depay0";
    0:00:00.186641091 [334m22515[00m       0xf93a80 [37mDEBUG  [00m [00;01m                 bin gstbin.c:3533:gst_bin_handle_message_func:<pipeline0>[00m [msg 0xfc44c0] handling child rtpl16depay0 message of type error
    0:00:00.186649484 [334m22515[00m       0xf93a80 [37mDEBUG  [00m [00;01m                 bin gstbin.c:3540:gst_bin_handle_message_func:<pipeline0>[00m got ERROR message, unlocking state change
    0:00:00.186656312 [334m22515[00m       0xf93a80 [37mDEBUG  [00m [00;01m                 bin gstbin.c:3870:gst_bin_handle_message_func:<pipeline0>[00m posting message upward
    0:00:00.186665962 [334m22515[00m       0xf93a80 [33;01mWARN   [00m [00m           structure gststructure.c:1935:priv_gst_structure_append_to_gstring:[00m No value transform to serialize field 'gerror' of type 'GError'
    0:00:00.186662657 [334m22515[00m       0xf93a80 [37mDEBUG  [00m [00;43m             GST_BUS gstbus.c:311:gst_bus_post:<bus2>[00m [msg 0xfc44c0] posting on bus error message: 0xfc44c0, time 99:99:99.999999999, seq-num 59, element 'rtpl16depay0', GstMessageError, gerror=(GError)NULL, debug=(string)"gstrtpL16depay.c\(276\):\ gst_rtp_L16_depay_process\ \(\):\ /GstPipeline:pipeline0/GstRtpL16Depay:rtpl16depay0";
    0:00:00.186688725 [334m22515[00m       0xf93a80 [37mDEBUG  [00m [00;43m             GST_BUS gstbus.c:350:gst_bus_post:<bus2>[00m [msg 0xfc44c0] pushing on async queue
    0:00:00.186706354 [334m22515[00m       0xf93a80 [37mDEBUG  [00m [00;43m             GST_BUS gstbus.c:353:gst_bus_post:<bus2>[00m [msg 0xfc44c0] pushed on async queue
    0:00:00.186713847 [334m22515[00m       0xf93a80 [37mDEBUG  [00m [00;43m             GST_BUS gstbus.c:346:gst_bus_post:<bus1>[00m [msg 0xfc44c0] dropped
    0:00:00.186720541 [334m22515[00m       0xf93a80 [36mINFO   [00m [00;01;31;47m    GST_ERROR_SYSTEM gstelement.c:1902:gst_element_message_full:<rtpl16depay0>[00m posted error message: Channel reordering failed.
    0:00:00.186729277 [334m22515[00m       0xf93a80 [37mDEBUG  [00m [00;01;34m          GST_MEMORY gstmemory.c:87:_gst_memory_free:[00m free memory 0x7f7780004b80
    0:00:00.186737518 [334m22515[00m       0xf93a80 [37mDEBUG  [00m [00;01;35m      GST_SCHEDULING gstpad.c:4192:gst_pad_chain_data_unchecked:[00m called chainfunction &amp;0x7f77a1a9ae00 with buffer 0x7f7780016060, returned ok
    0:00:00.186746868 [334m22515[00m       0xf93a80 [37mDEBUG  [00m [00;01;35m      GST_SCHEDULING gstpad.c:4192:gst_pad_chain_data_unchecked:[00m called chainfunction &amp;gst_base_transform_chain with buffer 0x7f7780016060, returned ok
    0:00:00.186734973 [334m22515[00m       0xd96a00 [37mDEBUG  [00m [00;43m             GST_BUS gstbus.c:523:gst_bus_timed_pop_filtered:<bus2>[00m got message 0xfc44c0, error from rtpl16depay0, type mask is 4294967295
    0:00:00.186759208 [334m22515[00m       0xf93a80 [37mDEBUG  [00m [00m             basesrc gstbasesrc.c:2456:gst_base_src_get_range:<udpsrc0>[00m calling create offset 18446744073709551615 length 4096, time 0
    0:00:00.186808915 [334m22515[00m       0xf93a80 [37mDEBUG  [00m [00;01;34m          GST_MEMORY gstmemory.c:138:gst_memory_init:[00m new memory 0x7f7780017ae0, maxsize:901 offset:0 size:894
    0:00:00.186812210 [334m22515[00m       0xd96a00 [33;01mWARN   [00m [00m           structure gststructure.c:1935:priv_gst_structure_append_to_gstring:[00m No value transform to serialize field 'gerror' of type 'GError'
    0:00:00.186798035 [334m22515[00m       0xd96a00 [37mDEBUG  [00m [00;43m             GST_BUS gstbus.c:791:gst_bus_source_dispatch:<bus2>[00m source 0xfc0b60 calling dispatch with error message: 0xfc44c0, time 99:99:99.999999999, seq-num 59, element 'rtpl16depay0', GstMessageError, gerror=(GError)NULL, debug=(string)"gstrtpL16depay.c\(276\):\ gst_rtp_L16_depay_process\ \(\):\ /GstPipeline:pipeline0/GstRtpL16Depay:rtpl16depay0";


    0:00:00.187438285 [334m22515[00m       0xf93a80 [33;01mWARN   [00m [00m         rtpL16depay gstrtpL16depay.c:276:gst_rtp_L16_depay_process:<rtpl16depay0>[00m error: Channel reordering failed.

    0:00:00.187861496 [334m22515[00m       0xf93a80 [36mINFO   [00m [00;01;31;47m    GST_ERROR_SYSTEM gstelement.c:1879:gst_element_message_full:<rtpl16depay0>[00m posting message: Channel reordering failed.
    0:00:00.187870817 [334m22515[00m       0xd96a00 [37mDEBUG  [00m [00;01;31m          GST_STATES gstelement.c:2523:gst_element_set_state_func:<autoaudiosink0>[00m set_state to PAUSED
    0:00:00.187917831 [334m22515[00m       0xd96a00 [37mDEBUG  [00m [00;01;31m          GST_STATES gstelement.c:2561:gst_element_set_state_func:<autoaudiosink0>[00m current READY, old_pending PAUSED, next PAUSED, old return ASYNC
    0:00:00.187926145 [334m22515[00m       0xd96a00 [37mDEBUG  [00m [00;01;31m          GST_STATES gstelement.c:2615:gst_element_set_state_func:<autoaudiosink0>[00m element was busy with async state change
    0:00:00.187931662 [334m22515[00m       0xf93a80 [33;01mWARN   [00m [00m           structure gststructure.c:1935:priv_gst_structure_append_to_gstring:[00m No value transform to serialize field 'gerror' of type 'GError'
    0:00:00.187932562 [334m22515[00m       0xd96a00 [36mINFO   [00m [00;01;31m          GST_STATES gstbin.c:2770:gst_bin_change_state_func:<pipeline0>[00m child 'autoaudiosink0' is changing state asynchronously to PAUSED
    0:00:00.187919799 [334m22515[00m       0xf93a80 [37mDEBUG  [00m [00;43m             GST_BUS gstbus.c:311:gst_bus_post:<bus1>[00m [msg 0xfc4540] posting on bus error message: 0xfc4540, time 99:99:99.999999999, seq-num 60, element 'rtpl16depay0', GstMessageError, gerror=(GError)NULL, debug=(string)"gstrtpL16depay.c\(276\):\ gst_rtp_L16_depay_process\ \(\):\ /GstPipeline:pipeline0/GstRtpL16Depay:rtpl16depay0";
    0:00:00.187957346 [334m22515[00m       0xd96a00 [37mDEBUG  [00m [00;01m                 bin gstbin.c:2182:gst_bin_sort_iterator_next:<pipeline0>[00m queue head gives queue0
    0:00:00.187965818 [334m22515[00m       0xf93a80 [37mDEBUG  [00m [00;01m                 bin gstbin.c:3533:gst_bin_handle_message_func:<pipeline0>[00m [msg 0xfc4540] handling child rtpl16depay0 message of type error
    0:00:00.187975510 [334m22515[00m       0xd96a00 [37mDEBUG  [00m [00;01m                 bin gstbin.c:882:find_message:<pipeline0>[00m no message found matching types 00001000
    0:00:00.187996861 [334m22515[00m       0xd96a00 [37mDEBUG  [00m [00;01m                 bin gstbin.c:889:find_message:<pipeline0>[00m   structure-change
    0:00:00.188003444 [334m22515[00m       0xd96a00 [37mDEBUG  [00m [00;01m                 bin gstbin.c:2098:update_degree:<pipeline0>[00m change element audioconvert0, degree 1->0, linked to queue0
    0:00:00.188010702 [334m22515[00m       0xd96a00 [37mDEBUG  [00m [00;01m                 bin gstbin.c:1981:add_to_queue:<pipeline0>[00m adding 'audioconvert0' to queue
    0:00:00.188019716 [334m22515[00m       0xd96a00 [36mINFO   [00m [00;01;31m          GST_STATES gstbin.c:2316:gst_bin_element_set_state:<queue0>[00m current PLAYING pending VOID_PENDING, desired next PAUSED
    0:00:00.188021589 [334m22515[00m       0xf93a80 [37mDEBUG  [00m [00;01m                 bin gstbin.c:3540:gst_bin_handle_message_func:<pipeline0>[00m got ERROR message, unlocking state change

    0:00:00.188204142 [334m22515[00m       0xf93a80 [33;01mWARN   [00m [00m           structure gststructure.c:1935:priv_gst_structure_append_to_gstring:[00m No value transform to serialize field 'gerror' of type 'GError'

    0:00:00.188196343 [334m22515[00m       0xf93a80 [37mDEBUG  [00m [00;43m             GST_BUS gstbus.c:311:gst_bus_post:<bus2>[00m [msg 0xfc4540] posting on bus error message: 0xfc4540, time 99:99:99.999999999, seq-num 60, element 'rtpl16depay0', GstMessageError, gerror=(GError)NULL, debug=(string)"gstrtpL16depay.c\(276\):\ gst_rtp_L16_depay_process\ \(\):\ /GstPipeline:pipeline0/GstRtpL16Depay:rtpl16depay0";

    0:00:00.188532703 [334m22515[00m       0xf93a80 [36mINFO   [00m [00;01;31;47m    GST_ERROR_SYSTEM gstelement.c:1902:gst_element_message_full:<rtpl16depay0>[00m posted error message: Channel reordering failed.

    0:00:00.199466751 [334m22515[00m       0xd96a00 [37mDEBUG  [00m [00;43m             GST_BUS gstbus.c:523:gst_bus_timed_pop_filtered:<bus2>[00m got message 0xfc4540, error from rtpl16depay0, type mask is 4294967295

    0:00:00.203389413 [334m22515[00m       0xd96a00 [37mDEBUG  [00m [00;01;36m  GST_PLUGIN_LOADING gstpluginfeature.c:66:gst_plugin_feature_finalize:[00m finalizing feature 0xf69ea0: 'errorignore'
    </bus2></rtpl16depay0></bus2></pipeline0></queue0></pipeline0></pipeline0></pipeline0></pipeline0></pipeline0></pipeline0></bus1></pipeline0></autoaudiosink0></autoaudiosink0></autoaudiosink0></rtpl16depay0></rtpl16depay0></bus2></udpsrc0></bus2></rtpl16depay0></bus1></bus2></bus2></bus2></pipeline0></pipeline0></pipeline0></bus1></rtpl16depay0></rtpl16depay0></rtpl16depay0></plugin223></plugin223></plugin223></plugin223></plugin223></plugin223></plugin223></plugin223></plugin106>