Csound Csound-dev Csound-tekno Search About

Re: [Cs-dev] tests and examples for Cs5

Date2005-02-22 21:23
From"Art Hunkins"
SubjectRe: [Cs-dev] tests and examples for Cs5
I've really been concerned about wildly differing command-line flags amongst
the various Csound versions too.

On the recent survey of real-time Csound I sent out, I toyed with the idea
of asking for the flags each version used to call for various options -
especially MIDI in and audio out.

Unless we do all we can to standardize these flags, moving among versions
and platforms will be a real hassle, and many will end up back in the
fragmented Csound world in which we currently live.

In this respect, I much appreciate Istvan's Csound5 change with respect to
MIDI devices.

BTW, Dave P., by "text mode" do you mean "console mode" - i.e., no GUI? If
so, good question (I use CsEdit for Windows (Tordini), within which I can
run console or GUI versions interchangeably; it's a non-issue there).

Art Hunkins

----- Original Message -----
From: "Dave Phillips" 
To: 
Sent: Tuesday, February 22, 2005 10:33 AM
Subject: [Cs-dev] tests and examples for Cs5


> Greetings:
>
>   After reading Rick B's latest message re: Cs5 I started working on a
> collection of files and examples for beginners in Cs5. I've completed
> material for realtime audio, realtime MIDI, FLTK opcode usage, and
> connecting to JACK. I intend to provide examples for plugin usage and
> for adding new opcodes, and I will try to address Rick's other concerns
> regarding example files.
>
>   Btw, am I correct to assume that the majority of Csound users have
> abandoned the use of text mode ? It certainly looks that way from here.
> I consider this assumption to be a critical point, one that perhaps
> should be discussed a little more thoroughly by the developers.
>
>   Also, am I correct to assume that files written for MacCsound are
> incompatible with CsoundAV and/or Winsound (and vice-versa) ?
>
>   I have no idea what might be required to reconcile files from those
> versions of Csound with Cs5 (or any other version of Csound). I cannot
> supply flags and option switches for those platforms (many ofwhich have
> been designed with no regard at all towards compatibility with Cs4), and
> I invite any developers or users on those platforms to contribute the
> needed flags/switches to the examples set. At this time I'm supplying
> CsOptions only for Cs5 under Linux.
>
>   To Dr. B: Rick, how did you try running Cs5 ? Your message was short
> on details, and I need details. You didn't mention on what platform you
> tried it, with what files you tested it, or with what options. As far as
> examples go, I use your very own Trapped In Convert to test realtime
> audio output, with these options:
>
>     csound -+rtaudio=alsa -odac2 -d -m0 trappedrt.csd
>
> Actually I can dispense with the -+rtaudio switch, it's already defined
> in my $CSRTAUDIO setting.
>
> Best,
>
> dp
>
>
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2005-02-22 21:31
From"Richard Boulanger"
SubjectRe: [Cs-dev] tests and examples for Cs5
David,

Important to note is the fact that Art (and others) have found GUI wrappers
such as WinXsoundPro or Csedit to be important tools that make the
environment more produtive.

Am I correct Art?  Hope I am not speaking out of line for you.  Tordini's
Editor is excellent as is WinXSoundPro that Gabriel recommends.

Rick

on 2/22/05 4:23 PM, Art Hunkins at abhunkin@uncg.edu wrote:

> I've really been concerned about wildly differing command-line flags amongst
> the various Csound versions too.
> 
> On the recent survey of real-time Csound I sent out, I toyed with the idea
> of asking for the flags each version used to call for various options -
> especially MIDI in and audio out.
> 
> Unless we do all we can to standardize these flags, moving among versions
> and platforms will be a real hassle, and many will end up back in the
> fragmented Csound world in which we currently live.
> 
> In this respect, I much appreciate Istvan's Csound5 change with respect to
> MIDI devices.
> 
> BTW, Dave P., by "text mode" do you mean "console mode" - i.e., no GUI? If
> so, good question (I use CsEdit for Windows (Tordini), within which I can
> run console or GUI versions interchangeably; it's a non-issue there).
> 
> Art Hunkins
> 
> ----- Original Message -----
> From: "Dave Phillips" 
> To: 
> Sent: Tuesday, February 22, 2005 10:33 AM
> Subject: [Cs-dev] tests and examples for Cs5
> 
> 
>> Greetings:
>> 
>>   After reading Rick B's latest message re: Cs5 I started working on a
>> collection of files and examples for beginners in Cs5. I've completed
>> material for realtime audio, realtime MIDI, FLTK opcode usage, and
>> connecting to JACK. I intend to provide examples for plugin usage and
>> for adding new opcodes, and I will try to address Rick's other concerns
>> regarding example files.
>> 
>>   Btw, am I correct to assume that the majority of Csound users have
>> abandoned the use of text mode ? It certainly looks that way from here.
>> I consider this assumption to be a critical point, one that perhaps
>> should be discussed a little more thoroughly by the developers.
>> 
>>   Also, am I correct to assume that files written for MacCsound are
>> incompatible with CsoundAV and/or Winsound (and vice-versa) ?
>> 
>>   I have no idea what might be required to reconcile files from those
>> versions of Csound with Cs5 (or any other version of Csound). I cannot
>> supply flags and option switches for those platforms (many ofwhich have
>> been designed with no regard at all towards compatibility with Cs4), and
>> I invite any developers or users on those platforms to contribute the
>> needed flags/switches to the examples set. At this time I'm supplying
>> CsOptions only for Cs5 under Linux.
>> 
>>   To Dr. B: Rick, how did you try running Cs5 ? Your message was short
>> on details, and I need details. You didn't mention on what platform you
>> tried it, with what files you tested it, or with what options. As far as
>> examples go, I use your very own Trapped In Convert to test realtime
>> audio output, with these options:
>> 
>>     csound -+rtaudio=alsa -odac2 -d -m0 trappedrt.csd
>> 
>> Actually I can dispense with the -+rtaudio switch, it's already defined
>> in my $CSRTAUDIO setting.
>> 
>> Best,
>> 
>> dp
>> 
>> 
>> 
>> 
>> -------------------------------------------------------
>> SF email is sponsored by - The IT Product Guide
>> Read honest & candid reviews on hundreds of IT Products from real users.
>> Discover which products truly live up to the hype. Start reading now.
>> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
> 
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

_______________________________________________________________________
 +  Dr. Richard Boulanger, Professor
 +  Music Synthesis Department, Berklee College of Music
 +  1140 Boylston Street  - Boston, MA  02215-3693
 +  Office Phone: (617) 747-2485   Office Fax: (617) 747-2564
 +  eMail: rboulanger@csounds.com  or  rboulanger@berklee.edu
 +  WebPage: http://csounds.com/boulanger/
________________________________________________________________________
 +  Almost Everything Csound @ http://csounds.com/
 +  The Csound Catalog with Audio @ http://csounds.com/catalog/
 +  The Csound Book @ http://csounds.com/book/
 +  The Csound Magazine @ http://csounds.com/ezine/
 +  CsoundForums @ http://csounds.com/phpBB2/
________________________________________________________________________



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2005-02-22 21:52
FromIstvan Varga
SubjectRe: [Cs-dev] tests and examples for Cs5
Art Hunkins wrote:

> On the recent survey of real-time Csound I sent out, I toyed with the idea
> of asking for the flags each version used to call for various options -
> especially MIDI in and audio out.

For Csound5 the flags are:

Real time audio
---------------

   -+rtaudio=NAME            select module 'NAME' for handling real time
                             audio I/O; choices are: null (no audio), portaudio,
                             alsa (Linux only), jack (Linux only, but maybe also
                             OS X). The default is portaudio.

   -i adc                    enable real time audio input from default device
   -i adcN                   use device number 'N' for audio input
   -i adc:NAME               use the device named 'NAME' for audio input
   -o dac                    enable real time audio output to default device
   -o dacN                   use device number 'N' for audio output
   -o dac:NAME               use the device named 'NAME' for audio output

   NOTE: it depends on the system and selected module if a number or a name
   should be specified for -iadc/-odac. PortAudio takes a device number,
   the others a device name, but on Linux PortAudio can also be used with
   a device name.

   -b NFRAMES                 set buffer fragment size to NFRAMES sample frames;
                              sound I/O will block at this interval (a lower
                              value means less timing jitter but higher CPU
                              usage)
   -B NFRAMES                 set total buffer size to NFRAMES sample frames;
                              should be greater than, and an integer multiple of
                              the value specified for -b;
                              a lower value means better latency but buffer
                              underruns are more likely to occur

   Some plugins may have additional options (csound --help prints any such
   flags); these are for JACK only:

   -+jack_client=NAME         JACK client name (default: csound5)
   -+jack_inportname=NAME     JACK input port name prefix (default: input)
   -+jack_outportname=NAME    JACK output port name prefix (default: output)
   -+jack_sleep_time=N        JACK sleep time in microseconds (default: 1000)

MIDI
----

   -+rtmidi=NAME              use module 'NAME' for handling real time MIDI
                              choices at this time are limited to null (no MIDI)
                              and portmidi (the default)

   -M INDEV                   read MIDI input from device 'INDEV'; device
                              identifiers may be numbers or names depending on
                              system, but are always numbers starting from zero
                              with PortMIDI

   -Q OUTDEV                  write MIDI output to device 'OUTDEV'; device
                              identifiers may be numbers or names depending on
                              system, but are always numbers starting from zero
                              with PortMIDI

   -F FILENAME                read MIDI file 'FILENAME'; file should not have
                              more than one track

   Some plugins may have additional options (csound --help prints any such
   flags); currently, there are none.


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2005-02-23 03:45
From"Richard Boulanger"
SubjectRe: [Cs-dev] tests and examples for Cs5
Dave,

Blue is an amazingly productive front-end for Csound.

If it were to be the default cross-platform GUI front-end for Csound5, that
would be great with me and an easy sell to the community at large too, with
the bonus that Steven has all those tools in there to support composition
and sound design too - and I would think, that if things came up, he would
address them in the same thoughtful way he has developed this fantastic app.

-dB  

 on 2/22/05 10:47 PM, Dave Phillips at dlphilp@bright.net wrote:

> Richard Boulanger wrote:
> 
>> David,
>> 
>> Important to note is the fact that Art (and others) have found GUI wrappers
>> such as WinXsoundPro or Csedit to be important tools that make the
>> environment more produtive.
>> 
> I agree, I have no beef with the GUI
> wrappers/launchers/frontends/environments, I'm glad they're available.
> And yes, they can definitely make for a more productive workflow.
> 
> blue pretty much rocks the house for me.
> 
> Best,
> 
> dp
> 
> 
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

_______________________________________________________________________
 +  Dr. Richard Boulanger, Professor
 +  Music Synthesis Department, Berklee College of Music
 +  1140 Boylston Street  - Boston, MA  02215-3693
 +  Office Phone: (617) 747-2485   Office Fax: (617) 747-2564
 +  eMail: rboulanger@csounds.com  or  rboulanger@berklee.edu
 +  WebPage: http://csounds.com/boulanger/
________________________________________________________________________
 +  Almost Everything Csound @ http://csounds.com/
 +  The Csound Catalog with Audio @ http://csounds.com/catalog/
 +  The Csound Book @ http://csounds.com/book/
 +  The Csound Magazine @ http://csounds.com/ezine/
 +  CsoundForums @ http://csounds.com/phpBB2/
________________________________________________________________________



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2005-02-23 03:47
FromDave Phillips
SubjectRe: [Cs-dev] tests and examples for Cs5
Richard Boulanger wrote:

>David,
>
>Important to note is the fact that Art (and others) have found GUI wrappers
>such as WinXsoundPro or Csedit to be important tools that make the
>environment more produtive.
>
I agree, I have no beef with the GUI 
wrappers/launchers/frontends/environments, I'm glad they're available. 
And yes, they can definitely make for a more productive workflow.

blue pretty much rocks the house for me.

Best,

dp




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net