![focusrite usb asio mix in buffer switch fl studio focusrite usb asio mix in buffer switch fl studio](https://i.redd.it/iuoc91h5yd471.jpg)
- Focusrite usb asio mix in buffer switch fl studio drivers#
- Focusrite usb asio mix in buffer switch fl studio Patch#
- Focusrite usb asio mix in buffer switch fl studio windows 10#
- Focusrite usb asio mix in buffer switch fl studio Pc#
I can now record up to 32 simultaneous channels using the MLAN ASIO device. My first attempt didn't work due to an incompatible firewire card, but getting a Belkin F5U502ea (£10 off eBay) solved this.
Focusrite usb asio mix in buffer switch fl studio windows 10#
I managed to get MLAN working on Windows 10 64 bit, and it seems pretty stable so far. In this case, all units function together as a single audio interface. If you need more I/O, get a proper setup where you can add additional I/O units. If you're dealing with two different record-latency figures, the only way to resolve that would be to manually correct for one interface (sliding all audio recorded by it) after recording. This is why Sonar/CbB (and most other DAWs) have a Record-Latency-Adjustment parameter.
Focusrite usb asio mix in buffer switch fl studio drivers#
Many ASIO drivers don't report the exact record-latency correctly. That means your audio tracks (across audio interfaces) would be slightly out of sync (phase issues/etc). The odds of both audio interfaces having the exact same record-latency (in samples) is minute. Even if the audio interfaces are word-clock sync'd. The main reason for introducing the mLAN setup was to avoid having to constantly "rewire" everything when using different outboard pre-amps, so I can have everything setup, and use the mLAN patchbay GUI to re-route things as required.įWIW, Trying to use two different ASIO audio interfaces simultaneously (via creating a software-based "aggregate device") is almost begging for problems. The more I think about it, I'll probably live with my current setup. Use Sonar 8.5 or X1 on the laptop or a separate boot on the PC, and use that for tracking. Switch to mLAN ASIO giving me the 32 inputs / outputs, although I'm not sure what the latency would be for the mLAN drivers.
![focusrite usb asio mix in buffer switch fl studio focusrite usb asio mix in buffer switch fl studio](https://i.ytimg.com/vi/G_4_hIoBtQI/maxresdefault.jpg)
Switch to WDM giving me both devices for recording my first lot of tracks or 2. If I really do need to record more than 8 tracks (which to be honest, is very rare), I've got a few choices: 1. In saying that, maybe it's not such a big deal. This would give me 32 inputs/outputs mLAN via ASIO, with the 18 / 20 focusrite inputs & outputs on top.
Focusrite usb asio mix in buffer switch fl studio Pc#
The idea was to try to get mLAN working on my main studio PC rather than the laptop (quite a few people have got this working, but I'm not sure how stable this is).
![focusrite usb asio mix in buffer switch fl studio focusrite usb asio mix in buffer switch fl studio](https://miro.medium.com/max/1400/0*tWkOiBKS_ltOPIq4.jpg)
However, it does limit me to recording only 8 tracks of the mLAN setup at once. This works pretty well, as it gives me a crazy amount of inputs. The 01x is used as an additional "Mackie" controller, which I use for controlling busses. One of the i88x's is connected via ADAT input to the Focusrite, the other i88x to the ADAT output, with a Behringer ADA8000 connected to the 2nd i88x's ADAT input.
Focusrite usb asio mix in buffer switch fl studio Patch#
My mLAN setup is effectively separate: a Yamaha 01X with 2 x i88x, connected to an old laptop running Vista (which basically acts as a patch bay GUI). I've got a Focusrite Scarlett 18i20 which unfortunately has only one ADAT input / output. This is basically what I'm doing at the moment. If they’re RME or one of the other manufacturers who write ASIO drivers which allow more than one of their imterfaces to work at the same time then that would be the preferred way to go. If the devices - I’m assuming they’re audio interfaces - have ADAT connections, linking them via ADAT might be a way to go. but this might well involve using another buffer, further increasing latency. It did occur to me after writing my post that the overall round-trip could be different between ASIO devices. At the very least, I'd have to report the slowest round-trip and work out the best way to delay the faster one. But how big this improvement can be is a good question. Theoretically ASIO4ALL based on ASIO end points can perform better then current. Even when devices are synced on sample level, so there is no drift in regularity of buffers exchange, the request to do so will come at different time from different real ASIO driver. I think the solution unavoidably add extra latency. Azslow3 msmcleod All of my devices are currently word-clock synced via the BNC word-clock input, so assuming that they also need to have an identical buffer size, can you see any reason why this wouldn't work?Īdding in a wrapper might add some extra latency as well.