Recherche avancée

Sur d’autres sites (7195)

• How to use ffmpeg to convert VCD(dat file) to a batch of images, then convert these images into another video ?

  4 juillet 2021, par Siwei

  I have a old VCD, and I want to enhance it using AI tech. my questions are :

  


  

  1. how to know the origin frame rate of this VCD(dat file) ?

  


  2. how to split this VCD into images with the raw frame rate ? ( I don't want to miss one frame )

  


  3. does google has the tech to enhance the old images ?

  


  4. once all the images are enhanced , how to re-combine these into a new video ?

  


  


  If these are some AI tech to repair/convert the entire VCD file, it's also a good choice.

  


  thanks a lot !

  


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

  


• Revision 407940243f : Changing initialization order of mb_to_top_edge & mb_to_bottom_edge Making cons

  21 mars 2013, par Dmitry Kovalev

  Changed Paths : Modify /vp9/decoder/vp9_decodemv.c Changing initialization order of mb_to_top_edge & mb_to_bottom_edge Making consistent initialization of mb_to_top,botton,left,right_edge variables after set_mb_row & set_mb_col calls. A little bit of code cleanup additionally. Change-Id : (...)