-
Videoon 11/24/2022
Do New Blue Legacy Plugins (years 2010 - 2015) Work With Vegas Pro
My copy of Vegas 11 came with NewBlue Motion Effects and Motion Blends, while Vegas 13 had Video Essentials 6, and they all work fine on v19. The Pro Titler that came with 12 and 13, however, did not work at all.
-
Videoon 11/23/2022
Vegas Pro 20 never launches correctly
…They seriously haven’t fixed this yet? Happens to me now and again on 19 (used to be really bad, but is now relatively rare, but did happen today). Thanks for the link to the utility, I’ll give it a try.
-
Videoon 10/28/2022
What system component is most important to preview speed?
That huge image is a linear pan, so I could break it up, but that particular example wasn't too critical as it's only in one small section. I was looking at PSD support, and seems it breaks the layers up into separate streams, accessed similarly to takes? Main issue is there doesn't seem to be any way to name the streams? Naming layers prior to saving the PSD doesn't seem to be reflected inside Vegas. This could still likely work for multiplane backgrounds, if there's any performance benefit, but the confusion factor might be an issue. I'll probably give it a try the next time I need a large image pan. I'm a bit surprised there isn't a good, efficient, fast-reading open-source multilayer image file format (at least one that's common). Like an extension to PNG. I've actually been using Vegas for a very long time! First project was in 2003, and I was using it for HDV video at the beginning of 2005 (bought a Sony HDR-FX1). Granted I only did a couple projects a year.
-
Videoon 10/26/2022
What system component is most important to preview speed?
Yes, I’ve battled with track motion resolution limits in prior posts - it’s one reason I settled at a 4K render resolution, as zoomed softness was too obvious at 1080p. I have since started pre-cropping my character source files (which are native 5000x5000) to ensure that, for every scene, I’m maintaining as much source resolution as possible. Otherwise, I already try to maintain 1:1 with projection resolution as much as possible. For example my latest video has a 19,900x2160 image file for a very large/wide horizontal pan, which does indeed perform very poorly, but at least there’s no scaling. Currently I’m using transparent PNG. I could experiment with TIFF or PSD just to see if it makes any difference. Personally, I think there needs to be far more multi-threaded activity going on. Clearly all image resizing is single-threaded, but I’m pretty sure folks like Adobe have figured out multi-threaded ways to handle that. And perhaps the way in which it handles large images needs to be reconsidered, so it’s not always working needlessly with all data. Typically I work at Preview/Auto for normal editing, Best/Full when I need accurate alignment, and use RAM preview for any awkward areas. I’m a bit jealous that V20 now has preview zoom. I typically turn off scaling when I need to see 1:1, but I can’t pan the window and can only see center.
-
Videoon 10/26/2022
What system component is most important to preview speed?
In trying to replicate my issue in a simple project (which is actually pretty easy to do), I’ve noticed that there is some kind of caching going on where if the project and motion is small enough (like a couple seconds max), it eventually gets cached and can play back smoother or, at one point, pretty smoothly. But in a larger project this cache isn’t big enough and keeps getting wiped by other elements, so the issue is very blatant. A couple things I’ve noticed… * Scaling large images is the biggest issue to performance, particularly if using a motion zoom. Do multiple of these simultaneously and a project can crawl to its knees. * Preview resolution and quality has far less effect on motion zooming performance than one might expect. It seems to impact composition and panning of already scaled images, but even at the lowest preview quality setting, any media-based zooms on large images are useless. And by “large images” I’m talking 3840x2160 minimum, going up to 5000x5000, 7860x4320, even 15000x10000 which is a nightmare (but necessary due to a zoom). * Creating a RAM preview seems to replicate exactly what happens during playback, but at least the system keeps working until the frame is done, so it’s easier to see what’s happening. And while building this preview, ONE core hits a maximum 48% utilization, and the GPU 68%. But not at the same time - it would appear that all image rescaling is done via a single CPU thread, while panning across that image and composition is GPU assisted. * Once a media motion event has been scaled, so long as the dimensions do not change, that existing scaled image seems to be used for pans even across portions of the image that were off-frame. Which kind of implies to me that the width/height keyframe values are essentially inverse: if you take a 5000x5000 image and keep it at 5000x5000, it actually creates a project resolution image of 1920x1920 showing the whole width of the image. But if you zoom in to a keyframe value of say 1920x1080, or 1:1, it’s actually now working with a 5000x5000 image you can pan across, which is a lot more intensive.
-
Videoon 10/24/2022
What system component is most important to preview speed?
Oh, I have to use RAM previews for sure. It's the only way to see what anything actually looks like. And Preview/Auto quality most other times. While previewing is definitely multi-threaded, and it does offload some work to the GPU, I get the sneaking suspicion that whatever causing the chugging is very single-threaded. One thing I've noticed is that if I'm working with a HUGE image, like 10,000x10,000 pixels and using media zoom/pan (to maintain source resolution), playback preview comes to a literal stop for SECONDS whenever it needs to be zoomed/resized overall. But, if I pan across the image at an unchanging zoom level, it's suddenly smooth. I was just trying to figure out what actually would help this be better, besides getting Magix to recode the software. :-)
-
Videoon 10/24/2022
Post Your VEGAS Creations!
Continuing to chug along in Vegas Pro 19 at these simple animation videos, this latest one is barely 3 minutes long but has a 4.1mb VEG file with over 1,800 events. Ouch...
-
Videoon 10/22/2022
Update for 19 is trying to remove 20
So you have an active subscription AND a standard standalone license for 19? Indeed you should be able to use both, but I’ll bet your situation wasn’t considered (as I assume the subscription model would only allow you to have one version installed/activated at a time). I would suggest contacting support and explaining the situation.
-
Videoon 10/16/2022
Caution: Windows 11 22H2 re-introduces AMD color bug.
Thing is, this happened only during the actual 22H2 install (system was otherwise fully up-to-date and rebooted before installation began), and I’m aware of that “feature” and checked immediately after, and no update to AMD drivers was listed in update history (so it could not, for example, be rolled back). I’m sure the update came through Windows Update, but it was not a “regular” installation. A lot if things seemed to be re-initialized after 22H2. For example, I got the prompt to install my motherboard’s tools again, which previously has only happened once when the system was first built.
-
Videoon 9/15/2022
Access Violation Error message when exiting App
Seems that one of your OFX plugins (assuming video) is crashing with Nvidia's OpenGL driver. Perhaps list what OFX plugins you have installed?
-
Videoon 9/15/2022
VEGAS Pro Feature Requests
Just a generic feature request. I would like to see an internal version of AMD VSR or Nvidia DSR. Or, the ability to render footage to a higher resolution and then downsample just before encoding, for improved quality. Let me explain: even when you use high resolution media, any motion performed on a track or parent level is done at the project/rendering resolution. So if you’re rendering at 1080p and apply a 25% zoom to a track, that track is now only displaying 810p. The only workaround is to do motion at the media/event level, but this is not practical for anything involving complex overlayed compositions with child tracks. Currently the only true workaround is to render the entire project to a higher-than-needed resolution, ie. 4K when you want 1080p, but this adds significant encoding time. Especially when you want 4K and need to encode at 8K. What I would propose is a flag that can be set at a project or track level that triggers everything (or that track and children) to be internally rendered at a higher integer resolution (ie 2x) and then downsampled before additional composition or passing to the encoder. While this would definitely add to the encoding time, it feels like it would be less than having to render and encode the whole thing at a higher resolution, while offering higher finished quality for any sort of media positionng or scaling.
-
Videoon 9/14/2022
Does your windows reboot at night while vegas is rendering?
What does the system log show? It should say why the PC rebooted, or at least what it was last doing before it rebooted.
-
Videoon 9/13/2022
Rendering 2x faster when restricting to P-cores for Alder Lake...
Are you rendering in the background, ie. not leaving Vegas as the active foreground application? And do you have one or more than one monitors?
-
Videoon 9/5/2022
H.264 video codec only supports resolutions up to 4K (True or False)
H264 is capable of supporting 8K, but the specific codec has to support it too. VP19 seems to allow up to 8192x4320 with either Mainconcept AVC or HEVC.
-
Videoon 9/5/2022
Post Your VEGAS Creations!
I have long suspected that the human brain is less forgiving with audio quality than it is with the quality of video images. I would agree with you, because I have always been “that guy” who notices every flaw with a movie’s audio track, but can be very forging to picture issues. Background noise, low sampling quality, over digital compression, obviously different take or overdub, glitching, harshness, etc. So audio is very important to me - if only I had the hardware, environment, and tools to create perfection! I’m still using onboard audio, gah! Though that might not last much longer as I think the headphone jack on the case is failing.
-
Videoon 9/5/2022
Post Your VEGAS Creations!
You are a rare breed -- I like that! Heh, well I can also be that super annoying guy who walks into a room, looks at any workflow, and can tell you how to be more efficient. Just ask my wife how well that goes over :) But without strict logic and structure I would go mad trying to create these. Just way too much stuff going on.
-
Videoon 9/4/2022
Post Your VEGAS Creations!
@Musicvid Thanks for the comments! I would actually greatly appreciate you sharing. For the next video I did a number of things differently with recording and audio processing to hopefully improve overall quality (some of which I backported to this one, though I couldn’t quite get it the same). I seriously can’t believe how long a good audio mix takes. Thanks for the screenshot on setting up the loudness meters correctly - was trying to figure out why I was getting +4 and not -19! I do manually create YouTube subtitle tracks for these vids (as the auto-generated one is worse than useless), but haven’t embedded anything into the actual file. I do have a script, but it’s not timecoded. I could work on a tutorial. This whole thing is based on a technical idea that’s been rattling around the back of my head for nearly a decade. “If I could do this and this in Vegas, then why couldn’t I…” until I finally went and tried it. Much of it boils down to having a very ordered and logical project structure - a lot of time has gone into just creating and continually refining a starting template. Every time I go to do something new, no matter how trivial it might seem, I have to figure out how to accomplish it efficiently within Vegas’ built-in abilities - which hasn’t always been easy to sort (masking multiple layers has been a bear), but so far I haven’t had to leave an idea off the table because I couldn’t do it. Goes to show Vegas’ great versatility!
-
Videoon 9/4/2022
Post Your VEGAS Creations!
@Musicvid What tools can I use to see the LUFS like that? And what are ideal maximums? I switched to 8-bit legacy and used the levels plug-in this time, at least for the final render.
-
Videoon 9/4/2022
Post Your VEGAS Creations!
So, here’s my third try at doing animation entirely in Vegas (19) with zero budget and minimal plugins. This definitely was a more complex project to figure out, with an ungodly number of keyframes! Still trying to sort out audio levels… I think I need more tools than I have to make things perfect.
-
Videoon 8/31/2022
Final output Codec
Despite the popularity of hardware encoders (I have access to AMD and Intel), I find the fantastic speed is ENTIRELY offset by the bloated file sizes and - even worse - plainly visible artifacting in complex scenes even with the bloated file size. Certainly fine for previewing, but not for final delivery / archival. I continue to swear by software/CPU encoding. Absolutely the best quality and file size you’ll get, but there’s a heavy penalty to pay with rendering time. I’m running a 12900K and it’s still slow to render, although I personally feel that’s some poor efficiency with Vegas processing on my particular usage as the CPU is often idling at 10-30% while it’s chunking along. Not sure where the bottleneck is… it’s not a GPU thing, definitely not a storage bottleneck… maybe memory? Or maybe it’s just a single threaded thing.
-
Videoon 8/30/2022
Two simple things that make Vegas a superior NLE
By "new user unfriendly" I mean more in the sense that it doesn't try to hold your hand with wizards or make everything big and pretty and show you only a few options at a time so you don't get totally overwhelmed by the possibilities. And I guess by "new user" I mean more "people unfamiliar with the technicalities of using complex software". Like, coming from a diet of CorelDRAW, I picked up Vegas almost instantly because it followed the same UI design and operation principles.
-
Videoon 8/29/2022
I have discovered a flaw/error in Vegas 20 that needs to be fixed
My latest project involves over 260 bitmap files that are often being changed, so I’ve definitely noticed!
-
Videoon 8/29/2022
Veg File Location on new computer
No, YOU enjoy! You’ll love the speed you get from a NVMe. The first time you copy a 20gb file and the progress bar just goes BING you’ll wonder how you ever lived with hard drives!
-
Videoon 8/29/2022
Two simple things that make Vegas a superior NLE
Vegas is “new user unfriendly” but that’s exactly what also makes it fast and efficient and a joy to use for experienced users. Things are “there”, exposed and within a few clicks, which is overwhelming if you don’t know what they are, but so much faster when you do. I feel the same way about the CorelDRAW suite - what a nightmare to get into fresh, but I’ve been using it for practically my whole life and can do pretty much anything with it in amazingly little time. I’ve been using Music Maker out of necessity, a program marketed towards beginners, and while one might reason that it’s simple, it’s also atrocious for usability. Major features/functions are hidden in nested tabs you don’t even know to look at, oft-used functions get microscopic buttons (ie. plug-in settings) and rarely used functions get giant buttons, default editing behaviors are bizarre and uncustomizable…
daniel-t
Offline, Last login 1/5/2023, Member since 11/25/2016