I have gotten virtually zero use out of the Vegas 23-302 trial because of the scant render options offered.

Even I can find a better use for my time than debugging my first render with a piece of software that was just announced.

@elmedin-o I think you need 3rd Party plugins like VoukoderPro-beta or HOS to get Cineform or Grass Valley codecs in vp23. I was also able to upgrade my MagicYUV license to the new version needed by vp23 without a problem and it works great. Free v6 of Debug Mode FrameServer also works with vp23 and is supplied with HOS.

Just one moment after i posted this, through random google search i found out for"show all format", so thank you all because i might also never find out

What a bizzare desition of software makers to hide big part of render codecs and you very likely could stay in delusion that is all that software offers, i run numerous all kinds of softwares and never saw things like this

Thank you all

If you are coming from simpler editing software (a market that Vegas does want to get), you don't have a zillion rendering options to confuse them.

A "bizarre" decision? Maybe, but it is not like the "down triangle" is hidden. I found it right away.

Just one moment after i posted this, through random google search i found out for"show all format", so thank you all because i might also never find out

What a bizzare desition of software makers to hide big part of render codecs and you very likely could stay in delusion that is all that software offers, i run numerous all kinds of softwares and never saw things like this

Thank you all

I agree it was a poor design decision. We will look to fix this in a future update.

Threw me at 1st too for filters to be enabled automatically by default. If new formats never seen in Vegas before were hidden under a New! icon, it would have been a more pleasant surprise.

My experience is the same as John Dennis's.

@Dexcon In your post is your image from a trial version or a purchased version?

@EricLNZ  ...

In your post is your image from a trial version or a purchased version?

It's from a purchased version.

@Dexcon Thanks.

Could you kindly show me what is in both the Sony AVC/MVC and Audio folders.

@EricLNZ  ... Here tis ...

Sony AVC/MVC:

All the audio codecs and templates:

@Dexcon Many thanks, that's very helpful.

AVCHD is still there contrary to a comment made in another thread. Also AC-3, so perhaps the AC-3 facility recently introduced into Vegas can decode and encode?

Oh, that's confusing. I have a German-language Vegas Pro 23 installation with a freshly installed Windows 11 25H2 without AC-3 codec in the operating system.
Audio AC-3 export and AVCHD export are no longer available for me.

(Presumably, this again highlights the difference between upgraded Windows systems that still have AC-3 and systems that no longer have it?)

@vegas-edit-user Yes, it's getting very confusing.

Also what has happened to MAGIX AVC/AAC MP4 and MAGIX HEVC/AAC MP4 that are in my VP21 list?

Do they perhaps now come under another heading but from your image I cannot work it which it would be.

@EricLNZ Try marking some Magix render presets as favorites in VP21, then see if they show up in VP23 as favorites. It seems that Magix AVC and HEVC are just in the AVC group and the HEVC group without the "Magix" in the preset name. They use the same File I/O plugins (just different versions).

@EricLNZ ...

Also what has happened to MAGIX AVC/AAC MP4 and MAGIX HEVC/AAC MP4 that are in my VP21 list?

Do they perhaps now come under another heading but from your image I cannot work it which it would be.

It looks the word 'MAGIX' has been dropped from the folder names. In VP22 'MAGIX AV1' is just 'AV1' in VP23, and with MAGIX AVC/AAC MP4 and MAGIX HEVC/AAC MP4 those folders are now named AVC (H.264) and NEVC (H.265) in VP23. On my desktop, all my custom AVC templates created under MAGIX AVC/AAC MP4 in VP22 and earlier all appear in VP23 under the AVC (H.264) folder. The default templates look to be the same as well, it's just that the folder names are different.

@Robert Johnston I already have some favorites and yes they do appear but not those that are 1080 as the trial only renders 720. Also only my Magix appear, no Sony AVC.

@Dexcon Getting back to the AC-3 query - does your system have the Windows AC-3 components still installed?

@EricLNZ

Getting back to the AC-3 query - does your system have the Windows AC-3 components still installed?

It is more than likely there because when Windows 24H2 was installed it was as an update on both my desktop and laptop, not clean new installations. I recall from the time the lack of Windows AC-3 support only applied to clean 24H2 installations but 24H2 as an update still accessed the AC-3 Windows components from the earlier Windows version. Those with a clean 24H2 installation couldn't use AC-3 in VP22, at least not until build 248 was released when AC-3 support was built-in to VP22.

We are excited to announce the release of VEGAS Pro 22 build 248. This update includes several bug fixes, adds new AC3 decoding capabilities for systems running Windows 11 24H2, and some major improvements to subtitling features. Please post any comments about this release in the general thread.

Please see the list of changes below.

Features: 

Text-to-speech and Speech-to-text are now available to try in trial installs 

Spoken words are now highlighted in the Subtitle Generator for Text-based Editing 

Support for AC3 media on Windows 11 systems with update 24H2 installed 

@Dexcon Yes, it looks like VP is still able to use the Windows AC-3 components if they are there.

Another mystery. Your and vegas-edit-user's screengrabs show MPEG-2. My trial version doesn't even though I have two SD MPEG-2 template favorites. Their resolution is below 720 so the image size shouldn't exclude them and their audio is MPEG Layer 2 so AC-3 isn't involved. Presumably another frustrating VP23 trial restriction. I do, occasionally, render old archived DV-AVI files to mpg for playing so I would have liked to test these out.

It appears the trial will only let you render videos with H264 MP4 and for audio only files just mp3.

To me, it would make lot of sense when there would be universal rendertemplates, which automatically adept project resolution and project framerate instead of needing for each resolution and framerate a seperate rendertemplate. This would eliminate a lot of rendertemplates in the render forrest of Vegaspro.

At least this seems to be working at the moment for framerates but not for resolutions.

Vegas has a selection filters for frame-rate and resolution. And in the past it always put an equals sign "=" next to templates that match the project parameters. But those features don't always work reliably for me lately. I often have to temporarily open up the filters and mark matching templates as favorites to pick them out consistently. In addition, the new UI doesn't scroll down to the last template used or the 1st favorite. So finding them is not particularly quick.