Hi Istvan and all,

I've been using the .csoundrc file now and it seems to be that putting 
--sched in there doesn't seem to work.  Also, if using --sched on the 
commandline, it gives me an error that -o dac and -d are needed, even 
though I have them in the .csoundrc.

I can't tell if --expression-opt is really working with .csoundrc; any 
way to tell?

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

Will lineevents be supported in Csound5?

Cecilia needs them.

_________________________________________
Pour en savoir plus / To find out more:
http://jeanpiche.com



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

steven yi wrote:

> I've been using the .csoundrc file now and it seems to be that putting 
> --sched in there doesn't seem to work.  Also, if using --sched on the 
> commandline, it gives me an error that -o dac and -d are needed, even 
> though I have them in the .csoundrc. 

I think that --sched has never worked anywhere but at the command line.

> I can't tell if --expression-opt is really working with .csoundrc; any 
> way to tell? 

Well, you can try running a file without it and subjectively compare the 
results, but that's a bit brute force.

Btw, can you please post an example .csoundrc file ? I'm unsure how one 
is composed now.

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

Greetings:

  I've spent the last few days working on organizing a set of tests and 
examples for newcomers to Cs5. I've taken this list of topics from Dr 
B's recent message:

Real-time audio I/O *
Real-time MIDI I/O *
Write to File *
Plugin opcodes
UDOs
Include files *
Multi-Channel Output *
InterApplication Communication
Python Driven Orcs
Changing buffer sizes
Analysis and Other Utilities
JACK *
FTLK *
SoundFonts *

Items with * are already done. I can deal with the utilities and buffer 
size stuff, but I'm soliciting for contributions to the plugins, UDOs, 
IPC, and Python topics. Those are all outside my domains of interest and 
I have little or no useful knowledge there.

What other topics ought to be included for this collection ?

I'm looking for brief demonstrations of the topics, not full-bore 
highly-detailed presentations. I need simple CSD or orc/sco files that 
clearly show how the topic is implemented in Cs5. For example, I don't 
want a technical explanation of the plugin API, I want an example that 
shows a beginner how to install and test a 3rd-party Csound plugin. The 
emphasis in these examples is on use, not theory. Explanations abound, 
useful examples do not.

TIA for any assistance you can give.

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

steven yi wrote:

> I've been using the .csoundrc file now and it seems to be that putting 
> --sched in there doesn't seem to work.  Also, if using --sched on the 
> commandline, it gives me an error that -o dac and -d are needed, even 
> though I have them in the .csoundrc.

--sched is a dangerous option and must be specified explicitly on
the command line. The other requirements are to avoid using --sched
in deferred time (which would lock up the machine), and the code
for --sched which is independent of the main command line parser
does not read .csoundrc.
I have created a simple "watchdog" utility (it was posted to the list
yesterday) that can terminate any real time processes (such as Csound
with --sched) in case of a lock-up, allowing for much safer real time
operation. Adding this feature to Csound and integrating with the
--sched code might make the checks unnecessarily and the "requires -d
and -o dac" message could go away.

> I can't tell if --expression-opt is really working with .csoundrc; any 
> way to tell?

Yes, it does, it is just like any other "normal" Csound options;
only --sched is treated in a special way, everything else should
work in .csoundrc and CSD files just as well on the command line
(well, there is one exception: you cannot set the orc/sco names
in .csoundrc).


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

Hi Istvan,

If --sched could either realize that -d and -o are in .csoundrc, or if 
it can not require them and the watchdog is incorporated, I think that 
would be great.  And thanks for the explanation on the rest!

steven

Istvan Varga wrote:

> steven yi wrote:
>
>> I've been using the .csoundrc file now and it seems to be that 
>> putting --sched in there doesn't seem to work.  Also, if using 
>> --sched on the commandline, it gives me an error that -o dac and -d 
>> are needed, even though I have them in the .csoundrc.
>
>
> --sched is a dangerous option and must be specified explicitly on
> the command line. The other requirements are to avoid using --sched
> in deferred time (which would lock up the machine), and the code
> for --sched which is independent of the main command line parser
> does not read .csoundrc.
> I have created a simple "watchdog" utility (it was posted to the list
> yesterday) that can terminate any real time processes (such as Csound
> with --sched) in case of a lock-up, allowing for much safer real time
> operation. Adding this feature to Csound and integrating with the
> --sched code might make the checks unnecessarily and the "requires -d
> and -o dac" message could go away.
>
>> I can't tell if --expression-opt is really working with .csoundrc; 
>> any way to tell?
>
>
> Yes, it does, it is just like any other "normal" Csound options;
> only --sched is treated in a special way, everything else should
> work in .csoundrc and CSD files just as well on the command line
> (well, there is one exception: you cannot set the orc/sco names
> in .csoundrc).
>



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

Hi Dave,


> Btw, can you please post an example .csoundrc file ? I'm unsure how 
> one is composed now.


A .csoundrc file is just a one-line textfile that  has flags that you 
would normally use.  For example, my .csoundrc file current is:

-+rtaudio=alsa --expression-opt -d -o dac -m0


So, since Istvan has fixed up the precedence order of flags, these are 
now my "defaults" for csound.  I can still override by giving flags to 
the commandline or in the CSD, but at least now if I type "csound 
somefile.csd" it defaults to realtime playback and using Alsa.

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