Recherche avancée

Sur d’autres sites (3983)

• MPEG Dash output generated by FFMPEG not working

  8 janvier 2019, par Anto Joy

  I created a dash output sample_video.mpd file using ffmpeg, but when I tried to play it using dash js the video was just loading and nothing else.
  Below is the generated mpd file

  <?xml version="1.0" encoding="utf-8"?>
  
  <mpd xmlns="urn:mpeg:dash:schema:mpd:2011" profiles="urn:mpeg:dash:profile:isoff-live:2011" type="static" mediapresentationduration="PT1M2.3S" minbuffertime="PT20.0S">
  
  <programinformation>
  
  </programinformation>
  
  <period start="PT0.0S">
  
      <adaptationset contenttype="video" segmentalignment="true" bitstreamswitching="true" lang="und">
  
          <representation mimetype="video/mp4" codecs="avc1.640015" bandwidth="255520" width="426" height="240" framerate="24/1">
  
              <segmenttemplate timescale="12288" initialization="init-stream$RepresentationID$.m4s" media="chunk-stream$RepresentationID$-$Number%05d$.m4s" startnumber="3">
  
                  <segmenttimeline>
  
                      <s t="198656" d="69120"></s>
  
                      <s d="75264"></s>
  
                      <s d="174592"></s>
  
                      <s d="122880"></s>
  
                      <s d="125440"></s>
  
                  </segmenttimeline>
  
              </segmenttemplate>
  
          </representation>
  
          <representation mimetype="video/mp4" codecs="avc1.64001e" bandwidth="726596" width="854" height="480" framerate="24/1">
  
              <segmenttemplate timescale="12288" initialization="init-stream$RepresentationID$.m4s" media="chunk-stream$RepresentationID$-$Number%05d$.m4s" startnumber="3">
  
                  <segmenttimeline>
  
                      <s t="198656" d="69120"></s>
  
                      <s d="75264"></s>
  
                      <s d="174592"></s>
  
                      <s d="122880"></s>
  
                      <s d="125440"></s>
  
                  </segmenttimeline>
  
              </segmenttemplate>
  
          </representation>
  
          <representation mimetype="video/mp4" codecs="avc1.64001f" bandwidth="1433314" width="1280" height="720" framerate="24/1">
  
              <segmenttemplate timescale="12288" initialization="init-stream$RepresentationID$.m4s" media="chunk-stream$RepresentationID$-$Number%05d$.m4s" startnumber="3">
  
                  <segmenttimeline>
  
                      <s t="198656" d="69120"></s>
  
                      <s d="75264"></s>
  
                      <s d="174592"></s>
  
                      <s d="122880"></s>
  
                      <s d="125440"></s>
  
                  </segmenttimeline>
  
              </segmenttemplate>
  
          </representation>
  
      </adaptationset>
  
      <adaptationset contenttype="audio" segmentalignment="true" bitstreamswitching="true" lang="und">
  
          <representation mimetype="audio/mp4" codecs="mp4a.40.2" bandwidth="341000" audiosamplingrate="48000">
  
              <audiochannelconfiguration schemeiduri="urn:mpeg:dash:23003:3:audio_channel_configuration:2011" value="6"></audiochannelconfiguration>
  
              <segmenttemplate timescale="48000" initialization="init-stream$RepresentationID$.m4s" media="chunk-stream$RepresentationID$-$Number%05d$.m4s" startnumber="3">
  
                  <segmenttimeline>
  
                      <s t="772096" d="270336"></s>
  
                      <s d="293888"></s>
  
                      <s d="681984"></s>
  
                      <s d="480256"></s>
  
                      <s d="492544"></s>
  
                  </segmenttimeline>
  
              </segmenttemplate>
  
          </representation>
  
          <representation mimetype="audio/mp4" codecs="mp4a.40.2" bandwidth="341000" audiosamplingrate="48000">
  
              <audiochannelconfiguration schemeiduri="urn:mpeg:dash:23003:3:audio_channel_configuration:2011" value="6"></audiochannelconfiguration>
  
              <segmenttemplate timescale="48000" initialization="init-stream$RepresentationID$.m4s" media="chunk-stream$RepresentationID$-$Number%05d$.m4s" startnumber="3">
  
                  <segmenttimeline>
  
                      <s t="772096" d="270336"></s>
  
                      <s d="293888"></s>
  
                      <s d="681984"></s>
  
                      <s d="480256"></s>
  
                      <s d="492544"></s>
  
                  </segmenttimeline>
  
              </segmenttemplate>
  
          </representation>
  
          <representation mimetype="audio/mp4" codecs="mp4a.40.2" bandwidth="341000" audiosamplingrate="48000">
  
              <audiochannelconfiguration schemeiduri="urn:mpeg:dash:23003:3:audio_channel_configuration:2011" value="6"></audiochannelconfiguration>
  
              <segmenttemplate timescale="48000" initialization="init-stream$RepresentationID$.m4s" media="chunk-stream$RepresentationID$-$Number%05d$.m4s" startnumber="3">
  
                  <segmenttimeline>
  
                      <s t="772096" d="270336"></s>
  
                      <s d="293888"></s>
  
                      <s d="681984"></s>
  
                      <s d="480256"></s>
  
                      <s d="492544"></s>
  
                  </segmenttimeline>
  
              </segmenttemplate>
  
          </representation>
  
      </adaptationset>
  
  </period>
  
  </mpd>

  The following is the ffmpeg command that i used to generate multi bitrate video

  ffmpeg -y -i sample_video.mp4 ^
  
  -c:v libx264 -x264opts "keyint=24:min-keyint=24:no-scenecut" -r 24 ^
  
  -c:a aac -b:a 128k ^
  
  -bf 1 -b_strategy 0 -sc_threshold 0 -pix_fmt yuv420p ^
  
  -map 0:v:0 -map 0:a:0 -map 0:v:0 -map 0:a:0 -map 0:v:0 -map 0:a:0 ^
  
  -b:v:0 250k  -filter:v:0 "scale=-2:240" -profile:v:0 baseline ^
  
  -b:v:1 750k  -filter:v:1 "scale=-2:480" -profile:v:1 main ^
  
  -b:v:2 1500k -filter:v:2 "scale=-2:720" -profile:v:2 high ^
  
  sample_dash.mp4

  and to generate the mpd file

  ffmpeg -y -re -i sample_dash.mp4 ^
  
  -map 0 ^
  
  -use_timeline 1 -use_template 1 -window_size 5 -adaptation_sets 
  
  "id=0,streams=v id=1,streams=a" ^
  
  -f dash sample_video.mpd

  Also I saw in the chrome network tab that only init-stream4.m4s and init-stream5.m4s was called.

• ffmpeg : VLC won’t open .sdp files generated by ffmpeg

  8 mai 2020, par tiredamage42

  TLDR : VLC or Quicktime won’t open .sdp video stream files generated by ffmpeg, even though ffplay does.

  



  Web development and ffmpeg noob, so apologies if I’m using the wrong terminology :

  



  I’m trying to stream my desktop capture (on OSX) using ffmpeg, sending it out via rtp protocol. 
As of right now I’m just testing it out by streaming it over a port in my localhost (4000). And trying to play it locally.

  



  The problem is that when I try and open the .sdp file generated by the ffmpeg command, VLC opens it and immediately stops, no errors or anything, and shows that it has a duration of 0:00. Quicktime won’t event open the file in the first place.

  



  ffplay does play the stream and I can see my desktop in the player window (with a significant loss in quality though). Even so there are a ton of warning and errors that show up intermittently (outlined below)

  



  I’m not sure if it’s a problem in the way I start the ffmpeg stream, the command is after a ton of iterations of trying to just make it work, so my options might be way wrong.

  



  command to 'serve' the desktop capture :

  



  ./ffmpeg -f avfoundation -s 1920x1080 -r 60 -i "1" -an \
-vcodec libx264 -preset ultrafast -tune zerolatency -pix_fmt yuv420p \
-sdp_file video.sdp -rtsp_transport tcp -f rtp rtp://127.0.0.1:4000


  



  SDP file that’s generated with the ffmpeg command :

  



  SDP:
v=0
o=- 0 0 IN IP4 127.0.0.1
s=No Name
c=IN IP4 127.0.0.1
t=0 0
a=tool:libavformat 58.29.100
m=video 4000 RTP/AVP 96
a=rtpmap:96 H264/90000
a=fmtp:96 packetization-mode=1


  



  ffplay command used to play the stream :

  



  ./ffplay -probesize 32 -analyzeduration 0 -sync ext \
-fflags nobuffer -fflags discardcorrupt -flags low_delay -framedrop \
-strict experimental -avioflags direct \
-protocol_whitelist file,rtp,udp -I video.sdp


  



  For a while before ffplay starts I see a bunch of these errors repeating (in red) :

  



  [h264 @ 0x7ff6b788de00] non-existing PPS 0 referenced
[h264 @ 0x7ff6b788de00] decode_slice_header error
[h264 @ 0x7ff6b788de00] no frame!


  



  then the window seems to 'catch up' to the stream and actually shows the desktop capture, and I get these errors and warnings on a regular interval :

  



  1- in a yellow warning color :

  



  [sdp @ 0x7fc85b830600] RTP: missed 4 packets
[sdp @ 0x7fc85b830600] max delay reached. need to consume packet


  



  2-in a red error color :

  



  [h264 @ 0x7fc85b02aa00] out of range intra chroma pred mode
[h264 @ 0x7fc85b02aa00] error while decoding MB 132 32


  



  (I have a feeling that the above errors have to do with previewing the desktop capture in the desktop I’m capturing and causing pixels in the display to overflow)

  



  Edit :
So, I solved the issue soon after posting, but will leave this up in case anyone runs into the same problem.

  



  The solution was to remove the top line in the .sdp file that said SDP:

  


• Google Analytics Now Illegal in Austria ; Other EU Member States Expected to Follow

  18 janvier 2022, par Erin — Privacy

  Breaking news : The Austrian Data Protection Authority (“Datenschutzbehörde” or “DSB” or “DPA”) has ruled that Austrian website providers using Google Analytics are in violation of the GDPR. 

  This ruling stems from a decision made in 2020 by the Court of Justice of the European Union (CJEU) that stated that cloud services hosted in the US are incapable of complying with the GDPR and EU privacy laws. The decision was made because of the US surveillance laws requiring US providers (like Google or Facebook) to provide personal data to US authorities. 

  The 2020 ruling, known as “Schrems II”, marked the ending of the Privacy Shield, a framework that allowed for EU data to be transferred to US companies that became certified. 

  The tech industry was sent into a frenzy following this decision, but many US and EU companies decided to ignore the case. The choice to ignore is what landed one Austrian business in the DPA’s line of fire, damaging the brand’s reputation and possibly resulting in a hefty fine of up to €20 million or 4% of the organisation’s global turnover. 

  About the Austrian DPA’s Model Case 

  In this specific case, noyb (the European Center for Digital Rights) found that IP addresses (which are classified as personal data by the GDPR) and other identifiers were sent to the US in cookie data as a result of the organisation using Google Analytics. 

  This model case led to the DPA’s decision to rule that Austrian website providers using Google Analytics are in violation of GDPR. It is believed that other EU Member States will soon follow in this decision as well.

  "We expect similar decisions to now drop gradually in most EU member states. We have filed 101 complaints in almost all Member States and the authorities coordinated the response. A similar decision was also issued by the European Data Protection Supervisor last week."

  What does this mean if you are using Google Analytics ?

  If there is one thing to learn from this case, it is that ignoring these court rulings and continuing to use Google Analytics is not a viable option. 

  If you are operating a website in Austria, or your website services Austrian citizens, you should remove Google Analytics from your website immediately. 

  For businesses in other EU Member States, it is also highly recommended that you take action before noyb and local data protection authorities start targeting more businesses. 

  "Instead of actually adapting services to be GDPR compliant, US companies have tried to simply add some text to their privacy policies and ignore the Court of Justice. Many EU companies have followed the lead instead of switching to legal options."

  Removing Google Analytics from your site doesn’t mean that you need to give up website analytics altogether though. There are a variety of Google Analytics alternatives available today. Matomo in particular is a powerful open-source web analytics platform that gives you 100% data ownership and GDPR compliance. 

  

  Matomo is one of the best Google Analytics alternatives offering privacy by design on our Cloud, On-Premise and Matomo for WordPress. So you can get the insights you need while remaining compliant. As the GDPR continues to evolve, you can rest assured that Matomo will be at the forefront of these changes. 

  In addition, all Google Analytics data can be imported into Matomo so no historical data is lost. To make your migration as seamless as possible, we’ve put together a guide to migrating from Google Analytics to Matomo. 

  Ready to begin your journey to GDPR compliance ? Check out our live demo and start your 21-day free trial now – no credit card required.

  If you are interested in learning more about GDPR compliance and Matomo, check out our GDPR resources below :    

  • GDPR Manager user guide
  • How to fill in the information asset registration when using Matomo
  • How to make Matomo GDPR compliant in 12 easy steps
  • How to not process any personal data with Matomo and what it means for you
  • PII, personal data and GDPR. Discover what this means for your privacy
  • How should I write my privacy notice for Matomo Analytics under GDPR
  • Lawful basis for processing personal data under GDPR with Matomo
  • How to complete your privacy policy with Matomo Analytics under GDPR
  • GDPR compliance for Premium Features
  • How to get your Matomo plugin ready for GDPR
  • Subprocessors on Matomo Cloud (subprocessors not applicable to On-Premise)
  • Privacy in Matomo

  What does this mean if you are using Matomo ? 

  Our users can rest assured that Matomo remains in compliance with GDPR as all data is stored in the EU (Matomo Cloud) or in any country of your choice (Matomo On-Premise). With Matomo you’re able to continue analysing your website and not worry about GDPR.

  Final thoughts

  For EU businesses operating websites, now is the time to act. While Google pushes out false narratives to try and convince users that it is safe to continue using Google Analytics, it’s clear from these court rulings that the data protection authorities across the EU disagree with Google’s narrative.

  The fines, reputational damage and stresses mounting from using Google Analytics are imminent. Find an alternative to Google Analytics as this problem is not going away. 

  Getting started with Matomo is easy. Make the switch today and start your free 21-day trial – no credit card required.