Some time lost transitioning from PPro2015 from PPro2017.
Everyone knows you don't perform major upgrades in-the-middle-of-a-project.
Well, this is a long project. And PPro2015 was never very stable. My "smooth sailing!" quickly turned into a series of crashes, so I took some time to see how I could possibly stabilize this thing.
(It was not always crashing constantly, the stability had a great deal to do with whatever portion of the project I was working on... but since my last post I hit a rough patch which is no longer a rough patch.)
Updated Quaro 4000 video driver.
Added another 8TB drive to "Audio Preview" cache now giving me 16TB for that cache's volume. PPro now constantly be consuming 10TB of cache since, so that was probably needed.
And... PPro2017.
Let me tell you about PPro2017.
Adobe has issued 4 updates (big and small) since the version of PPro2015 I've been working with.
And while those might have been fine builds, I was unable to migrate the project to them (in an attempt to address stability issues).
I could start a brand-new project in those newer versions, but my Thorium Remix project would not migrate. A memory leak would occur and my 64GB of RAM would be exhausted before I could complete the transition.
This was an issue I reported to Adobe (and other people complained about on the forums too). And it looks like they finally addressed it in PPro2017.
So all these things took place together. New PPro. New driver. More cache.
Do not know what single thing appears to have made my life easier, but at any rate PPro is no longer crashing constantly.
v20161124
This is just me moving forward thru the timeline cleaning it up. 3h58m is where I was at when I triggered this render. So I've advanced 39m since my last update to you.
There's been tiny narritive tweaks in that 39m but mostly it is just me normalizing audio and properly b-roll-ing video sequences.
Rendering Uncompressed
If you care to know how I'm rendering video now... Thorium Remix consists (internally) of about 15 sequences. (Even TR2017-Part-One-NASA was internally 5 sequences.)
They exist on my hard drives as uncompressed quicktime.
The sequences combined are 2.5 TB in size.
And they do also exist in combined form... there's also a single 2.5 TB QuickTime file of uncompressed 1920x1080 8-bit video data.
So that's 5 TB of uncompressed QuickTime... 2.5 in pieces and again 2.5 as a single merged file.
The creation of that merged QuickTime .MOV file was so I could try find a better way of rendering something that can be uploaded to YouTube than PPro WebM.
WebM encoding takes 80 hours... it is more computationally intensive than H.264, and is newer (or complicated) enough that I can NOT use my Quadro 4000 to render it. (I'd need some sort of newer GPU called "Pascal".)
However, a GPU powered H.264 render takes about a day. And now that I've got a single uncompressed 2.5 TB QuickTime I have no trouble rendering YouTube compatible MP4 files, as I can bypass PPro to render the H.264 MP4.
Bypassing PPro for this H.264 compression stage is also important because I'd like to use a command line approach when creating uploadable video. As there will be a great many videos I'll be splitting off once TR2016 edit is complete.
Chapters
Everyone wants chapters... at least anyone expressing an opinion on the matter. No one has said to me "I love the single 6-hour video approach!"
I do need to follow the single 6-hour video approach. Sorry folks.
Chapters will fall back out of it. But I do need a single-timecode by which the entire narrative can be addressed.
That way I'll have a command-line batch process by which I can extract chapters (probably using FFMPEG).
Chapters will exist online, including on YouTube.
There will also be this monolithic narrative.
If I don't have a monolithic narrative and corresopnding monolithic timeline, then some mechanisms by which people can create their own edits- go out the window.
I need to be able to say to people:
The chapter detailing how fission works is 3h36m50s09f to 04h05m23s14f.
There's a number of other ways to communicate that piece of information that doesn't revolve around a monolithic timeline. Like referring to a single YouTube URL for a video chapter called "Fission".
That will exist too.
But there needs to also be a timecode way of saying it, so that it is possible to "render out" a custom edit with nothing more than a single video download, and a single command-line statement.
That way I can present command-line "recipies" for custom edits, not just visual tutorials on how to use YouTube Editor.