The new audio interface I got for the station crashed, and this happened… luckily it was only a test.


Comments

12 responses to “Audio Interface Crash”

  1. KanawhaCountyWX Avatar
    KanawhaCountyWX

    I actually only recently got this interface for the station so I know the Focusrite drivers are up to date. At some point here soon (later tonight I think) I’m gonna take the station down for a while and try half a dozen different troubleshooting ideas I’ve got kicking around.

  2. EugeniuszPompiusz Avatar
    EugeniuszPompiusz

    Right, this is quite an optimal setup for this interface.

    Yes, this dell should have an USB 2 port, usually at the fromt of the machine.

    Also make sure if the USB hub driver in the system, the whole driver package is the latest.
    Updating focusrite drivers, even though it is 2nd gen should also help; they are lazy but they’re fixing bugs over time

  3. KanawhaCountyWX Avatar
    KanawhaCountyWX

    tHIS IS A fOCUSrITE sCARLETT 2i2 2ND GEN AUDIO INTERFACE CONNECTED TO A dELL oPTIPLEX 5070 mICRO, IT’S USING A 9TH GEN iNTEL cpu. i’M WORKING ON INCREASIN THE BUFFER SIZE, BUT i’LL TRY AND SEE IF THE MACHINE HAS ANY usb 2.0 PORTS AS WELL. iT IS DIRECTLY CONNECTED TO THE COMPUTER, NOT PASSING THROUGH ANY EXTERNAL HUBS.

  4. EugeniuszPompiusz Avatar
    EugeniuszPompiusz

    In short, glitches are caused by the fact that the same audio equipment uses few internal sub-interfaces at the USB protocol layer, supported by different drivers for each.
    From the operating system perspective these interfaces are a "composite device" not just an audio class and respective midi driver if any.

    Issues occur, when for instance some part of the device (this i2C chip responsible for controlling routing, phantom etc.), tells the system that it can safely energy save, but another part, for instamce the main audio driver transmitting PCM data internally across channels does not allow for energy saving.
    Then the master clock, synchronous vs asynchronous transfer issue occurs etc. etc.

  5. EugeniuszPompiusz Avatar
    EugeniuszPompiusz

    Try plugging the interface into an USB 2.0 port. Make sure that selective suspend is disabled for both the device and an USB hub you’re plugging the device into.
    Of course by hub I mean the internal unit inside PC.
    BTW: Geeky stuff: Are you using focusrite products for that?

    If this is a laptop, then things may get a little complicated, since the Intel stuff for 10th gen chips onwards is much much more integrated and a lot of new CPU/IO dependencies arises

  6. KanawhaCountyWX Avatar
    KanawhaCountyWX

    What is PipeWire?

  7. GraceDontmindbeingblind Avatar
    GraceDontmindbeingblind

    Oh wow, thats not good. I had pipe wire do that before.

  8. KanawhaCountyWX Avatar
    KanawhaCountyWX

    There’ll be slightly more latency, but hopefully this weird glitching won’t happen.

  9. Landon205 Avatar
    Landon205

    And what will happen when you incress the buffer to 1024?

  10. KanawhaCountyWX Avatar
    KanawhaCountyWX

    I don’t know how it happened, I think it’s some USB weirdness. If it happens again I’m gonna try increasing the buffer size to 1024.

  11. zlunglrg Avatar
    zlunglrg

    lmao good thing I was listening to asuracast

  12. Landon205 Avatar
    Landon205

    Oh boy, that doesn’t sound good. How did the audio interface crash?

Leave a Reply

Your email address will not be published. Required fields are marked *

EltenLink