Recherche avancée

Sur d’autres sites (12115)

• Revision 3e9cbd13236c73cb3cb79e433dc5b314edb3d4ec : Améliorer le comptage des liens entrants dans les stats (merci Daniel ...

  20 juin 2010, par davux — Log

  Améliorer le comptage des liens entrants dans les stats (merci Daniel Déchelotte) Explication de l’auteur du correctif : Le test ($n == $limit) compare le nombre maximal de visites renvoyées à un nombre de hosts après agrégation, donc s’évalue presque toujours à faux. Je propose de toujours afficher le (...)

• MPEG DASH - do I need to have audio and video tracks as seperate source file for creating DASH package using mp4box

  10 juillet 2016, par Tarun

  I have one source mp4, I tried to create MPEG DASH package using mp4box by GPAC.
  I am able to play output MPD files in OSMO4 player by GPAC.

  However I am not able to play the same in DASH JS player @ http://dashif.org/reference/players/javascript/0.2.3/index.html

  When I try to play the mpd in it I get error "Error creating source buffer"

  I tried reading their MPD files, and I found that those guys are using audio and video as separate source track.

  Ques1) Does DASH specs states that audio and video tracks should be seprate source tracks ?

  Ques2) Please find below the MPD file created by me, Let me know if anybody thinks that there is a problem in it

  <mpd type="static" xmlns="urn:mpeg:DASH:schema:MPD:2011" profiles="urn:mpeg:dash:profile:full:2011" minbuffertime="PT1.5S" mediapresentationduration="PT0H2M31.63S">
  
  <programinformation moreinformationurl="http://gpac.sourceforge.net">
  
  
  
  </programinformation>
  
   <period start="PT0S" duration="PT0H2M31.63S">
  
    <adaptationset>
  
  <contentcomponent contenttype="video"></contentcomponent>
  
  <contentcomponent contenttype="audio" lang="und"></contentcomponent>
  
  <segmenttemplate initialization="flight_init.mp4"></segmenttemplate>
  
  <representation mimetype="video/mp4" codecs="avc1.64001f,mp4a.40.02" width="1280" height="720" samplerate="44100" numchannels="2" lang="und" startwithsap="1" bandwidth="3096320">
  
  <segmenttemplate timescale="1000" duration="20164" media="flight_test_flight_3000$Number$.mp4" startnumber="1"></segmenttemplate>
  
  </representation>
  
  <representation mimetype="video/mp4" codecs="avc1.64001e,mp4a.40.02" width="640" height="360" samplerate="44100" numchannels="2" lang="und" startwithsap="1" bandwidth="1119428">
  
  <segmenttemplate timescale="1000" duration="20099" media="flight_test_flight_1000$Number$.mp4" startnumber="1"></segmenttemplate>
  
  </representation>
  
  <representation mimetype="video/mp4" codecs="avc1.640014,mp4a.40.02" width="320" height="180" samplerate="44100" numchannels="2" lang="und" startwithsap="1" bandwidth="722208">
  
  <segmenttemplate timescale="1000" duration="20164" media="flight_test_flight_600$Number$.mp4" startnumber="1"></segmenttemplate>
  
  </representation>
  
  </adaptationset>
  
  </period> 
  
  </mpd>

• ffmpeg (fluent ffmpeg) wrong length while converting mp4 (or mp3) to wav

  18 février 2019, par almarc

  The code :

  ytdl(URL, { quality: "18" })
  
      .pipe(fs.createWriteStream('song.mp4')).on("finish", () => {
  
          var mp4 = "song.mp4"
  
  
  
          ffmpeg({ source:mp4 })
  
          .inputFormat('mp4')
  
          .format('wav')
  
          .on('error', (err) => console.error(err))
  
          .on('end', () => console.log('Finished!'))
  
          .pipe(fs.createWriteStream('song.wav'), {
  
              end: true
  
          });
  
      })

  First it downloads an MP4 file from YouTube, using the ytdl library. Then, when the downloading is finished (the .mp4 file’s length is correct, 5 minutes), using the fluent-ffmpeg library, it converts the .mp4 file to .wav. No errors, it’s succesfull. But the .wav file is almost 7 hours long.
  The first 5 minutes are good, the content from that .mp4 file. Then, everything further is empty.

  I also tried to first convert it to .mp3, and then to .wav, but the results are still the same. 7 hour long track.

  Using ffmpeg from the command line gives the same results.