Recherche avancée

Sur d’autres sites (7927)

• Merge commit ’271ce76d317c5432e151216cf23f12b77ed6cb7e’

  30 juin 2015, par Michael Niedermayer

  Merge commit ’271ce76d317c5432e151216cf23f12b77ed6cb7e’
  * commit ’271ce76d317c5432e151216cf23f12b77ed6cb7e’ :
  
    h264 : Parse registered data SEI message and AFD value
  Conflicts :
  
  	libavcodec/h264.c
  
  	libavcodec/h264.h
  
  	libavcodec/h264_sei.c
  
  	libavcodec/version.h
  See : d6e95669496a89d186f923c34bcaf7d86b7cd59c
  
  See : 22291c372fa703242e8429bed61700ba81258f19
  
  Merged-by : Michael Niedermayer <michaelni@gmx.at>
  

  • [DH] libavcodec/h264.c
  • [DH] libavcodec/h264.h
  • [DH] libavcodec/h264_sei.c
  • [DH] libavcodec/version.h

• looking for Settings for FFmpeg, xTeVe, Plex [closed]

  3 août 2022, par Chris

  I am not sure if I am in the right place. But maybe someone can help me.

  


  Sorry for my bad english.

  


  I have a Qnap NAS, on this is insalled FFmepg, xTeVe and Plex.
I try to see IPTV Streams on Plex.

  


  Here the log file from xTeVe :

  


  ---

  


  2022-02-28 21:57:42 [xTeVe] Buffer : true [ffmpeg]

  


  2022-02-28 21:57:42 [xTeVe] Buffer Size : 4096 KB

  


  2022-02-28 21:57:42 [xTeVe] Channel Name : VIP SW : SRF 1 FHD

  


  2022-02-28 21:57:42 [xTeVe] Client User-Agent : Lavf/58.65.101

  


  2022-02-28 21:57:43 [xTeVe] Streaming Status : Playlist : Schweiz Neu - Tuner : 1 / 1

  


  2022-02-28 21:57:43 [xTeVe] FFMPEG path : /usr/bin/ffmpeg

  


  2022-02-28 21:57:43 [xTeVe] Streaming URL : http://tunestream.me:8080/XXXXXXX
/XXXXXXXX/9165

  


  2022-02-28 21:57:43 [xTeVe] FFMPEG : Processing data

  


  2022-02-28 21:57:43 [xTeVe] Streaming Status : Receive data from FFMPEG

  


  2022-02-28 21:57:43 [xTeVe] FFMPEG log : [mpegts @ 0x55e0732fe560] dimensions
not set

  


  2022-02-28 21:57:43 [xTeVe] [ERROR] FFMPEG error (Streaming was stopped by third party
transcoder (FFmpeg / VLC)) - EC : 1204

  


  2022-02-28 21:57:43 [xTeVe] FFMPEG log : Could not write header for output file
#0 (incorrect codec parameters ?) : Invalid argument

  


  2022-02-28 21:57:43 [xTeVe] FFMPEG log :

  


  2022-02-28 21:57:43 [xTeVe] Streaming Status : Client has terminated the connection

  


  2022-02-28 21:57:43 [xTeVe] Streaming Status : Channel : VIP SW : SRF 1 FHD (Clients : 0)

  


  2022-02-28 21:57:44 [xTeVe] Streaming Status : Channel : VIP SW : SRF 1 FHD - No client
is using this channel anymore. Streaming Server connection has ended

  


  2022-02-28 21:57:44 [xTeVe] Streaming Status : Playlist : Schweiz Neu - Tuner : 0 / 1

  


  ---

  


  on xTeVe i set this settings :

  


  Buffer Size : 5 MB

  


  Timeout for new client connections : 500

  


  FFmpeg Options : -hide_banner -loglevel error -i [URL] -c copy -f mpegts pipe:1

  


  If i put the Streaming URL on VLC is working.
But not with FFmpeg, xTeVe and Plex.

  


  Thanks for your help.

  


  Greetings
Chris

  


• 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...