Csound Csound-dev Csound-tekno Search About

Triggering "schedule" at metro rate

Date2015-06-07 17:08
Fromchronopolis
SubjectTriggering "schedule" at metro rate
For some reason, my schedule opcode only schedules at the default 1 per
second even with a conditional testing the ktrig value

ktrig metro 4

if ktrig ==1 then
schedule 1,itime,idur
endif

So this should trigger 4 times per second, right? But schedule will not
budge from only firing every second. 

What am I doing wrong?



--
View this message in context: http://csound.1045644.n5.nabble.com/Triggering-schedule-at-metro-rate-tp5742039.html
Sent from the Csound - General mailing list archive at Nabble.com.

------------------------------------------------------------------------------
_______________________________________________
Csound-users mailing list
Csound-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-users
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2015-06-08 12:04
FromVictor Lazzarini
SubjectRe: Triggering "schedule" at metro rate
schedule is init-time only, and you are trying to use it in perf-time. 
Try using event instead. 
========================
Dr Victor Lazzarini
Dean of Arts, Celtic Studies and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952 

> On 7 Jun 2015, at 17:08, chronopolis  wrote:
> 
> For some reason, my schedule opcode only schedules at the default 1 per
> second even with a conditional testing the ktrig value
> 
> ktrig metro 4
> 
> if ktrig ==1 then
> schedule 1,itime,idur
> endif
> 
> So this should trigger 4 times per second, right? But schedule will not
> budge from only firing every second. 
> 
> What am I doing wrong?
> 
> 
> 
> --
> View this message in context: http://csound.1045644.n5.nabble.com/Triggering-schedule-at-metro-rate-tp5742039.html
> Sent from the Csound - General mailing list archive at Nabble.com.
> 
> ------------------------------------------------------------------------------
> _______________________________________________
> Csound-users mailing list
> Csound-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-users
> Send bugs reports to
>        https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here


------------------------------------------------------------------------------
_______________________________________________
Csound-users mailing list
Csound-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-users
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2015-06-08 12:06
FromTarmo Johannes
SubjectRe: Triggering "schedule" at metro rate
AttachmentsNone  None  

hi,

 

schedule is i-time only opcode (works only on the strartiup of the instrument). use schedkwhen or event "i", ...

 

like

 

ktrig metro 4

schedkwhen ktrig,0,0,1,itime,idur

 

and you don't need even if-statement

 

 

best!

tarmo

 

On Sunday 07 June 2015 09:08:55 chronopolis wrote:

> For some reason, my schedule opcode only schedules at the default 1 per

> second even with a conditional testing the ktrig value

>

> ktrig metro 4

>

> if ktrig ==1 then

> schedule 1,itime,idur

> endif

>

> So this should trigger 4 times per second, right? But schedule will not

> budge from only firing every second.

>

> What am I doing wrong?

>

>

>

> --

> View this message in context:

> http://csound.1045644.n5.nabble.com/Triggering-schedule-at-metro-rate-tp574

> 2039.html Sent from the Csound - General mailing list archive at Nabble.com.

>

> ----------------------------------------------------------------------------

> -- _______________________________________________

> Csound-users mailing list

> Csound-users@lists.sourceforge.net

> https://lists.sourceforge.net/lists/listinfo/csound-users

> Send bugs reports to

> https://github.com/csound/csound/issues

> Discussions of bugs and features can be posted here