|
Avid Pro Audio CommunityHow to Join & Post • Community Terms of Use • Help Us Help YouKnowledge Base Search • Community Search • Learn & Support |
#21
|
|||
|
|||
Re: "ASIO properties changed" Focusrite Saffire Pro 40
I've also put in a support ticket with focusrite about the same problem with my saffire pro 24. Hopefully our voices will be herd!
__________________
******* Pro Tools 12.4 | Focusrite Scarlett 6i6 | Gigabyte X79-UD3 | Intel i7 3820 2011 LGA | GeIL EVO Leggera 16GB 4x4GB | MSI Nvidia 970 | Corsair XT 850 watt PSU |
#22
|
||||
|
||||
Re: "ASIO properties changed" Focusrite Saffire Pro 40
caatalyst, njpianist, let me know soon as you hear from them, especially if it is something none of us has tried yet.
Hopefully they will come through with a fix. I put my vendor on notice that I would probably be returning the unit, but I want to at least give Focusrite a chance to reply. Dear Focusrite... I do not want to return your product because I love what you make... but it does not work as advertised. I would rather have it work than not, but I have to have a system soon..
__________________
GIGABYTE X58A-UD3R, INTEL CORE i7 960, NVIDIA GEFORCE 8400GS, WIN 7, MOTU 896mk3 HYBRID, PT 10.3.2 |
#23
|
||||
|
||||
Re: "ASIO properties changed" Focusrite Saffire Pro 40
Still haven't heard from Focusrite, but I managed to get through over two hours of non-stop play last night with no ASIO shutdowns. That's good.
I reverted the driver back from the legacy driver to the TI driver. Could that be it? I have no idea. Also, and again I'm not sure if this helped or not, but I reinstalled Mixcontrol without the Saffire hooked up, with PT 10 already installed of course. This is opposite of what the PT 10 installation guide says to do. In the installation guide it specifically says to install the hardware and hardware drivers first, then install PT so that's how I did it initially. Again, I am not sure if this has anything to do with the problem. The other thing is I can't seem to recall a single instance where the ASIO shutdown occurred when I was actually working on something. It seems like it only occurs for me when PT has been sitting idle for a long time, as in 30 minutes to an hour or longer. If that is the actual trend, I can deal with that. When I am working it usually will not idle longer than the time it takes for a bathroom break. I'm going to keep messing with it, but I feel more hopeful than I have in a week now.
__________________
GIGABYTE X58A-UD3R, INTEL CORE i7 960, NVIDIA GEFORCE 8400GS, WIN 7, MOTU 896mk3 HYBRID, PT 10.3.2 |
#24
|
|||
|
|||
Re: "ASIO properties changed" Focusrite Saffire Pro 40
I had the same problems with my LS56. Replacing my nVidia graphicscard by a (cheap) Radeon HD5750 solved the problem for me.
Sometimes my LS56 loose connection. Putting is off and on helps. I worked with my setup (with PT10) for several hours without any crashes!! |
#25
|
|||
|
|||
Re: "ASIO properties changed" Focusrite Saffire Pro 40
Dont no but when I runned a dverb test I discovered that the legacy driver did'nt cope with the workload. TI driver did. I'm using a TI chip.
__________________
Intel i7 2600K, z68 with iGPU, 8Gb, Win7 64, PT11. TC Impact Twin. |
#26
|
||||
|
||||
Re: "ASIO properties changed" Focusrite Saffire Pro 40
arhall, did you get the ASIO message?
I'm going to push it tonight and see how it goes and how long I can work it with no errors. Fingers crossed. I think my wife is ready for me to get the rig out of the living room and into the studio where it belongs.
__________________
GIGABYTE X58A-UD3R, INTEL CORE i7 960, NVIDIA GEFORCE 8400GS, WIN 7, MOTU 896mk3 HYBRID, PT 10.3.2 |
#27
|
|||
|
|||
Re: "ASIO properties changed" Focusrite Saffire Pro 40
Milko: This is exact the same thing that happend to me, and what I have tried to tell people here. I belive it's the display port audio carrier that causes this.
When installing the AMD driver I can choose not to install the audio feature, and it works for hours at end after maybe 1 loss of connection at the begining. What I do before a session is to play some music/movie to see if the audio setup works, then use PT10.1. |
#28
|
|||
|
|||
Re: "ASIO properties changed" Focusrite Saffire Pro 40
Quote:
I'm not using spdif & adats so ASIO4ALL suits me quite well for now.
__________________
Intel i7 2600K, z68 with iGPU, 8Gb, Win7 64, PT11. TC Impact Twin. |
#29
|
|||
|
|||
Re: "ASIO properties changed" Focusrite Saffire Pro 40
Quote:
__________________
******* Pro Tools 12.4 | Focusrite Scarlett 6i6 | Gigabyte X79-UD3 | Intel i7 3820 2011 LGA | GeIL EVO Leggera 16GB 4x4GB | MSI Nvidia 970 | Corsair XT 850 watt PSU |
#30
|
||||
|
||||
Re: "ASIO properties changed" Focusrite Saffire Pro 40
I got a reply from them as well, only totally different from yours:
Quote:
The DPC laterncy checker says the only way to figure out which driver is causing the problem is to go into devices and shut them down one by one until you find out which one is the culprit. For me, given that it takes a long time just to get the message, this could take days of non-stop staring at the computer. I'm waiting to hear back from them. I hope you're right and that a fix is on the way.
__________________
GIGABYTE X58A-UD3R, INTEL CORE i7 960, NVIDIA GEFORCE 8400GS, WIN 7, MOTU 896mk3 HYBRID, PT 10.3.2 |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Midi Export -> "Apply Real Time Properties" Question | Sparky1 | macOS | 2 | 12-12-2020 04:54 AM |
'ASIO Device has changed properties' is back with avengeance. | TheJamsh | Third Party Interfaces | 13 | 09-29-2013 10:40 PM |
Asio device properties have been changed... | guitarbin | Pro Tools 10 | 2 | 03-31-2013 07:33 PM |
DICE chipset+PT10="ASIO device properties have been changed by the device" | Funk-O-Meter | Windows | 5 | 12-19-2012 05:12 PM |
Pro Tools 9 "Pausing" when I press "Play" with Focusrite Scarlett interface | eanderso22304 | macOS | 3 | 11-23-2011 06:45 AM |