I think the label for this section is misleading:

/** @}*/
    /** @defgroup FILEIO File Input/Output
     *
     *  @{
     */

It's not specifically about file input/output, but about audio and midi IO configuration.
The csoundSetOutput() etc functions can be used to set realtime audio IO as well as file.

I recommend a re-labelling. Actually I would prefer if these functions were moved to
a 'engine configuration' section. 


Dr Victor Lazzarini
Senior Lecturer
Dept. of Music
NUI Maynooth Ireland
tel.: +353 1 708 3545
Victor dot Lazzarini AT nuim dot ie




------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Ah, I had actually misunderstood their usage.

I'm thinking that:
PUBLIC void csoundSetOutput (CSOUND *csound, char *name, char *type,
char *format)
PUBLIC void csoundSetInput (CSOUND *csound, char *name)

Inherit the fact that there is a single command line flag, that can be
used as filename or using "dac" for RT audio. However, this is not a
clear interface. How about having:

PUBLIC void csoundSetOutputInterface (CSOUND *csound, char *name, char
*type, char *format)
PUBLIC void csoundSetInputInterface (CSOUND *csound, char *name)

PUBLIC void csoundSetOutputFilename (CSOUND *csound, char *name, char
*type, char *format)
PUBLIC void csoundSetInputFilename (CSOUND *csound, char *name)

to set more meaningful things, and using one set actually invalidates the other?

The same would apply to:
PUBLIC void csoundSetMIDIInput (CSOUND *csound, char *name)
PUBLIC void csoundSetMIDIFileInput (CSOUND *csound, char *name)
PUBLIC void csoundSetMIDIOutput (CSOUND *csound, char *name)
PUBLIC void csoundSetMIDIFileOutput (CSOUND *csound, char *name)

Is the function:
csoundGetOutputFileName (CSOUND *)
useful? Are there cases where the host wouldn't know, and need to?

I agree the previous functions should be moved to the engine section,
but should this one go with the other callbacks in the control and
events section?:
PUBLIC void csoundSetFileOpenCallback (CSOUND *p, void(*func)(CSOUND
*, const char *, int, int, int))

Cheers,
Andrés

On Thu, Feb 28, 2013 at 6:06 AM, Victor Lazzarini
 wrote:
> I think the label for this section is misleading:
>
> /** @}*/
>     /** @defgroup FILEIO File Input/Output
>      *
>      *  @{
>      */
>
> It's not specifically about file input/output, but about audio and midi IO configuration.
> The csoundSetOutput() etc functions can be used to set realtime audio IO as well as file.
>
> I recommend a re-labelling. Actually I would prefer if these functions were moved to
> a 'engine configuration' section.
>
>
> Dr Victor Lazzarini
> Senior Lecturer
> Dept. of Music
> NUI Maynooth Ireland
> tel.: +353 1 708 3545
> Victor dot Lazzarini AT nuim dot ie
>
>
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_feb
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-

The problem is that while MIDI has -M and -F for device and file output, audio has only -o. You can
have both -F and -M afaik, but audio is either file or dac. So we can change the name, but I think we
need to keep having a single function for setting audio output.

Victor
On 28 Feb 2013, at 20:41, Andres Cabrera wrote:

> Ah, I had actually misunderstood their usage.
> 
> I'm thinking that:
> PUBLIC void csoundSetOutput (CSOUND *csound, char *name, char *type,
> char *format)
> PUBLIC void csoundSetInput (CSOUND *csound, char *name)
> 
> Inherit the fact that there is a single command line flag, that can be
> used as filename or using "dac" for RT audio. However, this is not a
> clear interface. How about having:
> 
> PUBLIC void csoundSetOutputInterface (CSOUND *csound, char *name, char
> *type, char *format)
> PUBLIC void csoundSetInputInterface (CSOUND *csound, char *name)
> 
> PUBLIC void csoundSetOutputFilename (CSOUND *csound, char *name, char
> *type, char *format)
> PUBLIC void csoundSetInputFilename (CSOUND *csound, char *name)
> 
> to set more meaningful things, and using one set actually invalidates the other?
> 
> The same would apply to:
> PUBLIC void csoundSetMIDIInput (CSOUND *csound, char *name)
> PUBLIC void csoundSetMIDIFileInput (CSOUND *csound, char *name)
> PUBLIC void csoundSetMIDIOutput (CSOUND *csound, char *name)
> PUBLIC void csoundSetMIDIFileOutput (CSOUND *csound, char *name)
> 
> Is the function:
> csoundGetOutputFileName (CSOUND *)
> useful? Are there cases where the host wouldn't know, and need to?
> 
> I agree the previous functions should be moved to the engine section,
> but should this one go with the other callbacks in the control and
> events section?:
> PUBLIC void csoundSetFileOpenCallback (CSOUND *p, void(*func)(CSOUND
> *, const char *, int, int, int))
> 
> Cheers,
> Andrés
> 
> On Thu, Feb 28, 2013 at 6:06 AM, Victor Lazzarini
>  wrote:
>> I think the label for this section is misleading:
>> 
>> /** @}*/
>>    /** @defgroup FILEIO File Input/Output
>>     *
>>     *  @{
>>     */
>> 
>> It's not specifically about file input/output, but about audio and midi IO configuration.
>> The csoundSetOutput() etc functions can be used to set realtime audio IO as well as file.
>> 
>> I recommend a re-labelling. Actually I would prefer if these functions were moved to
>> a 'engine configuration' section.
>> 
>> 
>> Dr Victor Lazzarini
>> Senior Lecturer
>> Dept. of Music
>> NUI Maynooth Ireland
>> tel.: +353 1 708 3545
>> Victor dot Lazzarini AT nuim dot ie
>> 
>> 
>> 
>> 
>> ------------------------------------------------------------------------------
>> Everyone hates slow websites. So do we.
>> Make your web apps faster with AppDynamics
>> Download AppDynamics Lite for free today:
>> http://p.sf.net/sfu/appdyn_d2d_feb
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
> 
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_feb
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

Dr Victor Lazzarini
Senior Lecturer
Dept. of Music
NUI Maynooth Ireland
tel.: +353 1 708 3545
Victor dot Lazzarini AT nuim dot ie




------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I want to be able to output simultaneously to audio and to soundfile.

Regards,

Mike

On Thu, Feb 28, 2013 at 3:41 PM, Andres Cabrera <mantaraya36@gmail.com> wrote:

Ah, I had actually misunderstood their usage.

I'm thinking that:
PUBLIC void csoundSetOutput (CSOUND *csound, char *name, char *type,
char *format)
PUBLIC void csoundSetInput (CSOUND *csound, char *name)

Inherit the fact that there is a single command line flag, that can be
used as filename or using "dac" for RT audio. However, this is not a
clear interface. How about having:

PUBLIC void csoundSetOutputInterface (CSOUND *csound, char *name, char
*type, char *format)
PUBLIC void csoundSetInputInterface (CSOUND *csound, char *name)

PUBLIC void csoundSetOutputFilename (CSOUND *csound, char *name, char
*type, char *format)
PUBLIC void csoundSetInputFilename (CSOUND *csound, char *name)

to set more meaningful things, and using one set actually invalidates the other?

The same would apply to:
PUBLIC void csoundSetMIDIInput (CSOUND *csound, char *name)
PUBLIC void csoundSetMIDIFileInput (CSOUND *csound, char *name)
PUBLIC void csoundSetMIDIOutput (CSOUND *csound, char *name)
PUBLIC void csoundSetMIDIFileOutput (CSOUND *csound, char *name)

Is the function:
csoundGetOutputFileName (CSOUND *)
useful? Are there cases where the host wouldn't know, and need to?

I agree the previous functions should be moved to the engine section,
but should this one go with the other callbacks in the control and
events section?:
PUBLIC void csoundSetFileOpenCallback (CSOUND *p, void(*func)(CSOUND
*, const char *, int, int, int))

Cheers,
Andrés

On Thu, Feb 28, 2013 at 6:06 AM, Victor Lazzarini
<Victor.Lazzarini@nuim.ie> wrote:
> I think the label for this section is misleading:
>
> /** @}*/
>     /** @defgroup FILEIO File Input/Output
>      *
>      *  @{
>      */
>
> It's not specifically about file input/output, but about audio and midi IO configuration.
> The csoundSetOutput() etc functions can be used to set realtime audio IO as well as file.
>
> I recommend a re-labelling. Actually I would prefer if these functions were moved to
> a 'engine configuration' section.
>
>
> Dr Victor Lazzarini
> Senior Lecturer
> Dept. of Music
> NUI Maynooth Ireland
> tel.: +353 1 708 3545
> Victor dot Lazzarini AT nuim dot ie
>
>
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_feb
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel

--
Michael Gogins
Irreducible Productions
http://www.michael-gogins.com
Michael dot Gogins at gmail dot com

Dr. Richard Boulanger, Ph.D.   

Professor of Electronic Production and Design

Professional Writing and Music Technology Division

Office @ 161 Mass Ave - 4th Floor

617-747-2485 (office)  774-488-9166 (cell)

http://csounds.com/boulanger     http://csounds.com/mathews

http://boulangerlabs.com    http://csoundforlive.com   http://csounds.com