[Ryan Holmes]

It’s a $137 device. Buy it, try it. If it doesn’t work send it back.

BTW, this forum is for Adobe Media Encoder (video compression software). It has nothing to do with FMLE. Totally different animal.

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

[Ryan Holmes]

[Donald Daedalus] “Actually, adjustment layers exported as XML from Premiere to Davinci are a problem. Currently, they are imported into DaVinci as slug! “

Adjustment layers are unique to Premiere Pro….those won’t translate to other applications (FCP, Smoke, Resolve, etc). You may have success using a 3-way color corrector applied directly to the clip as Resolve does attempt to translate that upon import, but it’s an imperfect process and you’re changing color spaces between the two apps so it’s never a 1:1 translation.

[Donald Daedalus] “Leaving color correction for the end is an antiquated workflow. Even with DaVinci, you can do a “one-light” correction remotely, i.e. while the production is underway.”

Please note that this thread was created while Resolve 9 was out. Collaborative grading/editing was (and largely still is) reserved for Avid and Avid Isis users. You can apply a look or a LUT to your footage for editors to use while they cut. But finished color grading is done once you have picture lock. Resolve 11 is attempting to blur those lines by giving you a NLE within the app itself. How well that works, remains to be seen. But, color grading is more an end-of-the-line step for post-production.

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

[Ryan Holmes]

[Jimmy Ji] “That was my plan, but do you think 1080p 30fps conformed to a 24fps with twixtor might be able to pull it off?”

You could run some tests to see which meets your standards, but Twixtor will be attempting to interpolate and create frames in order to smoothly slow your footage down. Nothing will come out as clear as literally overcranking your camera. I would go with Matt’s approach – shoot 720p60 for all slow mo material, upscaling that to 1080p before you edit.

[Jimmy Ji] “I’m just worried the 720p footage will degrade if I upscale it.”

In my experience, 720p scales very well up to 1080. I think the end user will have a difficult time telling the difference. Especially since the slow-mo will look so much cleaner than if you use Twixtor.

Just my $.02

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

[Ryan Holmes]

If you took still pictures in RAW format you’ll need to use a program like Photoshop, Lightroom, or Aperture to process those.

Resolve is for video color correction. If you took video, you’ll need to provide the forum with more information for help. System specs, video format, storage device, Resolve version, etc.

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

[Ryan Holmes]

ProRes is still available as an export option in CC, provided you have the codecs on your computer. My shops workflow revolves around ProRes through Adobe software. The easiest way to get the codecs is to purchase Compressor from the App Store for $50, and then download the ProApps Codecs bundle from Apple: https://support.apple.com/kb/dl1396

A comprable codec to ProRes is DNxHD. But as the name implies, it only does HD resolutions (no 2K or 4K) – https://avid.force.com/pkb/articles/en_US/download/Avid-Codecs-LE-2-3-9?

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

[Ryan Holmes]

Something else to consider for the renderer:

ATI Graphics cards = OpenCL
Nvidia Graphics cards = CUDA

Depending on the type of GPU in your system that may have been hanging it up (if you had the wrong one selected). Software may be reliable, but it is substantially slower than harnessing the GPU for exporting processes. So you may try matching the setting to the type of GPU you have and see if that works.

An uninstall/reinstall of CC may be in order as well…. :-/

https://helpx.adobe.com/creative-suite/kb/cs5-cleaner-tool-installation-problems.html

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

[Ryan Holmes]

Are you running OS X 10.9.3? Others have reported similar problems if so.

Options:
(1) Install 10.9.4 and see if problem persists
(2) Switch to “software only” renderer inside of AME (drop down box on the bottom of your Queue window)

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

[Ryan Holmes]

Run the Adobe CC cleaner tool and that should straighten you out. Then re-install as needed. Instructions here:
https://helpx.adobe.com/creative-suite/kb/cs5-cleaner-tool-installation-problems.html

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

[Ryan Holmes]

[EricBowen] “The is nothing different to Xeons over I7 CPU’s that allow for any “any heavier lifting” than the I7 or workstation chips. The Xeons only have specific firmware for security and Server operations. Beyond that the CPU’s are the same and zero difference”

There is a difference between the processors you listed and the ones used by Apple, HP, Dell, etc in their more expensive computers. Besides server class processors, you have more L3 cache on the Xeon’s, QPI hooks to replace the front side bus, ability to address more system RAM, ability to address ECC memory-types, etc.

I’m not saying you can’t use the i7 consumer-grade processors to do 4K work. You could. What I am saying is there is a difference between what processor you listed and what Apple, HP, etc spec in their high-end workstations. There is a reason for the price tag associated with those computers. The processors are different and are capable of faster access to data provided the computer is built to take advantage of that…and that is what I mean by “heavy lifting.”

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

[Ryan Holmes]

More information is needed: what version of AME, what type of computer, what are the computer specs, what type of GPU, what file format is the original footage in, what format are you encoding to, what type of disk drive are you using, how fast is it, etc.

Disk speed can be a factor in encode times. If, say, you were using a USB connected external hard drive and all of your media lived there and you were trying to build the encoded file back to the same drive…that could suffer some performance.

But I’ll venture a guess that it has more to do with your actual hardware and file format type (both source and deliverable) as to why it takes so long….

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