Hello,
Is it possible to use the test camera with the option to select a specific ROI that I need for testing?
Regards,
Javier
Using a specific ROI with the test camera
Forum rules
If you have a problem or question, please check the FAQ to see if it already has an answer : https://www.sharpcap.co.uk/sharpcap-faqs
If you have a problem or question, please check the FAQ to see if it already has an answer : https://www.sharpcap.co.uk/sharpcap-faqs
-
javierdeelias
- Posts: 11
- Joined: Fri Sep 29, 2023 4:16 pm
-
javierdeelias
- Posts: 11
- Joined: Fri Sep 29, 2023 4:16 pm
Re: Using a specific ROI with the test camera
Hello,
To be more specific, I mean I am trying to test ROI capture through SharpCap scripting before using it with a real camera.
Setup:
- SharpCap running locally
- Camera: SharpCap test/simulator camera
- Output Format: FITS files (*.fits)
- Colour Space: MONO16
- Full frame Capture Area: 2328x1760
With full frame capture, everything works correctly. For example, with:
Capture Area = 2328x1760
Exposure = 100 ms
Output Format = FITS files (*.fits)
SharpCap produces FITS files normally.
However, when I reduce the Capture Area, SharpCap stops producing frames. I tested several ROI sizes:
262x421
320x240
640x480
800x600
In all these cases, the capture starts and finishes without an error, but no frames are saved.
I also noticed that setting Pan and Tilt appears to return success from the scripting/API side, but the values remain at 0 when I read the controls back.
So the observed behavior is:
Full frame: frames saved correctly
Reduced Capture Area: 0 frames saved
Pan/Tilt: accepted but not actually changed
My question: is ROI capture expected to work with the SharpCap test/simulator cameras, or is this a limitation of the test camera?
I am trying to validate ROI positioning before a real astronomical occultation capture, so I need to know whether the simulator can be used for this purpose.
Thanks.
To be more specific, I mean I am trying to test ROI capture through SharpCap scripting before using it with a real camera.
Setup:
- SharpCap running locally
- Camera: SharpCap test/simulator camera
- Output Format: FITS files (*.fits)
- Colour Space: MONO16
- Full frame Capture Area: 2328x1760
With full frame capture, everything works correctly. For example, with:
Capture Area = 2328x1760
Exposure = 100 ms
Output Format = FITS files (*.fits)
SharpCap produces FITS files normally.
However, when I reduce the Capture Area, SharpCap stops producing frames. I tested several ROI sizes:
262x421
320x240
640x480
800x600
In all these cases, the capture starts and finishes without an error, but no frames are saved.
I also noticed that setting Pan and Tilt appears to return success from the scripting/API side, but the values remain at 0 when I read the controls back.
So the observed behavior is:
Full frame: frames saved correctly
Reduced Capture Area: 0 frames saved
Pan/Tilt: accepted but not actually changed
My question: is ROI capture expected to work with the SharpCap test/simulator cameras, or is this a limitation of the test camera?
I am trying to validate ROI positioning before a real astronomical occultation capture, so I need to know whether the simulator can be used for this purpose.
Thanks.
- admin
- Site Admin
- Posts: 17539
- Joined: Sat Feb 11, 2017 3:52 pm
- Location: Vale of the White Horse, UK
- Contact:
Re: Using a specific ROI with the test camera
Hi,
from your point of view, the easiest thing to do is to switch from 'Test Camera 1' which doesn't support ROI to 'Test Camera 2' which does, and everything should work as expected.
I think the issue with 'Test Camera 1' is that although it doesn't support ROI, it seems to be claiming that the 'Custom ROI' option is available as the 'Select ROI' button shows up in the UI. That probably also allows it to accept custom ROI values via scripting, which then don't work properly. I will look into fixing that on my side.
cheers,
Robin
from your point of view, the easiest thing to do is to switch from 'Test Camera 1' which doesn't support ROI to 'Test Camera 2' which does, and everything should work as expected.
I think the issue with 'Test Camera 1' is that although it doesn't support ROI, it seems to be claiming that the 'Custom ROI' option is available as the 'Select ROI' button shows up in the UI. That probably also allows it to accept custom ROI values via scripting, which then don't work properly. I will look into fixing that on my side.
cheers,
Robin
-
javierdeelias
- Posts: 11
- Joined: Fri Sep 29, 2023 4:16 pm
Re: Using a specific ROI with the test camera
Hi Robi,
Many thanks for your help.
I switched to **Test Camera 2** and it works fine with the custom ROI. That solves the issue for my tests.
Regards,
Javier
Many thanks for your help.
I switched to **Test Camera 2** and it works fine with the custom ROI. That solves the issue for my tests.
Regards,
Javier