Recherche avancée

Sur d’autres sites (9090)

• How can I record video with FFMPEG in ISO BMFF format ready for Media Source Extensions ?

  17 novembre 2015, par Matt

  I’m trying to record video using ffmpeg and then play it back on a player using MSE. Here’s the script I’m using :

   ffmpeg -i /dev/video0 -c:v libx264 -profile:v baseline -level:v 13 -g 250 -r 25 -keyint_min 250 -strict experimental -pix_fmt yuv420p -movflags frag_keyframe+empty_moov -b:a 96k sintel.mp4

  This works except for the fact that there is an mfra box at the end of the video file, which I believe is not supported by MSE. How can I remove this mfra box ?

• How to seek mp4 aac audio using Media Source Extensions

  29 août 2018, par Chris

  Please can someone offer me a few pointers when trying to seek within streamed aac audio in mp4 containers ? I’m trying to develop a music download service that sips data via ranged requests rather than simply link to a mp4 file as an <audio></audio> src. (which will instead buffer the whole file as quickly as possible, and so be rather wasteful and expensive).

  So far I’ve managed to successfully append sequential audio range buffers to the SourceBuffer object using partial/ranged requests, attached to my suitably mime-typed MediaSource object. But as soon as I try to seek, the wheels come off and I receive a ’CHUNK_DEMUXER_ERROR_APPEND_FAILED’ error, with the specific issue : ’stream parsing failed’.

  I’ve prepared my mp4 files by encoding them with ffmpeg (via the fluent ffmpeg module), rewriting the movie header box at the start of the file (via the -movflags faststart setting) so that the duration can be parsed. I then fragment the file with mp4fragment (part of the Bento4 tools) with the default settings, and check to ensure the structure of the file matches the format specified by ISO BMFF, with pairs of movie fragments and data boxes (moof/mdat) describing the audio stream. Given the source buffer has no problem playing from the beginning, with contiguous subsequent ranges, this appears to confirm that the format of the mp4 file is acceptable.

  As an aside, I’ve tried fragmenting the file completely in ffmpeg/fluent ffmpeg (using the ’-movflags empty_moov+default_base_moof’ options), but while this works, it also removes the duration from the moov as you’d expect, so the file gets larger during playback as more fragments are fetched and appended. If I set the file duration manually, I still have the issue of not being able to seek to unbuffered audio, so I only seem to be making life more difficult trying to fragment the file solely in ffmpeg.

  So how should I go about seeking within the stream ? I gather that seeking effectively ’needle-drops’ randomly, and so the source buffer might struggle to parse the data out of context, but I imagined that it would skip to the next available fragment in the range that I fetch (which is calculated using the percentage of the seek bar width to set the player.currentTime, which is then converted to a suitable byte range using the 128kbps CBR figure to convert seconds to bytes, to send a 206 partial range request).

  I’ve seen mention of buffer offsets, but I don’t understand how these apply. Most of the dev examples I’ve seen just focus on whole files or segmented videos, rather than fragmented single audio files for seeking ? Do I need to somehow retain a portion of the data from the moov box when seeking for the source buffer to be able to parse it ? In the trun box I have a data offset that varies between two values throughout the file, 444 and 448, depending on whether the sample count is 86 or 87. I’m not sure why it’s not consistent.

  Here’s what the moov looks like from my audio file :

  [ftyp] size=8+24
  
    major_brand = isom
  
    minor_version = 200
  
    compatible_brand = isom
  
    compatible_brand = iso2
  
    compatible_brand = mp41
  
    compatible_brand = iso5
  
  [moov] size=8+620
  
    [mvhd] size=12+96
  
      timescale = 1000
  
      duration = 350047
  
      duration(ms) = 350047
  
    [trak] size=8+448
  
      [tkhd] size=12+80, flags=7
  
        enabled = 1
  
        id = 1
  
        duration = 350047
  
        width = 0.000000
  
        height = 0.000000
  
      [edts] size=8+28
  
        [elst] size=12+16
  
          entry count = 1
  
          entry/segment duration = 350000
  
          entry/media time = 2048
  
          entry/media rate = 1
  
      [mdia] size=8+312
  
        [mdhd] size=12+20
  
          timescale = 44100
  
          duration = 0
  
          duration(ms) = 0
  
          language = und
  
        [hdlr] size=12+41
  
          handler_type = soun
  
          handler_name = Bento4 Sound Handler
  
        [minf] size=8+219
  
          [smhd] size=12+4
  
            balance = 0
  
          [dinf] size=8+28
  
            [dref] size=12+16
  
              [url ] size=12+0, flags=1
  
                location = [local to file]
  
          [stbl] size=8+159
  
            [stsd] size=12+79
  
              entry-count = 1
  
              [mp4a] size=8+67
  
                data_reference_index = 1
  
                channel_count = 2
  
                sample_size = 16
  
                sample_rate = 44100
  
                [esds] size=12+27
  
                  [ESDescriptor] size=2+25
  
                    es_id = 0
  
                    stream_priority = 0
  
                    [DecoderConfig] size=2+17
  
                      stream_type = 5
  
                      object_type = 64
  
                      up_stream = 0
  
                      buffer_size = 0
  
                      max_bitrate = 128006
  
                      avg_bitrate = 128006
  
                      DecoderSpecificInfo = 12 10 
  
                    [Descriptor:06] size=2+1
  
            [stts] size=12+4
  
              entry_count = 0
  
            [stsc] size=12+4
  
              entry_count = 0
  
            [stsz] size=12+8
  
              sample_size = 0
  
              sample_count = 0
  
            [stco] size=12+4
  
              entry_count = 0
  
    [mvex] size=8+48
  
      [mehd] size=12+4
  
        duration = 350047
  
      [trex] size=12+20
  
        track id = 1
  
        default sample description index = 1
  
        default sample duration = 0
  
        default sample size = 0
  
        default sample flags = 0

  And here’s a typical fragment :

  [moof] size=8+428
  
    [mfhd] size=12+4
  
      sequence number = 1
  
    [traf] size=8+404
  
      [tfhd] size=12+8, flags=20008
  
        track ID = 1
  
        default sample duration = 1024
  
      [tfdt] size=12+8, version=1
  
        base media decode time = 0
  
      [trun] size=12+352, flags=201
  
        sample count = 86
  
        data offset = 444
  
  [mdat] size=8+32653

  Does that all look good ? Any pointers for seeking within such a file would be hugely appreciated. Thanks !

• How to make videos .mp4 for a Phillips Media Player GO GEAR VIBE models ? [closed]

  14 avril 2023, par Ivan Rojas Calvo

  Here is the answer by steps (4/13/23) :

  


  


  1. First download and install the software WinFF here

     


  


  2. Check the specificacions of your media player, mine is the GoGearVibe SA2VBE08K/55 model

     


  


  3. Look for the video specification : mine says that the video format needs to match this specifications :

     


     Format = MJPEG (.mp4)

     


     Resolution = 128 x 128 píxeles

     


     Frames per second = 30 cps (fps)

     


     Bitrate = 512 kpbs

     


  


  4. Read this tutorial to create a preset in WinFF here

     


  


  5. Create a preset that turns ANY mp4 video you have into an MJPEG video with the properties shown above with this info :

     


     name : GoGearVibe55

     


     preset label : MJPEG GOGEAR

     


     Preset command line :

     


     -f mov -vf scale=128:128 -c:v mjpeg -b:v 512k -r 25 -c:a adpcm_ima_wav -b:a 192k -ar 22050 -ac 2


     


     output file : mp4

     


  


  6. Understand how to adapt the code to your necessities with this image
enter image description here

     


  


  


  Do not change what is mark in red, that's the resolution of the screen and the encoder of the video. You can change the value mark in blue, which means the bitrate, more bitrate the video will have more definition without changing the resolution. Tha value in green refers to the fps and the ones marked in yellow is the audio settings, don't worry about that, are good audio settings.

  


  Done. I did'n know how to create an article so I let you try this solution, good luck !