Recherche avancée

Sur d’autres sites (12614)

• RTSP to RTMP Youtube Live only displays online for few seconds

  2 juin 2016, par Poison

  I’m trying to get the feed from an IP camera to Youtube Live. Simple enough uh.

  The command I’m using is the usual :

  ffmpeg -i rtsp://user:pass@ip:port/videoMain -f flv -r -s -an rtmp://a.rtmp.youtube.com/live2/per-sonal-code

  What happens

  Live Youtube receives the signal and says its healthy, after two or less seconds a red box appears saying they’re not receiving my signal. After that it displays "No signal". Webcam image is never shown.

  What I’ve tried

  Different parameters (-re, -rtsp_transport tcp, -s 640x480, -g 30, -r 30 ..) and different combinations of them, plus different resolutions, different buffer sizes and stream sizes, and different Ingestion settings on Youtube.

  Followed different very basic stuff tutorials.

  I’ve done it with ffmpeg in Windows 7 and Ubuntu 16.04, different networks (home and work), checked for possible port problems,...

  What confuses me

  Using streaming software like XSplit, or Manycam it actually works on the same computers !
  Also using the different command combinations, Youtube always receives the signal and its healthy before changing and displaying "No signal", its not complaining about low bitrate, or wrong format like I’ve seen in the different tutorials.

  I need to create two different streams for two cams, so ideally I’d prefer to use ffmpeg. However if anyone knows a software that can do this, please tell me. I’ve been stuck with this long enough !

  Thanks.

• Unbound variable error when installing ffmpeg on openshift online

  31 août 2016, par sinabakh

  I followed the steps on https://forums.openshift.com/ffmpeg but when performing make install I got this error :

  INSTALL doc/ffmpeg.1
  
  INSTALL doc/ffprobe.1
  
  INSTALL doc/ffserver.1
  
  INSTALL doc/ffmpeg-all.1
  
  INSTALL doc/ffprobe-all.1
  
  INSTALL doc/ffserver-all.1
  
  INSTALL doc/ffmpeg-utils.1
  
  INSTALL doc/ffmpeg-scaler.1
  
  INSTALL doc/ffmpeg-resampler.1
  
  INSTALL doc/ffmpeg-codecs.1
  
  INSTALL doc/ffmpeg-bitstream-filters.1
  
  INSTALL doc/ffmpeg-formats.1
  
  INSTALL doc/ffmpeg-protocols.1
  
  INSTALL doc/ffmpeg-devices.1
  
  INSTALL doc/ffmpeg-filters.1
  
  INSTALL doc/libavutil.3
  
  INSTALL doc/libswscale.3
  
  INSTALL doc/libswresample.3
  
  INSTALL doc/libavcodec.3
  
  INSTALL doc/libavformat.3
  
  INSTALL doc/libavdevice.3
  
  INSTALL doc/libavfilter.3
  
  /var/lib/openshift//python//bin/install: line 10: version: unbound variable
  
  make: *** [install-man] Error 1

  And It’s the install file(which gives error) :

  #!/bin/bash -eu
  
  
  
  source $OPENSHIFT_CARTRIDGE_SDK_BASH
  
  
  
  case "$1" in
  
       -v|--version)
  
       version="$2"
  
  esac
  
  
  
  echo "$version" > ${OPENSHIFT_PYTHON_DIR}env/OPENSHIFT_PYTHON_VERSION
  
  
  
  mkdir -p ${OPENSHIFT_PYTHON_DIR}template
  
  
  
  # Call the version specific install script
  
  exec ${OPENSHIFT_PYTHON_DIR}usr/versions/${version}/bin/install $version

  So what is the problem ? And how can I solve it ?
  thanks

• HTML5 Progressive Streaming — no follow-up range requests

  20 septembre 2023, par user2333829

  I'm working on an embedded device that is recording video on the fly. I'd like to stream that to an HTML5 video element, using our own custom server. I have this almost working and would like some help.

  



  So far as I can tell, I've got libav / ffmpeg doing their job right. I encoded an mp4 in RAM with the moov atom at the start of the file. I've written this file to disk and it plays everywhere it should.

  



  The problem, I think, lies with how I'm responding to HTTP range requests. When I try to do a live stream, I get an initial range request from the browser / player (currently tried Chrome, Firefox, and VLC) for bytes:0-. I responded with some initial bytes. The browser / player actually plays this fine, but never asks again. So the live stream doesn't work, just the first 3 seconds or whatever.

  



  I've looked at the RFC spec of partial content, and my understanding is I'm doing what I should be... Clearly I'm not though. Here is an example of a request / response with Chrome as the requester :

  



  ---

  



  
get /live.mp4 HTTP/1.1
host: localhost:1235
connection: keep-alive
accept-encoding: identity;q=1, *;q=0
user-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.167 Safari/537.36
accept: */*
dnt: 1
accept-language: en-GB,en-US;q=0.9,en;q=0.8
range: bytes=0-


  



  
HTTP/1.1 206 Partial Content
Accept-Ranges: bytes
Content-Type: video/mp4
Content-Length: 182400
Content-Range: bytes 0-182399/*


  



  ---

  



  Again, with that request / response pair, Chrome plays the first 182400 bytes but never makes a second request. I thought having the '*' in Content-Range would make this happen...