Page 1 of 1

Stalls at Setting Up

Posted: Fri Sep 10, 2021 7:37 pm
by Peter Mork
DCP-o-matic 2, Windows 10.
Was running four processes, all okay, then all quit responding.
Closed all four. Tried to restart DCP2, but it got stuck on Setting Up.
Rebooted computer, tried to run DCP, same thing - stalled.
Uninstalled DCP2, got a new .exe from the website, re-installed. still stalls.
There seems to be a dialog box behind the Setting Up box, but I can't unhide it. Can only quit via task manager.
What gives?
Thanks, PM

Re: Stalls at Setting Up

Posted: Fri Sep 10, 2021 8:29 pm
by carl
That's strange. I thought I'd fixed the problem with error dialogs hiding behind the splash screen, but it seems I only did it for the test version. I'll make a new 2.14.x release with the fix and hopefully that will give us some clues.

Re: Stalls at Setting Up

Posted: Sat Sep 11, 2021 12:21 am
by Peter Mork
Okay, let me know and I'll give it a try.

Re: Stalls at Setting Up

Posted: Sat Sep 11, 2021 7:09 am
by carl
Here's the updated version if you could try it and let us know what happens:

https://dcpomatic.com/rc-download

Re: Stalls at Setting Up

Posted: Sat Sep 11, 2021 12:49 pm
by Carsten
Shouldn't trashing prefs solve these issues?

The way I understand the programming/binary structure, uninstalling and reinstalling typically doesn't solve issues. Trashing prefs does.

Re: Stalls at Setting Up

Posted: Sat Sep 11, 2021 9:13 pm
by carl
Yes, it probably would - but it would be nice to see the error before the trashing happens!

Re: Stalls at Setting Up

Posted: Sun Sep 12, 2021 12:36 am
by Carsten
Ah, nooo...

Re: Stalls at Setting Up

Posted: Sun Sep 12, 2021 5:18 pm
by Peter Mork
Here's what the dialog said:

The existing configuration failed to load. Default values will be used instead. These may take a short time to create.

Re: Stalls at Setting Up

Posted: Sun Sep 12, 2021 5:20 pm
by Peter Mork
As soon as I closed the dialog, the program did load.

Re: Stalls at Setting Up

Posted: Fri Sep 17, 2021 11:12 pm
by Carsten
That is typical for either corrupted, or incompatible pref files. I see that message often, because I often switch back and forth between new and old versions for testing.