Can you define -+ type options for device names and whether or not to open in full duplex?

Is it possible to always open in full duplex even if no sound comes in? 

-----Original Message-----
From: Victor Lazzarini 
Sent: Apr 28, 2005 7:24 AM
To: csound-devel@lists.sourceforge.net
Subject: [Cs-dev] suggestions?

I don't like to be insistent, but sny suggestions as to how best to fit in 
the full-duplex code for
portaudio OSX ?


Victor Lazzarini
Music Technology Laboratory
Music Department
National University of Ireland, Maynooth 



-------------------------------------------------------
SF.Net email is sponsored by: Tell us your software development plans!
Take this survey and enter to win a one-year sub to SourceForge.net
Plus IDC's 2005 look-ahead and a copy of this survey
Click here to start!  http://www.idcswdc.com/cgi-bin/survey?id=105hix
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel





-------------------------------------------------------
SF.Net email is sponsored by: Tell us your software development plans!
Take this survey and enter to win a one-year sub to SourceForge.net
Plus IDC's 2005 look-ahead and a copy of this survey
Click here to start!  http://www.idcswdc.com/cgi-bin/survey?id=105hix
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I don't think so. There seems to be a problem to open in full-duplex if
we don't use the input signal. I have to investigate that.

However, I don't see that many people would use input-only audio, so
what we could do is to open full-duplex if the user asks for audio in,
and then bypass the open-for-output (recopen) code.

The only problem here is that we would be limiting full-duplex to the same
device, instead of being flexible with in-out devices. Then we'll also have
to make the code compatible with linux and windows MME (possibly?), that
have different devices for input and output.

I'll have a look at Istvan's jack code, but the callback issue is not a 
problem,
since Michael's code works with just a small adaptation. The device opening is
the crux.

using +-full-duplex perhaps is a way out as well, but ideally it would be 
nice to
keep the -iadc -odac options, for continuity reasons.
Possibly -ofull-duplex ?

Victor

At 14:49 28/04/2005, you wrote:
>Can you define -+ type options for device names and whether or not to open 
>in full duplex?
>
>Is it possible to always open in full duplex even if no sound comes in?
>
>-----Original Message-----
>From: Victor Lazzarini 
>Sent: Apr 28, 2005 7:24 AM
>To: csound-devel@lists.sourceforge.net
>Subject: [Cs-dev] suggestions?
>
>I don't like to be insistent, but sny suggestions as to how best to fit in
>the full-duplex code for
>portaudio OSX ?
>
>
>Victor Lazzarini
>Music Technology Laboratory
>Music Department
>National University of Ireland, Maynooth
>
>
>
>-------------------------------------------------------
>SF.Net email is sponsored by: Tell us your software development plans!
>Take this survey and enter to win a one-year sub to SourceForge.net
>Plus IDC's 2005 look-ahead and a copy of this survey
>Click here to start!  http://www.idcswdc.com/cgi-bin/survey?id=105hix
>_______________________________________________
>Csound-devel mailing list
>Csound-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
>
>
>
>-------------------------------------------------------
>SF.Net email is sponsored by: Tell us your software development plans!
>Take this survey and enter to win a one-year sub to SourceForge.net
>Plus IDC's 2005 look-ahead and a copy of this survey
>Click here to start!  http://www.idcswdc.com/cgi-bin/survey?id=105hix
>_______________________________________________
>Csound-devel mailing list
>Csound-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/csound-devel

Victor Lazzarini
Music Technology Laboratory
Music Department
National University of Ireland, Maynooth 



-------------------------------------------------------
SF.Net email is sponsored by: Tell us your software development plans!
Take this survey and enter to win a one-year sub to SourceForge.net
Plus IDC's 2005 look-ahead and a copy of this survey
Click here to start!  http://www.idcswdc.com/cgi-bin/survey?id=105hix
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Victor Lazzarini wrote:

> I'll have a look at Istvan's jack code, but the callback issue is not a 
> problem,
> since Michael's code works with just a small adaptation. The device 
> opening is
> the crux.

What rtjack.c does is that it just records the device parameters
when recopen/playopen are called, but does not actually open the
device. The device is opened when either rtrecord or rtplay is first
called, and the parameters of both input and output are already known.
This approach does have one minor problem: you cannot report device
open errors in the usual way (that is, return value of recopen/playopen).


-------------------------------------------------------
SF.Net email is sponsored by: Tell us your software development plans!
Take this survey and enter to win a one-year sub to SourceForge.net
Plus IDC's 2005 look-ahead and a copy of this survey
Click here to start!  http://www.idcswdc.com/cgi-bin/survey?id=105hix
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net