PT11 Video Engine Problems

[blizzard]

Hey All,

I recently upgraded to PT11 thinking that the Video Engine errors would be fixed by the time we got to 11.3 - sadly not the case. I am getting a constant error:

"There was a problem stopping Pro Tools"

This happens immediately after I get video freezing. I have tried to open the same session in PT10.3.9 and get very bad stuttering. Maybe there is something I have setup incorrectly?

Any advice would be great.

SiSoftware Sandra

ID
Host Name : althor
Workgroup : WORKGROUP

Computer
Model : OEM System Product Name
Serial Number : System Ser**********
Chassis : Desktop
Mainboard : ASUS P9X79
Serial Number : 1311186********
BIOS : AMI (OEM) 4608 12/24/2013
Total Memory : 32GB DIMM DDR3

Processors
Processor : Intel(R) Core(TM) i7-4820K CPU @ 3.70GHz (4C 8T 3.9GHz, 3.9GHz IMC, 4x 256kB L2, 10MB L3)
Socket/Slot : FC LGA2011

Chipset
Memory Controller : ASUS Core (Ivy Bridge-E) DMI2 100MHz
Memory Controller : ASUS Core (Ivy Bridge-E) Integrated Memory Controller 0 Target Address/Thermal Registers 100MHz, 4x 8GB DIMM DDR3 1.6GHz 256-bit

Memory Module(s)
Memory Module : Corsair CMZ32GX3M4X1600C10 8GB DIMM DDR3 PC3-12800U DDR3-1600 (9-9-9-25 4-33-10-5)
Memory Module : Corsair CMZ32GX3M4X1600C10 8GB DIMM DDR3 PC3-12800U DDR3-1600 (9-9-9-25 4-33-10-5)
Memory Module : Corsair CMZ32GX3M4X1600C10 8GB DIMM DDR3 PC3-12800U DDR3-1600 (9-9-9-25 4-33-10-5)
Memory Module : Corsair CMZ32GX3M4X1600C10 8GB DIMM DDR3 PC3-12800U DDR3-1600 (9-9-9-25 4-33-10-5)

Video System
Monitor/Panel : Samsung SyncMaster
(1680x1050, 22.0")
Monitor/Panel : Samsung SyncMaster
(1920x1080, 21.5")
Monitor/Panel : Samsung SyncMaster
(1920x1080, 21.5")
Video Adapter : NVIDIA GeForce GTX 660 (5CU 960SP SM5.0 1GHz/1.24GHz, 384kB L2, 2GB 6GHz 192-bit, PCIe 2.00 x16)
Video Adapter : NVIDIA GeForce GTX 660 (5CU 960SP SM5.0 1GHz/1.24GHz, 384kB L2, 2GB 6GHz 192-bit, PCIe 2.00 x16)
Video Adapter : NVIDIA GeForce GTX 660 (5CU 960SP SM5.0 1GHz/1.24GHz, 384kB L2, 2GB 6GHz 192-bit, PCIe 2.00 x16)

Graphics Processor
OpenCL GP Processor : NVIDIA GeForce GTX 660 (960SP 5C 1GHz/1.24GHz, 384kB L2, 2GB 6GHz 192-bit)
Compute Shader Processor : NVIDIA GeForce GTX 660 (960SP 5C 1GHz/1.24GHz, 384kB L2, 2GB 6GHz 192-bit)
CUDA GP Processor : NVIDIA GeForce GTX 660 (960SP 5C 1GHz/1.24GHz, 384kB L2, 2GB 6GHz 192-bit)

Storage Devices
Samsung SSD 840 EVO 250GB (250GB, SATA600, SSD) : 233GB (F:)
Samsung SSD 840 EVO 250GB (250GB, SATA600, SSD) : 233GB (E:)
KINGSTON SV300S37A120G (120GB, SATA600, SSD) : 112GB (C:)
WDC WD1001FALS-00E8B0 (1TB, SATA300, 3.5", 7200rpm, 32MB Cache) : 932GB (G:)
WDC WD5001AALS-00L3B2 (500.1GB, SATA300, 3.5", 7200rpm, 32MB Cache) : 466GB (H:)
ASMT109x - Config (104.9MB, USB3) : 100MB
ASUS DRW-24F1ST a (SATA150, DVD+-RW, CD-RW, 768kB Cache) : N/A (D:)

Logical Storage Devices
SAMPLES 2 (F:) : 233GB (NTFS) @ Samsung SSD 840 EVO 250GB (250GB, SATA600, SSD)
SAMPLES 1 (E:) : 233GB (NTFS) @ Samsung SSD 840 EVO 250GB (250GB, SATA600, SSD)
Hard Disk (C:) : 112GB (NTFS) @ KINGSTON SV300S37A120G (120GB, SATA600, SSD)
SAMPLES 3 (G:) : 932GB (NTFS) @ WDC WD1001FALS-00E8B0 (1TB, SATA300, 3.5", 7200rpm, 32MB Cache)
PROJECTS (H:) : 466GB (NTFS) @ WDC WD5001AALS-00L3B2 (500.1GB, SATA300, 3.5", 7200rpm, 32MB Cache)
Optical Drive (D:) : N/A @ ASUS DRW-24F1ST a (SATA150, DVD+-RW, CD-RW, 768kB Cache)

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 GK106 HDMI Audio Controller
Audio Codec : nVidia GeForce 6800 [NV40.1]
Serial Port(s) : 1
Disk Controller : ASUS Patsburg 6 Port SATA AHCI Controller
Disk Controller : ASUS Asmedia 106x SATA Controller
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 : ASUS VT6315 Series Firewire Controller
FireWire/1394 Controller 2 : Adaptec FW322/323 IEEE1394 OHCI 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 (600x600, Colour)
Fax : Microsoft Shared Fax Driver (200x200)
Printer : HP Deskjet 5400 Series (600x600, USB, Colour)

Network Services
Network Adapter : Intel(R) 82579V Gigabit Network Connection (Ethernet)
Network Adapter : Intel(R) Gigabit CT Desktop Adapter (Ethernet, 1Gbps)

Operating System
Windows System : Microsoft Windows 7 Ultimate 6.01.7601 (Service Pack 1)
Platform Compliance : x64

Windows Experience Index
Current System : 7.4

[Craig F]

moving to the correct section PSV

[blizzard]

Thanks for the move...

[blizzard]

I tried restoring a fresh OS install and reinstalled all of my software, including PT11.3.0. I am still getting this error. But now what happens is the video begins to play, but the transport does not move within PT. So, video is rolling but PT is not. I get the "There was a problem stopping Pro Tools" error.

[seanmccoy]

Originally Posted by blizzard

I tried restoring a fresh OS install and reinstalled all of my software, including PT11.3.0. I am still getting this error. But now what happens is the video begins to play, but the transport does not move within PT. So, video is rolling but PT is not. I get the "There was a problem stopping Pro Tools" error.

I'm still seeing this fairly regularly as well. Though in my case, the session will run fine for awhile before I get the error. It's especially bad if I'm trying to record into a project with video. Interestingly, I've found that I've been able to stop the runaway video a couple of times by changing the buffer size. How's that for a clunky workaround during a session?

[blizzard]

That is exactly what I just did to get this session up and running again. I changed the buffer size. I was using the 003R line 1/2 as default playback device and changed it to internal audio card (this hasn't caused any problems for me before, but I know it is recommended to not set it this way). I run at 512 because of VEPRO latency issues and for some reason my session had switched to 256 and I got the error. When switching it back to 512, it is running fine (knocks on wood).

[kkfaudio]

I tend to get this error with low data rate QT files - generally H264s from the client. Restarting PT will allow things to work fine for a while, but once transcoded to DNx I don't see the error anymore.

[seanmccoy]

Originally Posted by kkfaudio

I tend to get this error with low data rate QT files - generally H264s from the client. Restarting PT will allow things to work fine for a while, but once transcoded to DNx I don't see the error anymore.

Not here. I'm using exclusively DNx files and still get the error.

[Schottlandru]

Not that this is the same issue you are experiencing, but I get "run away" video too. Disabling the QT track lets audio play, but not while the video is running (as if play and stop flags for audio and video got stuck swapped).

I can make it recover though by scrubbing in an audio track, i.e. Windows+drag or I think it was Ctrl+drag on OSX.
Does this work as a quick fix for you guys?
Hope so :-\
Andrew

[blizzard]

I've been using H264s recently so maybe I'll try a different codec. Any others that people here would recommend trying for stability? I don't currently have software that enables DNx.

I will try the audio scrubbing and see if that makes a difference.