Peter Chamberlain
Forum Replies Created
-
Hi, looks like two or three different threads getting confused here. If we stick with the issue pointed out by Paul in the first post, an image rendered to DNxHD looks different on the Avid UI monitor compared to, some other monitor or application displaying the same file, I presume the Resolve SDI monitor. There is no firmware involved so that seems related to another thread, issue.
You can verify the DNxHD render, or any other, from Resolve by displaying on a HD-SDI grading monitor/projector. Use the same monitor to display the Avid HD-SDI output. They should look the same and can be also verified using a ramp image and a waveform monitor. If good, then work back to each UI monitor to see where the difference is.
Resolve processes in 32 bit floating point with full range images and so there are video level to data level transforms available in the input, render and monitoring depending on your config. Most are automatic but there are user controls too. We also provide the correct display for the UI monitor even though we recommend the HD-SDI output to a calibrated monitor or projector for grading.
Peter -
Hi all, I encourage you to keep an eye out for our next 8.2 beta for Mac and Windows OS that will include support for all four models in the Tangent Element range: Tk, Mf, Kb and Bt. I can also say we have no plans for a cheaper panel at NAB as the low cost panel market is well covered by third parties such as Tangent Devices, JLCooper, and Avid.
Peter -
Hi, do you have FCP installed? Please refer to the BMD support web site for the list of supported codecs and the basis for DVCPRO .mov support.
Peter -
Resolve uses CUDA for image processing and the CPUs for decompression and compression, disk I/O, memory buffer etc… my guess is the system config you have does not match the config guide so you are interpreting the GPU meter and slow speed of renders as a CUDA issue but its not. If you can play in real time and render a fraction of that the issue is likely disk I/O. One disk is too few for a compressed HD image. Try playing back from one and rendering to a second. That way the drives don’t need to change from read to write for each frame. The 1GB of ram in the GPU will also reach its limits if you have a few nodes, and you don’t mention the UI GPU, which should be separate.
Sounds like the application is working as it should given the hardware config.
Peter -
Hi, there is a number of examples in the manual that should help you try some different looks.
Peter -
It sounds like the original AAF from Avid for this project has been deleted or moved and so Resolve can’t read, modify and write the new one for export. If you put the original back in the same location it was in it should work fine.
Peter -
Hi, what GPU card are you using for UI?
If you run the BMD disk speed test what results do you get?
With one clip in the media pool, say a r3d, with 1/2 res good setting in the config, source tab, in the browse window can you scrub the clip ok? Now try in color page.As I mentioned, we don’t have this issue reported elsewhere and it seems fine on my iMac which has a lot less power than a MacPro.
Peter -
Hi, you need to provide some more detail before anyone can offer guidance. OS, system config, project resolution, file type and size etc. etc. We have no other reports of this issue so if you offer some more detail someone might be able to guide you.
Peter -
There are a number of workflow features which make sense when you have a dedicated panel that’s ‘design for optimal operation’ as the BMD panels are for Resolve so the scroll feature is available on the BMD panels.
Peter -
Hi, from your equipment list it seems you do not have an image processing GPU, like a Quadro 4000. If this is the case, the GT120 is being used for UI and processing and its running our of resources when you load the xml.
Please refer to the configuration guide at the BMD support web site for certified hardware configs.
Peter