VEGAS Pro 17 Update 2 (Build 353) - General Discussion

Comments

Former user wrote on 11/16/2019, 5:53 PM

Can someone technical explain what is happening here. If I press play, timeline performance is not useable, if I press pause after every transition it plays fine. Also of note is Video decoder use. When I just press play GPU video decoder stays high, but when I pause video decoder goes low. Btw you may ask if after the pausing example I playback again, will it play smoothly without low frame rate timeline. the answer is no. CPU use is in the 60's - 4core 3.6ghz

You can try this video on your computer if you'd like https://drive.google.com/open?id=1_T-ABxAJoVsDA5Sz2-V8p_dDtxE7zjqg&export=download

BruceUSA wrote on 11/16/2019, 6:01 PM

Can someone technical explain what is happening here. If I press play, timeline performance is not useable, if I press pause after every transition it plays fine. Also of note is Video decoder use. When I just press play GPU video decoder stays high, but when I pause video decoder goes low. Btw you may ask if after the pausing example I playback again, will it play smoothly without low frame rate timeline. the answer is no. CPU use is in the 60's - 4core 3.6ghz

You can try this video on your computer if you'd like https://drive.google.com/open?id=1_T-ABxAJoVsDA5Sz2-V8p_dDtxE7zjqg&export=download

 

bob-h .

I download and ran your clip. Its sailing smooth as butter, full frame rate @ best full. Does not matter where I pause and go. Instantly start full speed playing back.

Former user wrote on 11/16/2019, 6:20 PM

I should have mentioned I am using 50% visibility for both tracks. this means where transition occurs vegas must deal with 3 video streams at once. Bruce does GPU video decoding stay around 70%? You have threadripper I see, so more than enough cores if it's cores that vegas17 likes and not efficient at using my 4cores

BruceUSA wrote on 11/16/2019, 7:13 PM

bob-h

I am only seeing 10-11% gpu activity and 16% CPU.

alextudm95 wrote on 11/17/2019, 3:18 AM

Btw the screen capture still not working. This kind of problem should not happen. That will just put a bad images on VEGAS products.

The dedicated coloring panel has some weird glitches. If I do some correction on the Clip A, proceeding to Clip B by drag & drop the color grading FX, when I launch the dedicated coloring panel, it will save the previous Clip A adjustment onto clip B. But the FX is not applied. It just set all of the settings & tweaks exactly like in clip A. but once I double clip the correction/curves/Gain value etc to reset the value it will applied the FX. kinda annoying and slow down my working speed. I feel it is much more faster to use Pan/Crop to check color/masking certain portion of the clip to color grade rather then using Bezier masking inside the dedicated coloring panel. I mean its hard for me to go back & forth between FX panel of the clip to the coloring panel. The whole UI panel is kinda cluttered.

the WB still far from accurate. I think someone has stated it before in the forum.

the Vectorscope/Histogram/Parade might need to redesign give it some fresh look. Especially the vectorscope. In Premiere you can enbale Human skin tones guide in Vectorscope so that whenever you correcting the skin tone, the value will match on the Red value. I dont see this in VEGAS. this is more like a request for future VEGAS 18.

Since I talking about request. Will VEGAS actually introducing real useful FX? the Mesh Warp honestly would be something I rarely use or never for my projects. Luma Keying, Camera Shakes, Modern Glitches, Redesign 2nd Color Corrector for more accuracy color masking in grading/correction, new HUE curves (something like in Pr), Video denoise etc all of these are the real deal. And to make this possible in VEGAS, I have to spend more money on plugins. If Magix can offer more inside VEGAS without plugins, more people will show interest for sure.

I know all of these is impossible to be applied on the next update even on the next upcoming future VEGAS Pro, but if its possible to do I bet more people will starts to looking forward using VEGAS.

 

fr0sty wrote on 11/17/2019, 3:49 AM

Mesh warping enables Vegas, when paired with Vegas effects, to be a powerful tool for creating 3D video projection mapping visuals and being able to preview how they will look properly mapped onto the final object(s) without having to leave the app. Just because it isn't useful to you doesn't mean it isn't useful to many.

fifonik wrote on 11/17/2019, 5:26 AM

@Former user My PC is much lesst powerful, but I only have slight frame drop at the beginning of transitions. And everything recovering automatically. CPU usage ~20% (jumped to 50% on transition start), GPU usage -- ~10%.

It would be better if you provide test project as something important might be missed while others checking...

Camcorder: Panasonic X920

Desktop: MB: MSI B450M MORTAR TITANIUM, CPU: AMD Ryzen 3700X, RAM: G'Skill 16 GB DDR4@3200, Graphics card: MSI RX470 4GB, SSD (OS): Samsung 850 EVO SATA 250MB, HDDs: Seagate & Toshiba 2TB, OS: Windows 10 Pro 1909

NLE: Vegas Pro [Edit] 11, 12, 13, 15, 17

Former user wrote on 11/17/2019, 11:34 AM

I think the 70% video decoding relates to decoding 3 video streams. When I press pause vegas creates a ram cache no longer requiring the decode/compute overhead(decode reduced to 20%) and the only reason my computer can play it smoothly at all. After hearing you can play it just fine I will will look at my system to evaluate what I can fix. Thanks for testing

TheRhino wrote on 11/17/2019, 3:26 PM

FX & codecs vary on how well they utilize multi-core CPUs & GPUs... To compare apples-to-apples, when my 9900K renders the original RedCarTest to the newer Magix AVC 1080p 29.97fps QSV (in 14s), V17 utilizes the CPU up to 75% & VEGA 64 GPU/Intel iGPU combo up to 35%. Nearly all of the 8-core CPU's 16 threads are at 75%. In comparison, other FX or codecs do not utilize as many threads or cores because they are typically older legacy FX/codecs that were never optimized for newer CPUs... I can no longer remember what FX & codecs used, but one project tested with V17 utilized only 1 thread at nearly 100% while all of the other 15 threads were <25% utilized. The source & target drives were very fast M.2 in RAID0 so it was not a matter of read/write speed, etc...

Workstation D with $1,350 USD of upgrades in April, 2019
--$500 9900K @ 5.0ghz
--$140 Corsair H150i liquid cooling with 360mm radiator (3 fans)
--$200 open box Asus Z390 WS (PLX chip manages 4/5 PCIe slots)
--$160 32GB of G.Skill DDR4 3000
--$350 refurbished, but like-new Radeon Vega 64 LQ (liquid cooled)

Renders Vegas11 "Red Car Test" (QSV) in 13s-14s when clocked at 5.0 ghz
(note: BOTH onboard Intel & Vega64 show utilization during QSV renders...)

Source Video1 = 4TB RAID0--(2) 2TB M.2 on motherboard in RAID0
Source Video2 = 4TB RAID0--(2) 2TB M.2 (1) via U.2 adapter & (1) on separate PCIe card
Target Video1 = 32TB RAID0--(4) 8TB SATA hot-swap drives on PCIe RAID10 card

10G Network using cheap Mellanox2 Adapters
Copy of Work Files, Source & Output Video, OS Images on QNAP 653b NAS
Blackmagic Decklink PCie card for capturing from tape, etc.
(2) internal BR Burners connected via USB 3.0 to SATA adapters
Old Cooler Master CM Stacker ATX case with (13) 5.25" front drive-bays holds & cools everything.

Workstations A, B & C are 6-core 4.0ghz Xeon 5660 or I7 980x on Asus P6T6 motherboards.

VEGASPascal wrote on 11/18/2019, 9:52 AM

When editing or importing a large project with vegas 17 the committed ram for me will climb to the max amount than crash. As for Vegas 16 stays at like 10% of what 17 uses.

Here is the same exact project imported with 16 vs 17.

\


@LongIslanderrr Please compare the numbers in Options->Preferences...->Video->Dynamic RAM for Preview max:

Set to 0 on both.

@LongIslanderrr Thanks for pointing this to our attention. We will do some research.

VEGASHeman wrote on 11/21/2019, 8:08 AM

@AlesCZ: Nick Hope had raised the issue of blacklisting with us, and we hope to target it for our next update, so that the blacklisting will be disabled by default when a supported hardware decoder is detected. In the meantime, you can manually disable the so4 blacklist by turning off the following internal pref: "Enable Blacklist for So4 Compound Reader" - that way you do not need to physically delete the blacklist file.

Dmitriy-Makutenus wrote on 11/21/2019, 10:04 PM

updated version 353, the application of the transition Warm Flow is problematic: «your clips differ too much for dependable results, so the warp flow transitions may result in simple crossfade»

Marco. wrote on 11/22/2019, 12:57 AM

This depends on how the frames considered to be warped look like. In some cases a warp transition doesn't make sense no more. The frames must be similar, especially the background, e.g. it can't work properly if the camera moves.

gary-rebholz wrote on 11/22/2019, 8:05 AM

@Dmitriy-Makutenus, there is no problem there. If you're trying to morph two clips that are greatly different, as Marco points out, we warn you that you may not get good results. We put this warning in specifically because we know this will sometimes be the case. That is not specific to build 353.

Dmitriy-Makutenus wrote on 11/22/2019, 8:28 AM

@gary-rebholz, before update 353, the Warm Flow transitions didn't work satisfactorily, but they did (I inserted this transition between "different" fragments). Now, I can't use Warm Flow, and I need to use this transition

paul-priestley wrote on 11/30/2019, 5:46 AM

Hi I have been using Pro17 with no problems, everything work and was fast to execute, until I upgraded to build 353. Since the upgrade everything has slowed down, even moving an item on the timeline now takes a few seconds before it's completed. Virtually every action follows the same pattern, the system freezes for a moment, then says it's not responding, then says its saving 33% before finally executing the action. For example, executing a smart split goes through the same process taking 4 or 5 seconds before it completes. It's becoming a real pain to do anything.

My system is I7 4790, GTX 1060 with latest drivers, 32mb, 1 tb SSD and Windows 10

Anyone any ideas on what I can do or how to get back to the previous version?

Cheers Paul

Reyfox wrote on 12/1/2019, 12:16 PM

@Dmitriy-Makutenus I just installed VP17 build 353 and Warm Flow transition is working for me.

j-v wrote on 12/1/2019, 12:42 PM

@Reyfox & @Dmitriy-Makutenus.
What am I missing searching in Vegas after the Warm Flow transition but never found it. I have the Warp Flow transition, maybe this is you are pointing at?

met vriendelijke groet
Jan

Camera : Pan X900, GoPro Hero7 Hero Black, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W10, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti.
Laptop  :Asus ROG GL753VD, W10 home, version 1903 build 18.362,295 CPU i7 7700HQ, 8 GB RAM, GeF. GTX 1050 (2 GB) + Int. HD Graphics 630(2GB).VP 16,17 and VMS PL 16 are installed, all latest builds
Both Nvidia GPU's have driver version 441.66 Studio Driver, desktop the Studio DHC driver
TV      :LG 4K 55EG960V

Dutch video tutorials for beginners

My slogan is: BE OR BECOME A STEMCELL DONOR !!!

j-v wrote on 12/1/2019, 12:50 PM

@paul-priestley

With me I don't see those problems on both installations.
No idea what is happening with you without specifications about your project and used sourcefiles.
You can go back to the former build by uninstalling VPro 17 and after that install the former build. If you dont have that one or can find it somewhere, aske here or do a system restore to get it back.

met vriendelijke groet
Jan

Camera : Pan X900, GoPro Hero7 Hero Black, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W10, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti.
Laptop  :Asus ROG GL753VD, W10 home, version 1903 build 18.362,295 CPU i7 7700HQ, 8 GB RAM, GeF. GTX 1050 (2 GB) + Int. HD Graphics 630(2GB).VP 16,17 and VMS PL 16 are installed, all latest builds
Both Nvidia GPU's have driver version 441.66 Studio Driver, desktop the Studio DHC driver
TV      :LG 4K 55EG960V

Dutch video tutorials for beginners

My slogan is: BE OR BECOME A STEMCELL DONOR !!!

set wrote on 12/1/2019, 3:47 PM

Former build link can be found here:

https://www.vegascreativesoftware.info/us/forum/faq-where-can-i-download-vegas-pro-and-other-vegas-software--104782/

JJKizak wrote on 12/1/2019, 4:30 PM

I'm of the impression that everyone thinks that uninstalling and re-installing Vegas is a piece of cake. I assure you it is not. Adding all of the third party apps, the scripts, the option settings, the optional ancillary equipment, some of the codecs, window positioning, the product keys, and other stuff sometimes will take hours and hours of screwing around. Just thought I would throw out my opinion.

JJK

fifonik wrote on 12/1/2019, 5:38 PM

@JJKizak True. However, this is still way easier than re-installing Windows %-)

Camcorder: Panasonic X920

Desktop: MB: MSI B450M MORTAR TITANIUM, CPU: AMD Ryzen 3700X, RAM: G'Skill 16 GB DDR4@3200, Graphics card: MSI RX470 4GB, SSD (OS): Samsung 850 EVO SATA 250MB, HDDs: Seagate & Toshiba 2TB, OS: Windows 10 Pro 1909

NLE: Vegas Pro [Edit] 11, 12, 13, 15, 17

Reyfox wrote on 12/2/2019, 7:59 AM

@j-v I was "assuming" a typo and it's Warp Flow and not "Warm" flow.

klapkowscy.com wrote on 12/3/2019, 3:44 PM

 

in this version can somehow enable the old stabilizer