So I get this error:
08:46:36 WARN Image size/colour depth changed. Resetting stack.
08:46:36 NOTE Processor Expected {Width=6224, Height=4168}, 16 bpp, 3 planes
08:46:36 NOTE Expected Frame Info : (6224x4168, RGB, BitDepth=16, ColorPlanes=3, EffectiveBitDepth=16, BytesPerPixel=6, Binning=1x1
08:46:36 NOTE Current Frame Info : (6224x4168, RGB, BitDepth=16, ColorPlanes=3, EffectiveBitDepth=16, BytesPerPixel=6, Binning=1x1
08:46:36 NOTE Clearing stack
However, that is not correct. All the images are the same size and gray 16 bit.
What is going on? A bug?
Thanks!
- Chris
Live stack resets
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
Please also read about Troubleshooting USB Issues before posting.
*** Please do not post license keys - please report any problems with licensing to 'admin' by private message ***
Please include the following details in any bug report:
* Version of SharpCap
* Camera and other hardware being user
* Operating system version
* Contents of the SharpCap log after the problem has occurred.
[If SharpCap crashes, please send the bug report when prompted instead of including the log]
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
Please also read about Troubleshooting USB Issues before posting.
*** Please do not post license keys - please report any problems with licensing to 'admin' by private message ***
Please include the following details in any bug report:
* Version of SharpCap
* Camera and other hardware being user
* Operating system version
* Contents of the SharpCap log after the problem has occurred.
[If SharpCap crashes, please send the bug report when prompted instead of including the log]
-
admin
- Site Admin
- Posts: 17544
- Joined: Sat Feb 11, 2017 3:52 pm
- Location: Vale of the White Horse, UK
- Contact:
Re: Live stack resets
Hi Chris,
certainly doesn't look right - were you using a real camera at that point or loading previously saved frames via the virtual folder monitor camera? I can see a possible reason why that might happen incorrectly for the folder monitor possibility, but less obvious why it would happen for a real camera).
I think I can just remove the check logic check that might be wrong anyway, I can't quite see how it can do anything helpful (although maybe in a week I will be fixing a bug caused by me removing a check that actually *did* do something useful)
cheers,
Robin
certainly doesn't look right - were you using a real camera at that point or loading previously saved frames via the virtual folder monitor camera? I can see a possible reason why that might happen incorrectly for the folder monitor possibility, but less obvious why it would happen for a real camera).
I think I can just remove the check logic check that might be wrong anyway, I can't quite see how it can do anything helpful (although maybe in a week I will be fixing a bug caused by me removing a check that actually *did* do something useful)
cheers,
Robin
Re: Live stack resets
Hi Robin,
I was indeed using an earlier session through the folder option. I have never had any problems with it, until now.
Cheers,
Chris
I was indeed using an earlier session through the folder option. I have never had any problems with it, until now.
Cheers,
Chris
-
admin
- Site Admin
- Posts: 17544
- Joined: Sat Feb 11, 2017 3:52 pm
- Location: Vale of the White Horse, UK
- Contact:
Re: Live stack resets
Hi Chris,
phew, at leat that makes some sense then - I suspect that some of the old frames had slightly different metadata to the others (things like camera name or pixel size, which really shouldn't matter in this case). SharpCap was spotting the difference and deciding that things were not compatible and a reset was required. This would be more likely if the input frames came from 2 different sessions or had been captured to different formats or similar.
Anyway, I have removed the check now and the next update version should be fine I hope!
cheers,
Robin
phew, at leat that makes some sense then - I suspect that some of the old frames had slightly different metadata to the others (things like camera name or pixel size, which really shouldn't matter in this case). SharpCap was spotting the difference and deciding that things were not compatible and a reset was required. This would be more likely if the input frames came from 2 different sessions or had been captured to different formats or similar.
Anyway, I have removed the check now and the next update version should be fine I hope!
cheers,
Robin