VEGAS Pro 15 Update 5 (build 361) - General Discussion

gary-rebholz wrote on 5/31/2018, 4:34 PM

My question is; why did no one acknowledge all these bugs and problems. Sometime just admitting that there is a problem helps users work around it.

Of course, I'm very glad to hear things are working better for you now and that you will stick with VEGAS Pro. And I appreciate the way you started your post out with a thank you. You all may not realize just how far that simple thing goes toward making the developers feel as though their efforts really mean something.

Frankly, though, I do take exception each time someone on these pages implies that one of my teammates--whether a developer, a support person, or anyone else--is purposely trying to deceive you or anyone else. It just doesn't happen. I stand behind every member of this team as a person of high integrity who only wants to make the best software they can and help you customers as best they can.

The nature of fixing bugs is that the hard part isn't necessarily fixing them, it's often finding them. So it may seem to you that we knew about a specific bug and were keeping information from you, while in reality that is not the case at all. Sure, we knew there were bugs, but we didn't know what they were. They did not affect all users alike, and this is most certainly why the tech support crew was investigating your specific system. They weren't trying to pretend it was unique to you, or that it was somehow your fault. They were simply trying to get to the bottom of the problem and to find commonality between your system and the systems of others reporting similar problems.

I have tried to be as forthright as possible about the problems we have had and still have. I agree that it serves no one for me or any of us to pretend that nothing is wrong. I don't feel like it's fair to say we didn't acknowledge that there were (and still are) problems. We're just trying to work with you to find the solutions.

We shifted team focus heavily toward fixing the things we fixed in Update 5 once we realized how serious some of these were for many of you. It's an understatement to say that we're glad our fixes seem to have helped. We wish you hadn't had to endure that frustration, and we're thankful that you did. It means a lot to us to know that our tool is so highly valued that you will stick with us through difficult times like that. It makes all of us want to do even better work for you.

Steve_Rhoden wrote on 5/31/2018, 5:33 PM

Speaking of upcoming Vegas Pro 16, just having 8k resolution support or beyond and VST3 support....would be ALL i would ever want at this point, lol

sassabrass wrote on 5/31/2018, 6:19 PM

I have been a Vegas user since way-back-when, and have followed and used all the iterations. 11 and 12 and 13 were pretty stable and I got a lot of work done. I skipped 14 because it looked like a repainted 13, but was excited about 15. Well...... I like some of the new handling features, and I hear 4K is better, but I can't get past the crashes, even with the reinstall in an Admin account as Magix suggested, nor the new 361 update. I had a simple 4 minute project with 4 tracks of 1080 video and four audio, barely any plugins, and it took me four days to complete it! Importing media would crash 60% of the time; clicking the cursor ANYWHERE would crash 30% of the time; rendering would stop part way in and crash 25% of the time, etc.... it took 27 resaves and almost as many restarts/reboots to get 4 mins of output. This was a fresh project, too, no prior version imported. I disabled GPU acceleration which reduced the crashed by 20%, but that can't be the final answer.

On top of it all, when I'd go to render it, the my favorite template Magix AVC/AAC Mp4 would only appear 50% of the time (no filters on), and required a reboot. Magix Pro Rez always showed up, but sometimes other templates would (and still do) go missing. Also, in options I have Recently Used Projects List ticked, but there is no such thing in the dashboard.

I keep sending the auto crash reports with added info, but don't know if they are being looked at. I still have to use another version of Vegas on my other workstations because I know I can get it done easily. BTW, I totally uninstalled my prior version on this dedicated editing box, cleaned the registry, installed in Admin mode (twice), and am not running browsers etc in the background. So, who can tell me a fix?

I should also add that I save Control>S after every move out of necessity, and that is the only way I make any progress at all, BUT after a crash (with a freshly saved file), it prompts me/asks me to load the Auto Saved Project. If I do, some old project comes up from back down the line. AND. when I go to render, it never shows the render-to folder that I have been using, associated with the project.... I'm really frustrated. Three crashes during rendering a 3 minute file in the last 20 minutes....

Cliff Etzel wrote on 5/31/2018, 6:34 PM

@sassabrass since you don't list your hardware specs in your profile - there's no way to even begin discussing what troubleshooting help those here on the forum might be able to provide. I've had the opposite experience that you have had - Vegas 15 v361 build has been the most solid running version I've ever used - and that's not an understatement. I've tested with several projects, 6-8 tracks of video, stills titles audio, etc... I've tested with 1080p and 4K footage from the GH5, native MOV's, MP4's, Cineform AVI's, XAVC-I, XAVC-L, XAVC-S transcoded from Catalyst - Vegas 15 v361 doesn't miss a beat - in fact the bottleneck on my desktop machine is either using Neat Video (Drops to a paltry 5fps in draft mode) and the eSata raid0 I've been using for the past few years. Once I get some internal SSD's large enough to set up an internal Raid0 (in preparation for moving to 4K later this year), I'm sure that I'll experience even better stability and performance.

What I'm not doing is using QSV for anything and I'm still using an old nVidia GTX660ti 2GB card.

francis-leitner wrote on 5/31/2018, 6:36 PM

My Vegas 15 was working fine until I updated it with this update, now it is crashing all the time

sassabrass wrote on 5/31/2018, 6:42 PM

I have a fairly fresh Win 10 on a core i7 Media HP, NVidia GForce GT, with 25Gb free space on an internal Solid State drive. All my other Vegas versions were fine...

Cliff Etzel wrote on 5/31/2018, 6:51 PM

I have a fairly fresh Win 10 on a core i7 Media HP, NVidia GForce GT, with 25Gb free space on an internal Solid State drive. All my other Vegas versions were fine...

Version 15 seems to be more particular about hardware - as I stated in my last response - you haven't listed the details of your hardware. I had instability with my old x58 hardware (Hex core Xeon, 24GB matched GSkill RAM, same GPU I'm using now in my current hardware specs) - as soon as I updated my hardware (i8700k, 32GB RAM, ASUS Z370-H motherboard) - it got better, but still not completely stable - version v361 fixed basically all my stability issues. My OS/Apps 240GB SSD drive has over 150GB free...

The more details you provide about your specific hardware configuration the better those of us here can help.

francis-leitner wrote on 5/31/2018, 6:53 PM

Have used Vegas since version 1. Vegas 15 was working fine for months.. no crashing at all. updated today and it started quitting on me. Have core i7 4.2 ghz- Gforce GTX 1080 138 G free on SSD drive

sassabrass wrote on 5/31/2018, 6:56 PM

Damn! One step forward, two steps back. If my box was compatible with 11, 12, 13, it should be fine with 15!

fr0sty wrote on 5/31/2018, 9:35 PM

Not if new features have been added that may be conflicting with your drivers or something like that... I've had similar headaches resolved with something as easy as a GPU driver update or rollback. Give us your hardware setup, driver versions you have installed for your GPU included, then give us the format info for the media you have on your timeline (resolution, framerate, codec) and we can go from there trying to isolate what is causing this.

Cliff Etzel wrote on 5/31/2018, 10:08 PM

Not if new features have been added that may be conflicting with your drivers or something like that... I've had similar headaches resolved with something as easy as a GPU driver update or rollback. Give us your hardware setup, driver versions you have installed for your GPU included, then give us the format info for the media you have on your timeline (resolution, framerate, codec) and we can go from there trying to isolate what is causing this.

More or less what I said... 😉

david-ruby wrote on 6/1/2018, 8:43 AM

XaVC-s (mp4) still see something as simple as a fade between clips freezing between the transitions. Not smooth. It seems random when happens though. Any one else?

Is there anyone else seeing this? Hoping I am not alone here. : )

I am bumping this along as it is really a headache to see this performance issue in front of a client. : (

Again the footage is from a sony a7s camera shot in xavc-s 24p 50

XaVC-s (mp4) still see something as simple as a fade between clips freezing between the transitions. Not smooth. It seems random when happens though. Any one else?

Is there anyone else seeing this? Hoping I am not alone here. : )

I can edit in Premiere no problem but love the vegas platform for creativity. Thoughts from the team?

MH7 wrote on 6/1/2018, 9:32 AM

I haven’t updated to this recent build 361 yet. I’m currently on build 321 and it’s been working fine for me (I hope build 361 keeps things that way). It’s nice to see AMD GPUs getting some attention as I have an RX 580 from Gigabyte in my rig (see my signature for full system specs). I see that my good friend @Reyfox has had some speedy renders with this build because of this added support.

The overall consensus seems be that most are finding this recent update quite stable, in fact, the most stable in quite a while. That’s great to hear. I hope my mileage will be the same if not better. I do want to thank Gary and his team for such a stable update and the couple of added features. I think I can speak for most of us when I say the we’re appreciative of your dev teams efforts.

I know that it’s taken you guys a while to get to this point, because of the whole transition and everything associated with that, so it’s nice to know that VEGAS has improved greatly because of the feedback obtained from this community.

Whilst others might want to think that you guys don’t listen to the problems many have faced here with VEGAS, it’s quite evident that you obviously do, especially with this recent update.

So, from all of us I’d like to say a big - thank you! And keep up the excellent work!

Cliff Etzel wrote on 6/1/2018, 10:54 AM

XaVC-s (mp4) still see something as simple as a fade between clips freezing between the transitions. Not smooth. It seems random when happens though. Any one else?

Is there anyone else seeing this? Hoping I am not alone here. : )

I am bumping this along as it is really a headache to see this performance issue in front of a client. : (

Again the footage is from a sony a7s camera shot in xavc-s 24p 50

XaVC-s (mp4) still see something as simple as a fade between clips freezing between the transitions. Not smooth. It seems random when happens though. Any one else?

Is there anyone else seeing this? Hoping I am not alone here. : )

I can edit in Premiere no problem but love the vegas platform for creativity. Thoughts from the team?

XAVC-S is pretty compressed and requires quite a bit of resources to play back smoothly. I too experience lagging frames with dissolves/title motion graphics generated in Vegas. I've just come to accept that it's an area Vegas isn't as smooth with right now. Having used Premiere Pro CS6 for a long time, I learned that dissolve transitions are GPU accelerated so it can appear Premiere handles XAVC-S better. The trade off as I see it is the slow editing experience, the software rental scheme as well as the ongoing issues when an update is released. Example: I learned that if you want to use a "legacy" gpu as Adobe puts it - you can't (GTX400, 500 & 600 series). You have to roll back to PPro CC2015.2 - and those who use Premiere and read the lamenting of MAC users and the ongoing performance issues compared to Windows users.

Add to that the not fixed to date known bug of project file corruption and backups being corrupted as well, that's a huge issue IMO as Premiere Project files are basically XML's - and I have a couple of project files that are close to 17MB in size - can you imagine a 17MB text file? Then look at the amount of system resources Premiere uses just sitting there... on a 16GB rig, it will utilize close to 50% of available ram - that's before you start pushing pixels around. There's a reason custom builders advise a minimum of 32GB RAM and a higher end GPU.

Vegas is more efficient on system resources and the updates/additions within Vegas 15 (especially the latest v361 build) are what converted me back to Vegas after years of instability for me. It's not perfect - no one NLE is.

It's a matter of picking the NLE that best suits your needs.

Cliff Etzel wrote on 6/1/2018, 2:52 PM

Nothing pleases me more than to see Vegas 15 peg my CPU at 100% and my GPU seeing as much as 25% utilization during renders - unlike Premiere Pro CS6 that hardly utilized more than 20% of my CPU and maybe 7% GPU for renders... Says alot about how well MAGIX developers are tweaking the code in Vegas 15 to improve render performance - and I'm not even using NVENC (I'm still using the Mainconcept MP4 template)

HEADMASTER wrote on 6/1/2018, 6:59 PM

With this build 361, I get 1 plus more FPS than other versions in preview window. See my benchmarks on the link:

https://www.vegascreativesoftware.info/us/forum/my-own-benchmarks-i-will-update-in-future--111652/

andoe wrote on 6/2/2018, 12:35 AM

This build is useless as the video lags 1-2 seconds behind the audio for most of the NVIDIA Experience/Shadowplay encoded clips that I import (in the preview and also in the final rendering). It basically shows different frames from what it is supposed to show, but the audio is still correct, so it appears out of sync. It was not like this in my previous version (build 261) so I'm reverting.

Edit: I tested other builds and the problem exists since build 311, and in the two builds since then.

NickHope wrote on 6/2/2018, 12:49 AM

XaVC-s (mp4) still see something as simple as a fade between clips freezing between the transitions. Not smooth. It seems random when happens though. Any one else?

Is there anyone else seeing this? Hoping I am not alone here. : )

I am bumping this along as it is really a headache to see this performance issue in front of a client. : (

Again the footage is from a sony a7s camera shot in xavc-s 24p 50

XaVC-s (mp4) still see something as simple as a fade between clips freezing between the transitions. Not smooth. It seems random when happens though. Any one else?

Is there anyone else seeing this? Hoping I am not alone here. : )

I can edit in Premiere no problem but love the vegas platform for creativity. Thoughts from the team?

@david-ruby Is it any better with so3compoundplug disabled?

NickHope wrote on 6/2/2018, 12:56 AM

This build is useless as the video lags 1-2 seconds behind the audio for most of the NVIDIA Experience/Shadowplay encoded clips that I import (in the preview and also in the final rendering). It basically shows different frames from what it is supposed to show, but the audio is still correct, so it appears out of sync. It was not like this in the previous version so I'm reverting.

@andoe Can you share a sample file with this problem (e.g. on Dropbox, Google Drive, OneDrive, mega.nz, wetransfer.com or mediafire.com) for others to test? I could also link the developers to it to take a look.

andoe wrote on 6/2/2018, 1:19 AM

@Nick Hope I managed to fix it. In the clip properties I noticed that the files were being read with the so4compoundplug FileIO Plug-In. So I replaced the files in the Vegas Pro 15.0\FileIO Plug-Ins\so4compoundplug folder with the ones from the last build that was still showing the Shadowplay files in sync properly (build 261) and now everything works perfectly again! Basically, I'm now using build 361 with an outdated (but working) plugin.

ColdHardDrewth wrote on 6/2/2018, 3:35 AM

THANK YOU! This is so great, beautiful, and incredible! I'm so glad I upgraded from Studio to Pro. The only bug I seem to have is definitely an annoying one... When you go to "file, add media," the search function doesn't work. I'm not sure if this is a Windows 10 issue or a Vegas 15 but I'm certain it wasn't happening in the past. Often when I go to add a file I want to search for it or start typing the first letter but that does nothing now :(

Pursuit-Perfect-System wrote on 6/2/2018, 3:38 AM

new build is still crashing time and time again for me

NickHope wrote on 6/2/2018, 5:29 AM

THANK YOU! This is so great, beautiful, and incredible! I'm so glad I upgraded from Studio to Pro. The only bug I seem to have is definitely an annoying one... When you go to "file, add media," the search function doesn't work. I'm not sure if this is a Windows 10 issue or a Vegas 15 but I'm certain it wasn't happening in the past. Often when I go to add a file I want to search for it or start typing the first letter but that does nothing now :(

Still working for me in VP15 build 361 with my out-of-date Windows 10 version 1511.

Peter_P wrote on 6/2/2018, 6:57 AM

Still working for me in VP15 build 361 with my out-of-date Windows 10 version 1511.

Same here with Vp15 B361 and Windows pro 10 / 1709.