Csound Csound-dev Csound-tekno Search About

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

Date2005-02-22 23:18
From"Art Hunkins"
SubjectRe: [Cs-dev] tests and examples for Cs5
Thanks for these values, Istvan.

I'm especially thankful for the useful defaults, -i adc and -o dac.

I'll go a step further and ask why -M can't be valid (with a default of 0)
as well as -Q (likewise, default = 0)?

I presume that -b and -B have builtin defaults. Whatever they are, they work
really poorly (-B) for my fairly recent WinME machine. -B 1000 works fine.
It would be really helpful if the defaults were closer to that figure than
where they are now.

Art Hunkins

----- Original Message -----
From: "Istvan Varga" 
To: 
Sent: Tuesday, February 22, 2005 4:52 PM
Subject: Re: [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
> 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 23:26
FromIstvan Varga
SubjectRe: [Cs-dev] tests and examples for Cs5
Art Hunkins wrote:

> I presume that -b and -B have builtin defaults. Whatever they are, they work
> really poorly (-B) for my fairly recent WinME machine. -B 1000 works fine.
> It would be really helpful if the defaults were closer to that figure than
> where they are now.

I think -B defaults to 1024, but it may be very different on Windows
(16384 or something like that, if I recall correctly).



-------------------------------------------------------
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 23:26
Fromsteven yi
Subject[Cs-dev] Cs5 Windows
Hi All,

For the Windows users, I've compiled from CVS today and now get a 
segmentation fault when trying to output in realtime.

Began Exec(csound -W -d -o dac "C:\work\blue\music_gamma\tempCsd44665.csd").
Localisation of messages is disabled, using default language.
PortAudio real-time audio module for Csound by John ffitch
0dBFS level = 32767.0
time resolution is 279.365 ns
Csound version 5.00 beta (float samples) Feb 22 2005
libsndfile-1.0.11
UnifiedCSD:  C:\work\blue\music_gamma\tempCsd44665.csd
STARTING FILE
Creating orchestra
Creating C:\DOCUME~1\ADMINI~1.orc (77C5FD00)
Creating score
orchname:  C:\DOCUME~1\ADMINI~1.orc
scorename: C:\DOCUME~1\ADMINI~1.sco
**** allocgen tanh to 697C1170
**** allocated 44
Csound tidy up: Segmentation violation
inactive allocs returned to freespace
end of score.		   overall amps:      0.0
	   overall samples out of range:        0

Doesn't seem to matter if I use -o dac or -o dac3 (which I was using 
before).  Not using -d doesn't give any more information.

Anyone else getting this?

steven



-------------------------------------------------------
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 23:34
FromIstvan Varga
SubjectRe: [Cs-dev] tests and examples for Cs5
Art Hunkins wrote:

> I'll go a step further and ask why -M can't be valid (with a default of 0)
> as well as -Q (likewise, default = 0)?

The command line parser requires -M and -Q to have an argument
(this is also true of -i and -o, where you need to use adc, dac,
or a file name); also, it is not as easy to select a good "default"
device for MIDI, as it is most likely that of the many ports
available only one will be usable (the device that you have set up
to send data to or receive from Csound), unlike in the case of
audio.


-------------------------------------------------------
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 01:53
FromAnthony Kozar
SubjectRe: [Cs-dev] tests and examples for Cs5
There will never be default options for real-time that work for everyone or
every machine.  Or even most people and most machines.  The -b and -B
options are especially machine-dependent and what works for you may be
horribly unusuable on another machine.

I personally do not see any way to escape this.

Using default I/O devices may be a little bit easier but I would guess that
they still will not work for every "simple" or "common" setup.  *shrug*

Every time I get a CSD from someone, I have to modify the .  My
preference for OS 9 would be that they be blank.  (The Mac GUI provides all
necessary options).

Anthony

On 2/22/05 6:18 PM, Art Hunkins  etched in stone:

> I presume that -b and -B have builtin defaults. Whatever they are, they work
> really poorly (-B) for my fairly recent WinME machine. -B 1000 works fine.
> It would be really helpful if the defaults were closer to that figure than
> where they are now.



-------------------------------------------------------
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 10:45
FromIstvan Varga
SubjectRe: [Cs-dev] tests and examples for Cs5
Anthony Kozar wrote:

> Every time I get a CSD from someone, I have to modify the .  My
> preference for OS 9 would be that they be blank.  (The Mac GUI provides all
> necessary options).

I also do not like CSD files that have options which often differ
from my preferences or even do not work at all. And before my recent
changes to Csound5, CSD options even used to override command line
options, something that I found really annoying.


-------------------------------------------------------
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