Can't add content since 2.18.19

[carl]

Ah great! I'd be interested to hear what went wrong...

[jolavista]

I'm embarrassed, but I just hadn't created a new project and was waiting for the buttons to become active because I thought the verification process was still ongoing.

[carl]

Ah I see, so you're talking about the macOS verification of the download!

Don't be embarassed, you are definitely not the first one to be tripped up by the "File -> New" thing. Somewhere on the list are some ideas to stop that step being necessary...

[IoannisSyrogiannis]

An alternative would have been a pop-up that explains how that goes the first time the application starts, and until one checks "I understand how to start with making a DCP and I don't want this to show on every start". Something similar to that "the subtitle's positioning has changed".

[carl]

True. I also wonder if we can postpone the decision about where the project should be until "make dcp" or "save".

[Carsten]

Maybe we just need a 'New' button in a more prominent position. Everyone seems to recognize the 'Add file' button immediately. Another option based on that would be to create a new project/come up with the new project dialog automatically when someone adds a file for the first time. I admit, that sequence would probably also be a bit confusing at first, but it would a least force the user to act.

I have to say though - this really is just a problem for first time users. I never heard about irritations once a user went through this the first time. And I don't think it keeps these people from getting started with DCP creation. Maybe we just need a slightly better hint than the 'File' drop down menu offers.

Admittedly, even 'Microsoft software' (shudder) opens a new empty document upon start (well, most of the time).

[carl]

The idea I had was to open with an empty document, and keep logs in a temporary location (and don't save anything else). Then when they make dcp, force them to save so that we know where to create the DCP.

It's a bit tied up with the old classic question of how to stop people sending the whole DoM project folder as the "DCP". You could argue that all project metadata/logs should be kept in some internal store, and the only thing the user specifies is where the DCP is written. This would make it harder to move projects between machines, but maybe most people don't do that.

[Carsten]

I think the real problem actually is that many beginners believe that a DCP is just another video file, and thus think that it involves nothing more than 'Here's my source, start conversion right away!'.

They do not think that a project directory, logs, etc. are necessary for what they are trying to achieve. If we separate project and DCP directory, it will not make this any better - they may still try to transfer the project directory to a DCP server - but then without even the DCP

A similar issue could be that people, after having added their source, they may not find the 'Make DCP' in Jobs menu. It's just that, THEN, after having added content, they will probably start looking for something that get's something going.

Admittedly, after choosing 'Make DCP', one could offer an option where to store the DCP. That is probably easier for users to follow. Especially when people use e.g. laptops with a a rather small integrated SSD (like MacBooks AIrs), aiming to store the DCP on an external drive. On these machines, the default project location 'Documents' would very often lead to filling the drive. Yes, DCP-o-matic catches it if the DCP might grow to large, but still...

[carl]

They do not think that a project directory, logs, etc. are necessary for what they are trying to achieve. If we separate project and DCP directory, it will not make this any better - they may still try to transfer the project directory to a DCP server - but then without even the DCP

True, though I imagined the project data being totally hidden so that the only visible output is the DCP.

[Carsten]

Not sure wether I would actually change it that much. I mean, beginners ALWAYS need to learn something, and this is basic GUI functionality.

I would find it more frustrating if established methods would change for long time users, who have no problem with the existing scheme at all.
That said - an option to create/save the DCP at a desired target directory OR within the project directory right when/after choosing 'Make DCP' would certainly help (default to project directory). This would also facilitate hash checking on the distribution drive right after the DCP has been created. Which is safer than hash-checking the created DCP on a local drive, and then copying it to an external drive without hash checks through finder/explorer methods.
It would also be fairly easy to understand for all users and wouldn't break any expectations of experienced users.