[Ryan Holmes]

For others who may stumble across this in the future:
OpenCL = AMD GPU’s
CUDA = Nvidia GPU’s
Metal = Mac Only API allowing more direct connection to the core video code of OS X.

The cards you listed above in your original post wouldn’t benefit from any of these languages. The ASUS card is severely underpowered to be debayering R3D files on the fly. The Inter integrated GPU (i.e. a graphics card that’s integrated into the motherboard as a cost savings approach for laptops or inexpensive computes) is likely a step down from even the ASUS card.

Switching to the Nvidia card and running CUDA gives you the possibility of realtime playback depending on a host of other factors. Other factors would include – disk drive speed, CPU, RAM amount/speed, what FX you’re running on the timeline, etc.

Ryan Holmes
http://www.ryanholmes.me
@CutColorPost

[Ryan Holmes]

If you want to stay in the Avid DNx world you’ll need to move DNxHR. It’s suitable for 4K deliberables. As the DNxHD codec is named, it only covers resolutions up to HD. DNxHR is what Avid released as workflows changed.

Ryan Holmes
http://www.ryanholmes.me
@CutColorPost

[Ryan Holmes]

You can also look at Telestream Episode, Apple Compressor (if you own a Mac), or Wowza Streaming Engine which had a transcoding component to it.

Ryan Holmes
http://www.ryanholmes.me
@CutColorPost

[Ryan Holmes]

Best book ever written about the C100 Mark II, download link:
https://pdisp01.c-wss.com/gdl/WWUFORedirectTarget.do?id=MDMwMDAxNzQwODA0&cmp=ABR&lang=EN

Hint: It’s the C100 Mark II manual ??

Ryan Holmes
http://www.ryanholmes.me
@CutColorPost

[Ryan Holmes]

[Jeremy Garchow] “FCPX seemingly really long release delay was tied to a hardware release. “

FCPX, which handles Hollywood cinema, broadcast TV, indie film, corporate video, wedding video, and everything else in between in 4K, 6K or 8K was waiting on an updated laptop???

Or, my belief, that the programming team had to hammer out the bugs before release? If they were going to wait for a software release tied to hardware it would seem like the perfect opportunity to tie the Mac Pro or a Super iMac into the event….?

Ryan Holmes
http://www.ryanholmes.me
@CutColorPost

[Ryan Holmes]

[Eric Santiago] “Any updates to QuickTime with Sierra?”

Nothing acts differently on Sierra QT than it did on El Crapitan for me. It’s still the same Quicktime 10.4 version…so nothing newer.

Ryan Holmes
http://www.ryanholmes.me
@CutColorPost

[Ryan Holmes]

[Chuose Osemeka] “How do we now this this once simple thing now in Adobe Media Encoder?”

Your ability to export an Alpha channel hasn’t changed in AME. You need to determine which codec your using and if that codec supports an Alpha Channel. To enable the Alpha channel look for a drop down menu called “Depth.” That drop down will need to be set to 32bit, which denotes your three channels R, G, and B (24bit) + an alpha channel (8bit). You can then bring that file into whatever software and it should act as you’d expect.

[Chuose Osemeka] “Also how does one reduce the size in AME?”

You’ll have to be more specific on this. If you’re discussing h.264 encoding then you’ll need to look at the data rate you’re using and whether it’s CBR, VBR 1-Pass, or VBR 2-pass. If you’re just talking about any given codec…well that’s a big discussion. Different codecs encode files differently using different sample methods – ProRes vs DNxHD vs PNG vs Animaton vs DVCPRO. And within a given codec there can be multiple options offered (ProRes Proxy, ProRes LT, ProRes, ProRes HQ, ProRes 444) which will can greatly change the size of your resulting file.

Ryan Holmes
http://www.ryanholmes.me
@CutColorPost

[Ryan Holmes]

[steve Moore] “I am shooting mainly weddings in 4k on a Panasonic G7.”

4k h.264 footage can certainly be a challenge to edit. h.264 is a notoriously PITA codec to work with as an editable, imo.

[steve Moore] “Move it from my sd card to a sandisk extreme 500 SSD connected by USB. Graphics card is AMD FirePro D500 3072 MB.”

I’m assuming this is a USB 3.0 connection as I’m guessing you have a nMP trashcan based on these GPU’s. If so, have to tried copying the footage over to a Thunderbolt drive? Do you get the same crash?

[steve Moore] “I am attempting to transcode from External SSD using adobe media encoder 2015.3 and it gets through a few clips before message saying need more RAM to continue (i have the max of 64!!)”

Adobe has a well noted memory leak among the AMD chipsets. I haven’t been able to reproduce consistently enough, but this has happened on several of our nMP’s too. I generally recommend setting your destination deliverable to a different drive than your source material. You can also switch over to the “software renderer”….might be slower, but it might still get the job done. Also, have you tried using Prelude as an intermediary? That may or may not help….

Ryan Holmes
http://www.ryanholmes.me
@CutColorPost

[Ryan Holmes]

You can upload a 20Gb to YouTube. So those sizes are fine, just leave it working.

There’s no way around long form content and data rates. It’s just math. So you either live with those sizes or you lower your data rate to get a smaller overall file size which will impact image quality. Until h.265 becomes a usable standard this is the encoding dance we have to do.

Ryan Holmes
http://www.ryanholmes.me
@CutColorPost

[Ryan Holmes]

More details would help….what type of footage are you shooting? What drive(s) is it stored on? How are those drives connected to your computer? What type of graphics card(s) are you running? Are you using the software renderer in Adobe? CUDA? OpenCL? Have you purged your Media Cache? What version of Adobe software are the running? Is it compatible/support the type of footage you need to process?

When transcoding media what are your steps? Are you copying footage to local machine first then importing to AME? Are you transcoding footage directly from SD/CF/CFast card? What other software do you having running while transcoding?

Ryan Holmes
http://www.ryanholmes.me
@CutColorPost