Lines Matching refs:and
16 they are gone forever. Keeping this in mind and with a grain of salt this
17 document can be still interesting and very helpful.
25 Please read the SOUND-HOWTO (available from sunsite.unc.edu and other Linux FTP
27 date but still very useful. Information about bug fixes and such things
37 Packages "snd-util-3.8.tar.gz" and "snd-data-0.1.tar.Z"
57 Craig Metz 1/2 of the PAS16 Mixer and PCM support
59 Mika Liljeberg uLaw encoding and decoding routines
61 Greg Lee Volume computation algorithm for the GUS and
66 Anders Baekgaard Bug hunting and valuable suggestions.
69 Megens SA MIDI recording for SB and SB Pro (initial version).
70 Mikael Nordqvist Linear volume support for GUS and
73 Markus Aroharju and
91 patches and your name is not in the above list, please inform me.
113 Ensoniq Corp, a SoundScape card and extensive amount of assistance
144 good default configuration to use. Please try to use same I/O, DMA and IRQ
151 The following errors are likely with /dev/dsp and /dev/audio.
156 this particular device. For example /dev/audio and /dev/dsp will not
183 read the above notice. Then try to find proper directory where and how
195 - Configure and compile Linux as normally (remember to include the
197 for instructions about configuring and compiling kernel. File Readme.cards
201 Boot time configuration (using lilo and insmod)
234 (OSS/Linux) and its configuration is available from
251 "Support for /dev/dsp and /dev/audio"). The default values
281 In addition some applications require 16 bit mode and they produce just
289 software selectable IRQ and DMA settings. If the (power on default) values
298 Plug & Play is a protocol defined by Intel and Microsoft. It lets operating
299 systems to easily identify and reconfigure I/O ports, IRQs and DMAs of ISA
301 (versions 2.1.x and earlier) don't support PnP. This means that you will have
305 There are sometimes both PnP and non-PnP versions of the same sound card.
326 How to use sound without recompiling kernel and/or sound driver
329 There is a commercial sound driver which comes in precompiled form and doesn't
338 soft configuring their I/O, IRQ, DMA and shared memory resources.
339 Currently at least cards made by Creative Technology (SB32 and SB32AWE
340 PnP), Gravis (GUS PnP and GUS PnP Pro), Ensoniq (Soundscape PnP) and
342 chip by Crystal Semiconductor (Intel Atlantis, HP Pavilion and many other
359 work now. "Proper" means that I/O, IRQ and DMA settings are the same as in
380 should do it if you don't want to spend time recompiling the kernel and
389 card (usually SB, MSS/WSS and/or MPU401). The following cards have native
393 Pro Audio Spectrum 16 (PAS16) and compatibles:
398 and will not be supported by the driver.
413 NOTE! AWE63/Gold and 16/32/AWE "PnP" cards need to be activated
426 Forget the SB compatibility and check for other alternatives
430 only other SB compatible chips are ESS and Jazz16 chips
438 you get it working it may cause problems with games and
453 GUS ACE (No MIDI port and audio recording)
456 MPU-401 and compatibles
458 cards (such as MPU IPC-T and MQX-32M) and with the UART only
470 (AD1848 by Analog Devices and CS4231/CS4248 by Crystal Semiconductor).
473 MediaTrix AudioTrix Pro and TB Tropez (GUS MAX is not MSS compatible).
484 Yamaha FM synthesizers (OPL2, OPL3 (not OPL3-SA) and OPL4)
488 FM chip which provides better sound quality and/or more available
489 voices than the OPL2. The OPL4 is a new chip that has an OPL3 and
492 SM Wave and AudioTrix Pro) support the OPL4 mode using MPU401
502 to the FM synth this chip has also digital audio (WSS) and
509 (Intel) motherboards and on cheap sound cards. It should not be
511 different chip. OPL3-SA1 has support for MSS, MPU401 and SB Pro
515 are PnP chips and will not work with the OPL3-SA1 driver. You should
516 use the standard MSS, MPU401 and OPL3 options with these chips and to
530 selecting the CONFIG_SOFTOSS_RATE and CONFIG_SOFTOSS_VOICES
550 after minor modifications). For example gmod/xgmod and playmidi -g are
566 Analog Devices and Echo Speech have together defined a sound card
568 for emulation of SB Pro, FM and General MIDI/MT32.
571 ones are Orchid SW32 and Cardinal DSP16.
579 The ATP card is built around a CS4231 codec and an OPL4 synthesizer
583 Ensoniq SoundScape and compatibles
586 Several companies (including Ensoniq, Reveal and Spea) are selling
589 NOTE! The SoundScape PnP is not supported by OSS/Free. Ensoniq VIVO and
594 OPTi MAD16 and Mozart based cards
596 OPTi 82C924/82C925 (in _non_ PnP mode) and OPTi 82C930 interface
598 cards by Reveal miro and Turtle Beach (Tropez). The purpose of these
608 82C931 is compatible with 82C930 and should work with the MAD16 driver
610 chips are supported by OSS/Linux (both in PnP and non-PnP modes).
618 Crystal CS4232 and CS4236 based cards such as AcerMagic S23, TB Tropez _Plus_ and
621 SB and MPU401 emulations. There is support for OPL3 too.
626 CS4232 working you could try initializing it with DOS (CS4232C.EXE) and
630 Turtle Beach Maui and Tropez "classic"
631 This driver version supports sample, patch and program loading commands
635 NOTE! Tropez Plus is different card than Tropez "classic" and will not
640 Jumpers and software configuration
644 configure the driver use I/O, IRQ and DMA settings
646 configurable (SB 1.x/2.x, SB Pro and clones).
657 the driver to use I/O, IRQ and DMA settings which are known to work.
658 You could usually use the same values than with DOS and/or Windows.
680 are the OPTi MAD16, Mozart, SoundScape (Ensoniq) and the PSS architectures
682 cards and the ones which could be supported later.
684 The last resort is to send _exact_ name and model information of the card
690 such as SB, MSS and/or MPU401. In this case there is a chance to get the
692 and boot Linux without hard resetting the machine). In this method the
693 DOS based driver initializes the hardware to use known I/O, IRQ and DMA
725 After configuring the kernel and sound driver and compile the kernel
736 some drivers (like MPU401) may conflict with your SCSI controller and
743 questions. The default answer is shown so that (y/n) means 'y' by default and
774 Answering 'y' is usually a safe and recommended choice. However some
797 and MV Jazz16 cards is included in the SB driver. Use it instead
799 Soundscape, PSS and Maui drivers include their own MPU401
824 have their own MSS support and enabling this option will cause a
827 "nonstandard" feature and works only with very few cards (if any).
835 Spea and Reveal (note that Reveal makes other cards also). The oldest
841 "Support for MAD16 and/or Mozart based cards",
848 Reveal (some models) and Diamond (some recent models).
849 Note OPTi 82C924 and 82C925 are MAD16 compatible only in non PnP
853 and TB Tropez (may not work with Tropez Plus).
861 - Answering 'n' disables /dev/midi## devices and access to any
862 MIDI ports using /dev/sequencer and /dev/music. This option
863 also affects any MPU401 and/or General MIDI compatible devices.
867 - Answering 'n' disables /dev/sequencer and /dev/music.
869 Entering the I/O, IRQ and DMA config parameters
874 I/O address, IRQ and DMA numbers are asked. With some cards the program
886 Please refer manual of your card for valid I/O, IRQ and DMA numbers. Using
887 the same settings with DOS/Windows and Linux is recommended. Using
898 It's possible to configure these cards to use different I/O, IRQ and
901 a good idea to use the same values than with DOS/Windows. With SB and SB Pro
902 it's the only choice. SB16 has software selectable IRQ and DMA channels but
903 using different values with DOS and Linux is likely to cause troubles. The
907 The original (steam) Sound Blaster (versions 1.x and 2.x) use always
911 8 bit operation and a 16 bit one (5, 6 or 7) for the 16 bit mode. In theory
917 first configure OSS/Free for one card. Then edit local.h manually and define
918 SB2_BASE, SB2_IRQ, SB2_DMA and SB2_DMA2 for the second one. You can't get
919 the OPL3, MIDI and EMU8000 devices of the second card to work. If you are
921 and have different PnP IDs. There is no way to get two cards with the same
922 card ID and serial number to work. The easiest way to check this is trying
937 I know just Thunderboard and SM Games. Other cards require some kind of
948 - If you use the same I/O, IRQ and DMA settings in Linux, the
951 If your card is both SB and MSS compatible, I recommend using the MSS mode.
952 Most cards of this kind are not able to work in the SB and the MSS mode
953 simultaneously. Using the MSS mode provides 16 bit recording and playback.
955 ProAudioSpectrum 16 and compatibles
965 for the other card and to disable the SB emulation of PAS16 (there is a
968 With PAS16 you can use two audio device files at the same time. /dev/dsp (and
969 /dev/audio) is connected to the 8/16 bit native codec and the /dev/dsp1 (and
977 the driver uses a software emulation for synth and pcm playbacks. It's
980 to select the channel as a recording source and to use volume above 10%.
984 GUS MAX and the 16 bit sampling daughtercard have a CS4231 codec chip which
987 Configuring GUS is simple. Just enable the GUS support and GUS MAX or
992 uses /dev/dsp (and /dev/audio). Command "ln -sf /dev/dsp1 /dev/dsp"
996 for the I/O, IRQ and DMA numbers for the card. Use the same values than
1000 IRQ and DMA numbers for the daughter card. You have to use different I/O
1001 and DMA values than for the standard GUS. The daughter card permits
1002 simultaneous recording and playback. Use /dev/dsp (the daughtercard) for
1003 recording and /dev/dsp1 (GUS GF1) for playback.
1005 GUS MAX uses the same I/O address and IRQ settings than the original GUS
1008 (dev/dsp0 and /dev/dsp1). The second DMA channel is required for
1030 MPU401 and Windows Sound System
1045 MPU2_BASE & MPU2_IRQ (and MPU3_BASE & MPU3_IRQ) to the file.
1057 Even the PSS cards are compatible with SB, MSS and MPU401, you must not
1059 program handles these options itself. (You may use the SB, MPU and MSS options
1062 The PSS driver enables MSS and MPU401 modes of the card. SB is not enabled
1065 algorithm file (.ld) is read by the config program and written to a
1073 It's possible to load your own DSP algorithms and run them with the card.
1079 You have to enable the OPL3 and SB (not SB Pro or SB16) drivers in addition
1082 Configuring ATP is little bit tricky since it uses so many I/O, IRQ and
1088 both the SB driver and the SB mode of ATP to use the same IRQ, DMA and I/O
1109 The SoundScape driver handles initialization of MSS and MPU supports
1111 (enable also the /dev/dsp, /dev/sequencer and MIDI supports).
1116 !!!!! device files (/dev/dsp0 and /dev/dsp1). The first one WAS !!!!
1117 !!!!! used only for card initialization and the second for audio !!!!
1121 !!!!! This is not required with OSS versions 3.5-beta6 and later !!!!
1129 The configuration program asks one DMA channel and two interrupts. One IRQ
1130 and one DMA is used by the MSS codec. The second IRQ is required for the
1139 defines in the ssinit.c and then compile the program. You may run ssinit
1147 and install the DOS/Windows driver from ftp://ftp.ensoniq.com/pub.
1150 is the right one for most cards and sndscape.co1 is for few (older) cards
1151 made by Reveal and/or Spea. The driver has capability to detect the card
1153 and locate the sound driver initialization message for the SoundScape
1155 an old card and you will need to use sndscape.co1. For other cards use
1156 soundscape.co0. New Soundscape revisions such as Elite and PnP use
1170 are terrible), just modify ssinit.c to use another microcode file and try
1174 MAD16 (Pro) and Mozart
1179 /dev/audio, /dev/sequencer and MIDI supports.
1181 Mozart and OPTi 82C928 (the original MAD16) chips don't support
1183 MPU/MIDI I/O base. The MAD16 Pro (OPTi 82C929) and 82C930 chips have MPU401
1190 Tropez is jumper configurable and not connected to the MAD16 chip (the
1204 DMA channel pairs are: 0&1, 1&0 and 3&0.
1214 fairly well. You have to enable SB, SB Pro (_not_ SB16) and MPU401 supports
1217 'y' here and the driver asks the second (16 bit) DMA channel.
1237 MIDI0001.BIN and it's located in the DOS/Windows driver directory. The file
1254 ones are fully SB or SB Pro compatible and there should be no problems
1257 The older 16 bit cards (SG Pro16, SG NX Pro16, Nova and Lyra) have
1261 for all of the settings. Configure driver for MSS, MPU, SB/SB Pro and OPL3
1267 ESS ES1688 and ES688 'AudioDrive' based cards
1279 There are some ES1688/688 based sound cards and (particularly) motherboards
1284 recommended by ESS (5, 7, 9/2 and 10). In this case all IRQs don't work.
1295 are compatible with SoundScape and some use the MAD16 chip. You may have
1296 to look at the card and try to identify its origin.
1314 Sorry, can't help. Some cards may work and some don't.
1321 that there is something wrong with the mouse port and sound at least on
1324 and kernel failures when sound is used.
1329 The miroSOUND PCM1-pro, PCM12 and PCM20 radio has been used
1330 successfully. These cards are based on the MAD16, OPL4, and CS4231A chips
1331 and everything said in the section about MAD16 cards applies here,
1332 too. The only major difference between the PCMxx and other MAD16 cards
1339 /dev/mixer and the CS4231 mixer by /dev/mixer1 (depends on load
1343 The miroSOUND PCM12 and PCM20 radio is capable of full duplex
1344 operation (simultaneous PCM replay and recording), which allows you to
1345 implement nice real-time signal processing audio effect software and
1355 (limited by the OSS-design). Development has started and maybe
1357 read RadioText, the Programme Service name, Programme TYpe and
1359 strength value. See aci.[ch] and miropcm20*.[ch] for more details.
1374 You need to configure the driver with MSS and OPL3 supports enabled.
1375 In addition you need to manually edit linux/drivers/sound/local.h and
1397 loadlin.exe to boot Linux. If Linux is configured to use the same I/O, IRQ and
1405 don't work in the SB and MSS modes at the same time.
1407 Then there are cards which are no longer manufactured and/or which
1410 Adding support for a new card requires much work and increases time
1412 to all low level drivers and be tested too, maybe with multiple
1421 manufacturer of the card and ask if they have (or are willing to)
1428 maintaining and supporting a driver without any specs will be a pain.
1439 Sierra Aria and IBM Mwave. It's possible that these architectures
1444 Information about unsupported sound cards and chipsets is welcome as well
1445 as free copies of sound cards, SDKs and operating systems.
1447 If you have any corrections and/or comments, please contact me.