Avid Pro Audio Community

Avid Pro Audio Community

How to Join & Post  •  Community Terms of Use  •  Help Us Help You

Knowledge Base Search  •  Community Search  •  Learn & Support


Avid Home Page

Go Back   Avid Pro Audio Community > Pro Tools Hardware > FireWire & USB Audio Interfaces (Win)

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 12-03-2014, 08:44 AM
Joe.LoDuca Joe.LoDuca is offline
Member
 
Join Date: Nov 2010
Location: Sterling Heights, MI
Posts: 106
Default Potential solution for ASIO Audio Control panel issues of Firewire

Folks,
I want to try to post a potential solution for an issue that I have been seeing a lot lately with PT. And the reality is, ever since AVID’s open standard of audio hardware in PT version 9, this has been an issue. I first had this issue in version 9. Back then, I have solved it primarily by using specific audio hardware. But recently I changed hardware, I went from RME-audio which worked flawlessly with PT to using a Presonus SL 24.4.2 Mixer as my audio interface as a way of gaining some I/O. The RME has 16 channel I/O, the Presonus has 24. With Presonus hardware, all the errors of what I went thru in version 9 trying to talk to Focusrite equipment came back to haunt me. With Presonus, I get that non-stop relentless “ASIO properties have changed in control panel, protools must quit, etc, etc” - and it would be nice if rebooting or relaunching the app was all you had to do to fix it, BUT ITS NOT. This issue would NOT GO AWAY for me. I discovered thru the help of other forum users that its VITAL that your firewire use the LEGACY drivers, not the ones Windows will put on by default. If you don’t know how to do this, refer to the performance tuning steps for AVID, I believe its there. If your system is like mine, this will not be the end all fix for you:

Next concept:
I went to ASIO4all.com and downloaded their free driver. As I understand it, asio4all is a sort of dummy do nothing audio engine that cant produce any sound what so ever. Its only job in life is to make PT think it has something on your box that resembles an audio engine to talk to. But if you get the error I get, you’ll want to use ASIO4ALL to help you launch PT and hopefully work. This loading sequence seems to work for me for everything from version 9 thru 11. Try this if you are having audio control panel issues in PT:

1) EACH AND EVERY TIME YOU Launch Pro Tools and as soon as you see the black load up window, press and hold down your “n” key and do not let up until you get the new window asking about what engine to load up for pro tools.

2) Specify “ASIO4ALL” and click OK

3) Once PT fully loads, do not load a song yet, go back into your audio engine and specify the audio engine you intend to use for your normal day to day projects.

4) Load up a project and test it out, for me this process has worked each and every time regardless of versions.

Below is the relevant parts of my SANDRA so you know what Hardware I have and how it may compare to your system:

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: 24Gig
----------------------------------------------
Graphics Processor

Peripherals
FireWire/1394 Controller 2 : Gigabyte TSB43AB23 1394a-2000 OHCI PHY/link-layer Controller
SMBus/i2c Controller 1 : Intel ICH SMBus



What you don’t see here in my SANDRA is, I still have my RME card on my system. One day I curiously disabled that card in control panel of Windows.. From that point it should theoretically NOT BE ACCESSABLE to ANY software when you do that. But for some stupid reason, This is NOT the case with PT. Even disabled in Windows, PT still has that as one of the options of audio engines in the list. This is very fishy to me.. I believe AVID HAS some issues in how audio engines load..

But anyway, I want to share this with as much people and hope it helps some out at least. Its been a long time issue with AVID and I really don’t know if its ever going to get fixed. If I hadn’t discovered the above, I would have no choice but to cut AVID PT lose forever.. Either you can make music with or you can’t, its just that simple!!

Have a great day!
Reply With Quote
  #2  
Old 12-15-2014, 09:56 AM
Joe.LoDuca Joe.LoDuca is offline
Member
 
Join Date: Nov 2010
Location: Sterling Heights, MI
Posts: 106
Default Re: Potential solution for ASIO Audio Control panel issues of Firewire

I know common sense tells me I should just cut PT lose forever. The reality is, if you have a third party audio interface, and depending on what that interface is, PT can almost be impossible to get working. I have done way more tech support than should be required by any musician. Its Crazy.. But I am going to give this ONE LAST POST to see if anyone has some recommendations before I get a divorce from AVID.

The above post is short lived as many seemingly successful tweaks are in PT. It worked for a week or 2 and its just not been stable enough to rely on it ALL the time.

THIS BLOWS MY MIND: I have 3 sound cards/audio interfaces technically on my system: One is the motherboard audio I give to window to do what it wants. The 2nd is RME-Audio to Multiface on proprietary protocol(similar but not the same as traditional firewire) and then there is the 3rd: Traditional firewire400 (legacy driver) communicating to my Presonus StudioLive24.4.2 - The RME interface works flawlessly with PT, Presonus does not. I want to use the Presonus to get more I/o. But I keep getting the "ASIO properties changed" error. I tried all the tweaks and optimizations, no go. I decided for last effort before divorce proceedings start, I would COMPLETE UNINSTALL PT -- AND --- RME Audio drivers.. And when I say COMPLETE, I mean it!! I uninstalled the whole 9 yards, only thing left was my pluggins.. And I am not pulling those out! So, I looked in control panel and all windows knows in terms of audio was the presonus on firewire and internal mother board hardware. RME is GONE! From there I would reinstall PT 10.3.6 expecting to NOT see any option in the PT Audio engine referring to RME. Unfortunately, Protools will just not let go of my RME interface. AND THE PROPRIETARY CARD IS NOT IN THIS COMPUTER! This software is seriously flawed.. My thinking was that possibly the RME card was giving me issues with my Presonus on firewire. Anyone see this happen? Anyone have a recommendation to remove hardware from PT that isn't in the system. Normal software should not even operate like this, PT? Its flawed!
Reply With Quote
  #3  
Old 12-15-2014, 10:03 AM
Southsidemusic's Avatar
Southsidemusic Southsidemusic is offline
Moderator
 
Join Date: Dec 2011
Location: Stockholm - Sweden
Posts: 13,767
Default Re: Potential solution for ASIO Audio Control panel issues of Firewire

Well this doesn't happen to "all" 3rd party interfaces. We have Apollo,Quad, Apollo 16 and Prism Orpheus and they all work flawless with PT11-10 HD

This problems you have has to be down to your PC and other hardware since we never seen anything like this. We have several friends with RME interfaces and they have been running every day and made lots of money.

If I were you I would wipe the OS drive completely and restart. That might be the only way to clean up properly.

And don't take this post as a "you are the problem" as that is NOT what I wanted to say here, just that sometimes we have to move on and work with the passion we love and not keep fixing, reinstalling and having crashes days on end killing every ounce of creativity we have left!

There are WAY more important things in this short life we have on this planet than to fight with a computer everyday just to do what we love in that little extra time we have for hobby and music making

Christopher
__________________
Best Regards
Christopher

#thestruggleisreal
—————————————
South Side Music Group
WEBHOME
—————————————
Reply With Quote
  #4  
Old 12-15-2014, 06:01 PM
Joe.LoDuca Joe.LoDuca is offline
Member
 
Join Date: Nov 2010
Location: Sterling Heights, MI
Posts: 106
Default Re: Potential solution for ASIO Audio Control panel issues of Firewire

Christopher: I really appreciate your response, probably more than you know. I might try the clean windows install.. Still sorting that out, thats a pretty big plunge to take.. But One thing also that I have not put into my post is that my system right now does dual booting. I partitioned a 1TB WD drive and gave WIN7 ample room on both halves. I set my system up this way before PT11 came out. I put this in place early in 2013 and its worked well for me. At the the time, I had no idea that Avid was going to allow v10 and v11 to coexist on the same box. So I set up the dual boot and it has also been good to allow me to test versions and hardware and NOT disabling my recording ability. And I will tell you that I tried the same hardware on both partitions and get the same exact issue. I know the value of AVID, when you have the hardware that the system loves, it works extremely well. I know this for a fact because I have been using RME from version 9 to 11 and it is as you say "FLAWLESS". I totally agree. But interfacing PT to Presonus24.4.2 via firewire is just not happening. And with all due respect to Avid, they claim to adapt to any 3rd party interface, but I just don't exactly see it that way. Some yes, but some NO! There are a lot of folks having THIS ISSUE with focusrite gear. -of which I had as well in Version 9.. Focusrite makes good stuff but I had to abandon that hardware because I was becoming more of a techsupport person than a musician. All I want to do is create music, I am growing tired of googling errors and adjust parameters while spinning beach balls on my nose and juggling plates.. It shouldn't be anywhere near this hard to get things to work as advertised.

And then to top it off, I purchased Presonus Studio One, and it works FLAWLESSLY over the same firewire ASIO connections. (as does the control panel of that hardware) I know lots of people would say "But Joe, Presonus and Studio One - theres nothing 3rd party there! of course its going to work well ! Duh! " But my answer to that is, when I can flawlessly run Cubase, Studio One, & Sonar without issues - all of which speak in the language of ASIO, and the issues that do show are ALWAYS within PT and ALWAYS ASIO, - its not that difficult to know who has the issue at hand .. Definitely not rocket science.
Reply With Quote
  #5  
Old 12-15-2014, 06:13 PM
Southsidemusic's Avatar
Southsidemusic Southsidemusic is offline
Moderator
 
Join Date: Dec 2011
Location: Stockholm - Sweden
Posts: 13,767
Default Re: Potential solution for ASIO Audio Control panel issues of Firewire

I totally understand and AGREE with your thoughts, It shouldn't be that hard.

But (there is always a but) sometimes as you said PT needs more than we are willing to give her so in these situations like you are in maybe wipe the drive clean, take away the partitions and start fresh. Or get a new OS drive and keep the one you have now so you can use that as a storage and backup. Then when you get the new drive just drag the sessions onto the new harddrive. You can never have too many backup drives

I am sorry you have these issues and I really do feel your pain.

I hope you either get the system up and running with PT or go the other way with Presonus Studio One. Making music and upholding a small home studio and in that same process become an tech specialist isn't very productive so if you found a footing with Studio One I say give PT one more chance to function as you reinstall on a fresh hard drive and NO migration software and if that clunks out, Ditch and be Freeeee

I know many Billboard top 10 songs made on Logic and Studio One and Cubase so if you wanna make music, having FUN and not having to keep fiddling with computers and interfaces that clearly hates each other go with what works for YOU!

Best of Luck and hopefully you make this work for you Asap

Christopher
__________________
Best Regards
Christopher

#thestruggleisreal
—————————————
South Side Music Group
WEBHOME
—————————————
Reply With Quote
  #6  
Old 12-16-2014, 07:48 AM
Joe.LoDuca Joe.LoDuca is offline
Member
 
Join Date: Nov 2010
Location: Sterling Heights, MI
Posts: 106
Default Re: Potential solution for ASIO Audio Control panel issues of Firewire

Christopher, I have decided to take your advice.. Actually I too had been thinking of repaving the OS roads for the last 2 weeks or so. And I will definitely do this to a new drive. That way if it doesn't get me a solution, then I have another drive to put data should I need it. My aim is to start out with ONLY WIN7 and PT11.2.2 with appropriate firewire. I removed ALL RME hardware and will not install it unless lagacy firewire to Presonus still does not function after the new WIN install. If I can load PT without all my ASIO bits spilling out over the floor, then I will continuously ghost my drive, keep installing plugins and things making sure nothing gets disturbed in Pro Tools-land. It shouldn't be this hard but, based on the investment I made in aax, getting PT to work is what I really need.

I will report back my findings either way in a day or 2. I do notice a fair share of Focusrite people and some MOTU folks that are plagued with this exact same error. I think I have tried everything possible short of a fresh OS install. I am also going to use WIN7 Professional instead of home premium. Not sure all the differences, but the part about Home Premium that I don't like is you must first install XP as this is an upgrade. I want WIN7 from start to finish.

Good day all !
Reply With Quote
  #7  
Old 12-16-2014, 01:01 PM
Joe.LoDuca Joe.LoDuca is offline
Member
 
Join Date: Nov 2010
Location: Sterling Heights, MI
Posts: 106
Default Re: Potential solution for ASIO Audio Control panel issues of Firewire

Dear AVID,

After spending grueling hours troubleshooting your poorly written software and I am supposed to pay YOU for the high honor of fixing what YOUR software CLAIMs to support. I am done! I am no longer an AVID customer because your product simple does not work. There is very selected few pieces of hardware that can run with protools. Your website claims to support everything and you will continue to support 3rd party hardware. But many of your customers know better. I know better, but soon I will no longer be your customer. Ever since your open standard of version 9 using ASIO, you’ve had nothing but problems here. Being that the issue is unresolved in version11 tells me you don’t care to have it fixed. You want to add features to your software, but I have to tell you the most important feature is software that actually operates! When I look around on this forum, I see many users like myself with THIS EXACT problem. It surprises me that many 3rd party companies like TC electronics and Focusrite are trying to write special drivers to accommodate all that protools ASIO BS. Now lets do some basic analysis here: How long has AVID been using ASIO protocol? Answer: about 3 years now.. Lets consider other applications like Cubase or Sonar, how long have they been in the ASIO business? Answer: A heck of lot longer than AVID! And they have it right, you folks do not! I can’t believe you have a quality company like Focusrite working on their drivers to work with FLAWED Avid software. You guys charge top buck for your software, AND you charge for tech support to fix the issues YOU caused! I hate to be mean about this, but someone down there at AVID needs to wake the heck up .. This is not a great way to function in business.
I hope one day you finally get it!
Reply With Quote
  #8  
Old 12-16-2014, 07:59 PM
Emcha_audio's Avatar
Emcha_audio Emcha_audio is offline
Moderator
 
Join Date: May 2010
Location: Montréal, canada
Posts: 6,752
Default Re: Potential solution for ASIO Audio Control panel issues of Firewire

Would have actually helped if you had posted the full Sandra report as there's other things that what you have listed that might have contributed to your problem. So if you can post the complete Sandra maybe we can finally get to help you completely. As for the problem with the changes in asio settings, that's to the third parties to write their drivers in consequences. I know that Focusrite has apparently fixed that issue on Mac's but I'm still getting them on Pc's. It's not a problem with PT itself, even though they (focusrite) claims it, as other manufacturer have been able to resolve that problem while writing their drivers, example RME.

Secondly, Avid has opened the software to work with most ( I have never seen any documentation that said it was going to work with everything and certainly not providing support for any third party hardware, there's a distinction here in opening the software to work with other hardware and providing support for those hardware) pieces of thirds parties hardware that supported the Asio protocol.

Thirdly, Asio is not a Pro tools bs thingy as you claimed it, Asio is a protocol that has been developed by Steinberg to be used on PC's (not macs) to provide lower latency communications between the soundcards (or hardware) and the computer, which came to be adopted by all the hardware manufacturers instead of the slower and less dependable directsound that was developed by Microsoft. On the otherhand, the Asio4all which is loosely based on the Steinberg protocol but made to be a shareware was developed by Michael Tippach a german independent programmer.

So to go in closure about this, Avid has catered to the want of the majority and opened PT to work with Asio and core audio devices, which brought it's load of problems that Avid initially didn't want to have to deal with, but it did because it's users wanted it. Now that some third party hardware is having trouble communicating with PT through Asio or Core audio is up to the Thirdparty hardware to provide support. As users though we are always inclined to help other users get through their hurdles, which is why Southsidemusic tried to help you. This is not an Avid Support forum, it's a user forum.
__________________
Manny.

Wave-T.com
Reply With Quote
  #9  
Old 12-17-2014, 09:28 AM
Joe.LoDuca Joe.LoDuca is offline
Member
 
Join Date: Nov 2010
Location: Sterling Heights, MI
Posts: 106
Default Re: Potential solution for ASIO Audio Control panel issues of Firewire

Hi Manny,
I don’t want to come off mean towards AVID, trust me on that! I have had lots of good use out of it over the years. When it works perfectly with all your hardware, its simply the best in the industry. And there’s a reason you see Pro Tools in most studios today. But from my perspective, I got to tell you, I am not exactly in the dark about technology. Quite the opposite. For a musician, I know numerous programming languages, digital protocols, I can balance my check book in hexadecimal MIDI ! Seriously! AND I also have a pretty awesome background in electronics engineering. So I know a thing or two:

And I tell you, how anyone can totally REMOVE the physical card out of a PC along with uninstalling the RME drivers for that card and having PT STILL WANT TO TALK TO THAT CARD when Windows cant, that’s a software issue pure and simple. There is no excuse for that and its a sign that something is wrong in software-ville. It just doesn’t get any clearer than that. Yesterdays FRESH windows install was my attempt to work around this issue. And in terms of Protocols comes the term “Standards” – if you talk MIDI for example, there are standard you have to follow, you just don’t send a bunch of hex on the wire and hope a synth is smart enough to play. And I have seen issues with instruments that do not follow the MIDI spec. Same deal in ASIO, don’t follow the rules, go to jail. Its that simple! In my humble opinion, this has got a AVID non-compliance to ASIO standards written all over it. (not to be mean) but. I can place all the same hardware on every other software and get rock hard SOLID timing. And I have a RME system too, and proTools runs great to that. But again, in RME, we are not speaking the traditional firewire protocol between card and interface. Its RME proprietary.

But anyway, here’s the deal, I will post a full Sandra below. I really think I have tried everything, I have thrown money at trying to fix this, nothing has helped. If you can discover something I haven’t tried, I would love to know what that is. And if you can discover a resolution, I will become your biggest fan! I have totally run out of things to try.

What I did to try to fix:
I did ALL optimizations for windows 7. My Presonus24.4.2 is working flawlessly under other apps, not PT of any version. My C drive is partitioned into 2 Win7 bootable versions. The errors exist on BOTH partitions. I have the (legacy) firewire drivers as recommended by AVID. I also tried all 3 firewire drivers and all do not play nice with PT. I have uninstalled physical drivers and reinstalled, same issue. Also uninstalled physical cards and watch apps like PT relentlessly try to talk to something that isn’t physically on the system anymore. Then yesterday, I purchased a new bootup drive and totally reinstalled windows7 64. Then optimized the win7 recommendations of AVID, then returned the firewire to LEGACY, then installed the Presonus control panel. Once communication between mixer and computer was good, I then installed PT11.2.2 with ONLY the presonus as a viable option for PT audio. Also of interest here is my mother board also contains some 50 cent audio card so I always give that to WINDOWs to use. – I also set windows to “no sounds” anyway. But if it had something to play, it would at least NOT use something that Protools is using.. So Presonus is exclusive to PT! Also of interest is that my firewire interface (part of my gigabyte motherboard) is on the preferred list of interfaces and chipsets according to Presonus. I also believe the same from AVID's perspective, I have looked at lots of systems that I believe are deemed “approved” and I think everything I have falls on that list. (unless I am missing something) Aside from all this, I have no idea what else can be done to fix this.
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
Reply With Quote
  #10  
Old 12-17-2014, 10:00 AM
Emcha_audio's Avatar
Emcha_audio Emcha_audio is offline
Moderator
 
Join Date: May 2010
Location: Montréal, canada
Posts: 6,752
Default Re: Potential solution for ASIO Audio Control panel issues of Firewire

Alright I'm seeing two things that is sticking out for me, one is more a question the other is something I always recommend.

1rst, you got PT 11 on D and PT 10 on C:. I know you probably already know that but PT needs to be installed on the C: drive each time. I know that when you make a dual boot, the letters of the drive changes depending on which boot you are in, so please confirm that when you are in the PT 11 boot that the drive letter where PT 11 is installed is C?

now:
Audio Device : Gigabyte HD Audio Controller
Audio Device : PNY GF108 High Definition Audio Controller

Go into your bios and completely disable these two audio controllers and assign your mixer to windows as the default playback and recording interface, make sure there's no other listed there. I don't use Presonus, but that's what I'm doing with the LS56 and I have 0 problem with windows sounds. This won't fix the your asio settings has changed (if you change the buffer within pro tools or through the mixer software interface) but it may give more stability. Also make sure that in windows the bit rate and sample rate are the same that what your interface is set to. So if your interface is set to 24/96, that's what you need to set in the properties for the default advance proprieties.

I know many people will tell you not to do that that they haven't had any problems, but these are steps that were suggested to me by the manufacturers themselves.

An other thing, in the Asio drivers what is your firewire latency set to? Short, medium, long? (can't tell if Presonus uses the same thing as Focusrite). Have you tried to keep it on medium to see if it improves the stability of the connection? Although it won't change the asio settings has changed (if you change the buffer within pro tools or through the mixer software interface) but it may give more stability.

Although Avid recommends using the legacy drivers, have you tried the OHCI compliant drivers? And also, is that gygabyte firewire a card or is it the one imbedded into your Motherboard? If it's imbedded try getting this card SIIG NN-440012-S8, it's the one I use and I can attest that it gives me no compatibility issues. Even though it's the same chipset as your's it might be worth a try and it's only 30$ now. Which reminds me, in your device manager, there's now yellow declamation marks beside the IEEE bust host controller?

There's no graphical processor listed, are you using a motherboard imbedded chip? The cpu imbedded chip, or a separate V card and is it listed as the compatible cards in the system requirement FAQ or the i7builds thread?

This is what comes to mind at the moment.
Attached Images
File Type: jpg windows settings.jpg (59.4 KB, 0 views)
__________________
Manny.

Wave-T.com
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
ASIO device properties have been changed by the device control panel. medinarawk Third Party Interfaces 5 07-06-2015 02:18 PM
Error: ASIO device properties changed in control panel Joe.LoDuca Windows 15 12-02-2014 08:31 AM
Control Panel Issues... List them here. Loudnoize Ent. Pro Tools M-Powered (Mac) 1 06-24-2012 10:24 PM
Latency issues (pro tools and control panel show different values...) birdfluvirus 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Win) 0 06-24-2012 10:22 PM
Firewire 410 control panel shultzee13 Pro Tools M-Powered (Win) 11 10-16-2007 07:29 PM


All times are GMT -7. The time now is 12:01 AM.


Powered by: vBulletin, Copyright ©2000 - 2008, Jelsoft Enterprises Limited. Forum Hosted By: URLJet.com