[Dave Morrison]

Blaise is spot on with this. I came across this video the other day and it explains why we are constantly challenged with finding LED lights that have accurate color rendition. And, part of it is the reliance on CRI ratings for current technology. This little guy is great:

Some contents or functionalities here are not available due to your cookie preferences!

This happens because the functionality/content marked as “Vimeo framework” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.

BVE 2015: How accurate are your LED lights? Alan Roberts tests from Dan Chung on Vimeo.

Also, here is the link to the final test results he mentions in his interview….very interesting reading:

https://www.gtc.org.uk/tlci-results/tlci-results-new-format.aspx

[Dave Morrison]

I apologize if this is a stupid suggestion, but have you calibrated your computer monitor(s)? Maybe your original footage is fine, but your editing monitor is too dark?

[Dave Morrison]

Looks like the camera and the talent were on a dolly/cart and pulled through the room. Possibly undercranked but you could do that in post. A full-frame DSLR could give you the shallow DoF, too.

[Dave Morrison]

Sorry Walt. Tried it with 3 different browsers and no go.

[Dave Morrison]

Just to follow up and try to work around this problem, I imported the BPAV card into Premiere Pro CS6 and it has the same issue with spanned files. Did they fix this in CC? Specifically, at the end of the import process, it throws up a warning box listing all the files inside the BPAV folder that it can’t read/understand and .smi is one of them.

[Dave Morrison]

“The 50% discount was for users who purchased Browser licenses through the Sony Creative Software site. ”

I got a serial number for CB from Sony in some sort of “one time offer” but I can’t remember now if it was free or a paid upgrade.

“Exporting to .mxf is available as an export format in both Catalyst apps.”

I’m not seeing that option…unless it goes by a name other than “.mxf”. In Catalyst Prepare, If I select one of my EX1 clips, go to “Export Clips” and select the “Transcode clips” button, the only options on the pulldown are: AVC/AAC(*.mp4), DNxHD, DPX, OpenEXR, ProRes and XAVC.

And this is weird….NOW when I do the same Transcode steps in Catalyst Browse, I only see AVC/AAC(*mp4), DPX, ProRes and XAVC. .mxf doesn’t even appear any more on the pulldown list. I must be screwing this up somewhere.

[Dave Morrison]

Thanks for the info, Ian. I forgot that I didn’t have a sig attached with the info you needed re: OS. I’m on a MacPro at OS10.8.5 and edit in Premiere Pro CS6. I was hoping to use small footprint program like Content Browser, Catalyst Browser or Catalyst Prepare to be able to quickly prepare transcoded (and unedited) files for a client who is on Win7. It was during the Export/Transcode step that I was hitting the .smi problem.

What advantages would I have by buying Catalyst Prepare if that is the best program to use? Wasn’t there a 50% discount for Content Browser owners who wanted to move up? Expired?

Also, I noticed that the .mxf format does not seem to be available as a transcode choice in CP. Is this also a possible future update or should I try to get my client to switch to DNxHD?

[Dave Morrison]

The only things that affect depth of field are:
1. f-stop
2. camera to subject distance
3. sensor/film size
That’s pretty much it.

[Dave Morrison]

Ian, is this update recommended for all users or just those folks on Mavericks?

[Dave Morrison]

I’d love to know if Premiere Pro CC is afflicted with this same quirk. I still haven’t tested the other drives to see if I can screw them up….guess I’m having too much fun actually using all my drives again! 😉