Page 1 of 1

Logfile and interruptions

Posted: Wed Dec 24, 2025 12:27 pm
by Seginus
Hi together

I have two questions regarding the SharpCap Logfile stored under c:\Users\<USER>\AppData\Local\SharpCap\logs\ :

1) Is there a way to add the date in the log? Currently my logfile shows only the time and I run SharpCap permanently to operate an Allsky Cam. Sometimes I get interruptions in the recording and it would be helpful to know on which day that was.

2) For one of such an interruption/error, my logfile shows the following infomation:

Info 03:14:16.869471 #1 StopCapture event received in UI thread
in async void SharpCap.ViewModels.SharpCapViewModel.appModel_OnCaptureEvent(object sender, CaptureEventArgs e)

Is there a way to find out, what the real cause was that SharpCap stopped capturing? Actually it stopped in the middle of the night and did not finish capturing all the frames (set under Capture > Start Capture > Number of Frames). In the next night, everything was back to normal.

I am using the version v4.1.14013 64bit.

Cheers and merry christmas to all!
Stefan

Re: Logfile and interruptions

Posted: Thu Dec 25, 2025 5:19 pm
by admin
Hi Stefan,

unfortunately the date is only recorded in the log at the start - from then on, it just records the time for each event. In general, this makes it easier to read the log (less stuff to ignore at the start of each line), but awkward in your situation.

If you have set up the file naming in SharpCap to include the date in the file name then you will be able to work out the date by finding references to the output file names in the log - usually SharpCap records writing a capture settings file and also the notification that shows when the capture is complete. Both of those contain the full path and file name, so if either contains the date you can track the information you need.

As to why the capture is stopping - any useful info will be in the lines of the log preceeding the 'StopCapture event received' line. Often there will be a previous 'Stopping capture' event (which happens at the start of the shutdown of the capture - the 'StopCapture' one is basically after the stop has finished). There may also be a line with something like 'stopping capture because <some reason>', which should give a clearer indication of why the capture has been terminated.

In a more general way, things that could cause it to stop include

* Hitting the frame or time limit specified when starting capture
* Pressing the 'stop capture' button in the toolbar or the equivalent menu item
* Pressing the <ESC> key on the keyboard
* Running out of disc space (or being close to running out - SharpCap tries to stop before the disc space runs out so there is some space to finalize writing any capture files).

cheers,

Robin