I would anticipate this type of semantic snark on Reddit, but here we are. Ensuring that all the I’s are dotted and T’s crossed. Don’t worry about the topic of the post; just keep talking about getting the product name correct and being petty.

@BuzWeaver You've come to the official forum of VEGAS Pro; official meaning it is operated under the company that now owns the product and which does not want it associated with Sony a decade post acquisition. On Reddit the reason is more about confusion- if you say Sony VEGAS you are assumed to be talking about versions up to 13.

Anyway, I am having trouble understanding what I am looking at in your screenshot. Is it 3 stacked videos with the center one supposed to have a border using border Fx?

If so, here's an attempt to replicate it in 23 with an NVIDIA RTX 4060 mobile in use. I had to move the border Fx left of pan crop (added at the event level) to get it to look like this.

Understood on using the proper name. I record in 1920×1080 at 60 fps and use the 1920×1080 format on other video hosting sites, but when I post to YouTube, Instagram, and TikTok as Shorts, I have to use the 1080×1920 (9:16) format. What I would do is have the 1920×1080 format inside the 1080×1920 preview window, then make an additional copy on a new video track on top of the original. Then I select the original track > Pan/Crop > right click on the clip > Match Output Aspect > then Video FX > Border > drag the solid white border onto the selected duplicate top track (top track clip), then change the color and size.

Granted, it’s not necessary to do it this way, as I’ve done it with a solid background and no border, but it’s something I’ve been doing for a while

.

Hello Vegas Pro forum,

After experiencing very odd video anomalies with some imported .mp4 files, I googled this problem and found a recommendation on the internet. I opted to enable "Legacy AVC decoding" under the File I/O menu item (see screenshots) and this corrected the problem.

@mark56 what created the mp4 files? MP4 is a container that can contain "anything". But in order to fix these issues, the developers would have to have some idea of what the file(s) are.

Also what are your specific computer specifications? Add them to your Signature like mine below.

Thanks for the reply Reyfox, but not being very technically knowledgeable about these things, how do I find out more information about my mp4 files without installing any additional software?

@mark56 what most of us use to see what a file "is", is MediaInfo. It is a tiny free software that we all have installed.

If I left click on a video asset to highlight it in the Window folder, then right mouse click, a context menu will come up with MediaInfo there. I mouse to it, and then when MediaInfo opens, View>Tree. There I can see what the actual video file is and some necessary information about it, bit rate, frame rate, resolution, etc.. See screenshot below.

Thanks for adding your computer specs!

Thanks for the suggestion Reyfox. I installed MediaInfo and ran it. Do I get the resulting file to support?

What MediaInfo does is show what your file is. If you want a file that will work with Vegas, you can always transcode the file to something Vegas loves with Shutter Encoder, another utility software everyone has in their editing toolkit.

MP4 is a container. It can contain all sorts of files created by all sorts of video recording equipment.

Hi there, Best wishes for everyone here!

I have question, I have been playing around with Smart Mask 2.0 for quit a bit now. Besides that it works very slowly in "better, slower" option, the motion tracking is always drifting away. I watched all the tutorials to get better results. But I can't do a good job with it.

Also, I need to restart Vegas every time I want to do another try with the plugin, or else it doesn't work at all. So I can't use it in any production.

Is there somebody who get good results with the plugin. I run it at a Core-i7 11800H with Nvidia RTX3050ti and 32Gb RAM. And what is the right way to use it?

I figured out, that one specific key-bind is not stored and whould not work after restarting the application. I use ALT+D for global Trim.End and after setting, it is working just fine, until i turnoff the program. Trim.Start which i use with ALT+S is working just fine.

Hi,

After correctly downloading, installing and adding it as a plugin with VP, Smartsound is still not showing up in the VP23 Extensions list. Any help on how to fix this will be appreciated. Thanks in advance

Kind Regards

Smartsound, which extensions did you check? It does appear in Tools>Extensions for me. It doesn't appear in Edit or View. Also, I pinned it to Customize Tool bar at the top.

Saving Windows Layouts in Pro 23, See pics. I use a 34" wide screen and like the side-by-side layout, worked great in 22, however after setting it up in 23 and saving it, if I close and reopen 23 or click on the Split saved view it looks like the second pic with space at top and bottom of the left window. I can easily fix it and grab the top or bottom and stretch it out, but it does not reopen in full screen. Pro 22 saved window worked fine.

I like having the selected options highlighted in saturated yellow, but no matter how hard I try, they always appear in blue (!?) 😳...

Smartsound, which extensions did you check? It does appear in Tools>Extensions for me. It doesn't appear in Edit or View. Also, I pinned it to Customize Tool bar at the top.

I was checking the view menu. However, found it in the tools menu thanks for the help on this Reyfox, appreciated.

I like having the selected options highlighted in saturated yellow, but no matter how hard I try, they always appear in blue (!?) 😳...

 

@Sr_Garcia Just tried changing the button highlight color on my laptop in Options/Preferences/Display. Works fine with vp22 b250. But with vp23 b356 the button highlight color stays blue as you described. Appears to be a vp23 bug.

I like having the selected options highlighted in saturated yellow, but no matter how hard I try, they always appear in blue (!?) 😳...

It is something that is not working with VP 23. The initial goal was to give users extensive options for customizing the colors in the interface, but we ran out of time to finish that feature before VP 23 released. This setting was left over and not hooked up again.

I like having the selected options highlighted in saturated yellow, but no matter how hard I try, they always appear in blue (!?) 😳...

 

It is something that is not working with VP 23. The initial goal was to give users extensive options for customizing the colors in the interface, but we ran out of time to finish that feature before VP 23 released. This setting was left over and not hooked up again.

Well... it's not that important...

I suppose there are other, more relevant problems to solve.

Hello, VEGAS team and community,

I’d like to request an improvement for the Select All After Cursor command.

Currently when choosing Select All After Cursor from the right-click menu or the Edit → Select menu, a modal dialog always appears, asking whether to select on All Tracks or Selected Tracks and giving additional split/grouping options.
This breaks the editor workflow because:

I expect a single click → all events to the right of the cursor are selected without additional confirmation.

The dialog interrupts fast editing, adding an extra click every time I want to move or manipulate all events right of the cursor.

This behavior differs from the classic single-action selection many editors rely on.

Request:
Please add an option to remember the last choice or an option to disable the dialog so that Select All After Cursor can run immediately with one click, especially for the “All Tracks” default.

Thank you!

@MARJAN-MERTELJ, you can always write a quick script that will select everything the way you want things selected and tie it to a keypress or button press. Here's an example:

I would like to share an upgrade experience and ask for clarification regarding Suite feature continuity.

I upgraded to VEGAS Pro 23 Suite in November (during a promotional period).
My upgrade decision was based on workflows I had used in previous VEGAS Pro Suite versions, including Mocha-based tracking, which was an important reason for choosing the Suite tier over Pro.

By January, this workflow was no longer available or usable in VEGAS Pro Suite 23. During the upgrade process, I did not encounter any clear or prominent communication indicating that a previously available Suite-level workflow would no longer be accessible shortly after upgrading.

Support later confirmed that MochaVEGAS was part of earlier Suite versions but is not included in Suite 23.
While I understand product changes between versions, the short timeframe between upgrade and loss of this workflow raised concerns regarding value continuity for Suite upgrades.

I contacted MAGIX support to request clarification or a possible downgrade/refund of the Suite price difference, but unfortunately I was unable to reach a resolution.

My goal with this post is not to criticize, but to better understand:

how Suite feature changes are communicated between major versions, and

how users are expected to evaluate feature continuity when upgrading.

I believe clearer communication around Suite-level feature changes would help users make more informed upgrade decisions in the future.

I would like to share an upgrade experience and ask for clarification regarding Suite feature continuity.

I upgraded to VEGAS Pro 23 Suite in November (during a promotional period).
My upgrade decision was based on workflows I had used in previous VEGAS Pro Suite versions, including Mocha-based tracking, which was an important reason for choosing the Suite tier over Pro.

By January, this workflow was no longer available or usable in VEGAS Pro Suite 23. During the upgrade process, I did not encounter any clear or prominent communication indicating that a previously available Suite-level workflow would no longer be accessible shortly after upgrading.

Support later confirmed that MochaVEGAS was part of earlier Suite versions but is not included in Suite 23.
While I understand product changes between versions, the short timeframe between upgrade and loss of this workflow raised concerns regarding value continuity for Suite upgrades.

I contacted MAGIX support to request clarification or a possible downgrade/refund of the Suite price difference, but unfortunately I was unable to reach a resolution.

My goal with this post is not to criticize, but to better understand:

how Suite feature changes are communicated between major versions, and

how users are expected to evaluate feature continuity when upgrading.

I believe clearer communication around Suite-level feature changes would help users make more informed upgrade decisions in the future.

Thanks for sharing your experience. Unfortunately, it's been a recurring theme with several other posts in the community. Mocha VEGAS, legacy AVI encoding (even though it's still listed in settings), and stereoscopic 3D were all removed in 23 with no communication unfortunately. The only real 'solution' I've seen so far is that we should be downloading the trials for new versions of VEGAS Pro to see if our workflow is still supported. Not a great solution, but it is what it is. The lack of communication has already been acknowledged by a dev but so far nothing has come of it.

There was plenty of discussion in this forum about Mocha Vegas not being included in VP23 Suite, which was released August/September last year. Plenty. If you look at what is included with Suite, it did say with VP22, that Mocha Vegas was a part of it. Looking at what comes with the current version of Suite, it is not listed.

Vegas Suites have differed over the years, never the same thing offered (of what I use) twice. That is why I bought Continuum Complete to avoid this issue. As for Mocha Vegas, I too agree that it was a great addition, but then I am not a "bean counter". I even asked in the Boris forum would they make it available as a plugin (since that is what it essentially was), and the sad news is, no. If it were profitable for them, I am sure that they would. Mocha Pro is too costly for me, but with Continuum Complete 2026, most of the plugins do have Mocha Mask and Track.