Chris Armstrong
Forum Replies Created
-
Chris Armstrong
January 17, 2012 at 11:19 pm in reply to: Switching from Kona LHe to Decklink SDI – Pros/ConsI’ve got the Decklink SDI card on one my machines and it works just fine. Does exactly what you’re looking for. Works great as a monitor out card.
-
Chris Armstrong
April 17, 2011 at 7:14 pm in reply to: Conform FCP Red Project to Original R3D’s from ProRes TranscodesChris – I misspoke about it not working. Turned out my whole problem wasn’t the naming it was the Timecode.
When I started a new project and set it to read the Absolute Timecode and reloaded my media into the media pool everything worked fine.
The EDL FCP generated from the ProRes files was using the Absolute Timecode, whereas I was bring in the media using the edge code.
I was so busy looking at reel names I didn’t even notice that until now.
-
Chris Armstrong
April 17, 2011 at 7:12 pm in reply to: Conform FCP Red Project to Original R3D’s from ProRes TranscodesGot it figured out. The reel name wasn’t the issue. It was the time code.
The EDL generated from the ProRes material was using Absolute Timecode. But when I imported the material into Resolve it was using the Edge Code.
Once I switched Resolve to Absolute (as Chris Kenny mentioned to do above) the media connected properly.
Thanks for all your help guys.
-
Chris Armstrong
April 17, 2011 at 6:55 pm in reply to: Conform FCP Red Project to Original R3D’s from ProRes TranscodesActually I think the .Mov isn’t the issue.
I just compared the EDL generated from the ProRes, to the EDL I got to work using Mikhail method using Clipfinder.
The EDL’s have very different time codes listed, so for some reason the EDL that FCP generates from the ProRes clips is off.
For example, my ProRes file has this for the time code (which doesn’t work):
14:32:36:01 14:32:41:00The EDL generated from the proxies (which does work) has:
01:12:05:23 01:12:10:22 -
Chris Armstrong
April 17, 2011 at 6:44 pm in reply to: Conform FCP Red Project to Original R3D’s from ProRes TranscodesVladimir – I tried your method, but the clips come in unconnected as well.
I noticed in the comments field under “Conform EDL” that it has the file name correct, but then shows “.MOV” at the end. Do you think that could be what’s keeping it from connecting?
-
Chris Armstrong
April 17, 2011 at 6:30 pm in reply to: Conform FCP Red Project to Original R3D’s from ProRes TranscodesMikhail – Using clipfinder seems to work for me. Thanks.
I had to turn off the option “Assist using reel numbers from the: Source clip file pathname”, but once I did that it connected to the media.
I did this on a test sequence (of 8 clips), so now I guess the question is will it work with a reel that is 75 to 200 clips.
-
Chris Armstrong
April 17, 2011 at 6:06 pm in reply to: Conform FCP Red Project to Original R3D’s from ProRes TranscodesHmm, thanks for the help Chris, I followed what you outlined, but nothing worked.
Every time I load the EDL in Resolve it still shows it as unconnected. I don’t quite get it as I can see the media in the media pool. The EDL has the clip names (though the R3D in the Media pool has an added “_001” to the end of the clips (don’t know if that is throwing it off)).
-
Click on OS X’s “System Preferences”, then click “Display” in the hardware category. Then click on the “color” tab.
-
I solved my issue by changing my “Display Profile”, under the “Color” tab in the Display Setting.
Somehow my profile had gotten changed and once I reset it all went back to normal.
-
Yes I resolve it.
Turns out my “Display Profile” had gotten changed. Once I returned it to a normal profile everything looked fine after that.