While there's no watermarks on this video, please do not share yet. I need to watch it myself and check for errors... I'd appreciate any reporting of errors too. Maybe this one will be public... maybe not. Depends what errors are found. (Update: This will be deprecated!)
I hit a perfect storm of lack-of-time, despite being agonizingly close to done. Goodbye, entire month.
Some non-video good news I should share, we had a son "Angus", our second. He's in great health. Something we'd been trying to do for years and we lucked out before aging-out.
He sorta represented the deadline I was trying to beat (and failed), making this video public (with a bit of promo time) before my video hours were severely restricted. Fortunately I did get very close to p01 being done, so what little time I had got us to where we are now...
Narration is fixed-up as good as it will be. It isn't perfect, but it no longer drives me crazy.
The new bad-surprise was Adobe Premiere Pro vs YouTube... [see attachment] ...around March 10, 2016, YouTube stopped accepting PPro MP4 renders reliably!
My work-around is to render a huge MP4 using PPro, then re-compress (ug!) in Sony Vegas. THAT is successfully processed by YouTube. That is YouTube will accept MP4, just not 1080P 2h+ MP4 rendered by PPro.
That issue wasn't a ton of man-hours... mostly just me starting renders using various settings and letting it upload and wait while doing the new-baby stuff with wife. Eventually enough failed uploads with various settings were rejected by YouTube that it became clear there's a problem between Adobe MP4 and YouTube... It could be either, I have no idea if I updated PPro before-or-after March 10. And no one knows what goes on with YouTube server software. Anyway, that's why you didn't get any updates for an entire month... they all bounced off YouTube.
What man-hours I had were mostly spent fixing narration and music... there's 2 new musical moments in the video that help make it seem less sterile.
And there's a long closing credit, where I'll be using YouTube Annotations for call-to-action at the end of p01. Primarily this is to drive subscriptions so people will catch p02 when it is released.
I also captioned this thing in English. Normally, being man-hours constrained, that's a task I'd try get a volunteer or CastingWords to do. However much of this video was either already captioned elsewhere or based on a narration-script so it was something I could do faster than anyone else... a lot of copy/paste.
While I do need to check the timing of these captions, and their word-wrap spacing, I now much ask if anyone would care to help TRANSLATE into other languages?
Just comment there or email me gordonmcdowell@gmail.com and I'll get you the English data once I've checked timing/spacing.
Anyone can look at the non-timecoded-English here...
https://docs.google.com/document/d/1ODEAd-v84upOKG8Ip4578NEf4DpsGth1J7Ua5epIqfg/edit?usp=sharing
...HOWEVER please nobody translate non-time-coded English!
It must be timecoded, otherwise YouTube will not be able to time the non-English correctly.
So please just get in touch and hopefully we can have some translation happening while I try find time to watch and re-watch this thing via YouTube. (Because some audio issues are only apparent via YouTube when audio is mono at low bit-rate playback.)
And, again, report any errors you can find to me. As an example of the kind of stuff I was fixing since you last got an update, see the 4 "vlcsnap" attachments... there were effects glitches through-out, usually involving super-whites, grays, and cross-fades.
I mean, please report anything and everything. But that was the category of long-standing issue that I've been trying to fix since 2012, and hadn't been the lowest-hanging-fruit until last month. So, yeah, even tiny visual glitches, point them out. Maybe I won't be able to fix them, but at least I'll have an index of them.
UPDATE: p02 20160401
https://www.youtube.com/watch?v=i4TJ5jqRSJI
...shoot I forgot to include that when update went out.
That's the other thing I was working on. You'll hear nothing but TERRIBLE narration in p02... if there was an opportunity for me trying to record good narration it went into p01. What's left is me coughing, gasping, whispering... just really awkward times to capture narration, but I needed to in order to help figure out how it was fitting together.
Still lots of work to do on p02, but you get a sense how I'm thinking it'll fit together.
UPDATE: TRANSLATION
Anyone/everyone interested in translation please see...
https://docs.google.com/spreadsheets/d/1polwEZy7i86irlLTbtt7McCwXSYzG4NrS73po0u2Yx8/edit#gid=83140568
...that's a public sheet editable by anyone. Feel free to create a language column and go crazy.
If anyone would rather throw money than time at a language, then know I've never used a translation service myself only volunteers. So I have no advice or best-practices. I do NOT want to be the middle-man for a language I can't understand, so if you want to solve a language using money then I suggest you contact such a service provider yourself and simply try to keep me in the loop (even if just CC-ing me in email exchange).
I'll do my best to re-integrate any supplied language. But there MUST be a correlation back to original timecodes! If I only get Klingon with no timecodes then there's no way to sync it back properly.
That is why, if a service requires a text file, I'd suggest copy/pasting the contents of the FromYouTube sheet, which contains timecodes as part of text-file rather than as a column of data.