Ureader.com  
Microsoft software help and Community
   home   |   control panel login   |   archive   |  
 
Windos
win32.3rdparty
win32.directx.audio
win32.directx.ddk
win32.directx.graphics
win32.directx.input
win32.directx.managed
win32.directx.misc
win32.directx.networking
win32.directx.sdk
win32.directx.video
win32.dirx.grap.shaders
win32.gdi
win32.international
win32.kernel
win32.messaging
win32.mmedia
win32.networks
win32.ole
win32.rtc
win32.tapi
win32.tapi.beta
win32.tools
win32.ui
win32.wince
win32.wmi
windows.mediacenter
winfx.aero
winfx.announcements
winfx.avalon
winfx.collaboration
winfx.fundamentals
winfx.general
winfx.indigo
winfx.sdk
winfx.winfs
  
 
date: Mon, 27 Mar 2006 15:41:51 +0200,    group: microsoft.public.win32.programmer.directx.sdk        back       


Grabber and GetCurrentBuffer performance   
Hi,
looking for the best image processing performance based on Grabber filtet, 
I've tried to setup a Grabber in buffering mode.
I call GetCurrentBuffer,  copy the returned buffer to a new one and  launch 
a different thread to process the buffer.
Unfortunately if I call the GetCurrentBuffer to quickly the function returns 
always the same buffer. Somehow the buffer seems to be locked even if I 
should work  on a different copy.
Note that after the lock, the buffer sometime returns "free" to change.
In fact, If  I display the buffer, the video is frozen for certain period.

Any idea?
Thx
date: Mon, 27 Mar 2006 15:41:51 +0200   author:   aaa

Google
 
Web ureader.com


    COPYRIGHT 2007, YARDI TECHNOLOGY LIMITED, ALL RIGHT RESERVE  |   contact us