During 2008, several threads discussed the "writing final file" hang, some involving SD, but mostly HD disc probjects:
http://forums.pinnaclesys.com/forums/thread/211012.aspx
http://forums.pinnaclesys.com/forums/thread/268231.aspx
http://forums.pinnaclesys.com/forums/thread/293050.aspx
Here is one which was very explicity about a project and menu structure that resulted in a nightmare:
http://forums.pinnaclesys.com/forums/permalink/263753/261371/ShowThread.aspx#261371
The user attempted multiple changes and finally succeeded. Alas, it's not clear precisely what action untangled the knot.
50 stills and 60 (?) chapters, per se, are not much of a strain. jjn's test might be more realistic if the stills also had lots of PAZ, animations, and overlays. The stress also rises if there are hundreds of AVCHD clips and maybe dozens of transitions or title overlays, The minimum number of chapters, or the chapter structure, are another test imension.
The problem is not that the "writing final file" hang always occurs, but that it does occasionally. Sometimes I've successfully created disc images, on a 4-hour timeline with 90 chapters and all kinds of content, but then collide with the WFF problem after I later introduce additional content at an early or mid-point in the timeline.
Once the problem appears, the user must either:
- Quit the "Make Movie," re-start the program, let the auto-save function reload the aborted project, unclick the "always re-code entire movie," resume the BD image creation and (with luck) see Studio leap immediately to the final file righting and (with more luck) see it complete properly.
- Delete the AUX files and try again.
- Simplify the chapters or reduce the number of chapter points significantly.
- Shorten the project, or
- Pre-edit and export complex sequences as single intermediate files, usually in HDV, and then import the edited files into a final timeline and set up the chapter points and menus.
#5 is close to a cure-all. Re-creation of the menus and chapter is less trouble than it seems, especially since the final time-line stability will be higher and more preview friendly. The only drawback is some loss in IQ, mitigated by doing everying in the highest bitrate consisten with disc space. It also helps if one takes this measure with only the most render-demanding segments of the timeline, just enough to lower the final rendering threshhold.
Some people solve the problem by removing root buttons or by shifting the virtual memory to the defaul "system managed" mode, from whatever custom mode they may have picked.
I'm curious whether the problem might vanish if one has an i7 CPU or 1TB graphics card, but perhaps not.