Joseph Owens
16
COW Coins
16
DaVinci Coins
Forum Replies Created
-
[Jesse Glucksman] “Is the Mac too old for a Titan Black”
Anything prior to MacPro 4,1 cannot even see a non-Mac flashed nvidia card… + the OS must be at least Mountain Lion 10.8.5.jPo
“I always pass on free advice — its never of any use to me” Oscar Wilde.
-
[Itai Bachar] “What am I missing”
Do you need to change the “patch cord” slider on the left hand side of the timeline to select the target layer to copy into?
jPo
“I always pass on free advice — its never of any use to me” Oscar Wilde.
-
[Pedro Saboya Burgos] “and finding out that the monitoring in FCP was actually right.”
That’ll be the day.
Use the search function for this forum and look for terms like gamma difference, scaling issues and RGB problems with Quicktime. Its probably the difference between interpreting IRE levels between 0-1024 and 64-940… like it always is.
jPo
“I always pass on free advice — its never of any use to me” Oscar Wilde.
-
[Christian Cornelius] ” Is there any easy solution to this problem? “
Not for your particular macbook, no. Check with the Resolve configuration guide for screen resolution minimums.
jPo
“I always pass on free advice — its never of any use to me” Oscar Wilde.
-
[RuPaul Robbin] ” upgrading my video card to a GeForce GTX680 (advice so far is that this is my best option for a video card upgrade for my MacPro 3,1″
Sounds good on paper, –> big issue is that the Nvidia GPUs (non-flashed for MacOS) will only be recognized by later Mac Pros — 4,1 and 5,1. For this reason I am planning a dedicated PC workstation to continue on in the UHD world, as the MacMini in the coffee can is not going to allow any customization.
jPo
“I always pass on free advice — its never of any use to me” Oscar Wilde.
-
Typically most NLEs want to see Y’CbCr codecs — if you are using an RGB codec like Apple Animation for example, there will have to be a conversion and/or render before the media can be played in real time from most editing timelines.
jPo
“I always pass on free advice — its never of any use to me” Oscar Wilde.
-
[Jesse Glucksman] “I render (with the Final Cut Pro Roundtrip setting) it exports an FCPXML”
There is an option in the export dialog to select one of the appropriate XMLs for various NLEs. For FCP7, there should not be an “X” anywhere in the dialogues or preset offerings.
Premiere XML should be similar to the FCP7 (“5”?) template. The NLE itself should be smart enough to be able to parse out any incoming compatible script — it should ask what it is on import, anyway.
jPo
“I always pass on free advice — its never of any use to me” Oscar Wilde.
-
In Resolve, confirm that the R3D files media start time code value is the same as the .mov files. If they are different, there is provision to change that in the clip properties dialog.
“I always pass on free advice — its never of any use to me” Oscar Wilde.
-
[Chris Coote] “Anybody seen these error messages? Am I losing any metadata by dragging from the media tool, instead of importing the AAF?”
Similar error messages… but not the same. I got errors somewhat like this when I was trying to deal with some XDCam footage without the proper decoder installed, but I don’t think this is your issue.
I doubt you would lose any metadata by dragging with the media tool — another method is to delete the .mdb file, re-launch Symphony and let the application re-scan, then drag it into a new folder.
I can’t think of anymore conflicts other than some fundamental mismatch between media types and project settings between Symphony and Resolve Evelyn.
You are exporting a new AAF from Resolve, correct?… and conforming with the Avid MediaFiles/MXF/# catalog protocol…
jPo
“I always pass on free advice — its never of any use to me” Oscar Wilde.
-
[Mike Parfit] “fits all the minimum requirements in the Readme.”
Must be something different… overall memory, supported GPU, threshold VRAM…???
jPo
“I always pass on free advice — its never of any use to me” Oscar Wilde.