Dearest Pd-list,
I'm trying to migrate my system to Linux and I'm running into some problems. RH9, Alsa 1.0.0rc2, M-Audio Quattro.
I configured PD with --enable-alsa and compiled it. But when I do a -listdev I'm presented with "OSS Devices".
Does then mean the Pd is using the OSS emulation in Alsa, is it using alsa at all? What's going on ?!
The quattro does more or less work with alsa in xmms and one of the OSS Devices does send sound out of the quattro in Pd. But is it through alsa, or what?
Cheers, David
Hallo, David NG McCallum hat gesagt: // David NG McCallum wrote:
I'm trying to migrate my system to Linux and I'm running into some problems. RH9, Alsa 1.0.0rc2, M-Audio Quattro.
I configured PD with --enable-alsa and compiled it. But when I do a -listdev I'm presented with "OSS Devices".
listdev does not list alsa devices, but that doesn't mean you cannot use alsa devices.
Does then mean the Pd is using the OSS emulation in Alsa, is it using alsa at all? What's going on ?!
The quattro does more or less work with alsa in xmms and one of the OSS Devices does send sound out of the quattro in Pd. But is it through alsa, or what?
THis can get a bit tricky, but it will be easier, when Miller will reintrocude the option to select alsa devices by name. Here's the rundown:
To use alsa, you should start Pd with the "-alsa" flag. You also can select the card to use by "-audiodev X" where X is the card number starting from 1. These options are also available in the "Media" menu. Miller intends to also add a -alsadev or -alsaadd option again later.
This doesn't really work well with the Quattro. For the Q. you should first install a so called asoundrc file. You can find it on alsa-project.org/doc => Maudio => Quattro, or I could send it to you.
This defines several virtual PCM devices that map to different configurations on the Quattro. The ones to try are called "q4" and "q4b". But you cannot use these directly with Pd currently, unless you patch the s_audio_alsa.c file like I described on pd-dev or wait a moment, until the next Pd version.
Even then, I didn't make it to have both inputs and outputs available with the Quattro in 4-channel mode, yet.
Here I have another strange problem. Whereas I can use Pd with the Quattro in my homebox just fine, Pd on my laptop will crickle and crackle in regular intervals unless I set the buffer to "-blocksize 2048", which is quite a bit of latency.
Does someone have an idea, where this could come from?
ciao
Frank Barknecht _ ______footils.org__
morning Frank, morning list,
On 8 December 2003 at 12:20:47, Frank Barknecht appears to have written: [snip]
Here I have another strange problem. Whereas I can use Pd with the Quattro in my homebox just fine, Pd on my laptop will crickle and crackle in regular intervals unless I set the buffer to "-blocksize 2048", which is quite a bit of latency.
Does someone have an idea, where this could come from?
Possibly other devices nabbing the PCI bus while you're not looking? I found the article by Daniel Robbins at
http://www-106.ibm.com/developerworks/library/l-hw2.html
pretty informative, although I'm unable to alter most of the PCI latencies in my cheap laptop, so I still get clicks when using ALSA directly from Pd, although (oddly enough) not with OSS emulation -- all of this for the onboard sound chip (i810) only...
marmosets, Bryan
Frank,
I've got the .asoundrc as they instructed in the ALSA howto for the Quattro.
So am I supposed to do something like "-audiodev q4" or whichever setup I want to try?
I was confused about the "OSS Devices" because that's also all that shows up in the Media menu option...
<shrug>
David
Frank Barknecht wrote:
Hallo, David NG McCallum hat gesagt: // David NG McCallum wrote:
I'm trying to migrate my system to Linux and I'm running into some problems. RH9, Alsa 1.0.0rc2, M-Audio Quattro.
I configured PD with --enable-alsa and compiled it. But when I do a -listdev I'm presented with "OSS Devices".
listdev does not list alsa devices, but that doesn't mean you cannot use alsa devices.
Does then mean the Pd is using the OSS emulation in Alsa, is it using alsa at all? What's going on ?!
The quattro does more or less work with alsa in xmms and one of the OSS Devices does send sound out of the quattro in Pd. But is it through alsa, or what?
THis can get a bit tricky, but it will be easier, when Miller will reintrocude the option to select alsa devices by name. Here's the rundown:
To use alsa, you should start Pd with the "-alsa" flag. You also can select the card to use by "-audiodev X" where X is the card number starting from 1. These options are also available in the "Media" menu. Miller intends to also add a -alsadev or -alsaadd option again later.
This doesn't really work well with the Quattro. For the Q. you should first install a so called asoundrc file. You can find it on alsa-project.org/doc => Maudio => Quattro, or I could send it to you.
This defines several virtual PCM devices that map to different configurations on the Quattro. The ones to try are called "q4" and "q4b". But you cannot use these directly with Pd currently, unless you patch the s_audio_alsa.c file like I described on pd-dev or wait a moment, until the next Pd version.
Even then, I didn't make it to have both inputs and outputs available with the Quattro in 4-channel mode, yet.
Here I have another strange problem. Whereas I can use Pd with the Quattro in my homebox just fine, Pd on my laptop will crickle and crackle in regular intervals unless I set the buffer to "-blocksize 2048", which is quite a bit of latency.
Does someone have an idea, where this could come from?
ciao
Hallo, David NG McCallum hat gesagt: // David NG McCallum wrote:
I've got the .asoundrc as they instructed in the ALSA howto for the Quattro.
So am I supposed to do something like "-audiodev q4" or whichever setup I want to try?
The -audiodev option only accepts numbers and translates them to hw:X or plughw:X, I'm not sure which one. With older Pd's you could use "-alsadev DEVICE_NAME" to select "q4" or "q4b". This is currently disabled, but promised to come back.
Currently you only can use two channels with -alsa and -oss, as far as I could test.
ciao
Frank Barknecht _ ______footils.org__
Is the -alsa flag only for pre .37 versions of Pd?
Trying -alsa just spits out all the possible flags and doesn't actually run Pd (kind of like doing ./pd -?)
So... I should just wait until the next version?
David
. . David McCallum . Music wants to be free . http://mentalfloss.ca/sintheta .
Frank Barknecht wrote:
Hallo, David NG McCallum hat gesagt: // David NG McCallum wrote:
I've got the .asoundrc as they instructed in the ALSA howto for the Quattro.
So am I supposed to do something like "-audiodev q4" or whichever setup I want to try?
The -audiodev option only accepts numbers and translates them to hw:X or plughw:X, I'm not sure which one. With older Pd's you could use "-alsadev DEVICE_NAME" to select "q4" or "q4b". This is currently disabled, but promised to come back.
Currently you only can use two channels with -alsa and -oss, as far as I could test.
ciao
Hallo, David NG McCallum hat gesagt: // David NG McCallum wrote:
Is the -alsa flag only for pre .37 versions of Pd?
No, -alsa is in for several versions.
Trying -alsa just spits out all the possible flags and doesn't actually run Pd (kind of like doing ./pd -?)
This looks like -alsa is missing from your version of Pd. Does $ ldd /usr/bin/pd include something like: libasound.so.2 => /usr/lib/libasound.so.2 (0x4002d000) ? Do you run the official version from Miller's site or the CVS version? I'm not sure, if ALSA is still enable in Pd-MSP. I run the CVS version almost everytime.
It might also be, that although you did provide --enable-alsa to configure, it didn't get found. Maybe you don't have the header files for libasound installed. They normally come with a package ending in "-dev" or "-devel" and include above all the directory /usr/include/alsa/
ciao
Frank Barknecht _ ______footils.org__
-
Bryan Jurish -
David NG McCallum -
Frank Barknecht