


Sdi Input Scopebox Tv Home From
Those Lumetri scopes are pretty close to showing the actual signal level as it exists. Way too low.To actually get the media shown on the screen even close to how it was seen by those who created and distributed it takes a bit of work.With the cheapo amateur video players, you mostly need to ignore them. It's all set up from the factory to "enhance" your experience, probably way over-saturated in some color/colors (think reds & greens) and probably way too high a contrast. They're like getting a new cool tv home from the store or Amazon. It is crucial that I have a pure black background, and crushing the blacks in Premiere introduces grain and colour blocking - hence attempting this solution.I have confirmed the pedestal in camera using the Waveform display that is available on the XF 305s.When I look at the footage in Windows Media Player the blacks look right - as in pitch black, however once I import this footage, my blacks look grey and flat.Images for explanation (obviously screen grabs are a poor demonstration, but might help):Now my guess is that Premiere is reading the footage as RGB 16-255 however when I manually configure NVIDIA to display RGB 0-255 there is no change (and I also lose CUDA)I have confirmed my Matrox codec settings are locked to RGB 0-255.I know that Premiere doesn't actually have a colour space, so I am assuming forcing it to read footage in a different way is not possible.32.0GB Dual-Channel DDR3 664MHz (9-9-9-24)238GB Samsung SSD 850 PRO 256GB (SSD) 29 ☌238GB Samsung SSD 850 PRO 256GB (SSD) 24 ☌A "cheapo" video player like Windows Media Player is so designed around the concept of "enhancing the viewer's experience".
Their comments, when they've got PrPro up and looking at Lumetri. My GH3 in say a studio setup can give media that will read from -3 to about 105.My colorist friends all run Flanders Scientific main monitors and have a few grand in calibration gear besides having their complete setups (with 4-5 monitors & a projector typically) professionally calibrated at least once a year. The WMP was displaying them rather high-contrast, as if they were running about -3.And yes, the Lumetri scopes can certainly show data outside that 0-255 range. But pretty darn close.When his signals were showing at around 8.
Or those of SpeedGrade, which I still use at times. Pixel was over-saturated or below/above b/w levels.As I'm not doing any b-cast work, I'm comfortable with the Lumetri scopes. And that major (and costly!) embarrassment of a show rejected because one. Still, within their business, a point or two off is the difference between flying through the QC of the broadcaster without a hitch.
