Here are some of them:
1. When trying to write a video onto a file that's in read-only, there's no "Try again" option; it just fails and the user has to start all over again.

User error, don't try to render to a file that's read only.

2. After a failed render or after another edit, the name of the file previously entered is gone and the user has to enter it again.

Oh dear, is it that hard to copy paste.... Why the failed render..? User error, poor hardware ?

3. Clicking "Close program" by mistake and then clicking the window’s X (expecting to cancel) closes the application anyway. This is diabolical.

User error, don't click "Close program" by mistake.

4. Exporting with custom frame dimensions requires far too many clicks. Simply enable the Width and Height fields by default and, when you enter a number, it automatically jumps the "Frame size:" field to (Custom frame size).

I guess you want it to read your mind.

5. What in god's name is going on when you're using the mouse-wheel to zoom out of the video preview? The camera position jumps all over the place.

No problem here, (9:16 is awkward tho)

6. Handling video clips that are on top of each other is quite frustrating. If two clips are on top of each other the "fx" and "..." menus for one of the tracks often just disappear and it's impossible to select the clip underneath.

Why do you put videos on top of each other? There's an option called Takes.

7. Many UI elements that adjust rectangles (masking, pan/crop, event position) resize symmetrically around a center point instead of just moving the edge selected. This makes applying a mask (or any other action involving this UI) very cumbersome. The UI to adjust the clip position in the Video Event FX UI... I don't even know.

Picture in Picture, masking & Pan/Crop will resize around the centre, grab the corner points or highlight the 'Size About Centre' in Pan/Crop.

8. This is a big one: The mouse-wheel zooms in on the timeline at the playback position instead of the mouse-cursor. This is one of the most infuriating things about navigating Vegas Pro.

That's a positive to me not a negative, I don't want to have the timeline zoom relative to my mouse cursor, that'd be a pain having to position the mouse before zooming.

Again, this is about removing entirely unnecessary friction from the user experience without sacrificing any of Vegas Pro's power. I don't believe that these are intentional design choices, so I am wondering how some of these haven't had the necessary priority to be addressed in all the time Vegas Pro has been on the market and why its users are ok with them not being fixed.

Learn to use the software.

I apologize if this seems harsh but this is prob 'why its users are ok with them not being fixed'

Well explained @Gid 👍

User error, don't try to render to a file that's read only.

That's the most moronic take I've read in a long while.

I guess you want it to read your mind

No, I want it to not waste my time.

I guess I see the problem now and why these issues are not being fixed. Its user base is made up of elitists who take pride in being able to cope with terrible UI. Thank you for the clarification!

Thanks for sharing your feedback. I haven't seen some of these brought up before.

I find zooming and moving around the timeline with a laptop touchpad unnecessarily difficult. With a mouse it's fine but sometimes I'm on the go without one. It could use a few extra tricks like support for 3 finger scroll, etc

8. This is a big one: The mouse-wheel zooms in on the timeline at the playback position instead of the mouse-cursor. This is one of the most infuriating things about navigating Vegas Pro.

There are many aspects of the VEGAS Pro UI that I think could be improved, but I have a different view on this particular point.

During editing, an editor’s attention is primarily focused on the playhead, not on the mouse position. Because of that, zooming the timeline around the playhead feels more natural and aligned with the actual editing workflow.

In my experience, mouse-cursor–based zooming (as seen in Premiere Pro) often interrupts the editing flow.

Zooming relative to the playhead provides a more intuitive and efficient editing experience.

Dude, read the manual and learn how to use the software properly.

8. This is a big one: The mouse-wheel zooms in on the timeline at the playback position instead of the mouse-cursor. This is one of the most infuriating things about navigating Vegas Pro.

There are many aspects of the VEGAS Pro UI that I think could be improved, but I have a different view on this particular point.

During editing, an editor’s attention is primarily focused on the playhead, not on the mouse position. Because of that, zooming the timeline around the playhead feels more natural and aligned with the actual editing workflow.

In my experience, mouse-cursor–based zooming (as seen in Premiere Pro) often interrupts the editing flow.

Zooming relative to the playhead provides a more intuitive and efficient editing experience.

I disagree vehemently, which means there should at least be a toggle for this.

Dude, read the manual and learn how to use the software properly.

Another one of those. "I had to climb over barbed wire to get to school; why should the youth from today climb over anything else?"

No amount of manual reading will make any of my points invalid. Here, in case you never experienced a program with a good UI (since they are quite rare these days). Notice how in Topaz Gigapixel, it didn't take me a million clicks to choose the image dimensions.

@martin-2098

1. Vegas doesn't create read-only renders. It warns you prior to rendering if an existing render with the same should be overwritten (which is not possible when you changed manually the read only flag). What should Vegas do in that case, overwrite your read-only file or just do not overwrite?

2. Give your project a name and Vegas renders a videofile with that name, no need to rename the render when a earlier render is failed or stopped.

3. When you click "Exit" what should Vegas do, ask you again if you really want to exit? Vegas already gives you the option to save/exit/cancel when changes have been made and not saved yet.

4. I'm not sure what you mean, for me video has almost always fixed resolutions like 1920x1080 or 3840x2160.

5. As preview zooms in/out at the mouse-cursor position in the preview, this is a wanted behaviour. To return to 100% press CTRL+NUM 1.

6. Not sure what is meant, use takes as mentioned by @Gid.

7. Works for me as expected.

8. For what reason should timeline zoom in on mouse-cursor position instead of playhead position. The playhead is my position of interest and shown in the preview.

Just proves the old adage, "You can please some of the people all of the time. You can please all of the people some of the time. But you can't please all of the people all of the time".

Just proves the old adage, "You can please some of the people all of the time. You can please all of the people some of the time. But you can't please all of the people all of the time".

No, it doesn't really. Many of the design decisions or lack thereof in Vegas Pro are objectively bad. You might not care, but I do. I think that if a company charges a lot of money for a piece of software, its users are entitled to them delivering the best user experience possible.

@martin-2098

I think that if a company charges a lot of money for a piece of software, its users are entitled to them delivering the best user experience possible.

Who should decide what the best user experience is?

I've been editing since 1990 with tape onward to NLE's. Each software has a different "way" to edit using their particular UI. And while the basic functions are the same, allowing me to edit even without reading the manual, there are, as I learn and advance in using, features in the UI that I will have to learn as that is how the program is made. No two editing software are exactly the same, so learning "how to" in each one was what I had to do.

I oft see people write about if a particular software is "intuitive". "Intuitive" is based on that particular user's past experience with software they've used successfully and found easy to learn, in the past. What is "intuitive" to me, might not be to someone else. In other words, highly subjective to the individual only.

I've found using Vegas Pro to be quite easy, and by far, for the way I edit, the fastest in timeline editing. And for "me", quite "intuitive".

But I guess we all could come up with things we would like to see changed. And a lot of it would not be applicable to everyone, although some would be.

Are these intentional design choices? Yes! How else would they be there. And are Vegas users asking for them to be fixed? You can read for yourself that answer.

Now, there are feature requests that I've asked for, that to me, would enhance my editing experience, and they would be UI related. Example, a green dot on any asset used in the timeline when looking at the Project Media.

@martin-2098

1. Vegas doesn't create read-only renders. It warns you prior to rendering if an existing render with the same should be overwritten (which is not possible when you changed manually the read only flag). What should Vegas do in that case, overwrite your read-only file or just do not overwrite?

2. Give your project a name and Vegas renders a videofile with that name, no need to rename the render when a earlier render is failed or stopped.

3. When you click "Exit" what should Vegas do, ask you again if you really want to exit? Vegas already gives you the option to save/exit/cancel when changes have been made and not saved yet.

4. I'm not sure what you mean, for me video has almost always fixed resolutions like 1920x1080 or 3840x2160.

5. As preview zooms in/out at the mouse-cursor position in the preview, this is a wanted behaviour. To return to 100% press CTRL+NUM 1.

6. Not sure what is meant, use takes as mentioned by @Gid.

7. Works for me as expected.

8. For what reason should timeline zoom in on mouse-cursor position instead of playhead position. The playhead is my position of interest and shown in the preview.

1. That has nothing to do with it. Let's say you render your video, play it, realize you messed something up, then go back to fix it and go back into the Render menu. Now you have to type the file name again because Vegas doesn't remember what last you typed. You render but you forgot to close the video in the video player and now you get an export error. So, you go back into Render menu, type the file name AGAIN and export.

Every other program of the quality of Vegas would give you a "File is read-only" dialog with "Repeat" and "Cancel".

2. No, I don't want to create a project file every single time. I also may want to export a video from the project under a different name because I'm trying out a different setting.

Let's say I don't create a project. I export my video as FunnyCat.mp4. Now I do more edits and want to Render again. Instead of Untitled.mp4, the preset is still FunnyCat.mp4. How is there ANY downside to this? And this would take an engineer not more than half an hour to implement. This is the kind of lack of polish that you should never be ok with in a paid program.

3. If you click on the X in the "Do you want to save changes to XYZ?" dialog in the top-right corner, it closes the program without saving. In Every Single Other Program, the X is the same as Cancel, meaning you do not want to close the program. This is absolutely unacceptable. I lost work progress because of that.

4. There is no justification for disabling the Width: and Height: fields in the Custom Settings UI until you have Custom frame size selected. These could simply be enabled and the Frame size field would automatically jump to Custom frame size once you enter a number.

These points are so easy to concede. You could just say "Oh yea, you're right, they could improve that" and then we could have a discussion about the remaining points. But at least you didn't tell me to "Just don't make any mistakes, lol" like that moron above.

5. You seriously want to tell me this is intended behavior?

And don't tell me "Just use feature 375.4.b" to do that. No. I want the mouse-wheel zoom to work like it would in a sane program and not have to learn some cryptic key combination to do what is an extremely basic operation.

6. Takes has nothing to do with that. Have two clips on top of each other for blending purposes. Have the second clip start only a few frames after the first one. You can no longer see the fx and ... menus on the left clip. This UI element does not dock onto the end of the first clip but the beginning of the second. Even if it remains visible, it can be quite confusing and you end up having no idea where the menu for which clip is.

8. You can always just move the mouse-cursor to the position you want to zoom in on. Adjusting to this takes maybe a day and then you will realize how infinitely better it is that way. The reason you want it to zoom-in on the mouse cursor is:
-It saves you clicks.
-You can fine-tune your zoom-in position while zooming in.
-You don't have to keep track of where your playback position is.
-You often just want to quickly zoom in on a certain point to be able to adjust clip positions more precisely.

... its users are entitled to them delivering the best user experience possible.

And therein lies the problem ... not all users have exactly the same expectations and requirements of an NLE's UI and functions. Surely that depends on whether or not the NLE (any NLE) is what the editor has 'grown-up' with and accustomed with but then moves on to another NLE where things are self-evidently going to be different.

A few observations:

3. Clicking "Close program" by mistake and then clicking the window’s X (expecting to cancel) closes the application anyway. This is diabolical.

Having had Windows for a very long time and using many, many programs over those years, 'X' in the window (usually the top RH corner) has always been a method of closing the window.

5. What in god's name is going on when you're using the mouse-wheel to zoom out of the video preview? The camera position jumps all over the place.

Double-click on the mouse wheel and the preview window display returns to the default full screen size. Zooming in/out display issues like described are also present in BorisFX's Mocha Pro and the SAL version of Mercalli stabiliser (worse in the latter because there doesn't seem to be a reset to default size keyboard shortcut).

7. Many UI elements that adjust rectangles (masking, pan/crop, event position) resize symmetrically around a center point instead of just moving the edge selected.

If you don't want centreing in pan/crop, turn off the "Size about centre" button in the Properties list in the pan/crop window.

8.The mouse-wheel zooms in on the timeline at the playback position instead of the mouse-cursor.

This current timeline zoom behaviour is without doubt my preference - and has been mentioned with positive input from time-to-time over the years on the forum as being one advantage of Vegas Pro over other NLEs. Good grief, even the supposed gold-standard of daVinci Resolve Studio doesn't offer any timeline zooming with the mouse - only by moving a slider.

Even 3-star restaurants serve water.

Still or sparkling in a 1, 2 or 3 star Michelin restaurant anywhere around the world, water will almost certainly attract a charge, and even in many non-Michelin starred restaurants. And in cafes particularly in tourist areas such as Place Navona in Rome - some 18 years ago it was just tap water that got a charge. Lesson learned - never go to a restaurant/cafe in a tourist-centric location.

.............. But at least you didn't tell me to "Just don't make any mistakes, lol" like that moron above.

@martin-2098 Read the 'Community rules'

 

.............. But at least you didn't tell me to "Just don't make any mistakes, lol" like that moron above.

@martin-2098 Read the 'Community rules'

Yes, of course, if only I had read the community rules, I would have seen the error of my ways. 🤓

Your response was so insultingly stupid, it's far more offensive than anything I could ever say. YOU chose violence.

"This text editor sucks. It doesn't have an undo function."
"Lol, just don't make any mistakes."

"What? They removed the recycle bin in Windows 12"?
"Why are you complaining? JUST DON'T DELETE ANY FILES BY ACCIDENT, LOL!"

If this is the level of discussion you'll have about such issues on this forum, I'm out anyway.

Please, let's all return to the decorum and mutual respect that is the standard for this forum.

People can give their opinions about how they think the program should work without being accused of not knowing what they are doing. You can share your experience in a way that doesn't invalidate the experiences of others. @Gid @Adis-a

In turn please refrain from insulting users, whether or not you feel they insulted you first. @martin-2098

Please, let's all return to the decorum and mutual respect that is the standard for this forum.

People can give their opinions about how they think the program should work without being accused of not knowing what they are doing. You can share your experience in a way that doesn't invalidate the experiences of others. @Gid @Adis-a

In turn please refrain from insulting users, whether or not you feel they insulted you first. @martin-2098

Fair enough.

On the topic of the timeline mouse-wheel zoom, since we all have strong opinions one way or the other, can we agree that a toggle option would be a welcome addition?

@martin-2098 I didn't choose violence, your initial post was one of frustration with the software, I gave you short to the point answers -

I'll try again

I've been using Vegas Pro for over a year now and, while some of the initial frustrations have subsided, I still feel that Vegas Pro has one of the most infuriating UIs I’ve encountered in a professional software.

I've used many editors over the last 25yrs, I've found Vegas to be the most ergonomic of them all. Many editors are nodes n hidden features, their timelines can be difficult to understand like when you accidentally drag a clip over another & it cuts the preceding one rather than crossfading it. These are just learning curves & all I've used have a fairly steep learning curve.

A program that is as powerful and has as many features as Vegas Pro will always have a steep learning curve. This is not about that. This is about Vegas Pro making it difficult to do simple things and frustrating the user with unnecessary friction and weird quirks at every opportunity. And these are not a product of it being a professional software. These are problems that could be easily fixed without breaking any of its existing functionality.

As I mention there's a learning curve, that's why I wrote 'Learn to use the software' & added - 'I apologize if this seems harsh' because I understand that is a blunt comment. But a few of your points are not broken in need of fixing, they could however be improved upon.

Here are some of them:
1. When trying to write a video onto a file that's in read-only, there's no "Try again" option; it just fails and the user has to start all over again.

I doubt Vegas isn't the only software that won't write to a read only file, Some may give a warning msg some may not, but you can't blame the software for you trying to write to a read only file. This is where improvements could be made & a warning msg could be added, but you didn't request that.

2. After a failed render or after another edit, the name of the file previously entered is gone and the user has to enter it again.

After a failed render I doubt how many software's would remember all the details of that failed render, that render becomes null n void. As mentioned Vegas renders using the project name & if I know I may have to make multiple renders I'll copy n paste the name or I'll click the file in the destination box that pops up. Many improvements could be made, if as you say you don't want to create a project every time it would be useful to maybe have the option to render using a region name, but having the previous render name be applied automatically would make the default project name void & so causing a problem of it's own ..

3. Clicking "Close program" by mistake and then clicking the window’s X (expecting to cancel) closes the application anyway. This is diabolical.

You're closing the close window clicking the X, you haven't changed the initial decision to close the UI. The program doesn't know if to save the project 'Yes or No' or to Cancel, so the program carries on with the initial instruction to close the UI. I don't see this as a fault that needs fixing. Maybe a line of code could be added where if you click the X the program auto chooses Cancel rather than carrying on with the close of the UI, but 'diabolical' is a bit harsh.

4. Exporting with custom frame dimensions requires far too many clicks. Simply enable the Width and Height fields by default and, when you enter a number, it automatically jumps the "Frame size:" field to (Custom frame size).

There's far too many choices to choose from for the software to automatically know what you want, as mentioned you can't please everyone but Vegas does remember your previous render settings, the one at the top of the list marked with *, of which you can create a Template.. + Vegas auto uses the project size so all this clicking you mention is not necessary & rendering at a different frame size to the project is never recommended.

5. What in god's name is going on when you're using the mouse-wheel to zoom out of the video preview? The camera position jumps all over the place.

I gave a fair answer to that, for 16:9 I have no problem, the zoom goes where the cursor is & double clicking the mouse wheel restores the preview to 100%. working with 9:16 projects is a different matter. What's going on in your vid example I've no idea, to me it just like someone randomly zooming n moving the cursor erratically.

6. Handling video clips that are on top of each other is quite frustrating. If two clips are on top of each other the "fx" and "..." menus for one of the tracks often just disappear and it's impossible to select the clip underneath.

I still don't understand this even after your second explanation & it doesn't sound like others do either, 'clips that are on top of each other' will only ever show the upper most clip whatever blending option you apply? Share a screen shot or video for better understanding of that.

7. Many UI elements that adjust rectangles (masking, pan/crop, event position) resize symmetrically around a center point instead of just moving the edge selected. This makes applying a mask (or any other action involving this UI) very cumbersome. The UI to adjust the clip position in the Video Event FX UI... I don't even know.

I gave a fair answer to this one, 'Picture in Picture, masking & Pan/Crop will resize around the centre, grab the corner points or highlight the 'Size About Centre' in Pan/Crop.'

8. This is a big one: The mouse-wheel zooms in on the timeline at the playback position instead of the mouse-cursor. This is one of the most infuriating things about navigating Vegas Pro.

Again I gave a fair answer & reading the other comments I'm not the only one who likes it the way it is, there is a post on this forum tho where you can make 'Feature requests' to have this added as an optional feature.

Again, this is about removing entirely unnecessary friction from the user experience without sacrificing any of Vegas Pro's power. I don't believe that these are intentional design choices, so I am wondering how some of these haven't had the necessary priority to be addressed in all the time Vegas Pro has been on the market and why its users are ok with them not being fixed.

Far from it, some of these are design choices, items like the size about centre are not what you mention & others are about learning to use the software, this is why these haven't been addressed & why users are ok with them. Improvements could be made, safeguards could be added but these are not things that are broken & need fixing.

I have used Vegas since version 4. And now for some reasons I had to user Resolve for a project. Well, I have Resolve too for many years. But I would like that it behaves like Vegas. But that is unlikely to happen.

At least I would not use such a toggle option. But it would be ok for me to have it (even if there may be no capacities left from side of the development team for that).

@martin-2098

You can post all your feature request her:

https://www.vegascreativesoftware.info/us/forum/vegas-pro-feature-requests--134374/?page=28

jøran

@martin-2098 I didn't choose violence, your initial post was one of frustration with the software, I gave you short to the point answers -

3. Clicking "Close program" by mistake and then clicking the window’s X (expecting to cancel) closes the application anyway. This is diabolical.

You're closing the close window clicking the X, you haven't changed the initial decision to close the UI. The program doesn't know if to save the project 'Yes or No' or to Cancel, so the program carries on with the iintial instruction to close the UI. I don't see this as a fault that needs fixing.

Every single program ever created by our species, except one, agrees with me:

This needs to be fixed. It is not debateable. Imagine losing work because you don't know that a common and crucial UI element works opposite to every known program in existence.

I cannot take you seriously if you keep arguing against this.