Recherche avancée

Sur d’autres sites (7843)

• Creating own video server with ffserver/ffmpeg streaming RTSP

  24 août 2018, par Brykyz

  I have created app that plays video when url is provided. It can recieve video via RTSP (already tried to play famous big bunny), but now I want to debug it with my own server. Currently I have downloaded ffserver/ffmpeg and want to create my own video server, but i don’t know how.

  I have already tried

  ffserver &
  
  sudo ffmpeg -r 24 -i "video.mp4" http://localhost:8090/feed1.ffm
  
  ffplay http://localhost:8090/feed1.ffm

  but it doesn’t work. I am trying to achieve same thing that happens when I type to terminal

  ffplay rtsp://wowzaec2demo.streamlock.net/vod/mp4:BigBuckBunny_115k.mov

  (it should play my video), but I want to use private server.

  How can I create server that will stream video via RTSP ?

  Thank you for your help !

  //Edit :

  ffserver.conf

  HttpPort 8090 
  
  RtspPort 5554
  
  HttpBindAddress 0.0.0.0 
  
  MaxClients 1000 
  
  MaxBandwidth 10000 
  
  NoDaemon 
  
  
  
  <feed> 
  
  File /tmp/feed1.ffm 
  
  FileMaxSize 1000M 
  
  </feed> 
  
  
  
  <stream>
  
  Feed feed1.ffm
  
  Format rtp
  
  VideoCodec mpeg4
  
  VideoFrameRate 25
  
  VideoBufferSize 80000
  
  VideoBitRate 100
  
  VideoQMin 1
  
  VideoQMax 5
  
  VideoSize 1920x1080
  
  PreRoll 0
  
  Noaudio
  
  </stream>

  and I am trying to launch it via

  ffserver -d & ffmpeg -re -i "simpsons.mp4" http://localhost:8090/feed1.ffm

  and then

  ffplay "rtsp://localhost:5554/test.mpeg4"

  Output is

  [tcp @ 0x7fb0880079c0] Connection to tcp://localhost:5554?timeout=0 failed: Connection refused
  
  rtsp://localhost:5554/test.mpeg4: Connection refused

• avcodec/put_bits : Make bit buffers 64-bit

  18 juillet 2020, par Steinar H. Gunderson

  avcodec/put_bits : Make bit buffers 64-bit
  Change BitBuf into uint64_t on 64-bit x86. This means we need to flush the
  
  buffer less often, which is a significant speed win. All other platforms,
  
  including all 32-bit ones, are unchanged. Output bitstream is the same.
  All API constraints are kept in place, e.g., you still cannot put_bits()
  
  more than 31 bits at a time. This is so that codecs cannot accidentally
  
  become 64-bit-only or similar.
  Benchmarking on transcoding to various formats shows consistently
  
  positive results :
    dnxhd                 25.60 fps ->  26.26 fps ( +2.6%)
  
    dvvideo               24.88 fps ->  25.17 fps ( +1.2%)
  
    ffv1                  14.32 fps ->  14.58 fps ( +1.8%)
  
    huffyuv               58.75 fps ->  63.27 fps ( +7.7%)
  
    jpegls                 6.22 fps ->   6.34 fps ( +1.8%)
  
    magicyuv              57.10 fps ->  63.29 fps (+10.8%)
  
    mjpeg                 48.65 fps ->  49.01 fps ( +0.7%)
  
    mpeg1video            76.41 fps ->  77.01 fps ( +0.8%)
  
    mpeg2video            75.99 fps ->  77.43 fps ( +1.9%)
  
    mpeg4                 80.66 fps ->  81.37 fps ( +0.9%)
  
    prores                12.35 fps ->  12.88 fps ( +4.3%)
  
    prores_ks             16.20 fps ->  16.80 fps ( +3.7%)
  
    rv20                  62.80 fps ->  62.99 fps ( +0.3%)
  
    utvideo               68.41 fps ->  76.32 fps (+11.6%)
  Note that this includes video decoding and all other encoding work,
  
  such as DCTs. If you isolate the actual bit-writing routines, it is
  
  likely to be much more.
  Benchmark details : Transcoding the first 30 seconds of Big Buck Bunny
  
  in 1080p, Haswell 2.1 GHz, GCC 8.3, generally quantizer locked to
  
  5.0. (Exceptions : DNxHD needs fixed bitrate, and JPEG-LS is so slow
  
  that I only took the first 10 seconds, not 30.) All runs were done
  
  ten times and single-threaded, top and bottom two results discarded to
  
  get rid of outliers, arithmetic mean between the remaining six.
  Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>
  

  • [DH] libavcodec/asvenc.c
  • [DH] libavcodec/put_bits.h

• How to implement Clear-Key video encryption in PHP and play it in HTML [closed]

  22 octobre 2018, par Ali Farhoudi

  I want to implement video encryption in php and play encrypted video in HTML5 video. I have read some documents about it :

  • https://en.wikipedia.org/wiki/Encrypted_Media_Extensions
  • https://w3c.github.io/encrypted-media/

  And I know there are alternative tools and services that I can use :

  • https://support.uplynk.com/tut_embedding_the_uplynk_player_3.html
  • https://www.wowza.com/products/capabilities/streaming-content-security
  • https://www.intertrust.com/products/drm-system/livestream/
  • https://bitmovin.com/cenc-widevine-drm/
  • https://www.html5rocks.com/en/tutorials/eme/basics/

  I want to provide like this example :

  • https://demo.castlabs.com/ (play big buck bunny smooth streaming : that can’t be downloaded and the url is one-time usable)

  What steps should I pass ?
  I use PHP (laravel) in server-side.