Comments

Reyfox wrote on 11/14/2025, 3:49 AM

It is not only Ignite's lights and flares that do not work properly any more for me. If I go back a couple of years on my GPU driver, everything works. But I am using the latest GPU driver, and a lot of the plugins no longer work for me.

Most of the other Ignite plugins, no matter what, for me are hit and miss for the most part. And again, there is nothing that I would use in it that isn't available in Continuum.

NBFX works fine on my computer. I've had TotalFX for some time now and am using their latest build.

As for Artlist and their false promises, I knew as soon as they took over what was going to happen, told a friend of mine who also had Ignite and Hitfilm Pro, that it was the end. Especially when all the FXHome people were leaving who did so much to build up the community. I'm just glad I invested in Continuum some years ago for the perpetual, and have upgraded each year. It is an amazing kit of plugins.

Newbie😁

Vegas Pro 23 B356 (VP18-22 also installed)

Win 11 Pro 23H2 (Build 22631.6199)

AMD Ryzen 9 5950X 16 cores / 32 threads

64GB DDR4 3200 Patriot Viper

Sapphire RX6700XT 12GB Driver: 25.12.1

Gigabyte X570 Elite Motherboard

Panasonic G9, G7, FZ300

Boris FX Continuum Complete 2026, Newblue FX Total FX360, Ignite Pro V5, proDAD Vitascene V5 Pro and Mercalli V6 OFX

Dexcon wrote on 11/14/2025, 4:18 AM

I'm just glad I invested in Continuum some years ago for the perpetual, and have upgraded each year. It is an amazing kit of plugins.

I totally agree. Some 10 years ago I cross-graded from Red and Graffiti to BCC and have been on the BCC 'hamster-wheel' ever since. One of the great features of many BCC FX is access within the FX to basic Mocha (so not Mocha Pro) which allows spline masking/tracking thus limiting the FX to selected areas of the image.

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

13Year_User wrote on 11/19/2025, 1:44 PM

Vegas 23 Pro. Vegas Screen Capture is not working.
First time the Stop Button is not working.
Now i have now no screen is avaible to capture.

Same here in the trial

ISPanesLocos wrote on 12/10/2025, 3:55 PM

Hi, this is my problem, when I split an event with keyframes, the new half has the same keyframe pattern, even if the split was after the keyframes that now appear in this new half, do you know if it is a new feature of vp23 or if it is really a bug (if it is the first, how do I turn this off? It's annoying)

Reyfox wrote on 12/11/2025, 5:04 AM

Don't add the keyframes before splitting? You are splitting something with them included. They will be there, should they not?

Newbie😁

Vegas Pro 23 B356 (VP18-22 also installed)

Win 11 Pro 23H2 (Build 22631.6199)

AMD Ryzen 9 5950X 16 cores / 32 threads

64GB DDR4 3200 Patriot Viper

Sapphire RX6700XT 12GB Driver: 25.12.1

Gigabyte X570 Elite Motherboard

Panasonic G9, G7, FZ300

Boris FX Continuum Complete 2026, Newblue FX Total FX360, Ignite Pro V5, proDAD Vitascene V5 Pro and Mercalli V6 OFX

Dexcon wrote on 12/11/2025, 5:29 AM

... when I split an event with keyframes, the new half has the same keyframe pattern, even if the split was after the keyframes that now appear in this new half ...

It has always been thus. One way to get around that issue is to render the video event with pan/crop keyframes in place and then split the rendered video - the keyframing is then already embedded in the rendered video. If fearing generational loss by rendering, use a no loss render such as an applicable ProRes render template or an applicable .AVI render with custom settings set to 'Uncompressed'.

@ISPanesLocos

Last changed by Dexcon on 12/11/2025, 5:29 AM, changed a total of 1 times.

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

ISPanesLocos wrote on 12/11/2025, 7:30 AM

... when I split an event with keyframes, the new half has the same keyframe pattern, even if the split was after the keyframes that now appear in this new half ...

It has always been thus. One way to get around that issue is to render the video event with pan/crop keyframes in place and then split the rendered video - the keyframing is then already embedded in the rendered video. If fearing generational loss by rendering, use a no loss render such as an applicable ProRes render template or an applicable .AVI render with custom settings set to 'Uncompressed'.

@ISPanesLocos

But this only happend me in VP 23 in another versions (22,21,18) the new part of event after divide dont duplicate keyframes,and another detail that I forgot to mention is that it only happens in the keyframes of the effects, such as Image in Image here a video: