RE: Issues with FX from older versions

lotsedits wrote on 1/10/2026, 4:23 PM

Hi everyone! I have recently upgraded from Vegas Pro 19 to Vegas Pro 23 and filter packages that I have created and been using in Vegas 19, now look entirely different! They are exactly the same, no changes made anywhere but I can't wrap my head around what's going on!

Any suggestions?

Comments

Dexcon wrote on 1/10/2026, 5:45 PM

...  filter packages that I have created and been using in Vegas 19, now look entirely different! 

How so? Please explain exactly how they look different. To assist, it would be helpful if you would take screenshot of how one looks in VP19 and another image of how the same custom filter looks in VP23 - there's an upload button in the header when making a new comment on the forum so links to 3rd party download sites aren't necessary.

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition; Samsung S23 Ultra smart phone

Installed: Vegas Pro 13, 15, 16, 17, 18, 19, 20, 21, 22 & 23, HitFilm Pro 2021.3, DaVinci Resolve Studio 20.3, BCC 2026, Mocha Pro 2026, NBFX TotalFX 7, Neat NR 6, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 12, iZotope RX11 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11 25H2

Dell Alienware Aurora 11:

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

 

LAPTOP:

Dell Inspiron 5310 EVO 13.3"

i5-11320H CPU

C Drive: 1TB Corsair Gen4 NVMe M.2 2230 SSD (upgraded from the original 500 GB SSD)

Monitor is 2560 x 1600 @ 60 Hz

zzzzzz9125 wrote on 1/10/2026, 7:10 PM

@lotsedits Unfortunately, VP23 has indeed made changes to the plugin chain (filter package) feature. See: https://www.vegascreativesoftware.info/us/forum/fx-plugin-chooser-presets-can-t-be-deleted-or-renamed-vegas-23--150526/#ca947125

Although I don't know exactly what you mean by "different", it's most likely caused by this change.

lotsedits wrote on 1/11/2026, 1:27 PM

@Dexcon @zzzzzz9125 Thank you for your comments. I realise now I should have included an example. Just using this screenshot of a tv show for example.

 

So this image (top) was coloured using Vegas Pro 19 - this is how it should look. It doesn't contain anything overly complicated: Sharpen, Unsharp Mask, Channel Blend, Colour Curves & then when I upgraded to Vegas pro 23 - this is how it looks (bottom) and as you can see there is a HUGE change.

Friends have told me Channel Blend might be the issue, I've taken it out, re-added it, changed it - nothing is working. I just want to be able to rely on the filter packages I have.

Thanks in advance for any ideas you may have.

Dexcon wrote on 1/11/2026, 4:59 PM

I've tested those FX in a chain in my VP23 and they seem to be working as expected.

One thing to check though ... has the FX Bypass button inadvertently been activated?

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition; Samsung S23 Ultra smart phone

Installed: Vegas Pro 13, 15, 16, 17, 18, 19, 20, 21, 22 & 23, HitFilm Pro 2021.3, DaVinci Resolve Studio 20.3, BCC 2026, Mocha Pro 2026, NBFX TotalFX 7, Neat NR 6, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 12, iZotope RX11 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11 25H2

Dell Alienware Aurora 11:

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

 

LAPTOP:

Dell Inspiron 5310 EVO 13.3"

i5-11320H CPU

C Drive: 1TB Corsair Gen4 NVMe M.2 2230 SSD (upgraded from the original 500 GB SSD)

Monitor is 2560 x 1600 @ 60 Hz

Steve_Rhoden wrote on 1/12/2026, 1:43 AM

How did you save those "filter packages" and how did you import them in the new Vegas Pro 23?

That can have some bearing to why you are having this mismatch.

lotsedits wrote on 1/12/2026, 2:08 PM

@Steve_Rhoden I assure you this isn’t the issue. I’ve saved them as a filter package, I’ve even recreated the colouring using the steps. There’s something going on with Vegas itself.

lotsedits wrote on 1/12/2026, 2:08 PM

@Dexcon Thank you for your suggestion! I will check this out at the next opportunity I get

3POINT wrote on 1/12/2026, 2:25 PM

In VP23 changes have been made to the Video Effects Package Management:

"Video Effects Packages have been redesigned to provide more flexibility to users so they can store chains of Video Effects that can be used over again on multiple tracks, events or even between projects."

If this has any influence on filter packages made in earlier Vegas versions, I don't know, till now I didn't discover issues with the filter packages I made in earlier versions.

@lotsedits to find out, I think a complete rebuild of the filter package in VP23 is an option.

lotsedits wrote on 1/12/2026, 2:41 PM

Thanks @3POINT it seems to be more a consistent issue with how VP23 is processing some of the actual FX now as opposed to how the filter package is being made. I’ve saved it, imported it, rebuilt it - the issue seems to be the same. I’ve spoken to some friends in my editing community & I think the issue seems to be with channel blend and possibly some other Video FX - I just wish I knew if there was a work around, like a setting I could turn off or something, you know???

anthony-chiappette wrote on 1/12/2026, 4:22 PM

Have you tried moving things around in the chain? Some effects work differently based on where they are placed in the chain.

I used to have issues with the border fx with PIP video, it would create the border differently based on where the effect is placed in the chain. And it still does, but at least now in V23 you can use a border around a cropped image by placing the border effect at the end.

Last changed by anthony-chiappette on 1/12/2026, 4:22 PM, changed a total of 1 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).

3POINT wrote on 1/12/2026, 8:55 PM

@anthony-chiappette with a filter package you save the complete chain of used filters (even used keyframes). So a filter package should give the same result in every Vegas version.