Bruno Mansi

I think you're talking about a DCTL that can set middle gray? Cullen Kelly has a free Exposure Chart DCTL. He explains all this YouTube video which also provides links to download the DCTL

Not clear from your post if you're running the Flanders directly from the Mac or from something like a Blackmagic Ultrastudio monitor 3G

Just tried some tests with the HDMI output to an Eizo monitor and the SDI output to my main OLED monitor. 1080p/25 project loaded in Resolve. The 'use 4:4:4 SDI' option seems to feed RGB to both outputs. The Eizo doesn't always correctly identify this consistently in Auto (for it's Input Color Format) so I set this to RGB. You can separately switch the SDI output to Y, Cb, Cr 4:2:2 in the Desktop Video and this doesn't effect the HDMI output, although switching from 1080p to 1080 psf does seem to effect both outputs. Switching the Data levels in Resolve from 'video' to 'full' effects both outputs. The 'auto' setting in the Eizo 'Input Range' doesn't seem to identify the signal level, so you have to set this manually. I've found that sometimes switching back and forth between the Resolve settings and the Desktop Video settings, can cause problems with a setting not 'sticking'. In these situations you have to go away from a setting (say, the 1080p/1080psf) and then come back to it. But in conclusion, I could get my OLED reference monitor to display Y, Cr, Cb, 4:2:2 video levels and my Eizo monitor to RGB with video levels with the combination of 'Use 4:4:4 SDI' (Resolve menu) and 'Video is converted to Y, Cb, Cr 4:2:2' (in Desktop Video menu).

What's Blackmagic Desktop Video Setup saying your output is set to? I've found that to be the main determiner of what comes out of the Ultrastudio 3G monitor

Hi Darren, I can confirm that by adding a Paint effect (with a circular blur) would cause a crash in the Baselight plugin, and I didn't need to add any feathering. It seems to happen when you actually park on the shot with the paint effect. I can see some sort of revolving icon in the extreme top left of the Baselight window, and then everything stops. If you render the Paint effect first, then there's no problem with Baselight, so this is the workaround for now. It must be something to do with the real-time rendering of this effect that's causing some issue with the Baselight plugin. Might be worth a support call to Filmlight, who are pretty good in this area.

When you export the AAF, are you choosing to consolidate the media? This is where I've seen Avid adding the '.new' extension to the clip name, as it's effectively creating a new clip. I haven't tried exporting an audio AAF to Resolve - just picture AAFs, but if I have all my original audio rushes available to Resolve, I would think to just export the AAF without any consolidating or embedding of media (as you might do if sending to Protools). In fact, I don't think Resolve can accept AAFs with embedded media.

Hi Darren, Tried a quick test and couldn't reproduce your crash. So, Baselight on layer 3 with shots on layer 1. Various effects added to shot layer and layer 2, including Avid native effects and a couple of BCC effects. Not done anything too dramatic like stacked effects or multiple Baselight layers. Specs of this test setup: HP G9 Laptop with Nvidia graphics, 32MB RAM, MC 2018.12.15, Baselight version 5.3.16760, no external hardware (eg. Ultrastudio). B

It's always going to be hard to match an internal NVME drive as it's directly attached to the PCIE lanes. The sorts of performance I get ( on HP laptop with TB4) is as follows... Mechanical, single hard drive - 100MB/s SSD drive connected via SATA (eg. Samsung T5) - 500MB/s NVME SSD drive in cheap, NVME enclosure with USB C (USB3.1 Gen 2) - 1000MB/s Internal NVME - 3000MB/s I would imagine that (assuming the interface was not limiting the transfers) for RAID 0 with mechanical drives, you'd be getting anything up-to approx 180MB/s per drive. There are some expensive NVME enclosures with proper TB interfaces, which supposedly can reach the sorts of speeds of internal NVME. There's also RAID NVME boxes that can really push the limits of Thunderbolt. Obviously, SSD is the way to go for ultimate speed, but if you need many terabytes of storage, it might become too expensive if you don't need TB/s of speed.

Are you talking about the USB A ports? I think they're 5Gb max, so not going to be as fast as the TB ports. In the past (not with the Mac mini) I've experienced problems with wired mice or keyboards slowing down USB when connected to adjacent USB A ports. What sorts of speeds are you getting?

I don't know of an 'automatic' function, however, if the timecodes of the audio and grade match, then isn't this just a matter of matching them on the timeline when inserting your audio? If not, then off the top of my head... Lay the synced video and audio such that the video is on a track above your grade and the audio on the relevant audio tracks. Now slip this video & audio so the picture matches the graded shot below. You could use a cut point or any other matching action. To aid this match, you could set the transparency of this video layer to 50% so that you'll see both images superimposed. Once you're happy, just delete the top video track.

Going back to the Groups issue, Just read this from the Avid forums... Ok, so I figured out how to update the sequence. You need to make your changes to your group clip, then highlight the sequence that contains that group clip, rightclick and choose "Refresh Sequence > Group Edits". This then updates the sequence with your changes. HOWEVER... I've actually just noticed a very major limitation of grouping in this manner - you cannot shorten the length of a group. You can only add cameras. I just tried taking an already built sync map that I had made and removing a section from the middle. Then updated the group clip and refreshed the sequence by going to Clip > Refresh Sequence > Group Edits. I either get no change - the sequence does not update to show where the gap should be, or I get the error Exception: PMM_INSUFFICIENT_MEDIA. The manual actually states that this is a current limitation - see attached screenshot. So it looks like refreshing the sequence to update it is a no go if you make the new group shorter. You'll still have to cut the new group clip in over the top of your current sequence. If you add to the sequence then it works. This is a pretty major limitation - Avid - when will this be addressed or has it already been in a newer version? I'm working on 2018.12.7. Taken from this thread... https://community.avid.com/forums/t/198883.aspx

Not sure what OS's and versions you're on but there was a problem with certain combinations of software that wasn't putting the driver in the correct place (the AVX2_plugins folder). I believe the latest Desktop Video installer (12.4.2) has fixed the problem Have a look at this Avid forum thread for details... https://community.avid.com/forums/t/207955.aspx

Strange, I thought that was what the 'refresh group edits' was specifically designed for. Possible bug?

Don't know if you can aggregate the memory like this in Resolve to give you the 2 Gig that's mentioned in the specs. Normally, when you install Resolve it runs you through a quick setup which checks your GPU and gives a 'tick' if it meets the minimum specs. I suspect you'd be fine with ProRes or DNX media at 1080p, but RAW files might not play well. I would always go with SSD storage for both the boot drive and media drive to maximise performance.

Did you remember to refresh the main sequence? i.e. Right-click on main timeline in bin Go to 'Refresh Sequence' Click on 'Group Edits'