I agree. We get it, you love resolve. I love it too, it's cool software. It does some cool tricks and it does them cheap, or free if you buy one of BM's excellent cameras. However, it does have some compatibility issues with certain formats, it too can crash once in a while, I have to have special hardware to get full screen previews, and it can only render to a limited number of formats. Sometimes I also feel like I have to go around my bum to get to my elbow, on tasks that take me no time at all in Vegas. So, we all have our reasons for sticking around. We don't know what Magix has been up to with Vegas. I don't expect 16 to come dethrone Resolve at color any time soon, but if it can do it good enough, I'm willing to give it a shot, especially if it can do what resolve cannot do... deliver a file with HDR metadata encoded and ready to play.

If Vegas pulls that off, I may still round trip to Resolve to get certain things done, but I will be able to bring it right back into Vegas to encode and deliver. Who knows, maybe Magix will surprise us all with some super awesome color tools that really do best Resolve at its own game, I don't expect to see that happen on launch day, but I know Magix wants to stay relevant in the market as well, so we should give them the chance to prove themselves. They've only got one full version behind them, let's see where they go from here. No sense in hating on them before they've even revealed what they are up to.

All I'd want in 16 is faster rendering, more stability (less crashes), even better chroma key, and more cooperation with .mov files. I wish they'd build in something to make it so I don't need old, outdated Quicktime software. Also we should be able to import .m4a files (as all my music is) without having to convert to .mp3 first. I just like convenience and reliability... I do an interview series and the people often send me stupid .mov files and such because they are shooting on iphone or ipad and it makes me so sick eww.

Hi, well, I would say that .mov files have not been extremely problematic, lately anyway, I think it depends on the underlying codec, as .mov, like .avi, is a wrapper.....but with a good quicktime version, you should be mostly ok. Try different QT s --- maybe check here or on Creative Cow to find the better one.

I personally think pointing out a software's failings, issues, problems is a good thing when done constructively. Comparing it to the competition also is good. I don't think for one moment that the developers of Vegas are not keenly aware of what Resolve offers for free, and what Media Composer and Adobe are doing. They have to know to remain competitive and to offer a viable working solution for those out there to even consider buying Vegas. Vegas is charging "pro" prices for the software, so the comparison is inevitable, pointing out the differences. We all have our own "needs" in editing and preferences in what we think Vegas should include. That doesn't nullify what others may think, it's just different needs and they are pointed out in the public forum.

If what is posted is false, then that should be pointed out. I know that I am willing to be corrected if what I post is incorrect. I am an adult and have long given up on the ego and emotion and "listen" to what is being said. Even if I do not agree, is there some truth in what is being said?

I know for me personally to be better at whatever I do, I want criticism and seek it out. Without it, I will continue on not really knowing how I can improve. Yes, it can hurt, but I have to ask myself if there is some truth in what is said, not how it's said.

I am new to Vegas and have no real background with it like many here, but have been editing since a/b roll with the Amiga/Toaster. I've used many different NLE software over the years. I bought the humble bundle VP14Edit for $20. I never ever considered Vegas.. the interface was just too ugly for me (yeah, a poor reason not to try it). For $20, I figured why not. I got "hooked" right away with the timeline editing (and am still learning) and how fast it was. I was hooked so much so that I bought the upgrade to VP15 Suite, told my other editing friends about it, and look forward to see what VP16 has to offer. I, like many of you have Resolve and other editing tools out there, so some comparison is to be expected. This in wanting to see Vegas improve. Constructive criticism and comparison should be welcomed, not discouraged, not squelched. This would stop people from posting legitimate issues/comparisons/opinions, and only creates a "safe space" where no disagreement can happen.

Are there problems with VP? Yes. Timeline playback is a big one for me to give an example. There are others, but I hope no one uses personal adjectives to describe me and my issues with the software with their replies. Correct me if I am wrong and show me.

My number one requests for Vegas 16 is 8K & beyond support, VST3 support and far better stability (During installation and usage).... Little gimmicky features added here and there wont really cut it.

My number one requests for Vegas 16 is 8K & beyond support, VST3 support and far better stability (During installation and usage).... Little gimmicky features added here and there wont really cut it.

Right. A subscription model - allowing that it would be a reasonable price - actually favors the company focusing on stability issues and not creating new "bells and whistles" to attract steady stream of new customers. NOW ...before some became reactionary, VEGAS has wisely offered that as an OPTION, not a must ...so you have the best of both.

Also If by a subscription you can also get new subscribers who otherwise could not afford Vegas, you can cut down on the pirating of the software as well.

If your team is well financed, they can hire more and better developers to apply the sort of muscle required to right the ship, so to speak. I believe this new alliance with Magix, a company i know well and admire, can make this possibility a reality, but we need to give it a bit more time and ENCOURAGEMENT... if you can't read frustration and disheartening in the comments of Mr. Rebholz, you're not paying attention. Probably a small and dedicated dev team trying to keep up with quite a few issues and it's probably quite daunting. So, let's try to be supportive and not just cranks, not talking about anyone here in particular, but we've seen that sort of commentary, and it really is not that helpful, at the end of the day.

Vegas needs better hardware acceleration. Even a few animated text layers can make the playback stutter while CPU is at 30% and GPU 2%. It's just isn't optimized. With Premiere I can do way more animations and add more color effects+masking and it works smoothly on the same PC. We need a stable more optimized Vegas. Don't waste money on features until the program can't utilize the PC's resources properly.

My PC: Ryzen 1700x, GTX 1080, 1 TB Samsung Pro m.2 SSD, 32 GB RAM.

The only feature I would like to see is multi timeline editing and nesting - without Vegasaur and crashes.

Until there are old bugs like deleting an event during playback crashes the program if ripple delete is on they shouldn't add more features. You can't build stable new features on an unstable program. Playback's framerate drops at every new video event, too...

Vegas is my favorite NLE but it has its drawbacks and I think if all the money would be spent on stabilizing and optimizing the program to use the PC's full potential would be a better step. I can buy even NASA's supercomputer, if Vegas can't use the hardware properly the playback will stutter.

I bought a very expensive PC for video editing and recently I couldn't afford to play with Vegas so I edited in Premiere - which has a very dumb editing style next to Vegas but it's still waaay more optimized and at least it uses every resources it's given properly.

I hope I won't be disappointed when Vegas 16 comes out. :)

This would stop people from posting legitimate issues/comparisons/opinions, and only creates a "safe space" where no disagreement can happen.

I agree with that, criticism should be welcomed at any company that want to improve their product.

I feel Vegas has its place along other NLE. Recently I am editing a music heavy feature film in Vegas. no major showstoppers except few.

The biggest problem I face is that there is no communication between Magix own software I have also noticed that different software dev/departments are not aware of the other limits and issues and appear to be not to eager to look into and collaborate in solving the issues. Yes I mean sharing timelines between Samplitude and Vegas including plugins.

Before 16 I would love some major bugs that I have reported to be fixed so that I can finish the project in 15 before moving on to 16. Its not safe to upgrade in between projects.

Please Magix Fix the bugs in 15.

And Please Dont stop development and updates for 15

 

The biggest problem I face is that there is no communication between Magix own software I have also noticed that different software dev/departments are not aware of the other limits and issues and appear to be not to eager to look into and collaborate in solving the issues. Yes I mean sharing timelines between Samplitude and Vegas including plugins.

Hell to the yes, BUT, easier said than done, and that is why I appeal for lobbying, but also patience. There is a great link inside Vegas for ANY 3rd party audio in a built in round trip protocol that works seemlessly, (with Samp at least, I've done it with no others), it is great, but not as good, as you suggest, as Samplitude shared timeline. Resource wise, it is not that great to play a lot of audio and audio plugs and VSTi's while doing video edits anyway, but that somewhat depends on the complexity of your video or audio, whatever the case may be. I use both programs, I'll use one or the other as a guide, edit video and audio discretely in both programs, then import audio into Vegas. So far, so good.

That said, the way Samplitude presents editing on its timeline, GUI and Event editing (called objects in Samp) is brilliant and THAT should be incorporated into Vegas, ASAP, without disruption of Vegas norms, at least fundamentally, and THAT IS DOABLE, I am convinced, as I am intimately familiar with both and both programs are foundationally audio editors.

I have often dreamed of integration with ACID PRO. Seems unlikely, but probable more likely than Samplitude.

You can use Acid as a third party editor from within Vegas, have you tried that? Should work like a charm.

Go to Options/preferences/audio and in the browse window for "preferred audio editor" just browse to Acid Program.

Before 16 I would love some major bugs that I have reported to be fixed so that I can finish the project in 15 before moving on to 16. Its not safe to upgrade in between projects.

Please Magix Fix the bugs in 15.

You are dreaming :)

You can use Acid as a third party editor from within Vegas, have you tried that? Should work like a charm.

Go to Options/preferences/audio and in the browse window for "preferred audio editor" just browse to Acid Program.

I used Sound Forge as an audio editor in VEGAS Pro. After Editing and saving the Audio File in Sound Forge, the file did not automatically update in VEGAS on the Timeline. I had to remove it and then drag it back there.

---

I'd like if they would implement support (or at least put in a Template Set, similar to ProRes) for Grass Valley HQ and HQX in VEGAS Pro 16. I've been using HQ/HQX via their Official CODEC (which is a Native Windows CODEC that uses the AVI Container) and it performs much better than ProRes. I'm getting 12-15 FPS higher playback on 4K Video on my machine; using HQX with the SuperFine CODEC setting vs. ProRes 422.

I am seeing similar disparities at 1080p 60 FPS, as well. The HQX will play back at 58-60FPS, while the ProRes plays back at 35-38 FPS.

The CPU load is also lower, and renders from HQ/HQX to H.264/HEVC are faster.

Since this CODEC is supported by most other Pro Video Applications (Resolve, Premiere Pro, and I'm pretty sure Media Composer supports it), it would be nice if they at least put in the Templates; even if we have to install the CODEC ourselves (which is trivial).

The ProRes support is nice, but it performs worse at lower quality settings and bitrates than HQ/HQX does on Windows machines in practically everything I've tried. Even Vegas Movie Studio will edit 4K HQX better than VEGAS Pro using ProRes, since it just uses the Encoder/Decoder installed on the system (which may be Hardware Accelerated, I'm not sure).

Why not saving your own GV HQX template set? It's done in a minute. I use such HQX render presets in Vegas Pro for many years now.

The GV codecs are great - but only if one uses 8bit in Vegas since they are decoded as 8bit in Vegas only. But I love them too - in Edius.

For Vegas Cineform, ProRes or XAVC-I are better if one uses 10bit.

Ahaha, just bought Vegas 15 1 month ago :D. i didn't see this one coming lol... hope the upgrade will not be "too high"...

They have upgrade deals going to get 16 free if you just bought 15, so I'd hit up Magix if you did.

They have upgrade deals going to get 16 free if you just bought 15, so I'd hit up Magix if you did.

I bought it on 4th june, you think it can work ?

Hope this doesn't get too buried but I'm reluctant to start a new thread on the same topic. So what I'm keenly interested to know is if Magix Vegas 15 Suite will install side by side with Magix Vegas 14 Suite component for component. In other words, I'm sure V15 will side x side with V14 but I'm very reluctant to throw away DvD Architect 6 in favor of 7 until I know NO feature I use in 6 has been eliminated. Ditto for NewBlue and Hitfilm components. I want to preserve each Vegas environment in its functioning state; I realize that this is going to mean categorizing projects by Vegas version in all probability but that's a small price to pay for being able to go back weeks later in the face of a new environment to an old project and pick up where you left off.

Most stuff in V14 suite works in 15, except for Mercalli.

@FilmsvDigital - Yes they are all separate installations so can sit side by side. Some users have several versions of Vegas and DVDA installed. Some things are possibly common though such as your favourite render templates. Also there's no guarantee that TP plugins might not get confused.

I found that when the video capture ceased to work, it was crocked for both vp14 and vp15, so there must be some commonality here. It had worked aok in both versions before going down. When I get vp16 it might start working again.