Recherche avancée

Sur d’autres sites (12993)

• Where to store the .mpd file on django to play on a dash player ?

  3 janvier 2019, par enigmaVada

  I am trying to build a video player on django. I am using MPEG-DASH for adaptive streaming of the video file. I have chosen a sample video in the beginning. Then, using ffmpeg commands, I have encoded the video into 240p, 360p, 480p and 720p videos. Also have encoded audio separately.

  Then, using mp4box, I have generated the .mpd file. I have read that mpd files cannot be run from the local file system and need to be hosted on a server. I have a dash player setup as follows :

    
  
      
  
      
  
      <code class="echappe-js">&lt;script src=&quot;https://cdn.dashjs.org/latest/dash.all.min.js&quot;&gt;&lt;/script&gt;
  
         
     
  

  The url in the src field is a random manifest file that i used to test the player out. It works fine.

  Then, on my django project, I have created a media folder which stores the media files uploaded via a form(root included in settings.py).
  My question is where do i store the video, audio and .mpd file so that i can play them using the html code which resides in the templates folder. I have tried using the media url of .mpd file in the source but I am unable to play the video.

  Here is the generated mpd file for reference :

  <?xml version="1.0"?>
  
  
  
  <mpd xmlns="urn:mpeg:dash:schema:mpd:2011" minbuffertime="PT1.500S" type="static" mediapresentationduration="PT0H1M9.869S" maxsegmentduration="PT0H0M9.985S" profiles="urn:mpeg:dash:profile:isoff-on-demand:2011,http://dashif.org/guidelines/dash264">
  
   <programinformation moreinformationurl="http://gpac.io">
  
    
  
   </programinformation>
  
  
  
   <period duration="PT0H1M9.869S">
  
    <adaptationset segmentalignment="true" lang="und" subsegmentalignment="true" subsegmentstartswithsap="1">
  
     <representation mimetype="audio/mp4" codecs="mp4a.40.2" audiosamplingrate="44100" startwithsap="1" bandwidth="130920">
  
      <audiochannelconfiguration schemeiduri="urn:mpeg:dash:23003:3:audio_channel_configuration:2011" value="2"></audiochannelconfiguration>
  
      <baseurl>sample_audio_dashinit.mp4</baseurl>
  
      <segmentbase indexrangeexact="true" indexrange="902-1017">
  
        <initialization range="0-901"></initialization>
  
      </segmentbase>
  
     </representation>
  
    </adaptationset>
  
    <adaptationset segmentalignment="true" group="1" maxwidth="426" maxheight="240" maxframerate="30" par="426:240" lang="und" subsegmentalignment="true" subsegmentstartswithsap="1">
  
     <representation mimetype="video/mp4" codecs="avc1.640015" width="426" height="240" framerate="30" sar="1:1" startwithsap="1" bandwidth="590708">
  
      <baseurl>sample_video_240_dashinit.mp4</baseurl>
  
      <segmentbase indexrangeexact="true" indexrange="914-1053">
  
        <initialization range="0-913"></initialization>
  
      </segmentbase>
  
     </representation>
  
    </adaptationset>
  
    <adaptationset segmentalignment="true" group="1" maxwidth="640" maxheight="480" maxframerate="30" par="4:3" lang="und" subsegmentalignment="true" subsegmentstartswithsap="1">
  
     <representation mimetype="video/mp4" codecs="avc1.64001E" width="480" height="360" framerate="30" sar="1:1" startwithsap="1" bandwidth="883873">
  
      <baseurl>sample_video_360_dashinit.mp4</baseurl>
  
      <segmentbase indexrangeexact="true" indexrange="914-1053">
  
        <initialization range="0-913"></initialization>
  
      </segmentbase>
  
     </representation>
  
     <representation mimetype="video/mp4" codecs="avc1.64001E" width="640" height="480" framerate="30" sar="1:1" startwithsap="1" bandwidth="1188712">
  
      <baseurl>sample_video_480_dashinit.mp4</baseurl>
  
      <segmentbase indexrangeexact="true" indexrange="913-1052">
  
        <initialization range="0-912"></initialization>
  
      </segmentbase>
  
     </representation>
  
    </adaptationset>
  
    <adaptationset segmentalignment="true" group="1" maxwidth="1280" maxheight="720" maxframerate="30" par="16:9" lang="und" subsegmentalignment="true" subsegmentstartswithsap="1">
  
     <representation mimetype="video/mp4" codecs="avc1.64001F" width="1280" height="720" framerate="30" sar="1:1" startwithsap="1" bandwidth="2365717">
  
      <baseurl>sample_video_720_dashinit.mp4</baseurl>
  
      <segmentbase indexrangeexact="true" indexrange="914-1053">
  
        <initialization range="0-913"></initialization>
  
      </segmentbase>
  
     </representation>
  
    </adaptationset>
  
   </period>
  
  </mpd>

• lavc/vvc : Ensure subpictures don't overlap

  22 février, par Frank Plowman

  lavc/vvc : Ensure subpictures don't overlap
  This is essentially a re-implementation of
  
  https://patchwork.ffmpeg.org/project/ffmpeg/patch/20241005223955.54158-1-post@frankplowman.com/
  That patch was not applied last time.  Instead we opted to identify
  
  issues which could be caused by invalid subpicture layouts and remedy
  
  those issues where they manifest, either through error detection or code
  
  hardening.  This was primarily implemented in the set
  
  https://patchwork.ffmpeg.org/project/ffmpeg/list/?series=13381.
  This has worked to some degree, however issues with subpicture layouts
  
  continue to crop up from the fuzzer and I've fixed a number of bugs
  
  related to subpicture layouts since then.  I think it's best to return
  
  to the initial plan and simply check if the subpicture layout is valid
  
  initially.
  This implementation is also lighter than the first time — by doing a
  
  bit more logic in pps_subpic_less_than_one_tile_slice, we are able to
  
  store a tile_in_subpic map rather than a ctu_in_subpic map.  This
  
  reduces the size of the map to the point it becomes possible to allocate
  
  it on the stack.  Similar to 8bd66a8c9587af61c7b46558be3c4ee317c1af5a,
  
  the layout is also validated in the slice map construction code, rather
  
  than in the CBS, which avoids duplicating some logic.
  Signed-off-by : Frank Plowman <post@frankplowman.com>
  

  • [DH] libavcodec/vvc/ps.c

• Video won't play with Android's native MediaPlayer, however it plays with Dropbox's video player

  12 novembre 2014, par Nachi

  I’m having trouble playing a certain .3gp file (from a Dropbox link) with Android’s MediaPlayer. However the file magically plays without problems from the Dropbox Android app.

  I’m trying to play it using this :

  Intent intent = new Intent(android.content.Intent.ACTION_VIEW);
  
  intent.setData(Uri.parse("https://www.dropbox.com/s/zpiqwmxka6llavt/SketchyFile.3gp"));
  
  startActivity(intent);

  and my manifest contains

  which gives a "Can’t play this video" error.

  

  Logcat shows :

  I/NuCachedSource2(89): new range: offset= 2245017
  
  I/ChromiumHTTPDataSource(89): connect to https://dl.dropbox.com/0/view/a1crokuhpprsaeo/SketchyFile.3gp @2245017
  
  I/NuCachedSource2(89): ERROR_END_OF_STREAM
  
  E/MediaPlayer(3629): error (1, -2147483648)
  
  E/MediaPlayer(3629): Error (1,-2147483648)
  
  D/VideoView(3629): Error: 1,-2147483648

  If I try to play it from the Dropbox Android app, Dropbox’s video player has no problem playing it.

  

  According to ffmpeg’s ffprobe tool I could verify that the media type is not something exotic to Android.

  Is Dropbox performing some weird transcoding voodoo and is there a way I can make this work in a similar way ?

  EDIT : Here’s some more insight into DropBox’s encoding voodoo.