Recherche avancée

Sur d’autres sites (8850)

• FATE Under New Management

  2 août 2010, par Multimedia Mike — FATE Server

  At any given time, I have between 20-30 blog posts in some phase of development. Half of them seem to be contemplations regarding the design and future of my original FATE system and are thus ready for the recycle bin at this point. Mans is a man of considerably fewer words, so I thought I would use a few words to describe the new FATE system that he put together.

  Overview
  Here are the distinguishing features that Mans mentioned in his announcement message :

  • Test specs are part of the ffmpeg repo. They are thus properly versioned, and any developer can update them as needed.
  • Support for inexact tests.
  • Parallel testing on multi-core systems.
  • Anyone registered with FATE can add systems.
  • Client side entirely in POSIX shell script and GNU make.
  • Open source backend and web interface.
  • Client and backend entirely decoupled.
  • Anyone can contribute patches.

  Client
  The FATE build/test client source code is contained in tests/fate.sh in the FFmpeg source tree. The script — as the extension implies — is a shell script. It takes a text file full of shell variables, updates source code, configures, builds, and tests. It’s a considerably minor amount of code, especially compared to my original Python code. Part of this is because most of the testing logic has shifted into FFmpeg itself. The build system knows about all the FATE tests and all of the specs are now maintained in the codebase (thanks to all who spearheaded that effort— I think it was Vitor and Mans).

  The client creates a report file which contains a series of lines to be transported to the server. The first line has some information about the configuration and compiler, plus the overall status of the build/test iteration. The second line contains ’./configure’ information. Each of the remaining lines contain information about an individual FATE test, mostly in Base64 format.

  Server
  The server source code lives at http://git.mansr.com/?p=fateweb. It is written in Perl and plugs into a CGI-capable HTTP server. Authentication between the client and the server operates via SSH/SSL. In stark contrast to the original FATE server, there is no database component on the backend. The new system maintains information in a series of flat files.

• vdpau : add av_vdpau_bind_context()

  4 octobre 2014, par Rémi Denis-Courmont

  vdpau : add av_vdpau_bind_context()
  This function provides an explicit VDPAU device and VDPAU driver to
  
  libavcodec, so that the application is relieved from codec specifics
  
  and VdpDevice life cycle management.
  A stub flags parameter is added for future extension. For instance, it
  
  could be used to ignore codec level capabilities (if someone feels
  
  dangerous).
  Signed-off-by : Anton Khirnov <anton@khirnov.net>
  

  • [DBH] doc/APIchanges
  • [DBH] libavcodec/vdpau.c
  • [DBH] libavcodec/vdpau.h
  • [DBH] libavcodec/vdpau_internal.h
  • [DBH] libavcodec/version.h

• usb capture device to "cast" stream

  6 juin 2021, par cubesareneat

  im using a raspberry pi with a usb capture device (dmesg -w below)

  


  [ 3825.105250] cx231xx 1-1.4:1.1: New device Geniatech Inc. Video Capture @ 480 Mbps (1f4d:0102) with 6 interfaces
[ 3825.105571] cx231xx 1-1.4:1.1: Identified as Geniatech OTG102 (card=17)
[ 3825.106698] i2c i2c-12: Added multiplexed i2c bus 14
[ 3825.106948] i2c i2c-12: Added multiplexed i2c bus 15
[ 3825.233031] cx25840 11-0044: cx23102 A/V decoder found @ 0x88 (cx231xx #0-0)
[ 3827.270228] cx25840 11-0044: loaded v4l-cx231xx-avcore-01.fw firmware (16382 bytes)
[ 3827.307022] cx231xx 1-1.4:1.1: v4l2 driver version 0.0.3
[ 3827.411911] cx231xx 1-1.4:1.1: Registered video device video0 [v4l2]
[ 3827.412183] cx231xx 1-1.4:1.1: Registered VBI device vbi0
[ 3827.418150] cx231xx 1-1.4:1.1: audio EndPoint Addr 0x83, Alternate settings: 3
[ 3827.418179] cx231xx 1-1.4:1.1: video EndPoint Addr 0x84, Alternate settings: 5
[ 3827.418203] cx231xx 1-1.4:1.1: VBI EndPoint Addr 0x85, Alternate settings: 2
[ 3827.418224] cx231xx 1-1.4:1.1: sliced CC EndPoint Addr 0x86, Alternate settings: 2


  


  i want to stream the audio to "cast" dose this protocol have a more specific name ? its the one that Spotify and YouTube can send audio video to over local network ; little screen with a wifi signal in the bottom left corner.

  


  i am thinking of going into ffmpeg or vlc to stream from usb to some cast program, dose anyone have any suggestions on where to start any key words so im not blindly googling ?
sorry this is so open ended, ill mark it solved with the best answer in like 5 days or when i finish this project ( turntable -> usb audio capture card on pi -> steam to cast protocol -> wifi speakers )