Vegas Pro and Movie Studio 'Vegas HSL Plugin' Error

Brandigan wrote on 4/9/2018, 5:49 AM

This plugin is common to all versions of Vegas and is v1.0 in the 'about' section of the plugin.

Basically it goes loopy when it's applied, even when the sliders are at default 'do nothing' settings.

It causes the upper ranges to go out of bounds, so you get a big, overbright smeary section on things like skies, or bright surfaces. No amount of adjust the available sliders can bring those things back into range either. They're just permanently mangled.

A sort of workaround is use Curves, just before it, to bring the whole range down quite a lot (so bright white is more of a muddy grey) then it can be applied to...push the brightness back up where it was before without it going out of range.

See the before and after when it should be doing nothing...yet.

http://i854.photobucket.com/albums/ab106/pickaname2/HSL%20Off.jpg
http://i854.photobucket.com/albums/ab106/pickaname2/HSL%20On.jpg

Comments

matthias-krutz wrote on 4/9/2018, 6:59 AM

The HSL plugin has been redesigned with VEGAS Pro 15 Update 1 (build 216). Unfortunately the version number stayed the same. The described error should be corrected.

Desktop: Ryzen R7 2700, RAM 32 GB, X470 Aorus Ultra Gaming, Radeon RX 5700 8GB, Win10 2004

Laptop: T420, W10, i5-2520M 4GB, SSD, HD Graphics 3000

VEGAS Pro 14-18, Movie Studio 12 Platinum, Vegasaur, HOS, HitfilmPro

Brandigan wrote on 4/9/2018, 7:02 AM

OK, so only having Vegas Pro 14, Vegas Movie Studio 14,15, how do I get hold of that?

NickHope wrote on 4/10/2018, 1:21 AM

The release notes for VP15 build 216 said:

"HSL Adjust plug-in no longer causes color banding in 8bit GPU or 32bit CPU projects"

I don't ever remember the color banding issue being discussed on the forum.

I just did some brief tests in VP14 build 270 and VP15 build 321 using a generated media gradient and some GH4 UHD footage. I don't see any difference in their behaviour. For me, neither changes levels like in your screenshots. Both introduce banding at default settings in an 8-bit project.

matthias-krutz wrote on 4/10/2018, 2:07 AM

I don't ever remember the color banding issue being discussed on the forum.

It was here in the German forum.

Brandigan wrote on 4/10/2018, 2:43 AM
 

I just did some brief tests in VP14 build 270 and VP15 build 321 using a generated media gradient and some GH4 UHD footage. I don't see any difference in their behaviour. For me, neither changes levels like in your screenshots. Both introduce banding at default settings in an 8-bit project.

Well, it's easy to reproduce. Just take this .JPG image and add the HSL Adjust plugin to it.

Turn on your scopes and you'll see there is nothing special about it, although I find pushing the highlights into the magenta space seems to trigger it more easily.

And it's not banding so much as clipping, although the top several colours all do change to only 2 or 3: white with something around the edges that's not even close to the originals.



http://i854.photobucket.com/albums/ab106/pickaname2/HSL_Error.jpg

 

NickHope wrote on 4/10/2018, 3:07 AM

Could you share that on a different site? The direct jpg link redirects to an html page embedding the image and right click > "save images as" saves a corrupt jpeg.

Brandigan wrote on 4/10/2018, 3:15 AM

Could you share that on a different site? The direct jpg link redirects to an html page embedding the image and right click > "save images as" saves a corrupt jpeg.

The link goes to Photobucket where you can Right Click and Save As with the correct image name once you are there. Or clicking on the embedded image in the post opens it up on this site; where you can Right-Click and Save As, when this site gives it a randomly long name, but the image is not corrupted. I just tried it both ways.

NickHope wrote on 4/10/2018, 3:47 AM

Thanks. The 2nd method worked.

I'm still not seeing the behaviour that you are seeing. Just a bit of banding gets introduced, indicated by the black gaps in the histograms. This was recorded in VP14 build 270, and it's similar in VP15 build 321. VMS15 appears similar (there are no scopes in VMS to verify).

(I should have recorded that at "Best (full)" but it's near enough the same.)

Which version and build are your screengrabs from?

Brandigan wrote on 4/10/2018, 4:28 AM

VP 14.0 build 270 , VMS 14.0 build 148 and VMS 15.0 build 116.

It's the GPU acceleration. I turned it off the problem nearly went away.

It still changes just very slightly, as it does in your video - watch the scopes - just not nearly as much. Well that's annoying. Faithful old GTX580 is good for everything else.

If you want to see the scopes change in VMS, the demo version of NewBlue ColorFast 2 has them and they work fine, despite the watermark.
 

NickHope wrote on 4/10/2018, 4:40 AM

You're right. The top end goes completely nuts in VP14 build 270 with GPU acceleration on. In VP15 build 321 not a single pixel on the scopes moves, which surprised me because GPU-accelerated normally degrades FX quality if anything, not improves it. VMS Platinum 15 build 116 seems to be the same behaviour as VP15, which I'd expect.

Brandigan wrote on 4/10/2018, 4:43 AM

So, how likely is it that I could use the plugin from VP15 build 321 in VP 14 and/or VMS 15?

As you have all versions, would you be able to confirm if swapping the plugin would fix the problem?

Where would I get it from anyway? Not upgrading for just that.

NickHope wrote on 4/10/2018, 4:53 AM

I don't actually know where that plugin is stored. I did have a quick look earlier. I doubt you'd be able to use the VP15 plugin legally if you don't own a license for it. If you have VMS15 and the plugin is an actual specific file (i.e. not compiled into a more general file) and you can locate where it is then it would be worth seeing if it works to drop it into the VP14 file structure. Lots of "ifs" there.

Brandigan wrote on 4/10/2018, 5:06 AM

Yes, I know there are a lots of "ifs", but knowing if it works would be a start. :)
 

NickHope wrote on 4/11/2018, 2:24 AM

If you have VMS15 and VP14 like you say you do then you could try copying the VMS15 version of that the VP14 version of that file and see what happens. Even if it works, I expect you'll be missing some other FX that are VP-only. The VMS file is smaller. It also might officially be against the terms of use.

Brandigan wrote on 4/11/2018, 2:30 AM

VMS15 has the same issue, so that wouldn't be a fix, unfortunately.

NickHope wrote on 4/11/2018, 9:42 AM

VMS15 has the same issue, so that wouldn't be a fix, unfortunately.

VMS15 Platinum build 116 does not show the same issue for me.

Brandigan wrote on 4/11/2018, 9:57 AM

Does for me. You have GPU turned on?

Former user wrote on 4/11/2018, 10:35 AM

This is a bug that happens in the HSL plugin when the GPU is enabled. Here I solve it by changing the settings in the properties box as shown below.

This error no longer occurs in vegas pro 15 build 321

NickHope wrote on 4/11/2018, 10:57 AM

Does for me. You have GPU turned on?

Yes. An old AMD HD 6970 with driver 15.7.1.

matthias-krutz wrote on 4/11/2018, 11:21 AM

@Former user

It also happens if I set project properties to 32-bit full range and view transform to "Off". I tested it with color gradient and VP14.

Desktop: Ryzen R7 2700, RAM 32 GB, X470 Aorus Ultra Gaming, Radeon RX 5700 8GB, Win10 2004

Laptop: T420, W10, i5-2520M 4GB, SSD, HD Graphics 3000

VEGAS Pro 14-18, Movie Studio 12 Platinum, Vegasaur, HOS, HitfilmPro

Former user wrote on 4/11/2018, 2:03 PM

@matthias-krutz

Did you test in Vegas Pro 15 Build 321? Here is ok

matthias-krutz wrote on 4/11/2018, 2:19 PM

Yes, I know.

Desktop: Ryzen R7 2700, RAM 32 GB, X470 Aorus Ultra Gaming, Radeon RX 5700 8GB, Win10 2004

Laptop: T420, W10, i5-2520M 4GB, SSD, HD Graphics 3000

VEGAS Pro 14-18, Movie Studio 12 Platinum, Vegasaur, HOS, HitfilmPro