oaCapture 1.5 on El Capitan crashes when selecting a camera

[Fivel]

Hello to all.

I am running the app on my iMac with 32 GB of RAM and a 1TB SSD.

When I open the app and select the ZWOasi1600MC-cooled, the app crashes (closes).

I finally got it to stay open, but it is not stable. It crashed 3 times in a row before it would stay open.

I will need to check during the day to see if the app is getting a feed from the camera.

The camera works fine with other Mac capture apps.

Has this version of the app been tested with El Capitan?

Please Advise

 

Fivel

 

[JamesF]

It should work, but I can't test with every camera so perhaps there's some ASI1600-specific issue that I'm not aware of.  If you're able to start the application from a terminal window it would be useful to know if there's any output to the terminal window that might shed some light on the cause of the crash.

James

[Fivel]

Hi James, thank you for your reply.

I am not familiar with how to open the app in the console (Mac is called Terminal).

Are you knowledgeable of how to do this on a Mac? If so, please provide me with the command line.

I tried to find a log, in the files structure, but none was created.

As additional info, I previously used oaCapture with my planetary camera, the ZWOasi185mc (not cooled).

It worked well on a Windows 10 laptop. I had no issues with that camera.

I hope we can get this issue solved.

Fivel

 

[JamesF]

Ok, if you have installed oaCapture in the applications folder then in the terminal window you need to enter:

/Applications/oaCapture.app/Contents/MacOS/oaCapture

and hit return.  Hopefully that should work.

James

[Fivel]

Hi James.

oaCApture opens properly from the Terminal. Thank you for that advice.

I hope today to see if that keeps the app from crashing.

Fivel

[Fivel]

Hello again James.

It took quite a while before I could accomplish this but here is the result.

I could open oaCapture vai the terminal but the same problem exists.

I could select the ZWOasi185mc, but nit the 1600mc-cooled. It still causes a crash.

Here is the info that was in the Terminal app before and after the crash. Not much help there.

Both cameras are USB 3.0 and connected via the same USB 3.0 powered hub to my Mac Mini.

------------------------------------------------------------------------------------------

FredsMacMini:~ User$ /Applications/oaCapture.app/Contents/MacOS/oaCapture

libpng warning: iCCP: known incorrect sRGB profile

oaZWASI2InitCamera: control AutoExpMaxGain is not supported

oaZWASI2InitCamera: control AutoExpTargetBrightness is not supported

oaZWASI2InitCamera: control HardwareBin is not supported

Segmentation fault: 11

FredsMacMini:~ User$ 

-------------------------------------------------------------------------------------------

All I could see is the Segmentation fault: 11

So waht are your thoughts?

 

Fivel

 

[Fivel]

Well, some good news.

I installed the older version (1.4.1) and it works well with both cameras.

The only thing I need to check again is that the reticule doesn't appear to work.

No matter which type I choose, nothing shows up on the display.

Maybe the next decent evening (who knows when that will be?) it may surprise me and start to show up.

At least now I can avail myself of all of oaCapture's nice features and options.

 

Fivel

[JamesF]

I don't have a 1600 camera, but I believe this should be fixed in the next release.  If I can just find enough time to finish off testing that will be very soon.

James

[Fivel]

James, thank you for your hard work and great support.

I look forward to the next version.

Do you know what caused that fault with one of the two USB 3.0 cameras I have, and not the other?

I will be re arranging the connectivity between the cameras and my Mac Mini. I hope it will improve some minor data handling issues.

Fivel

[JamesF]

4 hours ago, Fivel said:

Do you know what caused that fault with one of the two USB 3.0 cameras I have, and not the other?

Just a coding error that meant I mishandled the frame size, I think.

James