Comments

Nath.veg wrote on 9/9/2025, 2:43 PM

I’ll start: I’m getting a texture bug when rendering here

chell wrote on 9/9/2025, 2:48 PM

Having issues with the pixel format/color range not properly decoding ProRes files anymore with ACES or something? idk i'm still trying to diagnose and fix my project.

current workstation

cpu: intel core ultra 9 285k - 24 cores (8p + 16e), 24 threads, up to 5.7 ghz boost, 36 mb l3 cache, integrated intel arc xe graphics (64 eus)

gpu: nvidia geforce rtx 5080 -16 gb gddr7 vram, 10,752 cuda cores, dlss 4, latest studio driver

memory: 128gb ddr5

storage: 4 tb samsung nvme ssd

os: windows 11 64-bit

chell wrote on 9/9/2025, 2:49 PM

Prior to update:

After update:

:

 

current workstation

cpu: intel core ultra 9 285k - 24 cores (8p + 16e), 24 threads, up to 5.7 ghz boost, 36 mb l3 cache, integrated intel arc xe graphics (64 eus)

gpu: nvidia geforce rtx 5080 -16 gb gddr7 vram, 10,752 cuda cores, dlss 4, latest studio driver

memory: 128gb ddr5

storage: 4 tb samsung nvme ssd

os: windows 11 64-bit

Nath.veg wrote on 9/9/2025, 3:10 PM

Same here

I’ll start: I’m getting a texture bug when rendering here

 

J-Toresen wrote on 9/9/2025, 3:48 PM

@Nath.veg

Are you employed by Magix?

If not, you shouldn't pretend this is an "Official Bug & Issues Thread".

Jøran Toresen

jacknsb wrote on 9/9/2025, 3:48 PM

The Checkbox for "Make spacebar and F12 Play/Stop instead of Play/Pause" under the "Edit Visible Button Set" window is non-functional. The functionality can only be changed through the preferences menu.

VEGASDerek wrote on 9/9/2025, 8:21 PM

The Checkbox for "Make spacebar and F12 Play/Stop instead of Play/Pause" under the "Edit Visible Button Set" window is non-functional. The functionality can only be changed through the preferences menu.

The toggle appears to be working for me.

yoo-changyun wrote on 9/9/2025, 8:42 PM

When importing graphics with ProRes 4444 alpha, incorrect colors are displayed. On the left is the original color, which appears correctly in Vegas Pro 22. On the right, in Vegas Pro 23, it appears overexposed or shows only white with no color information.

 

 

 

yoo-changyun wrote on 9/9/2025, 8:46 PM

And another problem The Look LUT in Vegas Pro does not work when you add an external LUT. Vegas’s built-in LUT is applied, but applying an external LUT makes no difference. LUTs that worked fine in Vegas Pro 22 no longer apply in Vegas Pro 23.

wildgarlic wrote on 9/9/2025, 9:25 PM

Not sure if bug, but disabling hover scrub is not behaving as it did in Vegas 22. While it does disable trimming, it now still previews the video files causing unnecessary load on software/PC.

It is still called the "BYPASS HOVER SCRUB button" in the Vegas 23 (and 22) manual, however while holding the mouse over the button in Vegas 23 it instead says "Enable Hover Scrub Trimming." In the manual it still states when enabled, "the thumbnail doesn’t change and you are not scrubbing through the video."

WHE wrote on 9/10/2025, 4:00 PM

Vegas Pro 23 installed without incident. I have yet to use it for a project and have only opened and closed it twice. Both times it crashed while closing. Also my problem with all recent versions of Vegas remains. When I try to access the individual page for stock media I see three spinning dots. I can search without problem and in Vegas 23 I was able to download three times in a row directly to the time line so v23 is better than v22 in this regard. But still not practical. Anyone else having issues with the hub and/or stock media.

anthony-chiappette wrote on 9/10/2025, 8:37 PM

I cannot apply the Flicker Control FX to a video. If I do, and preview the video, video freezes but audio plays, and program locks up. I can't render either, it locks up. Removing the flicker control from the video events let the video play and render normally. I created a separate post about this.

ASUS Prime Z590-A Motherboard with Intel Core i7 11700 8 Core / 16 Thread 2.50GHZ, 64GB Crucial DDR4 3200 (4 x 16GB), nVidia GeForce RTX5060 8GB GDDR7, SoundBlaster X AE5 soundcard, 3 x 4TB Samsung 860 EVO SATA 3 SSD, 2 x 8TB Samsung 870 QVO SATA 3 SSD, 1 x 2TB Samsung 980 Pro NVME PICE4 SSD, 2 X WD 4 TB NVME PCIE3 SSD, 2 X Viewsonic HD monitors, LG Blu-Ray writer. Windows 11 (latest build), currently using Vegas Pro 22 latest build, and limited VP23 use to gauge performance and ease of use differences. Videos come from 2 x Sony HDR CX-405 Cameras, XAVC-S MP4 @ 50Mbps 1080P 60fps video files. (Previously: 2 x Canon HFR800 cameras, MP4 files at 1920 x 1080 60p 35Mbps).

anthony-chiappette wrote on 9/10/2025, 9:52 PM

UPDATE: I spoke too soon! The rendering froze solid at 70%. After I killed VP23, I reopened the project and rendered it again. This time it froze at 63%. I knew I should have waited to install this until the initial bugs were worked out. Now I have to do the project over from scratch in VP22.

ASUS Prime Z590-A Motherboard with Intel Core i7 11700 8 Core / 16 Thread 2.50GHZ, 64GB Crucial DDR4 3200 (4 x 16GB), nVidia GeForce RTX5060 8GB GDDR7, SoundBlaster X AE5 soundcard, 3 x 4TB Samsung 860 EVO SATA 3 SSD, 2 x 8TB Samsung 870 QVO SATA 3 SSD, 1 x 2TB Samsung 980 Pro NVME PICE4 SSD, 2 X WD 4 TB NVME PCIE3 SSD, 2 X Viewsonic HD monitors, LG Blu-Ray writer. Windows 11 (latest build), currently using Vegas Pro 22 latest build, and limited VP23 use to gauge performance and ease of use differences. Videos come from 2 x Sony HDR CX-405 Cameras, XAVC-S MP4 @ 50Mbps 1080P 60fps video files. (Previously: 2 x Canon HFR800 cameras, MP4 files at 1920 x 1080 60p 35Mbps).

jetdv wrote on 9/11/2025, 8:22 AM

@anthony-chiappette you might try going into the Preferences to the Video tab and the File I/O tab (you can test them separately) and see if changing off of the GPU makes a difference.

Nath.veg wrote on 9/11/2025, 9:43 AM

Someone know how to fix this visual bugs ?

RogerS wrote on 9/11/2025, 5:05 PM

@Nath.veg These are where the keyframes go for Fx now, no? See the TechDiveAV overview of new features.

Timbsi wrote on 9/11/2025, 8:52 PM

The way Vegas renders is very very fustrating to me. The audio always goes out of sync by one frame, no matter what I try to do. Legacy AVC decoding doesn't fix it, disabling the GPU decoding in Vegas doesn't work. The only time it syncs is when I render the video with the NVIDIA (RTX 5070) GPU with the "High Quality" preset, but that also brings another problem where the first frame of the audio doesn't exist instead it's replaced by the second frame of the audio. Worse is that the renders I made in previous versions are off sync. It's also the same problem with Vegas 22, worse with the nearly unfixable off sync for every imported video and render.

I've gotten a new fresh computer months ago, yet the latest Magix Vegas versions can't get syncing right at all.

RogerS wrote on 9/11/2025, 11:57 PM

I also see the audio sync issues too and depending on the media is up to 4 frames off with 22 and 23.

I just bought a 5070 and when I install it will see what's going on with high quality.

anthony-chiappette wrote on 9/12/2025, 12:27 AM

@anthony-chiappette you might try going into the Preferences to the Video tab and the File I/O tab (you can test them separately) and see if changing off of the GPU makes a difference.

No, it made no difference. The same auido playback only and program locks.

ASUS Prime Z590-A Motherboard with Intel Core i7 11700 8 Core / 16 Thread 2.50GHZ, 64GB Crucial DDR4 3200 (4 x 16GB), nVidia GeForce RTX5060 8GB GDDR7, SoundBlaster X AE5 soundcard, 3 x 4TB Samsung 860 EVO SATA 3 SSD, 2 x 8TB Samsung 870 QVO SATA 3 SSD, 1 x 2TB Samsung 980 Pro NVME PICE4 SSD, 2 X WD 4 TB NVME PCIE3 SSD, 2 X Viewsonic HD monitors, LG Blu-Ray writer. Windows 11 (latest build), currently using Vegas Pro 22 latest build, and limited VP23 use to gauge performance and ease of use differences. Videos come from 2 x Sony HDR CX-405 Cameras, XAVC-S MP4 @ 50Mbps 1080P 60fps video files. (Previously: 2 x Canon HFR800 cameras, MP4 files at 1920 x 1080 60p 35Mbps).

anthony-chiappette wrote on 9/13/2025, 3:49 PM

I came across this just now. I had a project loaded when VP23 was launched. I closed the project and the last displayed frame from the timeline remains in the preview window. See attached, empty project with video in the preview window.

 

ASUS Prime Z590-A Motherboard with Intel Core i7 11700 8 Core / 16 Thread 2.50GHZ, 64GB Crucial DDR4 3200 (4 x 16GB), nVidia GeForce RTX5060 8GB GDDR7, SoundBlaster X AE5 soundcard, 3 x 4TB Samsung 860 EVO SATA 3 SSD, 2 x 8TB Samsung 870 QVO SATA 3 SSD, 1 x 2TB Samsung 980 Pro NVME PICE4 SSD, 2 X WD 4 TB NVME PCIE3 SSD, 2 X Viewsonic HD monitors, LG Blu-Ray writer. Windows 11 (latest build), currently using Vegas Pro 22 latest build, and limited VP23 use to gauge performance and ease of use differences. Videos come from 2 x Sony HDR CX-405 Cameras, XAVC-S MP4 @ 50Mbps 1080P 60fps video files. (Previously: 2 x Canon HFR800 cameras, MP4 files at 1920 x 1080 60p 35Mbps).

anthony-chiappette wrote on 9/13/2025, 3:55 PM

One more issue, I shoot at 60p, but the timeline in VP23 only shows 30 fps measurements. In VP22, the timeline shows the correct 60 fps.

 

 

OH, Never mind. when I changed the view to time&frames, it now shows correctly.

Last changed by anthony-chiappette on 9/13/2025, 4:02 PM, changed a total of 2 times.

ASUS Prime Z590-A Motherboard with Intel Core i7 11700 8 Core / 16 Thread 2.50GHZ, 64GB Crucial DDR4 3200 (4 x 16GB), nVidia GeForce RTX5060 8GB GDDR7, SoundBlaster X AE5 soundcard, 3 x 4TB Samsung 860 EVO SATA 3 SSD, 2 x 8TB Samsung 870 QVO SATA 3 SSD, 1 x 2TB Samsung 980 Pro NVME PICE4 SSD, 2 X WD 4 TB NVME PCIE3 SSD, 2 X Viewsonic HD monitors, LG Blu-Ray writer. Windows 11 (latest build), currently using Vegas Pro 22 latest build, and limited VP23 use to gauge performance and ease of use differences. Videos come from 2 x Sony HDR CX-405 Cameras, XAVC-S MP4 @ 50Mbps 1080P 60fps video files. (Previously: 2 x Canon HFR800 cameras, MP4 files at 1920 x 1080 60p 35Mbps).

Len Kaufman wrote on 9/14/2025, 12:05 PM

Another weird phenomenon. In the past, the size of the trimmer box changed the configuration of the thumbnail screen. For example, if previously, you would see 8 rows of thumbnails across, if you expanded the trimmer screen to the left, it would reduce the number of rows to 6 or 4, etc. Now, if you expand the trimmer screen, it covers several rows. I usually leave the trimmer screen on all the time, as I use it a lot. So with the trimmer screen covering several rows, I couldn't find some clips I knew to be in the group. And when I render that segment out, the output is black. Thought I was losing it!

Sadlylate wrote on 9/14/2025, 1:22 PM

On Vegas 23 the qt7plug.dll is no longer being used when dragging in a .mov with alpha channels. Despite the depreciated option being ticked on.

Having the same issues as some of the users above where the Prores alternative seems incredibly bright.

Reyfox wrote on 9/14/2025, 1:53 PM

@VEGASDerek, like @jacknsb wrote,

The Checkbox for "Make spacebar and F12 Play/Stop instead of Play/Pause" under the "Edit Visible Button Set" window is non-functional. The functionality can only be changed through the preferences menu.

I too didn't see any change whether the box is check marked or not. And I too had to change it in the Preferences> General tab to get things to work as in previous Vegas versions.

Newbie😁

Vegas Pro 22 B250 (VP18-21 also installed)

Win 11 Pro 23H2 (Build 22631.5909)

AMD Ryzen 9 5950X 16 cores / 32 threads

64GB DDR4 3200 Patriot Viper

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, proDAD Vitascene V5 Pro and Mercalli V6.