![]() ![]() Like the previous beta driver update, it has only improved my workflow. I recall a Focusrite rep commenting that the 4th series beta drivers are intended to work on 1st gen 2i2/2i4’s, which is why the driver page doesn’t specifically mention 2nd gen 2i2/2i4’s. If it does, I’ll give you a list of all of the updates I haven’t installed and maybe you can isolate some issue-causer. I have a bunch of Windows updates in the pipeline that never installed but I will attempt to install ’em and see if it screws up my situation. The step-by-step disconnect/uninstall/install/reconnect method made it work for me.įor reference I am on 64-bit Windows 7. Now I don’t know if I did some modding to my Windows back when I first got the interface to make it more compatible (who knows?) or something but I went through the whole fiasco of getting blue screens trying to update drivers and the like. Step 6: now when you are back to your Windows desktop, connect your interface and wait. Step 5: (optional?) Restart for the heck of it. Step 3: (optional?) Restart for the heck of it. Step 2: uninstall all of your current interface drivers. The key is to follow the instructions on this page carefully: Very very important.I’ve managed to get all of the beta drivers to work with my first gen 2i4. However RME cards are widely used as professional audio measurement devices, and that is where you need that kind of sampling rate, in order to measure high frequency harmonic distorsion, interference and so on. Some people say it is useless and to an extent they are right, as you don't need it for either recording nor listening to audio material. One big thing is the crazy sampling frequency of 768kHz. Everything can be controlled from the hardware itself. Also the fact that you have no software control panel is a plus, as those things never work in Linux. That is what you pay for, a company that delivers what they claim and does not cut corners. With RME ADI-2 PRO instead I measure exactly 124dBA Dynamic Range 44.1kHz as specified. ![]() I even measured it with input shortcircuit (best case for noise) and powered directly from my linearly-regulated laboratory power supply with no difference. I could see in the spectrum analysis lots of harmonics above the noise floor, probably due to bad power supply design. I got first a Focusrite Clarett 4 Pre but the measured specs were not even close to what they advertise, I measured 101dBA Dynamic Range against the 119dBA specified, ridiculous. For me the noise floor (AKA Dynamic Range) is very important, because I use the ADC to measure low-noise preamplifiers that I build. Yes it's expensive, but I use it for work so the price is justified. ![]() Unifying Receiverīus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hubīus 009 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hubīus 008 Device 002: ID 0499:1509 Yamaha Corp.īus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubĪny idea of what may cause the problem on my specific machine, and in particular, why the problem does not appear on windows with the same exact machine? Keyboard K120īus 001 Device 002: ID 1a40:0201 Terminus Technology Inc. Hubīus 001 Device 004: ID 046d:c31c Logitech, Inc. hg expulsion ats wrttemberg saturation humility scarlett ooh caretaker xm. Webcam C270īus 001 Device 005: ID 1a40:0101 Terminus Technology Inc. parking paint tx drivers bottle represented adults allen readers monthly. Here is the output of lsusb (at the moment the audio interface is connected to USB 2.0):īus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubīus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hubīus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hubīus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubīus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hubīus 001 Device 010: ID 0403:6010 Future Technology Devices International, Ltd FT2232C Dual USB-UART/FIFO ICīus 001 Device 006: ID 046d:0825 Logitech, Inc. So I installed the same Linux mint and kernel on an old lenovo W510, same audio interface, still on USB 2.0 port and I can set QJackctl all the way down to 64-samples-per-frame and 2 buffers without ever having xruns (neither audible nor measured by the software). However I did the same experiment booting windows 10 on the same exact machine and same exact recording software and I can set asio drivers as low as 48 sample buffers without having audible dropouts, even when connected to USB 2.0. I tried disabling wifi and even disconnecting all USB peripherals except for the mouse without success. Connecting it to an USB 3.0 port helps a lot but I still get occasional audible xruns. When my audio interface is connected to USB 2.0 I get many many xruns while reproducing sound or recording. I installed qjackctl and I set it up to 128-sample-per frame, 2 buffers, 48kHz. I wanted to produce some music on linux, so here are my specs:Īudio Interface: Steinberg-Yamaha UR22 (USB 2.0) ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |