John Rofrano
3
COW Coins
Forum Replies Created
-
[Anthony Regar] “I’d rather not have to uninstall the plugin, so what can I do?”
You really have no choice. At a minimum, you have to uninstall the plug-in to see if that’s what is causing the problem. Then contact the manufacturer of the plug-in and ask for help.
What plug-in was it?
~jr
http://www.johnrofrano.com
http://www.vasstsoftware.com -
Great! You can now increate the pixelation amount without being too distracting because the blur will smooth it out.
~jr
http://www.johnrofrano.com
http://www.vasstsoftware.com -
That was going to be my next suggestion. I forget which version of Vegas Pro got broken by the new QuickTime and you have to go back to an older version.
That’s the problem with using old software… you have to keep the rest of your computer back-leveled because newer versions of other components can break it.
Glad you figured it out.
~jr
http://www.johnrofrano.com
http://www.vasstsoftware.com -
[Steve Rhoden] “If no solution from that link works, maybe a Flicker repair filter”
If no solution works maybe sell the camera and get something that works! You should not have to repair the footage from a perfectly good camera.
~jr
http://www.johnrofrano.com
http://www.vasstsoftware.com -
[Steve Rhoden] “… the built in filters in Vegas are at times limited”
Yea, but in this case they are not. Both the Pixelate and Gaussian Blur are more than capable of obfuscating a face behind recognition.
Blurring a face is always going to draw attention to itself. Humans do not like seeing bodies with burred faces. There is nothing any plug-in can do about this unless you clone someone else head on the body. It’s human nature to want to identify a face.
This is why I recommended to distort the features with Pixelate and then Blur them; this way you can use less of each and still achieve acceptable obfuscation.
~jr
http://www.johnrofrano.com
http://www.vasstsoftware.com -
Open the MOV file in Quicktime Player, use Ctrl+I to bring up the Inspector and see what codec the file requires. Then make sure that codec is installed. For example, Avid DNxHD is not installed by default so you would need to install that separately if that’s the codec that the file requires.
~jr
http://www.johnrofrano.com
http://www.vasstsoftware.com -
[eric adler] “I tried pixelate on it’s own but it draws eyes far too much to that particular area.”
Try Pixelate with a Gaussian Blur after it. This will allow Pixelate to distort the image and then the Blur will smooth the distortion making it even more indiscernible.
~jr
http://www.johnrofrano.com
http://www.vasstsoftware.com -
[Rick Anvican] “I can’t find a reason for the lossy codec to introduce clipping into black/white levels where the levels are perfectly in legal boundaries since lossless codecs don’t have that problem.”
So you are saying that you set your levels, render to CineForm, drop it back into an empty Vegas project and the levels charge? I’ve never seen that happen before.
~jr
http://www.johnrofrano.com
http://www.vasstsoftware.com -
[eric adler] “Gaussian Blur has the best results so far but there are parts of the video even with the effect that show too many features of the face through the blur.”
I would use Pixelate with a mask. That will definitely hide the features better. Also BCC Witness Protection is designed exactly for this job but you have to buy it from Boris FX.
~jr
http://www.johnrofrano.com
http://www.vasstsoftware.com -
[Rick Anvican] “Upon analyzing the videos rendered by the lossy codecs, they all had clipping in white levels, exceeding 100IRE up to about 110IRE (black levels seem to be more “stable” as they tend to stay in the legal levels). The same project rendered to Lagarith (lossless) does not produce a video with clipping on either black or white levels. “
One explanation might be that you are comparing levels in YUV codecs like CineForm with RGB codecs like Lagarith and the levels aren’t measured the same.
[Rick Anvican] “On several YouTube videos, I found that both black and white clipping occur even if the video levels are using the correct sRGB 0-100IRE range.”
The YouTube player will blindly expand all video. It expects Studio RGB 16-235 and if you give it full Computer RGB 0-100 you will get the wrong levels. Only give YouTube Studio RGB.
~jr
http://www.johnrofrano.com
http://www.vasstsoftware.com