Same HSL FX, same project, looks horrible in SVP12.770, perfectly OK in SVP11.701

[Norman Black]

[Stephen Crye] “The HSL effect in SVP12 *seemed* to initially be a GPU accelerated; not sure how to tell by inspection which version was in the chain.”

HSL Adjust is one of the GPU accelerated effects. GPU accelerated effects are in the GPU accelerated folder in the Video Fx pane, and/or when the effect is selected in the list you can see its properties listed at the bottom of the pane where the presets are listed.

If GPU is enabled in your video prefs AND the effect is GPU enabled then GPU is used.

I don’t have any VP11 to VP12 setup to compare. I have typically used color corrector to adjust saturation and I compared color corrector against HSL adjust. I did notice a significant difference between the two is a very bright area (light colored ground). The HSL adjust clipped out and lost detail and color corrector was very smooth. Actually in this case it looks like the effect was rolled off in the extreme highs. They both had about the same effect in the mids. The same value, 1.15, seemed to give about the same effect.

From that little test, I will personally stick with color corrector. Maybe color corrector can give you what you want.

If you have a project, you can setup to show the difference from VP11 to VP12, then send that project in to Sony support. Maybe there is a bug. Since video files are so big you would be best have to whittle down to minimal clip to demo.

[Stephen Crye]

Norman, thanks for weighing in on this. I felt so alone …

In the last 30 minutes I have determined that the problem mostly effects extreme highs. But the problem is absent in SVP11; it can easily apply HSL regardless of the levels without the banding or shift. Also, it does not have the problem where even the default with Saturation set to 1.0 causes the banding and color shift.

I found a work-around – use the Sony Saturation Adjust, which does not exhibit the problem.

But, I am beginning to smell a bug. HSL for a quick bit of extra saturation was easy and fast, I don’t want to give it up. Yes, I will file a report with Sony, but I am sooo tired of being a beta tester.

[Norman Black] “If GPU is enabled in your video prefs AND the effect is GPU enabled then GPU is used.”

OK, this gets even weirder. In both SVP11 and SVP12, regardless of which version of the HSL effect is chosen, the description at the bottom of the window stays the same. It does not matter what the project settings are – 8-bit, 32-bit, etc. I have tried restarting Vegas, that also has no effect. No matter which group the HSL effect is selected from, the description says: Sony HSL Adjust: OFX, 32-bit floating point, GPU accelerated, Grouping Sony\Color, Version 1.0 Description: From Sony Creative Software Inc.

Win7 Pro X64 on Dell T7500, MultiTB SATA, 8GB RAM, nVidia Quadro 2000, Vegas 12, 11, 10, 9 DVDA 6.0 & 5.2(build 135) Sony HDR-CX550V, Panasonic GH3 with LUMIX G X VARIO 12-35mm / F2.8 ASPH, LUMIX G X VARIO 35-100mm / F2.8

[Norman Black]

Of course the effect description will not change. All that description is telling you is what modes the effect can operate in.

It is assumed that all effects work with 8-bit data so it never says anything about that. If an effect can work in 32-bit floating mode it will say so. If is can work with GPU accel it will say so.

If your project is 32-bit and you are using the effect then of course you are using the 32-bit floating implementation of the effect.

[Norman Black]

I can confirm that this seems to be a bug in VP12 HSL adjust. I downloaded a VP11 trial and tried the one position in a clip I have.

In VP11, HSL adjust and color corrector are the same. Both good in highs and everywhere else. In VP12 the highs get clipped and posterized.

I have not yet isolated if this is a GPU implementation bug as yet. I am going to put together a whittled project to send to Sony that demonstrates this problem.

EDIT: It appears to be a bug in the VP12 GPU algorithm. CPU only in video prefs and all is fine. VP11 is fine GPU on or off.

EDIT: EDIT: I submitted a bug report to Sony with an example VEG file.

[Stephen Crye]

[Norman Black] “It appears to be a bug in the VP12 GPU algorithm. CPU only in video prefs and all is fine. VP11 is fine GPU on or off.”

Thanks, Norman. I had lost track of which tests I had done in CPU mode vs GPU mode. I confirm that HSL in CPU mode works OK, but in GPU mode results in clipping and posterization. Sony Saturation works OK (at least for my mid-tones test) in both CPU and GPU modes.

Steve

Win7 Pro X64 on Dell T7500, MultiTB SATA, 8GB RAM, nVidia Quadro 2000, Vegas 12, 11, 10, 9 DVDA 6.0 & 5.2(build 135) Sony HDR-CX550V, Panasonic GH3 with LUMIX G X VARIO 12-35mm / F2.8 ASPH, LUMIX G X VARIO 35-100mm / F2.8

[Stephen Crye]

Hi Norman;

How did you “submit a bug report?”

I still have no answer from Sony on the support ticket I opened on 1/30/14 for the problem with Google+ YouTube integration breaking “upload to YouTube.”
https://forums.creativecow.net/readpost/24/974126

I tried to get on Live Chat support today, but after waiting in the queue for over an hour, the system kicked me off because their 2-hour “lunch” window had started.

Is there an official way to submit a bug report?

Thanks,

Steve

Win7 Pro X64 on Dell T7500, MultiTB SATA, 12GB RAM, nVidia Quadro 2000, Vegas 12, 11, 10, 9 DVDA 6.0 & 5.2(build 135) Sony HDR-CX550V, Panasonic GH3 with LUMIX G X VARIO 12-35mm / F2.8 ASPH, LUMIX G X VARIO 35-100mm / F2.8