Wayne Waag
2
COW Coins
Forum Replies Created
-
Pulling my hair out!!!
Don’t do that! But, you do need to provide more information about your source footage, project settings, and render settings–screen shots are preferable. Also, you need to provide information on exactly what you mean by “pixelation”. A sample YT video would be helpful. Granted, there are better encoders available than either Mainconept or Sony AVC, but there is no reason why these in-built encoders should not be OK. There is something in your workflow that is most likely the problem, but first you need to tell us precisely what it is.
wwaag
-
If you do try the the Yadif plug-in, remember that you have to set the Deinterlace method to “none”.
wwaag
-
The short answer-no.
wwaag
-
Roger,
It’s really simple. This screen shot shows both the meters and how to generate the log file. If you render, there is a checkbox that permits you to generate a log file as well. It’s much simpler and faster just to generate from the Tools menu.
wwaag
-
For simple titles shown in the video, I’d suggest using Photoshop. Create a transparent empty image, add whatever titles/boxes/graphics you want and export as a png. Or you can import files directly as a PSD from Vegas. I do a lot of moving map animations and Photoshop is my “go to” for all of my text and graphic overlays. To me, it’s the ultimate tool for versatility and compatibility.
wwaag
-
I understand V13 can do the same job and even print out a copy of the report.
Yes it can. You can generate your loudness log before the actual render which produces a text file. Or you can do an “audio only” render which also creates a text file. Extremely useful–unlike plugins, you no longer have to “play” the entire timeline in order to produce loudness data.
wwaag
-
Are you using a UHD monitor? If so, that’s your problem with V13. The icons are extremely small and almost unreadable. Fixes–scale back display resolution to 1920 x 1080 (which kinda defeats the purpose of getting a UHD monitor) or upgrade to V14 which supports UHD monitors.
wwaag
-
For text scripts (those written in Jscript or C#), the fix is very simple. Using a text editor (e.g. notepad) simply replace “Sony” with “ScriptPortal”. Then copy into your V14 script menu folder and they should work. Script extensions (.dll’s) are another kettle of fish.
wwaag
-
“Most people are stuck with whatever camera they have.”
Agreed, but the OP is not doing a camera recording, he is using game recording software, a completely different kettle of fish.
Sorry–I see that he is adding webcam footage as well. Still–no reason for such excessive renderin times.
I did some tests awhile back using OBS for recording. The results can be found here.
https://forums.creativecow.net/readpost/24/1012989
At the time, I didn’t do any speed tests for subsequent renders, but in general I get roughly 44 fps for 1080 60P renders using Handbrake, a much better encoder (IMHO) than those within Vegas. There is an available script that permits one-click operation. Adding levels, color curves and unsharpening drops it to around 38-39 fps. Again, this is on a 4yr old core i7, so newer systems should be faster.
wwaag
-
The problem is your recording software–not Vegas. You need to find something compatible with Vegas–e.g. OBS. A 10 minute video should take no more than 20 minutes to render. Even with with my old i7 3770K, I can render 1080 60P footage in just a little slower than real-time, assuming no effects.
wwaag
