Leaked source code of windows server 2003
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

40 lines
1.7 KiB

  1. Work items for Vfw capture driver wrapper
  2. 1) Support IOverlay
  3. No work has been done yet to support overlays.
  4. the thunks should already exist. refer to
  5. motown\avicap.32\*.c to see how avicap manages overlays
  6. the thunks from avicap.32 are already in place in this
  7. filter
  8. 2) Support IReferenceClock slaved to the VSYNC clock.
  9. the _vsyncmem structure in vidx.h is the structure
  10. that will be shared with the driver. the driver will
  11. update this struture with a QPC value and with a VSYNC
  12. count on each vsync. we will expose a clock that
  13. periodically checks this memory and keeps it's own clock
  14. (based on QPC from drifting relative to this memory)
  15. the thunks for this have been written but not tested.
  16. (see vidxSetupVsyncMem)
  17. 3) Complete work to support IPropertyPage. the thunking
  18. for videoDialog is complete. No new thunks should
  19. be necessary here, just expose editing of _vfwcaptureoptions.
  20. A new thunk to enum video capture drivers may make life easier.
  21. one caveat here: VfwCapDriverDialog currently works only
  22. when the filters is Paused (because only then does it have
  23. the driver open).
  24. 4) Expose Line21 (closed caption) and SMPTE timecode streams.
  25. Thunks for these are complete (these streams are returned
  26. as extra fields in the VIDEOHDREX for each frame captured).
  27. 5) Support variable frame rate capture (for video conferencing).
  28. preferably some form of frame-on-demand rather than doing
  29. this by munging frame rates on the fly.
  30. 6) Port to NT. all of the vidxZZZ functions are part of the
  31. thunking layer. equivalents will have to be written for NT.
  32. (some of this work has aleady been done in the NT version
  33. of avicap32.