I'm a systems designer, yet I still have no idea how/why these sliders interact. Then it turned out that Latency was changing depending on ?mysteries? The Windows driver has 3 sliders that don't match what any other driver uses. Now that's truly amazing, as it's hard NOT to let the compiler stamp a version number into the code that a system query will display. And there was/is no way to determine which version of the firmware is actually installed in a unit. My problems started with the first firmware update, when some problems were fixed at the cost of the latency increasing. If you're a techie, you can fight your way through most issues OK. It's clear they buy generic drivers with their name stamped on. It's complex stuff, in reality, and although they use the same parts and techniques as everyone else, and sell gear for less, Behringer doesn't have the staff to write drivers and support them. For Windows you must install drivers, and these are pretty baffling. It's more usable on a mac because the driver is effectively embedded in OsX. But it's a little more complicated up close, and it illustrates some of Behringer's issues, so bear with me. The actual sound quality is good, the I/O count is great, the feature/price ratio excellent. I've gone up and down on these, meaning the FCA1616 and the FCA610.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |