Having never operated this type of software but seen demos of various aspects of Aurora and prior to that Cerify I did hear from some folks it was a slow process. I have been advised by the folks at Tek that many times the speed has a lot to due with what hardware and network infrastructure used. I don't know what that means to the average user.
When you say dead or stuck pixel detection I'm curious if those are really the same process? Isn't a dead pixel in essence a stuck pixel? I've seen where a dead pixel can be black or white or various colors. I think it was green and or magenta artifacts that indicate loss of signal in an mpeg stream. I'm thinking a dead pixel is just stuck at a certain value be it black, white or whatever.
The main issue I'm dealing with is a flashing intermittent Red dot/pixel. As it only pops up for a frame or two and is intermittent I would think that would be very hard for software to detect. It's really hard for my eyes to detect it as well unless I park right on the frame.
---In Avid-L2@yahoogroups.com, <bogdan_grigorescu@...> wrote :
From: "bigfish@... [Avid-L2]" <Avid-L2@yahoogroups.com>
To: Avid-L2@yahoogroups.com
Sent: Wednesday, September 21, 2016 6:58 AM
Subject: [Avid-L2] Re: detecting 4K pixel issues and display response time?
Now if only there was and event tailor made to discuss this exact funtionality? ;-) Oh wait Editor's Lounge September 30th including Tektronix File based QC. I see light at the end of the tunnel, or is it a dead pixel? I'll see if I can find out if they are using a file based QC. In the past it was done by eye to the best of my knowledge.
---In Avid-L2@yahoogroups.com, <tcurren@...> wrote :
Posted by: bigfish@pacbell.net
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (5) |
No comments:
Post a Comment