Everything what you will need for ASI camera control, imaging, guiding and processing at one place! Windows, MAC and Linux USB drivers, ASCOM drivers, latest firmware and camera control and processing software for all ZWO devices.
- Planets can be dissapointing Chris. The seeing has to be very good to get great shots. The higher the planet the better as it has less atmosphere to go through and avoiding shooting near buildings as they give off heat which the cam will pick up.
- OaCapture is a planetary imaging application for Linux and MacOS. It currently supports cameras such as the ZWO ASI series, many of the USB Imaging. C++ with support libraries in C so they can potentially be shared by other software. Oacapture was used for capturing data from an ASI120MC for this image of Jupiter.
Width: 28 mm Diameter: 62 mm Sensor Type: Color CMOS - 12 bit Sensor size: 4.8 mm x 3.6 mm Number of pixels: 1280 x 960 pixels Pixel size: 3.75 μm x 3.75 μm Sensor: CMOS AR0130CS Color Number of frames per second: Up to 254 frames per second in 320 x 240 pixel resolution Autoguiding: YES Connection: USB 3.0 Cooling: NO (passive cooling) IR Filter: YES Compatibility: Prism 8, FireCapture Weight: 100 g Flow: 31.75 mm and 50.8 mm (1.25 'and 2') and T2 (M42 x 0.75) USB cable: Length 2 m CD Rom: Includes drivers, acquisition software and instructions for use. Minimum exposure time: 0.000064 seconds Maximum exposure time: 16 minutes Computers: Windows XP, Vista, 7 and 8 (32bits / 64bits) Quantum yield: 68% Model: ZWO color camera ASI120MC-S USB3.0.
I run El Capitan on an old Macbook Air USB2 with oaCapture and an ASI120MM or ASI174MM. It works very well. The only bug I have encountered is the saving of the 'last' profile which I have reported to James so he is aware. I ran it for 5 hours solid on Mercury transit day without any other issues. Did you see the video I attached? I get a jumpy, broken up pixelated image. But it's intermittent.
Zwo Asi120mc-s For Mac
Before, for about 5 minutes I managed to get it to stableise so I know the camera (which is brand new) is ok. It seems to be the software!
Have been looking forward to this camera arriving and am really disappointed that I can't get it working. Have wasted so much time on it already! What model MacBook? Retina or non-retina? I have same issues using USB2 cameras on retina (USB3) MacBook Pro. If I switch to my older non-retina USB2 MacBook Pro, everything works perfectly.
S'a known issue with Darwin based operating systems and USB2 hardware in USB3 ports, caused by libusb being a bit fritzy. You can try installing libusb-dev via MacPorts or similar. But no guaranteed fix. In the backend there'll be a flood of isochronous errors going on. Ultimately s'an OSX / Darwin issue which means if it's a USB3 MacBook, buy USB3 cameras. That's the only guaranteed fix. Issue has been the scourge of my life for years (I do a lot of Kinect-based realtime mocap work, with several original xbox360 kinects which all behave the same as you're seeing, alongside my Opticstars, which pass thru to a Windows VM).
And is the sole reason I keep multiple MacBooks in my possession. Cei ensight 10.2.3a gold free download java profiler 14 for mac pro. What model MacBook?
Retina or non-retina? I have same issues using USB2 cameras on retina (USB3) MacBook Pro. If I switch to my older non-retina USB2 MacBook Pro, everything works perfectly. S'a known issue with Darwin based operating systems and USB2 hardware in USB3 ports, caused by libusb being a bit fritzy. You can try installing libusb-dev via MacPorts or similar. But no guaranteed fix. In the backend there'll be a flood of isochronous errors going on.
Ultimately s'an OSX / Darwin issue which means if it's a USB3 MacBook, buy USB3 cameras. That's the only guaranteed fix.
Issue has been the scourge of my life for years (I do a lot of Kinect-based realtime mocap work, with several original xbox360 kinects which all behave the same as you're seeing, alongside my Opticstars, which pass thru to a Windows VM). And is the sole reason I keep multiple MacBooks in my possession. It's a 2012 MacBook Pro. I bought the USB 2 camera because I was aware of my MacBook having USB 2 ports. There is no problem with incompatability as far as I can see. Just glitchy software or glitchy camera!
Could be that I was unlucky enough to get a bad cable in the box. I'm using oaCapture 1.0 on an early 2015 MacBook Pro 13' retina display running MacOS Sierra 10.12.4 with a ZWO ASI120MC. This is a USB 2 ASI camera on a USB 3 MacBook.
It appears to be working very well. I've found only 2 bugs. There is an interface display bug that causes some default values in settings panels not to display properly on startup. They display properly when toggled. The most important setting is in Settings / Camera / USB / High Speed which appears to be not enabled but really is.
If it is set to 'High Speed' frames are corrupted and communications to the camera can lock up. The workaround is to click on on the 'High Speed' check box a couple of times to get the check box displaying correctly and turn off the default High Speed setting. The second problem is a memory leak. OsCapture will use up large amounts of application memory - eventually all of it freezing up your Mac's applications if you leave the camera Preview running. Turning off Preview either stops the leak or slows it down considerably.
The workaround is to not run preview when not needed and keep an eye on osCapture's application memory usage and restart it when it gets too large. This is a wonderful app to have on the Mac and I'm looking forward to making use of it!;rob Edited April 2, 2017 by rcpettengill. I'm afraid I have the same problem. I'm dual booting 10.11.6 and windows 7 on a USB2 mac (2009 macbook pro). My new ASI120mm works fine in firecapture on windows. However oacapture fails to provide more than 1 f/s of broken-up looking images on preview. The camera controls also seem sort of weirdly unresponsive - I assume checkboxes for things like gain are setting it to automatic but after changing any of the settings, the apply button is grayed out so I'm not sure if its making any difference.
Setting USB traffic to lower settings helped maintain framerates in firecap but seems to have no effect in oacapture. Setting a lower resolution didnt help either. Weirdly, I can use the camera to autoguide with PhD on mac with no problems (on highest frame rate setting which is 0.01).
Is it possible there are variations between camera examples that determine how well oacapture can work with them? I dont mind working in windows to do image capture, but I'd like to do it all on a mac if possible. And oacapture looks like a great program if I could get it working for me. I think I may sell this camera and get one of the usb3 versions which apparently work much better on mac.