Is there a way to switch playback buffer without having to restart PT?

[DeyBwah]

I can't switch my playback buffer rate without having to restart PT... and even if I do, sometimes the whole thing bugs out; after closing PT and trying to open it again, it says it didn't close down properly and I need to reboot.

Just wondering if others are having success changing the playback, and maybe if someone had issues and resolved them, they could share their experiences.

This is really proving to be a headache as my workflow requires switching between 32 and 512 for tracking or mixing in PT.


SiSoftware Sandra

Computer
Model : Gigabyte X58A-UD3R
Workgroup : WORKGROUP
Host Name : i7Pro
User : Dey Bwah

Processor
Model : Intel(R) Core(TM) i7 CPU 930 @ 2.80GHz
Speed : 2.83GHz
Cores per Processor : 4 Unit(s)
Threads per Core : 2 Unit(s)
Type : Quad-Core
Integrated Data Cache : 4x 32kB, Synchronous, Write-Thru, 8-way, 64 byte line size, 2 threads sharing
L2 On-board Cache : 4x 256kB, ECC, Synchronous, ATC, 8-way, 64 byte line size, 2 threads sharing
L3 On-board Cache : 8MB, ECC, Synchronous, ATC, 16-way, Exclusive, 64 byte line size, 8 threads sharing

Computer
Mainboard : Gigabyte X58A-UD3R
BIOS : Award (Phoenix) FA 04/20/2010
Bus(es) : X-Bus PCI PCIe IMB USB FireWire/1394 i2c/SMBus
Multi-Processor (MP) Support : No
Multi-Processor Advanced PIC (APIC) : Yes
Total Memory : 12GB DIMM DDR3

Chipset
Model : Giga-Byte X58 I/O Hub
Front Side Bus Speed : 2x 2.43GHz (4.86GHz)

Chipset
Model : Giga-Byte Core Desktop (Bloomfield) UnCore
Front Side Bus Speed : 2x 2.43GHz (4.86GHz)
Total Memory : 12GB DIMM DDR3
Channels : 3
Memory Bus Speed : 2x 540MHz (1GHz)

Memory Module(s)
Memory Module : Corsair CMX4GX3M2A1600C9 2GB DIMM DDR3 PC3-12800U DDR3-1600 (9-9-9-24 5-34-10-5)
Memory Module : Corsair CMX4GX3M2A1600C9 2GB DIMM DDR3 PC3-12800U DDR3-1600 (9-9-9-24 5-34-10-5)
Memory Module : Corsair CMX4GX3M2A1600C9 2GB DIMM DDR3 PC3-12800U DDR3-1600 (9-9-9-24 5-34-10-5)
Memory Module : Corsair CMX4GX3M2A1600C9 2GB DIMM DDR3 PC3-12800U DDR3-1600 (9-9-9-24 5-34-10-5)
Memory Module : Corsair CMX4GX3M2A1600C9 2GB DIMM DDR3 PC3-12800U DDR3-1600 (9-9-9-24 5-34-10-5)
Memory Module : Corsair CMX4GX3M2A1600C9 2GB DIMM DDR3 PC3-12800U DDR3-1600 (9-9-9-24 5-34-10-5)

Video System
Video Adapter : NVIDIA GeForce GTX 460 (336 SM5.0 810MHz, 768MB, PCIe 2.00 x16)

Graphics Processor
OpenCL Processor : NVIDIA GeForce GTX 460 (224SP 7C 810MHz, 738.4MB)
CUDA Processor : NVIDIA GeForce GTX 460 (224SP 7C 810MHz, 738.4MB)
Compute Shader Processor : NVIDIA GeForce GTX 460 (336SP 810MHz, 738.4MB)

Storage Devices
GRAID 2TB (RAID) : 2TB (G:)
WDC WD6401AALS-00L3B2 (640.1GB, SATA300, 3.5", 7200rpm, NCQ, 32MB Cache) : 596GB (C:) (D:)
SAMSUNG HD103SJ (1TB, SATA300, 3.5", 7200rpm, NCQ, 32MB Cache) : 932GB (E:)
SAMSUNG HD103SJ (1TB, SATA300, 3.5", 7200rpm, NCQ, 32MB Cache) : 932GB (F:)
HL-DT-ST DVDRAM GH22LS50 (SATA150, DVD+-RW, CD-RW, 2MB Cache) : 3GB (H:)

Logical Storage Devices
Backup (G:) : 2TB (NTFS) @ GRAID 2TB (RAID)
WinXP (D:) : 188GB (NTFS) @ WDC WD6401AALS-00L3B2 (640.1GB, SATA300, 3.5", 7200rpm, NCQ, 32MB Cache)
Audio Files (E:) : 932GB (NTFS) @ SAMSUNG HD103SJ (1TB, SATA300, 3.5", 7200rpm, NCQ, 32MB Cache)
Samples (F:) : 932GB (NTFS) @ SAMSUNG HD103SJ (1TB, SATA300, 3.5", 7200rpm, NCQ, 32MB Cache)
Win7_x64 (C:) : 409GB (NTFS) @ WDC WD6401AALS-00L3B2 (640.1GB, SATA300, 3.5", 7200rpm, NCQ, 32MB Cache)
Body Target ABS (H:) : 3GB (UDF) @ HL-DT-ST DVDRAM GH22LS50 (SATA150, DVD+-RW, CD-RW, 2MB Cache)

Peripherals
LPC Hub Controller 1 : Giga-Byte LPC Interface Controller
LPC Legacy Controller 1 : ITE IT8720F
Audio Device : EVGA GF104 High Definition Audio Controller
Audio Codec : nVidia 0012h
Audio Codec : nVidia 0012h
Audio Codec : nVidia 0012h
Audio Device : Xilinx RME Hammerfall DSP MADI
Disk Controller : Giga-Byte 4 port SATA IDE Controller
Disk Controller : Giga-Byte 2 port SATA IDE Controller
Disk Controller : Giga-Byte 88SE91A3 SATA-600 Controller
Disk Controller : Giga-Byte JMB36X PCIE-to-SATAII/IDE RAID Controller
Disk Controller : Giga-Byte JMB36X PCIE-to-SATAII/IDE RAID Controller
Disk Controller : Giga-Byte JMB36X PCIE-to-SATAII/IDE RAID Controller
USB Controller 1 : Giga-Byte USB UHCI Controller #4
USB Controller 2 : Giga-Byte USB UHCI Controller #5
USB Controller 3 : Giga-Byte USB UHCI Controller #6
USB Controller 4 : Giga-Byte USB EHCI Controller #2
USB Controller 5 : Giga-Byte USB UHCI Controller #1
USB Controller 6 : Giga-Byte USB UHCI Controller #2
USB Controller 7 : Giga-Byte USB UHCI Controller #3
USB Controller 8 : Giga-Byte USB EHCI Controller #1
FireWire/1394 Controller 1 : Giga-Byte TSB43AB23 1394a-2000 OHCI PHY/link-layer Controller
SMBus/i2c Controller 1 : Intel 801xx/63xx SMBus

Printers and Faxes
Printer : Microsoft XPS Document Writer (600x600, Colour)
Fax : Microsoft Shared Fax Driver (200x200)

Network Services
Network Adapter : Realtek PCIe GBE Family Controller (Ethernet, 100Mbps)

Power Management
Mains (AC) Line Status : On-Line

Operating System
Windows System : Microsoft Windows 7 Home 6.01.7600
Platform Compliance : x64

Windows Experience Index
Current System : 5.9

[daeron80]

You mean the H/W Buffer Size in the Playback Engine settings? I can change that all day and never restart PT.

[DeyBwah]

Originally Posted by daeron80

You mean the H/W Buffer Size in the Playback Engine settings? I can change that all day and never restart PT.

Yep, that's what I mean. Thanks for the help.

[mykhal c]

Originally Posted by DeyBwah

Yep, that's what I mean. Thanks for the help.

whatz up DeyBwah!! you have 'run as admin' checked when runnin' PT, right? and for that matter, i recommend runnin' all audio related apps with 'run as admin' on...

[sunburst79]

No problem with changing buffer sizes or playback engines here. But...I only have Digi interfaces. This applies to both Mac and PC.

I suspect that the manufacterers driver for your interface may have something to do with your issue.

[DeyBwah]

Originally Posted by mykhal c

whatz up DeyBwah!! you have 'run as admin' checked when runnin' PT, right? and for that matter, i recommend runnin' all audio related apps with 'run as admin' on...

Hey man!

Yep, I tried runnin' it as admin, but when I go to change the h/w buffer size, it only shows the size I'm already running. No other options. If I try to change it from my RME control panel, it says I need to restart PT for the changes to take effect.

What a bummer. One of the big reasons for my upgrade was being able to use my interface with PT, that was the BIG + with PT9 after all.

Just kick me while I'm down AVID.

[DeyBwah]

Originally Posted by sunburst79

No problem with changing buffer sizes or playback engines here. But...I only have Digi interfaces. This applies to both Mac and PC.

I suspect that the manufacterers driver for your interface may have something to do with your issue.

Hey sunburst,

I don't think there's anything wrong with my manufacture's drivers.. I can change buffer playback all day long in REAPER. I can change sample rates, master/slave clock, etc...

DigiTech, any word on if AVID is working on a upcoming patch?

[TOM@METRO]

Hey DeyBwah,

I don't believe there is anything wrong with RME drivers per say, but simply that the PT9 software has not been fine tuned yet for all the various 3rd party hardware to run as simply as the Avid hardware. I have seen this myself on other devices that I have. I usually choose 128 and live with it.

[guitardom]

you cannot change the HW buffer with ANY asio interface w/o restarting. they are well aware of this and spoke to them imediately after i found this. they gave the technical reasons. basically i came out of it not being confident a fix will be anytime soon.

[sunburst79]

Originally Posted by guitardom

you cannot change the HW buffer with ANY asio interface w/o restarting. they are well aware of this and spoke to them imediately after i found this. they gave the technical reasons. basically i came out of it not being confident a fix will be anytime soon.

That was my point about it being driver dependent. Somewhere theres a post by Digi stating something along those lines. And yes its due to how the manufacterer writes the driver or how the driver interacts with PT. The take away message is that some interfaces seem to work better than others.