Changes between Version 38 and Version 39 of DirectShow


Ignore:
Timestamp:
Jan 27, 2015, 10:47:36 PM (3 years ago)
Author:
rogerdpack
Comment:

and we're live with crossbar support

Legend:

Unmodified
Added
Removed
Modified
  • DirectShow

    v38 v39  
    118118== !TroubleShooting == 
    119119 
    120 If you have a video capture card with multiple inputs (ex: !AverMedia, possibly some !BlackMagic, etc.) it may not work (yet) out of the box with FFmpeg, as it lacks crossbar support presently. email rogerdpack@gmail.com to test an experimental patch 
     120 email rogerdpack@gmail.com  
    121121 
    122122== Using !DirectShow with libav* == 
     
    160160}}} 
    161161* Do you have a feature request? Anything you want added? digital capture card support added? analog tv tuner support added? email me (see above).  Want any of the below fixed? email me... 
    162 * does not work with crossbar devices (email roger for experimental patch!) 
    163 * may not work with devices that somehow share audio and video together [http://stackoverflow.com/questions/16618686/directshow-capture-source-and-ffmpeg DirectShow Capture Source and FFmpeg] -- email roger for experimental patch 
    164 * currently there is no ability to "push back" against upstream sources if ffmpeg is unable to encode fast enough, this might be nice to have. 
     162* currently there is no ability to "push back" against upstream sources if ffmpeg is unable to encode fast enough, this might be nice to have in certain circumstances, instead of dropping it when the rtbuffer is full. 
    165163* currently no ability to select "i420" from various yuv options [screen capture recorder] meh  
    166 * doesn't work with medialooks screen capture: http://ffmpeg.org/pipermail/ffmpeg-devel/2014-March/155497.html 
    167 * cannot use audio pins on certain "combined" video/audio sources http://stackoverflow.com/questions/19113197/ffmpeg-directshow-capture-2-pins ping roger for experimental patch 
    168 * could use an option "just keep latest frame" to decrease latency to absolute minimum 
    169 * could use an option "trust video timestamps" 
    170 * lacks "show filter properties dialog" option/serialization 
    171 * cannot take more than 2 inputs [today] per invocation. this can be arranged, please sak 
     164* could use an option "trust video timestamps" today it just uses wall clock time... 
     165* lacks "filter properties dialog"serialization 
     166* cannot take more than 2 inputs [today] per invocation. this can be arranged, please ask if it is a desired feature 
    172167* no device enumeration API as of yet (for libav users).  At least do the name!