Recherche avancée

Sur d’autres sites (11004)

• How can I make a Transcoded Video Filestream using C# and .NET Core

  25 avril 2021, par Drew Chase

  Overview

  


  I'm currently working on a media streaming server using ASP.net Core REST Server. I'm currently using .net 5.0 and ASP.net Core MVC

  


  What I need

  


  I need to be able to dynamically down-res the original video file. from 1080p to 720p for example.
Also I need to be able to make the media file able to be transcoded to a different encoding based on client capabilities.

  


  What I've Tried

  


  I've been looking for a library that can manage this feat, but I can't seem to find one. I thought FFMpeg would be able to do this. I know this is possible because applications like plex and emby seem to manage this.

  


  What I've Done

  


  [HttpGet("/api/streaming/video")]
public IActionResult GetFile()
{
    string path = "C:\Path\To\Video\FILE.mp4";
    System.IO.FileStream stream = new(path, System.IO.FileMode.Open, System.IO.FileAccess.Read);
    Microsoft.AspNetCore.Mvc.FileStreamResult file = File(stream, "video/mp4", true);
    return file;
}


  


  Framework Tried

  


  

  • Xabe.FFmpeg

  


  • FFMpegSharp

  


  


• ffmpeg direct show obvoius problem. ffmpeg is not letting to reconnect to camera

  11 avril 2021, par josh joyer

  I use ffmpeg with command

  


  ffmpeg -f dshow -i video="@device_pnp_\\?\usb#vid_1908&pid_2311&mi_00#6&353461d3&0&0000#{65e8773d-8f56-`11d0-a3b9-00a0c9223196}\global" output.mkv`


  


  It is fine to record camera but it uses direct show standard
Microsoft Windows library that is faulty.
Once connected to camera one is unable to use camera again or disconnect from it.
One should restart computer to connect to camera again.
Microsoft tells not to use direct show (dshow) for camera but
to use AForge or VisioForge libraries.

  


  But ffpmeg uses faulty dshow library. Is there any way to
change direct show to some other so one could connect to camer multiple times ?

  


• HTML5 Video Compatibility (MP4, WEBM, OGG) in 2021

  19 juillet 2021, par William

  The support of HTML5 video has evolved a lot over the years. I am trying to understand whether the <video></video> element still needs to have three sources : MP4, WEBM, and OGG.

  


  There are a lot of answers throughout StackOverflow with deeply conflicting information - some of which say that you just need MP4 now, others say, MP4 and WEBM are enough, and then finally many say that you need all three (although many of those article are 10 years old).

  


  W3 suggests that either MP4 or WEBM alone would have universal support (Even though I found a 2011 article from Google saying that they would be removing support for MP4/H.264). Wikipedia paints a more complicated picture (as well as listing that Google Chrome does indeed support MP4/H.264). Azure Media services ONLY seems to allow output in MP4, which would suggest to me that MP4 must have widespread compatibility.

  


  Also see Example 1, Example 2, Example 3.

  


  Is there any definitive information on what video types to include in an HTML5 video player to achieve widespread compatibility ?

  


  Background : I am building a Content Management Platform that allows uploading videos. When a new video is uploaded, a conversion process kicks off to convert the video into the required formats. This takes time and CPU/Memory, so if it is possible I would like to convert uploaded videos into as few formats as possible.

  


  p.s. This question HAS been asked before, however, the fundamentals of playing video on the web continually evolve and most of the answers out there have become irrelevant.