← All posts

Thorium Remix 2016 v20161207

3 min read

Edited up to 4h23m, the moment Kirk is standing in front of a blue-screen talking about nuclear waste. Parts past that might look somewhat done, but I need to pass through it again, so feedback beyond that point would be a waste of your time.

Narrative remains same, except for one moment of levity injected at 4h19m. (Candles!)

The above YouTube video is posted to my gordonmcdowell YouTube channel.

An identical copy has been posted to my other YouTube channel...

https://www.youtube.com/watch?v=4vuXF0MVGCw

...which is only different in that is a channel not whitelisted to use Kilowatts music... the music I licensed from Jamie Watts for Thorium Remix.

This is a fairly important point that I was not yet able to illuistrate because I had not posted an identical video to both channels yet.

Every wonder why some of my videos are copied to other channels and get millions of views (and propagating info about MSR), and some do not?

It is all about the music. The music copyright keeps people from copying the videos, because the people doing the copying are unable to monetize the copies. And all they care about is monetization not spreading information.

While you and I would be posting to YouTube to propagate information, there's an entire YouTube ecosystem dedicated to copying other people's videos and monetizing them. I'd like 1 billion people to know about Th/MSR so we'll need to leverage that ecosystem.

Part of the eventual Thorium Remix infrastructure will include a means of addressing the music-copyright issue.

I'll be posting about that in the future, but I just wanted to take this 2-copies-different-channels moment to illuistrate it. This is why the NASA chapter hasn't propagated as quickly as some of my earlier releases. Because that problem has not yet been addressed. And addressing it isn't as high a priority for me as finishing the entire edit.

Gord vs PPro

Remember when I said "smooth sailing" regarding Premiere Pro 2017? Well I shouln't have said that.

Upgrading was all-in-all a good thing. 2017 is more stable.  And Adobe is incentivized to actually fix problems... they don't issue fixes for older versions they just encourage people to use the latest versions of their software.

BUT...

There is a bug in 2017. Not a crashy bug like in PPro2015, but a time wasting bug.

I lose Audio Preview data whenever PPro is closed. So I re-open the project and need to "render audio" for about 8 hours before I can work.

Spent a couple hours with Adobe tech support remotely logged into my PC poking around changing settings. They were unable to fix it, but hey they tried.

The issue has been escalated with Adobe and I'll hear back from them (I expect) with some new thing to try. Or, worst case, they'll incorporate a fix into next incremental release of PPro.

I've made almost no progress this week not becuase this bug keeps me from working so much as I've been trying (with Adobe) to confirm it is real and figure a solution to it.

That meant an awful lot of closing and opening of PPro. With that 8-hour Audio Render... Every. Single. Time.

On the other hand, having my ediitng PC churning for 8 hours at a time gives me an opportuntiy to write lengthy posts like this one.

So, how was your day? ...Nice weather we're having here in Calgary.

Trump was elected.

...I got nothing.