ultra scopes 1.5 not showing gamut

I just updated my ultra scopes to v 1.5 Seems like there is a bug. With gamut checked for both parade and luma waveform out of gamut trace doesn't appear read as it used to. Anyone having the same problem?

Previous versions of UltraScope had illegal levels locked to anything below 0% or above 100% RGB. UltraScope 1.5 is more flexible and the gamut warning is now based upon your choice of Error Logging Profile. Please see pages 24 and 25 of the manual for details about error logging and error logging profiles. By default, UltraScope 1.5 now uses the EBU-R103 standard for error logging and I believe this will explain the different behavior you have observed.

This is very very helpful. I wasn't aware the the logging profile impacted out of gamut highlighting. However on the B/W waveform or Comp or Both for that matter out of gamut trace is still not being highlighted RED like it is on the Parade. This is the same for the default profile or a profile that I make. Was this intentional or a bug?

Also the error logging is pretty useless to me at the moment because of another issue I've been trying to figure out. Before I moved to Resolve I had a Kona 3 in my machine and it based Timecode to the Ultrascopes via SDI. Now however with the Decklink Extreme 3 the card doesn't seem to pass timecode to the Ultrascopes, thus making error logging not all that helpful. Any ideas on this one? I've looked everywhere for an option but can't seem to find one.

The parade view will show RGB gamut errors whilst the B/W view (YUV colour space) will show luminance gamut errors. These are quite separate and on everyday footage the errors may be different but on extreme images may show similar areas in error.
Like RGB gamut errors, luminance error thresholds can be set up in the profile.

Thanks Hersh and Joshua for your updates. (Joshua I just responded to your email).

After Luke informed me about the profile tie-in, now gamut highlighting it does indeed work for RGB however I still can't get the highlighting to work for out of gamut luma. I've restricted my profile to 100 IRE played with sensitive settings and even if trace is clearly above 100IRE its not being highlighted RED. Granted it does show up in the log and I can clearly see that its out it would be nice to have that highlighted back.

[Robbie Carman]"Thanks Hersh and Joshua for your updates. (Joshua I just responded to your email).

After Luke informed me about the profile tie-in, now gamut highlighting it does indeed work for RGB however I still can't get the highlighting to work for out of gamut luma. I've restricted my profile to 100 IRE played with sensitive settings and even if trace is clearly above 100IRE its not being highlighted RED. Granted it does show up in the log and I can clearly see that its out it would be nice to have that highlighted back.

Robbie Carman"

I'm still searching for an answer to this one. It seems the gamut warning in red is gone in 1.5.

Right now Timecode out of the Decklink HD Extreme 3D+ only works on the resolve application. The Decklink HD Extreme 3D+ supports RP188 output if the Decklink SDK was used to do the integration. This is the case with Resolve, but it is not implemented in FCP or Premiere.