Login  Sign up

Monitor mode adding 10000 empty monitors

My monitor mode add somethimes empty monitors not 1 or 2 but 1000 of them .... it take 30 minutes to delete them because i must do it 1 by 1, i can't select multiple monitors. I cant do this anymore.

Why is this happening?

(171 KB)

No idea. Havnt seen that before.  Name is missing as well - it shouldnt be possible to create a monitor without a name.

Does this happen when you press the New Monitor heart button to create a new monitor, fill out all the details and then click save?  Is that when they are all created?

You can delete them all from C:\Users\<your user>\AppData\Roaming\Jaksta Media Recorder 7\Monitors

Please provide debug log following these instructions and perform the actions that cause this: https://support.jaksta.com/discussions/topics/6000009063

This happened to me also and it was a nightmare.

Can you provide logs so we can see whats happening as per the above?  Deleting them is pretty simple. Just delete all the files.

It is simple but time consuming when there are THOUSANDS of "extra" monitors are created every day. please add bulk deletion to this program, or figure out what is making thgese phantom monitors start.

Can you provide logs as per above?   We have never received logs showing this issue nor can we reproduce it.  

Would appreciate someone providing logs as per my first post showing it happening so we can see what the issue is and fix it.

Bull deleting monitors can be achieved at the moment by remove files from C:\Users\<your user>\AppData\Roaming\Jaksta Media Recorder 7\Monitors.

Any one able to help by providing logs or other details such as an export of their monitors so we can get to the bottom of this?

I have experienced this behavior several times over several versions of the software.  I export out my monitors to a .dat file so I can remove the software with all settings, reinstall and reimport the monitors.  Quickest way to get back to good.

If/when it happens again, I will def forward logs to this thread.


It occurred for me again, I am letting the debug run for a bit and I will email them to support.


Login or Signup to post a comment