newblue auto contrast in V14 different than V15

bitman wrote on 7/7/2018, 3:58 AM

I was testing the latest Vegas patch with the new Nvidia HEVC Nvec encoding support on an older V14 project opened in V15, and the resulting encoding quality was NOK (washed out, details lost etc...). I first blamed NVEC encoding, but that turned out not to be the issue. The real issue was the plugin "auto contrast" from Newblue wich I used a lot in that project. Strangely enough I needed to reduce by a very significant amount the intensity setting in the plugin to get the look and detail when opened in Vegas 15 to what I had in the past in Vegas 14 timeline view and the rendered result. As far as I know I never changed nor updated the plugin sw itself. So why is Vegas 15 requiring a change in the setting of this plugin?

Anyone experiencing the same issue?

 

Last changed by bitman

Current system: VP16 (suite) build 307, VP15 (suite) build 384, Magix video pro X, Corel VS ultimate 2018, a lot of NEWBLUE plugins, Titler Pro 6, Mercalli 4.0, respeedr, Vasco Da Gamma 11, VASST stuff, Production Assistent pro3,...

  • OS: Windows 10 Pro 64, version 1803
  • 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)
  • 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)

 

Comments

bitman wrote on 7/11/2018, 1:04 AM

Bump,

Can someone offer any explanation?

Last changed by bitman on 7/11/2018, 12:16 PM, changed a total of 1 times.

Current system: VP16 (suite) build 307, VP15 (suite) build 384, Magix video pro X, Corel VS ultimate 2018, a lot of NEWBLUE plugins, Titler Pro 6, Mercalli 4.0, respeedr, Vasco Da Gamma 11, VASST stuff, Production Assistent pro3,...

  • OS: Windows 10 Pro 64, version 1803
  • 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)
  • 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)

 

OldSmoke wrote on 7/11/2018, 11:07 AM

Make sure the project settings are exactly the same.

bitman wrote on 7/11/2018, 12:14 PM

Make sure the project settings are exactly the same.

That may be a difficult one to compare or remember what it was, when installing Vegas 15 when it came out in 2017, I uninstalled 14, and the V14 created project was dormant on my hard drive. It was untouched by 15 and now opened for the first time in Vegas 15 with the afore mentioned issue...

Is there maybe something different under the hood of V15 concerning color or contrast or related OFX treatment versus V14?

 

Last changed by bitman on 7/11/2018, 12:15 PM, changed a total of 1 times.

Current system: VP16 (suite) build 307, VP15 (suite) build 384, Magix video pro X, Corel VS ultimate 2018, a lot of NEWBLUE plugins, Titler Pro 6, Mercalli 4.0, respeedr, Vasco Da Gamma 11, VASST stuff, Production Assistent pro3,...

  • OS: Windows 10 Pro 64, version 1803
  • 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)
  • 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)

 

Red Prince wrote on 7/11/2018, 12:36 PM

It was untouched by 15 and now opened for the first time in Vegas 15 with the afore mentioned issue...

Sounds like your project settings are exactly the same, then.

He who knows does not speak; he who speaks does not know.
                    — Lao Tze in Tao Te Ching

Can you imagine the silence if everyone only said what he knows?
                    — Karel Čapek (The guy who gave us the word “robot” in R.U.R.)

jetdv wrote on 7/11/2018, 4:41 PM

@bitman, I would suggest you contact NewBlue support and send them the file in question as well as any comparison images you can provide.