No, this doesn't necessarily help anyone who is currently having issues, but I figured I would put in my 2 cents that not all is broken moving forward. Hopefully these issues can be resolved. It sucks to lose perfectly good gear to obsolescence!
Statistics: Posted by gurulogic — 01 Feb 2023, 05:06
]]>
Statistics: Posted by manarimnhkjgg — 24 Jan 2023, 22:16
]]>
]]>
BSOD means hardware issue. Very strange because Usine is not supposed to access to hardware level?
that BSOD is because windows is dropping support for some old drivers, and focusrite is dropping support for older hardware (shame on focusrite regarding this because Saffire is great piece of hardware but almost unusable with new windows because of this)mainly i am using Hollyhock, Tracktion Waveform, and NI Traktor.
It seems that Traktor is using/initialising ASIO in different way as HH/Tracktion. because with win 2004 i had no problems running traktor and switching between different audio interfaces. with tracktion an HH i got BSOD..
Statistics: Posted by drakh — 16 Jul 2020, 13:14
]]>
]]>
but my saffire 24 causes crashes (oh thunderbol3->thunderbolt2->firewire) so anytime i started usine i got BSOD because of safffire, which is strange, because, with traktor in asio mode it worksfine. anyway focusrite dropedthe support for saffire card. and they recommend using it with windows 1809 build.
Anyway then i tried my scarlet 6i6 and i got strange things with usine. somehow, ind windows sound panel it was running in 24b/44kHz. And the sound fromusine was totally glitchy. sdo i needed to play with buffersize, switched it to 16b/44khz in windows sound control panel, but it magically switched back to 24bit after selecting foccusrtie usb asio - but, this behaviour is only with usinee. with other audio software i am using it works well.
so i rollbacked to 1909..
and yeah i've got strange issues when i updated from 1809 to 1903 (and they remain in 1909) with usine... some strange random dropooffs appeared even with light workspaces which worked without any issue
have you tried recent new update, version 2004?
Statistics: Posted by drakh — 03 Jul 2020, 15:11
]]>
]]>
]]>
The audio just stops, as if Windows just stop making it available to the driver - the audio endpoint or whatever its called.
The focusrite support sent me a new driver to try - same problem.
They seem pretty helpful. I expect the next stage would be some special driver creating lots of log files.
One thing I have learned over the years - its vary rare to have a unique problem - someone out there will be seeing the same thing.
The point is it worked until a certain version of Windows 10.
But it is not feasible for me to maintain an old version.
Statistics: Posted by sm_jamieson — 31 May 2020, 19:18
]]>
]]>
There are two places in windows where you have to disable it.
Control Panel/Power Options/Advanced Plan settings/USB settings/USB selective suspending - set as disabled
Control Panel/Device Manager/Universal Serial Bus Controllers and disable "allow the computer to turn off this device" in each usb device in which "power management" tab is avialable
You need to disable it in both places to keep ech USB device ON.
And yeah after each major windows 10 update, windows resets these settings
so you need to check it from time to time.I have a Roland Duo Capture EX audio interface that seems to be playing up more with each Windows 10 update.
It worked perfectly on Windows 10 until sometime last year.
The audio output will cut out after between 5 minutes or half an hour. Switching it off and back on again will reset it,
and also sometimes just switching an audio output off and on in the Usine audio settings, which is weird.
It has done it just running Omnisphere, so its not Usine at fault.
If I use the Duo Capture via asio4all this does not happen, so I expect it is a Roland driver issue. Unfortunately Roland are not
the best at updating drivers.
Anyone else having problems with audio interfaces and Windows 10 ?
Thanks,
Simon.
Statistics: Posted by drakh — 26 May 2020, 08:43
]]>
I think it is a windows bug.
Statistics: Posted by sm_jamieson — 19 May 2020, 17:05
]]>
Well the Focusrite 4i4 is doing the same thing as the Roland. I have all the latest drivers. I uninstalled all the audio devices (windows re-installs them on reboot) and the problem persists. When the sound cuts out, everything else works on the 4i4, changing the settings changes the lights on the front panel, etc.
It happened with windows 10 build 1903 and 1909. Did NOT happen in the 18xx series.
Since this happens with Roland and Focusrite it is obviously a problem in Windows 10.
I am thinking writing a dummy usb asio device driver to try and understand what is happening, but leaning curve is steep.
It seems like something is going to sleep or switch off and activating audio inputs or outputs or change the sample rate wakes it back up.
When it happens the Focusrite Control indicates no audio in the on-screen meters.
I wonder if any of the Usine programming team can help ?
Statistics: Posted by sm_jamieson — 18 May 2020, 21:57
]]>
Statistics: Posted by x.iso — 08 May 2020, 16:50
]]>
]]>
Simon.
Statistics: Posted by sm_jamieson — 17 Apr 2020, 13:55
]]>
The audio output will cut out after between 5 minutes or half an hour. Switching it off and back on again will reset it,
and also sometimes just switching an audio output off and on in the Usine audio settings, which is weird.
It has done it just running Omnisphere, so its not Usine at fault.
If I use the Duo Capture via asio4all this does not happen, so I expect it is a Roland driver issue. Unfortunately Roland are not
the best at updating drivers.
Anyone else having problems with audio interfaces and Windows 10 ?
Thanks,
Simon.
Statistics: Posted by sm_jamieson — 14 Apr 2020, 21:36
]]>