Video color changes when applying some plugins in VP 17

Veg wrote on 8/12/2019, 11:13 AM

This problem does not occurs on all plugins. It happens randomly when applying some plugins like Twixtor and Boris FX Sapphire for example. It seems to be something that affects some plugins and others not.

Picture demonstration

Screen record

Comments

fr0sty wrote on 8/12/2019, 11:14 AM

Can you isolate which ones it is? It may help to single out the issue causing them.

adis-a3097 wrote on 8/12/2019, 11:23 AM

Leme guess: it's the GPU accelerated ones? 🙂

Veg wrote on 8/12/2019, 11:44 AM

I disabled the GPU and still have the same problem.

Marco. wrote on 8/12/2019, 11:49 AM

Similar with NB ColorFast here. It's a luma shift (offset) of about 2 or 3 R'G'B' values.

It does not happen with my DFT filter collection where I have the GPU support disabled (inside the plug-in, not in Vegas Pro).

Edit:
I just saw exactly same happens with ColorFast in VP16 and VP15. So this must be something different.

Sr_Garcia wrote on 8/12/2019, 1:02 PM

I have the same problem with Transitions and Plugins.
I have activated/deactivated the Acceleration GPU and everything is just as bad...
It doesn't happen to me with Vegas Pro V16
It is impossible to edit with this problem(!)...

bitman wrote on 8/12/2019, 2:42 PM

No issue here so far, but that does not mean that there is no issue. I tried a few newblue colorfast (and also colorfast2), some boris and sapphire. No color shift (yet) on my PC...

Current system: VP 17 (edit), VP16 (suite) build 424, VP15 (suite) build 416, Magix Video Pro X (VPX11), Corel VS ultimate 2019, a lot of NEWBLUE plugins, Titler Pro 6, Mercalli 4.0, Respeedr, Vasco Da Gamma 12, VASST stuff, Production Assistent pro3, Boris Continuum 2019, Davinci Resolve Studio 16 b...

  • OS: Windows 10 Pro 64, version 1903
  • CPU: der8auer i7-8700K (advanced edition), default speed (no overclock), Cooler: Noctua NH-D15s
  • RAM: G.Skill Trident Z 3200C14 DDR4 64GB, XMP set to profile 1 in BIOS
  • Videocard: NVIDEA RTX 2080Ti (Founders edition), NVIDEA studio drivers
  • Monitor: LG 38 inch ultra-wide (21x9) - yes upgraded from 34 to 38, I can see more tracks now! Resolution: 3840x1600
  • C-drive: Samsung NVMe SSD 2TB 960 pro
  • Data storage: WD gold 6TB + WD Yellow 4TB
  • MOBO: Gigabyte Z370 Aorus Gaming 7
  • PS: Corsair HX1200i, Case: Silverstone fortress 2, shuttlePROv2, Keyboard and mouse: Logitech G910 and G700s (and now Evoluent Vertical Mouse)

Before November 2018: NVIDEA Gibabyte GTX 1080ti

Before November 2017: windows 10 Pro 64, i7-4790k, mem: DDR3 16GB GTX TITAN X (Maxwell)

 

AVsupport wrote on 8/13/2019, 8:22 AM

had some spookey preview corruption with 4K xavcs clips on a 1080 timeline with some track fx applied, that looked awefully like a memory overrun to the gpu accelerated plugins. had to exit and restart. unresolved. details tomorrow

my current Win10/64 system (latest drivers, water cooled) :

Intel Coffee Lake i5 Hexacore (unlocked, but not overclocked) 4.0 GHz on Z370 chipset board,

16GB (2x8GB Corsair Dual Channel DDR4-2133) XMP-3000 RAM,

Intel 600series 512GB M.2 SSD system drive running Win10/64 home automatic driver updates,

4TB 7200RPM NAS HGST data drive,

Intel HD630 iGPU - currently disabled in Bios,

nVidia GTX1060 6GB, always on latest [creator] drivers. nVidia HW acceleration enabled.

main screen 4K/50p 1ms scaled @175%, second screen 1920x1080/50p 1ms.

Richvideo wrote on 8/13/2019, 9:19 AM

This problem does not occurs on all plugins. It happens randomly when applying some plugins like Twixtor and Boris FX Sapphire for example. It seems to be something that affects some plugins and others not.

Picture demonstration

Screen record

I am getting the same thing when applying the most recent version of Neat Video 5 to a clip, however I found if you also drop in the Boris Continuum Complete Color Balance filter with the Neat one the color goes back to normal--no need to adjust any settings it just jumps back to normal. I need to do a test render to see if the color stays correct over a long clip when using this workaround.

Update: This fixes the color in the preview monitor but it will not render-When using the RTX 2080ti GPU to render it says stream not found and when I switch it to the MainConcept codec it starts to render but then seems to go into a memory overrun and Neat video crashes

 

AVsupport wrote on 8/14/2019, 12:32 AM

 Using ColorFast2, Sharpen and Skin Touch Up lead to video preview corruption. The corruption persisted in the actual clip, so when disabling the FX, the original corrupted clips would still play back.

NewBlueFX [V6 180730] are nvidia GPU enabled. I saw default Preferences>File IO>HardwareDecoder was intel QSV. I have disabled my iGPU. Changed default to nVidia, which has 'somewhat' improved the situation (less crash prone) due to better performance.

But not sure what's causing this? Load= CPU~60%, GPU~29, 6.6GB =~50% RAM.

Also changed the chain of FX to GPU users first, CPU after.

Shall try nVidia creator drivers next

 

Last changed by AVsupport on 8/14/2019, 12:34 AM, changed a total of 1 times.

my current Win10/64 system (latest drivers, water cooled) :

Intel Coffee Lake i5 Hexacore (unlocked, but not overclocked) 4.0 GHz on Z370 chipset board,

16GB (2x8GB Corsair Dual Channel DDR4-2133) XMP-3000 RAM,

Intel 600series 512GB M.2 SSD system drive running Win10/64 home automatic driver updates,

4TB 7200RPM NAS HGST data drive,

Intel HD630 iGPU - currently disabled in Bios,

nVidia GTX1060 6GB, always on latest [creator] drivers. nVidia HW acceleration enabled.

main screen 4K/50p 1ms scaled @175%, second screen 1920x1080/50p 1ms.

Grazie wrote on 8/14/2019, 1:09 AM

@AVsupport - Wow! - That IS severe. I'm just checking CF2. Prevew has "some" but then I rendered and it appears calmed down.

Last changed by Grazie on 8/14/2019, 1:10 AM, changed a total of 1 times.

Grazie

PC 7 64-bit 16gb * Intel® Core™i7-2600k Quad Core 3.40GHz * 2GB NVIDIA GEFORCE GTX 560 Ti

PC 10 64-bit 64gb * Intel® Core™i9 - 3.3GHz * 40Gb NVIDIA  GeForce RTX 2070

Cameras: Canon XF300 + PowerShot SX60HS Bridge

AVsupport wrote on 8/14/2019, 10:55 PM

whilst re-installing NewBlue FX didn't seem to help, changing to nVidia Creator drivers certainly improved the situation. Recommendable @Grazie

/add: whilst the preview looks better, the rendered output file remains corrupt [using Magix HEVC / nVenc].

/add: this might be related to the Dynamic RAM memory leak; FIX see Nick hopes post here:

https://www.vegascreativesoftware.info/us/forum/faq-how-can-i-stop-vegas-pro-hanging-or-crashing-during-rendering--104786/

 

Last changed by AVsupport on 8/15/2019, 12:16 AM, changed a total of 3 times.

my current Win10/64 system (latest drivers, water cooled) :

Intel Coffee Lake i5 Hexacore (unlocked, but not overclocked) 4.0 GHz on Z370 chipset board,

16GB (2x8GB Corsair Dual Channel DDR4-2133) XMP-3000 RAM,

Intel 600series 512GB M.2 SSD system drive running Win10/64 home automatic driver updates,

4TB 7200RPM NAS HGST data drive,

Intel HD630 iGPU - currently disabled in Bios,

nVidia GTX1060 6GB, always on latest [creator] drivers. nVidia HW acceleration enabled.

main screen 4K/50p 1ms scaled @175%, second screen 1920x1080/50p 1ms.

Sr_Garcia wrote on 8/16/2019, 9:36 AM

I have spent many hours making adjustments in Vegas Pro 17 to try to get this issue fixed.
Everything is just as bad! This does not work !!
IMPOSSIBLE to edit in these circumstances!

If with the same PC and the same settings, with Vegas Pro 16, EVERYTHING worked fine, the conclusion seems clear: the error is in the new Vegas Pro 17

Sr_Garcia wrote on 8/16/2019, 10:33 AM

Thank you, pierre-k, for your collaboration!
I had already tried your suggestion and... nothing: everything is still just as bad.


I guess we will have to wait for an update to solve these problems (which did not exist in VP-16)...😟

Richvideo wrote on 8/16/2019, 9:14 PM

Thank you, pierre-k, for your collaboration!
I had already tried your suggestion and... nothing: everything is still just as bad.


I guess we will have to wait for an update to solve these problems (which did not exist in VP-16)...😟

Well they updated Boris Sapphire yesterday so maybe that will fix some of the issues for those of you who use it

https://borisfx.com/release-notes/

Sr_Garcia wrote on 8/17/2019, 2:15 AM

Mmmm... everything is the same for me (bad...) 😒
I think the problem is not the plugins, the problem is in the Program (VP-17).

harry-worth wrote on 8/17/2019, 2:35 AM

The only way to work around it for me is... If I add a BORIS FX ( Continuum Complete 2019  - 12.5.0 ) and the colour changed then I also add the BCC Colour Balance FX to the same Media and without adjusting any of the sliders it corrects the colour.

If I then add another BCC FX ( say BCC MOCHA ) and the colours change I just Un-Tick the BCC Colour Balance to correct it.

I have tried the new BCC Continuum 2019 12.5.1 ( Trial ) but it is the same with that.

So at the moment it is workable for me...  as a quick Tick or Un-Tick only takes a few seconds..

I guess it will get sorted soon..

Sr_Garcia wrote on 8/18/2019, 10:29 AM

The only way to work around it for me is... If I add a BORIS FX ( Continuum Complete 2019  - 12.5.0 ) and the colour changed then I also add the BCC Colour Balance FX to the same Media and without adjusting any of the sliders it corrects the colour.

Confirmed !! 😏

Hopefully this problem will be solved quickly...

DeTomasi wrote on 8/18/2019, 10:38 AM

The only way to work around it for me is... If I add a BORIS FX ( Continuum Complete 2019  - 12.5.0 ) and the colour changed then I also add the BCC Colour Balance FX to the same Media and without adjusting any of the sliders it corrects the colour.

Confirmed !! 😏

Hopefully this problem will be solved quickly...

This workaround worked... Thank you Mr

harry-worth wrote on 8/18/2019, 11:13 AM

Thanks for the feedback. Always welcome for reports of if things work or not….  Nice one..

Sr_Garcia wrote on 8/19/2019, 2:31 AM

This (temporary) solution is no longer effective if any transition is incorporated...

During the transition the error appears in the color. 😕

For me, it is IMPOSSIBLE to edit with VP17 currently.

harry-worth wrote on 8/19/2019, 2:41 AM

I just add the BCC Colour Balance to the next bit of media after the transition. So each media had BCC Colour Balance added and then either Ticked or Un-ticked to correct the colour on that particular bit of media..  I know it is not the actual solution but it is working for me until a correct Bug is sorted

pierre-k wrote on 8/21/2019, 4:40 AM

This is the problem of the cracked version. Install the officiall version and your problem will be solved.