locked
SampleGrabberSink respect MF_TOPONODE_WORKQUEUE_ID RRS feed

  • Question

  • I am using the SampleGrabberSink in an real-time application where multiple sources are being decoded at the same time.  I am able to set MF_TOPONODE_WORKQUEUE_ID on the source node so that each source is running in its own work queue but I'm still seeing the sample grabber calling my callback from the same thread.   Is there a way to force the samplegrabber to create its own work queue for each topology?  I have another node in the same topology that is running its own queue.



    Jay

    Friday, April 8, 2016 1:24 PM