Win 8.1, HD Native, PT 11.1.2, and Waves issues

[manichouse]

Hi all,
Running into some issues with the above config. When loading any session with Waves plugins (latest release) at a low buffer setting (32 or 64), initially clicking on the Waves plugin to open the GUI will cause massive CPU spike in Pro Tools 11 and throw 90XX errors. Hovering the mouse over their GUI's also causes spikes. Oddly enough, after running the session for a while and after opening and closing the Waves GUI's, the spiking stops and the session runs perfectly. I do not have this issue on my Win7 partition, (or on the Hackintosh side)... only in Win 8.1. I can run any sessions at a buffer of 32 all day long without problems on those. I've done all the usual troubleshooting, disabling devices, swapped pcie slots, and even changed from Nvidia graphics to ATI and the issue persists. Also adjusted gpu performance settings in Nvidia control panel which actually helped slightly but not enough. Any other suggestions? It seems to be Waves' use of OpenGL causing issues once again. Thanks!! Sandra report below:

SiSoftware Sandra
ID
Host Name : DAW-PC
Workgroup : WORKGROUP
Computer
Model : OEM System Product Name
Serial Number : System Ser**********
Chassis : Desktop
Mainboard : ASUS P9X79 WS
Serial Number : ST20230********
BIOS : AMI (OEM) 4505 12/05/2013
Total Memory : 16GB DIMM DDR3
Processors
Processor : Intel(R) Core(TM) i7-3930K CPU @ 3.20GHz (6C 4.17GHz/7.18GHz, 4.16GHz IMC, 6x 256kB L2, 12MB L3)
Socket/Slot : FC LGA2011
Chipset
Memory Controller : ASUS Core DMI2 (Sandy Bridge-E) 126MHz
Memory Controller : ASUS Core (Sandy Bridge-E) Integrated Memory Controller Registers 126MHz, 4x 4GB DIMM DDR3 1.34GHz 256-bit
Memory Module(s)
Memory Module : G.Skill F3-12800CL9-4GBXL 4GB DIMM DDR3 PC3-12800U DDR3-1600 (11-11-11-29 5-40-13-6)
Memory Module : G.Skill F3-12800CL9-4GBXL 4GB DIMM DDR3 PC3-12800U DDR3-1600 (11-11-11-29 5-40-13-6)
Memory Module : G.Skill F3-12800CL9-4GBXL 4GB DIMM DDR3 PC3-12800U DDR3-1600 (11-11-11-29 5-40-13-6)
Memory Module : G.Skill F3-12800CL9-4GBXL 4GB DIMM DDR3 PC3-12800U DDR3-1600 (11-11-11-29 5-40-13-6)
Video System
Monitor/Panel : Dell Computer DELL 2007WFP
(1680x1050, 20.1")
Monitor/Panel : Dell Computer DELL 2007WFP
(1680x1050, 20.1")
Video Adapter : NVIDIA GeForce GTX 670 (7CU 1344SP SM5.0 914MHz/1.2GHz, 512kB L2, 2GB 6GHz 256-bit, PCIe 2.00 x16)
Video Adapter : NVIDIA GeForce GTX 670 (7CU 1344SP SM5.0 914MHz/1.2GHz, 512kB L2, 2GB 6GHz 256-bit, PCIe 2.00 x16)
Graphics Processor
OpenCL GP Processor : NVIDIA GeForce GTX 670 (1344SP 7C 914MHz/1.2GHz, 512kB L2, 2GB 6GHz 256-bit)
Compute Shader Processor : NVIDIA GeForce GTX 670 (1344SP 7C 914MHz/1.2GHz, 512kB L2, 2GB 6GHz 256-bit)
CUDA GP Processor : NVIDIA GeForce GTX 670 (1344SP 7C 914MHz/1.2GHz, 512kB L2, 2GB 6GHz 256-bit)
Storage Devices
Crucial M4-CT256M4SSD2 (256GB, SATA600, 2.5", SSD) : 238GB (C:) (F:)
Crucial M4-CT256M4SSD2 (256GB, SATA600, 2.5", SSD) : 238GB
Seagate ST3000DM001-9YN166 (3TB, SATA600, 3.5", 7200rpm) : 3TB (D:)
Seagate ST1500DM003-9YN16G (1.5TB, SATA600, 3.5", 7200rpm) : 1TB
Seagate ST1500DM003-9YN16G (1.5TB, SATA600, 3.5", 7200rpm) : 1TB
WDC WD5000BMVW-11AJGS1 (500.1GB, USB3/SATA300, 2.5", 5400rpm, 8MB Cache) : 466GB (E:)
SanDisk Cruzer (16GB, USB2) : 15GB (I:)
PLEXTOR DVDR PX-L890SA (SATA150, DVD+-RW, CD-RW) : N/A (G:)
Logical Storage Devices
System Reserved : 350MB (NTFS)
WinMedia (D:) : 470GB (NTFS) @ Seagate ST3000DM001-9YN166 (3TB, SATA600, 3.5", 7200rpm)
Air Music (E:) : 466GB (NTFS) @ WDC WD5000BMVW-11AJGS1 (500.1GB, USB3/SATA300, 2.5", 5400rpm, 8MB Cache)
Removable Drive (I:) : 15GB (exFAT) @ SanDisk Cruzer (16GB, USB2)
Win8.1 (C:) : 139GB (NTFS) @ Crucial M4-CT256M4SSD2 (256GB, SATA600, 2.5", SSD)
Win7 (F:) : 99GB (NTFS) @ Crucial M4-CT256M4SSD2 (256GB, SATA600, 2.5", SSD)
Optical Drive (G:) : N/A @ PLEXTOR DVDR PX-L890SA (SATA150, DVD+-RW, CD-RW)
Peripherals
LPC Hub Controller 1 : ASUS Patsburg LPC Controller
LPC Legacy Controller 1 : T0 C3-33
Audio Device : ASUS Patsburg High Definition Audio Controller
Audio Codec : Realtek Semi High Definition Audio
Audio Device : ASUS GK104 HDMI Audio Controller
Audio Codec : nVidia GeForce 6800 Ultra [NV40.0]
Audio Codec : 1 0001
Serial Port(s) : 1
Disk Controller : ASUS Patsburg 6 Port SATA AHCI Controller
Disk Controller : ASUS 88SE9128 PCIe SATA 6 Gb/s RAID controller with HyperDuo
USB Controller 1 : ASUS Patsburg USB2 Enhanced Host Controller #2
USB Controller 2 : ASUS Patsburg USB2 Enhanced Host Controller #1
USB Controller 3 : ASUS ASMedia XHCI Controller
USB Controller 4 : ASUS ASMedia XHCI Controller
FireWire/1394 Controller 1 : Avlab Technology XIO2213A PCI Express to 1394b OHCI with 3-Port PHY
FireWire/1394 Controller 2 : ASUS VT6315 Series Firewire Controller
SMBus/i2c Controller 1 : Intel ICH SMBus
SMBus/i2c Controller 2 : Intel SNB-E XMB Ch 0 SMBus
SMBus/i2c Controller 3 : Intel SNB-E XMB Ch 1 SMBus
Printers and Faxes
Printer : Microsoft XPS Document Writer v4 (600x600, Colour)
Fax : Microsoft Shared Fax Driver (200x200)
Peripherals
Media Player : SanDisk Cruzer (14.9GB)
Media Player : WD My Passport 07A8 (465.73GB)
Network Services
Network Adapter : Intel(R) 82574L Gigabit Network Connection (Ethernet, 1Gbps)
Operating System
Windows System : Microsoft Windows 8.1 Home 6.03.9600
Platform Compliance : x64

[Shan]

Unfortunately, Waves doesn't support multi-graphic card systems (http://duc.avid.com/showpost.php?p=2086264&postcount=9). There is a thread dedicated to this issue here (http://duc.avid.com/showthread.php?t=344809). In case you haven't already, make sure you do the Avid recommended Windows 8 optimizations (http://avid.force.com/pkb/articles/en_US/troubleshooting/Windows-8-Optimizations?popup=true&NewLang=en&DocType=1078&q=Optimizations&spell=1&site=kbase&q=windows+8+optimizations&x=-1369&y=-20).

I'll try and get TOM@METRO to chime in, as he's been dealing with this and might have a workaround.

Shane

[manichouse]

Thanks for your input Shane. I'm not sure why Sandra is showing two gtx 670's, but there is only one video card installed. Both displays are driven by the single card. And the same rig works perfectly fine in Win7 or Mavericks with Waves. Will keep troubleshooting...

[TOM@METRO]

This is not exactly the troubling issue Waves is famous for, (the multiple card issue), but it may well be related.

Waves uses a graphics code that has been a nightmare for many of us, and it may well be popping up here in another form.

Be sure you have updated your video drivers, if that doesn't help, start trying older driver versions and see if you have better luck.

Waves is aware of this issue. I have have had lengthy discussions with them, both with customer service at at the NAMM show. They (at this point) do not have the expertise to easily fix these video issues.

We are hoping that version 10 will see a solution, if that ever appears. :rolleyes:

[manichouse]

Thanks Tom. All drivers are current. Even tried swapping the card out for an ATI 6850 that I have here and the problem is the same (actually worse with the ATI). However, if I switch to the stock generic Windows driver on either the gtx670 or the 6850, the issue goes away and the performance is perfect... amazing actually. Obviously, I can only use one display with that driver though. I have noticed that when first opening a waves gui, the gpu will clock up which I believe is what's causing the spike. Izotope also uses OpenGL on the Insight plugin and that works flawlessly, without causing a spike. Just Waves... will keep experimenting. Thanks again!

[TOM@METRO]

Thanks Tom. All drivers are current. Even tried swapping the card out for an ATI 6850 that I have here and the problem is the same (actually worse with the ATI). However, if I switch to the stock generic Windows driver on either the gtx670 or the 6850, the issue goes away and the performance is perfect... amazing actually. Obviously, I can only use one display with that driver though. I have noticed that when first opening a waves gui, the gpu will clock up which I believe is what's causing the spike. Izotope also uses OpenGL on the Insight plugin and that works flawlessly, without causing a spike. Just Waves... will keep experimenting. Thanks again!

Interesting about Izotope. Waves is blaming a huge part of their issue on Open GL.