-
Videoon 10/31/2023
Potential Support For VP9 & Opus
I suspect, even the programs that already decode VP9 and Opus would work better with an editing codec. @john_dennis This is YT 4K30 VP9 on a 4K timeline, Clicking on various locations on timeline is pretty instant, scrubbing is not as smooth as a good Camera AVC codec, but this is most likely because instead of a Camera codec with maybe a GOP of 12 or 24 this file is GOP128. That would likely mean for every frame displayed when scrubbing the decoder needs to find the I frame up to 128 frames away. You can see the play across edit points but showing transitions is pointless in capcut as they are automatically cached. So you can either look forward to or seethe about the existence of VP9 in Vegas in the future. With the new render engine I would expect same playback, no requirement for transcoding to an editing codec. Also a self correction, Resolve does load VP9 in webm container and does play opus audio in an mp4 container but not mkv or webm which is unusual.
-
Vegas Movie Studio (up to ver. 17)on 10/30/2023
Different frame rates in one given project
Hi, I have clips at 25 fps (Canon EOS70, FullHD) and others at 30 fps (Sony action cam, 4K), in the same project. Whatever output rate/parameters I choose, the render is wobbly, not fluid at all and almost impossible to watch. Are you aware of any integrated solution in Movie Studio Platinum v17 ? Do I need to move to studio pro ? Try optical flow if MSPV17 has that. It can smooth things out if you go from 25 to 30fps or 30 to 25fps. Problem is Vegas's optical flow is rarely perfect. In this example look at left and right edges, Vegas has problems. No optical flow will work in all situations and should only be used on a scene by scene basis. Some optical flows have the ability to detect scene changes but not sure how reliable that is. Here's an example of 24fps on 30fps timeline 1. 24fps on 30fps timeline (default) 2. 24fps on 30fps timeline optical flow (VP21) 3. 24fps on 30fps timeline optical flow (Resolve) Maybe there's a better approach to mixed timeline for 25/30 fps Edit: not completely smooth actually.
-
Videoon 10/30/2023
Reduce grain
Here's a comparison *nlmeans has been placed on the timeline, it's not processing in real time I like all of them except Vegas's noise reduction, it's using 220watts but giving poor results and 10fps. Neat is very efficient, using almost 1/2 the GPU power of Vegas and did not drop any frames on playback, Resolve NR was getting about 20fps
-
Videoon 10/28/2023
MP4 4K drone files and upload to youtube settings
- during the pan moves of the camera or in the drone circular moves i have a strange effect with a not smooth movement Upload that section of video here, or link to it on youtube etc - once the file is upoaded on Youtube the quality is lower compared to the original MP4 file. Not much you can do about that, it's YT's encoding. As you uploaded at 4K it will be played back either from an AV1 or VP9 encode depending on device playing back the video. They both give reasonable quality generally but can still fail in a spectacular fashion. Look at the first 10 seconds of this video. It looks like a combination of grain, zoom and changing lighting is to blame
-
Videoon 10/26/2023
Does not recognise video files - Vegas Pro 21.0
Vegas can't read VP9 video, that's why you had to transcode 2nd problem, after loading file into handbrake, click the Dimensions tab, change Resolution limit to 4K.
-
Videoon 10/25/2023
Potential Support For VP9 & Opus
Resolve has VP9 support, but only in a mkv or mp4 wrapper, it doesn't support Opus Capcut supports VP9 in webm,mkv and mp4, it also supports Opus audio. Capcut being a Chinese company may be more willing to take risks on codec support where licensing is in a gray area with Resolve being on the conservative end. Fraunhofer and Dolby have made patent claims on Opus, I have read that payment is only required for hardware that decodes and encodes Opus, and software is not affected, but also read it's open source software that is not affected, not all software.
-
Videoon 10/24/2023
issue since a lot of Vegas Pro version, any idea of what it is ?
hello, a video is more easier to undertand than explaining it. sometimes, the dots next to the frame number under the preview blink without stopping and nothing is updated anymore. after that, no other solution to close Vegas Pro, which then crash. That looks like encoding bug where part way through a render Vegas stops encoding, but it's not smart enough to know anything is wrong and will stay like that forever. The encode can't be recovered from, but Vegas is still semi alive. You seem to be seeing the timeline version of that. I'd be interested to see the solution
-
Videoon 10/22/2023
Vegas Pro 20 and BCC Particle Illusion
@Reyfox @VEGASDerek This wasn't after using Particle illusion, it was after some basic Vegas effects & Dynamic RAM previews. @Gid Check if it's only shared GPU memory is filling up, or if infact it has nothing to do with shared GPU memory. In this test after shared GPU memory is filled, the memory leaking stops. It's still bad though, windows becomes more unstable even though there technically is some ram left to use. Nvidia GPU's need to use a combination of Vram/system ram but only system ram from shared GPU memory.
-
Videoon 10/21/2023
Extremely slow and laggy preview with Vegas Pro 21
That's interesting, maybe because your CPU has such high IPC, with my 5900x encoding to 1440P Nvenc from 1440P media I get 100fps with GPU decoder, 105fps using legacy AVC, similar enough not to worry. I tried with resolve too 280fps with both decoder on and off. EDIT: Actually you should check if your media is variable frame rate, Vegas encoding can slow down a lot when it has to decode VFR but I wonder if that's only a problem for the GPU decoder. Remuxing flv,mkv,webm,ts all turn CFR video into VFR
-
Videoon 10/20/2023
Extremely slow and laggy preview with Vegas Pro 21
I did some testing for the recent days and with legacy AVC decoding, editing works smoothly - even with 1440p@120 Hz footage. But rendering was extremely demanding on my CPU, resulting in instantly 95° celcius CPU temps while rendering. Potentially you could turn GPU decoding on again by deactivating legacy AVC when you go to encode. Very fiddly but would make sense the longer your project is. Keep the stress of the CPU especially when hardware encoding.
-
Videoon 10/20/2023
Eye Contact Augmentation
Can't add to last post. Also tried automated eye whitening in Resolve. It also failed. I left the masking on the screen to better show what goes wrong. AI tracking isn't quite there. Mocha sounds ideal for this sort of stuff, but more work
-
Videoon 10/20/2023
Eye Contact Augmentation
I tried a very simple windows build based on Maxine. Not great results, messes up eyes, and eyes are very low resolution. You wouldn't use this in anything but a social media post, but personally I don't think this example is usable at all. Try for yourself, maybe it does better with other scenes/resolutions https://drive.google.com/u/0/uc?id=1wSYviRSL4pktIIvF6Xer5s3AOwHKbN1a&export=download
-
Videoon 10/19/2023
Eye Contact Augmentation
There are apps made for what you require from Maxine SDK, I've seen one demonstrated but can't recall the details. Also with the Nvidia broadcast approach you can use a virtual camera that plays video files, Nvidia Broadcast will pick that up as a source, and OBS will pickup Nvidia Broadcast as a source. Like I say a very messy approach. There's likely a YT tutorial on how to do it I tried it near a year ago so don't recall details
-
Videoon 10/19/2023
Extremely slow and laggy preview with Vegas Pro 21
'How on earth did they manage to increase timeline lag on a product with 10years potential to refine performance plus added GPU decoding?" I expect a much faster response when using GPU decoding in a product of this class, but well... seems like the GPU decoding is still beta or something :-( The GPU decoder lagged 6 years ago when introduced, it lags today. At some point you just gotta admit to yourself that they're not fixing it, and to try work arounds where available. The really big problem is HEVC, it only became established as a distributable format due to GPU decoders, much like AV1 in the future. A $60 android can decode HEVC fine, but not Vegas Pro for many codecs, resolutions and frame rates without lagging. It's a master class in losing customers.
-
Videoon 10/19/2023
Eye Contact Augmentation
If you have an Nvidia RTX GPU look at Github etc for apps or plugins built from the Nvidia Maxine SDK https://blogs.nvidia.com/blog/2023/08/08/maxine-3d-video-communications/ Alternatively you could use a less elegant approach of a virtual camera, OBS and Nvidia Broadcast. The eye contact stuff looks silly to me and people mostly make fun it but I could see how it could work with short cutaways to someone who was obviously reading from a display to the side of the camera
-
Audioon 10/19/2023
Pop Up problem
You can most likely block msedgewebview2.exe in your firewall to stop it if all else fails. I think Vegas is responsible for me seeing it all the time in logs
-
Videoon 10/19/2023
Extremely slow and laggy preview with Vegas Pro 21
First thing you should do is go to preferences/FIle IO, and click on Legacy AVC. This will use the same CPU decoder as VP13 and turn off GPU decoding. You may exclaim: 'How on earth did they manage to increase timeline lag on a product with 10years potential to refine performance plus added GPU decoding?" That's a good question, I'd love to know too. At 1440P AVC and below or maybe even 4K AVC (depending on encoding) with your CPU you will likely have less lag over edit points/transitions with GPU decoding OFF. Possibly you have a real problem that can be fixed, but as you describe it, it sounds reasonably normal depending on what you're trying to play. Tested some 2160x3840 AVC phone footage just then, with legacy AVC turned on it's good, but unticked lags at basic cross fade transitions If your 1440P is from a screen recorder there may be settings you can alter with it's recording settings to make it play better with Vegas's GPU decoder
-
Videoon 10/16/2023
Trying to move to 4K files but previewing is doing my head in
I resisted proxies for several years, and tried fiddling and upgrades. Wish I'd just switched to them earlier, and not worried about higher spec GPU. Hope that helps a little. @gabgilson The problem for him and his R6 is that each minute of 422 10bit footage will take a minimum of 3m30s to encode. I tried the proxy generation in both Vegas and resolve for 2m20s R6 HEVC 422 10bit Vegas 8m48s Resolve 50s I think there's (paid?) tools that can create the vegas proxy externally so doesn't incur the Vegas slow down although I could be confusing that with the 'replace media' method that RogerS was talking about. I think it's natural to resist something that isn't efficient and you know could be done faster.
-
Videoon 10/15/2023
Trying to move to 4K files but previewing is doing my head in
I can't imagine I'm the first to encounter such issues especially as I'm just starting to use formats / res that have been around for 3+ years?I've never created proxies before or transcoded to something else. This sounds like a lot of extra work so am I being picky or is this just one of those things people just accept (with Vegas)?4K YCbCr4:2:2 10bit I tried encoding 1minute of R6 4K camera footage above to 1080P via Hardware encoding. The reason for 1080P is because I"m interested in how fast Vegas can read the camera file, not how fast it can write. These are results Vegas 3m29s Capcut 23s Resolve 20s So from those results if there were to be no losses we could expect Resolve and Capcut can play the 24fps camera footage at 2x - 3x speed and not drop frames while Vegas is only capable of 7fps. So as far as hints or tricks to gain over 3x the performance of the Vegas render engine in order to play 24fps smoothly, there are none. I also have the 5900x, and you'll notice the same problem, Vegas isn't capable of utilizing our CPU's using only 15% to read and process the file, Capcut using 85% and Resolve 65% . Both our systems do not have GPU decode for these 422 files, but the workflow is much more flexible in other editors which are able to edit without transcoding or proxies if required.
-
Videoon 10/10/2023
The System is low on memory
@marcinzm The Vegas fault I conjured is not related to GPU, The same pause on render at random spots that isn't recoverable happens when GPU processing is turned off, GPU decode off, and software encode. I was using iphone 14 10bit HEVC media as replacement files in the Vegas Benchmark Project. I've never seen the pause/crash during render with simple transcode type renders of these files, but put it in a more complex project Vegas dies. There is no crash information because Vegas pseudo crashes, stops encoding and would still sit there for weeks not knowing anything is wrong.
-
Videoon 10/7/2023
When im rendering video my GPU not working just 1% and CPU 100%
How can I make iGPU ? My PC has just NVIDIA GeForce RTX 4060 here is link https://www.uschovna.cz/sk/zasilka/MZVSM93VA5KH79TE-RPZ where you can see my chopping video i add just 15secs You should match your encoding fps with your source and timeline fps. So 30fps source, 30fps timeline, 30fps encode. I believe you have to manually type 30 into the encoding template, as Vegas only has 29.975fps option. However I don't think that accounts for the dropped frames (choppiness) seen with your encode. Vegas handles phone videos very poorly, it can't see all the video frames, while editors like Resolve and Capcut and transcoders like Shutter Encoder and handbrake can handle phone videos much better. That means you either use another editor or you transcode all your phone footage. Capcut is a 4K editor so if you want 8K you'll have to use Vegas. Also to confuse things, I have the same S23U phone, and also use the high bitrate encode option that encodes to HEVC. It does sometimes drop frames but not as bad as the video you uploaded. You're making a comparison between Capcut encode and Vegas encode and find Vegas encode choppy while Capcut is smooth, so that's a Vegas problem . They need to fix the editor.
-
Videoon 10/4/2023
The System is low on memory
@marcinzm I tried the same modified Vegas Benchmark project. 3 of the clips were replaced with 4K HEVC 10bit. Tried rendering three times. Froze at 0.5% and 4% and 2%. Freezes can't be recovered from.
-
Videoon 10/3/2023
The System is low on memory
@marcinzm I only use Vegas for fast simple social media edits. I would not have made a video over 20minutes on Vegas in years. What is the simplest project I could try to get the low memory error, could it be as simple as transcoding a 1080P? 4k? video of a duration of an hour using Hardware encoding and wait for the low memory error? It would be helpful if you give specifics I tried the Vegas benchmark project, cut and pasted it to a bit over 40mins, would have tried an hour but Vegas kept crashing when pasting. I was able to encode the full project at 4K, no low memory error using Voukoder NVENC H.264. You could try the same see if you get an error
-
Videoon 10/1/2023
Vegas Pro keeps crashing when loading frames
Your media is strange 1920x1017. OBS would refuse to capture at that resolution due to incompatibilities. Maybe that's the problem. If there's a requirement to capture at that resolution instead of normal 1080P try 1920x1016 which is divisible by 4 giving it better compatibility
Todd-A0
Offline, Last login 11/29/2023, Member since 1/10/2023