VEGAS Pro 23 build 278 General Discussion

Comments

Reyfox wrote on 9/20/2025, 10:20 AM

@Chris021, not seeing that issue here, ever. And I often click under the bottom track.

Your User Profile is blank. How about adding your computer specs to your Signature like mine below? Create a new post with the information from this POST, including "B" and "C".

Newbie😁

Vegas Pro 22 B250 (VP18-21 also installed)

Win 11 Pro

AMD Ryzen 9 5950X 16 cores / 32 threads

32GB DDR4 3200

Sapphire RX6700XT 12GB Driver: 25.9.1

Gigabyte X570 Elite Motherboard

Panasonic G9, G7, FZ300

Boris FX Continuum Complete 2025.5.1, Newblue FX Total FX360, Ignite Pro V5

Chris021 wrote on 9/20/2025, 11:01 AM

Thanks @Reyfox, I've opened a new topic, following your suggestions : https://www.vegascreativesoftware.info/us/forum/v23-crash-when-clicking-under-bottom-track--149738/

Last changed by Chris021 on 9/20/2025, 11:01 AM, changed a total of 1 times.

Vegas Pro 23 (278) - Vegas Pro 19
HP Z2 Tower G9 Workstation
Windows 10 Pro 64bits, Version 10.0.19045 (Build 19045)
Intel Core i9-12900K, RAM 32Gb DDR5
NVIDIA GeForce RTX 3060 12Gb GDDR6
NVIDIA Driver : 14/08/2024 Version 32.0.15.6094
GPU Acceleration : Optimal - NVIDIA GeForce RTX 3060
Hardware Decoder : Auto - NVIDIA GeForce RTX 3060
Video files : Panasonic G9 - Honor 200 Pro

digilyd wrote on 9/20/2025, 12:29 PM

What is going on here? - the visual differences between gui of V22 and V23 are a matter of taste, not that I am happy about them, but the visual difference between the previews of the same frame in the same project are a disaster. The V23 preview is plain wrong.


@digilyd The preview quality setting on your video preview is different, comparing is best done with the same settings (e.g. both BEST (full))

Good point in as much as that is not something I checked because I generally got rid of grainy previews after getting a 4060 card, the same setting ought to have been used, but that is not what this is about. The preview quality setting is about resolution, not about colour rendering, the file is displayed dramatically brighter than it is. However to not leave it unadressed, here is a screen snapshop of the preview of V23 with the same setting as the one in V22, Best, half:



As you can see, there grave difference in color rendering is the same. Cut a square in a sheet of paper and compare the lawn or the clarinet player with everything else masked off, that is how printers compare colour.​​​​

Reyfox wrote on 9/20/2025, 1:42 PM

Would it be possible to share one of your clips in the cloud along with your Vegas Project Video Properties settings?

Newbie😁

Vegas Pro 22 B250 (VP18-21 also installed)

Win 11 Pro

AMD Ryzen 9 5950X 16 cores / 32 threads

32GB DDR4 3200

Sapphire RX6700XT 12GB Driver: 25.9.1

Gigabyte X570 Elite Motherboard

Panasonic G9, G7, FZ300

Boris FX Continuum Complete 2025.5.1, Newblue FX Total FX360, Ignite Pro V5

Hajowo wrote on 9/20/2025, 1:53 PM

Hi,

I've now installed Vegas Pro 23. The first thing I noticed was that the EDL interface (project transfer from VPX17 to VP23) still doesn't work.

Unfortunately, this wasn't surprising to me: The EDL/AAF/project interfaces between MAGIX Video Pro X and VEGAS Pro have never been truly compatible since I started using both software. Although both programs are "under the same roof," the development teams are quite independent of each other – or what?

I know, many editors instead use the intermediate step via exchange formats like MXF, DNxHD/DNxHR, or Cineform – that is, they "bake" clips and then import them.

A direct "project bridge" from VPX to VEGAS is not officially planned, as far as I know.

In short: My test confirms that, unfortunately, nothing has improved here.

Or does anyone have more knowledge?

Gruß Hansi
https://pinnacle-hilfe.boards.net/

Software: DaVinci Resolve 20 Studio, Magix Video Pro X17, Vegas Pro 23
Kamera: Lumix GH6, G9II, S5IIX, Blackmagic PCC4K, Objektive Leica 12-60, Lumix 12-60, Sigma 16mm und 30mm, Atomos Ninja V+
Desktop: i7-9700K, Win11, GTX 1060-6GB, 32 GB RAM, SSDs 2x250GB,1TB, 2TB, 2TB M.2
Mobil: Notebook HP-ProBook 470-G7 Intel i7-10510 U, RAM 32GB, 1TB SSD, 1 TB HDD, Radeon 530.

 

Richard-Buswell wrote on 9/20/2025, 5:32 PM

I installed the upgrade to Vegas 23 with no issues. I am running Windows 10. I started Vegas 23, which displayed the splash screen showing the loading progress and it crashed within a few seconds. When I say it crashed, I mean I got the problem reporting screen. I submitted the issue from that screen and have heard nothing in over a week. Is this a known issue or am I just special?

RogerS wrote on 9/20/2025, 7:08 PM

What is going on here? - the visual differences between gui of V22 and V23 are a matter of taste, not that I am happy about them, but the visual difference between the previews of the same frame in the same project are a disaster. The V23 preview is plain wrong.


@digilyd The preview quality setting on your video preview is different, comparing is best done with the same settings (e.g. both BEST (full))

Good point in as much as that is not something I checked because I generally got rid of grainy previews after getting a 4060 card, the same setting ought to have been used, but that is not what this is about. The preview quality setting is about resolution, not about colour rendering, the file is displayed dramatically brighter than it is. However to not leave it unadressed, here is a screen snapshop of the preview of V23 with the same setting as the one in V22, Best, half:



As you can see, there grave difference in color rendering is the same. Cut a square in a sheet of paper and compare the lawn or the clarinet player with everything else masked off, that is how printers compare colour.​​​​

Did you see my reply as well?

digilyd wrote on 9/21/2025, 12:53 AM

What is going on here? - the visual differences between gui of V22 and V23 are a matter of taste, not that I am happy about them, but the visual difference between the previews of the same frame in the same project are a disaster. The V23 preview is plain wrong.


@digilyd The preview quality setting on your video preview is different, comparing is best done with the same settings (e.g. both BEST (full))

Good point in as much as that is not something I checked because I generally got rid of grainy previews after getting a 4060 card, the same setting ought to have been used, but that is not what this is about. The preview quality setting is about resolution, not about colour rendering, the file is displayed dramatically brighter than it is. However to not leave it unadressed, here is a screen snapshop of the preview of V23 with the same setting as the one in V22, Best, half:



As you can see, there grave difference in color rendering is the same. Cut a square in a sheet of paper and compare the lawn or the clarinet player with everything else masked off, that is how printers compare colour.​​​​

Did you see my reply as well?

Yes, that is why I posted the screenshot of the properties settings.

bitman wrote on 9/21/2025, 2:12 AM

Are you using ACES? 23 is using an updated version.

ACES? - huh? - I don't know, in that regard I use the software as is out of the shrink wrap. Ah well, something to look in to, thank you!

First image project properties in V22
Second image project as loaded in V23


@digilyd I see you have the same prerendered file location path set for VP22 as for VP23, which is not advisable. In such case I assume VP23 is picking a VP22 prerendered file with the same same or vice versa. If I am not mistaken using 4K (or greater) creates proxies if not disabled in the video section of the preference.

APPS: VIDEO: VP 365 suite (VP 22 build 250) VP 21 build 315, VP 365 20, VP 19 post (latest build -651), (uninstalled VP 12,13,14,15,16 Suite,17, VP18 post), Vegasaur, a lot of NEWBLUE plugins, Mercalli 6.0, Respeedr, Vasco Da Gamma 17 HDpro XXL, Boris Continuum 2025, Davinci Resolve Studio 18, SOUND: RX 10 advanced Audio Editor, Sound Forge Pro 18, Spectral Layers Pro 10, Audacity, FOTO: Zoner studio X, DXO photolab (8), Luminar, Topaz...

  • OS: Windows 11 Pro 64, version 24H2 (since October 2024)
  • CPU: i9-13900K with Air Cooler: Noctua NH-D15 G2 HBC
  • RAM: DDR5 Corsair 64GB (5600-40 Vengeance)
  • Graphics card: Gigabyte GeForce RTX 5090 Aorus Xtreme WF AIO 32GB
  • Monitor: LG UltraGear 45GX950A 44.5" WUHD 5K2K OLED monitor (21:9), Resolution: 5120x2160, 165 Hz
  • C-drive: Corsair MP600 PRO XT NVMe SSD 4TB (PCIe Gen. 4)
  • Video drives: Samsung NVMe SSD 2TB (980 pro and 970 EVO plus) each 2TB
  • Mass Data storage & Backup: WD gold 6TB + WD Yellow 4TB
  • MOBO: Gigabyte Z690 AORUS MASTER
  • PSU: Corsair HX1500i, Case: Fractal Design Define 7 (PCGH edition)
  • Misc.: Logitech G915, Evoluent Vertical Mouse, shuttlePROv2

 

 

bitman wrote on 9/21/2025, 2:26 AM

@digilyd using 32bit may very well be the issue with your different look in VP23, as using 32 bit probably triggers the new color space handling in VP23. A temporary solution may be in using 8 bit full, or go into the internal settings (hold shift while pressing preference) and set "enable extended color format conversion" to FALSE.
Not sure it would help tough.

APPS: VIDEO: VP 365 suite (VP 22 build 250) VP 21 build 315, VP 365 20, VP 19 post (latest build -651), (uninstalled VP 12,13,14,15,16 Suite,17, VP18 post), Vegasaur, a lot of NEWBLUE plugins, Mercalli 6.0, Respeedr, Vasco Da Gamma 17 HDpro XXL, Boris Continuum 2025, Davinci Resolve Studio 18, SOUND: RX 10 advanced Audio Editor, Sound Forge Pro 18, Spectral Layers Pro 10, Audacity, FOTO: Zoner studio X, DXO photolab (8), Luminar, Topaz...

  • OS: Windows 11 Pro 64, version 24H2 (since October 2024)
  • CPU: i9-13900K with Air Cooler: Noctua NH-D15 G2 HBC
  • RAM: DDR5 Corsair 64GB (5600-40 Vengeance)
  • Graphics card: Gigabyte GeForce RTX 5090 Aorus Xtreme WF AIO 32GB
  • Monitor: LG UltraGear 45GX950A 44.5" WUHD 5K2K OLED monitor (21:9), Resolution: 5120x2160, 165 Hz
  • C-drive: Corsair MP600 PRO XT NVMe SSD 4TB (PCIe Gen. 4)
  • Video drives: Samsung NVMe SSD 2TB (980 pro and 970 EVO plus) each 2TB
  • Mass Data storage & Backup: WD gold 6TB + WD Yellow 4TB
  • MOBO: Gigabyte Z690 AORUS MASTER
  • PSU: Corsair HX1500i, Case: Fractal Design Define 7 (PCGH edition)
  • Misc.: Logitech G915, Evoluent Vertical Mouse, shuttlePROv2

 

 

yves-sarrut wrote on 9/21/2025, 4:25 AM

Bonjour, j'ai installé la version essai de végas pro 23 et impossible de l'ouvrir avec le code TRIALC envoyé par mail après enregistrement. Comment faire pour lancer le logiciel en essai ?

Chris021 wrote on 9/21/2025, 4:55 AM

Faut juste entrer le code dans la zone prévue. Vérifie que tu as bien fait le copier-coller dans la bonne case. Je n'ai pas eu de problème.

Vegas Pro 23 (278) - Vegas Pro 19
HP Z2 Tower G9 Workstation
Windows 10 Pro 64bits, Version 10.0.19045 (Build 19045)
Intel Core i9-12900K, RAM 32Gb DDR5
NVIDIA GeForce RTX 3060 12Gb GDDR6
NVIDIA Driver : 14/08/2024 Version 32.0.15.6094
GPU Acceleration : Optimal - NVIDIA GeForce RTX 3060
Hardware Decoder : Auto - NVIDIA GeForce RTX 3060
Video files : Panasonic G9 - Honor 200 Pro

RogerS wrote on 9/21/2025, 6:06 AM

What is going on here? - the visual differences between gui of V22 and V23 are a matter of taste, not that I am happy about them, but the visual difference between the previews of the same frame in the same project are a disaster. The V23 preview is plain wrong.


@digilyd The preview quality setting on your video preview is different, comparing is best done with the same settings (e.g. both BEST (full))

Good point in as much as that is not something I checked because I generally got rid of grainy previews after getting a 4060 card, the same setting ought to have been used, but that is not what this is about. The preview quality setting is about resolution, not about colour rendering, the file is displayed dramatically brighter than it is. However to not leave it unadressed, here is a screen snapshop of the preview of V23 with the same setting as the one in V22, Best, half:



As you can see, there grave difference in color rendering is the same. Cut a square in a sheet of paper and compare the lawn or the clarinet player with everything else masked off, that is how printers compare colour.​​​​

Did you see my reply as well?

Yes, that is why I posted the screenshot of the properties settings.

I posted about the extended color space setting in internal preferences, not ACES.

bitman wrote on 9/21/2025, 6:12 AM

Bonjour, j'ai installé la version essai de végas pro 23 et impossible de l'ouvrir avec le code TRIALC envoyé par mail après enregistrement. Comment faire pour lancer le logiciel en essai ?


@yves-sarrut Did you perhaps install the French version of Vegas Pro? There is a long standing (and confirmed) issue with the French VP22 version not opening after installing. I am not sure if they fixed it yet, or if it is still the case with VP23. If it is still the case, a solution was to install the English version...

APPS: VIDEO: VP 365 suite (VP 22 build 250) VP 21 build 315, VP 365 20, VP 19 post (latest build -651), (uninstalled VP 12,13,14,15,16 Suite,17, VP18 post), Vegasaur, a lot of NEWBLUE plugins, Mercalli 6.0, Respeedr, Vasco Da Gamma 17 HDpro XXL, Boris Continuum 2025, Davinci Resolve Studio 18, SOUND: RX 10 advanced Audio Editor, Sound Forge Pro 18, Spectral Layers Pro 10, Audacity, FOTO: Zoner studio X, DXO photolab (8), Luminar, Topaz...

  • OS: Windows 11 Pro 64, version 24H2 (since October 2024)
  • CPU: i9-13900K with Air Cooler: Noctua NH-D15 G2 HBC
  • RAM: DDR5 Corsair 64GB (5600-40 Vengeance)
  • Graphics card: Gigabyte GeForce RTX 5090 Aorus Xtreme WF AIO 32GB
  • Monitor: LG UltraGear 45GX950A 44.5" WUHD 5K2K OLED monitor (21:9), Resolution: 5120x2160, 165 Hz
  • C-drive: Corsair MP600 PRO XT NVMe SSD 4TB (PCIe Gen. 4)
  • Video drives: Samsung NVMe SSD 2TB (980 pro and 970 EVO plus) each 2TB
  • Mass Data storage & Backup: WD gold 6TB + WD Yellow 4TB
  • MOBO: Gigabyte Z690 AORUS MASTER
  • PSU: Corsair HX1500i, Case: Fractal Design Define 7 (PCGH edition)
  • Misc.: Logitech G915, Evoluent Vertical Mouse, shuttlePROv2

 

 

Chris021 wrote on 9/21/2025, 7:36 AM

I've installed french version of Trial and final with no issue.

Vegas Pro 23 (278) - Vegas Pro 19
HP Z2 Tower G9 Workstation
Windows 10 Pro 64bits, Version 10.0.19045 (Build 19045)
Intel Core i9-12900K, RAM 32Gb DDR5
NVIDIA GeForce RTX 3060 12Gb GDDR6
NVIDIA Driver : 14/08/2024 Version 32.0.15.6094
GPU Acceleration : Optimal - NVIDIA GeForce RTX 3060
Hardware Decoder : Auto - NVIDIA GeForce RTX 3060
Video files : Panasonic G9 - Honor 200 Pro

digilyd wrote on 9/21/2025, 8:21 AM


@digilyd I see you have the same prerendered file location path set for VP22 as for VP23, which is not advisable. In such case I assume VP23 is picking a VP22 prerendered file with the same same or vice versa. If I am not mistaken using 4K (or greater) creates proxies if not disabled in the video section of the preference.

It is a project setting and it is the same project opened in V22 and V23. This is what the software itself selects to do, opens the project as it was opened.

Proxies can be selected to be automatically created for *greater than* 4k. It takes forever to generate proxies, so I am confident that I would have noticed.

The combined size of the folders that would be used for pre-rendering is 220 megabytes.

AUDIS-8 wrote on 9/21/2025, 11:47 AM

Hello esteemed Vegas Pro Team. You know, I'm a big fan. I've been with you since Vegas 5, and now I have Vegas 23. It's the most beautiful version yet! It has the exact style a great program like Vegas Pro should have.
But there's a big but. In 2025, these kinds of things are unacceptable. I can't wrap my head around who approved the release of Vegas Pro 23 (Build 278). Is this person getting paid? Does anyone there have eyes? Or am I exaggerating? You tell me, ladies and gentlemen:
You click the button to launch Vegas 23 Pro.
(See Photo 1)


And in one second, a small window appears in the middle of the desktop asking you to "please wait a couple of minutes."
(See Photo 2)


Another second later, the Vegas Pro 23 splash screen appears.
(See Photo 3)


The program starts to load, and instead of just opening, a blank, white window with a "V" in the middle appears on the taskbar.
(See Photo 4)


Then that second white window disappears.
(See Photo 5)


And you see the Vegas Pro 23 splash screen in the center of your Windows desktop. You're so close to the program loading, and instead of getting excited, you're left with a strange feeling, like you were sold glasses with broken lenses. Why did this happen?
(See Photo 6)


You know, it's not even funny anymore. Everywhere in the world, a program that opens on the desktop opens from the center of the screen. This is a fundamental rule for both macOS and Windows. It's correct, pleasant, and what your eyes and brain expect. So who approved this, where after loading, the program window flies out from the bottom-left corner? Are you serious, Carl? The bottom-left corner? Not from the center of the screen, but the bottom-left corner? How am I supposed to understand this, Vegas Pro Team? Why are you upsetting your fans like this? Just think about how many bugs had to happen before the program even launched. Do you get that? Hello?
Okay, so the program finally stumbles into action, and we start working, but no, there's another surprise.
I'm working on a single project that I've used with every version from Vegas 10 to Vegas 22, and all of them handled it perfectly—except for Vegas 23 Build 278.
Vegas 22 Pro loads the entire project and the audio perfectly. Everything is great, the workflow is smooth, and the program doesn't crash.
(See Photo 7 - Pay attention to the audio track)


But when I open the same project in Vegas 23, I'm immediately greeted with an "Error Error" window. I click "OK." The project starts to load, the video track loads, but the audio track doesn't load at all.
(See Photo 8 - Look at the audio track)


If I open the project ten times, the audio might load once, but the next time it won't. The sound is there, but the track itself doesn't load.
And that's not all. With this specific project, Vegas 23 crashes while I'm working with video. There aren't even any effects—they are just VOB DVD files. All the previous versions handled everything perfectly, but Vegas Pro 23 (Build 278) is like a handsome guy with a slow brain.
And the most important thing, THE MOST IMPORTANT THING:
Change the function of the left mouse button to the right mouse button, or give us the option in the settings to switch the functions ourselves.
Who is doing your thinking over there, Vegas Team? Who is the brain of the team?
For 20 years, we've been clicking the left mouse button to get a certain result, and it was perfect. Then someone on your team—someone who has clearly never used Vegas Pro themselves—suddenly decided that the left mouse button would now perform an action that I, for one, have never used!
(See Photo 9)


Yes, this new option is convenient and correct, and I like it a lot. When I need it, I'll just click the right mouse button and use it.
Just swap the functions of the mouse buttons, left for right. Or, add an option in the settings for customers to choose which function is assigned to which mouse button.
Otherwise, it looks like you don't respect your company's traditions and you don't respect your fans. This will undoubtedly kill the company. These are the kinds of unforgivable mistakes in 2025.

 

bvideo wrote on 9/21/2025, 2:36 PM

Here is one area of terribly worse performance of V23 over V22:

Stills that use pan and crop: some pan-crop motions kill performance. Not all. These are stills of 4000 X 3000 from a Samsung S21 in a project of 1920 X 1080. So far, it seems when the crop size varies, V23 runs 3 or 4 times more slowly. Pan motion without changing the size doesn't seem like much of a problem. Rotation bothers the performance a bit.

I've only unit tested with a start and an end keyframe, and only with stills.

Edit: this is with my system with UHD 730. My other system with a GTX 1660 super also had performance problems with pan-crop.

Last changed by bvideo on 9/21/2025, 2:44 PM, changed a total of 1 times.

Dedicated: Vegas 20, 21, & 22, i7 8700k (w/ UHD 630), GTX 1660 super, 32 gig ram, ssd & 2 spinning units.

General purpose: i5 11400 (w/ UHD 730), 32 gigs, ssd, 1 spinning unit (Vegas 21 & 22)

AUDIS-8 wrote on 9/21/2025, 7:25 PM

To the Vegas Pro team, I do love you!!!  But who allowed this terrible change in the video preview? When you press the play button and the video starts playing, I press fullscreen to enjoy the picture, then press Esc to exit fullscreen and continue watching the video. That’s exactly how it worked in Sony Vegas 10. You watch the video, go fullscreen, then back to a smaller screen, watch the picture, keep watching the video, and if needed, press spacebar or enter to pause the video, right? Of course it is.

But in Vegas Pro 23, some genius who probably never used Vegas Pro decided that if you play the video in fullscreen and then press Esc, the video stops and returns to normal mode. But here’s the question: I never pressed stop! Nobody pressed stop, so why has the Esc key become so dumb? Why are you ruining what was perfect!

Example videos: Video 1, Video 2
Versus Vegas 23 vs Vegas 10

I want the Vegas Pro company to be respected.
All my notes show obvious negligence from your programmers. This is just not serious, guys.
I use Vegas 10 Pro and Vegas 22 Pro.
You promised the video preview in Vegas 23 Pro would be four times better than previous versions, but the only thing Vegas 23 is better at than Vegas 22 is the white line at the top of the screen that was distracting in Vegas 22—you painted it over in Vegas 23, and many themes were changed to dark mode, and that’s it. Vegas 23 is unstable and crashes constantly.
My notes have deep meaning. Fix this, and you will truly earn respect as you deserve

AUDIS-8 wrote on 9/21/2025, 8:16 PM

Here is the perfect example of how Vegas Pro 23 should load. But only Vegas Pro 10, Carl, loads this perfectly, so quickly, so clearly, and correctly. Ten!))))
Not Vegas 22, which ends up popping up from the bottom left corner.
Not Vegas Pro 23, which sometimes disappears from the screen, sometimes splits on the control panel like a robot from Terminator 2, and opens painfully slowly like my grandmother’s old wardrobe.

Vegas Pro team, I’ve left three comments here for the first time in my life because I really love this program! But someone on your team doesn’t love it like we, the fans, do. And little by little, Vegas Pro is drifting away from its original roots, which is why we loved Vegas in the first place.

Watch this video and draw your own conclusions, ladies and gentlemen. You should be selling this program to millions of people. Go back to the roots in an updated shell. Then your business will take off.

Vegas team, please take my messages seriously.
Sincerely, Anonymous 

Thomas97 wrote on 9/22/2025, 5:13 AM

@Thomas97 There's a lot here so it might be good to also create a new post so we can try to replicate bugs or help you with UI issues that aren't obvious.

You refer to ACES but are you using ACES? You are in 32-bit full mode with view transform on?

For the 4 panel graph, do you mean the color curves? You prefer to have R, G, B and overall luminance as separate graphs than overlaid as in below here? The problem I see with 23's implementation is that the lines are all on top of each other unless you toggle one off or move one out of the way.

For pixelation the screenshot isn't high enough resolution to see an issue.

Are these issues specific to the footage you are using? I don't see general issues with cropping and masking. The reported issue is about a problem that returned where a proxy file resulted in an offset Fx.
 

Hello @RogerS
I'll create a separate post then, and I'll reply to those questions there as soon as I have some time!

Hello @RogerS and @VEGAS_CommunityManager, I created a post with updated information, answering the questions: https://www.vegascreativesoftware.info/us/forum/multiple-v23-bugs-color-grade-broken-4x-slow-render-ux-pan-crop--149757/

(or click here)

Reyfox wrote on 9/22/2025, 7:00 AM

@AUDIS-8 I gotta say, I love your "passive aggressive" writing. Saying you love the Vegas programmers and then proceed to try and belittle them because VP23 doesn't behave like the 13 year old VP10. Really? Where have you been? Three comments and you say you have VP22 and just getting around to complaining about how VP23 stops timeline playback when you go from Full Screen back to the Video Preview??? Really? Where have you been the last many years? It's been like that for quite a while. No one has complained about it.

And if you spent more time asking questions about how the software works instead to trying to berate the programing team, maybe you would have answers to your questions.

You expect zero progress in 12 years in the way things work. Zero. And beef without commenting on the functionality of it, just that you don't like it and that the programmers have never used Vegas. You want things to be stuck in the past, never progressing to the future. And if you set up Windows Layouts, you can have Vegas start any way you want with whatever windows you want docked to it. Customization.

The company's traditions have been kept. It is expecting no improvements in UI and functionality that is disrespectful to the Vegas users.

You can always continue to use VP10 and edit or not. You had VP22 and that was a taste of how VP23 would be like. And yet, no complaints. Strange in deed.

Oh BTW, your User Profile is totally blank. Not even your computer specs. Nothing.

And in closing, you write:

Vegas team, please take my messages seriously.
Sincerely, Anonymous 

That's funny. I would never take anything serious from anyone who sign as "anonymous", writes that I don't know what I am doing, and do what I want to please me. Again, VP22 was the precursor for VP23 with a lot of the same functionality, yet nothing reported.

Are there issues with VP23? Yes. I've commented on them to help the developers, without calling them "Carl", and writing "But in Vegas Pro 23, some genius who probably never used Vegas Pro decided...."

Last changed by Reyfox on 9/22/2025, 7:07 AM, changed a total of 2 times.

Newbie😁

Vegas Pro 22 B250 (VP18-21 also installed)

Win 11 Pro

AMD Ryzen 9 5950X 16 cores / 32 threads

32GB DDR4 3200

Sapphire RX6700XT 12GB Driver: 25.9.1

Gigabyte X570 Elite Motherboard

Panasonic G9, G7, FZ300

Boris FX Continuum Complete 2025.5.1, Newblue FX Total FX360, Ignite Pro V5

_litz wrote on 9/22/2025, 7:54 AM

For whatever it's worth, I've been quite happy with 23. Does what I need it to do, and is rock solid.

My only beef was the swapping of the space/enter functionality for play/pause/stop. Was NOT expecting that default to be the opposite of 22 and older. But one checkbox, and expected behavior is back to what I wanted.

Oh, and losing Voukoder, but Vouk is working on that.

digilyd wrote on 9/22/2025, 10:19 AM

@digilyd Out of the shrink rap is 8-bit full, so not 32-bit full with ACES.

The only other difference is VEGAS can now for the first time correctly read color spaces other than the standard Rec709 and Rec2020 ones. If that's causing unexpected issues for your footage (or you just don't like the effect) you can disable it in internal preferences. Hold down shift, go to options, search for color and change "("enable extended color format conversion" from TRUE to FALSE. Then restart VEGAS.

Sorry, new text went into a new post ..... but yes, [shift] Options\Internal and changing that setting solved the issue, [bowing] thank you, I've had a busy weekend ...... my footage is from Panasonic 990-series cameras, a VX3 just added, but not testdriven yet.