Talley Lambert

@ZBaker11, could you run one more test for me when you have a moment? On the command line, please just run ``` mmcore bench -c your_config.cfg ``` that will (hopefully)...

thanks!

ok, then that suggests that the dual-call to `SENDING: RUN` is caused upstream, in the driver itself (or core, or your config), and not something that pymmcore-plus is doing

hey @ZBaker11, there are tons of options for that. it might be useful for us to have a zoom at some point. but briefly: - a very quick way to...

`self._mmc.snapImage()` literally does nothing but call the C++ code via pymmcore. so the camera isn't being addressed here any differently than it would be via the java mm studio app....

> literally does nothing but call the C++ code via pymmcore actually... i take that back... it does have a little additional logic related to autoshutter: https://github.com/pymmcore-plus/pymmcore-plus/blob/75cea0737ee6624209709c907991df4d8185f325/src/pymmcore_plus/core/_mmcore_plus.py#L1429-L1444 so, perhaps also...

Ah yes, I’ve always had difficulty using the pvcam driver simply (I’ve seen that buffer error that you mention). But I can’t remember the details on that driver. @marktsuchida? Do...

> I don't remember any problem with PVCAM in general what I'm recalling is that, with other photometrics cameras I have used. Simply doing the standard `loadDevice`, `initializeDevice`, `snapImage` programmatically...

hey @ZBaker11 glad you're still working at it. a couple quick notes here: it is interesting that setProperty alone incurs 100ms... that probably has to do with the camera driver...

Aha! Double snap image without get :). I see! That’s helpful. And I don’t think that should happen… so let’s look in the c++ code for hints