DevonB

They didn´t need "drivers" w/ Logic and Sounddiver, but IIRC, when using ´em outside of these apps, they needed Unitor8Control app at least for configuration,- no ? On one of my harddrives I just found "UnitorMIDIDriver.dmg for Unitor8_AMT_MT4 and OS X 10.5.7 as also "Unitor8_Control.dmg" files. I use AMT interfaces for Powerbook G3/MacOS9.22 and Powerbook G4/OS X 10.4.11 ... Sounddiver 3.0.4 and Logic 6.4.3. IIRC, installing Unitor8Control automaticly installs a driver. A.C. Forgive me, but I sold my AMT8/Unitor8 config back in 2010 and went with a MOTU setup instead since I'm on PC, so things are a bit fuzzy in the head. However, looking at the manual, there is Computer Mode and Patch Mode. Once you set up your interfaces, you could save it and do patch mode without the computer, which would have all your routing set up. I do miss being able to actually name my MIDI ports. Even the MOTU won't let you do that on the PC, just the Mac. http://www.deepsonic.ch/deep/docs_manuals/emagic_unitor8_mkII_amt8_manual.pdf Devon

Mike, while 'technically' not one unit, you could daisy chain up to 8 Emagic AMT8/Unitor 8 and have them as one unit doing 64 ins and 64 outs. Since drivers stopped working after Windows XP for them, I'll defer over to you as the Mac guy, on configuring them. As I recall they didn't need any drivers with OSX? You could use them without a computer once you initially set them up. Devon

Hate to break it to you, but that iPad is still a computer. I've not tried doing massive daisy chaining myself as every synth I have is on its own dedicated MIDI Out, and some have both on Out and In. However, I would suggest careful planning and documentation, and take it one step at a time. Figure out what you think it might all look like on paper first (or Excel spreadsheet or whatever makes you comfortable) and do it one step at a time. Trying everything at once is like boiling the ocean and can be overwhelming sometimes too. What I'm worried about is something in the chain breaks the rest of the chain, and you lose where you started from and don't know how to get back to what was working.For example, I have some issues with my new Korg Minilogue XD. With MIDI Clock set to External and MIDI In and Out hooked up to my MOTU MTP 8x8, it literally messes with every other synth on my MIDI interface, like significant lag, missing notes, etc when controlled from my master keyboard. Heck, even the waveform display goes wonky during this issue. If I remove the MIDI Out cable or set MIDI Clock to Internal, everything returns to normal. I tried writing support twice and never could get an answer. So also expect to not get help on gear, even if it's new sometimes too. Bottom line, keep a log of how you configure everything. Label your cables with address labels and write on those. If you change a setting in one of your synths, write that down. Hopefully you just hook it all up at once, and it all works. However, I'm more realistic, and expect something to not work as planned. Devon

I am a PC guy. A few observations - Forget MIDI in this whole conversation. It has nothing to do with audio and just clouds trying to figure out what is going on. ASIOForAll was designed for audio cards that did not have an ASIO driver written for them specifically. For example, the onboard ReakTek audio likely doesn't have ASIO drivers for it, so in this case, you'd use it. Otherwise, I'd always use the manufacturers drivers. Since it's Line6, I doubt they don't have an ASIO driver for WIndows. Get the latest driver for your Line6 device. Drivers are finicky things, esp between OS's. I've had Windows 3.1 drivers work on Windows 95. I've had Win95 drivers work on XP, I've known Win7 drivers to work on Win10.... but not always. Best to always get the drivers that were designed for your OS. If this worked before, and now it doesn't, it could have been something that was updated that no longer works with your system. Using old XP drivers on Win7 and the USB driver got updated might be the problem? Again, get the latest drivers from Line 6. Your latency buffer is very very high. If it was 32 or 64, then I'd believe possibly that's the problem, but it's 3072. Anything for real time I wouldn't go higher than 256 as you'll typically notice the 'lag' of your playing to the sound coming out your speakers. Few things to try - normal process of elimination. Try another USB port. Check to see what the Line6 device requires - If it's a USB2.1 device, don't put it on a USB1 port. Try another USB cable. Try doing this on a different PC to see if it's the PC or the device. It's all a pain, especially if this was working, but you'd got to go through this. If this does the same thing on a different PC, then I'd say it's the Line 6 device died potentially. I would also output your guitar into another interface that you know works. If that works, then it's the Line6. It could be your guitar. Try another device into the Line6 as well. Short answer - swap everything around and see what's the issue; the guitar, the interface or the PC. Devon