Recherche avancée

Sur d’autres sites (12961)

• Naive Sorenson Video 1 Encoder

  12 septembre 2010, par Multimedia Mike — General

  (Yes, the word is “naive” — or rather, “naïve” — not “native”. People always try to correct me when I use the word. Indeed, it should actually be written with 2 dots over the ‘i’ but who has a keyboard that can easily do that ?)

  At the most primitive level, programming a video encoder is about writing out a sequence of bits that the corresponding video decoder will understand. It’s sort of like creating a program — represented as a stream of opcodes — that will run on a given microprocessor or virtual machine. In fact, reading a video codec bitstream specification will reveal a lot of terminology along the lines of “transmitting information to the decoder” or “signaling the decoder to do xyz.”

  Creating a good encoder that will deliver decent quality at a reasonable bitrate is difficult. Creating a naive encoder that produces a technically compliant bitstream, not so much.

  
  
  

  When I wrote an FFmpeg encoder for Sorenson Video 1 (SVQ1), the first step was to just create a minimally compliant bitstream. The coarsest encoding mode that SVQ1 allows is to encode the average (mean) of each 16×16 block of samples. So I created an encoder that just encoded the mean of each block. Apple’s QuickTime Player was able to play the resulting video in all of its blocky glory. The result rather reminds me of the Super Nintendo’s mosaic effect.

  Level 5 blocks (mean-only 16×16 encoding) :
  

  
  
  

  Level 3 blocks (mean-only 8×8 encoding) :
  

  
  
  

  It’s one thing for your own decoder (in this case, FFmpeg’s own decoder) to be able to decode the data. The big test is whether the official decoder (in this case, Apple QuickTime Player) can decode the file.

  
  
  

  Now that’s a good feeling. After establishing that sort of baseline, it’s possible to adapt more and more features of the codec.

• FFMPEG not copying over metadata GPS data

  15 novembre 2017, par JK81

  Recording device tags the video file with geolocation, when converting from mov to mp4 the geolocation data is missing.
  ffmpeg -i source.mov -r 60 -c:v libx264 -c:a aac -map_metadata -1 -movflags faststart destination.mp4

  Am I doing something wrong ? I’m running the command from Windows 10 x64. If it’s not possible, is there a way to use a command at the same time for ExifTool to write it ?

  The lines for metadata missing :
  com.apple.quicktime.location.I &
  ©xyz

• How to calculate the start time of mp4 video ?

  27 mai 2022, par Neil Galiaskarov

  I am studying mp4 video structure. I have an issue with reading the start time value for the following mp4 video

  


  I have read this answer
mp4 video starts at different time on Quicktime/AVplayer vs Chrome/Firefox

  


  and it says that Edit atom can modify the start time.

  


  Using ffprobe I have the following output :

  


      "start_time": "0.033333",
    "duration_ts": 327,
    "duration": "10.900000",
    "bit_rate": "9420949",


  


  Using mp4dumper I have the following atoms structure which proves missing Edit atom file :

  


  ftyp (24 @ 0)
free (8 @ 24)
moov (7034 @ 32)
  mvhd (108 @ 40)
  trak (2883 @ 148)
      tkhd (92 @ 156)
      mdia (2783 @ 248)
          mdhd (32 @ 256)
          hdlr (52 @ 288)
          minf (2691 @ 340)
              smhd (16 @ 348)
              dinf (36 @ 364)
                  dref (28 @ 372)
                      url  (12 @ 388)
              stbl (2631 @ 400)
                  stsd (91 @ 408)
                      mp4a (75 @ 424)
                  stts (24 @ 499)
                  stsc (304 @ 523)
                  stsz (2056 @ 827)
                  stco (148 @ 2883)
  trak (4035 @ 3031)
      tkhd (92 @ 3039)
      mdia (3935 @ 3131)
          mdhd (32 @ 3139)
          hdlr (52 @ 3171)
          minf (3843 @ 3223)
              vmhd (20 @ 3231)
              dinf (36 @ 3251)
                  dref (28 @ 3259)
                      url  (12 @ 3275)
              stbl (3779 @ 3287)
                  stsd (163 @ 3295)
                      avc1 (147 @ 3311)
                  stts (24 @ 3458)
                  ctts (1960 @ 3482)
                  stsc (40 @ 5442)
                  stsz (1328 @ 5482)
                  stco (148 @ 6810)
                  stss (108 @ 6958)
mdat (13096745 @ 7066)


  


  How ffprobe calculates 0.033333 start time value ?