Recherche avancée

Sur d’autres sites (9176)

• Error in ffmpeg conversion

  9 avril 2015, par Adam Mo.

  I have a VPS 1G RAM with CentOS 6 i386 minimal installed and installed ffmpeg by ffmpeginstaller.com to setup clipbucket 2.7 in the VPS.
  when I test the ffmpeg by this command :

  wget "http://mirrorblender.top-ix.org/peach/bigbuckbunny_movies/big_buck_bunny_720p_surround.avi"
  
  ffmpeg -i big_buck_bunny_720p_surround.avi -vcodec libx264 big_buck_bunny_720p_surround-H264.avi

  by following this tutorial I get error
  the output :

  ffmpeg version N-71343-g32e06c4-syslint Copyright (c) 2000-2015 the FFmpeg     developers
  
    built with gcc 4.4.7 (GCC) 20120313 (Red Hat 4.4.7-11)
  
    configuration: --prefix=/usr/local/cpffmpeg --enable-shared --enable-nonfree --enable-gpl --enable-pthreads --enable-libopencore-amrnb --enable-decoder=liba52 --enable-libopencore-amrwb --enable-libfaac --enable-libmp3lame --enable-libtheora --enable-libvorbis --enable-libx264 --enable-libxvid --extra-cflags=-    I/usr/local/cpffmpeg/include/ --extra-ldflags=-L/usr/local/cpffmpeg/lib --enable-    version3 --extra-version=syslint
  
    libavutil      54. 22.101 / 54. 22.101
  
    libavcodec     56. 34.100 / 56. 34.100
  
    libavformat    56. 30.100 / 56. 30.100
  
    libavdevice    56.  4.100 / 56.  4.100
  
    libavfilter     5. 13.101 /  5. 13.101
  
    libswscale      3.  1.101 /  3.  1.101
  
    libswresample   1.  1.100 /  1.  1.100
  
    libpostproc    53.  3.100 / 53.  3.100
  
  Input #0, avi, from 'big_buck_bunny_720p_surround.avi':
  
    Metadata:
  
      encoder         : AVI-Mux GUI 1.17.7, Aug  8 2006  20:59:17
  
      JUNK            :
  
    Duration: 00:09:56.46, start: 0.000000, bitrate: 4456 kb/s
  
      Stream #0:0: Video: mpeg4 (Simple Profile) (FMP4 / 0x34504D46), yuv420p,     1280x720 [SAR 1:1 DAR 16:9], 4001 kb/s, 24 fps, 24 tbr, 24 tbn, 24 tbc
  
      Stream #0:1: Audio: ac3 ([0] [0][0] / 0x2000), 48000 Hz, 5.1(side), fltp, 448 kb/s
  
      Metadata:
  
        title           : BBB-Master
  
  [libx264 @ 0x9360de0] using SAR=1/1
  
  [libx264 @ 0x9360de0] using cpu capabilities: none!
  
  x264 [error]: malloc of size 5258784 failed
  
  Output #0, avi, to 'big_buck_bunny_720p_surround-H264.avi':
  
    Metadata:
  
      encoder         : AVI-Mux GUI 1.17.7, Aug  8 2006  20:59:17
  
      JUNK            :
  
      Stream #0:0: Video: h264, none, q=2-31, 128 kb/s, SAR 1:1 DAR 0:0, 24 fps
  
      Metadata:
  
        encoder         : Lavc56.34.100 libx264
  
      Stream #0:1: Audio: mp3, 0 channels, 128 kb/s
  
      Metadata:
  
        title           : BBB-Master
  
        encoder         : Lavc56.34.100 libmp3lame
  
  Stream mapping:
  
    Stream #0:0 -> #0:0 (mpeg4 (native) -> h264 (libx264))
  
    Stream #0:1 -> #0:1 (ac3 (native) -> mp3 (libmp3lame))
  
  Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height

  I don’t know what the problem, can any one help me ?

• How to generate a PDF (1.7) from a MP4 movie (Rich Media annotation) ?

  19 août 2020, par malat

  I am a happy user of img2pdf. This tool does the minimal amount of work to put a series of JPEG 2000/JPEG/PNG images into a PDF "enveloppe". However I am now faced with a new challenge : embed a MP4 file into a PDF "enveloppe".

  


  I see that commercial tool can do it, as seen at :

  


  

  • Add audio, video, and interactive objects to PDFs

  


  


  It seems to have been introduced in ISO 32000-1 (PDF 1.7 Extension Level 5)

  


  I am looking for a solution which will use the Rich Media annotation inside the PDF stream.

  


  There are dozen of duplicated questions on superuser/stackoverflow, which all pretty much refer to imagemagick/convert command line tool. But in my case, convert expand the images into a multi-page PDF (which is not my desired behavior) :

  


  $ convert input.mp4 output.pdf
$ pdfinfo output.pdf 
Title:          out
Producer:       https://imagemagick.org
CreationDate:   Wed Aug 19 15:38:01 2020 CEST
ModDate:        Wed Aug 19 15:38:01 2020 CEST
Tagged:         no
UserProperties: no
Suspects:       no
Form:           none
JavaScript:     no
Pages:          1601
Encrypted:      no
Page size:      352 x 288 pts
Page rot:       0
File size:      534407296 bytes
Optimized:      no
PDF version:    1.3


  


  with :

  


  $ convert --version
Version: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org
Copyright: © 1999-2019 ImageMagick Studio LLC
License: https://imagemagick.org/script/license.php
Features: Cipher DPC Modules OpenMP 
Delegates (built-in): bzlib djvu fftw fontconfig freetype jbig jng jpeg lcms lqr ltdl lzma openexr pangocairo png tiff webp wmf x xml zlib


  


  and

  


  $ file input.mp4 
input.mp4: ISO Media, MP4 Base Media v1 [IS0 14496-12:2003]
$ ffprobe -v quiet -print_format json  -show_streams input.mp4 | grep codec_long_name
            "codec_long_name": "H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10",


  


• checkasm : use perf API on Linux ARM*

  1er septembre 2017, par Clément Bœsch

  checkasm : use perf API on Linux ARM*
  On ARM platforms, accessing the PMU registers requires special user
  
  access permissions. Since there is no other way to get accurate timers,
  
  the current implementation of timers in FFmpeg rely on these registers.
  
  Unfortunately, enabling user access to these registers on Linux is not
  
  trivial, and generally involve compiling a random and unreliable github
  
  kernel module, or patching somehow your kernel.
  Such module is very unlikely to reach the upstream anytime soon. Quoting
  
  Robin Murphin from ARM :
  > Say you do give userspace direct access to the PMU ; now run two or more
  
  > programs at once that believe they can use the counters for their own
  
  > "minimal-overhead" profiling. Have fun interpreting those results...
  
  >
  
  > And that's not even getting into the implications of scheduling across
  
  > different CPUs, CPUidle, etc. where the PMU state is completely beyond
  
  > userspace's control. In general, the plan to provide userspace with
  
  > something which might happen to just about work in a few corner cases,
  
  > but is meaningless, misleading or downright broken in all others, is to
  
  > never do so.
  As a result, the alternative is to use the Performance Monitoring Linux
  
  API which makes use of these registers internally (assuming the PMU of
  
  your ARM board is supported in the kernel, which is definitely not a
  
  given...).
  While the Linux API is obviously cross platform, it does have a
  
  significant overhead which needs to be taken into account. As a result,
  
  that mode is only weakly enabled on ARM platforms exclusively.
  Note on the non flexibility of the implementation : the timers (native
  
  FFmpeg vs Linux API) are selected at compilation time to prevent the
  
  need of function calls, which would result in a negative impact on the
  
  cycle counters.
  

  • [DH] configure
  • [DH] tests/checkasm/checkasm.c
  • [DH] tests/checkasm/checkasm.h