Is there a way to define a Master clock variable, that I can use both in
tempo statements and for example the timing of a LFO?
I have tried to define a global variable, but that didn´t work.
gitempo  = 120
I then put in a tempo statement in the score: t 0 gitempo, but Csound will
not accept that. 
How would you solve this? It is probably very easy, but I can´t figure it
out. 
I mostly want to use it for setting the tempo and making tempo-synced LFO:s,
and only have to change the tempo in one place. 



--
View this message in context: http://csound.1045644.n5.nabble.com/Master-clock-tp5726664.html
Sent from the Csound - General mailing list archive at Nabble.com.

i am not sure if it is easy, as Csound has actually two different 
languages in one csd document: the orchestra language, and the score 
language. this is the reason why t 0 gitempo does not work.

depending on what you want to do, you could consider to include your 
score events in the orchestra (via event or scoreline) -- in this way 
you can do everything in the orc language.

the use of macros could also be a (dirty) solution. see below for a 
simple example. but actually it is a fake, as BEAT means something 
different in orc and sco, and has by this reason to be defined twice in 
the options.

perhaps someone else has a better idea ...

best -

	joachim




--omacro:BEAT=120 --smacro:BEAT=120



instr 1
prints "Beat = %f\n", $BEAT
endin



t 0 $BEAT.
i 1 0 1
i 1 + .
i 1 + .
i 1 + .
i 1 + .






Am 14.08.2013 11:28, schrieb orebronerd:
> Is there a way to define a Master clock variable, that I can use both in
> tempo statements and for example the timing of a LFO?
> I have tried to define a global variable, but that didn´t work.
> gitempo  = 120
> I then put in a tempo statement in the score: t 0 gitempo, but Csound will
> not accept that.
> How would you solve this? It is probably very easy, but I can´t figure it
> out.
> I mostly want to use it for setting the tempo and making tempo-synced LFO:s,
> and only have to change the tempo in one place.
>
>
>
> --
> View this message in context: http://csound.1045644.n5.nabble.com/Master-clock-tp5726664.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
> Send bugs reports to the Sourceforge bug trackers
> csound6:
>              https://sourceforge.net/p/csound/tickets/
> csound5:
>              https://sourceforge.net/p/csound/bugs/
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>
>

Thank you for your swift reply. A bit annoying that you can´t use the same
variables in instrument and score, but you can´t have it all. I have been
using Csound now for some years, and it is truly a fantastic program.
 



--
View this message in context: http://csound.1045644.n5.nabble.com/Master-clock-tp5726664p5726716.html
Sent from the Csound - General mailing list archive at Nabble.com.

They are different languages. If you want, you can use only the orchestra  language and launch events from there.
On 15 Aug 2013, at 06:44, orebronerd wrote:

> Thank you for your swift reply. A bit annoying that you can´t use the same
> variables in instrument and score, but you can´t have it all. I have been
> using Csound now for some years, and it is truly a fantastic program.
> 
> 
> 
> 
> --
> View this message in context: http://csound.1045644.n5.nabble.com/Master-clock-tp5726664p5726716.html
> Sent from the Csound - General mailing list archive at Nabble.com.
> 
> 
> Send bugs reports to the Sourceforge bug trackers
> csound6:
>            https://sourceforge.net/p/csound/tickets/
> csound5:
>            https://sourceforge.net/p/csound/bugs/
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
> 
> 

Dr Victor Lazzarini
Senior Lecturer
Dept. of Music
NUI Maynooth Ireland
tel.: +353 1 708 3545
Victor dot Lazzarini AT nuim dot ie

Thank you for the reply. Yes, I realize that I can use events in the
instrument part, but it is a bit cumbersome if you write large scores (well,
not that large :-) ), so I think I will stick to manually changing tempo. If
I use a variable for the instrument part, and change in the score with a t
statement, I only need to change in 2 places.



--
View this message in context: http://csound.1045644.n5.nabble.com/Master-clock-tp5726664p5726727.html
Sent from the Csound - General mailing list archive at Nabble.com.

Just out of personal curiosity: couldn't you set a score macro from an orchestra? If not, could that be implemented?

Regards,
Anders



15 aug 2013 kl. 12:46 skrev orebronerd :

> Thank you for the reply. Yes, I realize that I can use events in the
> instrument part, but it is a bit cumbersome if you write large scores (well,
> not that large :-) ), so I think I will stick to manually changing tempo. If
> I use a variable for the instrument part, and change in the score with a t
> statement, I only need to change in 2 places.
> 
> 
> 
> --
> View this message in context: http://csound.1045644.n5.nabble.com/Master-clock-tp5726664p5726727.html
> Sent from the Csound - General mailing list archive at Nabble.com.
> 
> 
> Send bugs reports to the Sourceforge bug trackers
> csound6:
>            https://sourceforge.net/p/csound/tickets/
> csound5:
>            https://sourceforge.net/p/csound/bugs/
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
> 
> 

yes, this sounds easy enough.

just to note that there is also readf(i) so that you could read lines 
from an external file, tranform them to strings, and send via the 
scoreline opcode as score events.

	joachim


Am 15.08.2013 12:46, schrieb orebronerd:
> Thank you for the reply. Yes, I realize that I can use events in the
> instrument part, but it is a bit cumbersome if you write large scores (well,
> not that large :-) ), so I think I will stick to manually changing tempo. If
> I use a variable for the instrument part, and change in the score with a t
> statement, I only need to change in 2 places.
>
>
>
> --
> View this message in context: http://csound.1045644.n5.nabble.com/Master-clock-tp5726664p5726727.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
> Send bugs reports to the Sourceforge bug trackers
> csound6:
>              https://sourceforge.net/p/csound/tickets/
> csound5:
>              https://sourceforge.net/p/csound/bugs/
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>
>

I don't think that would be easy to implement. However, you could write shared info in a file and then #include it from both the orc and sco.

What about just sending the tempo event from the instrument part and 
doing the rest of the score as usual? Just an idea, haven't tried that 
yet...

Best,
Jana


Am 15.08.2013 12:46, schrieb orebronerd:
> Thank you for the reply. Yes, I realize that I can use events in the
> instrument part, but it is a bit cumbersome if you write large scores (well,
> not that large :-) ), so I think I will stick to manually changing tempo. If
> I use a variable for the instrument part, and change in the score with a t
> statement, I only need to change in 2 places.
>
>
>
> --
> View this message in context: http://csound.1045644.n5.nabble.com/Master-clock-tp5726664p5726727.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
> Send bugs reports to the Sourceforge bug trackers
> csound6:
>              https://sourceforge.net/p/csound/tickets/
> csound5:
>              https://sourceforge.net/p/csound/bugs/
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>

i think you cannot do that (sending the tempo event from the instrument 
part), can you?
best -
	joachim


Am 15.08.2013 19:04, schrieb Jana Hübenthal:
>
> What about just sending the tempo event from the instrument part and
> doing the rest of the score as usual? Just an idea, haven't tried that
> yet...
>
> Best,
> Jana
>
>
> Am 15.08.2013 12:46, schrieb orebronerd:
>> Thank you for the reply. Yes, I realize that I can use events in the
>> instrument part, but it is a bit cumbersome if you write large scores
>> (well,
>> not that large :-) ), so I think I will stick to manually changing
>> tempo. If
>> I use a variable for the instrument part, and change in the score with
>> a t
>> statement, I only need to change in 2 places.
>>
>>
>>
>> --
>> View this message in context:
>> http://csound.1045644.n5.nabble.com/Master-clock-tp5726664p5726727.html
>> Sent from the Csound - General mailing list archive at Nabble.com.
>>
>>
>> Send bugs reports to the Sourceforge bug trackers
>> csound6:
>>              https://sourceforge.net/p/csound/tickets/
>> csound5:
>>              https://sourceforge.net/p/csound/bugs/
>> 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 trackers
> csound6:
>             https://sourceforge.net/p/csound/tickets/
> csound5:
>             https://sourceforge.net/p/csound/bugs/
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>
>
>

Don't know...  the manual says "usual an 'e', 'i' or 'f'" at the "event" 
opcode, but ist seems not be limited to that. By the way, there's also a 
"tempo" opcode and "tempoval" as its counterpart. Never used them, too...

Best,
Jana


Am 15.08.2013 19:14, schrieb joachim heintz:
> i think you cannot do that (sending the tempo event from the 
> instrument part), can you?
> best -
>     joachim
>
>
> Am 15.08.2013 19:04, schrieb Jana Hübenthal:
>>
>> What about just sending the tempo event from the instrument part and
>> doing the rest of the score as usual? Just an idea, haven't tried that
>> yet...
>>
>> Best,
>> Jana
>>
>>
>> Am 15.08.2013 12:46, schrieb orebronerd:
>>> Thank you for the reply. Yes, I realize that I can use events in the
>>> instrument part, but it is a bit cumbersome if you write large scores
>>> (well,
>>> not that large :-) ), so I think I will stick to manually changing
>>> tempo. If
>>> I use a variable for the instrument part, and change in the score with
>>> a t
>>> statement, I only need to change in 2 places.
>>>
>>>
>>>
>>> -- 
>>> View this message in context:
>>> http://csound.1045644.n5.nabble.com/Master-clock-tp5726664p5726727.html
>>> Sent from the Csound - General mailing list archive at Nabble.com.
>>>
>>>
>>> Send bugs reports to the Sourceforge bug trackers
>>> csound6:
>>>              https://sourceforge.net/p/csound/tickets/
>>> csound5:
>>>              https://sourceforge.net/p/csound/bugs/
>>> 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 trackers
>> csound6:
>>             https://sourceforge.net/p/csound/tickets/
>> csound5:
>>             https://sourceforge.net/p/csound/bugs/
>> 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 trackers
> csound6:
>            https://sourceforge.net/p/csound/tickets/
> csound5:
>            https://sourceforge.net/p/csound/bugs/
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body 
> "unsubscribe csound"
>
>

this was worth a test. calling instr 1 with the line
event_i "t", 0, 120
returns an error:
INIT ERROR in instr 1: event: param 1 must be "a", "i", "q", "f", or "e"
	event_i	"t"	0	120	

but tempo is a good idea. i get somehow funny results at the transition 
between the two tempos, though (two notes together):



-odac -t60


sr = 44100
ksmps = 32
0dbfs = 1
nchnls = 1

seed 0

instr 1 ;set tempo statement
tempo 120, 60
turnoff
endin

instr 10
aImp mpulse 1, p3
iFreq random 400, 1000
iQ random 500, 1000
aTone mode aImp, iFreq, iQ
out aTone
endin



i 10 0 1
i 10 1 1
i 10 2 1
i 1 3 1
i 10 3 1
i 10 4 1
i 10 5 1
i 10 6 1
i 10 7 1
i 10 8 1



	joachim


Am 15.08.2013 19:49, schrieb Jana Hübenthal:
>
> Don't know...  the manual says "usual an 'e', 'i' or 'f'" at the "event"
> opcode, but ist seems not be limited to that. By the way, there's also a
> "tempo" opcode and "tempoval" as its counterpart. Never used them, too...
>
> Best,
> Jana
>
>
> Am 15.08.2013 19:14, schrieb joachim heintz:
>> i think you cannot do that (sending the tempo event from the
>> instrument part), can you?
>> best -
>>     joachim
>>
>>
>> Am 15.08.2013 19:04, schrieb Jana Hübenthal:
>>>
>>> What about just sending the tempo event from the instrument part and
>>> doing the rest of the score as usual? Just an idea, haven't tried that
>>> yet...
>>>
>>> Best,
>>> Jana
>>>
>>>
>>> Am 15.08.2013 12:46, schrieb orebronerd:
>>>> Thank you for the reply. Yes, I realize that I can use events in the
>>>> instrument part, but it is a bit cumbersome if you write large scores
>>>> (well,
>>>> not that large :-) ), so I think I will stick to manually changing
>>>> tempo. If
>>>> I use a variable for the instrument part, and change in the score with
>>>> a t
>>>> statement, I only need to change in 2 places.
>>>>
>>>>
>>>>
>>>> --
>>>> View this message in context:
>>>> http://csound.1045644.n5.nabble.com/Master-clock-tp5726664p5726727.html
>>>> Sent from the Csound - General mailing list archive at Nabble.com.
>>>>
>>>>
>>>> Send bugs reports to the Sourceforge bug trackers
>>>> csound6:
>>>>              https://sourceforge.net/p/csound/tickets/
>>>> csound5:
>>>>              https://sourceforge.net/p/csound/bugs/
>>>> 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 trackers
>>> csound6:
>>>             https://sourceforge.net/p/csound/tickets/
>>> csound5:
>>>             https://sourceforge.net/p/csound/bugs/
>>> 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 trackers
>> csound6:
>>            https://sourceforge.net/p/csound/tickets/
>> csound5:
>>            https://sourceforge.net/p/csound/bugs/
>> 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 trackers
> csound6:
>             https://sourceforge.net/p/csound/tickets/
> csound5:
>             https://sourceforge.net/p/csound/bugs/
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>
>
>

The thing to note about Csound's t-statement is that it is used when
SCO is processed.  The score is read in, then processed with
t-statements, then runtime happens.  At runtime, the tempo information
is no longer around, i.e. it is not stored anywhere.  Therefore, any
runtime t-statement really has no effect.

Csound *could* be modified to apply t-statements at runtime instead of
parse-time.  So far, what I see in possible ramifications:

1. Run-time performance may be impacted. Not sure by how much; would
need testing and measurement.

2. Run-time score parsing semantics would need clarification.  Up
until now, new score is processed at realtime (tempo 60).  It might be
something that can be configured, but it would need to default to no
tempo processing to maintain backwards compatibility with older
systems.

Perhaps others can chime in if they see other possible ramifications.


On Thu, Aug 15, 2013 at 3:22 PM, joachim heintz  wrote:
> this was worth a test. calling instr 1 with the line
> event_i "t", 0, 120
> returns an error:
> INIT ERROR in instr 1: event: param 1 must be "a", "i", "q", "f", or "e"
>         event_i "t"     0       120
>
> but tempo is a good idea. i get somehow funny results at the transition
> between the two tempos, though (two notes together):
>
> 
> 
> -odac -t60
> 
> 
> sr = 44100
> ksmps = 32
> 0dbfs = 1
> nchnls = 1
>
> seed 0
>
> instr 1 ;set tempo statement
> tempo 120, 60
> turnoff
> endin
>
> instr 10
> aImp mpulse 1, p3
> iFreq random 400, 1000
> iQ random 500, 1000
> aTone mode aImp, iFreq, iQ
> out aTone
> endin
>
> 
> 
> i 10 0 1
> i 10 1 1
> i 10 2 1
> i 1 3 1
> i 10 3 1
> i 10 4 1
> i 10 5 1
> i 10 6 1
> i 10 7 1
> i 10 8 1
> 
> 
>
>         joachim
>
>
> Am 15.08.2013 19:49, schrieb Jana Hübenthal:
>
>>
>> Don't know...  the manual says "usual an 'e', 'i' or 'f'" at the "event"
>> opcode, but ist seems not be limited to that. By the way, there's also a
>> "tempo" opcode and "tempoval" as its counterpart. Never used them, too...
>>
>> Best,
>> Jana
>>
>>
>> Am 15.08.2013 19:14, schrieb joachim heintz:
>>>
>>> i think you cannot do that (sending the tempo event from the
>>> instrument part), can you?
>>> best -
>>>     joachim
>>>
>>>
>>> Am 15.08.2013 19:04, schrieb Jana Hübenthal:
>>>>
>>>>
>>>> What about just sending the tempo event from the instrument part and
>>>> doing the rest of the score as usual? Just an idea, haven't tried that
>>>> yet...
>>>>
>>>> Best,
>>>> Jana
>>>>
>>>>
>>>> Am 15.08.2013 12:46, schrieb orebronerd:
>>>>>
>>>>> Thank you for the reply. Yes, I realize that I can use events in the
>>>>> instrument part, but it is a bit cumbersome if you write large scores
>>>>> (well,
>>>>> not that large :-) ), so I think I will stick to manually changing
>>>>> tempo. If
>>>>> I use a variable for the instrument part, and change in the score with
>>>>> a t
>>>>> statement, I only need to change in 2 places.
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> View this message in context:
>>>>> http://csound.1045644.n5.nabble.com/Master-clock-tp5726664p5726727.html
>>>>> Sent from the Csound - General mailing list archive at Nabble.com.
>>>>>
>>>>>
>>>>> Send bugs reports to the Sourceforge bug trackers
>>>>> csound6:
>>>>>              https://sourceforge.net/p/csound/tickets/
>>>>> csound5:
>>>>>              https://sourceforge.net/p/csound/bugs/
>>>>> 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 trackers
>>>> csound6:
>>>>             https://sourceforge.net/p/csound/tickets/
>>>> csound5:
>>>>             https://sourceforge.net/p/csound/bugs/
>>>> 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 trackers
>>> csound6:
>>>            https://sourceforge.net/p/csound/tickets/
>>> csound5:
>>>            https://sourceforge.net/p/csound/bugs/
>>> 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 trackers
>> csound6:
>>             https://sourceforge.net/p/csound/tickets/
>> csound5:
>>             https://sourceforge.net/p/csound/bugs/
>> 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 trackers
> csound6:
>            https://sourceforge.net/p/csound/tickets/
> csound5:
>            https://sourceforge.net/p/csound/bugs/
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>
>

> I've been pondering on whether a sequencer opcode might be useful:
> 
> ihandle seq kbpm, knum_beats, ksync, knum_divs, ktrig_instrument [, kp3,
> ... , kpN]
> 
> ksync - to force hard sync with another seq
> knum_divs - divisions in beat
> ktrig_instrument - instrument to be triggered (could also take array or
> ftable)
> kpX - pfield for note (could also take array or ftable)
> 
> Each seq instance could be made available to the API, and maybe created
> from it too. Maybe
> with some additions (duration and separation instead of tempo) a seq
> instance could be
> spawned by the score (and then it could be controlled/altered in realtime
> while performance is
> running).

I like this idea a lot. The fact that you're suggesting knum_divs and
starting the p-fields with p3 suggests, however, that you're thinking of a
rigid step sequencer implementation, with one note per step -- rather like
an old Tangerine Dream analog sequencer. Creating a complex rhythm (or
including chords) with this implementation would be difficult, unless I'm
missing something obvious (as I sometimes do).

--JA



--
View this message in context: http://csound.1045644.n5.nabble.com/Master-clock-tp5726664p5727311.html
Sent from the Csound - General mailing list archive at Nabble.com.

Hi,

Andrés's idea for sequencer like opcode would work definitely in some 
situations, for me it has been most difficult to calculate the beats' 
durations in seconds when there is a accelrando, let' say in the score:

t 0 60 6 120

And suppose I want to generate an event in the orchestra of every beat of the 
accelerando. I can't do just

ktempo line 60,6,120

since the progression is not linear nor exactyl exponential and the time 
duration of the 6 accelrating beats is not 6 seconds but something less.

If there were equivalent for tempo score statement for use in orchestra (to be 
calculated in instr 0, why not doubleing the score statement), I mean if the 
orcestra could know where any beat in a given tempo is, would be great.

I know that there are equations by Istvan Varga and Steven Yi to calculate it, 
but something easier would be very welcome (for example for generating dynamic 
click-tracks).

best!
tarmo


On Monday 02 September 2013 10:04:09 Jim Aikin wrote:
> > I've been pondering on whether a sequencer opcode might be useful:
> > 
> > ihandle seq kbpm, knum_beats, ksync, knum_divs, ktrig_instrument [, kp3,
> > ... , kpN]
> > 
> > ksync - to force hard sync with another seq
> > knum_divs - divisions in beat
> > ktrig_instrument - instrument to be triggered (could also take array or
> > ftable)
> > kpX - pfield for note (could also take array or ftable)
> > 
> > Each seq instance could be made available to the API, and maybe created
> > from it too. Maybe
> > with some additions (duration and separation instead of tempo) a seq
> > instance could be
> > spawned by the score (and then it could be controlled/altered in realtime
> > while performance is
> > running).
> 
> I like this idea a lot. The fact that you're suggesting knum_divs and
> starting the p-fields with p3 suggests, however, that you're thinking of a
> rigid step sequencer implementation, with one note per step -- rather like
> an old Tangerine Dream analog sequencer. Creating a complex rhythm (or
> including chords) with this implementation would be difficult, unless I'm
> missing something obvious (as I sometimes do).
> 
> --JA
> 
> 
> 
> --
> View this message in context:
> http://csound.1045644.n5.nabble.com/Master-clock-tp5726664p5727311.html
> Sent from the Csound - General mailing list archive at Nabble.com.
> 
> 
> Send bugs reports to the Sourceforge bug trackers
> csound6:
>             https://sourceforge.net/p/csound/tickets/
> csound5:
>             https://sourceforge.net/p/csound/bugs/
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"