Recherche avancée

Sur d’autres sites (8294)

• FFmpeg Android : Freezes / stops silently at 'SoundHandle'

  8 décembre 2014, par jgads

  I’m trying to get FFmpeg working on Android, but it seems to fail silently with no output file. I have tested the same command on Windows and it fully completes.

  I’m trying to convert an mp4 into a format which I can then ’concat’ with other videos files to make one ’compilation’ video.

  The command is :

  ffmpeg -i 1.mp4 -c copy -bsf h264_mp4toannexb -t 30 out1.ts

  The logcat shows that ffmpeg seems to get ’stuck’ - with no updates and seemingly quitting half way through. Is there anything obvious I’m doing wrong ? This is being tested on just a bog-standard Galaxy Note 2. ’ffmpeg -version’ works just fine.

  Here is the logcat :

  12-08 13:38:27.670  18599-18599/com.company.app E/﹕ Device driver API match
  
  Device driver API version: 23
  
  User space API version: 23
  
  12-08 13:38:27.670  18599-18599/com.company.app E/﹕ mali: REVISION=Linux-r3p2-01rel3 BUILD_DATE=Fri Mar 21 13:52:50 KST 2014
  
  12-08 13:38:27.710  18599-18599/com.company.app D/OpenGLRenderer﹕ Enabling debug mode 0
  
  12-08 13:38:29.060  18599-18599/com.company.app E/FFMPEG﹕ Success loading ffmpeg
  
  12-08 13:38:29.080  18599-18661/com.company.app D/FFmpeg﹕ Running publishing updates method
  
  12-08 13:38:29.090  18599-18599/com.company.app E/FFMPEG﹕ Progress: ffmpeg version n2.4.2 Copyright (c) 2000-2014 the FFmpeg developers
  
  12-08 13:38:29.090  18599-18599/com.company.app E/FFMPEG﹕ Progress:   built on Oct  7 2014     15:08:46 with gcc 4.8 (GCC)
  
  12-08 13:38:29.095  18599-18599/com.company.app E/FFMPEG﹕ Progress:   configuration: --target-os=linux --cross-prefix=/home/sb/Source-Code/ffmpeg-android/toolchain-android/bin/arm-linux-androideabi- --arch=arm --cpu=cortex-a8 --enable-runtime-cpudetect --sysroot=/home/sb/Source-Code/ffmpeg-android/toolchain-android/sysroot --enable-pic --enable-libx264 --enable-libass --enable-libfreetype --enable-libfribidi --enable-fontconfig --enable-pthreads --disable-debug --disable-ffserver --enable-version3 --enable-hardcoded-tables --disable-ffplay --disable-ffprobe --enable-gpl --enable-yasm --disable-doc --disable-shared --enable-static --pkg-config=/home/sb/Source-Code/ffmpeg-android/ffmpeg-pkg-config --prefix=/home/sb/Source-Code/ffmpeg-android/build/armeabi-v7a-neon --extra-cflags='-I/home/sb/Source-Code/ffmpeg-android/toolchain-android/include -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -fno-strict-overflow -fstack-protector-all -mfpu=neon' --extra-ldflags='-L/home/sb/Source-Code/ffmpeg-android/toolchain-android/lib -Wl,-z,relro -Wl,-z,now -pie' --extra-libs='-lpng -lexpat -lm' --extra-cxxflags=
  
  12-08 13:38:29.095  18599-18599/com.company.app E/FFMPEG﹕ Progress:   libavutil      54.  7.100 / 54.  7.100
  
  12-08 13:38:29.095  18599-18599/com.company.app E/FFMPEG﹕ Progress:   libavcodec     56.  1.100 / 56.  1.100
  
  12-08 13:38:29.095  18599-18599/com.company.app E/FFMPEG﹕ Progress:   libavformat    56.  4.101 / 56.  4.101
  
  12-08 13:38:29.095  18599-18599/com.company.app E/FFMPEG﹕ Progress:   libavdevice    56.  0.100 / 56.  0.100
  
  12-08 13:38:29.095  18599-18599/com.company.app E/FFMPEG﹕ Progress:   libavfilter     5.  1.100 /  5.  1.100
  
  12-08 13:38:29.095  18599-18599/com.company.app E/FFMPEG﹕ Progress:   libswscale      3.  0.100 /  3.  0.100
  
  12-08 13:38:29.100  18599-18599/com.company.app E/FFMPEG﹕ Progress:   libswresample   1.  1.100 /  1.  1.100
  
  12-08 13:38:29.100  18599-18599/com.company.app E/FFMPEG﹕ Progress:   libpostproc    53.  0.100 / 53.  0.100
  
  12-08 13:38:29.230  18599-18599/com.company.app E/FFMPEG﹕ Progress: Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/storage/emulated/0/Pictures/videotest/1.mp4':
  
  12-08 13:38:29.230  18599-18599/com.company.app E/FFMPEG﹕ Progress:   Metadata:
  
  12-08 13:38:29.230  18599-18599/com.company.app E/FFMPEG﹕ Progress:     major_brand     : isom
  
  12-08 13:38:29.230  18599-18599/com.company.app E/FFMPEG﹕ Progress:     minor_version   : 0
  
  12-08 13:38:29.230  18599-18599/com.company.app E/FFMPEG﹕ Progress:     compatible_brands: isom3gp4
  
  12-08 13:38:29.235  18599-18599/com.company.app E/FFMPEG﹕ Progress:     creation_time   : 2014-12-03 18:40:00
  
  12-08 13:38:29.235  18599-18599/com.company.app E/FFMPEG﹕ Progress:   Duration: 00:00:03.14, start: 0.000000, bitrate: 10598 kb/s
  
  12-08 13:38:29.235  18599-18599/com.company.app E/FFMPEG﹕ Progress:     Stream #0:0(eng): Video: h264 (Constrained Baseline) (avc1 / 0x31637661), yuv420p, 1280x720, 10594 kb/s, SAR 65536:65536 DAR 16:9, 29.94 fps, 29.92 tbr, 90k tbn, 180k tbc (default)
  
  12-08 13:38:29.235  18599-18599/com.company.app E/FFMPEG﹕ Progress:     Metadata:
  
  12-08 13:38:29.240  18599-18599/com.company.app E/FFMPEG﹕ Progress:       creation_time   : 2014-12-03 18:40:00
  
  12-08 13:38:29.240  18599-18599/com.company.app E/FFMPEG﹕ Progress:       handler_name    : VideoHandle
  
  12-08 13:38:29.245  18599-18599/com.company.app E/FFMPEG﹕ Progress:     Stream #0:1(eng): Audio: aac (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 97 kb/s (default)
  
  12-08 13:38:29.250  18599-18599/com.company.app E/FFMPEG﹕ Progress:     Metadata:
  
  12-08 13:38:29.250  18599-18599/com.company.app E/FFMPEG﹕ Progress:       creation_time   : 2014-12-03 18:40:00
  
  12-08 13:38:29.250  18599-18599/com.company.app E/FFMPEG﹕ Progress:       handler_name    : SoundHandle

• How to "filter" a file through command line before apache sends it to client ?

  1er septembre 2020, par Timothe Jahan

  I have large collection of video files which are available on our website.
For each video we have multiple quality and language, so in order to save space we store only 1 file, which contains all audio and video tracks.

  


  Our streaming server can handle these multitrack files in order to serve only the useful part to each user, but we also make them available for download through the apache web server.
Currently, when a user request a file (certain quality, certain language), we first create a temporary file with only his needs, and give him for download.
I would like to remove this intermediate step and extract on the fly.
Extraction can be done by ffmpeg, but I need to have apache "pipe" the file through ffmpeg before sending the bytes out. Do you have any way of doing this.

  


  example :

  


  


  Filename_multi.mp4 [SD,HD,fr,en,ru]
User request : Filename_HD_fr.mp4 [HD,fr]
Apache fetch the file Filename_multi.mp4 and pipe it through an ffmpeg command and send the bytes as > they are encoded, not waiting for the end.

  


  


  Note this is on linux, and the ffmpeg part is not a problem.

  


  Thx
Timothé

  


• How can I split an RTSP stream so that I can both save it to files and apply a motion detection client ? (e.g. ffmpeg, motion)

  1er septembre 2022, par Pat Niemeyer

  I’ve been using "motion" successfully to read an rtsp stream and save motion triggered events.

  


  motion -c motion.conf # config file has the rtsp url and other params


  


  However I’d like to both save the full stream and analyze for motion in this way. I know that I can capture the stream to files with ffmpeg something like this :

  


  ffmpeg -i rtsp://mystream -vcodec copy -acodec copy -map 0 -f segment -segment_time 300 -segment_format mp4 "ffmpeg_capture-%03d.mp4"


  


  Is there is a way to split / duplicate the rtsp stream (perhaps using ffmpeg again) so that I can have both motion and ffmpeg processes looking at it simultaneously ? Alternately is there some option on motion that I’m missing that would automatically save both the raw video and the motion segments ?