Only capturing when using ROI

ckhorne

I'm having a problem with several programs with my ASI290 cameras (both a 290MC and a 290MM, delivered today). I run VMWare Fusion - the lastest version, and all the latest drivers.

When running SharpCap (v2.9 and v3.0) or Firecapture v2.5 beta, frames are only captured if it's within an ROI. That ROI can even be anything, even if it's just slightly less than full size.

It does work correctly fine in Firecapture v2.4 in the same environment.

I'm running:

Macbook pro retina (2015) / OSX El Capitan 10.11.6

VMWare Fusion 8.5.6

Windows 7

USB 3 drivers required by VMWare

ZWO Windows drivers v2.0.1.3

Any ideas?

Sam@ZWO

can you try native app such like this one

http://blog.gulinux.net/en/planetary-imager

seems this problem related to vmware

ckhorne

Sam wrote:
can you try native app such like this one

http://blog.gulinux.net/en/planetary-imager

seems this problem related to vmware

It does work fine with planetary-imager under OSX.

However, note that it also works fine with Firecapture v2.4 (just not v2.5) under vmware/windows 7.

I saw somewhere that a firmware flash may be needed for mac or vmware - could this be the case here?

Sam@ZWO

ckhorne wrote:
Sam wrote:can you try native app such like this one

http://blog.gulinux.net/en/planetary-imager

seems this problem related to vmware

It does work fine with planetary-imager under OSX.

However, note that it also works fine with Firecapture v2.4 (just not v2.5) under vmware/windows 7.

I saw somewhere that a firmware flash may be needed for mac or vmware - could this be the case here?

no, there is no firmware update for our USB3.0 cameras

how about Sharpcap?

ckhorne

Sam wrote:
no, there is no firmware update for our USB3.0 cameras

how about Sharpcap?

Sharpcap has the same problem - it can't pull down frames unless I'm using an ROI. PHD2 also has the same issue, even when using the camera via ASCOM.

It may be a vmware issue, but I'm not sure why it'd be working in Firecapture 2.4...

Sam@ZWO

I think maybe the max resolution under FC2.4 is different

VMware may have problem with very strange max resolution

you can use 1920*1080 which should be very close to the full resolution