VEGAS Pro 15 Update 4 (build 321) - General Discussion

Industrystandard wrote on 3/25/2018, 6:13 PM

@industrystandard, curious as to what performance issues you have. I have VP14 Edit and VP 15 Suite. I don't do long form videos any more. Short, usually under 10 minutes, but they are 4K UHD. I don't quite have the computer horsepower you have, but editing on the timeline has been really great for me. Yes, using proxies for sure, and Preview>Full, but doing color correction, etc., has been painless for me. That, along with memory usage being less than VP15 at the moment. I am a novice with VP, but not so with editing. I bought VP because I was impressed with it's timeline editing performance. I do see I will have to upgrade to 32GB of RAM in the future when RAM prices come back to earth.

Computer specs:

Ryzen 1700X overclocked to 3.9Ghz

MSI Gaming X RX480 8GB RAM

16GB DDR4 3200 RAM

Win10 Pro 64

1TB SSD system drive, lots of mechanical storage drives.

Performance issues, playback, rendering crashes, regular crashes, stalls, buggy plugins especially with compatible plugs like blue fx, HitFilm etc.. The weird report a problem window that actually doesn’t send errors ( I know you have to do some other workaround to actually send this error message). The editing tools are really good with VP and that’s why I chose it, but having a powerful computer like mine should improve my experience, not hinder it.

Reyfox wrote on 3/26/2018, 12:58 AM

@Industrystandard, my experience has been different than yours for whatever reason. It certainly isn't because my hardware is vastly different than yours. I have NBFX and Vitascene, in addition to Boris Beauty Studio and what comes with VP15 Suite. All work as I would expect it to. And for "me", working in 4K with proxies turned on, timeline editing is as fast as I can move the mouse or type on the keyboard. The added Hitfilm plugins worked and caused no slow down that I could notice.

I agree with you, the editing tools are really good. And the reason I bought VP is because of the speed I could edit with. Still learning the software so haven't ventured too far into what it can do. Maybe then, I'll be joining your chorus.

As for the error reporting, I just found out that you have to use the "work around" to get an error reported. I had the trial VMS15 and it crashed all the time and wrecked the plugins for VP. I would think something as informative as what the error reporting could bring to making VP better would be high on the priority to fix.

paul-priestley wrote on 3/30/2018, 5:35 AM

Hi, I wonder if anyone else is experiencing this problem. The program (321 version) itself freezes on loading at :

'Creating File I/O Manager' or it will take on average around 5 minutes to get past this point and then it loads up reasonably quickly. My system is Windows 10 (latest updates install), I7 4 core processor, 32 GB ram and GTX 750TI

I find 321 crashes (white screen) a lot, but this has been much reduced by setting Enable Multi-rendering to False, but I haven't as yet disabled so4compoundplug.dll I don't know whether this will help with the loading problem. Has anyone any ideas, because having to restart the program is becoming a real pain.

Cheers Paul

Reyfox wrote on 3/30/2018, 6:10 AM

I personally haven't experienced that. I've found (with my limited use and understanding of Vegas, I'm new) it to start quickly and at least when I've used it, not crash...... so far.....

Dexcon wrote on 3/30/2018, 6:16 AM

I haven't as yet disabled so4compoundplug.dll I don't know whether this will help with the loading problem

Why not give it a try ... it's actually quite easy to disable. If it doesn't solve the loading problem, get back to the forum afterwards.

Roberto65 wrote on 4/1/2018, 5:46 PM

Hi all,

I am using Vegas Pro Edit 15 and I am experiencing RAM usage steadily increasing during rendering: once I loaded the project I am working on, about 47% RAM reported to be used. After 5% of rendering completion the RAM usage was already at 72%, then it moved a bit down, but then the RAM usage increased till 84% and at 13% of the rendering completion Vegas Pro crashed. I have 16GB RAM, so, in just 5% of rendering it used 25%, that means 4GB... and later is sunk other 1 or 2GB of RAM!!!! The project is absolutely nothing complicated (just few video tracks with some video effects) and the rendering is targeting HD 1920x1080 format.
I developed and rendered much more complicated projects with VMS13 and got no issue at all: really stable.
It sounds really like a poor SW coding that generates memory leaking during the rendering process... to be fixed asap, otherwise to me the SW is basically unusable and I will have to file a reimbursement of the money.

Roberto

toineenzo wrote on 4/1/2018, 5:55 PM

Still no news for the update coming to the Steam version? I am waiting for a month already......

vkmast wrote on 4/1/2018, 6:08 PM

@Roberto65 just to confirm. As this is the build 321 discussion I assume you do have that latest build. I've not seen it mentioned in any of the three threads you bring up your issue, only "just bought, so I guess I have the latest version."

Roberto65 wrote on 4/2/2018, 4:15 AM

Hi vkmast, yes, it is Build 321

UPDATE: it seems I sorted out the problem. The root cause seems to be a nesting of BCC Continuum Object FX, which means the same effect is applied to both the Track and some of the events along the track. This seems to create memory leaking. I "baked" the Track effect into a rendered clip, imported the resulting clip, then applied the single Event FX (after splitting the clip into sections) and now I do not see any memory leaking anymore.

AVsupport wrote on 4/9/2018, 12:09 AM

what helped me the most (so far) to arrive at a stable system was to DISABLE the internal GPU in the BIOS. I run everything of the nVidia GTX1060, system, timeline, rendering; 4K monitor + FullHD monitor. so far so good.

Fiola wrote on 4/9/2018, 6:30 AM

So, I gave it a shot and I was working under 321 for two weeks now. And I have still same issues, but less frequently.

After some time of editing, every time I am finishing my timeline (i.e. 7 minutes long video), when I press the RENDER AS - the Vegas hangs and stop working. After reload of the application and the project, clicking on RENDER AS working as should. So maybe some another memory leak or uncovered exception? :)
Render times are still long. But I can live with that, I am more outraged with 4K timeline preview which is still pretty unusable for me. I am really editing on "blind" here, even with DRAFT (QUARTER) the preview is unusable, especially when I will add more 4K videos over. I know there is a big bitrate and datarate going on, that why I have so much RAM and NVMe SSD for. Again, I am checking this behaviour also with Adobe Premiere - where timeline works fine with same sources without creation of Proxy Files.
Video preview is still "hanging" between cuts. For instance, when I will insert two videos besides them, everytime I play preview, before preview wants to show another frame of next video on timeline, the VEGAS just stops the preview showing "..." in FRAME number, skipping few frames later on, which makes for me difficult to say how the cut looks exactly in full speed. Instead I need to use arrows to check every cut. The SHIFT+B pre-render should help, unfortunately, many times after I do my RAM preview, it will just hangs again like RAM preview never was in effect.

These are just quality of life improvements I would like to see to the nearest future resolved. Overall, stability is much better with 321. And I mean a lot better. So thanks MAGIX to finally addressing this and for the work. Please, keep the updates coming on more frequent way. There needs to be a way how to replicate these issues, I am not only one having trouble with this :).

Former user wrote on 4/9/2018, 3:15 PM

@Fiola

“But I can live with that, I am more outraged with 4K timeline preview which is still pretty unusable for me.”

I know its so basic, but still, we can sometimes overlook, setting/matching project properties to timeline media properties is so important in giving the best playback.

Reyfox wrote on 4/9/2018, 3:33 PM

I too edit 4K on my computer: Ryzen 7 1700X @3.95Ghz, 16GB DDR4 3200 RAM, RX480 8GB, and it works ok with 4K on the timeline if I don't do anything "crazy". I usually let VP15 create the proxies with Preview>Full. Yeah, proxies are created, but at least I can see what happens with I do something to the clips and have smooth playback....

OldSmoke wrote on 4/9/2018, 3:57 PM

I had some time over the weekend and played with the internal settings of SVP13 and VP14, I cant test it on VP15 but maybe some can. These was all done with the intent to get smoother timeline playback, especially for 4K XAVC-S footage. While unsuccessful with that type of footage, it greatly improved playback of XAVC-I 4K footage to the point where I can playback 32bit full at Best/Full even with FX applied.

I changed these to 4, 8 and 2 (from the top).

And there are these two

I changed it to 4000 and 8000 (from the top).

And these ones

As one says " Your mileage may vary" but it did wonders on my machine with SVP13 and VP14.

Reyfox wrote on 4/9/2018, 4:09 PM

Hmm.. interesting... will try later...

AVsupport wrote on 4/9/2018, 8:25 PM

@Fiola , try this memory tweak also, this did help stabilize my system:

NickHope wrote on 4/10/2018, 2:17 AM

I had some time over the weekend and played with the internal settings of SVP13 and VP14...

Thanks for that OldSmoke (and AVsupport). I added a link to these internal preference tweaks from the FAQ post on smooth playback. Currently point #15. [Edit: Removed for the time being following concern from developers about users causing instability by editing internal preferences without knowledge of the side effects.]

ritsmer wrote on 4/10/2018, 10:11 AM

Tried OldSmokes suggestions on some 3840x2160x12 AVC media but did not see significant improvement in previewing on my machine - however:

Then I tried to change Dynamic RAM preview from 0 to 100 - that made the CPU usage (when rendering) jump from app. 43% to 100% and render time from 49 seconds to 21 seconds. Output is MainConcept mpeg2 1920x1080 25 Mbps.

Actually in "the good old days" (Vegas 8,9 etc) in the forum we used to help each other finding the sweet spot for Dynamic Ram for rendering every time a new Vegas version was released as the peak was rather narrow and mostly was around some 130 MB - but could move a little up or down from version to version - as far as I remember 🙂

Edit: With this knowledge it is not a good idea to set Dynamic RAM to 0 in order to improve stability - as it - in some cases, at least - significantly slows down the render time.

OldSmoke wrote on 4/10/2018, 10:57 AM

Tried OldSmokes suggestions on some 3840x2160x12 AVC media but did not see significant improvement in previewing on my machine - however:

Then I tried to change Dynamic RAM preview from 0 to 100 - that made the CPU usage (when rendering) jump from app. 43% to 100% and render time from 49 seconds to 21 seconds. Output is MainConcept mpeg2 1920x1080 25 Mbps.

Actually in "the good old days" (Vegas 8,9 etc) in the forum we used to help each other finding the sweet spot for Dynamic Ram for rendering every time a new Vegas version was released as the peak was rather narrow and mostly was around some 130 MB - but could move a little up or down from version to version - as far as I remember 🙂

Edit: With this knowledge it is not a good idea to set Dynamic RAM to 0 in order to improve stability - as it - in some cases, at least - significantly slows down the render time.

On my machine nothing but the default 200 works.

OldSmoke wrote on 4/10/2018, 11:04 AM

Tried OldSmokes suggestions on some 3840x2160x12 AVC

On my system it made a big difference specifically with XAVC-I footage, that is XAVC-S from my a6300 & AX700 converted via Catalyst Browse to XAVC-I.

Kinvermark wrote on 4/10/2018, 8:34 PM

FYI, I gave the above settings a try in V15, but couldn't detect any obvious improvement using gh5 video and stills.

OldSmoke wrote on 4/10/2018, 8:58 PM

You could try and convert one or two GH5 files with Catalyst Browse to XAVC-I and see how that does.

Kinvermark wrote on 4/10/2018, 9:24 PM

If you REALLY REALLY want me to do this, I can, but I don't have Catalyst browse installed anymore and don't have a pressing need / desire to convert GH5 files for my own workflow. Someone else perhaps? :)

fr0sty wrote on 4/10/2018, 10:42 PM

With so4compoundplug.dll enabled, GH5 video works just fine for me. I get full speed preview at preview to good quality (depending on fx used), but the system then gets plagued by stability issues and render bugs. With if off, I still get ok performance on the 100mbps 8 bit 4K codec, but the 10bit codecs don't work at all without rewrapping the video as an MXF file, and the performance is terrible vs. with so4 enabled.