Re: [linux-audio-dev] Some ALSA mixer API questions

Ross Vandegrift wrote: > I'm a bit confused by how to get element types. It seems like amixer > opens the ctl device to get a mixer element's type? All accesses to the mixer go through the ctl device. HTH Clemens

Re: [linux-audio-dev] ALSA performance issues?

Mario Lang wrote: > I just tried to get sound working on a LinkSys NSLU2 (ARM) running > Debian Etch using a USB sound card. > > What I discovered I find pretty strange, and would like to know some > more details. Apparently, all ALSA native clients don't > manage to play sound click-free, they a

Re: [linux-audio-dev] snd_pcm_poll_descriptors_revents() question

Fons Adriaensen wrote: > On Wed, Nov 08, 2006 at 05:58:40PM +0100, Clemens Ladisch wrote: > > > In that case, how can one test if *all* pollfd for a given > > > pcm are ready ? > > > > You cannot. The state of the file descriptors is not necessarily > >

Re: [linux-audio-dev] snd_pcm_poll_descriptors_revents() question

Fons Adriaensen wrote: > On Wed, Nov 08, 2006 at 02:24:30PM +0100, Fons Adriaensen wrote: > > Is snd_pcm_poll_descriptors_revents() more than an > > accessor ? If it is, the name is a quite misleading. > > To answer my own question, it seems that it *is* more > than an accessor. > > The docs le

Re: [linux-audio-dev] OSS will be back (was Re: alsa, oss , efficiency?)

Fons Adriaensen wrote: > On Wed, Nov 08, 2006 at 12:20:42AM +, James Courtier-Dutton wrote: > > The current jackd skips a step in the processing of the poll events. > > Basically what happens comes down to (ignoring error > checking and timeouts): > > - The set of pollfd is poll()'ed until al

Re: [linux-audio-dev] alsa, oss , efficiency?

lemmel wrote: > The sound was always troncated (even with finished software such as xmms, > amarok), Were there samples missing at the beginning or at the end? > and even randomly truncated, What do you mean with "randomly"? What sound card/kernel version/ALSA version are you using? Regards,

Re: [linux-audio-dev] about MIDI timing...

Chris Cannam wrote: > Clemens: > > Most sound cards don't have an internal timer that could be used for > > MIDI timing. ALSA uses whatever timer is configured, the default for > > this is the RTC timer. > > It is? For ALSA sequencer queues? I thought the > default was system timer. Since 1.0

Re: [linux-audio-dev] about MIDI timing...

Mulyadi Santosa wrote: > I also read that not all Linux kernel sound card driver enable the > internal card timer, thus the software must rely on system timer. Most sound cards don't have an internal timer that could be used for MIDI timing. ALSA uses whatever timer is configured, the default for

Re: [linux-audio-dev] Help needed: mpg123 lives!

Nicholas J Humfrey wrote: > I have been trying to add ALSA 0.9/1.0 API support - but have been > having a few problems - is anyone able to help out? Yes. Regards, Clemens

Re: [linux-audio-dev] Basic MIDI question

Ari Kauppi wrote: > On Wed, 26 Jul 2006, Jens M Andreasen wrote: > > > if(runningStatus == NOTE_ON || runningStatus == NOTE_OFF) > > If you plan to receive messages from other channels than 0 you have to > use (runningStatus & 0xF0) instead of the full runningStatus and perhaps > check for

Re: [linux-audio-dev] Basic MIDI question

Lee Revell wrote: > On Tue, 2006-07-25 at 11:03 +0200, Clemens Ladisch wrote: > > (ALSA's > > sequencer event -> rawmidi converter uses running status by default.) > > "By default" - so it can it be disabled? How? snd_midi_event_no_status(), but this cann

Re: [linux-audio-dev] Basic MIDI question

Lee Revell wrote: > I was confused because I also see these timestamps when snooping > the MIDI output stream inside the kernel's MPU401 driver. I guess I > assumed that aplaymidi would deliver the events with correct timing, > rather than passing the timestamps through. The MIDI data at a raw MI

Re: [linux-audio-dev] MIDI... know how to do bank/patch changes on yamaha Motif Rack?

Stephen Cameron wrote: > The manual fails to mention what the Bank Change message is > (probably because it is "standard MIDI stuff.") It is 0xB0 > (or 0xBn, where n is the channel the device receives basic > messages on.) Bx is the Control Change command. The two halves of the bank number are

Re: [linux-audio-dev] How to use the alsa sequencer?

Stephen Cameron wrote: > What I'm supposed to use for the "name" parameter for snd_seq_open > is not exactly clear. "default" > I've been using "hw:0,0" and it returns zero, "default" happens to be an alias for "hw" at the moment, and the ALSA library doesn't bother to check for superfluous para

Re: [linux-audio-dev] precise event timer examples (HPET?)

Alex wrote: > Does anyone have any examples that use HPET (or any other high > resolution event) timers? I've built HPET support into my kernel but > I cannot figure out how to compile the example given in the > documentation : > /usr/src/linux-2.6.12/Documentation/hpet.txt /dev/hpet didn't quite

Re: [linux-audio-dev] ALSA Picture

Richard Spindler wrote: > 2006/3/24, Clemens Ladisch <[EMAIL PROTECTED]>: > > The SUSPENDED and XRUN states can happen asynchronously, i.e., the > > device can go into them at any time (from some other states), and the > > next call to snd_pcm_writei() only reports

Re: [linux-audio-dev] select() ?? before snd_pcm_writei(handle, buffer, frames);

kurmisk wrote: > I have write my small _alsa_test_program_. > [C code ckunkz see below] > It works good but now i wanna before call > rc = snd_pcm_writei(handle, buffer, frames); > somehow check - is sound device free for this call or not. You could call snd_pcm_avail_update(). If you don't wan

Re: [linux-audio-dev] Alsa Problem

Lee Revell wrote: > On Fri, 2006-03-24 at 14:09 +0100, Richard Spindler wrote: > > I'm using snd_pcm_writei to playback some audio, however, after a > > little time the call fails with the error: "File descriptor in bad > > state", which I believe I cannot recover from. > > > > Why does this happe

Re: [linux-audio-dev] ALSA Picture

Richard Spindler wrote: > on my quest to understand the ALSA API, I created a little Image to > get an overview about the various states and how they relate to each > other. > > http://propirate.net/oracle/bilder/ALSA.png Cool, the first complete page of The ALSA Programming Manual! Now we only

Re: [linux-audio-dev] What is currently the best USB audio interface for Linux?

ico wrote: > I am in the process of considering a portable USB audio interface. Having > checked the alsa matrix, I am a bit at a loss what may be the best option. Have a look at , too. > 2) Preferrably USB 2.0 capable The only supported USB 2

Re: [linux-audio-dev] Writing PCM to left and right channel sperately?

Tobias Scharnberg wrote: > I need to use the left and the right audio channel seperately. If you're using the ALSA library, you can use the following definitions in /etc/asound.conf or ~/.asoundrc to get two independent virtual devices: pcm.left { type plug slave.pcm {

Re: [linux-audio-dev] Reliability of SPDIF sync w/ onboard audio?

[EMAIL PROTECTED] wrote: > Ok, given a pair of commodity Linux PC's with cheapo onboard audio > codecs capable of SPDIF input and output, assuming I sent identical > input signals into both machines and didn't perform any processing in > the middle, could I reasonably expect the output signals to b

Re: [linux-audio-dev] Fwd: OT -- USB History

Christoph Eckert wrote: > Some of us (including me) would like to see a USB 2.0 breakout box which > grants more than 2x2 channels while using a standard USB 2.0 protocol. There is the SB Audigy 2 NX with 8+2 channels. (You didn't mention any quality constraints. ;-) Clemens

Re: [linux-audio-dev] Hello & Help

Vaughan Famularo wrote: > The Ux16 shows up in the qjackctrl midi connections gui. BUT nothing > appears to be triggered by my exterior keyboard. Do you get anything with "amidi --dump -p ..."? (see "amidi -l" for a list of port names) Regards, Clemens

Re: [linux-audio-dev] configuring ALSA support in linux 2.6.11

chandrasheakhar singh wrote: > I think we are right, but as far as ALSA is concerned if i'm correct, it > does talk about lowest audio > driver, it emulates oss to access lowest audio driver, if this is the case > then ALSA should work with existing audio driver. ALSA can emulate the OSS API for

Re: [linux-audio-dev] configuring ALSA support in linux 2.6.11

chandrasheakhar singh wrote: > Do you suggest me anything to test or verify in driver as default > config file for this target (omap_h4_2420_defconfig) does not have > ALSA configuration macro to configure. > > >>CONFIG_SOUND_OMAP=y > >>CONFIG_SOUND_TSC2101 =y It looks as if these are OSS driver

Re: [linux-audio-dev] configuring ALSA support in linux 2.6.11

chandrasheakhar singh wrote: > I wanted to configure ALSA for omap 2420 (h4) in linux 2.6.11. > > CONFIG_SOUND=y > CONFIG_SND=y > CONFIG_SND_PCM=y > CONFIG_SND_OSSEMUL=y > CONFIG_SND_MIXER_OSS=y > CONFIG_SND_PCM_OSS=y > CONFIG_SOUND_OMAP=y > CONFIG_SOUND_TSC2101 =y > > After booting the kernel i ca

Re: [linux-audio-dev] ALSA MIDI Sync

Peter Brinkmann wrote: > I'm trying to figure out how to build an ALSA MIDI sequencer that'll > sync with other sequencers. I've looked around but didn't see any > recent information. > So, my question is, what's the recommended way of synchronizing two > MIDI sequencers these days, using ALSA? Is

Re: [linux-audio-dev] ALSA configuration help and building help

chandrasheakhar singh wrote: > After executing the kernel on OMAP 2420 I got the following devices for > ALSA in /dev/snd [controlC0 midiC0D0 midiC0D1 midiC0D2 midiC0D3 seq > timer] but the snd > device which can play the PCM data is not coming up. Looks like a bug in the driver (you didn't t

Re: [linux-audio-dev] [linux-audio-user] External audio interface (edirol FA/UA-101)

Paul Davis wrote: > 8 channels across USB? forget it. USB can stretch to about 4 channels > before things start to fall apart. An Audigy 2 NX manages eight channels just fine, even in USB 1.1 mode (but then with no more than 16 bits at 48 kHz, and without capturing). > YMMV, but this is what i've

Re: [linux-audio-dev] USB-MIDI Transfer rate

Jens M Andreasen wrote: > I am running into troubles here. After reboot, the usb-midi goes > haywire!? And I have not even done any changes to the system yet ... > > At first, I reboot with the usb device off and then have a peek: > > $ ls /dev/midi* > /dev/midi1 > > $ amidi -l > DeviceName > h

Re: [linux-audio-dev] USB-MIDI Transfer rate

Jens M Andreasen wrote: > On Fri, 2005-09-16 at 17:10 +0200, Clemens Ladisch wrote: > > Jens M Andreasen wrote: > > > Are you absolutely sure that it is not possible to increase the thruput? > > > > Try changing the line: > > > > ep->max_trans

Re: [linux-audio-dev] USB-MIDI Transfer rate

Jens M Andreasen wrote: > On Fri, 2005-09-16 at 09:52 +0200, Clemens Ladisch wrote: > > > The MIDI-USB device also have a control channel without any endpoints > > > (without any physical midi-jacks.) Again only as far as I have > > > understood; the control channel

Re: [linux-audio-dev] USB-MIDI Transfer rate

Jens M Andreasen wrote: > I am currently working on digesting the USB-MIDI Class Definition ... > > http://www.usb.org/developers/devclass_docs/midi10.pdf > > As I understand, you can have up to 16 USB MidiStreams (MS), each equal > to a physical midi-cable (and each "cable" having 16 virtual > mi

Re: [linux-audio-dev] USB: Is a CLASS_INTERFACE request a kind of control transfer ?

Jan Holst Jensen wrote: > I am (still) trying to implement a control panel > feature for the U2A USB sound card. > > Now, half of the URBs sent to the device are > CONTROL_TRANSFER blocks, but the other half are marked > as CLASS_INTERFACE in the SnoopyPro logs. See a > typical example below. Snoo

Re: [linux-audio-dev] Alsa Sequencer Raw MIDI Data

Dirk Jagdmann wrote: > I'm currently developing an application which should be controlled via > MIDI. I'd like to use the Alsa Sequencer API, so I can use aconnect and > friends to connect my app to other apps and MIDI hardware. However I > like to get access and send the raw MIDI stream. The whol

Re: [linux-audio-dev] Marian soundcards

Marije Baalman wrote: > Unfortunately, the most interesting card they have (the UCON CX) is not > amongst those for which they supply info... It's an USB device. With luck, it's already supported by snd-usb-audio. Regards, Clemens

Re: [linux-audio-dev] Libs for reading/writing midis

Jens M Andreasen wrote: > On Tue, 2005-08-09 at 15:31 +0200, Clemens Ladisch wrote: > > [...] when going from the graveyard to the tomb, the > > music is blended to another track that plays the same melody with > > different instruments for a more "closed" feeling.

Re: [linux-audio-dev] Libs for reading/writing midis

Jens M Andreasen wrote: > What is type 2 ? Type 2 files contain several related tracks, like type 1, but instead of being played in parallel, these tracks are to be used in some unspecified way. For example, the background music in Monkey Island 2 uses one type 2 file for each room where the othe

Re: [linux-audio-dev] ALSA MIDI latency correction

Peter Brinkmann wrote: > I have a sequencer application that has several MIDI output ports, > each connected to some device that accepts MIDI input. Those > devices may have vastly different latencies ... but of course I > don't want to hear a time lag between those devices. > > I'm currently sched

Re: [linux-audio-dev] HOw to create an ALSA out port

Jens M Andreasen wrote: > int err = snd_rawmidi_open(/*in*/NULL,/*out*/&handle_out, >device,0); > > The code above will wait forever if the device is already taken. > Opening the device with SND_RAWMIDI_NONBLOCK as last argument will get > you past that point, but then

Re: [linux-audio-dev] HOw to create an ALSA out port

Christoph Eckert wrote: > I only need to write sysex data which are kept in a character > array. Is there a possibility to easily > > * connect to a certain port of a device (the Midisport control > port) > * send the contents of the array to this port > * close the port This is pretty much exactl

Re: [linux-audio-dev] best soundcard revisited

Aaron wrote: > I plan to have all the computers dual booting lin/win and want the > best quality sound card I can get that will run on both lin and win > with the least trouble and the most bang for the buck. > > I don't need multitrack recording necessicarily. And what _do_ you need? Neither "bes

[linux-audio-dev] Re: What Parts of Linux Audio Simply Work Great?

Christoph Eckert wrote: > well, I have written a small login script which catches the > ALSA ID of my USB card and starts JACK on top of it each time > I login. This is because I use three USB devices and I didn't > manage to index them correctly to make them appear in the > same order each day. I

Re: [linux-audio-dev] Compiling ALSA. Was: Sending USB msgs to sound card...

Jan Holst Jensen wrote: > Hmmm... I have checked out alsa via anonymous CVS from > sourceforge. Can't get it to compile - it misses a > ./configure script when running "./build config". Run the cvscompile script, or see the INSTALL file. The patch should work with the 1.0.9b release, too. HTH C

Re: [linux-audio-dev] Two / Three HDSPM Cards?

Audio Developer wrote: > bindings.112.slave b; > bindings.112.channel 56; This is the 113th channel. > pcm.hdspm_112 { > type multi; > slaves.a.pcm hdspm_0; > slaves.a.channels 56; > slaves.b.pcm hdspm_1; > slaves.b.channels 56; > bindings.0.slave

Re: [linux-audio-dev] Sending USB msgs to sound card through snd_usb_audio driver - how ?

Jan Holst Jensen wrote: > --- Clemens Ladisch <[EMAIL PROTECTED]> wrote: > > > Are there any standard ioctl() calls in the > > > > No, but this would be a very good idea for testing > > purposes. I'll add a hwdep device for this. > > Great. Looking

Re: [linux-audio-dev] Sending USB msgs to sound card through snd_usb_audio driver - how ?

Jan Holst Jensen wrote: > I am trying to control the settings of my EgoSys U2A > sound card by sending it the same commands that I can > see being sent to it when I am using the Windows U2A > control panel. What kind of messages are these? > Are there any standard ioctl() calls in the > snd_usb_a

Re: [linux-audio-dev] [ot] [rant] gcc, you let me down one time too many

Tim Goetze wrote: > [Clemens Ladisch] > > > You mean you want to omit \n and the quotes? That was always invalid > > in both C and C++. > > Makes me wonder how come it used to compile cleanly then. Now please > don't tell me "it's a gcc extension so i

Re: [linux-audio-dev] [ot] [rant] gcc, you let me down one time too many

Tim Goetze wrote: > [Clemens Ladisch] > > Tim Goetze wrote: > >> Enter gcc version 3, which drops multi-line inline assembly support. > > > > The following compiles fine with gcc 3.3.3: > > > >__asm__ ("nop\n" > >

Re: [linux-audio-dev] [ot] [rant] gcc, you let me down one time too many

Tim Goetze wrote: > Enter gcc version 3, which drops multi-line inline assembly support. The following compiles fine with gcc 3.3.3: void f() { __asm__ ("nop\n" "nop\n"); } > Enter gcc version 3, moving the vtable member to memory offset 0 of a > derived type even if the

Re: [linux-audio-dev] ALSA Sequencer API - How to Receive Events?

Sean Don wrote: > 1) I don't have a hardware sequencer; so, I use > timidity as an ALSA sequencer, then pmidi a player... > > timidity -iA -B8,8 -Os & > pmidi -p 128:0 > > 2) That plays fine, but how to tap into the events > pmidi is sending to 128:0? The events are sent to Timidity (128:0), not

Re: [linux-audio-dev] Best-performing Linux-friendly MIDI interfaces?

Jay Vaughan wrote: > i'd like to ask members of LAD to report on their experiences with > using professional MIDI interfaces, such as (for example) the Motu > MTP AV, Digidesign MIDEX-8, etc? > > what is the 'easiest' MIDI interface to get working under the average > Linux kernel? The 8x8 interfac

Re: [linux-audio-dev] deblocking snd_seq_event_input()

Jens M Andreasen wrote: > On Sun, 2005-05-08 at 12:50 +0200, Fons Adriaensen wrote: > > But this is besides the point. In my original problem it is not the > > intention > > to terminate the thread - just to force the snd_seq_event_input() to return. > > The thread could well close the handle, ope

Re: [linux-audio-dev] deblocking snd_seq_event_input()

Fons Adriaensen wrote: > Shouldn't a call that waits on fd return with an error code when > that fd is closed ? The ALSA library isn't thread safe. > Since snd_seq_event_input() probably uses poll() internally, why > doesn't it test for POLLERR,-HUP,-NVAL ? It just calls read(). Regards, Cleme

Re: [linux-audio-dev] deblocking snd_seq_event_input()

Fons Adriaensen wrote: > Is there a simple (i.e. simpler than getting the pollfd and using them) > to force snd_seq_event_input() in blocking mode to return, so the the > calling thread can close the handle and cleanup ? You could try to send this thread a signal, but I don't know how well signals

Re: [linux-audio-dev] jitter on USB audio

Alfons Adriaensen wrote: > At 48 kHz, USB delivers and consumes audio samples in chunks of 48 frames. Depends. This is true for playback (for most devices), but recording is done with whatever chunk sizes the device delivers. This may be close to 48 samples per USB frame if the device synchroniz

Re: [linux-audio-dev] Extreme (midi) omni-mode

Jens M Andreasen wrote: > Say you had an external single channel midi module, and it wakes up in > omni-mode (all channels are equal), you will ofcourse expect it to make > a sound, no matter the settings on your sending keyboard. > > Now, suppose the module is multi-timbral? > What is the expected

Re: [linux-audio-dev] XITEL INPORT

Charles A. Crayne wrote: > I have recently acquired a XITEL INPORT device, to capture music from my > stereo system, and although [as shown below] it seems to be supported by > the FC3 kernel, I have not yet managed to find any way to access the USB > data stream. > > arecord -l > card 1: Audio [US

Re: [linux-audio-dev] Re: EMI26

Andrew Burgess wrote: > Mine comes up as 102, I've had to edit the driver source in the > past to get it to work. Could you make sure 102 will work too? The firmware for IDs 0100 and 0102 is indeed the same. Editing drivers/usb/misc/emi26.c in the kernel source and replacing 0x0100 with 0x0102, a

Re: [linux-audio-dev] Developing and audio driver

fred doh wrote: > The OSS doc seems to be directed to the user of the API and not > for the driver developer. These docs describe the interface between applications and the driver, so you can read them "from the other side". But I'd really recommend to write an ALSA driver instead. Regards, Cl

Re: [linux-audio-dev] EMI26 (was: Welcome to the "linux-audio-dev" mailing list)

krsrtn wrote: > after that I looked at what you said, /proc/bus/usb/devices:: > ... > D: Ver= 1.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS=64 #Cfgs= 1 > P: Vendor=086a ProdID=0102 Rev= 0.01 > C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA > I: If#= 0 Alt= 0 #EPs= 0 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)

Re: [linux-audio-dev] EMI26 (was: Welcome to the "linux-audio-dev" mailing list)

krsrtn wrote: > 0 [ICH5 ]: ICH4 - Intel ICH5 > Intel ICH5 with ALC202 at 0xcc00, irq 177 > 1 [VirMIDI]: VirMIDI - VirMIDI > Virtual MIDI Card 1 > 2 [Modem ]: ICH-MODEM - Intel ICH5 Modem > Intel ICH5 Modem

Re: emi26 [was: Re: [linux-audio-dev] Re: Welcome to the "linux-audio-dev" mailing list9

(please don't top-post) krsrtn wrote: > ok, but still the frimware is not claimed by the device: > > [EMAIL PROTECTED] ~]$ lsmod | grep emi26 > emi26 168704 0 This driver just loads the firmware. After that, the device is a standard USB audio device, and the snd-usb-audio driver

Re: [linux-audio-dev] Linux DSP Hardware?

Shane wrote: > There has been some fuss in the past about linux drivers for some of the > Creamware products. It's been mentioned that drivers for linux are back > under development but creamware has swayed on this issue before. I > couldn't say exactly what is going on in this area, In March 20

Re: [linux-audio-dev] Linux DSP Hardware?

jipi wrote: > currently, all signal processing algos are being done in software for > Linux Audio. > are there any hardware accelerated support for audio hardware when doing > these sort of algos? If you bend the definition of "hardware accelerated" enough, SIMD extensions like MMX/SSE... would qu

Re: [linux-audio-dev] M-Audio Transit USB with ALSA?

Albert Graef wrote: > has anyone tried the M-Audio Transit USB with ALSA yet? It should work, but you need the firmware loader from . > I'm looking for a not-too-expensive USB audio interface for my laptop, http://www.qbik.ch/usb/devices/ HTH Clemens

Re: [linux-audio-dev] [Alsa-devel] [PATCH]: better X-Station/Speedio/ReMOTE25 support

rnel/usb/usbmidi.c 26 Jan 2005 15:56:47 - @@ -1,7 +1,7 @@ /* * usbmidi.c - ALSA USB MIDI driver * - * Copyright (c) 2002-2004 Clemens Ladisch + * Copyright (c) 2002-2005 Clemens Ladisch * All rights reserved. * * Based on the OSS usb-midi driver by NAGANO Daisuke, @@ -77,11 +77,18 @@ typ

Re: [linux-audio-dev] Trying to record midi with OSS

[EMAIL PROTECTED] wrote: > However, I'm unable to get rosegarden21 to record any > midi notes. This may be the same as this bug: HTH Clemens

Re: [linux-audio-dev] muse and /dev/rtc

Alfons Adriaensen wrote: > the ALSA sequencer API seems to allow *timestamped* events - you put such > an event in a queue and it will appear at the other end at the right moment. > If this is true, It is. > and if ALSA has an high precision timer available to implement it, Standard 2.4 kernels

Re: [linux-audio-dev] cli midi

Hans Fugal wrote: > Is there an app that will dump midi events in human-readable format to > stdout (or a file, or gui window, whatever)? "arecordmidi --dump"; or the tool I posted last week: ("amidi --dump" is human-readable, too,

Re: [linux-audio-dev] Novation ReMOTE, Speedio & XStation

Nick Dowell wrote: > The MIDI communication is not class compliant. It is a very simple > protocol though, and should be easy to implement. If anyone wants > information to write one we'd be more than happy to give it. I'm definitely interested in implementing this protocol. Best regards, Clemen

Re: [linux-audio-dev] USB sound card for Mac and PC

Frank Barknecht wrote: > And thanks to Clement, who? ;-) > Clemens Ladisch hat gesagt: // Clemens Ladisch wrote: > > > There is the M-Audio Audiophile USB but it does not work on Gentoo (and > > > of course, I use Gentoo!!). > > > > It should work with recent

Re: [linux-audio-dev] USB sound card for Mac and PC

Pamplemousse Mk2 wrote: > > Whatever you buy, look for (how to say?), look for an indication that it > > will work in MacOS(X) without any additional install of drivers ... > > Which translates into that the device is "standards-compliant" and > > *should* work out of the box with your Linux box (o

Re: [linux-audio-dev] USB sound card for Mac and PC

Pamplemousse Mk2 wrote: > Is there any USB sound card compatible with both Mac and PC under Linux? The sound drivers run on all architectures. You can use any supported device. > My sound card would be used essentially for full duplex recording, and > sampling in live with software that I code o

Re: [linux-audio-dev] M-Audio Sonica/Ozone/MobilePre/Transit firmware loader now works

Stephen Hassard wrote: > I just tried madfu with my Sonica, and I get a segfault. > > madfuload -f ma005101.bin --waitbyte3 -D /proc/bus/usb/002/003 > Segmentation fault Please show the output when you add the -v parameter. Clemens

[linux-audio-dev] M-Audio Sonica/Ozone/MobilePre/Transit firmware loader now works

Hi, it has been reported that the 2.6.8 kernel has fixed the handling of USB resets, so now it's possible to use a Linux firmware loader to get these devices to work. You can get the loader at . Best regards, Clemens

Re: [linux-audio-dev] a question re: the MIDI spec

Martijn Sipkema wrote: > > > It's not unusable, but IIRC it can get to several ms of jitter. > > > > Why is that? The USB iso clock is every ms IIRC, so naively you > > would expect the maximum jitter to be just under 1ms (if the bus was > > saturated by audio transfers), and less in proportion to

Re: [linux-audio-dev] a question re: the MIDI spec

Jens M Andreasen wrote: > [...] the USB specification. And it even appears like some vendors > are (finally!) starting to follow suit: > >http://midiman.com/products/en_us/KeystationPro88-main.html > >- "USB class compliant—no drivers required for > Windows XP or Mac OS X" M-Audio sta

Re: [linux-audio-dev] a question re: the MIDI spec

Dave Phillips wrote: > I'm doing some research for an article about Linux MIDI support. In my > text I briefly describe the evolution of the MIDI specification since > its adoption, mentioning things like MIDI Time Code, MMC, the sample > dump standard, and the standard MIDI file. However, one it

Re: [linux-audio-dev] Firewire Breakout-Boxes

Daniel Wagner wrote: > > You really should get in contact with the ALSA guys. > > I have already posted a message there couple of weeks ago. Messages from non-subscribers are routed to /dev/null because there isn't a moderator. Clemens

Re: [linux-audio-dev] Re: [linux-audio-user] Setting up linux computer

Paul Winkler wrote: > On Tue, Aug 24, 2004 at 04:23:10PM +0200, Clemens Ladisch wrote: > > The snd-usb-audio driver currently supports multiport USB > > interfaces from ESI/Edirol/Roland/M-Audio/Yamaha. > > Note that others have reported issues with the M-audio usb devices

[linux-audio-dev] Re: [linux-audio-user] Setting up linux computer

ChristianH wrote: > - and I assume MIDI interface as well (6 to 8 ports in+out) > > For Windows I was considering an Emagic AMT8 or Unitor8 interface, There is no Linux driver for these. The snd-usb-audio driver currently supports multiport USB interfaces from ESI/Edirol/ Roland/M-Audio/Yamaha.

Re: [linux-audio-dev] swh plugins and fixing undenormalize

Steve Harris wrote: > You can do > > y += delta > y -= delta > > but youre at the mercy of the optimiser. The IEEE standard specifies exactly what happens with denormals, so, in theory, the compiler must not optimize this away. However, optimization options for speed often disable strict IEEE com

Re: [Alsa-devel] [linux-audio-dev] DSP2000 C-PORT and MIDI input

Lukas Degener wrote: > Hi everybody and sorry for posting this to both, lad and alsa-dev, > i was not sure which one fits better. alsa-devel would be appropriate, but non-subscribers cannot post there, so I'm keeping linux-audio-dev in the CCs. > Concerning the issue with non-functional midi in o

Re: [linux-audio-dev] [request] Info on the Awe32 schematics

Juan Linietsky wrote: > Does any of you know how to get PROPER docummentation on the Sound Blaster > AWE32? and If possible, official datasheets or something.. It is sometimes said that not even Creative's driver developers get proper datasheets ... > I think creative's official devkit is gone fr

Re: [linux-audio-dev] Vsound-like tools for ALSA?

Mark Constable wrote: > On Wed, 28 Jan 2004 07:42 pm, Mike Rawes wrote: > > pcm.fileout { > > type file > > slave.pcm "hw:0,0" > > file alsaout.raw > > } > > > > ..then aplay -D fileout foo.wav, will create a file called alsaout.raw > > ... and, how would one go about doing this for pmidi, an

Re: [linux-audio-dev] Re: [Alsa-devel] alsa 1.0.0 API changes???

Maarten de Boer wrote: > Out of curiosity: how did you manage to keep binary compatibility? With assembler magic (see alsa-symbols.h and pcm.h). Regards, Clemens

Re: [linux-audio-dev] Linux Security Module for realtime audio

Jesper Anderson wrote: > On Mon, Dec 08, 2003 at 12:13:48PM -0800, Tim Hockin wrote: > > Do they have a valid reason? Or are they just imposing their paranoia on us > > for fun? > > Their explanation is here: > > http://www.gtk.org/setuid.html Good reasons, IMHO. And I see no reason why drawing

Re: [linux-audio-dev] M-audio transit/ozone/MobilePre experiences?

[EMAIL PROTECTED] wrote: > Does the M-audio MobilePre work with Linux? No. > Earlier there was a 'beta' released (by Clemens Ladisch): It doesn't work. I think there is a bug in the USB subsystem in the kernel, but I don't have time to research further now. Currently

Re: [linux-audio-dev] MIDI part II

[EMAIL PROTECTED] wrote: > alsa-0.9.7 ( current version) seems to need some "magic" to get > started What exactly is your problem with 0.9.7? Regards, Clemens

[linux-audio-dev] M-Audio MobilePre/Sonica/Transit/Ozone testers wanted

The M-Audio MobilePre/Sonica/Transit/Ozone devices need a firmware download before they can be used with Linux. I've released a first beta of the madfu-firmware package which tries to accomplish this. Please note that I do not have any of these devices, and that the loader is not tested at all.

[linux-audio-dev] [ANN] MidiSport firmware loader 0.2

The MidiSport firmware loader allows to use the MidiSport USB MIDI interfaces from M-Audio/Midiman with Linux. Version 0.2 fixes a bug in the loader script which tried to load the firmware files from the wrong directory. Supported devices: MidiSport 1x1, 2x2, 4x4, 8x8, KeyStation, Oxygen, Radium,

Re: [linux-audio-dev] MIDI files contain strange byte sequences ?

Benno Senoner wrote: > I'm just writing some MIDI file ( SMF 0/1) loading routines and > while the file structure is quite simple I came across some MIDI files > (mainly .KAR (=midi + embedded lyric events)) where there are some > byte sequences that do not make sense to me. > (attaching a short h

Re: [linux-audio-dev] simultanious access to audio input

Robert Ross wrote: > I need to allow multiple programs/processes to take data from the same > audio device at the same time. ALSA has the dsnoop plugin for this. This isn't very well documented, but you might be able to find some example in the ALSA list archives. HTH Clemens

Re: [linux-audio-dev] System Exclusive question

[EMAIL PROTECTED] wrote: > Clemens Ladisch <[EMAIL PROTECTED]> wrote: > > My unit's light is active while the dump is being transmitted (several > > seconds, depending on the size of the data). Are you sure your's is > > sending anything? > > The MIDI a

Re: [linux-audio-dev] System Exclusive question

[EMAIL PROTECTED] wrote: > Jay Vaughan <[EMAIL PROTECTED]> wrote: > > >Has anyone had succes in getting SysEx data flowing back and forth > > >between Roland sound modules and their computer? Yes, SC-8820, over USB. > > >I have attached my > > >simple test program in case I'm doing something obvi

Re: [linux-audio-dev] midi 'resolution'

Lukas Degener wrote: > In a system/application, that recieves external midi data of any kind, > is there anything one can assume about _when_ some midi data is recieved? The data is received when the hardware raises an interrupt to notify the driver that some data is available, which can be at any

Re: [linux-audio-dev] request for a small app

Dave Phillips wrote: > I'm wondering if it might be possible to whip up a small app that > displays the following: > > ALSA/JACK connection status > patch name update > MIDI message flow (minus active sensing, of course) ASeqView does something like that.

[linux-audio-dev] Re: [linux-audio-user] problems with Midisport 2x2

Ivica Bukvic wrote: > I've got a small problem with my Midisport 2x2 MIDI interface. While it worked > ok before, now for some odd reason I cannot get it to open for MIDI output > (from the computer). I've checked the /var/log/messages and this is what I > got: > [...] > It says that the device was

  1   2   >