Jabber.org would benefit from an open IM standard. Unfortunately, Jabber.com would lose its only competitive advantage and would quickly go out of business.
It's important to distinguish between consumer IM and enterprise IM. The open source Jabber servers would be adopted by techies and small shops (like linux in the early days), while Jabber.com would have a fair chance at selling to the high end enterprise market where perceived scale, reliability and 24/7 support are a must.
Remember, AOL and Microsoft don't even have an offering in the enterprise world yet.
It's quite possible to set up linux with multiple sound cards. They manifest themselves as additional/dev/[mixer,audio,dsp] devices.
The application I set up was using multiple Real encoders taking input from two soundcards and outputting it to 6 Real streams (2 sources @ 3 bandwidths each)
Some software is hardcoded to use/dev/mixer when setting up the line/mic levels, if not/dev/audio, too.
The solution? A sickening hack...but it worked:) You fire up one version of the player, and once it's happy, you change the device (via symlinks) that/dev/[mixer,audio,dsp] point to.
For example: ln -s/dev/dsp0/dev/dsp ln -s/dev/audio0/dev/audio ln -s/dev/mixer0/dev/mixer mp3play mp3file_for_soundcard1.mp3
Yeah, yeah..I know it's horrible, but if you haven't got the source for the application, and it doesn't allow you to specify different devices on the command line, this should work.
And as ppl have correctly pointed out, make sure you don't have any resource conflicts: cat/proc/interrupts cat/proc/ioports
Check that all soundcards have been detected using: cat/dev/sndstat
You should see entries for each of the soundcards.
Slashdot Mirror
Not so fast with the Jabber angle...
Jabber.org would benefit from an open IM standard. Unfortunately, Jabber.com would lose its only competitive advantage and would quickly go out of business.
It's important to distinguish between consumer IM and enterprise IM. The open source Jabber servers would be adopted by techies and small shops (like linux in the early days), while Jabber.com would have a fair chance at selling to the high end enterprise market where perceived scale, reliability and 24/7 support are a must.
Remember, AOL and Microsoft don't even have an offering in the enterprise world yet.
It's quite possible to set up linux with multiple sound cards. They manifest themselves as additional /dev/[mixer,audio,dsp] devices.
/dev/mixer when setting up the line/mic levels, if not /dev/audio, too.
:) You fire up one version of the player, and once it's happy, you change the device (via symlinks) that /dev/[mixer,audio,dsp] point to.
/dev/dsp0 /dev/dsp /dev/audio0 /dev/audio /dev/mixer0 /dev/mixer
/dev/dsp1 /dev/dsp /dev/audio1 /dev/audio /dev/mixer1 /dev/mixer
/proc/interrupts /proc/ioports
/dev/sndstat
The application I set up was using multiple Real encoders taking input from two soundcards and outputting it to 6 Real streams (2 sources @ 3 bandwidths each)
Some software is hardcoded to use
The solution? A sickening hack...but it worked
For example:
ln -s
ln -s
ln -s
mp3play mp3file_for_soundcard1.mp3
ln -s
ln -s
ln -s
mp3play mp3file_for_soundcard2.mp3
Yeah, yeah..I know it's horrible, but if you haven't got the source for the application, and it doesn't allow you to specify different devices on the command line, this should work.
And as ppl have correctly pointed out, make sure you don't have any resource conflicts:
cat
cat
Check that all soundcards have been detected using:
cat
You should see entries for each of the soundcards.
Hope this helps.
Coma