Comments

Behringer X-Touch series external controller support. I have an X-Touch One and can't figure out a way to get the automation controls to work with the interface using Mackie Control Emulated. Works fine in Reaper.

I just want to see Vegas without bugs. I am waiting almost 10 years. :( 
Please, do not implement new functions until the software will be stable!

I just want to see Vegas without bugs. I am waiting almost 10 years. :( 
Please, do not implement new functions until the software will be stable!

I am with you, but I think this will never happen, because of the real world and universal PC platform. :( Until there will be a certified machine, cameras, codecs... You have to find your way... Every year there is a new technology needed to implement from hardware manufacturers, OS manufacturer, camera manufacturers, etc... Take your hardware and try if any other software is more stable with your setup... I have found myself that there is no such big difference. I am now running VP16 almost stable, but it depends on the project I am working on. For example, I am working with Sony XAVC most the time, but I have issues with the new 10bit 4K DJI Mavic Pro 2 – I am not able to open files from the one-day session in one Vegas project, it's very frustrating. I have i7-8700 CPU, 32 GB RAM, 4GB Radeon RX580...

I just want to see Vegas without bugs. I am waiting almost 10 years. :( 
Please, do not implement new functions until the software will be stable!

Almost all stability problems, I face are GPU related. When I disable GPU support, Vegas is solid as a rock but also that slow.

1. @3POINT maybe it's your iGPU that's the issue. Have you tried disabling that and not your GPU?

What is iGPU?

I'd like to suggest that Vegas 17 at least notify you that another instance of the file is open when double-clicking on a .VEG file. Sometimes I forget a project is open when I double-click on the file and start working on it. The changes from the first instance may not have been saved.

My wishes:

- Option to automatically do Studio RGB => Computer RGB for preview window only. I know about possibility to add Levels to Output FX and or use SemW extension. Unfortunately, they require constant switching on/off as scopes are affected. I'm waiting this for years already :(

- Bigger/scale-able Color Curves (I'm aware about Color Grade panel, but see below)

- Bigger/scale-able circles in Color Corrections (I'm aware about Color Grade panel, but see below)

- Possibility to un-dock Color Grade panel (preview window becoming too small when the panel is ON)

- GPU accelerated decoding for AMD GPU

- Speed up stabilization plugin (it is much slower in my system then Mercalli v4)

Nest sequences or multiple timelines.I wish that vegas will be more stable and userfriendly.

You can already Nest sequences and have been able to since well before Magix took over. Just drag a .Veg file onto a new timline and it will be nested.

The great thing about Vegas is that it lets you do this and have multiple instances of the program open because you really don't want

Sequence tabs

Nested sequences or multiple timelines is like premiere, you can see several timeline in one UI, not like vegas' nested project just can see one project int one UI.

Nested sequences or multiple timelines is like premiere, you can see several timeline in one UI,.....

@lan-mLMC - O...K...

... not like vegas' nested project just can see one project int one UI.

@lan-mLMC - What do you mean?

Hi friends,

I read some of this thread and I appologize if these ideas might have been expressed before - I write before I read it all to make sure I don't forget my ideas :) Also, if these does not sound exactly tehcnical or even reasonable smart, just put it on my short experience with Vegas. :) And there might be some workarounds that I don't know about, so feel free to mention them.

1. Stability for GPU usage. Indeed, as someone else said it, when no GPU enabled, Vegas is rock solid for me too. So, maybe try to organize/wrap the GPU activity under a separate process, so that even if something goes wrong with it, will not kill Vegas all together. I don't even know if this would be possible...

2. Allowing more custom keys options. For instance, I would love to be able to press lets say Shift and Select with the mouse in order to mark multiple clips and then drag them where I need, rather than pressing D twice, select, drag then again press D twice. Or, when using ripple, instead of changing the mode, rather have the function assigned to a key and to work only while that key is pressed down, when release it, it goes back in no-ripple.

3. I miss a plugin that would do progressive defocus.

4. An updated text editor, with some 3D abilities.

5. A way to export transitions for instance as a whole unit, so anyone else could insert it in a new project, elsewhere in the world, and have it functional. I must say, I am not sure maybe this is possible with nesting tracks in VP17, but definitely when it comes for Lower Thirds for instance, would be nice to just be able to insert and customize, rather then create them each time.

6. Please - customizable size for icons - or if not possible, just make them a little bit bigger, not by much, but some what larger. And then customizable UI colors would be sooo nice!

7. I would like to have the edges of events/clips a little bit better marked. This is huge (for me) as very often when I try to edit two events next to each other. When clicking the back edge in order to trim the event A, I grab instead the front edge of clip B. I noticed this happened quite often when I need to do Shift+Click and drag, it moves the cursor to the next clip's edge... Anyway, please bear with me. Problem is the edges are not well defined in my oppinion and they could do with better snapping. So, for instance, when you are close to the edge, just have the mouse snap either to the end of clip A - if the mouse comes from the left, or to the beginning of clip B - if the mouse comes from the right. I hope it makes sense what I am saying here, it does in my mind...:)

8. Smoother results on the velocity curves. I cannot explain it well, but this could do with nicer results.

9. Improved stabilization, in the sense that it should be reliable - to me, quite often when I re-open a project where I used stabilization for media in the previous edit, it is not there at all or it is broken. The media clip had the plugin on it, but the settings are grayed out and the only solution is to delete it and re-apply stabilization. But this means that you need to go through may clips and only stabilize them in the lest session, before rendering, otherwise you cannot be sure the final product is not compromised.

10. Please add a de-noiser plugin, even if basic. Of course I am talking about video noise. I tried Median, but does not work really. A proper de-noise would be needed, in a Pro version of any NLE. Vegas could do with one!

11. Wound be very useful if the plug-in pop-up windows would adapt its dimensions dynamically according to the plug-in that is open. That would save time and energy avoiding the need to adjust the window's edges in order to be able to see and use the controls.

12. Please fix the render window to not hide anymore behind the main Vegas window. When first happened I was very confused what was going on. And it still does.

13. Add a kind of Inspector window, similar to Color Grade window in VP17.

14. Please make a shortcut command for Normalize function for audio events.

15. Please upgrade the transitions and effects, as they are for many many versions the same. Basically, they are pretty much all at version 1.0.0 and definitely they would need some modern feel, look and functions.

I am sorry this became a huge list. :) I might have broken some rules maybe, like only two-three items to propose, or something. Sorry for that. But this would be my list of proposals.......

You all have a great day guys!

Adi

 

1. Stability for GPU usage. Indeed, as someone else said it, when no GPU enabled, Vegas is rock solid for me too. So, maybe try to organize/wrap the GPU activity under a separate process, so that even if something goes wrong with it, will not kill Vegas alltogether. I don't even know if this would be possible...

Related to that, Give vegas an ability to check plugins to see if they will cause problems. Davinci Resolve does that with this message on startup

It is helpful because if you do choose to enable and then your software crashes you can start troubleshooting the plugins. Currently with vegas (as far as I know) you just have to guess it's a plugin problem

@Former user ... that is such a great suggestion.

Hi! It would be great to add a feature of changing individual clip colors on the timeline and also to change marker and regions colors.

I know it's a long-time-ago requested feature but it is VERY important.

Most editors nowadays (even beginners) use a tremendous amount of footage from different sources, so it would be very handy to categorize it on the timeline in addition to bins and folders.

Color labeling and ratings would give so much flexibility that it can't be ignored in 2020.

I hope my request would be heard and implemented in the upcoming updates.

Thanks!

Related to that, Give vegas an ability to check plugins to see if they will cause problems. Davinci Resolve does that with this message on startup

It is helpful because if you do choose to enable and then your software crashes you can start troubleshooting the plugins. Currently with vegas (as far as I know) you just have to guess it's a plugin problem

I like this idea too. I've had VP stop when loading FX plugins and when the Error window would open, I would check to see what caused the problem. For me, it was the Ignite Pro 4 plugins.

The fix for me was to remove them from the OFX Plugin folder, restart VP, and then exit the software. THEN, put the Ignite Pro plugins back into the folder, restart VP again, and all is well.

But to have the software full load and then tell you there is a plugin issue and which plugin is the offender would be great!

Memory usage (or lack there of) needs to be addressed. Vegas will use 20 gigs of page file and only 1 gig out of my 16 of physical ram? Additionally importing large amounts of media 99% of the time results in a crash. Why cant I import 60 gigs of footage at once like I can in resolve or cyberlink with 0 issues? SFK files seem culprit during creation. We need a new import function.

Additionally higher speed ramping without the need for velocity envelopes.