Recherche avancée

Sur d’autres sites (6475)

• linking libavcodec os x ffmpeg ApplicationServices.framework

  30 décembre 2015, par Grady Player

  Here is my error : (newer version of ffmpeg)

  dyld: Library not loaded: /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices
  
    Referenced from: /Users/me/path/to/lib/libavcodec.dylib
  
    Reason: Incompatible library version: libavcodec.dylib requires version 64.0.0 or later, but ApplicationServices provides version 1.0.0

  I have read the questions on SO that say you need to link ApplicationServices.framework... which I have done, it makes no difference...

  I have searched for other versions of that framework :

  $ mdfind ApplicationServices.framework
  
  /System/Library/Frameworks/ApplicationServices.framework

  just one...

  so then inspecting frameworks...

  $ otool -L /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices 
  
  /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices:
  
      /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices (compatibility version 1.0.0, current version 48.0.0)
  
      /System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics (compatibility version 64.0.0, current version 600.0.0)
  
  ...

  and libavcodec

  otool -L ../lib/libavcodec.dylib 
  
  ../lib/libavcodec.dylib:
  
      libavcodec.dylib (compatibility version 56.0.0, current version 56.60.100)
  
      @loader_path/libswresample.dylib (compatibility version 1.0.0, current version  ...
  
  ...
  
  /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices (compatibility version 64.0.0, current version 600.0.0)

  I am compiling everything with -mmacosx-version-min=10.7

  so maybe a bug in the toolchain ?

  compiler :

  clang -v
  
  Apple LLVM version 7.0.2 (clang-700.1.81)
  
  Target: x86_64-apple-darwin15.2.0
  
  Thread model: posix

  linker :

  ld -v
  
  @(#)PROGRAM:ld  PROJECT:ld64-253.9
  
  configured to support archs: armv6 armv7 armv7s arm64 i386 x86_64 x86_64h armv6m armv7k armv7m armv7em (tvOS)
  
  LTO support using: Apple LLVM 7.0.2 (clang-700.1.81)

• Using ffmpeg rtmp stream a static image and audio input [on hold]

  30 octobre 2017, par Chad

  Using a Raspberry Pi, stream audio in and use a static image as the video input thru ffmpeg over RTMP to a Cloud video provider (DaCast in this instance)

  So far, I’ve gone through many blog posts, Stack Overflow questions, and package documentation. I’ve found that most of the posts are no longer valid with the newer versions of ffmpeg. Or don’t quite line up with what I am trying to achieve.

  However, I have figured out the right settings to stream the Raspberry Pi Camera v2 with the audio in.

  ffmpeg \
    -f alsa -ac 1 -i plughw:1,0 \
    -f v4l2 -s 1920x1080 -r 30 -input_format h264 -i /dev/video0 \
    -vcodec copy -preset veryfast -r 15 -g 30 -b:v 64k -ar 44100 -threads 6 -b:a 96k -bufsize 3000k \
    -f flv rtmp ://streaming_server_url
  

  But can’t seem to get it right to replace the video input with a static image.

  I have tried removing the 3rd line and adding -loop 1 -i '/path/to/image.jpg'

  The logs look like :

  [alsa @ 0x55e4b980] Thread message queue blocking ; consider raising the thread_queue_size option (current value : 1024)
  [alsa @ 0x55e4b980] ALSA buffer xrun.  0kB time=00:00:00.00 bitrate=N/A speed=   0x
  [alsa @ 0x55e4b980] ALSA buffer xrun.130kB time=00:00:00.27 bitrate=3822.5kbits/s speed=0.0403x
  ...
  

  I have also tried looping a 4 second video, with similar outcomes.

  ---

  My Setup for context :

  • Raspberry Pi 3 Model B
  • USB Audio Device (Sabrent USB External Stereo Sound Adapter)
  • Ubuntu MATE 16.04.2 (Xenial)
  • ffmpeg version 3.2-2+rpi1 xenial1.7 (I can post what is configured with the build, if needed)

• Révision 103307 : - Les plugins-dist de spip 3.2 ne sont pas supposé avoir de support pour qu’il f...

  17 mars 2017, par spip.franck@lien-d-amis.net

  - La version de mini de compatibilité est maintenant 3.2.0-dev, comme, ça, quand l’alpha sortira, cela devrait être bon (quand la version 3.2.0 stable sortira, je mettrais 3.2.0 comme version mini)
  - Il y avait aussi un ou deux mots avec des accents comme par exemple è j’ai fait le changement pour y mettre à la place è ou autres