Changes between Version 32 and Version 33 of DirectShow


Ignore:
Timestamp:
Jan 1, 2015, 6:03:54 PM (4 years ago)
Author:
rogerdpack
Comment:

update bug list, some in works

Legend:

Unmodified
Added
Removed
Modified
  • DirectShow

    v32 v33  
    157157Send a message to rogerdpack@gmail.com if you want to discuss these issues.
    158158}}}
    159 
     159*
    160160* unable to specify device by guid (but you can use name/index currently, sometimes this isn't enough for certain names not console friendly)
    161161
    162162* "could not enumerate video devices" -> "could not enumerate or none installed"
    163163* video property enumeration using `-video_device_number` appears to be broken (is using it broken too?)
    164 * does not work with crossbar devices (see above mention of amarectv)
    165 * 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]
    166 * if you have `-i audio=x:video=x` and video comes too frequently ("dropping packet") it might start dropping audio packets too, which may not be desired (ping me if you want this fixed).
     164* does not work with crossbar devices (email roger for experimental patch)
     165* 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
     166* wants an option "never drop initial packets" during setup 
    167167* 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.
    168168* currently no ability to select "i420" from various yuv options: http://ffmpeg.org/pipermail/ffmpeg-devel/2014-March/155497.html
    169 * cannot use audio pins on certain "combined" video/audio sources http://stackoverflow.com/questions/19113197/ffmpeg-directshow-capture-2-pins
    170 * json output?
     169* 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