Recherche avancée

Sur d’autres sites (10866)

• Chromium Build Failed on Windows:D3D Compiler DLL (\third_party\angle\src)

  31 mars 2016, par Vish

  I have followed same step mentioned in this question. Few extra flag I have set get propriety FFMPEG codec. Its failing every time, with following logs.

  [233/19712] ACTION Copying D3D Compiler DLL...
  
  FAILED: F:\Chrome\depot_tools\python276_bin\python.exe gyp-win-tool action-wrapper environment.x86 copy_compiler_dll_target_copy_dll_a30e198148542d4bce19a5c818c6884f..rsp ..\..\third_party\angle\src
  
  [233/19712] CC obj\third_party\icu\source\stubdata\icuuc.stubdata.obj
  
  ninja: build stopped: subcommand failed.

  For FFMPEG using following set command :

  set GYP_DEFINES=branding=Chromium buildtype=Official component=shared_library disable_nacl=1 enable_automation=0 enable_captive_portal_detection=0 enable_google_now=0 enable_hidpi=0 fastbuild=1 ffmpeg_branding=Chrome incremental_chrome_dll=0 proprietary_codecs=1 remoting=0

  My System Information Details :

  Windows 10 64 Bit 8 GB RAM. Trail Version of Visual Studio 2015
  Installed, but now it is expired. Now I have installed Community
  Version 2013 update 4.

  Does it effect both version effect the execution ? Checked in path, its using Window Kit 8.1. What other part should I check for successful execution ?

• muxing streamable segmented mp4 with libav

  24 juillet 2020, par Elias Wagnerberger

  currently i have an application that is supposed to send fragmented mp4 data over a websocket to a client for it to be played there.

  


  i have a working implementation that pipes the raw frames to a spawned ffmpeg process and then reads fragmented mp4 segments from the output pipe before it sends those on to the client where the client then displays the video correctly.

  


  my problem is that when i try to make an implementation using libav it doesnt seem to work. my libav config uses libx264 to encode the frames before muxing them to a mp4, but when i try to play the provided segments in a browser using MSE it spits out an error. after having checked chrome ://media-internals i have figured out that chrome complains when i provide the moov box that is one of the two initialization boxes of a fmp4 stream.

  


  chrome apparently has a problem with parsing that box when its sent from libav, but not when its sent from ffmpeg.

  


  my question is :
What is the correct muxer configuration of libav so that it creates a fragmented mp4 stream where the client can recieve media boxes from the middle, after having been provided the init boxes ?

  


• muxing streamable segmented mp4 with libav

  24 juillet 2020, par Elias Wagnerberger

  currently i have an application that is supposed to send fragmented mp4 data over a websocket to a client for it to be played there.

  


  i have a working implementation that pipes the raw frames to a spawned ffmpeg process and then reads fragmented mp4 segments from the output pipe before it sends those on to the client where the client then displays the video correctly.

  


  my problem is that when i try to make an implementation using libav it doesnt seem to work. my libav config uses libx264 to encode the frames before muxing them to a mp4, but when i try to play the provided segments in a browser using MSE it spits out an error. after having checked chrome ://media-internals i have figured out that chrome complains when i provide the moov box that is one of the two initialization boxes of a fmp4 stream.

  


  chrome apparently has a problem with parsing that box when its sent from libav, but not when its sent from ffmpeg.

  


  my question is :
What is the correct muxer configuration of libav so that it creates a fragmented mp4 stream where the client can recieve media boxes from the middle, after having been provided the init boxes ?