Multiple interfaces

[Scott Stillwell]

I would bet that it depends on the hardware...ASIO on the PC is limited to a single driver being loaded at one time. That being said, some manufacturers' drivers support multiple interfaces under the control of a single driver. M-Audio, for example, allows multiple Delta series interfaces to be combined within a single instance of their driver. Same with most MOTU PCI or Firewire devices (but only WITHIN the series...multiple PCI devices, or multiple Firewire devices...but you can't mix them because they use two different drivers)

MOTU PCI/PCIe series is going to take you higher than PT9's supported IO count of 32, anyway...all the way up to 96 inputs on a single card. Same with RME...a single RayDAT card will give you as much IO as you can handle.

Long and short of it...you may be able to use multiple interfaces if they all use the same driver and the hardware vendor supports it, but you won't be able to use multiple mix-and-match interfaces unless you use something like ASIO4ALL, which is not going to be ideal...you won't have any form of clock sync between the interfaces unless it's externally via wordclock.

Scott

[guitardom]

Originally Posted by bwalraven

I had read the info for aggregate interfaces in Mac, but I'm a PC guy...

Anyone have any more info?

BJ

everything i have tried, pt will only load one interface. i have can run multiple converters into an interface and that works fine. i am running multiple units into an rme fireface and works fine. digi will only recognize one and gets the hw buffer info from that unit for latency. each device is viewable in the playback engine and can switch between the main interface mid session, but must restart the session. the other issue at the moment is that if you switch hw buffer mid session it will lock up the session and must actually restart pro tools to get it working again.

[kbruff]

Originally Posted by guitardom

everything i have tried, pt will only load one interface. i have can run multiple converters into an interface and that works fine. i am running multiple units into an rme fireface and works fine. digi will only recognize one and gets the hw buffer info from that unit for latency. each device is viewable in the playback engine and can switch between the main interface mid session, but must restart the session. the other issue at the moment is that if you switch hw buffer mid session it will lock up the session and must actually restart pro tools to get it working again.

interesting

[albee1952]

Originally Posted by bwalraven

I had read the info for aggregate interfaces in Mac, but I'm a PC guy...

Anyone have any more info?

BJ

PT9 is supposed to work with ASIO. I ran a successful test with my M-Audio Fast Track Pro

[bwalraven]

@Scott - that was my understanding of ASIO (and the Delta interfaces in particular) as well. Wondering if anyone out there has tried it yet?

@guitardom - did you have your other converters tied to the computer as well (i.e. firewire, USB, PCI, etc.)? If they were just stand-alone converters hooked to the interface, what you're seeing makes sense...if they were also tied to the computer, then it doesn't look good for me.

Hope to hear from someone who's tried it...

BJ

[Spidouz]

Well, I can't fully confirm, but when I did installed PT9 yesterday, I could aggregate my ProFire Lightbridge (34ch detected) and the Mac Pro built-in audio ports...

With more than one audio interface, we maybe could aggregate them and finally have more I/O.

I'm seeking to use my Lynx Auroras (with the LT-USB) and aggregate them together for 32 I/O in 96kHz and 16 I/O in 192 kHz.

Phil

[CME]

Good to hear. From what I've read the interfaces might have to support being "aggragated". Seems as though avid/digi interfaces might not support this. Anyone else try this yet?

[bonestonne]

As of yet, I get errors when trying to use say two Delta 1010 rack units with PT 9.

I have additional errors that I need to clear up first, may come down to downloading it again...I'm not looking forward to another 7gb download.

Once I get the software actually running where I can open a session, it may be possible to run the Delta 1010's over ASIO, but again, if PT 9 wont launch with both cards enabled, this might still be a no-go situation.

Until I can get the software running on my machine, I can't make any headway. M-Powered installed just fine, but 9 always gives me a weird error:

Could not create a new document because Assertion in
"f:\code\ws.preston\alturaports\dfw\views\umenu.wi n 32.cpp", line 1142.

Uninstalled, reinstalled, exact same error. Asked people at M-Audio/Avid directly, no replies because it's the weekend though. One more day of trying before I throw in the towel and re-download this stuff.

[theDAWstudio]

Pro Tools has finally entered the world of non-proprietary audio interfaces. Pro Tools 9 introduces a handful of new features, but the biggest bombshell is that you no longer have to have a Pro Tools (or Digidesign or now Avid) interface. This is great news, but what about all of the baggage that comes with it?

Read the rest at Avid Pro Tools 9: An Old Player in a New Game

[firefox13]

You can get 4 motu 8 pres and daisy chain them for 32 inputs..
They're like $500.00 a piece