-
Videoon 11/26/2020
Denoise is too slow to use
As I specified in the original post, I have 2 GPUs enabled, The built-in Intel UHD 630 and an AMD Rx580. Task manager shows the complete usage of the device on the left hand side. So you're wrong, As I have told you twice, render using denoise, and go through the various gpu engines to check of the GPU activity I have shown. When using denoise for an encode, task manager shows 1-2% CPU usage , 10-15% Memory usage, 1-3% for the RX580 (main display GPU) I dont' have an AMD, but considering we get similar performance and your encoding is not dramatically slower I would say it is using a different engine, you're just too lazy to find out what it is. I would not disagree with you that it is slow and inefficient compared to other denoisers, but then you go on to say it's because it's not using the GPU, which it is. It's not using much of the 3d engine that much is true. Ok, you are right about the GPU but dead wrong about me being lazy, don't know why you have to do that! I'm running Win10 Pro 2004, with all updates. I used GPU-Z to check and yes the RX580 is being used. Seems like A BUG in task manager prevents it from displaying the correct usage on the AMD GPU. In addition, my dropdown menu for what to display does not even include Cuda as a choice. I did a search and it appears this is a common problem, I have no idea what the setup has to be to have windows populate the dropdown with Cuda but it is not there for the RX580 or the Intel GPU on my machine. I changed preferences in Vegas to use the Intel GPU and task manager does show the usage for the UHD 630. BTW: the 14sec clip takes almost 20 minutes to encode using the UHD 630.
-
Videoon 11/25/2020
Denoise is too slow to use
As I specified in the original post, I have 2 GPUs enabled, The built-in Intel UHD 630 and an AMD Rx580. Task manager shows the complete usage of the device on the left hand side. When using denoise for an encode, task manager shows 1-2% CPU usage , 10-15% Memory usage, 1-3% for the RX580 (main display GPU) and 0% usage for the Intel GPU. Neither of the GPUs are being used much at all and neither is the CPU. Temps all stay the same as they are at idle. The GPU's are not being used and neither is the CPU. I don't know what Vegas is doing but it looks like it is spending most of the time blocked waiting for something instead of doing the work required.
-
Videoon 11/25/2020
Denoise is too slow to use
@Hulk, thank you
-
Videoon 11/22/2020
Denoise is too slow to use
Yes, but not an option in many cases.
-
Videoon 11/22/2020
Denoise is too slow to use
I have decent cameras, Panasonic HC-X1, Sony NX-80 and a Full Frame EOS R. The video is decent, I'm looking for the last 5% here. I generally don't have ideal conditions and in most cases certainly not studio/set lighting. I also have some camera lights but in many cases they cannot be used for many different reasons. Just would like the Denoise feature used in the marketing material to work in a usable manner
-
Videoon 11/22/2020
Denoise is too slow to use
I did just now try the Flicker Control and I can see where this may be useful for some of the video I deal with. It does seem to be much faster also. Doesn't detract from the fact that denoise would be unusable in most of my cases. I do lots of recordings of 2-20 minute scenes in poorly lit high school rooms and/or poorly lit stages. Some shows are 2+ hours with many dim scenes. Upgrading the lighting is not an option - I keep trying though! It's not unusual for me to record an event with twenty 3-4 minute performances for chorus or theater departments. At the above rates to denoise would take about 3 hours for each or 60+ hours for the complete event. I currently turn these around for teaching reviews or for families to have the videos in 24 hours of less. 60 hours for just the encoding is not an option. I guess we will live with a little noise!
-
Videoon 11/22/2020
Denoise is too slow to use
I do understand there is lots of processing going on but it would get done faster if the resources of the computer were being used and not left sitting at 1-3% usage on all fronts!
-
Videoon 11/21/2020
Denoise is too slow to use
I understand that some FX is slow, 10 minute to denoise 14 seconds (420 frames) is terrible! In addition, task manager reports no usage so what is Vegas doing? Spending time waiting on something instead of using the resources to encode? I've been in software for 40+ years (systems and production with lots of experience with optimization on compilers and systems) Seems like something is very wrong here. In addition I have used other video editors with build-in denoise plugins that are much faster - much...
-
Videoon 11/21/2020
Denoise is too slow to use
I understand there are other products. That doesn't mean the built-in should be unusable.
-
Videoon 2/24/2020
Color Grading Bugs - 421
#1 is straight forward and really does not require a screen shot. Add color grading to any event in a project and save the veg file. When that project is reopened (same session or a new session) before I do any editing (or anything in VP) the file is marked modified (* next to filename in the title bar) and the undo list includes items from the color grading (lift and gain for example). This cause the "Save File" question if you just open then then close or shut down Vegas. I admit that is not a big deal but does not instill confidence in the release.
-
Videoon 2/23/2020
Problems with rendered bitrate Magix AVC/AAC MP4 MainConcept
I understand there are options but if you request a bitrate that should be a target. I don't recall having this issue with VP15. I think it was a problem with the first VP17 release but was better in a couple of the patches, just to come back worse in 421. I've used a lot of different Video Editing (pro and consumer) and they all get much closer to template requested bitrates. In addition, the Magix HEVC encoders seem to do a much better job.
-
Videoon 2/23/2020
Color Grading Bugs - 421
I will double check on the selection but on my test project I only have a single event on the timeline and I click on the event to work on it...
-
Videoon 2/23/2020
Problems with rendered bitrate Magix AVC/AAC MP4 MainConcept
Does anyone else see this as a problem? I target specific bitrates for my output for different customer requirements and usage. I ask for the required bitrate in the template I'm using and I DON'T get it. It would be ok if it was off by a little (10%) but it's not even close at over 30% off! I have a sample below but it happens on every Magix AVC render I do no matter the project! I did try it with the Magix HEVC templates and it's much better, I just cannot always deliver H.265 media files. I ran a couple more test to illustrate. I have a 30 sec 4k/100Mbps clip right out of a Sony NX-80. Drop it on the timeline and render: Magix AVC/AAC MP4 using the built-in template Internet HD 1080P 29.97 (bitrates are set to 12Mbps avg, 24 Max) Mainconcept (CPU only): Render Time: 0:30, output MP4 size: 61MB, bitrate - 16 Avg, 24 Max! QSV: Render Time: 0:25, output MP4 size: 34MB, bitrate - 8 avg, 24 Max!! AMD VCE: Render Time: 0:09, output MP4 size: 43MB, bitrate - 11.8 (no max specified) I can make AVG and MAX the same and the output is much closer to what was requested but I feel like I'm limiting the encoder. I could also choose constant but again - limiting the encoders ability to vary the bitrate based on content.
-
Videoon 2/20/2020
VEGAS Pro 17 Update 4 (Build 421) - General Discussion
I had a few minutes to test and it appears that my problems with VP not being able to use multiple GPUs when one is the Intel built-in HD 630 have been fixed in this release! Yay! BTW: this worked correctly way back in VP15 in 2018 until it broken when Intel switched to DCH video drivers! Specifically, I can now use an AMD RX 580 as my main GPU running my monitor at 4k/60 (only able to run it at 4k/30 using Intel GPU) and still have VP use the Intel GPU for timeline editing acceleration. A few quick encode timings for a 2 minute 4k clip encoded using Magix AVC/AAC MP4 to 1080p/30 6Mbps avg/10Mbps MAX. Only difference in the runs is the encode mode is changed from Mainconcept to QSV and then AMD, no other settings are changed! Using only the built-in Intel HD 630: MC (CPU only): 2:14 but output is 8Mbps with Max at 10, instead of the requested 6/10 QSV: 1:00, output very close to 6 avg, 10 max With both Intel HD 630 and AMD RX580 installed and enabled: MC (CPU only): 2:08, again output at 8/10 instead of 6/10 QSV: 1:24, output 4.8/10 instead of 6/10 - don't know why speed and actual bitrate dropped with extra GPU. AMD VCE: 1:02, output close to 6/10. So, I'm not at all concerned with the exact speed, just wondering why MC and QSV output doesn't at least get close to the requested bitrates in the template used.
-
Videoon 2/20/2020
VEGAS Pro 17 Update 4 (Build 421) - General Discussion
Finally got it installed after 3 downloads. Only the direct link worked - vegaspro17_dlm. Also, the download from the program auto update took at least 10 minutes. It was 10x faster using the direct link.
-
Videoon 2/20/2020
VEGAS Pro 17 Update 4 (Build 421) - General Discussion
Just tried for the second time to update from VP 17 387. Started VP17, it said there was an update, I said go for it. Took it 10+ minutes to download. I said install immediately, VP17 window disappeared, security window appears (allow VP install...) I clicked yes, and then I get an error - Installer unable to update while VP is running!... Ok, I tried it again - UGHHH it started the download again from the beginning. and I get the exact same error message - cannot install with VP running. It's not running - the install shut it down and the window disappeared before the security window opened!!! Trying the direct download and install now!
-
Videoon 2/19/2020
Color grading causes bad frames in rendered output
I did go back and test other formats (Sony AVC/MVC, Magix Intermediate and WMV) and they all failed with the bad frames. I turned off GPU in preferences and they all rendered correctly. Not the first time there have been issues with GPUs and VP but GPU acceleration is one of the reasons I use VP! I suspect I can find an earlier version of the Intel HD 630 driver that does not have the issue - not a fix, just a work around. It's a bug in either VP or the Intel driver! To reproduce the GPU timeline acceleration issue... Drop a 4k video on the timeline, something longer than about 45 seconds. Open the pan and crop tool (sync cursor enabled) and just drag the scrubber back and forth. If I only have the Intel GPU enabled the scrubber is very responsive and using the task manager performance tab you can see the Intel GPU being used while you move the scrubber. If I have the intel GPU disabled and use the RX 580 or even if I have both GPUs installed and enabled there is a noticeable lag on my machine (i7-8700K, 16GB, 2 fast NVMe M.2 SSDs, Samsung PM981, WD Black) and again checking the performance tab neither GPU is getting used for that operation. Note that the last time I tried this was with the original release build of VP17. I may try again when I get time drop the RX 580 back in...
-
Videoon 2/19/2020
Color grading causes bad frames in rendered output
As I mentioned in my original post I have the same result using Mainconcept (CPU only) and QSV (Intel HD 630) rendering. I have the latest Intel HD 630 driver (7755) installed but I might try an older one to see if there is a change. Intel has broken stuff before with these DCH drivers. I have a couple AMD RX cards (560 and 580) but pulled them out because of problems with stability with VP17 with both GPUs installed. In addition, if I only use the Intel HD 630 I see timeline editing speed improvements (especially in pan & zoom) that disappear if both GPUs are installed and active. I like the idea of GPU accelerated FX and encodes but not at the expense of timeline editing performance! And, just for reference, using VP15 I was able to use both the Intel built-in HD 630 (and get the timeline speed improvements) and the AMD GPU for FX and rendering UNTIL Intel changed to the new architecture DCH video drivers! At the time Intel claimed that they were aware of the issue but the only fix would be to have the application rebuilt with the newest Intel Media SDK. Magix would not do that with VP15 so I upgraded to VP17. Both GPUs now show up but VP17 does not use them correctly. If both are installed I get lags in pan and zoom just moving the scrubber!
-
Videoon 2/19/2020
Thought I would give vegas 15 a shot at stabilizing a project. Help?
I was never able to get VP15 to stabilize any 4K video, it would either hang or crash. I had one project I really needed it for and ended up using a cheap competing product and it worked! I have not tried it but VP17 claims an all new video stablization to correct the issues with previous versions. I was happy with VP15 but paid to upgrade to VP17 in hopes of some specific problems getting fixed. Some were, some were not - oh well. The real problem is when they come out with a bugfix but break other stuff!
-
Videoon 2/3/2020
A reason of why VP17 not load HitFilm Movie Essentials Pack
I was trying to use Hitfilms Movie Essentials that I purchased with Vegas Pro 15 directly from Magix. I did get another response from FXHome today and it's looks like I'm out of lucky unless I want to go back to VP 15: A new response has been posted to your ticket: Hello,Thank you for your reply. It is not possible to use Movie Essentials in VEGAS 17. You must use an earlier version of VEGAS in order to access those plugins. Regards, Axel WilkinsonHitFilm Support Great guys, thanks for putting your customers first!
-
Videoon 2/2/2020
A reason of why VP17 not load HitFilm Movie Essentials Pack
Yes, I have projects using the Hitfilm plugins. I've contacted FMHome and they blame Magix (you need an update of Vegas - no, I have had 2 updates since the problem) and Magix blames FXHome (you need a Hitfilms update) . I got my Hitfilms license with a purchase of Vegas Pro 15 and I used it in projects. Now I update to Vegas Pro 17 and my projects fail with missing plugins - How can any user trust Magix going forward? Doesn't make sense! I was in software for years and there is no way we would have ever done this to our customers!!!! Image updated to a new version of corporate DB software and not being able to access your data!!! I have an investment in software and training in Vegas but I am looking for other options as this is not acceptable!
-
Videoon 9/26/2019
VEGAS Pro 17 Update 1 (build 321) - General Discussion
Just installed 321 and it is still not loading hitfilms movie essentials. I also tried uninstalling and reinstalling Movie Essentials after the VP17 321 update but it is still not being loaded! I did contact FXhome about this issue at the beginning of Sep (before the VP update) and received the following response. Where is the fix is this update???? A new response has been posted to your ticket: Hello,Thank you for contacting FXhome. That compatibility requires an update to VEGAS Pro 17, and I believe Magix plans to include it in the next update to that software. Regards, Axel WilkinsonHitFilm Support
-
Messageson 9/5/2019
[Release] VEGAS Pro 17 – The fastest NLE. For passionate creatives.
I keep reading in the forum that the VP 17 plugin problems (hitfilms not working , BCC installed crashes VP at start, etc) are caused by the plugins and require plugin updates. It appears to be a problem with VP. I asked about a new compatible version of Hitfilm Movie Essentials at FxHome and got the following response: "Hello,Thank you for contacting FXhome. That compatibility requires an update to VEGAS Pro 17, and I believe Magix plans to include it in the next update to that software. Regards, Axel WilkinsonHitFilm Support"
-
Videoon 9/5/2019
VP17 and Hitfilm and Boris
I asked at FXHome and it seems like it is a VP 17 problem as this is the response I got: "Hello,Thank you for contacting FXhome. That compatibility requires an update to VEGAS Pro 17, and I believe Magix plans to include it in the next update to that software. Regards, Axel WilkinsonHitFilm Support"
john-rappl
Offline, Last login 12/3/2020, Member since 10/1/2017