Csounders,

I'd like to take the opportunity to share this little tutorial I wrote with the community: it's a very easy way to set up a multi-channel audio/MIDI router to use Csound with Logic (or any other sequencer) through the OSX IAC driver and Soundflower.
this is coming from a beginner, so it should really be accessible to everyone.
you can find it here: http://www.csounds.com/node/1501

beside the obvious easy way of creating MIDI automations, the reason why I wanted this set up was to facilitate the mixing process. which leads me to the next topic:

as a beginner I find managing the gain stage in Csound to be a fairly complex process and I honestly think other people feel the same way about it.
would it be possible to develop some sort of "mixer" opcode, or any other way that could make the whole process easier without pushing people like me to resort to external tools like Logic?

of course, if this is just me, there's nothing really to talk about here, but I do think other people feel the same.
I'd like you to share your thoughts on the topic.

Andreas

Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

hi andreas -
i think there are different options for mixing in csound, for instance
global audio variables, the chn opcodes, the zak patch system. did you
try one of it and found it not suitable for your needs?
	joachim

Am 30.08.2011 16:08, schrieb andreas russo:
> Csounders,
> 
> I'd like to take the opportunity to share this little tutorial I wrote with the community: it's a very easy way to set up a multi-channel audio/MIDI router to use Csound with Logic (or any other sequencer) through the OSX IAC driver and Soundflower.
> this is coming from a beginner, so it should really be accessible to everyone.
> you can find it here: http://www.csounds.com/node/1501
> 
> beside the obvious easy way of creating MIDI automations, the reason why I wanted this set up was to facilitate the mixing process. which leads me to the next topic:
> 
> as a beginner I find managing the gain stage in Csound to be a fairly complex process and I honestly think other people feel the same way about it.
> would it be possible to develop some sort of "mixer" opcode, or any other way that could make the whole process easier without pushing people like me to resort to external tools like Logic?
> 
> of course, if this is just me, there's nothing really to talk about here, but I do think other people feel the same.
> I'd like you to share your thoughts on the topic.
> 
> Andreas
> 
> Send bugs reports to the Sourceforge bug tracker
>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
> 
> 


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Hi Andreas,

There's also the mixer opcodes:

http://csounds.com/manual/html/MixerOpcodes.html

and the signal flow graph opcodes:

http://csounds.com/manual/html/SignalFlowGraphOpcodes.html

I also wrote an article about setting up a mixer setup that is similar
to hardware mixers or mixers you see in GUI environments:

http://www.csounds.com/journal/issue13/emulatingMidiBasedStudios.html

Hopefully one of those addresses your concerns!
steven


On Tue, Aug 30, 2011 at 2:52 PM, joachim heintz  wrote:
> hi andreas -
> i think there are different options for mixing in csound, for instance
> global audio variables, the chn opcodes, the zak patch system. did you
> try one of it and found it not suitable for your needs?
>        joachim
>
> Am 30.08.2011 16:08, schrieb andreas russo:
>> Csounders,
>>
>> I'd like to take the opportunity to share this little tutorial I wrote with the community: it's a very easy way to set up a multi-channel audio/MIDI router to use Csound with Logic (or any other sequencer) through the OSX IAC driver and Soundflower.
>> this is coming from a beginner, so it should really be accessible to everyone.
>> you can find it here: http://www.csounds.com/node/1501
>>
>> beside the obvious easy way of creating MIDI automations, the reason why I wanted this set up was to facilitate the mixing process. which leads me to the next topic:
>>
>> as a beginner I find managing the gain stage in Csound to be a fairly complex process and I honestly think other people feel the same way about it.
>> would it be possible to develop some sort of "mixer" opcode, or any other way that could make the whole process easier without pushing people like me to resort to external tools like Logic?
>>
>> of course, if this is just me, there's nothing really to talk about here, but I do think other people feel the same.
>> I'd like you to share your thoughts on the topic.
>>
>> Andreas
>>
>> Send bugs reports to the Sourceforge bug tracker
>>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>
>>
>
>
> Send bugs reports to the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Steven,

Thanks for pointer to these excellent links, and for the reminder of this wonderful article you wrote for the journal.

All are very helpful and I will point my students to them in the future.

Still, do you or any of the other developers think that there might be a way to add some sort of "anti-clip" option to Csound
(something under the hood, or some general set of controls from the QuteCsound GUI for instance that would allow one
to scale the overall levels on the fly - a "master fader" of some sorts... That would not require special instrument design or
the re-design of "classic" and "historic" orchestras?

Hopefully we can all discuss this in Hanover.

Best,

Dr. B.

On Aug 30, 2011, at 3:39 PM, Steven Yi wrote:

> Hi Andreas,
> 
> There's also the mixer opcodes:
> 
> http://csounds.com/manual/html/MixerOpcodes.html
> 
> and the signal flow graph opcodes:
> 
> http://csounds.com/manual/html/SignalFlowGraphOpcodes.html
> 
> I also wrote an article about setting up a mixer setup that is similar
> to hardware mixers or mixers you see in GUI environments:
> 
> http://www.csounds.com/journal/issue13/emulatingMidiBasedStudios.html
> 
> Hopefully one of those addresses your concerns!
> steven
> 
> 
> On Tue, Aug 30, 2011 at 2:52 PM, joachim heintz  wrote:
>> hi andreas -
>> i think there are different options for mixing in csound, for instance
>> global audio variables, the chn opcodes, the zak patch system. did you
>> try one of it and found it not suitable for your needs?
>>        joachim
>> 
>> Am 30.08.2011 16:08, schrieb andreas russo:
>>> Csounders,
>>> 
>>> I'd like to take the opportunity to share this little tutorial I wrote with the community: it's a very easy way to set up a multi-channel audio/MIDI router to use Csound with Logic (or any other sequencer) through the OSX IAC driver and Soundflower.
>>> this is coming from a beginner, so it should really be accessible to everyone.
>>> you can find it here: http://www.csounds.com/node/1501
>>> 
>>> beside the obvious easy way of creating MIDI automations, the reason why I wanted this set up was to facilitate the mixing process. which leads me to the next topic:
>>> 
>>> as a beginner I find managing the gain stage in Csound to be a fairly complex process and I honestly think other people feel the same way about it.
>>> would it be possible to develop some sort of "mixer" opcode, or any other way that could make the whole process easier without pushing people like me to resort to external tools like Logic?
>>> 
>>> of course, if this is just me, there's nothing really to talk about here, but I do think other people feel the same.
>>> I'd like you to share your thoughts on the topic.
>>> 
>>> Andreas
>>> 
>>> Send bugs reports to the Sourceforge bug tracker
>>>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>> Discussions of bugs and features can be posted here
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>> 
>>> 
>> 
>> 
>> Send bugs reports to the Sourceforge bug tracker
>>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>> 
>> 
> 
> 
> Send bugs reports to the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
> 



Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

This could be done with a delay line with a gain at the far end
controlled by a meter at the near end, in the form of a master output
fed by the signal flow graph opcodes. Instead of using the out
opcodes, instruments would use connect and outleta to send signals to
this dynamic limiter.

Hope this helps,
Mike

On Wed, Aug 31, 2011 at 1:41 AM, Dr. Richard Boulanger
 wrote:
> Steven,
>
> Thanks for pointer to these excellent links, and for the reminder of this wonderful article you wrote for the journal.
>
> All are very helpful and I will point my students to them in the future.
>
> Still, do you or any of the other developers think that there might be a way to add some sort of "anti-clip" option to Csound
> (something under the hood, or some general set of controls from the QuteCsound GUI for instance that would allow one
> to scale the overall levels on the fly - a "master fader" of some sorts... That would not require special instrument design or
> the re-design of "classic" and "historic" orchestras?
>
> Hopefully we can all discuss this in Hanover.
>
> Best,
>
> Dr. B.
>
> On Aug 30, 2011, at 3:39 PM, Steven Yi wrote:
>
>> Hi Andreas,
>>
>> There's also the mixer opcodes:
>>
>> http://csounds.com/manual/html/MixerOpcodes.html
>>
>> and the signal flow graph opcodes:
>>
>> http://csounds.com/manual/html/SignalFlowGraphOpcodes.html
>>
>> I also wrote an article about setting up a mixer setup that is similar
>> to hardware mixers or mixers you see in GUI environments:
>>
>> http://www.csounds.com/journal/issue13/emulatingMidiBasedStudios.html
>>
>> Hopefully one of those addresses your concerns!
>> steven
>>
>>
>> On Tue, Aug 30, 2011 at 2:52 PM, joachim heintz  wrote:
>>> hi andreas -
>>> i think there are different options for mixing in csound, for instance
>>> global audio variables, the chn opcodes, the zak patch system. did you
>>> try one of it and found it not suitable for your needs?
>>>        joachim
>>>
>>> Am 30.08.2011 16:08, schrieb andreas russo:
>>>> Csounders,
>>>>
>>>> I'd like to take the opportunity to share this little tutorial I wrote with the community: it's a very easy way to set up a multi-channel audio/MIDI router to use Csound with Logic (or any other sequencer) through the OSX IAC driver and Soundflower.
>>>> this is coming from a beginner, so it should really be accessible to everyone.
>>>> you can find it here: http://www.csounds.com/node/1501
>>>>
>>>> beside the obvious easy way of creating MIDI automations, the reason why I wanted this set up was to facilitate the mixing process. which leads me to the next topic:
>>>>
>>>> as a beginner I find managing the gain stage in Csound to be a fairly complex process and I honestly think other people feel the same way about it.
>>>> would it be possible to develop some sort of "mixer" opcode, or any other way that could make the whole process easier without pushing people like me to resort to external tools like Logic?
>>>>
>>>> of course, if this is just me, there's nothing really to talk about here, but I do think other people feel the same.
>>>> I'd like you to share your thoughts on the topic.
>>>>
>>>> Andreas
>>>>
>>>> Send bugs reports to the Sourceforge bug tracker
>>>>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>> Discussions of bugs and features can be posted here
>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>>
>>>>
>>>
>>>
>>> Send bugs reports to the Sourceforge bug tracker
>>>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>> Discussions of bugs and features can be posted here
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>
>>>
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>
>
>
>
> Send bugs reports to the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>



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


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

not sure if this is the best solution (and i'm assuming this is one feature QuteCsound didn't adopt?)
but MacCsound has[had] some reserved invalue/outvalue channels names for specific functionality.

one is a gain on the master output (done from csound output right before sending to the OS - so
it does not change rendering to file) so you could set a GUI slider to the "_Gain" channel to do what you were talking about.  
the nice thing is you could also do it from your orc too

=====
Reserved Control Channels
There are a number of pre-specified, "reserved" control channels for controlling MacCsound functionality via an i/o object or an instrument. They all begin with an underscore and are defined as follows:

_Offset - sets the score offset [ values in secs ]
_Play - starts/stops render [ 1=play, 0=stop ]
_Pause - toggles pause [ any value ] 
_Gain - output gain factor [ 0=silence, .5=1/2amp, 1=nochange, 2=2xamp, etc ] 
_Preset - performs all preset commands, recognized values are:
>0 - Number of Preset to Load
-1 - Save Settings as New Preset
-2 - Save Current Preset
-3 - Rename Current Preset
-4 - Delete Current Preset

See the "Reserved_Controls.csd" example file for more details. 



On Aug 30, 2011, at 10:41 PM, Dr. Richard Boulanger wrote:

> Steven,
> 
> Thanks for pointer to these excellent links, and for the reminder of this wonderful article you wrote for the journal.
> 
> All are very helpful and I will point my students to them in the future.
> 
> Still, do you or any of the other developers think that there might be a way to add some sort of "anti-clip" option to Csound
> (something under the hood, or some general set of controls from the QuteCsound GUI for instance that would allow one
> to scale the overall levels on the fly - a "master fader" of some sorts... That would not require special instrument design or
> the re-design of "classic" and "historic" orchestras?
> 
> Hopefully we can all discuss this in Hanover.
> 
> Best,
> 
> Dr. B.
> 
> On Aug 30, 2011, at 3:39 PM, Steven Yi wrote:
> 
>> Hi Andreas,
>> 
>> There's also the mixer opcodes:
>> 
>> http://csounds.com/manual/html/MixerOpcodes.html
>> 
>> and the signal flow graph opcodes:
>> 
>> http://csounds.com/manual/html/SignalFlowGraphOpcodes.html
>> 
>> I also wrote an article about setting up a mixer setup that is similar
>> to hardware mixers or mixers you see in GUI environments:
>> 
>> http://www.csounds.com/journal/issue13/emulatingMidiBasedStudios.html
>> 
>> Hopefully one of those addresses your concerns!
>> steven
>> 
>> 
>> On Tue, Aug 30, 2011 at 2:52 PM, joachim heintz  wrote:
>>> hi andreas -
>>> i think there are different options for mixing in csound, for instance
>>> global audio variables, the chn opcodes, the zak patch system. did you
>>> try one of it and found it not suitable for your needs?
>>>       joachim
>>> 
>>> Am 30.08.2011 16:08, schrieb andreas russo:
>>>> Csounders,
>>>> 
>>>> I'd like to take the opportunity to share this little tutorial I wrote with the community: it's a very easy way to set up a multi-channel audio/MIDI router to use Csound with Logic (or any other sequencer) through the OSX IAC driver and Soundflower.
>>>> this is coming from a beginner, so it should really be accessible to everyone.
>>>> you can find it here: http://www.csounds.com/node/1501
>>>> 
>>>> beside the obvious easy way of creating MIDI automations, the reason why I wanted this set up was to facilitate the mixing process. which leads me to the next topic:
>>>> 
>>>> as a beginner I find managing the gain stage in Csound to be a fairly complex process and I honestly think other people feel the same way about it.
>>>> would it be possible to develop some sort of "mixer" opcode, or any other way that could make the whole process easier without pushing people like me to resort to external tools like Logic?
>>>> 
>>>> of course, if this is just me, there's nothing really to talk about here, but I do think other people feel the same.
>>>> I'd like you to share your thoughts on the topic.
>>>> 
>>>> Andreas
>>>> 
>>>> Send bugs reports to the Sourceforge bug tracker
>>>>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>> Discussions of bugs and features can be posted here
>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>> 
>>>> 
>>> 
>>> 
>>> Send bugs reports to the Sourceforge bug tracker
>>>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>> Discussions of bugs and features can be posted here
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>> 
>>> 
>> 
>> 
>> Send bugs reports to the Sourceforge bug tracker
>>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>> 
> 
> 
> 
> Send bugs reports to the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
> 



Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

It would be great to add these to QuteCsound.  Would that be possible?

Thanks for the reminder/suggesion Matt.

Dr. B.


On Aug 31, 2011, at 1:50 PM, matt ingalls wrote:

> not sure if this is the best solution (and i'm assuming this is one feature QuteCsound didn't adopt?)
> but MacCsound has[had] some reserved invalue/outvalue channels names for specific functionality.
> 
> one is a gain on the master output (done from csound output right before sending to the OS - so
> it does not change rendering to file) so you could set a GUI slider to the "_Gain" channel to do what you were talking about.  
> the nice thing is you could also do it from your orc too
> 
> =====
> Reserved Control Channels
> There are a number of pre-specified, "reserved" control channels for controlling MacCsound functionality via an i/o object or an instrument. They all begin with an underscore and are defined as follows:
> 
> _Offset - sets the score offset [ values in secs ]
> _Play - starts/stops render [ 1=play, 0=stop ]
> _Pause - toggles pause [ any value ] 
> _Gain - output gain factor [ 0=silence, .5=1/2amp, 1=nochange, 2=2xamp, etc ] 
> _Preset - performs all preset commands, recognized values are:
>> 0 - Number of Preset to Load
> -1 - Save Settings as New Preset
> -2 - Save Current Preset
> -3 - Rename Current Preset
> -4 - Delete Current Preset
> 
> See the "Reserved_Controls.csd" example file for more details. 
> 
> 
> 
> On Aug 30, 2011, at 10:41 PM, Dr. Richard Boulanger wrote:
> 
>> Steven,
>> 
>> Thanks for pointer to these excellent links, and for the reminder of this wonderful article you wrote for the journal.
>> 
>> All are very helpful and I will point my students to them in the future.
>> 
>> Still, do you or any of the other developers think that there might be a way to add some sort of "anti-clip" option to Csound
>> (something under the hood, or some general set of controls from the QuteCsound GUI for instance that would allow one
>> to scale the overall levels on the fly - a "master fader" of some sorts... That would not require special instrument design or
>> the re-design of "classic" and "historic" orchestras?
>> 
>> Hopefully we can all discuss this in Hanover.
>> 
>> Best,
>> 
>> Dr. B.
>> 
>> On Aug 30, 2011, at 3:39 PM, Steven Yi wrote:
>> 
>>> Hi Andreas,
>>> 
>>> There's also the mixer opcodes:
>>> 
>>> http://csounds.com/manual/html/MixerOpcodes.html
>>> 
>>> and the signal flow graph opcodes:
>>> 
>>> http://csounds.com/manual/html/SignalFlowGraphOpcodes.html
>>> 
>>> I also wrote an article about setting up a mixer setup that is similar
>>> to hardware mixers or mixers you see in GUI environments:
>>> 
>>> http://www.csounds.com/journal/issue13/emulatingMidiBasedStudios.html
>>> 
>>> Hopefully one of those addresses your concerns!
>>> steven
>>> 
>>> 
>>> On Tue, Aug 30, 2011 at 2:52 PM, joachim heintz  wrote:
>>>> hi andreas -
>>>> i think there are different options for mixing in csound, for instance
>>>> global audio variables, the chn opcodes, the zak patch system. did you
>>>> try one of it and found it not suitable for your needs?
>>>>      joachim
>>>> 
>>>> Am 30.08.2011 16:08, schrieb andreas russo:
>>>>> Csounders,
>>>>> 
>>>>> I'd like to take the opportunity to share this little tutorial I wrote with the community: it's a very easy way to set up a multi-channel audio/MIDI router to use Csound with Logic (or any other sequencer) through the OSX IAC driver and Soundflower.
>>>>> this is coming from a beginner, so it should really be accessible to everyone.
>>>>> you can find it here: http://www.csounds.com/node/1501
>>>>> 
>>>>> beside the obvious easy way of creating MIDI automations, the reason why I wanted this set up was to facilitate the mixing process. which leads me to the next topic:
>>>>> 
>>>>> as a beginner I find managing the gain stage in Csound to be a fairly complex process and I honestly think other people feel the same way about it.
>>>>> would it be possible to develop some sort of "mixer" opcode, or any other way that could make the whole process easier without pushing people like me to resort to external tools like Logic?
>>>>> 
>>>>> of course, if this is just me, there's nothing really to talk about here, but I do think other people feel the same.
>>>>> I'd like you to share your thoughts on the topic.
>>>>> 
>>>>> Andreas
>>>>> 
>>>>> Send bugs reports to the Sourceforge bug tracker
>>>>>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>>> Discussions of bugs and features can be posted here
>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>>> 
>>>>> 
>>>> 
>>>> 
>>>> Send bugs reports to the Sourceforge bug tracker
>>>>          https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>> Discussions of bugs and features can be posted here
>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>> 
>>>> 
>>> 
>>> 
>>> Send bugs reports to the Sourceforge bug tracker
>>>          https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>> Discussions of bugs and features can be posted here
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>> 
>> 
>> 
>> 
>> Send bugs reports to the Sourceforge bug tracker
>>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>> 
> 
> 
> 
> Send bugs reports to the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
> 



Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Hi,

I've implemented some of them, but _Offset and _Gain are not there...

Cheers,
Andres

On Thu, Sep 1, 2011 at 3:59 AM, Dr. Richard Boulanger
 wrote:
> It would be great to add these to QuteCsound.  Would that be possible?
>
> Thanks for the reminder/suggesion Matt.
>
> Dr. B.
>
>
> On Aug 31, 2011, at 1:50 PM, matt ingalls wrote:
>
>> not sure if this is the best solution (and i'm assuming this is one feature QuteCsound didn't adopt?)
>> but MacCsound has[had] some reserved invalue/outvalue channels names for specific functionality.
>>
>> one is a gain on the master output (done from csound output right before sending to the OS - so
>> it does not change rendering to file) so you could set a GUI slider to the "_Gain" channel to do what you were talking about.
>> the nice thing is you could also do it from your orc too
>>
>> =====
>> Reserved Control Channels
>> There are a number of pre-specified, "reserved" control channels for controlling MacCsound functionality via an i/o object or an instrument. They all begin with an underscore and are defined as follows:
>>
>> _Offset - sets the score offset [ values in secs ]
>> _Play - starts/stops render [ 1=play, 0=stop ]
>> _Pause - toggles pause [ any value ]
>> _Gain - output gain factor [ 0=silence, .5=1/2amp, 1=nochange, 2=2xamp, etc ]
>> _Preset - performs all preset commands, recognized values are:
>>> 0 - Number of Preset to Load
>> -1 - Save Settings as New Preset
>> -2 - Save Current Preset
>> -3 - Rename Current Preset
>> -4 - Delete Current Preset
>>
>> See the "Reserved_Controls.csd" example file for more details.
>>
>>
>>
>> On Aug 30, 2011, at 10:41 PM, Dr. Richard Boulanger wrote:
>>
>>> Steven,
>>>
>>> Thanks for pointer to these excellent links, and for the reminder of this wonderful article you wrote for the journal.
>>>
>>> All are very helpful and I will point my students to them in the future.
>>>
>>> Still, do you or any of the other developers think that there might be a way to add some sort of "anti-clip" option to Csound
>>> (something under the hood, or some general set of controls from the QuteCsound GUI for instance that would allow one
>>> to scale the overall levels on the fly - a "master fader" of some sorts... That would not require special instrument design or
>>> the re-design of "classic" and "historic" orchestras?
>>>
>>> Hopefully we can all discuss this in Hanover.
>>>
>>> Best,
>>>
>>> Dr. B.
>>>
>>> On Aug 30, 2011, at 3:39 PM, Steven Yi wrote:
>>>
>>>> Hi Andreas,
>>>>
>>>> There's also the mixer opcodes:
>>>>
>>>> http://csounds.com/manual/html/MixerOpcodes.html
>>>>
>>>> and the signal flow graph opcodes:
>>>>
>>>> http://csounds.com/manual/html/SignalFlowGraphOpcodes.html
>>>>
>>>> I also wrote an article about setting up a mixer setup that is similar
>>>> to hardware mixers or mixers you see in GUI environments:
>>>>
>>>> http://www.csounds.com/journal/issue13/emulatingMidiBasedStudios.html
>>>>
>>>> Hopefully one of those addresses your concerns!
>>>> steven
>>>>
>>>>
>>>> On Tue, Aug 30, 2011 at 2:52 PM, joachim heintz  wrote:
>>>>> hi andreas -
>>>>> i think there are different options for mixing in csound, for instance
>>>>> global audio variables, the chn opcodes, the zak patch system. did you
>>>>> try one of it and found it not suitable for your needs?
>>>>>      joachim
>>>>>
>>>>> Am 30.08.2011 16:08, schrieb andreas russo:
>>>>>> Csounders,
>>>>>>
>>>>>> I'd like to take the opportunity to share this little tutorial I wrote with the community: it's a very easy way to set up a multi-channel audio/MIDI router to use Csound with Logic (or any other sequencer) through the OSX IAC driver and Soundflower.
>>>>>> this is coming from a beginner, so it should really be accessible to everyone.
>>>>>> you can find it here: http://www.csounds.com/node/1501
>>>>>>
>>>>>> beside the obvious easy way of creating MIDI automations, the reason why I wanted this set up was to facilitate the mixing process. which leads me to the next topic:
>>>>>>
>>>>>> as a beginner I find managing the gain stage in Csound to be a fairly complex process and I honestly think other people feel the same way about it.
>>>>>> would it be possible to develop some sort of "mixer" opcode, or any other way that could make the whole process easier without pushing people like me to resort to external tools like Logic?
>>>>>>
>>>>>> of course, if this is just me, there's nothing really to talk about here, but I do think other people feel the same.
>>>>>> I'd like you to share your thoughts on the topic.
>>>>>>
>>>>>> Andreas
>>>>>>
>>>>>> Send bugs reports to the Sourceforge bug tracker
>>>>>>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>>>> Discussions of bugs and features can be posted here
>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> Send bugs reports to the Sourceforge bug tracker
>>>>>          https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>>> Discussions of bugs and features can be posted here
>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>>>
>>>>>
>>>>
>>>>
>>>> Send bugs reports to the Sourceforge bug tracker
>>>>          https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>> Discussions of bugs and features can be posted here
>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>>
>>>
>>>
>>>
>>> Send bugs reports to the Sourceforge bug tracker
>>>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>> Discussions of bugs and features can be posted here
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>
>>
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>
>
>


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

thanks all,
I wasn't aware of all these interesting features.
I'm going to explore them all.

andreas

On Sep 1, 2011, at 08:22, Andres Cabrera wrote:

> Hi,
> 
> I've implemented some of them, but _Offset and _Gain are not there...
> 
> Cheers,
> Andres
> 
> On Thu, Sep 1, 2011 at 3:59 AM, Dr. Richard Boulanger
>  wrote:
>> It would be great to add these to QuteCsound.  Would that be possible?
>> 
>> Thanks for the reminder/suggesion Matt.
>> 
>> Dr. B.
>> 
>> 
>> On Aug 31, 2011, at 1:50 PM, matt ingalls wrote:
>> 
>>> not sure if this is the best solution (and i'm assuming this is one feature QuteCsound didn't adopt?)
>>> but MacCsound has[had] some reserved invalue/outvalue channels names for specific functionality.
>>> 
>>> one is a gain on the master output (done from csound output right before sending to the OS - so
>>> it does not change rendering to file) so you could set a GUI slider to the "_Gain" channel to do what you were talking about.
>>> the nice thing is you could also do it from your orc too
>>> 
>>> =====
>>> Reserved Control Channels
>>> There are a number of pre-specified, "reserved" control channels for controlling MacCsound functionality via an i/o object or an instrument. They all begin with an underscore and are defined as follows:
>>> 
>>> _Offset - sets the score offset [ values in secs ]
>>> _Play - starts/stops render [ 1=play, 0=stop ]
>>> _Pause - toggles pause [ any value ]
>>> _Gain - output gain factor [ 0=silence, .5=1/2amp, 1=nochange, 2=2xamp, etc ]
>>> _Preset - performs all preset commands, recognized values are:
>>>> 0 - Number of Preset to Load
>>> -1 - Save Settings as New Preset
>>> -2 - Save Current Preset
>>> -3 - Rename Current Preset
>>> -4 - Delete Current Preset
>>> 
>>> See the "Reserved_Controls.csd" example file for more details.
>>> 
>>> 
>>> 
>>> On Aug 30, 2011, at 10:41 PM, Dr. Richard Boulanger wrote:
>>> 
>>>> Steven,
>>>> 
>>>> Thanks for pointer to these excellent links, and for the reminder of this wonderful article you wrote for the journal.
>>>> 
>>>> All are very helpful and I will point my students to them in the future.
>>>> 
>>>> Still, do you or any of the other developers think that there might be a way to add some sort of "anti-clip" option to Csound
>>>> (something under the hood, or some general set of controls from the QuteCsound GUI for instance that would allow one
>>>> to scale the overall levels on the fly - a "master fader" of some sorts... That would not require special instrument design or
>>>> the re-design of "classic" and "historic" orchestras?
>>>> 
>>>> Hopefully we can all discuss this in Hanover.
>>>> 
>>>> Best,
>>>> 
>>>> Dr. B.
>>>> 
>>>> On Aug 30, 2011, at 3:39 PM, Steven Yi wrote:
>>>> 
>>>>> Hi Andreas,
>>>>> 
>>>>> There's also the mixer opcodes:
>>>>> 
>>>>> http://csounds.com/manual/html/MixerOpcodes.html
>>>>> 
>>>>> and the signal flow graph opcodes:
>>>>> 
>>>>> http://csounds.com/manual/html/SignalFlowGraphOpcodes.html
>>>>> 
>>>>> I also wrote an article about setting up a mixer setup that is similar
>>>>> to hardware mixers or mixers you see in GUI environments:
>>>>> 
>>>>> http://www.csounds.com/journal/issue13/emulatingMidiBasedStudios.html
>>>>> 
>>>>> Hopefully one of those addresses your concerns!
>>>>> steven
>>>>> 
>>>>> 
>>>>> On Tue, Aug 30, 2011 at 2:52 PM, joachim heintz  wrote:
>>>>>> hi andreas -
>>>>>> i think there are different options for mixing in csound, for instance
>>>>>> global audio variables, the chn opcodes, the zak patch system. did you
>>>>>> try one of it and found it not suitable for your needs?
>>>>>>      joachim
>>>>>> 
>>>>>> Am 30.08.2011 16:08, schrieb andreas russo:
>>>>>>> Csounders,
>>>>>>> 
>>>>>>> I'd like to take the opportunity to share this little tutorial I wrote with the community: it's a very easy way to set up a multi-channel audio/MIDI router to use Csound with Logic (or any other sequencer) through the OSX IAC driver and Soundflower.
>>>>>>> this is coming from a beginner, so it should really be accessible to everyone.
>>>>>>> you can find it here: http://www.csounds.com/node/1501
>>>>>>> 
>>>>>>> beside the obvious easy way of creating MIDI automations, the reason why I wanted this set up was to facilitate the mixing process. which leads me to the next topic:
>>>>>>> 
>>>>>>> as a beginner I find managing the gain stage in Csound to be a fairly complex process and I honestly think other people feel the same way about it.
>>>>>>> would it be possible to develop some sort of "mixer" opcode, or any other way that could make the whole process easier without pushing people like me to resort to external tools like Logic?
>>>>>>> 
>>>>>>> of course, if this is just me, there's nothing really to talk about here, but I do think other people feel the same.
>>>>>>> I'd like you to share your thoughts on the topic.
>>>>>>> 
>>>>>>> Andreas
>>>>>>> 
>>>>>>> Send bugs reports to the Sourceforge bug tracker
>>>>>>>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>>>>> Discussions of bugs and features can be posted here
>>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> Send bugs reports to the Sourceforge bug tracker
>>>>>>          https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>>>> Discussions of bugs and features can be posted here
>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>>>> 
>>>>>> 
>>>>> 
>>>>> 
>>>>> Send bugs reports to the Sourceforge bug tracker
>>>>>          https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>>> Discussions of bugs and features can be posted here
>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>>> 
>>>> 
>>>> 
>>>> 
>>>> Send bugs reports to the Sourceforge bug tracker
>>>>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>> Discussions of bugs and features can be posted here
>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>> 
>>> 
>>> 
>>> 
>>> Send bugs reports to the Sourceforge bug tracker
>>>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>> Discussions of bugs and features can be posted here
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>> 
>> 
>> 
> 
> 
> Send bugs reports to the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
> 



Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"