Recherche avancée

Sur d’autres sites (6497)

• problem compiling ffmpeg for iFrameExtractor

  11 septembre 2012, par Robin Rye

  I'm trying to compile the ffmpeg by using the make and build files in iFrameExtractor example. firstly i tried to follow the readme file on the github, which only says to run the ./build_universal in ffmpeg folder. it did not work

  i then tried to follow the info in INSTALL without success. i then tried doing the stuff in INSTALL followed by the ./build_universal which didn't work. All the *.a files that are imported to the project exists until the end of the build sequence. when the lipo commands in build_universal are run, which i guess concat the .a files for the different architectures(?). anyhow these leave the following errors :

  lipo: specifed architecture type (armv6) for file (armv6/libavcodec.a) does not match it's cputype (16777223) and cpusubtype (3) (should be cputype (12) and cpusubtype (6))
  
  lipo: specifed architecture type (armv6) for file (armv6/libavdevice.a) does not match it's cputype (16777223) and cpusubtype (3) (should be cputype (12) and cpusubtype (6))
  
  lipo: specifed architecture type (armv6) for file (armv6/libavformat.a) does not match it's cputype (16777223) and cpusubtype (3) (should be cputype (12) and cpusubtype (6))
  
  lipo: specifed architecture type (armv6) for file (armv6/libavutil.a) does not match it's cputype (16777223) and cpusubtype (3) (should be cputype (12) and cpusubtype (6))
  
  lipo: specifed architecture type (armv6) for file (armv6/libswscale.a) does not match it's cputype (16777223) and cpusubtype (3) (should be cputype (12) and cpusubtype (6))

  i can get the project to compile for simulator if i only use ./build_armv7 but if i run the universal the .a files are removed in the end. and only using doesn't work to build for iphone 4 .

• HEVC video cutting issues using FFmpeg

  4 novembre 2017, par Dmitry Katkevich

  I need to cut videos using FFmpeg and I cannot transcode original videos (because of the performance reason). And I ran into a problem with HEVC videos from IPhone : there are glithes in the beginning of the cutted video.

  Here is how we converted videos before issue :

  ffmpeg.exe -i original.MOV -c:v copy -c:a aac -ss 4 -y good.mp4

  But for HEVC video there are glitches for 1 second in the beginning of the cutted video :

  

  Then I’ve tried to put seek option before input video :

  ffmpeg.exe -ss 4 -i original.MOV -c:v copy -c:a aac -y good.mp4

  The result seems good :

  

  After some googling it turns out that -ss option before input is faster but less accurate whereas -ss option after input and before output is slower but more accurate.

  So my questions are :

  • Why -ss option behaves differently then it is put before/after input ?

  • Is there a way to avoid glitches using output seek ffmpeg option ?

  • What does ’more/less accurate’ mean ? Does it mean that the seek may be too big or to little (bigger/less than we specified) ? How big may be this difference ?

• avcodec/h2645_sei : add support for Ambient Viewing Environment SEI

  9 janvier 2023, par Jan Ekström

  avcodec/h2645_sei : add support for Ambient Viewing Environment SEI
  Defined by H.274, this SEI message is utilized by iPhones to save
  
  the nominal ambient viewing environment for the display of recorded
  
  HDR content. The contents of the message are exposed to API users
  
  as AVFrame side data containing AVAmbientViewingEnvironment.
  As the DV RPU test sample is from an iPhone and includes Ambient
  
  Viewing Environment SEI messages, its test result gets updated.
  

  • [DH] libavcodec/h2645_sei.c
  • [DH] libavcodec/h2645_sei.h
  • [DH] tests/ref/fate/hevc-dv-rpu