Rescue
Registrierter Benutzer
hab ich gerade auf den Steinbergserver gefunden
könnte mal einer der der Technik affinen Mods Stellung dazu nehmen? ist es das wovon alle träumen?
ftp://ftp.steinberg.net/Download/Hardware/ASIO_multiclient_driver/
ASIO Multiclient Wrapper
*please* read this first remark in order to avoid problems, it's simple:
After installation, you should proceed as follows:
- start the ASIO Server application and select the target ASIO driver.
- start each application that is to be used with the ASIO Client
seperately, select the ASIO Client as the application's audio
device, and exit the application before proceeding to the next one.
This way you avoid possible problems which may occur with the
target ASIO driver when it is beeing accessed directly, and at the
same time by the ASIO Multiclient wrapper. You only need to run
this procedure once.
But what is it?
ASIO (Audio Streaming Input Output) is a technology of Steinberg.
It allows for low latencies and pretty much every state-of-the-art
audio device is nowadays delivered with an ASIO driver
(on Windows, at least). However, the basic idea behind ASIO is
that professional audio applications entirely take ownership of
the ASIO device.
Only very few ASIO drivers support true multiple application
access. This effectively means that you can not use 2 or more
applications using the same ASIO device at the same time.
The ASIO Multiclient wrapper overcomes this problem by
providing a 'proxy' ASIO driver (the ASIO client), several of
which can connect to the one ASIO Server, which in turn
'speaks' to the target ASIO device (driver). The server mixes
the output streams of all applications, and provides that mix
to the target device.
Restrictions:
- You can not change the block size (also named buffer
size, or latency setting) of the target driver while an application
is using the ASIO client (you can tell that an ASIO Client is
active when the ASIO Server window is opened or minimized).
- all applications using the ASIO Client should be set to the
same sampling rate (there can only be one common sampling
rate, naturally).
It's best to avoid problems with block size and sampling rate
by setting these up in the target drivers' control panel before
starting any application using the ASIO Client, and to not
attempt to change these settings while any such application
is running.
ASIO Server window:
You can start the ASIO Server at any time. It is automatically
started when the first ASIO Client is activated, and closes
when the last client exits. When you invoke the ASIO Server
manually, it does not consume resources as it does not
activate the target ASIO driver before the first client signs in.
The upper menu selects the target ASIO driver (this is of course
only possible when no client is active). This setting is beeing
remembered and restored whenever the server opens.
Below that menu is a list of active applications using the
ASIO client application (if any), and their started state (if any
application is in the started state, the ASIO driver is started
and streams audio).
Then there is an info text which also shows errors etc when
the ASIO Server encounters problems with the target ASIO driver.
Finally:
Pls note that there is no warranty whatsoever. If you encounter
problems with specific devices, let us know. No support
promised but you can try contact info@vidance.com
Disclaimer:
The owner and distributor of this freeware, Karl Steinberg, accepts
no responsibility for damages resulting from the use of these files
and makes no warranty or representation, either express or implied,
including but not limited to, any implied warranty of merchantability
or fitness for a particular purpose. This software is provided "AS IS",
and you, its user, assume all risks when using it.
Use at your own risk!
könnte mal einer der der Technik affinen Mods Stellung dazu nehmen? ist es das wovon alle träumen?
ftp://ftp.steinberg.net/Download/Hardware/ASIO_multiclient_driver/
ASIO Multiclient Wrapper
*please* read this first remark in order to avoid problems, it's simple:
After installation, you should proceed as follows:
- start the ASIO Server application and select the target ASIO driver.
- start each application that is to be used with the ASIO Client
seperately, select the ASIO Client as the application's audio
device, and exit the application before proceeding to the next one.
This way you avoid possible problems which may occur with the
target ASIO driver when it is beeing accessed directly, and at the
same time by the ASIO Multiclient wrapper. You only need to run
this procedure once.
But what is it?
ASIO (Audio Streaming Input Output) is a technology of Steinberg.
It allows for low latencies and pretty much every state-of-the-art
audio device is nowadays delivered with an ASIO driver
(on Windows, at least). However, the basic idea behind ASIO is
that professional audio applications entirely take ownership of
the ASIO device.
Only very few ASIO drivers support true multiple application
access. This effectively means that you can not use 2 or more
applications using the same ASIO device at the same time.
The ASIO Multiclient wrapper overcomes this problem by
providing a 'proxy' ASIO driver (the ASIO client), several of
which can connect to the one ASIO Server, which in turn
'speaks' to the target ASIO device (driver). The server mixes
the output streams of all applications, and provides that mix
to the target device.
Restrictions:
- You can not change the block size (also named buffer
size, or latency setting) of the target driver while an application
is using the ASIO client (you can tell that an ASIO Client is
active when the ASIO Server window is opened or minimized).
- all applications using the ASIO Client should be set to the
same sampling rate (there can only be one common sampling
rate, naturally).
It's best to avoid problems with block size and sampling rate
by setting these up in the target drivers' control panel before
starting any application using the ASIO Client, and to not
attempt to change these settings while any such application
is running.
ASIO Server window:
You can start the ASIO Server at any time. It is automatically
started when the first ASIO Client is activated, and closes
when the last client exits. When you invoke the ASIO Server
manually, it does not consume resources as it does not
activate the target ASIO driver before the first client signs in.
The upper menu selects the target ASIO driver (this is of course
only possible when no client is active). This setting is beeing
remembered and restored whenever the server opens.
Below that menu is a list of active applications using the
ASIO client application (if any), and their started state (if any
application is in the started state, the ASIO driver is started
and streams audio).
Then there is an info text which also shows errors etc when
the ASIO Server encounters problems with the target ASIO driver.
Finally:
Pls note that there is no warranty whatsoever. If you encounter
problems with specific devices, let us know. No support
promised but you can try contact info@vidance.com
Disclaimer:
The owner and distributor of this freeware, Karl Steinberg, accepts
no responsibility for damages resulting from the use of these files
and makes no warranty or representation, either express or implied,
including but not limited to, any implied warranty of merchantability
or fitness for a particular purpose. This software is provided "AS IS",
and you, its user, assume all risks when using it.
Use at your own risk!
- Eigenschaft
Zuletzt bearbeitet:
