[Keith Koby]

Did you try QT Edit or good old fashioned cinema tools to conform the frame rate without transcoding? That might work..

[Keith Koby]

I played back the file on the 8core d700 machine today in fcpx. I’d say it performed similarly to the 6core d500.

I also rendered out the same timeline on each computer which consisted of a 1 min long 4k clip cropped down to around 1:1 for 1920×1080 (cropped down to about a quarter of the original 4k image). The render time was nearly identical between the two machines. The 6 core was actually 4 seconds faster… 5:32 vs 5:36. I’m curious what the speeds will be for this on RedCineX.

[Keith Koby]

Hi David,

According to FCPX it is redcode 7:1. So somewhat middle of the road I guess. We have some 8 core machines here as well. Tomorrow I’ll install the red apple workflow on an 8 core d700 Late 2013 Mac Pro and see how much processor it chews up with the same test library.

Keith

[Keith Koby]

Hey Oliver,

I agree that fcpx is much closer than other NLEs. I’m just missing that feature from 7 where we could control the amount of compensation on playback.

I think some editors are accustom to there being a difference between the gui and the external. We use the external (sdi) monitor for our audio monitoring, so it’s a bit irritating when you do look at the gui monitor in X and it is out of sync with the external audio.

Keith

[Keith Koby]

[Tim Wilson] “There are multiple well-supported professional applications from people like Telestream and Harmonic Rhozet that work directly inside Premiere. ProRes is an export option like any other. No hacks, no freeware, no workarounds.”

I wasn’t aware of this on the windows side… I was under the impression that both episode (on windows) and rhozet (windows only) required windows server (and multiple servers in the case of rhozet) to enable ProRes. A lone windows 7 64 box would be out of luck.

Hopefully you are right and they changed that licensing, but it was a real mess trying to encode to prores from a windoze box.

On the other hand, Vantage/Tachyon ProRes files created on a lightspeed windows server 2008 r2 are very nice. We think the quality is better than ProRes from episode engine, especially when frame conversions are made. I highly recommend the vantage workflow control and video quality generated (with a few exceptions) for anyone who can afford, and needs that much processing.

[Keith Koby]

Thanks Ronny and Andy! Very helpful information re: loop point. Now if we could only include audio…

[Keith Koby]

Audio coming along for the ride in generators as you mention. Bars and tone or countdown slate templates, or lower third with audio effects can’t be made.

Along those lines, generators, inside of fcpx need to be trimmable/expandable, and not just retimed. Imagine you create an animated lower 3rd that is 20 seconds long but only want 10 seconds of it and want to throw a fade on the end. Making it shorter only retimes it to make it faster. Or if you make a 7 second countdown slate and want to shorten it to 5. Impossible.

[Keith Koby]

For posterity, I’m doing a reset of the subject and re-defining the issue:

In Mavericks 10.9.1, attempting to play some 3rd party generated ProRes .mov files through either QuickLook (spacebar) or QT Player X, results in unexpected behavior:

1. On opening, QuickTime Player X will convert the ProRes file to the same format (ProRes) before playing it and prompt the user to save the new movie on close. According to this KB, QT Player X should play ProRes without convert. https://support.apple.com/kb/HT6055

2. QuickLook does not play the movie and instead displays a still and shows the file’s size as 0 kb.

Additional info:

The issue seems to only affect ProRes files that come from third-party transcoders (i.e. vantage) or third-party cameras that record to ProRes.

The preview picture in the finder for assets that experience this problem is a 4:3 image with letterbox when the actual asset is 1080 HD 16:9. CLAP atom issue?

[Keith Koby]

[Franz Bieberkopf] “(also, what sense in the decline of music sales?)”

I can’t remember where, but I read that this was happening because of the radio launch and other radio services. They figured to eat their own with iradio.

[Keith Koby]

Thanks Jari. From the kb, it looks as if ProRes files should playback in quicklook with no issue, but it is not the case with (at least some, maybe not all) third party created ProRes files.