Starburst broken - GPU Acceleration

Shivaxi wrote on 7/12/2024, 12:27 PM

This has been a problem since at least Vegas 16. I've tried newer Vegas versions all the way up to the latest Vegas 21 and the problem remains. The Starburst effect renders differently depending on if you have "GPU Acceleration Of Video Processing" turned on in the video settings. Specifically the main difference is if the option "Center Burst" in the Starburst effect is turned up. You get a residual image of whatever you applied the starburst effect on casting to the upper left. Looks like this:

With "Center Burst" all the way down, you get this:

If I max "Center Burst" again and change to "Points" to 2 only and leave the 45 degree angle from bottom left to top right, you can really see this effect and its issue:

The distance of the 'ghost image' moves further away the more you increase the "Radius" option.

Now if I restart Vegas and disable "GPU Acceleration Of Video Processing", this is what the effect looks like with "Center Burst" maxed:

This to me looks far more correct of how it's supposed to look. However there's plugins and effects that rely on GPU Acceleration (such as Picture In Picture), so disabling GPU Accel isn't a good solution. Starburst with GPU Accel off also has other strange artifacting, such as some strange cut off lines when increasing the Radius too far:

Or even weirder dupe images at the edges of the burst if you're at a specific radius like 20 and with Center Burst maxed:

I have tested actually rendering out to see if it was just a preview thing, but it does actually render the way it shows here in the preview window in Vegas, both with GPU Accel on and off, which seems to change how the effect renders. I really like this effect (when it works) and would love to see this get fixed at some point.

Comments

Reyfox wrote on 7/17/2024, 5:37 AM

I don't have a simple image to test, but using your settings with the image below, I am not seeing the issue. But you have given no real information on what version and build of Vegas and what are your computer specs. There is zero information in your User Profile. And if this issue has persisted since, as you say, VP16, why hasn't it been reported before?

MikeS wrote on 7/17/2024, 6:43 AM

Yes, I can see the same thing

Shivaxi wrote on 11/10/2025, 2:58 PM

I don't have a simple image to test, but using your settings with the image below, I am not seeing the issue. But you have given no real information on what version and build of Vegas and what are your computer specs. There is zero information in your User Profile. And if this issue has persisted since, as you say, VP16, why hasn't it been reported before?

What is wrong with you lol. What are you trying to insinuate here? That I'm a bot? That I'm making sh*t up? There's zero information on my profile because I made this account literally just to post this bug. And I don't know why it hasn't been reported before, it's possible people just think it's working as intended and leave GPU acceleration on, who knows. Also "no real information on what version and build of vegas and what are your computer specs" I quite plainly listed Vegas 16 all the way to Vegas 21, it happens in all versions since at least Vegas 16 UP TO 21. My computer specs don't matter. Another user already confirmed, so I'm going to guess you didn't test this correctly and actually tried GPU acceleration on vs off. You even admitted you didn't have an image to test. Literally go download any PNG and actually test it before spewing nonsense and trying to insinuate I'm some AI bot or something, good lord.

bitman wrote on 11/11/2025, 1:47 AM

@Shivaxi You need to tone down here, and be more respectful. First of all, most are volunteers here, and I happen to know @Reyfox as being a helpful and respected volunteer. What he is suggesting is that you provide more info, not that you are a bot. And version build of Vegas, windows software version, computer specs and source file actually do matter in 99% of the cases.
As you are suggesting this is a GPU acceleration issue, did you ever consider this maybe related to computer specs? @Reyfox does not see the issue, but has an AMD GPU, @MikeS has an NVIDEA GPU, so that already maybe a clue. But what about you? So you see computer specs do matter.
If you want the developers to be able to fix this, they need to know how to simulate this. Like any company they will fix this only if they have the time and resources, meaning they may never fix this if this is on the bottom of their priority list.