AISO properties have been changed in the device panel

[YYR123]

Has anybody seen this happening on their machines



Just started happening tonight


I should charge Tapatalk 2 pennies every time this message comes up !!!

[arhall]

Originally Posted by YYR123

Has anybody seen this happening on their machines



Just started happening tonight


I should charge Tapatalk 2 pennies every time this message comes up !!!

Just another thing Avid ignores. I get it all the times and it wrecks my workflow totally.
I'm moving over to other DAW's now.

http://duc.avid.com/showthread.php?t=287669
http://duc.avid.com/showthread.php?t=314619
http://duc.avid.com/showthread.php?t=314922
http://duc.avid.com/showthread.php?t=311605
http://duc.avid.com/showthread.php?t=298521

[albee1952]

Never seen it here

[YYR123]

God help me i am thinking about a mac again.....and maybe this will go away.

I really haven't had too many issues, but I just updated my antivirus software and that's it recently....I hope i don't have to get a MAC for these problems to go away.

[deanrichard]

Happens all the time to me. Usually I need a full reboot to get it working again. God forbid I should ever load a 48K session when the interface is set to 44.1K, or vice-versa. That's a full reboot for sure, and sometimes I need to reboot twice.

The worst part isn't the error. It's annoying, but that's all. The very, very worst part is that it kills the app and there is no way to recover except to start the app again and have the same thing happen all over again and again, repeated indefinitely. Reboot usually works, like I said. I've wasted hours fighting this error message because some sadistic programmer at Avid didn't feel it necessary to program PT with the ability to recover from what PT detects as a simple change to the ASIO settings - a change which usually didn't even occur.

[YYR123]

I wonder if there are many different versions of AISO drivers out there? if this has something to do with it.???? If i can remember I will post that info here.

Thanks.

Daniel

[arhall]

Originally Posted by deanrichard

I've wasted hours fighting this error message because some sadistic programmer at Avid didn't feel it necessary to program PT with the ability to recover from what PT detects as a simple change to the ASIO settings - a change which usually didn't even occur.

Second THAT!
In really bad moments I sometimes think Avid had put in the error to deliberately make us buy Avid h/w instead of third part.

[YYR123]

so here is the question that i would like to postulize???? Is AVID willing to/or interested in support 3rd party interfaces....or are they just kinda on there own......

Does it even matter because of AISO....?????

I mean Focusrite does have a driver bundle for my computer.....and it looks like they have connected into somehow the AISO driver.....(judging by my device manager).....

But logically you would expect it to have problems off and on with other software inside of Win7 - which it doesnot.....The problem is just when you try to load PT it doesn't seem to like it......(i still have my 003r still in the rack i suppose i could always utilize it huh)


So does AVID even care about supportting the 3rd party interfaces (not really upset just trying to find out what the direction of the company is) or do they just play the tune that it is the 3rd party that is responsible to come out and play nice with us.....Just asking b/c i am sure that focusrite is trying to correct this issue....(you would think anyway).

Currently talking to the tech support off and on with email will keep the thread updated.....

[arhall]

Originally Posted by YYR123

so here is the question that i would like to postulize???? Is AVID willing to/or interested in support 3rd party interfaces....or are they just kinda on there own......

Does it even matter because of AISO....?????

I mean Focusrite does have a driver bundle for my computer.....and it looks like they have connected into somehow the AISO driver.....(judging by my device manager).....

But logically you would expect it to have problems off and on with other software inside of Win7 - which it doesnot.....The problem is just when you try to load PT it doesn't seem to like it......(i still have my 003r still in the rack i suppose i could always utilize it huh)


So does AVID even care about supportting the 3rd party interfaces (not really upset just trying to find out what the direction of the company is) or do they just play the tune that it is the 3rd party that is responsible to come out and play nice with us.....Just asking b/c i am sure that focusrite is trying to correct this issue....(you would think anyway).

Currently talking to the tech support off and on with email will keep the thread updated.....

A really good thing that you have open a case at Avid support.
I'll subscribe to this thread.
Not one day goes by without some poor guy addressing this particular problem here. So does AVID even care about ....? Well I could chime with real mean things here.

[hue]

I know this is old. The problem is when you change the sample rate/bit rate when you exit protools so that all of your system sounds are audible. Before you open Pro Tools, change the Bit/Sample rate in your ASIO control panel to match the Bit/Sample rate of the project. This will prevent that message from popping up. It's a very simple issue.