Recherche avancée

Sur d’autres sites (4186)

• Can't connect to ffserver when running on android device

  11 décembre 2016, par Antonio C G

  I am working on an android app. This will run a ffserver (on the device, not another computer). The server is running and I can access the status page, everything seems ok. But when I try to send the video using ffmpeg I always get connection refused.

  This is my ffserver.conf file :

  HTTPPort 8090
  
  HTTPBindAddress 0.0.0.0
  
  MaxHTTPConnections 2000
  
  MaxClients 1000
  
  MaxBandwidth 1000
  
  CustomLog /data/user/0/com.antonio.droidcast/files/log.txt
  
  NoDefaults
  
  
  
  <feed>
  
      File /data/user/0/com.antonio.droidcast/cache/feed1.ffm
  
      FileMaxSize 200M
  
      ACL allow 127.0.0.1
  
  </feed>
  
  
  
  <stream>
  
      Format mp4
  
      Feed feed1.ffm
  
  
  
      VideoCodec libx264
  
      VideoFrameRate 30
  
      VideoBitRate 512
  
      VideoSize 320x240
  
      AVOptionVideo crf 23
  
      AVOptionVideo preset medium
  
      AVOptionVideo flags +global_header
  
  
  
      AudioCodec aac
  
      Strict -2
  
      AudioBitRate 128
  
      AudioChannels 2
  
      AudioSampleRate 44100
  
      AVOptionAudio flags +global_header
  
  </stream>

  I connect to server using this command :

  ffmpeg -i VIDEO_PATH2 http://localhost:8090/feed1.ffm

  And this is the ouput I get :

  Splitting the commandline.
  
  Reading option '-loglevel' ... matched as option 'loglevel' (set logging level) with argument 'debug'.
  
  Reading option '-i' ... matched as input file with argument '/storage/emulated/0/Download/video1.mp4'.
  
  Reading option 'http://localhost:8090/feed1.ffm' ... matched as output file.
  
  Finished splitting the commandline.
  
  Parsing a group of options: global .
  
  Applying option loglevel (set logging level) with argument debug.
  
  Successfully parsed a group of options.
  
  Parsing a group of options: input file /storage/emulated/0/Download/video1.mp4.
  
  Successfully parsed a group of options.
  
  Opening an input file: /storage/emulated/0/Download/video1.mp4.
  
  [file @ 0xf5f5e060] Setting default whitelist 'file,crypto'
  
  [mov,mp4,m4a,3gp,3g2,mj2 @ 0xf5f58000] Format mov,mp4,m4a,3gp,3g2,mj2 probed with size=2048 and score=100
  
  [mov,mp4,m4a,3gp,3g2,mj2 @ 0xf5f58000] ISO: File Type Major Brand: isom
  
  [mov,mp4,m4a,3gp,3g2,mj2 @ 0xf5f58000] Unknown dref type 0x08206c7275 size 12
  
      Last message repeated 1 times
  
  [mov,mp4,m4a,3gp,3g2,mj2 @ 0xf5f58000] Before avformat_find_stream_info() pos: 5446 bytes read:32768 seeks:0
  
  [h264 @ 0xf5f49000] user data:"x264 - core 148 - H.264/MPEG-4 AVC codec - Copyleft 2003-2015 - http://www.videolan.org/x264.html - options: cabac=1 ref=3 deblock=1:0:0 analyse=0x3:0x113 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=6 lookahead_threads=1 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1 b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2 keyint=250 keyint_min=1 scenecut=40 intra_refresh=0 rc_lookahead=40 rc=crf mbtree=1 crf=23.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00"
  
  [h264 @ 0xf5f49000] no picture 
  
  [mov,mp4,m4a,3gp,3g2,mj2 @ 0xf5f58000] All info found
  
  [mov,mp4,m4a,3gp,3g2,mj2 @ 0xf5f58000] After avformat_find_stream_info() pos: 6081 bytes read:98304 seeks:2 frames:3
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/storage/emulated/0/Download/video1.mp4':
  
    Metadata:
  
      major_brand     : isom
  
      minor_version   : 512
  
      compatible_brands: isomiso2avc1mp41
  
      encoder         : Lavf57.25.100
  
    Duration: 00:02:45.59, start: 0.128000, bitrate: 24 kb/s
  
      Stream #0:0(eng), 2, 1/450000: Video: h264 (High), 4 reference frames (avc1 / 0x31637661), yuv420p(left), 1920x1080 (1920x1088) [SAR 1:1 DAR 16:9], 7451717/900000, 0 kb/s, 0.06 fps, 0.06 tbr, 450k tbn, 0.12 tbc (default)
  
      Metadata:
  
        handler_name    : VideoHandler
  
      Stream #0:1(eng), 1, 1/8000: Audio: aac (LC) (mp4a / 0x6134706D), 8000 Hz, mono, fltp, 29 kb/s (default)
  
      Metadata:
  
        handler_name    : SoundHandler
  
  Successfully opened the file.
  
  Parsing a group of options: output file http://localhost:8090/feed1.ffm.
  
  Successfully parsed a group of options.
  
  Opening an output file: http://localhost:8090/feed1.ffm.
  
  [http @ 0xf5f5e1e0] Setting default whitelist 'http,https,tls,rtp,tcp,udp,crypto,httpproxy'
  
  [tcp @ 0xf5f5e3c0] Connection to tcp://localhost:8090 failed: Connection refused
  
  http://localhost:8090/feed1.ffm: Connection refused

  Does anybody know what could be wrong ?
  Just to be clear, I recompiled ffserver and ffmpeg for android. They both seem to be ok as I can execute commands. Both binaries are part of the app, so everything runs inside the phone.

  Thanks.

• FFMPEG, macOS Catalina : "ffmpeg stderr : /private/tmp/com.apple.launchd.ID/org.macosforge.xquartz:0 : Operation not supported on socket"

  11 février 2021, par Bogdan Slyusarenko

  I'm trying to record selenium test run with FFMPEG, for automation testing of web extensions (selenium+js/ts).
FFMPEG initiated by command :

  


      const { spawn } = require("child_process");
        ffmpeg = spawn("ffmpeg", [
          "-x265-params",
          "-f",
          "xcbgrab", 
          "-video_size",
          "1280x1024", 
          "-i",
          process.env.DISPLAY, // "/private/tmp/com.apple.launchd.ID/org.macosforge.xquartz:0"
          "-loglevel",
          "debug", 
          "-y", 
          "-pix_fmt",
          "yuv420p",
          videoPath, 
        ]);


  


  Return constantly error,related to process.DISPLAY, I'm not sure why it's so :

  


      ffmpeg stderr: /private/tmp/com.apple.launchd.W851FkeNXz/org.macosforge.xquartz:0: Operation not supported on socket


  


  Full debug login is :

  


  ffmpeg stderr: ffmpeg version 4.3.1 Copyright (c) 2000-2020 the FFmpeg developers
ffmpeg stderr:   built with Apple clang version 12.0.0 (clang-1200.0.32.28)
ffmpeg stderr:   configuration: --prefix=/usr/local/Cellar/ffmpeg/4.3.1_9 --enable-shared --enable-pthreads --enable-version3 --enable-avresample --cc=clang --host-cflags= --host-ldflags= --enable-ffplay --enable-gnutls --enable-gpl --enable-libaom --enable-libbluray --enable-libdav1d --enable-libmp3lame --enable-libopus --enable-librav1e --enable-librubberband --enable-libsnappy --enable-libsrt --enable-libtesseract --enable-libtheora --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libxvid --enable-lzma --enable-libfontconfig --enable-libfreetype --enable-frei0r --enable-libass --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-librtmp --enable-libspeex --enable-libsoxr --enable-videotoolbox --enable-libzmq --enable-libzimg --disable-libjack --disable-indev=jack
ffmpeg stderr: libavutil      56. 51.100 / 56. 51.100
ffmpeg stderr:   libavcodec     58. 91.100 / 58. 91.100
ffmpeg stderr:   libavformat    58. 45.100 / 58. 45.100
ffmpeg stderr:   libavdevice    58. 10.100 / 58. 10.100
ffmpeg stderr:   libavfilter     7. 85.100 /  7. 85.100
ffmpeg stderr:   libavresample   4.  0.  0 /  4.  0.  0
ffmpeg stderr:   libswscale      5.  7.100 /  5.  7.100
ffmpeg stderr:   libswresample   3.  7.100 /  3.  7.100
ffmpeg stderr:   libpostproc    55.  7.100 / 55.  7.100
ffmpeg stderr: Splitting the commandline.
ffmpeg stderr: Reading option '-x265-params' ...
ffmpeg stderr: matched as AVOption 'x265-params' with argument '-f'.
ffmpeg stderr: Reading option 'xcbgrab' ...
ffmpeg stderr: matched as output url.
ffmpeg stderr: Reading option '-video_size' ...
ffmpeg stderr: matched as AVOption 'video_size' with argument '1280x1024'.
ffmpeg stderr: Reading option '-i' ... matched as input url with argument '/private/tmp/com.apple.launchd.W851FkeNXz/org.macosforge.xquartz:0'.
ffmpeg stderr: Reading option '-loglevel' ... matched as option 'loglevel' (set logging level) with argument 'debug'.
ffmpeg stderr: Reading option '-y' ...
ffmpeg stderr: matched as option 'y' (overwrite output files) with argument '1'.
ffmpeg stderr: Reading option '-pix_fmt' ... matched as option 'pix_fmt' (set pixel format) with argument 'yuv420p'.
ffmpeg stderr: Reading option '/Volumes/MacHD2/Upprojects/TEST/log/Checkout-Google.com-Search-on-Google.mp4' ... matched as output url.
ffmpeg stderr: Finished splitting the commandline.
ffmpeg stderr: Parsing a group of options: global .
ffmpeg stderr: Applying option loglevel (set logging level) with argument debug.
ffmpeg stderr: Applying option y (overwrite output files) with argument 1.
ffmpeg stderr: Successfully parsed a group of options.
ffmpeg stderr: Parsing a group of options: input url /private/tmp/com.apple.launchd.W851FkeNXz/org.macosforge.xquartz:0.
ffmpeg stderr: Successfully parsed a group of options.
ffmpeg stderr: Opening an input file: /private/tmp/com.apple.launchd.W851FkeNXz/org.macosforge.xquartz:0.
ffmpeg stderr: [NULL @ 0x7fcf80016800] Opening '/private/tmp/com.apple.launchd.W851FkeNXz/org.macosforge.xquartz:0' for reading
ffmpeg stderr: [file @ 0x7fcf7f507a00] Setting default whitelist 'file,crypto,data'
ffmpeg stderr: /private/tmp/com.apple.launchd.W851FkeNXz/org.macosforge.xquartz:0: Operation not supported on socket



  


  Any feedback appreciated

  


• Revised FATE Test Spec System

  9 juin 2010, par Multimedia Mike — FATE Server

  FATE involves some database tables that define the test specifications. Like everything else in FATE, the concept could use some improvement. After I prototyped an improved, multithreaded testing client, the next logical revision seemed to be the test spec system.

  History
  The test spec system has been handled by a single table that includes an FFmpeg command line (with a few possible modifiers thrown in), an integer ID, a human-friendly ID, a description, the expected command line return code, the expected command output, a maximum runtime, and a Boolean to indicate whether the test is to be considered active.

  Adjunct to this test database is a large corpus of test media named the FATE suite.

  At first, the FATE testing script used a direct MySQL database protocol to query the test specs from the server before every build/test cycle. I soon realized this was ludicrously inefficient since the test specs don’t change that often. So I cached the tests in a static file to be retrieved via HTTP, first in Python’s "pickled" (serialized) format, then in an SQLite database.

  Planned Upgrades
  There are 2 major features I would like to build into the system going forward :

  1. The ability to version the entire suite so that it’s possible to test old branches of FFmpeg
  2. Another database field to indicate which, if any, other test specs must be executed before this spec can be executed

  I think I will take this opportunity to switch the test cache serialization format to JSON. I switched from Python pickling to SQLite because the latter was more portable between languages. JSON has that same benefit. Further, working with JSON data doesn’t require a round trip to disk (i.e., want to generate an SQLite database for sending via HTTP ? It needs to go onto disk first. It’s possible to create and manipulate a database entirely in memory but not fetch the bits).

  Things To Research

  • Pondering how version control systems operate and what they have to teach regarding how to version this data (including the question of whether I can just use an existing version control mechanism instead of creating my own system)
  • Efficient caching mechanism
  • Tagging test specs for alternate purposes such as longevity testing
  • Learn about web form programming in the 21st century so that it’s not quite as painful to maintain the system.

  Preliminary Versioning Concept
  Here is one approach I am thinking of : Create test groups. Each test spec is assigned to at least one test group. I can think of at least 2 groups : functional (the base test set in existence that validates functionality) and profiling (the projected test set that will be used for ongoing performance and memory profiling). The web frontend will allow for the creation of labels that will apply to a single group. Doing so will apply that label to all active tests in the group.