DCP-o-matic freezing at every step

[Joao.Gri]

First and foremost, thank you! This is an amazing software.

Since about three versions back, DCP-o-matic started freezing at every step, from opening a project to adding subtitles. It is a behavior that did not happen in the past, but now it does and makes all the process painstakingly long and infuriating.

Would like to know if someone is experiencing the same or if it is just here. I've tried the newer versions on two desktops and one Dell Notebook. The current configuration is: Core i7 4790, 24GB RAM, Geforce 1070 8GB. Working with files on 2 separate disks.

Thanks!

[carl]

Hi,

Do you remember the last version that worked? Does it happen with all your projects?

[Joao.Gri]

Yes it is happening with all projects. The problem is source file agnostic aswell. Happens with JPEG200 from DaVinci (Kakadu), MXF files encoded on DNxHD, WAV, srt, you name it.

Just to make it clear, DCP-o-matic unfreezes, but it stays put for almost a minute at a time. The only thing I haven't done, yet, for lack of opportunity, is formatting all our PCs.

Thanks!

[carl]

That's odd. Is it possible to record a short screencast so that I can see what's happening?

Is this with 2.12.something? Do you know a version when it didn't happen?

[Joao.Gri]

I'll record my screen, no problem.

I do not remember correctly when it started, possibly on 2.12.11 or on the prior update.

[Joao.Gri]

Maybe, just maybe, it coincided with the latest Windows Update. Cant'really tell.

[carl]

OK. If it was one of the later 2.12.x versions I'd be surprised if it was DCP-o-matic's fault as the changes there have been very small.

If you could send that screencast it would be help. Thanks!

[scozz76]

I had this problem with 2.13.53 (win10 64)
Went back to 2.12.11 and it's been fine.
I haven't tested 2.13.57 yet.

*UPDATE+
2.13.57 crashes when "Show graph of audio levels" is selected (repeatable). Did not do any further testing.
Rolled back to 2.12.11 (without uninstalling) and it's fine.

[Joao.Gri]

I think I managed to find out what was creating this behavior. Apparently it was not DCP-o-matic fault, but Windows Defender's. What I did was to add an exception to Windows Defender's malware monitoring tool. After that the behavior stopped.

I made a screen capture of the process, I'll post it soon enough.

Thanks!

[Joao.Gri]

The video link:

https://youtu.be/4AUIofzTD98