Delay in folder monitor

A place to report problems and bugs in SharpCap
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]
Post Reply
MikeB838
Posts: 129
Joined: Sun Jan 28, 2024 5:18 pm

Delay in folder monitor

#1

Post by MikeB838 »

Hi Robin,

I use the Folder Monitor (with Live Stack) very often to rework my captures.

With SC 285 I encounter a new delay of some seconds, when I select a new source.
SC disables live stack, all goes black and it is enabled again.
Is this by will or by accident?

Thanks for looking!

cheers,
Michael
User avatar
admin
Site Admin
Posts: 17544
Joined: Sat Feb 11, 2017 3:52 pm
Location: Vale of the White Horse, UK
Contact:

Re: Delay in folder monitor

#2

Post by admin »

Hi,

there is an extra stage required when you change the source with the folder monitor camera - once the new source is selected, SharpCap needs to reconfigure the camera again as the new image resolution (or bit depth) may be different to the one used previously. That can introduce a second or two of 'thinking' time with things seeming to become disabled while it is happening. It *sounds* as though that is what you are encountering, although not 100% sure.

I should note though that this hasn't been changed recently, so odd if this has only just started happening to you in the very latest version... I certainly can't see any changes between the previous version and 285 that I would expect to cause this...

cheers,

Robin
MikeB838
Posts: 129
Joined: Sun Jan 28, 2024 5:18 pm

Re: Delay in folder monitor

#3

Post by MikeB838 »

Hi Robin,

thanks for your fast answer.
The delay is distracting now and I would have noticed before. If I remember correctly with former versions there was no disabling of the live stack.
Has the check for reconfiguration need be changed lately? All frames are from one camera and have the same setup.
Is it possible to skip the reconfiguration, if it is detected that it is not needed?

BTW: how can I easily test older versions of SC without uninstalling/installing the full setup? Is it possible?

Cheers,
Michael
User avatar
admin
Site Admin
Posts: 17544
Joined: Sat Feb 11, 2017 3:52 pm
Location: Vale of the White Horse, UK
Contact:

Re: Delay in folder monitor

#4

Post by admin »

Hi Michael,

no, nothing has changed recently there, which is why this is a bit odd.

You can do a quick experiment on an older version by installing a 32-bit version of SharpCap for the older version, which can stay installed alongside the 64-bit version that you normally use with the newer version. Of course, with the 32-bit version you are more likely to hit 'out of memory' problems, particularly if you use high resolution images, but it should be good enough for quick tests of this sort of thing.

cheers,

Robin
MikeB838
Posts: 129
Joined: Sun Jan 28, 2024 5:18 pm

Re: Delay in folder monitor

#5

Post by MikeB838 »

Hi Robin,

thanks for the 32-bit tip, I will give it a try!

Cheers
Michael
MikeB838
Posts: 129
Joined: Sun Jan 28, 2024 5:18 pm

Re: Delay in folder monitor

#6

Post by MikeB838 »

Hi Robin,

I checked SC 295 and the delay is history. Thank you very much!

When I select a new source in the folder monitor, I can see only a fast switch (under 1 second) - as it was before :D

Great work, as usual !

Cheers,
Michael
User avatar
admin
Site Admin
Posts: 17544
Joined: Sat Feb 11, 2017 3:52 pm
Location: Vale of the White Horse, UK
Contact:

Re: Delay in folder monitor

#7

Post by admin »

Hi Michael,

glad to hear all well now - still confused about what happened to 13285 - the wrong version number showing in the log and the slowdowns have to be related (too much of a coincidence for both of those to suddenly appear at the same time in a new version and then both be gone together without any obvious causes).

I think I will add a check to the build process to look for the mismatch of version number (easy to spot) to prevent it happening again - whatever the cause might have been.

cheers,

Robin
Post Reply