ilya.pastushenko wrote: RME Support wrote: ilya.pastushenko wrote:
And no support from RME. Is this like you are buying interface that costs almost 1000 $ and you are supposed to figure out why it is not working properly by yourself ?
From what I see here, it's more of an issue of the computer not working as it should, which has little to do with the price of the interface. Unless something is actually defective, it's not the Babyface that causes these problems...
What exactly allows you to make assumptions like this one ?
What exactly is wrong with my PC/OS ?
As far as I can see I did not provide any information that compromises my PC. I have operable PC that did not show any defect for the long time and it works perfectly in any other situation except unstable working of RME driver.
I provided all test that were asked - no problem found.
Even if there is some problem with OS/PC why your system requirements did not mentioned exact specification that should be provided to support this interface ? If some OS tweaking needed why exact instruction is not provided in guide ?
Buying equipment like this I expect it to be plug and play device that should work perfectly without any additional effort. What I've got - you buy audio interface and supposed to play guess game to find out by yourself what exactly should I do to suffice obscure requirements of this audio interface.
And more thing: if your equipment and driver is perfect in every situation - why there is so much threads and topics in variety of forums where people are complaining about same problem ?
Hi, sorry to hear about your problems. Maybe a few background informations ..
Why do you think there are still companies on the market selling audio optimized / tested audio workstations for up to double of HW price because testing and optimizing costs time ? If the PC HW world was as good as you want it to be, then no one would really need them, but they are still there.
There are many ways for a computer to fail. In the area of BIOS, hardware, interrupt processing, bad drivers, bad installation, internal organization of PCIe lanes, temperature and possibly clock fluctuations and that was not all.
Audio makes tough demands on a computer system in terms of timely processing of audio and the more channels a recording interface has, the more audio data must be processed in a timely manner.
But Windows is not a real-time OS, which could also ensure in the area of low level routines (processing of kernel code) that drivers and programs from the audio area do not come up short in terms of CPU time. Thus, it also depends on the devices and the programming of their drivers whether everything works properly (DPC latencies, bad programming of drivers that block a core for too long on which potentially an audio related low level routine or process is waiting).
Even on a good working system a driver update can cause issues and much higher DPC latencies, because sometimes the programming changes. So that CPU cores become blocked for too long by a running driver code. The problem is, that the normal process scheduler may not control/end this job. Only the driver itself is allowed to detach itself from the CPU core on a non-real time OS for data consistency reasons so that nothing gets lost during I/O operations. You can only hope, that developers stick to recommended programming conventions, how long at maximum a driver / low level routine shall utilize a CPU core.
Furthermore, there are even bigger differences if you have a desktop or laptop, with the latter the performance is not as
high and you still have to compromise on the clock and performance because of heat development. Then there are possible problems in chipsets, for example USB is sometimes not implemented without problems, then, as MC mentioned you can try to solve this by a) trying every USB port on your system and if you do not find a good working one b) getting a separate PCIe USB card with USB chipset that is known to work. Also with the goal to isolate audio traffic / the interface to another USB infrastructure of this separate card.
This is a wide topic. Usually it works quite well, but it can also fail and you need to find out, what solves the issues best or try to get working compromises with e.g. higher ASIO buffersizes.
My next PC will be from such a manufacturer, because I know how much time it may take to get a good working system and I think after I made this exercise once, I do not need / want to repeat that again.
X10SRi-F, E5-1650v4, Win10Pro21H1, Cub11Pro, UFX+, XTC, 12Mic, ADI-2 Pro FS R BE, RayDAT