As described in a separate topic, which I have now annotated as closed, I suffered from repeated system hanging when playing back the only flow in a project. This generated multiple copies of the flow. I ultimately attributed the problem to system memory leaks, which I solved (apparently) by rebooting my system. However there was collateral damage: the project containing my flow disappeared, and only the flow file remains.
I intend to make use of the capabilities of the project environment at a later stage of the development of the score. How do I re-establish the flow in a project?
I’m not sure what this means. Flows don’t exist in files on their own; they are always contained in project files. Are you perhaps saying that layouts disappeared from your project file? (RIght-hand panel in Setup mode.) Or something else?
I have backup project instances resulting from multiple Dorico freezes, which I infer were caused by depletion of system dynamic memory before I rebooted. I do not pretend to understand how the linkages between projects and their flows work, but the fact that there is no version of the project outside the backup area worries me that linkages may be fragile without due caution. I can still edit the orphan flow file (which I renamed because I was confused by all the crash survivor file names and wanted to simplify down to one file to work on), but I am not sure whether those edits have a promising future. Your question suggests to me that the flow file contains a link to something in the saved project area, but I cannot see my way at that level.
Currently, many of the things you say don’t really fit with how Dorico works.
If you want help, to discover what happened, how to avoid it, and how to fix whatever problem there might be, you’ll need to upload this “flow without a project” file.
Then try this one. I opened up Dorico again, several hours after exiting from another editing session with my “orphan” flow, and suddenly there was a single project with the correct name in the main Dorico menu. I opened it, looked at the flow that came up, and there were all my latest edits since the system hang-up. This was easily verified in part, since one of the post-crash edits was the only change to the list of instruments since I created the score. Maybe that triggered something internally… eventually…
Otherwise I can only assume that Windows has some really weird quirks that manifest when it has been starved of dynamic memory somehow. I will admit to hating to close a variety of simultaneously running applications, simply to avoid losing memory of where I was up to, and the odd update that I might have been interrupted doing without saving.
I can no longer claim to have a problem with current symptoms, so I think this issue can close for me. Is the score still of interest to Dorico staff?
I’m sure the team would like to see your diagnostics, in order to understand what has been happening.
Do Help>Create Diagnostic Report and upload the zip file that appears on your desktop.
The only other zip file visible now is too large to upload, according to this site. I may get better results if I reboot my system, or maybe not, suggestions welcome.
The above file at least has the correct date/time in my Australian time zone. My last exit from Dorico, at that date/time, advised that a crash file had been generated, and I selected the option to send it. I’m sure that I did that after the previous hang-up; I hope it got to the destination this time.
The project now shows up in the Dorico menu without my having to go looking for it explicitly in the backups, but apparently that is where the latest modification now lives. Yes, that confuses me about what I am seeing.
There is also a .json file of appropriately recent origin, but resistant to being uploaded.