multiple Audio interfaces and Pulsar 1 ?

criote · Post by **criote** » Wed Sep 19, 2007 3:58 am

Hi

I ve seen an article in SOS magazine (Feb 2006) issue mentioning that
You can use multiple Audio interfaces using Asio4all drivers.
I want to use Konnekt 24 D with my Pulsar 1 card to record the Synths of Pulsar and to use the Konnekt24 D as an interface to record Guitars , and Vocal for Analog recordings in Cubase 4.
Can You tell me how is this possible and what project to use in Pulsar
( connections)

thanks in advance

Criote

Post by **hubird** » Wed Sep 19, 2007 5:02 am

Scope is not multi client, there are no other ASIO drivers than the ones we have (ASIO1 and ASIO2).

husker · Post by **husker** » Wed Sep 19, 2007 4:58 pm

that wasn't his question - he doesn't want multiple client with 1 card, he wants 1 client with multiple (different) audio interfaces...

in terms of the answer to the question, you should just use the same ASIO project you always use in scope - in theory this will work with ASIO4ALL, although I haven't tried it

astroman · Post by **astroman** » Thu Sep 20, 2007 12:30 am

no, he meant to trash Scope Asio and to use Asio4All instead, as the latter obviously can deal with multiple (brands of) cards simultaneously...

husker · Post by **husker** » Thu Sep 20, 2007 8:01 pm

yes, ASIO4ALL has some magic to wrap mutliple cards together to look like 1 ASIO device - although I think it does this by wrapping WDM drivers (so may not be very successful for Scope?)

valis · Post by **valis** » Fri Sep 21, 2007 3:02 pm

ASIO4All wraps itself around the Wav/WDM drivers, and I wouldn't recommend that for the Scope cards. Also I thought you needed to use the same card type to achieve that? Could be wrong there. However there are other solutions.

My first choice if I was looking at combining those 2 audio devices would be to use the optical port on the Konnekt 24 D as an ADAT connection to the Pulsar1. This would give you 8 channels of i/o between the 2 (versus 2 in spdif format) up to 48khz, and allow you to choose either audio device as your primary ASIO driver. This should also yield the lowest latency of any routing as you're routing via hardware rather than worrying about sharing software layers.

Another potential solution for the more technically inclined is JACK (initially from the Linux audio world) is now supported on Windows.in the newer Jackdmp form: http://www.grame.fr/~letz/jackdmp.html

You can also try to download and install the demo of Reaper which has an interesting audio interconnect called ReaRoute.

Post by **hubird** » Fri Sep 21, 2007 3:33 pm

thanks for that cool summary

valis · Post by **valis** » Sat Sep 22, 2007 2:09 am

There's a halfway decent frontend for patching too. I haven't played with it much since I found out so it slips my mind atm, but I'll fire it up later and post up a link.

What was obvious before I even fired it up was that unlike the open source sequencers and other musical tools, most windows software doesn't support the advanced JACK interfae for transport control, automation compensation etc. I was mostly fiddling around with it since it was basically just an advanced VAC (virtual audio cable) compared to the level of support rewire in commercial software. It would be nice to see Max/PD and bidule gain support, perhaps apps like fruity and reaper.

Nestor · Post by **Nestor** » Sat Sep 22, 2007 3:56 am

I’m not quite sure about JACK. Which would it be its advantage for a Pulsar user? What is it all about?

valis · Post by **valis** » Sat Sep 22, 2007 4:22 pm

Re-phrasing my last post: to a WIndows user it's of limited use atm unless you can find windows ports of open source apps that support the extended functionality of JACK.