SharpCap Forums

Hi, Robin, further to the above discussions, I've tried to use the Live Stacking approach tonight, and whilst it is an improvement, it just shows up that the PHD interface state machine isn't sufficiently clever: I run 2 instances, controlling 2 cameras; I set one of these to dither, say every 180 s...

Yes, clever, but still not "frame oriented": as has been raised before on these forums, if you're running longer exposures, it's frustrating to have to wait one or two subframes to hope that the dither has finished, and then be able to get another usable frame, plus annoying to have to hav...

Robin, not sure if this has been requested before, but I'd like to suggest a "Flip Type" template option in the file names section of settings. Since SharpCap saves frames pre-processed by flipping, it would be very handy to be able to indicate this in the filename, otherwise it's not easi...

Don, you seem to be missing the point that SkySafari isn’t a Celestron product - it’s from Simulation Curriculum... Celestron licence a simple version of this for “plug & play” users. The reason for the warning to use either hand control OR SkySafari is because only one of them can control the s...

This has been mentioned in passing, Robin, but I'll start a thread here as a reminder. It would be nice, IMHO, to have all frames saved to disc with native sensor orientation, and only have the flip settings apply to screen display. This would be applied to all frame types; light, dark, flat. I appr...

Sorry to chime in, but some thoughts that might help... Hi Robin, Thanks for fast reply! Yes a weird issue. After your testing it sounds like a unique case limited to my setup, so thanks for digging deeper into it! The camera can be managed remotely via HTTP GET and I control it with powershell on w...

Hope you can read it ok? I find that things aren't reliable if I connect a camera to the Renesas controller - things like timeouts downloading frames, random hangs...

Carl

Really glad to hear that we’ve got you up & running, Bill Guys, I would strongly recommend that disabling power saving should be the first step, not even in debugging, but in normal setup - as it doesn’t produce just a single symptom, but a host of undesirable behaviours that are hard to explain...

Robin, Bill,
this rescan can readily be caused by Windows default power management strategy for USB hubs, hence my previous recommendation to disable this “feature” - I, too, wondered why things were repeatedly coming & going, when I obviously hadn’t changed anything...

Cheers,
Carl

Bill, this sounds like USB chipset compatibility issues, to me - I’ve had this battle - particularly as you note you have only 1 USB3 port, but several USB2s: older chipsets tend to be not very good combined with new USB3 cameras - I’ve found that only the Intel chipset on my motherboard is reliable...