Thanks again for all your help!! I finally managed to get Telestream to work. It took LOTS of time, as setting up the S3 storage and applying the rights for telestream to work wasnt flawless at all - and there were no presets for broadcast available. At least with pulsar I found those RGB value error, corrected it by making the scene a little brighter and now there are no RGB alerts in Pulsar or in Telestream qualify anymore. It was during a very short camera pan shot so I just had to animate the brightness level of the scene. So in the end it helped, but still its strange that a "broadcast safe" filter with stricter settings plus the Adobe Media encoder with strictest video limiter settings didnt get me safe colors.. I will scan all my deliverables in the future just to be safe.
The other checks from telestream could be useful as well:
one progressive (psf) scene in my interlaced timeline - which was right.
Audio transients - in this case clicking noise which was intended, but could be useful.
Freeze frames, which detects every slight slomo I apply for a second to some clips
Audio integrated loudness, true peak max, momentary max - just to be safe for final export.
And it has this "video quality rating" graph, which is nice to have a look at..
Andrew Kolakowski wrote:It’s totally unreliable, so forget about those errors or learn that 95% of them is false.
The more different checks you turn on the more false errors you will get.
It can show you that field dominance keep changing even if your file is perfect.
If you preview properly interlaced content you see straight away bad field order.
You really need to stop trusting those QC tools so much.