Error: ASIO device properties changed in control panel

[Joe.LoDuca]

Folks,

I want to give DUC one chance to keep me as a AVID user. I am coming extremely close to making the decision to just cut ProTools lose
and go with some other software. And based on the fact that this issue has been around us for 3 SOLID SOFTWARE VERSIONS (PT9-11) tells me that it will never be fixed. So dropping PT is likely going to be the fix but. Trying to make this work as advertised. I shouldn't feel this way but, I am ok with paying for techsupport - but I have gone that path with PT9 and it got me absolutely nowhere with less money. I am thinking today would be much the same. I thought I had this working but apparently not.

Here's the deal, anyone, please look over everything, what I've done, Sandra, etc. If anything is gleaming and blaring out as a problem, I would really love to hear your recommendation. I think I am out of ideas other than something that isn't Protools.

I am using 2 versions of PT, 10.3.6 and 11.2.2 - sound hardware wants to be Presonus SL24.4.2 with latest firmware. Ever since PT9, AVID
brags about the fact that you can now use other sound harware over and above your DIGI-RACK2 or whatever. So, I am just trying this "as
advertised". I am constantly getting a "ASIO device properties changed in control panel" - and I wish rebooting or relaunching this once would fix it, but nooooooo.. -we can't have that, can we?

Here is what I did so far:
- I always make sure windows DOES NOT USE the same sound card as PT. I shut off ALL sounds on window and give it the default (on the motherboard)
sound card for that reason.
- Originally, I was using the firewire400 on my GigaByte X58A-UD3R, but to get a second opinion, I also tried Belkin Firewire400 you see
on SANDRA and got the
exact same issues.
- I am using presonus version 1.72 now but tried 1.71 and 1.7 and of course this did nothing for me.
- in the control panel of Presonus, there are a couple of modes. "Normal, safe mode1, safe mode2" - I have tried them all, no help.
- I have deleted prefs, tuned microsoft.. its playing A 440 now!
- I have reinstalled PT multiple times, multiple versions too ( not that I thought that would do anything, it hasn't been right since the beginning of PT9)
- Also in the control panel, there is some MAPPINGs that I originally didn't like the sound of. We have 8 WDM's which I think are Windows Media channels or something.. They were originally mapped to the first 8 inputs and outputs of my presonus board. Not liking the looks of it, I deleted ALL those mappings so now there is no connection between my mixer channels and WDM. launched PT and NO GO!



So.. Here is a totally up to date SANDRA:

ID
Host Name : JoeLoDuca-PC
Workgroup : WORKGROUP

Computer
Model : GigaByte X58A-UD3R
Chassis : GigaByte Desktop
Mainboard : GigaByte X58A-UD3R
BIOS : Award (OEM) FB 08/24/2010
Total Memory : 16GB DIMM DDR3

Processors
Processor : Intel(R) Core(TM) i7 CPU 950 @ 3.07GHz (4C 3.1GHz, 2.16GHz IMC, 4x 256kB L2, 8MB L3)
Socket/Slot : FC LGA1366

Chipset
Memory Controller : Gigabyte X58 I/O Hub 2x 2.43GHz (4.86GHz)
Memory Controller : Gigabyte Core Desktop (Bloomfield) UnCore 2x 2.43GHz (4.86GHz), 3x 8GB DIMM DDR3 1.08GHz 192-bit

Memory Module(s)
Memory Module : Kingston KHX1600C9D34GX 4GB DIMM DDR3 PC3-12800U DDR3-1600 (9-9-9-25 4-34-10-5)
Memory Module : Kingston KHX1600C9D34GX 4GB DIMM DDR3 PC3-12800U DDR3-1600 (9-9-9-25 4-34-10-5)
Memory Module : Kingston KHX1600C9D34GX 4GB DIMM DDR3 PC3-12800U DDR3-1600 (9-9-9-25 4-34-10-5)
Memory Module : Kingston KHX1600C9D34GX 4GB DIMM DDR3 PC3-12800U DDR3-1600 (9-9-9-25 4-34-10-5)
Memory Module : Kingston KHX1600C9D34GX 4GB DIMM DDR3 PC3-12800U DDR3-1600 (9-9-9-25 4-34-10-5)
Memory Module : Kingston KHX1600C9D34GX 4GB DIMM DDR3 PC3-12800U DDR3-1600 (9-9-9-25 4-34-10-5)

Video System
Monitor/Panel : (Standard monitor types) Generic Non-PnP Monitor
Video Adapter : Standard VGA Graphics Adapter (PCIe 1.00 x16)

Graphics Processor

Storage Devices
WDC WD1001FALS-00Y6A0 (1TB, SATA300, 3.5", 7200rpm, 32MB Cache) : 932GB (C:) (D:)
WDC WD5000AAKS-22V1A0 (500.1GB, SATA300, 3.5", 7200rpm, 16MB Cache) : 466GB (H:)
WDC WD1003FBYX-01Y7B1 (1TB, SATA300, 3.5", 7200rpm) : 932GB (I:)
WDC WD1003FBYX-01Y7B0 (1TB, SATA300, 3.5", 7200rpm) : 932GB (F:) (G:)
EPSON Stylus Storage (USB2) : N/A (K:)
ATAPI DVD A DH20A4P (2.2GB, RAID, DVD+-RW, CD-RW) : 2GB (E:)

Logical Storage Devices
PT11 (D:) : 477GB (NTFS) @ WDC WD1001FALS-00Y6A0 (1TB, SATA300, 3.5", 7200rpm, 32MB Cache)
Apps&Ghs (H:) : 466GB (NTFS) @ WDC WD5000AAKS-22V1A0 (500.1GB, SATA300, 3.5", 7200rpm, 16MB Cache)
Studio1 (I:) : 932GB (NTFS) @ WDC WD1003FBYX-01Y7B1 (1TB, SATA300, 3.5", 7200rpm)
VI-DATA (F:) : 391GB (NTFS) @ WDC WD1003FBYX-01Y7B0 (1TB, SATA300, 3.5", 7200rpm)
PT10 (C:) : 455GB (NTFS) @ WDC WD1001FALS-00Y6A0 (1TB, SATA300, 3.5", 7200rpm, 32MB Cache)
STUDIO-BKUP (G:) : 541GB (NTFS) @ WDC WD1003FBYX-01Y7B0 (1TB, SATA300, 3.5", 7200rpm)
Removable Drive (K:) : N/A @ EPSON Stylus Storage (USB2)
Cubase SX 3 (E:) : 1GB (CDFS) @ ATAPI DVD A DH20A4P (2.2GB, RAID, DVD+-RW, CD-RW)

Peripherals
LPC Hub Controller 1 : Gigabyte LPC Interface Controller
LPC Legacy Controller 1 : ITE IT8720F
Audio Device : Gigabyte HD Audio Controller
Audio Device : PNY GF108 High Definition Audio Controller
Audio Codec : nVidia 0014
Audio Codec : nVidia 0014
Audio Codec : nVidia 0014
Disk Controller : Gigabyte 4 port SATA IDE Controller
Disk Controller : Gigabyte 2 port SATA IDE Controller
Disk Controller : Gigabyte 88SE91A3 SATA-600 Controller
Disk Controller : Gigabyte JMB36X PCIE-to-SATAII/IDE RAID Controller
Disk Controller : Gigabyte JMB36X PCIE-to-SATAII/IDE RAID Controller
USB Controller 1 : Gigabyte USB UHCI Controller #4
USB Controller 2 : Gigabyte USB UHCI Controller #5
USB Controller 3 : Gigabyte USB UHCI Controller #6
USB Controller 4 : Gigabyte USB EHCI Controller #2
USB Controller 5 : Gigabyte USB UHCI Controller #1
USB Controller 6 : Gigabyte USB UHCI Controller #2
USB Controller 7 : Gigabyte USB UHCI Controller #3
USB Controller 8 : Gigabyte USB EHCI Controller #1
FireWire/1394 Controller 1 : Belkin FW322/323 IEEE1394 OHCI FireWire Controller
FireWire/1394 Controller 2 : Gigabyte TSB43AB23 1394a-2000 OHCI PHY/link-layer Controller
SMBus/i2c Controller 1 : Intel ICH SMBus

Printers and Faxes
Printer : Microsoft XPS Document Writer (600x600, Colour)
Fax : Microsoft Shared Fax Driver (200x200)
Printer : EPSON Stylus Photo RX680 Series (360x360, USB, Colour)

Scanners and Cameras
Scanner : EPSON RX680/RX685/RX690 (Scanner, 1200x1200, USB)

Peripherals

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

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

Windows Experience Index
Current System : 1.0

[junkgear]

Do you notice that after a reboot that Windows has switched back to using the Presonus interface for Windows audio?

A lot of the internal sound card drivers use what is called positive jack detection. If the driver does not detect anything plugged into your on-board audio jacks (speaker out) then it tries to be smart and Windows will use the next device in line for Windows audio. which in this case may be the Presonus.

I use a Presonus Firestudio Project firewire interface, which runs their Universal Control driver and have not had issues with either PT 10 or 11.

[Joe.LoDuca]

Hello junkgear

For your question: "Do you notice that after a reboot that Windows has switched back to using the Presonus interface for Windows audio?"

My answer is "no". My motherboard has an integrated sound card on it so what I have done is to shut off ALL sounds in Microsoft (couldn't care less about hearing dings and gongs anyway). On top of that, I set the internal gigabyte sound card to be that windows default sound card.. and it seems to stay that way after reboots too.. The other day, I went 1 step farther which was that I saw Presonus in the list of potential sound devices Windows can use. So I disabled that (left click, disable) and so presonus doesn't even show on the list of what Windows is willing to us.. I like that. Presonus IS still in control panel and the Presonus Control panel still talks to the mixer. So.. Windows to presonus seems pretty satisfied.

As for the "Inputs changing on the mixer" that might disrupt ASIO, I am pretty sure I can rule that out as a cause. If I am lucky enough to not get this error at the launch, I can sometimes play about 4 minutes of a already recorded song while doing NOTHING but listening, and the error pops up..

I really like your Presonus Firewire card though.. I am seriously going to look into that.. So that gives you good results? I mean you use it this way everytime you track? If so, thats an experiment I am willing to make. I really believe that there isn't anything actually changing in ASIO, the software just "THINKS" thats what is happening.. So to me its something in the firewire communications or someones use of (or lack of) ASIO standards in terms of a digital protocol. Thats my 2 cents.

Thanks for some great insight.. Joe

[Joe.LoDuca]

I looked at "Presonus Firestudio Project firewire interface" - I can't use that, its a separate rack of I/O.. I want to use my Presonus 24.4.2 AS my audio interface to ProTools. I thought this may be a firewire card that Presonus makes that is on the same page as their mixers are..

Another point you make that I am going to try. Even though Windows sound nonsense is going to the gigabyte sound card on the mother board, I have nothing plugged into of any speakers. So if you are saying what Ithink you are about Windows jack detection, I better test this stuff out with something plugged in ... I did not try this..

[Joe.LoDuca]

Will : Thanks again for your insight. I did look into the jack detection thing you mentioned.. You are correct, Windows knows when something is plugged in or not.. And originally I had my default sound pointed to something that wasn't plugged in.. So on your recommendation, I put in a plug and Windows sees that.. But unfortunately it doesn't do anything to fix my problem.. But it was a seriously good idea. I also went 1 step further - I usually record everything at 48K/24 - So I made all the windows stuff be that sample rate too thinking if it was going to crossover into Presonus, at least it would be talking the right speed.. - didn't help.

I am at a loss of what else to do.

[lennieh]

I've got the same problem with my Apollo, it's totally random as far as I can tell. It can happen when I've been working for hours, in the same session, but the most usual time is immediately after opening a session, either a new one or an existing one.

I'm guessing it's some sort of heartbeat problem, protools must periodically poll the ilok and the interface to make sure they are playing nice and if the answer is slow coming back then you'll get that message.

I usually just have to save the session and restart Protools.

[Tim Mayock]

I have been struggling with this for a while and I still have the problem. I recently bought a new siig fire-wire card for my PC and that helps a lot but i still get the problem. I was using an on board fire-wire card and it worked with frequent intermittent problems. now it does it quite a bit less. It is not just you!

[junkgear]

Too bad the jack detection didn't pan out.
Regarding FireWire interfaces, I've actually found the VIA chipsets to work well using the VIA OHCI driver.
Sometimes changing the driver to use the OHCI Compliant driver helps. Even for non VIA chipsets.

[Joe.LoDuca]

Will : I am going to try again your idea, I am very curious. It will cost me next to nothing too. I should have a VIA firewire interface in about a week. I will report my findings either way, sounds like we have an audience of others with this issue. I really want to try to make this all work although I do have a backup plan in case it doesn't. I got Presonus STUDIO One Pro of which I am VERY impressed with. Unlike all this PT error nonsense, I can actually make music instead of trying to be some techsupport guy. And the sound is amazing. Still, in AVID's defense, PT is also impressive- but only when it works.

What I haven't posted in this thread is that I was pretty happy with PT 10 or 11 when I used it with an RME PCIe connecting with a MULTIFACE interface. RME is quite impressive and I have NEVER EVER saw any kind of ASIO control panel nonsense. A few weeks ago I decided to buy a Presonus SL24.4.2 to gain 8 more audio i/o that I cant get from the RME. So, it turned out to be an upgrade that I can't successfully use with PT of any version.

[junkgear]

Sorry I didn't post this earlier, but here is the list of approved chipsets from Presonus; which is what I used when I orderd my VIA based PCIe card.

Presonus FW Chipsets

Good luck and let us know how it turns out.