Recherche avancée

Sur d’autres sites (6801)

• Webcam - Publishing and Archiving on line video files

  11 novembre 2014, par Emmanuel Brunet

  I want to publish an ASF live video stream over the internet and also copy the backup to disk (without sound to spare disk space)

  I’m running debian 7.7 wheezy / ffmpeg 2.2 and ffserver 1.2.9.

  ---

  The IP camera video streams specifications are

  Input #0, asf, from 'http://account:password@webcam/videostream.asf':
  
    Duration: N/A, start: 0.000000, bitrate: 32 kb/s
  
      Stream #0:0: Video: mjpeg (MJPG / 0x47504A4D), yuvj422p(pc), 640x480, 50 tbr, 1k tbn, 1k tbc
  
      Stream #0:1: Audio: adpcm_ima_wav ([17][0][0][0] / 0x0011), 8000 Hz, 1 channels, s16p, 32 kb/s

  To achieve this I have set up a /etc/ffserver.conf configuration

  Port 11000
  
  
  
  BindAddress 0.0.0.0
  
  
  
  MaxClients 1000
  
  
  
  MaxBandwidth 40000
  
  
  
  CustomLog -
  
  
  
  <feed>
  
  File /tmp/feed1.ffm
  
  FileMaxSize 200K
  
  ACL allow localhost
  
  ACL allow 192.168.1.1 192.168.255.255
  
  
  
  </feed>
  
  
  
  
  
  # --------------------------- ASF ----------------------
  
  
  
  <stream>
  
  Feed feed1.ffm
  
  Format asf
  
  
  
  AVOptionVideo flags +global_header
  
  VideoFrameRate 25
  
  VideoSize 640x480
  
  VideoBitRate 1024
  
  VideoBufferSize 1024
  
  StartSendOnKey
  
  NoAudio
  
  </stream>
  
  
  
  # ------------ Server status -------------------
  
  
  
  <stream>
  
  Format status
  
  
  
  # Only allow local people to get the status
  
  ACL allow localhost
  
  ACL allow 192.168.0.0 192.168.255.255
  
  
  
  #FaviconURL http://pond1.gladstonefamily.net:8080/favicon.ico
  
  </stream>
  
  
  
  
  
  # ---------- Redirect --------------------
  
  
  
  <redirect>
  
  URL http://www.ffmpeg.org/
  
  </redirect>

  To connect the feed I run

  to start the ffserver

  ffserver -f /etc/ffserver.conf

  to collect the stream from the camera

  ffmpeg -i http://account:password@webcam/videostream.asf -c:v libx264 -an http://localhost:11000/feed1.ffm

  and all works like a charm.

  ---

  My questions are :

  • How in the same time having the stream saved to disk ?

  (as done by the command)

  ffmpeg -i http://account:password@webcam/videostream.asf -preset veryfast -t 00:60:00 -b:v 512K -c:v libx264 -pix_fmt yuv420p -an /var/backup/videos/YYY-MM-DD.mp4

  Note that the output .mp4 file names should rotate to get multiple timestamped output archives

  • How can I published video over RTSP ?

  I’ve found examples on the internet but none worked for me

  Thanks in advance

  regards

• Can't build ffmpeg

  7 avril 2016, par Dev_Vlad

  I have some problems with building ffmpeg for servestream radio.

  Here’s the log :

  build-ffmpeg:
  
   [exec] arm-linux-androideabi-gcc is unable to create an executable file.
  
   [exec] C compiler test failed.
  
   [exec] 
  
   [exec] If you think configure made a mistake, make sure you are using the latest
  
   [exec] version from Git.  If the latest version fails, report the problem to the
  
   [exec] ffmpeg-user@ffmpeg.org mailing list or IRC #ffmpeg on irc.freenode.net.
  
   [exec] Include the log file "config.log" produced by configure as this will help
  
   [exec] solving the problem.
  
   [exec] Copying FFmpeg .so files from /home/vlad/WORK/Ubuntu/OnlineRadioSamples/servestream-master-minstrely/submodules/ffmpeg-0.11.1-android-2012-09-18/build/ffmpeg to /home/vlad/WORK/Ubuntu/OnlineRadioSamples/servestream-master-minstrely/jni/ffmpeg/ffmpeg/armeabi
  
   [exec] Copying FFmpeg .so files from /home/vlad/WORK/Ubuntu/OnlineRadioSamples/servestream-master-minstrely/submodules/ffmpeg-0.11.1-android-2012-09-18/build/ffmpeg to /home/vlad/WORK/Ubuntu/OnlineRadioSamples/servestream-master-minstrely/jni/ffmpeg/ffmpeg/armeabi-v7a
  
   [exec] Native build complete, exiting...
  
   [exec] cp: не could not execute stat for «/home/vlad/WORK/Ubuntu/OnlineRadioSamples/servestream-master-minstrely/submodules/ffmpeg-0.11.1-android-2012-09-18/build/ffmpeg/armeabi-v7a»: No such file or catalog
  
  
  
  native-clean:
  
   [exec] Android NDK: WARNING: APP_PLATFORM android-17 is larger than android:minSdkVersion 8 in ./AndroidManifest.xml    
  
   [exec] Android NDK: ERROR:jni/ffmpeg/Android.mk:avcodec: LOCAL_SRC_FILES points to a missing file    
  
   [exec] Android NDK: Check that jni/ffmpeg/ffmpeg/armeabi/lib/libavcodec.so exists  or that its path is correct   
  
   [exec] /home/vlad/android/ndk/build/core/prebuilt-library.mk:45: *** Android NDK: Aborting    .  Stop.

  In arm-build.sh file I edited some lines :

  export NDK=${HOME}/android-ndk

  to

  export NDK=/home/vlad/android/ndk

  next :

  TOOLCHAIN=`echo $NDK/toolchains/arm-linux-androideabi-4.6/prebuilt/linux-x86*`

  to

  TOOLCHAIN=`echo $NDK/toolchains/arm-linux-androideabi-4.9/prebuilt/linux-x86*`

  What’s wrong ?

• avformat/hlsenc : strftime identifiers and segment index

  27 décembre 2016, par Bodecs Bela

  avformat/hlsenc : strftime identifiers and segment index
   in filenames
  Putting date/time values into segment filenames is very usefull.
  
  But to produce non-conflicting segment filenames with -use_localtime
  
  option with date/time
  
  values in hls_segment_filename option, sometimes is not enough.
  
  Like in cases when multiple segments produced in the same second.
  
  But hlsenc currently does not make possible to use segment index (%d) at
  
  the
  same time whe use_localtime is in effect, due to identifier conflict.
  
  This patch makes possible to use strftime identifiers and still put
  
  segment index (%d) at same time in segment filenames by introducing
  
  second_level_segment_index flag. When -use_localtime is active,
  
  identifier %d is for month day index, so %%d is the segment index
  
  placeholder. This enhanced behaviour only exists when new
  
  second_level_segment_index flag is specified.
  
  For instance putting ’segment_%Y%m%d%H%M%S_%%05d.ts’ value into
  
   hls_segment_filename option and specifing -hls_flags
  
  second_level_segment_index and -use_localtime 1, may produce segment
  
  filename as ’segment_20161230235758_00002.ts’
  An example :
  ffmpeg -loglevel info -y -f lavfi -i color=c=red:size=640x480:r=25 -f
  
  lavfi -i anullsrc=r=44100:cl=stereo -c:v mpeg2video -g 25 -acodec aac
  
   cutoff 20000 -ac 2 -ar 44100 -ab 192k -f hls -hls_time 3 -hls_list_size
  
  5 -hls_flags delete_segments+second_level_segment_index -use_localtime 1
  
   hls_segment_filename "segment_%Y%m%d%H%M%S_%%05d.ts" stream.m3u8
  will produce segments filenames :
  ....
  
  segment_20161227005902_00013.ts
  
  segment_20161227005902_00014.ts
  
  segment_20161227005902_00015.ts
  
  segment_20161227005903_00016.ts
  
  segment_20161227005903_00017.ts
  
  segment_20161227005903_00018.ts
  
  segment_20161227005903_00019.ts
  
  segment_20161227005903_00020.ts
  
  ....
  Signed-off-by : Bela Bodecs <bodecsb@vivanet.hu>
  

  • [DH] doc/muxers.texi
  • [DH] libavformat/hlsenc.c