I’m also seeing another very bizarre behavior, where my output fps (as reported by Timing) drops to 30fps, unless I click on the VideoOut node to highlight it; then the output fps goes to 60. Clicking anywhere else in the patch drops the fps back to 30. But this is in a much larger patch and I have yet to be able to isolate a test case.
i wasn’t able to reproduce the situation jet. tried your patch in beta27.1 with a microsoft hd webcam (on a vista 32bit machine), running with 60fps and i saw no differences in framerate between the preview and video-output. both constantly about 30fps, either the property page was opened or not.
the latency was about 150ms in both versions, beta26 and beta27.1
maybe it is ps3cam specific…
will try the same thing with a ps3cam on monday.
well… now i tried the same thing again with the microsoft hd webcam and a ps3eye. while your patch works fine with the microsoft cam, i noticed exactly the same problems with the ps3eye that you described above. not only showing up with the property-page, but with every different window, like the firefox-browser for example.
it looks like its a ps3eye specific problem, but to be honest - i have no idea how to explain that properly.
i have app. 3 frames by 30fps =100 ms using PS3 with VideoIn measuring time between action and appearing on screen (beta 27.1/Win7 and CL-EyeTest.exe)
i have app. the same latency using IDS UI122x LE with VideoIn
i can get smaller latency (50-60 ms) only using uEyeCam (Devices) plugin.