Re: Broadcast safe levels
Posted: Thu Nov 24, 2022 11:50 am
File which you say is bad after AME.
https://forum.blackmagicdesign.com/
https://forum.blackmagicdesign.com/viewtopic.php?f=3&t=84272
Andrew Kolakowski wrote:First bad source. I limit myself in AME.
AME seems to be quite mild and doesn't go slightly above thresholds, so 105% preset may still fail after compression overshoots are added.
If your source is graded properly without extremes all should be fine every time after 103% preset.
It's this low luma 1% threshold which cause most issues here.
Andrew Kolakowski wrote:PSE is about purely UK thing. I think only Japan requires it as well. Not sure who else.
Andrew Kolakowski wrote:First bad source. I limit myself in AME.
AME seems to be quite mild and doesn't go slightly above thresholds, so 105% preset may still fail after compression overshoots are added.
If your source is graded properly without extremes all should be fine every time after 103% preset.
It's this low luma 1% threshold which cause most issues here (but YUV levels are easy to handle before final export).
Andrew Kolakowski wrote:For PSE legalisation (if you need it 1 time a year) you can use https://hardingtest.com.
Most European broadcasters don't need PSE compliancy though. Also don't trust anyone who says it can fix it automatically (like Vidchecker for example). Results are far from usable.
Steve Fishwick wrote:Peter, it might be useful for you to know too, that what happens when you have a fail in QC, is you are normally required to correct it and deliver only a 'patch', i.e. the error plus 1 or 2 shots either side. These are then dropped into the final delivery file. There is no need to output the whole show again.
Andrew Kolakowski wrote:PSE issues are annoying as it's not as simple as "fix flashing". Patterns are specific and something which you think is going to be a problem passes without issue and then others (which look nothing big) fail.
Andrew Kolakowski wrote:Have you tried this link to create TS cloud account:
https://cloud.telestream.net/console/signup
I see other services, but no Qualify. I think I use to be able to use it. Maybe it's gone.
Steve Fishwick wrote:It is by far the most common and biggest fail in QC and is required every time, especially when editors love their flashy FX. We don't just deliver for the UK either. It is integral to Vidchecker in any case and Videchecker fixes nothing. There is no automatic fix I know of. Usually a BCC vignette will fix about 90% of them but there are stationery fails for PSE too, such as a multi-paned window or many parallel boxes.
Marc Wielage wrote:They generally ran the film with a disclaimer that said something like:
Andrew Kolakowski wrote:AVID (FCP, Edius not sure about Premiere) seems to use YUV internal processing, so this is very different.
Andrew Kolakowski wrote:There are other color models, better than YUV/RGB (eg. new Dolby ICtCp)
Andrew Kolakowski wrote:This is why I said ‘seems’. Fact you can do 12bit doesn’t mean it can’t be YUV. It can be 32bit float YUV. It’s internal pixel format which typically has not much to do with export etc. formats. Apple uses special YUV4444 32bit float format.
I still suspect that when possible AVID will stay with YUV processing as it’s desired. Their documents suggest so as they have both RGB and YUV 32bit float formats. For ages AVID was always purely YUV internally.
Andrew Kolakowski wrote:Avid was all YUV as well which you can read about as stated by AVID support. Now it’s hybrid.
Andrew Kolakowski wrote:I already asked Adobe as it happens I have direct email to Premiere product manager.
Then we can see who talks nonsense on forums and who should leave them.
Andrew Kolakowski wrote:It’s 3rd time you accused me talking nonsense ( and already failed twice).
Told you. We will check based on facts who talks nonsense.
You and your professionalism…
Andrew Kolakowski wrote:Have you tried this link to create TS cloud account:
https://cloud.telestream.net/console/signup
I see other services, but no Qualify. I think I use to be able to use it. Maybe it's gone.
Andrew Kolakowski wrote:Vidchecker use to round (if I'm correct) loudness to 0.1 (I think they changed it now) so you quite often get +- 0.1 difference, which could mean reject :