AudioScience, Inc.' S Modules and Drivers. If you are looking for a particular module/driver that is not listed or would like to learn more about having a. AudioScience Sound Card Drivers & Utilities. ASI 4000 Cards Important Note: We should like to draw the attention of customers utilizing any older ASI4000 series audio cards (which have been discontinued for some time) in new PCs to the following AudioScience ASI 4000 Series Product Advisory. The ASI5811 is a professional PCI audio adapter designed for use in radio broadcast production. The adapter offer two stereo record streams from either a balanced analog input or AES/EBU digital input and four stereo play streams mixed to both a. AudioScience Drivers and Utilities NOTE: IF USING MULTIPLE AUDIO CARDS IN YOUR COMPUTER WHICH REQUIRE DIFFERENT DRIVER VERSIONS, USE THE LOWEST VERSION NUMBER SPECIFIED If you are not sure which driver to use, or your driver is not listed here please contact Technical Support. . Windows and Linux software drivers available (Visit AudioScience Windows Driver Downloads for Windows 10 drivers and more.) Specifications: BALANCED INPUT/OUTPUT:. Connector: DB-26HD Female with XLRs on breakout cable CBL1312. Input Level: -10 to +24dBu in 1dBu steps. Input Impedance: 20K ohms. Output Level: -10 to +24dBu in.
IMPORTANT NOTICE:
The following are the recommended driver & application versions that have been shown to work well with BSI systems. We DO NOT advise going directly to manufacturers web sites to download drivers as although newer drivers may be available directly from third-party vendors, BSI has not yet certified these to be free of undesirable side-effects until listed here!
BSI (Sentinel) Hardware Key DriverThis Sentinel Hardware Key Driver (also known as the Sentinel Protection Installer) is required for all customers using a BSI Hardware Key (Dongle). It should NOT be installed by customers that are not using Hardware Keys to license their software. This special version of the installer for BSI customers negates the need for any further configuration of the driver as was previously required (that information will be removed in the next revision of manuals). Sentinel Hardware Key Driver for BSI Customersversion 7.5.72.71MB Cleanup Utility for Hardware Key DriverAlthough the following utility should not be used without consulting BSI Tech Support, it is provided for those customers who wish to completely remove the Sentinel Protection System and Driver from their Computers. This will prevent any software using a BSI dongle from working, but can be a useful tool in removing and re-installing drivers in case of corruption or errors with an older install. Sentinel Driver Removal Tool for 32bit Operating Systems |
BSI Trigger/Relay/Closure Kit (Instacal) DriverFor Windows XP & Windows 7 only This driver is required by all versions of the BSI Trigger, Relay & Closure Kits, including the latest USB/PMD1024LS from Measurement Computing. As the driver only supports one instance of an application and one application at a time, you should ensure that the Instacal Utility is closed before attempting to use this application with Simian or WaveCart (only one of which should be open and using the trigger kit at any one time). Multi-instance version of Simian will allow the first (session 1) instance to communicate with the device. Instacal Driver and Utilityversion 6.1016.1MB |
Driver for cards from Matrix:Vendor-AudioScience
|
Card Specific Information
Additional Installation notes
The asihpi driver was merged with mainline kernel at version 2.6.35. However, to keep up with latest developments you may need to build from source.
In addition to the alsa-driver source package, the matching alsa-firmware package must be downloaded, and run 'make install' in the asihpi subdirectory.
If you have installed the hpklinux driver available from AudioScience website, you will end up with two different drivers that can claim the cards. To avoid unexpected behaviour, either remove one of the drivers or blacklist one or both E.g add 'blacklist asihpi' to /etc/modprobe.d/blacklist. If both drivers are blacklisted, it is still possible to load either of them manually using modprobe.
Also you need to take care that incompatible firmware is not installed. In this case, it is recommended to rebuild the alsa driver using source from the hpklinux package (see that package for instructions).
Card indices
AudioScience cards have a hardware jumper to specify the card index. This ensures that cards keep the same index even if they are moved between slots, or other cards are added.
The driver will try to make ALSA card indices match the card jumper settings. This may fail if another card (onboard sound) is present and has already claimed a desired index. The cards will still work, but have unexpected indices.
By default the card name shown by ALSA will be the card model eg 'ASI6644'
PCM streams
AudioScience cards support multiple streams (PCMs). These are exposed as ALSA substreams of device 0. I.e. hw:0,0,0 hw:0,0,1 etc.
The reason the driver doesn't map streams to ALSA devices is that there is a limit of four devices per card, and some cards have up to 16 streams.
Streams do not correspond to physical inputs and outputs, see Mixer section for more on this.
Mixer
control names
Controls use ALSA naming conventions that differ from AudioScience HPI names.
| ALSA | HPI |
|---|---|
| PCM | Stream |
| Capture | In |
| Playback | Out |
| Clock | SampleClock |
| Digital | AES/EBU |
| Mode | ChannelMode |
| Route | Multiplexer |
| Switch | Mute |
| Volume, Level, Meter | same |
For example HPI 'LineOut 0 Level' becomes ALSA 'Line 0 Playback Level'
The general format for an ALSA control name is 'SOURCE SINK DIRECTION TYPE'. Some examples
'PCM 0 Playback Volume' = master volume of player 0
'PCM 0 Line 0 Playback Volume' = matrix volume between player 0 and output 0
'Line 0 Line 0 Monitor Playback Volume' = feedthrough volume from input 0 to output 0
'PCM 0 Capture Route' = select one source for recorder 0 (more common)
'Line 0 PCM 0 Capture Volume' = matrix volume between input 0 and recorder 0 (less common alternative to capture route)
setting card master samplerate
Most cards will have a Sample Rate control. This sets the master samplerate for the card. The default rate will be 44100 or 48000. Setting this to the same rate as your source material means that the card will not have to do sample rate conversion.
Read the control amixer -c1 cget name='Clock0 LocalRate'
Set a new rate amixer -c1 cset name='Clock0 LocalRate' 48000
Level controls
Note that input level controls do not set input gain directly. The setting of an input level control is the full scale input signal level in dBu. So increasing input level control DECREASES the input gain.
Likewise, the setting of output level controls is the fullscale output level in dBu
Linked streams
Most AudioScience cards support multiple independent stereo play and record streams with different formats and samplerates (not ASI5xxx)
ALSA allows streams to be grouped together into a virtual stream with more channels using the multi plugin, maybe also requiring ttable plugin to allow memory mapped operation of the virtual stream.
To support stream grouping with the multi plugin, the card must support mmap. This will be reported in 'dmesg' when the driver loads as Supports mmap:1
Cards which support hardware linking of streams for sample-accurate start and stop report grouping:1
Example definitions for .asoundrc
Capabilities and limitations
- HPI ioctl provided in addition to ALSA interface
- No support for compressed formats, though card supports them
- Limited use of large on card buffers
The module options for snd-asihpi
| description: | AudioScience sound or tuner card |
| author: | AudioScience |
| license: | GPL |
| parm: | index:Index value for AudioScience soundcard. (int) |
| parm: | id:ID string for AudioScience soundcard. (charp) |
| parm: | enable:Enable card(bool) |
| parm: | enable_hpi_hwdep:ALSA enable HPI hwdep for AudioScience soundcard (bool) |
| parm: | hpi_debug_level:Debug level for Audioscience HPI 0:none.5:verbose (int) |
| parm: | prealloc_stream_buf:Preallocate size for per-adapter stream buffer (int) |
Introduction for AudioScience ASIxxxx soundcard
There are two ways of getting Linux drivers to work, you can either compile them into the kernel or build them separately as modules. Read the Kernel-HOWTO for details of how to compile a kernel.
You must turn on the sound support soundcore module. This is in the kernel. Look in the sound drivers directory and it should be the first option. Most people enable the module setting. That way you can load and unload the module manually if you have multiple soundcards/devices or if you intend to debug or use cutting edge software which may cause your drivers to halt sometimes. Of course it also means you have more control of your system.
Most modern distros come with soundcore compiled as a module. You can check this in numerous ways. The easiest way is to type:
If this command returns that you have this module, then you don't need to recompile your kernel.
Quick installation
This explains how to build from source tarballs. See GIT_Server for instructions on getting and using the latest source from git repositories.
Type the following commands in the shell of your choice.
Make a directory to store the alsa source code in:
Now unzip and install the alsa-driver package:
Now unzip and install the alsa-lib package:
Now unzip and install the alsa-firmware package:
Now unzip and install the alsa-utils package:
Now insert the modules into the kernel:
Now adjust your soundcard's volume levels. All mixer channels are muted by default. You must use a native mixer program to unmute appropriate channels, for example alsamixer from the alsa-utils package. Note that some usb-audio devices do not have internal mixer controls. Run:
You can also look at the utils/alsasound file. This script is designed for the RedHat Linux distribution, but it can also be used with other distributions which use System V style rc init scripts. This will allow you to load your modules at boot time. If you don't want to do this you can of course compile them into the kernel instead and save yourself the hassle of coming to terms with the rc init scripts.
Setting up modprobe and kmod support
Before you send a mail complaining that 'I don't have /etc/modules.conf, where do I find it ……' ‒ the /etc/conf.modules has been deprecated with a few distro's, but in your case it may still be /etc/conf.modules. Basically they are both the same, but recent version of modutils use /etc/modules.conf instead. Nothing to worry about as such, optionally please update to the latest version of modutils. This should solve your problem.
Here's the example for this card. Copy and paste this to the bottom of your /etc/modules.conf file.
| Note: | Debian GNU/Linux users need to save this information into a file in the /etc/modutils/ directory (eg. /etc/modutils/alsa) and run update-modules. Note also that the kernel module soundcore has been renamed in Debian kernels >2.6.23 into snd. A workaround is to put a symlink at /lib/modules/x.x.xx/kernel/sound/soundcore.ko pointing to snd.ko |
|---|
| Note: | Systemd users need to save this information into a file in the /etc/modprobe.d/ directory terminating with .conf (eg. /etc/modprobe.d/alsa.conf). BBot 84.1 Posted on Hello guys, this is a continuation of 84.1 duhh The biggest change is the introduction of String variables, that add incredible powers to the Macro engine. Beyond that, we also added a When systems, a kind of event system for macros. We also added several new macros that allow the user to explore more the Tibia. Bbot tibia 8.6. In case of modules auto-loading instead, the module name must be inserted in a file in the/etc/modules-load.d/ directory terminating with .conf (eg. Acdsee pro 7 crack serial. /etc/modules-load.d/alsa.conf). |
|---|
To copy and paste the above to your /etc/modules.conf file follow these instructions.
modules.conf
This is a short explanation of what happens in the /etc/modules.conf file.
Native devices
After the main multiplexer is loaded, its code automatically requests the top level sound card module. String snd-card-%i is requested for native devices where %i is the sound card number, counted from zero (the first sound card) to seven (the eighth sound card). String sound-slot-%i is requested for native devices where %i is slot number for the corresponding ALSA owner (which is basically the sound card number). The options line allows you to set various configuration options before the module is loaded. String id (or snd_id) lets you set the name of the card which is then returned in the /proc/asound/cards file, i.e. to user space applications. Other options may be available depending on the specific card. Options for these cards are found in the INSTALL file or above.
| NB: | For drivers older than 0.9.0rc5 use: |
|---|
| NB: | The 'snd_' prefix has been removed from the module options to fit with the kernel standard. |
|---|
Autoloading OSS/free emulation
At this point we are finished with the configuration for ALSA native devices, but you may also need autoloading for the OSS/Free emulation modules, an ALSA add-on. At this time only one module does not depend on any others, thus must be loaded separately: snd-pcm1-oss. String sound-service-%i-%i is required for OSS/Free service where the first %i is the slot number/sound card number and the second %i is the service number.
The alias for snd-seq-oss is not necessary on the second device, because there is only one /dev/sequencer regardless how many devices you have.
The .asoundrc file
Presonus Driver For Windows 10
This file allows you to have more advanced control over your card/device. For most setups the default, system-wide configuration is sufficient. You may change this file only for special setup. The .asoundrc file consists of definitions for the various sound devices available in your system. It also provides access to the pcm plugins in alsa-lib. These allow you to do tricky things like combine your cards into one or access multiple I/O streams on your multi-channel card.
Below is the most basic definition (only example - not required to define at all).
Make a file called .asoundrc in your home and/or root directory:
Copy and paste the following into the file, then save it:
Software volume control
If your card doesn't have hardware volume control (e. g. Asus Xonar XD/XDG), you might want to create software Master control. Edit .asoundrc as follows.
Restart alsa, then open a music player, play a file and close the player. Then check alsamixer, as you should have a Master volume control. Note that this control doesn't have a mute option.
If you have installed the hpklinux driver available from AudioScience website, you will end up with two different drivers that can claim the cards. To avoid unexpected behaviour, either remove one of the drivers or blacklist one or both E.g add 'blacklist asihpi' to /etc/modprobe.d/blacklist. If both drivers are blacklisted, it is still possible to load either of them manually using modprobe.
Also you need to take care that incompatible firmware is not installed. In this case, it is recommended to rebuild the alsa driver using source from the hpklinux package (see that package for instructions).
Card indices
AudioScience cards have a hardware jumper to specify the card index. This ensures that cards keep the same index even if they are moved between slots, or other cards are added.
The driver will try to make ALSA card indices match the card jumper settings. This may fail if another card (onboard sound) is present and has already claimed a desired index. The cards will still work, but have unexpected indices.
By default the card name shown by ALSA will be the card model eg 'ASI6644'
PCM streams
AudioScience cards support multiple streams (PCMs). These are exposed as ALSA substreams of device 0. I.e. hw:0,0,0 hw:0,0,1 etc.
The reason the driver doesn't map streams to ALSA devices is that there is a limit of four devices per card, and some cards have up to 16 streams.
Streams do not correspond to physical inputs and outputs, see Mixer section for more on this.
Mixer
control names
Controls use ALSA naming conventions that differ from AudioScience HPI names.
| ALSA | HPI |
|---|---|
| PCM | Stream |
| Capture | In |
| Playback | Out |
| Clock | SampleClock |
| Digital | AES/EBU |
| Mode | ChannelMode |
| Route | Multiplexer |
| Switch | Mute |
| Volume, Level, Meter | same |
For example HPI 'LineOut 0 Level' becomes ALSA 'Line 0 Playback Level'
The general format for an ALSA control name is 'SOURCE SINK DIRECTION TYPE'. Some examples
'PCM 0 Playback Volume' = master volume of player 0
'PCM 0 Line 0 Playback Volume' = matrix volume between player 0 and output 0
'Line 0 Line 0 Monitor Playback Volume' = feedthrough volume from input 0 to output 0
'PCM 0 Capture Route' = select one source for recorder 0 (more common)
'Line 0 PCM 0 Capture Volume' = matrix volume between input 0 and recorder 0 (less common alternative to capture route)
setting card master samplerate
Most cards will have a Sample Rate control. This sets the master samplerate for the card. The default rate will be 44100 or 48000. Setting this to the same rate as your source material means that the card will not have to do sample rate conversion.
Read the control amixer -c1 cget name='Clock0 LocalRate'
Set a new rate amixer -c1 cset name='Clock0 LocalRate' 48000
Level controls
Note that input level controls do not set input gain directly. The setting of an input level control is the full scale input signal level in dBu. So increasing input level control DECREASES the input gain.
Likewise, the setting of output level controls is the fullscale output level in dBu
Linked streams
Most AudioScience cards support multiple independent stereo play and record streams with different formats and samplerates (not ASI5xxx)
ALSA allows streams to be grouped together into a virtual stream with more channels using the multi plugin, maybe also requiring ttable plugin to allow memory mapped operation of the virtual stream.
To support stream grouping with the multi plugin, the card must support mmap. This will be reported in 'dmesg' when the driver loads as Supports mmap:1
Cards which support hardware linking of streams for sample-accurate start and stop report grouping:1
Example definitions for .asoundrc
Capabilities and limitations
- HPI ioctl provided in addition to ALSA interface
- No support for compressed formats, though card supports them
- Limited use of large on card buffers
The module options for snd-asihpi
| description: | AudioScience sound or tuner card |
| author: | AudioScience |
| license: | GPL |
| parm: | index:Index value for AudioScience soundcard. (int) |
| parm: | id:ID string for AudioScience soundcard. (charp) |
| parm: | enable:Enable card(bool) |
| parm: | enable_hpi_hwdep:ALSA enable HPI hwdep for AudioScience soundcard (bool) |
| parm: | hpi_debug_level:Debug level for Audioscience HPI 0:none.5:verbose (int) |
| parm: | prealloc_stream_buf:Preallocate size for per-adapter stream buffer (int) |
Introduction for AudioScience ASIxxxx soundcard
There are two ways of getting Linux drivers to work, you can either compile them into the kernel or build them separately as modules. Read the Kernel-HOWTO for details of how to compile a kernel.
You must turn on the sound support soundcore module. This is in the kernel. Look in the sound drivers directory and it should be the first option. Most people enable the module setting. That way you can load and unload the module manually if you have multiple soundcards/devices or if you intend to debug or use cutting edge software which may cause your drivers to halt sometimes. Of course it also means you have more control of your system.
Most modern distros come with soundcore compiled as a module. You can check this in numerous ways. The easiest way is to type:
If this command returns that you have this module, then you don't need to recompile your kernel.
Quick installation
This explains how to build from source tarballs. See GIT_Server for instructions on getting and using the latest source from git repositories.
Type the following commands in the shell of your choice.
Make a directory to store the alsa source code in:
Now unzip and install the alsa-driver package:
Now unzip and install the alsa-lib package:
Now unzip and install the alsa-firmware package:
Now unzip and install the alsa-utils package:
Now insert the modules into the kernel:
Now adjust your soundcard's volume levels. All mixer channels are muted by default. You must use a native mixer program to unmute appropriate channels, for example alsamixer from the alsa-utils package. Note that some usb-audio devices do not have internal mixer controls. Run:
You can also look at the utils/alsasound file. This script is designed for the RedHat Linux distribution, but it can also be used with other distributions which use System V style rc init scripts. This will allow you to load your modules at boot time. If you don't want to do this you can of course compile them into the kernel instead and save yourself the hassle of coming to terms with the rc init scripts.
Setting up modprobe and kmod support
Before you send a mail complaining that 'I don't have /etc/modules.conf, where do I find it ……' ‒ the /etc/conf.modules has been deprecated with a few distro's, but in your case it may still be /etc/conf.modules. Basically they are both the same, but recent version of modutils use /etc/modules.conf instead. Nothing to worry about as such, optionally please update to the latest version of modutils. This should solve your problem.
Here's the example for this card. Copy and paste this to the bottom of your /etc/modules.conf file.
| Note: | Debian GNU/Linux users need to save this information into a file in the /etc/modutils/ directory (eg. /etc/modutils/alsa) and run update-modules. Note also that the kernel module soundcore has been renamed in Debian kernels >2.6.23 into snd. A workaround is to put a symlink at /lib/modules/x.x.xx/kernel/sound/soundcore.ko pointing to snd.ko |
|---|
| Note: | Systemd users need to save this information into a file in the /etc/modprobe.d/ directory terminating with .conf (eg. /etc/modprobe.d/alsa.conf). BBot 84.1 Posted on Hello guys, this is a continuation of 84.1 duhh The biggest change is the introduction of String variables, that add incredible powers to the Macro engine. Beyond that, we also added a When systems, a kind of event system for macros. We also added several new macros that allow the user to explore more the Tibia. Bbot tibia 8.6. In case of modules auto-loading instead, the module name must be inserted in a file in the/etc/modules-load.d/ directory terminating with .conf (eg. Acdsee pro 7 crack serial. /etc/modules-load.d/alsa.conf). |
|---|
To copy and paste the above to your /etc/modules.conf file follow these instructions.
modules.conf
This is a short explanation of what happens in the /etc/modules.conf file.
Native devices
After the main multiplexer is loaded, its code automatically requests the top level sound card module. String snd-card-%i is requested for native devices where %i is the sound card number, counted from zero (the first sound card) to seven (the eighth sound card). String sound-slot-%i is requested for native devices where %i is slot number for the corresponding ALSA owner (which is basically the sound card number). The options line allows you to set various configuration options before the module is loaded. String id (or snd_id) lets you set the name of the card which is then returned in the /proc/asound/cards file, i.e. to user space applications. Other options may be available depending on the specific card. Options for these cards are found in the INSTALL file or above.
| NB: | For drivers older than 0.9.0rc5 use: |
|---|
| NB: | The 'snd_' prefix has been removed from the module options to fit with the kernel standard. |
|---|
Autoloading OSS/free emulation
At this point we are finished with the configuration for ALSA native devices, but you may also need autoloading for the OSS/Free emulation modules, an ALSA add-on. At this time only one module does not depend on any others, thus must be loaded separately: snd-pcm1-oss. String sound-service-%i-%i is required for OSS/Free service where the first %i is the slot number/sound card number and the second %i is the service number.
The alias for snd-seq-oss is not necessary on the second device, because there is only one /dev/sequencer regardless how many devices you have.
The .asoundrc file
Presonus Driver For Windows 10
This file allows you to have more advanced control over your card/device. For most setups the default, system-wide configuration is sufficient. You may change this file only for special setup. The .asoundrc file consists of definitions for the various sound devices available in your system. It also provides access to the pcm plugins in alsa-lib. These allow you to do tricky things like combine your cards into one or access multiple I/O streams on your multi-channel card.
Below is the most basic definition (only example - not required to define at all).
Make a file called .asoundrc in your home and/or root directory:
Copy and paste the following into the file, then save it:
Software volume control
If your card doesn't have hardware volume control (e. g. Asus Xonar XD/XDG), you might want to create software Master control. Edit .asoundrc as follows.
Restart alsa, then open a music player, play a file and close the player. Then check alsamixer, as you should have a Master volume control. Note that this control doesn't have a mute option.
Links
Generic
- Keep up to date with the news at M-Station
- The most current book about Linux audio is Linux Music and Sound (September 2000)
- Find more applications at Sound & MIDI Software For Linux SourceForge
- For professional quality, low latency audio routing use JACK ‒ the 'Jack Audio Connection Kit'.
Specific
- Old User contributed notes at www-old.alsa-project.org (old page)
Audio Science Sound Card Drivers
