Wayne Waag
2
COW Coins
Forum Replies Created
-
[Martin]
The screen shots are quite helpful. A couple of things. Your media is 1280 x 720 at 50fps, Progressive. However, your Project settings indicate 25 fps interlaced (upper field first). Why? You should probably change that to Progressive and also Disable Resample of your events at 50fps. That will make Vegas skip every other frame, rather than trying to do an average or resample. You should also set your Full Resolution Rendering to Best rather than Good and change your Deinterlace Method to Blend, just in the event you also have interlaced footage. And finally, why the odd frame size (1920×804)? Do you have other media at 1920 x 1080? Just curious. Another question, what’s your intended delivery mechanism? Media file? Youtube? Bluray? Anyway, I’d first try to change the Project Properties to Progressive and disable resample.
wwaag
-
I use the Mercallli plug-in in V13 quite frequently and it works quite well. My suspicion is that your problem has nothing to do with Mercalli, but rather an issue of your combination of media properties, project properties, and render settings. In any case, you need to provide a lot more detailed information. Screen shots of these three would be the most helpful, as well as on overall screen shot of your timeline. Without such basic information, we really have no idea.
wwaag
-
Are there any online benchmarks of rendering?
Here is a link to the VP11 Benchmark from Sony which is more or less the defacto standard for HD in Vegas. It’s about 2.5GB. There is also a newer 4K Benchmark. There are threads on the Sony Vegas Pro forum where contributors have posted the results with their systems.
https://download.sonycreativesoftware.com/whitepapers/vp11_benchmark.zip
wwaag
-
[Edward Wrobel]
It would be great if there was a book or something that a beginner could read to get a better grasp on things.
Here’s a suggestion. https://www.amazon.com/Vegas-Pro-11-Editing-Workshop/dp/0240823699/ref=sr_1_6?s=books&ie=UTF8&qid=1439433577&sr=1-6&keywords=douglas+spotted+eagle
wwaag
-
[Rick]
This may or may have any thing to do with your problem, but I discovered some time ago that Mpeg-2 renders always add a roughly 10 msec delay to the audio. And that if you now import that file into vegas, and render it again, it will add another delay so that now you’re 20 msec off. Here’s a screenshot
You’ll note that the wave render from the original is spot-on, whereas the m2t render is delayed by almost a frame (60P). In any case, you might want to test for yourself just to see if there is any delay resulting from your render settings.
wwaag
Added: Here’s a link to my original post. https://www.sonycreativesoftware.com/forums/showmessage.asp?forumid=4&messageid=856218
-
[Norman]
Here’s the dropbox link. https://www.dropbox.com/s/zvb2tengg52rbcl/Channel%20Blend%20Presets.vpb?dl=0
wwaag
-
[Grazie]
Comment1: Love the Otter and the chuckling! Around the house, my wife refers to me as the Happy Otter for reasons I can’t say. The “chuckling” came from a YT video of a baby otter and the photo from a screensaver site. No originality on my part.
Comment2: Should ProDad be made aware and thence their option to work with SCS to make people aware and possibly a User friendly solution? Or am I thinking this around the wrong way?
To my way of thinking, the best way to avoid problems is to use the Version 2 plug-in inside of Vegas. No problems of changing levels or colors. Since I can now batch process selected events on the timeline using scripts, there is no read to use the Standalone except in those instances requiring CMOS correction using Version 4. In Vegas, we’re used to doing everything manually when it comes to levels unlike other editors. Mercalli seems to be in the same camp as others in this regard. Hopefully collaboration with SCS will lead to new plug-in that enables batch processing from the timeline without the use of scripts. Their choice to use the SD 601 standards rather than HD 709 is a mystery to me. Having said that, there are others that will argue (notably Glenn Chan) that it really doesn’t make that much of a difference anyway. In other words, don’t worry about the lack of color accuracy. It’s really too bad that Mercalli dropped their AVI rendering option, since it was the only instance of maintaining complete color and levels accuracy. Sadly, most editors are probably unaware that these problems exist, which was really the whole point behind this exercise.Comment3: Could you do a YT on just how you pulled the Levers on Channel? Your trial and error and your reasoning, motivation to use the adjustments and approach would be great to hear and see. Having used Corel’s Channel Blend, I’ve used Channel Blend in Vegas to perform valuable CC. It would be valuable to see your approach.
As far as use of Channel Blend filter, I simply plugged in the numbers for the conversion from the DVinfo thread. The underlying mathematics is beyond my pay grade. The only trial and error was finding a value for gamma correction for ProRes. In searching online, there seemed to be a consensus that a problem with gamma existed, so after applying the 601 to 709 conversion, I applied a levels filter and tried different gamma settings. For testing, I would simply “copy” the preview in Vegas, “paste” into a new file in Photoshop, and then use the eyedropper to determine the color values of the six primaries. Using this procedure, I arrived at a gamma correction value of .86. The first article I referenced has a suggested value of .88, which seems pretty close. I had actually forgotten about this article when I did the testing. Of note, the problem with gamma for ProRes seems to be a Vegas decoding issue. When opened directly in Photoshop, the colors were correctly displayed.
Comment4: Outstanding work!
I appreciate your kind words. It really does mean a lot, especially from someone who’s been a respected contributor to these forums over the years.
wwaag
-
Can you describe this 601 to 709 conversion filter mentioned.
A little background. My interest in this stemmed from using Proshow Producer for slideshows where I export a high bit rate MPEG-2 for import into Vegas. A look at MediaInfo revealed the color primaries, transfer characteristics and matrix coefficients to be BT601, those used for Standard Definition video. My understanding is that, when Vegas decodes MPEG-2 files with a vertical resolution of 720 or greater, it assumes the file was encoded using BT709, the high definition set of coefficients, the result being, the colors are off. I found that applying a 601 to 709 conversion filter in Procoder fixed the problem and then began searching for a fix in Vegas. Eventually, I found this article https://www.personal-view.com/faqs/software/sony-vegas-pro, which referenced a thread at DVinfo https://www.dvinfo.net/forum/what-happens-vegas/115239-mixing-hd-709-sd-601-clips.html wherein the originator calculated the coefficients for such a conversion that could be applied in the Vegas Channel Blend Fx. Some slightly different coefficients were suggested by Glenn Chan, which I also tried but couldn’t see a difference.
What are the channel blend settings?
Here is a screen shot of the actual coefficients.
If you have Vegasaur, I can upload these presets to Dropbox which also include the conversion suggested by Glenn Chan as well as the reverse 709 to 601 conversion filter.
wwaag
-
Thanks Wayne, very useful little video.
You’re quite welcome. Glad that you found it useful. One other thing. Some of the newer LCD TV’s, including an older Sony that I own, have the option to display full pixel. However, its probably safer to assume at least 5% (my choice) or even 10% as John recommended to be extra safe.
wwaag
-
Here’s an easy way to determine the amount of overscan on your TV. Simply download and “play” the file on your TV. My older RPTV has an overscan of 10%, but the 2 newer LCD TV’s are 5%.
https://www.dropbox.com/s/ykxf37o23ofdlrk/Safe%20Zone.mp4?dl=0
Just a little something I put together when learning Proshow Producer.
wwaag
