I have been testing MC 8.9.3. Ran into a recurring bug.
FYI - I work in a shared storage environment.
I set up a sequence in 8.9.3. Top layer is the Safe Color Limiter effect. I set my normal settings. Confirmed that it was working as expected on external scopes.
Then facility needs changed. I went to a different room running 8.5.3 (our current house standard). I opened the sequence created in 8.9.3 and prepared to do an AMA Export / op1a.
Spot checked my sequence and noticed that black levels were now being clipped at around 20 ire!!
I opened the Safe Color Limiter effect and all settings were where they should be. I tossed this effect and redid it in the currently open 8.5.3 system. Levels were now correct. I am currently creating the file to go to QC.
This issue of the Safe Color Limiter effect in a sequence not working correctly between software versions and even PC / Mac systems has come up several times.
Quite boring.
Jef
_____________________________________________
Jef Huey
Senior Editor
Just wanted to check something, Jef.
I recently moved from 8.5.3 to 8.6.5 and found issues with some (not all) grades done before the upgrade.
After some testing, it was found that SOME LUTs were being treated differently in the two versions. In particular, it was the 10bit LUTs applied to the Sony 10bit profiles. The Sony 8bit LUT was fine and the XDCam footage was also fine.
Are you sure your issue is the Safe Color Limiter, and not a problem similar to mine, with LUTs?
Cheers,
Neil.
Different problem I believe. There is a known issue with LUTs acting differently between versions. Can not tell you off the top of my head what those versions are though.
jef: I have been testing MC 8.9.3. Ran into a recurring bug. FYI - I work in a shared storage environment. I set up a sequence in 8.9.3. Top layer is the Safe Color Limiter effect. I set my normal settings. Confirmed that it was working as expected on external scopes. Then facility needs changed. I went to a different room running 8.5.3 (our current house standard). I opened the sequence created in 8.9.3 and prepared to do an AMA Export / op1a. Spot checked my sequence and noticed that black levels were now being clipped at around 20 ire!! I opened the Safe Color Limiter effect and all settings were where they should be. I tossed this effect and redid it in the currently open 8.5.3 system. Levels were now correct. I am currently creating the file to go to QC. This issue of the Safe Color Limiter effect in a sequence not working correctly between software versions and even PC / Mac systems has come up several times. Quite boring. Jef
I have been testing MC 8.9.3. Ran into a recurring bug. FYI - I work in a shared storage environment.
Jef - I have support looking at this now.... Case # 03327496. I used both your email addresses on the case so you get the scoop and also added myself so I can follow it.
Marianna
marianna.montague@avid.com
Thanks M&M,
I have sent the requested info off to support.
Perfect... I got it as well as I am following the case with you... :)
Hi Marianna and Jef!
Just wanted to check in and see if this issue has been resolved as I'm also seeing the bug where a Safe Color Limiter effect that I've used successully for years is now lifting the bottom 20% or so of the signal.
If this information helps your engineers at all, in my case both Avid systems were on 8.5.3, Mac OS X 10.10.5, but the effect only functions properly on one of the systems. When I'm back at that edit bay, I can double check all the other specifics - what I/O is being used, etc. But for now I just wanted to see if you've gotten anywhere as this is a big one for us.
Thanks in advance and hope all is well with you, Marianna!
Jeremy
If I remember correctly, there was an issue with color FX and LUT translating correctly from to 8.5.x. It was fixed in 8.6.x. This means going from 8.4 or earlier to 8.6 or later would be correct.
Replacing the source or destination with 8.5 version and the color limiter would create wrong levels.
Solution would be do everything in 8.5 or remove 8.5 from the equation.
DQS
www.mpenyc.com
My situation was going from a higher ver to a lower ver. It was suggested that that was not a recommended procedure.
Bottom line - in my opionion - is that you should always rebuild the Safe Color effect. You can use the same numbers, just "make it fresh".
jef: My situation was going from a higher ver to a lower ver. It was suggested that that was not a recommended procedure. Bottom line - in my opionion - is that you should always rebuild the Safe Color effect. You can use the same numbers, just "make it fresh". Jef
If its known as broken then it would be better if current MC versions recognised older safe colour limiter effects and automatically rebuilt them. No cure for going backwards but solvable going forwards.
Broadcast & Post Production Consultant / Trainer Avid Certified Instructor VET (Retired Early 2022)
Still offering training and support for: QC/QAR Training - Understanding Digital Media - Advanced Files * Compression - Avid Ingest - PSE fixing courses and more.
Mainly delivered remotely via zoom but onsite possible.
T 07581 201248 | E pat@vet-training.co.uk
Hi. Just wanted to clarify two specifics about what I'm seeing:
1. I'm using a Safe Color Limiter effect that works fine on 8.5.3 on one system, but not the other. Maybe there's something else triggering the issue, other than just the Avid MC version. If I find anything further on what's causing this, I'll update everyone. And I'll keep checking back in case any of you do.
2. Even if I recreate the effect using the same values, the issue persists. I actually need to use different numbers for the bottom of the signal to avoid lifting the blacks about 20% or so.
Are the Safe Color Settings set the same on both systems? (NOT the actual Safe Color Limiter effect)
How are you applying the effect? Is it from a Template effect? If so, what happens if you set the Safe Color Settings with the appropriate values, then add the Safe Color Limiter from the Effects Palette/Image?
I am curious. Are the two system both the same OS? Do they both have the same IO?
© Copyright 2011 Avid Technology, Inc. Terms of Use | Privacy Policy | Site Map | Find a Reseller