Re: Simultaneous recording

Joachim Boomberschloss wrote:

>Thanks Ross and Jasper.
>
>I am wondering how difficult it would be to write with
>portaudio a windows driver that will record from a
>device and let multiple clients to "record" from
>itself, passing along the audio recorded from the
>original device. Anyone done something like that in
>the past?
>
>I think there are commercial products that do this,
>but I would like something I can distribute with my
>application.
>
>Any thoughts?
>  
>
Sounds a lot like esd and friends.

I'd bet there's already a port of esd for windows..

-SteveK

RE: ASIO multiple device output in V19?

Does it actually work and compile npw?

Bob

-----Original Message-----
From: portaudio-admin <at> techweb.rfa.org
[mailto:portaudio-admin <at> techweb.rfa.org]On Behalf Of Andrew Baldwin
Sent: Sunday, October 31, 2004 7:13 PM
To: Portaudio List
Cc: svogelpo <at> ist.ucf.edu
Subject: Re: [Portaudio] ASIO multiple device output in V19?

One alternative might be to try the WDMKS interface in PA19.

That would give low latency, and shouldn't have any architectural
limitations about opening multiple devices. In the case of the Audigy 2 it
would bypass the need for using the ASIO4ALL driver. I guess the MOTU828
also has WDM drivers.

The problems with this approach could be that WDMKS does not yet work with
those devices (though fixing it to work may still be less effort that
re-architecting the whole ASIO backend!)

Andrew.

On Fri, 29 Oct 2004 19:33:22 +0200, Ross Bencina <rbencina <at> iprimus.com.au>
wrote:

> Hi Scott

WDMKS (was: Re: ASIO multiple device output in V19?)

Robert McGwier wrote:

>Does it actually work and compile npw?
>
>Bob
>
  I can report that WDMKS does compile and work on my system (XP, VS.NET 
2003). It seems to behave somewhat oddly, though.

  As I said earlier, I have a MOTU828 and an Audigy 2 NX that I want to 
use for output simultaneously. PortAudio doesn't seem to want to 
initialize the MOTU using the WDMKS host. Two devices are reported from 
the MOTU, one for analog and one for S/PDIF, and both report an "Invalid 
device" error when I call Pa_OpenStream(). I assume this is probably a 
problem with the MOTU drivers; the Audigy is my default Windows output 
device, so I doubt my application is conflicting with something else for 
the use of the MOTU.

  What I can do, however, is use the ASIO host for the MOTU and the 
WDMKS host for the Audigy. This works, and I can get sound from both 
devices---except when I try to initialize the Audigy with more than 2 
output channels. Even though the device reports 8 outputs, when I try to 
initialize it with any more than 2 I get another "Invalid device."

  But, now that I know about the WDMKS host I am definitely getting 
closer to what I need. Hopefully this report will help in debugging the 
host---or someone can tell me that I'm just not using it properly. :-P

  ~Scott Vogelpohl
 Media Convergence Lab

Re: Simultaneous recording

Steve Kann wrote:
> Joachim Boomberschloss wrote:
>> Thanks Ross and Jasper.
>>
>> I am wondering how difficult it would be to write with
>> portaudio a windows driver that will record from a
>> device and let multiple clients to "record" from
>> itself, passing along the audio recorded from the
>> original device. Anyone done something like that in
>> the past?
>>
>> I think there are commercial products that do this,
>> but I would like something I can distribute with my
>> application.
>>
>> Any thoughts?
>>  
>>
> Sounds a lot like esd and friends.
> 
> I'd bet there's already a port of esd for windows..

If there is, could you PLEASE point it out, I've just searched for a bit 
and didn't find any mention of it. I do know that arts uses, or was 
planning on using platform-independent library for its sound input and 
output, but that's only one (relatively unimportant) aspect of the system.

If anyone were to create something like this as an open-source (or at 
least freeware) project, possibly also with functionality similar to 
Virtual Audio Cable (commercial product), that would be incredibly cool. 

Who has tried WDM but couldn't get it to work?

I managed to modify the WDM code enough to get it running on my Dell
laptop (with crappy onboard "Crystal Audio" sound).  I'm looking for
people to test it out and see if I've solved anyone else's problems. 
Also, if anyone who got WDM to work, I'd like to have you test to see
if there are any regressions

thanks,
-Ben Allison

RE: Who has tried WDM but couldn't get it to work?

I tried it out and got it to compile.  However, I could never get a stream
to open (got various errors about bad I/O, etc).  I'd be interested in
testing your changes.

Eric Wachsmann
FlexRadio Systems

-----Original Message-----
From: portaudio-admin <at> techweb.rfa.org
[mailto:portaudio-admin <at> techweb.rfa.org] On Behalf Of
portaudio-request <at> techweb.rfa.org
Sent: Wednesday, November 03, 2004 5:30 AM
Date: Tue, 2 Nov 2004 19:47:34 -0500
From: Ben Allison <benjamin.james.allison <at> gmail.com>
Reply-To: Ben Allison <benjamin.james.allison <at> gmail.com>
To: portaudio <at> techweb.rfa.org
Subject: [Portaudio] Who has tried WDM but couldn't get it to work?

I managed to modify the WDM code enough to get it running on my Dell laptop
(with crappy onboard "Crystal Audio" sound).  I'm looking for people to test
it out and see if I've solved anyone else's problems. 
Also, if anyone who got WDM to work, I'd like to have you test to see if
there are any regressions

thanks,
-Ben Allison

[PATCH] pa_linux_alsa.c: Support of multiple devices for each card.

This patch adds support of multiple devices for each card to 
pa_linux_alsa.c.
It's a diff against todays cvs version tagged v19-devel.

Mikael Magnusson

#! /bin/sh -e
## 30_alsa2.dpatch by  <mikma <at> users.sourceforge.net>
##
## All lines beginning with `## DP:' are a description of the patch.
## DP: Support of multiple devices for each card.

if [ $# -lt 1 ]; then
    echo "`basename $0`: script expects -patch|-unpatch as argument" >&2
    exit 1
fi

[ -f debian/patches/00patch-opts ] && . debian/patches/00patch-opts
patch_opts="${patch_opts:--f --no-backup-if-mismatch} ${2:+-d $2}"

case "$1" in
    -patch) patch -p1 ${patch_opts} < $0;;
    -unpatch) patch -R -p1 ${patch_opts} < $0;;
    *)
        echo "`basename $0`: script expects -patch|-unpatch as argument" >&2
        exit 1;;
esac

[PATCH] updated configure.in and Makefile.in patch

I have updated my configure.in and Makefile.in patch against todays cvs 
tag v19-devel.

Mikael Magnusson

#! /bin/sh -e
## 10_configure.in.dpatch by  <mikma <at> users.sourceforge.net>
##
## All lines beginning with `## DP:' are a description of the patch.
## DP: Using libtool and set rpath, release 19, version-info 0:19:0 and
## DP: add needed libs to DLL_LIBS.

if [ $# -lt 1 ]; then
    echo "`basename $0`: script expects -patch|-unpatch as argument" >&2
    exit 1
fi

[ -f debian/patches/00patch-opts ] && . debian/patches/00patch-opts
patch_opts="${patch_opts:--f --no-backup-if-mismatch} ${2:+-d $2}"

case "$1" in
    -patch) patch -p1 ${patch_opts} < $0;;
    -unpatch) patch -R -p1 ${patch_opts} < $0;;
    *)
        echo "`basename $0`: script expects -patch|-unpatch as argument" >&2
        exit 1;;
esac

[PATCH] V18 compatibility in V19

Hello,

I have made a patch for Portaudio V19 (cvs 20040729), that makes the API 
backward compatible with the V18 API.

The patch consists of both changes to portaudio.h and addition of 
pa_compat18.c.

The compatibility layer is activated with "#define PA_COMPAT18" before 
including portaudio.h. It will define the following macros:

#define PortAudioStream PaStream
#define Pa_CountDevices Pa_GetDeviceCount
#define Pa_GetDefaultInputDeviceID Pa_GetDefaultInputDevice
#define Pa_GetDefaultOutputDeviceID Pa_GetDefaultOutputDevice
#define PaTimestamp PaTime
#define PaDeviceID PaDeviceIndex
#define Pa_OpenStream Pa_OpenStream18
#define Pa_CloseStream Pa_CloseStream18
#define Pa_GetMinNumBuffers Pa_GetMinNumBuffers18

The source pa_compat18.c contains definitions of Pa_OpenStream18, 
Pa_CloseStream18, Pa_GetMinNumBuffers18.

I have tested the compatibility layer with several test programs in 
pa_tests and iaxclient, and it seems to work well. I'm using a Sound 
Blaster Live 5.1 and VIA V8233 on a Athlon running Debian testing.

Mikael Magnusson

Re: Simultaneous recording

Jasper van de Gronde wrote:

> Steve Kann wrote:
>
>> Joachim Boomberschloss wrote:
>>
>>> Thanks Ross and Jasper.
>>>
>>> I am wondering how difficult it would be to write with
>>> portaudio a windows driver that will record from a
>>> device and let multiple clients to "record" from
>>> itself, passing along the audio recorded from the
>>> original device. Anyone done something like that in
>>> the past?
>>>
>>> I think there are commercial products that do this,
>>> but I would like something I can distribute with my
>>> application.
>>>
>>> Any thoughts?
>>>  
>>>
>> Sounds a lot like esd and friends.
>>
>> I'd bet there's already a port of esd for windows..
>
>
> If there is, could you PLEASE point it out, I've just searched for a 
> bit and didn't find any mention of it. I do know that arts uses, or 
> was planning on using platform-independent library for its sound input