Thanks for your patience in working with csound 5. I'm glad your show went 
well. Please continue keeping us informed of your needs.

Regards,
Mike Gogins

----- Original Message ----- 
From: "Iain Duncan" 
To: 
Sent: Friday, April 15, 2005 8:13 PM
Subject: [Cs-dev] Thoughts from the field and csound5 goes live!


> So we just did our live show last night with csound5, and all was fine. 
> Yay! We did have to make mulitple versions of the score with various 
> starting points in case of problems because of the lack of advance 
> statement, but that was a fairly trivial task.
>
> One thought, perhaps this is already in the works. It would be really cool 
> for live use if one could start csound, and start/stop/move the score 
> independently. Perhaps this could be an api function, or is it already? 
> For example, it takes a while ( say 5 or 6 seconds ) for csound to finish 
> loading up our tables/score etc. Would be nice if we could do that, then 
> hit play at the right time and have music instantly on the beat. I am, of 
> course, just pie in the sky dreaming here, so my apologies if I'm asking 
> for very difficult features.
>
> Anyway, thanks everyone for all the work that's gone into csound5. Folks 
> at the show were very impressed with the sound, and all we did was run 
> straight from the machine into one eq unit and the main mixer. And we 
> appear to making a lot of folks curious about the feasability of running 
> an AMD/linux/csound instead of Mac/MAX-MSP. You can buy some really nice 
> nearfields with the price difference ... ; )
>
> Iain
>
>
>
>
> -------------------------------------------------------
> 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

> Thanks for your patience in working with csound 5. I'm glad your show 
> went well. Please continue keeping us informed of your needs.

I think we're the ones who should be doing the thanking here, the speed 
of bug fixes has been awesome. = )


>> already? For example, it takes a while ( say 5 or 6 seconds ) for 
>> csound to finish loading up our tables/score etc. Would be nice if we 
>> could do that, then hit play1 at the right time and have music 

It just occured to me that part of the reason for the slow start up may 
be all the console ouput. Even with -d and -m0 we still get a message 
for each instrument being defined, every macro definition, and every 
table header. For our show rig, this amounts to at least a thousand 
messages going by, maybe this is the cause of some of the delay? Is 
there any way we can actually get csound 5 to suppress absolutely all 
print output, or come up with more options so that we can further 
control what gets printed and what doesn't?

Thanks,
Iain


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

The additional printing it the price you pay for working with
unfinished software!  I suspect many of these message can go now as
those aspects seem to work.
==John ffitch


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

Maybe we aren't talking about the same messages, these are the same 
messages that have always been unsupressable with csound4 as well ...

ie
macro soanso defined etc

Thanks
Iain

jpff@codemist.co.uk wrote:
> The additional printing it the price you pay for working with
> unfinished software!  I suspect many of these message can go now as
> those aspects seem to work.
> ==John ffitch
> 
> 
> -------------------------------------------------------
> 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

I suppose that this would work:

csound >> /dev/null


Anthony

On 4/15/05 10:20 PM, Iain Duncan  etched in stone:

> Is 
> there any way we can actually get csound 5 to suppress absolutely all
> print output, or come up with more options so that we can further
> control what gets printed and what doesn't?



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

I am still having troubles understanding which messages you mean.
The nearest I can find is in score macros.  Is that what you mean?
That should have gone ages ago, but as I rarely use score macros I had
not noticed it.
==John ffitch


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

Anthony Kozar wrote:

> I suppose that this would work:
> 
> csound >> /dev/null

This one will work better (csound5 on linux prints messages to stderr):

csound ... 2> /dev/null


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

Well, I'd still like to get error messages, and actually I'd like to get 
the first sort of "I turned on" messages too. It's the thousand odd 
other messages I don't want. Would one of the below still allow error 
messages through?

Thanks
Iain

Istvan Varga wrote:
> Anthony Kozar wrote:
> 
>> I suppose that this would work:
>>
>> csound >> /dev/null
> 
> 
> This one will work better (csound5 on linux prints messages to stderr):
> 
> csound ... 2> /dev/null
> 
> 
> -------------------------------------------------------
> 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

I changed the code so more messages look at the -m#
==John ffitch


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

Attached is the output from csound -d -m0 piped to a file. Ideally, I 
think it would be good to still see everything up to the beginning of 
the macro messages. These are orc macro definitions as well as score 
ones. Apologies for the file size!

Iain

jpff@codemist.co.uk wrote:
> I am still having troubles understanding which messages you mean.
> The nearest I can find is in score macros.  Is that what you mean?
> That should have gone ages ago, but as I rarely use score macros I had
> not noticed it.
> ==John ffitch
> 
> 
> -------------------------------------------------------
> 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
> 

Awesome, thanks. Shall I report back any others I find that aren't being 
suppressed? Aside from error messages I mean. I assume that with -d -m0 
we should be seeing no messages aside from errors and the initial stuff?

Thanks
Iain

jpff@codemist.co.uk wrote:
> I changed the code so more messages look at the -m#
> ==John ffitch
> 
> 
> -------------------------------------------------------
> 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

Yes please; report any messages you think should not be there, and we
will either fix or tell you you are wrong :-)
==John ffitch


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

Ha ha ha, awesome. Will do some testing early next week.

You guys all rock, I just went to an underground party and had loads of 
folks telling us how great our live show sounded on Thursday, including 
comments on the overall sound, which was 100% csound processing. Lot of 
people excited about the system and curious about Csound!!!

I will also post a tar of all the files we used for the show in case 
anyone wants to look at it, though it is rather large and cluttered 
right now. Had to stop sometime and start doing the shows though!

To bed
Iain

jpff@codemist.co.uk wrote:
> Yes please; report any messages you think should not be there, and we
> will either fix or tell you you are wrong :-)
> ==John ffitch
> 
> 
> -------------------------------------------------------
> 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