ASIO Properties have been changed ...

[Zergei72]

- ASIO device properties have been changed by the device control panel. -

I'm using a Behringer UPHORIA UMC-404 on Windows 10 with Pro Tools 12 .

I have no such issues with any other DAW neither on WIN or Mac OS X .

REAPER, SEQUOIA, etc . work correctly
with the UMC-404 without any issues .


It's just Pro Tools 12, that's losing the connection with the audio-interface .

I have tried changing the buffers on the UMC-404,
but no success whatsoever ...

I've also disabled the properties of UMC-404 in Windows Control Panel so, that the UMC-404 is not used by any sound related tasks by the operating system . In other words the UMC-404 is disabled in Hardware / Sound in Windows Control Panel .

I see this has been covered quite widely here (with other audio-interface manufacturer's devices also ... )

but is there a fix for this ... ???

Reply ASAP,

- zergei W -

[cwsand]

Pro Tools isn't supported in Windows 10, though some people have gotten it to work. I had similar issues with my interfaces and Pro Tools 12 in Windows 10 so I went back to Windows 7 and got back to recording. The fix will be a version of Pro Tools supported in Windows 10...

Windows 10 support for Media Composer, Pro Tools, Sibelius, EUCON, ISIS, iNEWS and MediaCentral

[deanrichard]

I used to see that error all the time. PT can be very problematic with 3rd party ASIO drivers. I installed ASIO4ALL (which PT does support) and most of those problems went away.

ASIO4ALL is a free driver / wrapper that will create an additional ASIO driver front end to your audio interface. It's straightforward to set up, and I think it works with most any interface. It has never interfered with my existing audio drivers. The system sees two sets of ASIO drivers, just pick the ASIO4ALL one for use within PT.

PT's ASIO implementation has always been spotty.

Originally Posted by Zergei72

- ASIO device properties have been changed by the device control panel. -

I'm using a Behringer UPHORIA UMC-404 on Windows 10 with Pro Tools 12 .

I have no such issues with any other DAW neither on WIN or Mac OS X .

REAPER, SEQUOIA, etc . work correctly
with the UMC-404 without any issues .


It's just Pro Tools 12, that's losing the connection with the audio-interface .

I have tried changing the buffers on the UMC-404,
but no success whatsoever ...

I've also disabled the properties of UMC-404 in Windows Control Panel so, that the UMC-404 is not used by any sound related tasks by the operating system . In other words the UMC-404 is disabled in Hardware / Sound in Windows Control Panel .

I see this has been covered quite widely here (with other audio-interface manufacturer's devices also ... )

but is there a fix for this ... ???

Reply ASAP,

- zergei W -

[deanrichard]

This error is quite common in every supported (and unsupported) version of Windows. PT's ASIO implementation is not very good. The solution for me was to install ASIO4ALL.

Originally Posted by cwsand

Pro Tools isn't supported in Windows 10, though some people have gotten it to work. I had similar issues with my interfaces and Pro Tools 12 in Windows 10 so I went back to Windows 7 and got back to recording. The fix will be a version of Pro Tools supported in Windows 10...

Windows 10 support for Media Composer, Pro Tools, Sibelius, EUCON, ISIS, iNEWS and MediaCentral

[ex-user]

I cannot but help wonder what effects ASIO4ALL has on latency, since it is an ASIO wrapper around existing WDM drivers. Also, does it really change sample rates on the hardware or does it just re-sample from the ASIO configured rate to whatever Windows is currently running WDM at?

[cwsand]

Originally Posted by deanrichard

This error is quite common in every supported (and unsupported) version of Windows. PT's ASIO implementation is not very good.

True, but trying to troubleshoot in an unsupported environment is going to be a crap-shoot IMHO.

[deanrichard]

Given that ASIO4ALL is the only supported ASIO environment, that makes the ASIO implementation very confining.

Originally Posted by cwsand

True, but trying to troubleshoot in an unsupported environment is going to be a crap-shoot IMHO.

[cwsand]

Originally Posted by deanrichard

Given that ASIO4ALL is the only supported ASIO environment, that makes the ASIO implementation very confining.

Yes, I was actually referring to the original poster trying to run Pro Tools in Windows 10, which is not supported.