[Csnd] Unusual jitter issues with kschedwhen and metro opcodes

Date	2013-05-13 01:02
From	Paul Batchelor
Subject	[Csnd] Unusual jitter issues with kschedwhen and metro opcodes
	Hello list, It would appear that using kschedwhen with metro will cause consistent jitter issues, both in realtime and non-realtime performances: <CsoundSynthesizer> <CsOptions> -ojitterout.wav -W -d </CsOptions> ; ============================================== <CsInstruments> sr = 44100 ksmps = 1 nchnls = 2 0dbfs = 1 gisine ftgen 0, 0, 4096, 10, 1 instr 1 ktrig_audio metro (140/60) * 4 schedkwhen ktrig_audio, 0, 1, "looper", 0, (60/(140 * 4)) endin instr looper kenv linseg 1, p3, 0 ipch random 300, 400 a1 oscili kenv, ipch, gisine outs a1, a1 endin </CsInstruments> ; ============================================== <CsScore> i1 0 200 </CsScore> </CsoundSynthesizer> I tested this on my Linux box with Csound 5.16 and Csound 5.18. Both produce identical results. The jitter will consistently happen at around 2:09, even with ksmps=1, where you will begin to hear noticeable gaps in the triggered output. Any idea what is happening? Thanks, -P

Date	2013-05-13 01:09
From	Rory Walsh
Subject	Re: [Csnd] Unusual jitter issues with kschedwhen and metro opcodes
	I get no such gaps here with Csound6. What OS are you using? On 13 May 2013 01:02, Paul Batchelor wrote: > Hello list, > > It would appear that using kschedwhen with metro will cause consistent > jitter issues, both in realtime and non-realtime performances: > > > > -ojitterout.wav -W -d > > ; ============================================== > > > sr = 44100 > ksmps = 1 > nchnls = 2 > 0dbfs = 1 > > gisine ftgen 0, 0, 4096, 10, 1 > > instr 1 > ktrig_audio metro (140/60) * 4 > schedkwhen ktrig_audio, 0, 1, "looper", 0, (60/(140 * 4)) > endin > > instr looper > > kenv linseg 1, p3, 0 > ipch random 300, 400 > a1 oscili kenv, ipch, gisine > outs a1, a1 > endin > > > ; ============================================== > > > i1 0 200 > > > > > I tested this on my Linux box with Csound 5.16 and Csound 5.18. Both produce > identical results. > > The jitter will consistently happen at around 2:09, even with ksmps=1, where > you will begin to hear noticeable gaps in the triggered output. > > Any idea what is happening? > > Thanks, > > -P

Date	2013-05-13 05:03
From	Paul Batchelor
Subject	Re: [Csnd] Unusual jitter issues with kschedwhen and metro opcodes
	I'm using csound 5.16 with Slackware 13.37 and 5.18 with OSX 10.8.2 On Sun, May 12, 2013 at 8:09 PM, Rory Walsh <rorywalsh@ear.ie> wrote: I get no such gaps here with Csound6. What OS are you using? On 13 May 2013 01:02, Paul Batchelor <pbatchelor@berklee.edu> wrote: > Hello list, > > It would appear that using kschedwhen with metro will cause consistent > jitter issues, both in realtime and non-realtime performances: > > <CsoundSynthesizer> > <CsOptions> > -ojitterout.wav -W -d > </CsOptions> > ; ============================================== > <CsInstruments> > > sr = 44100 > ksmps = 1 > nchnls = 2 > 0dbfs = 1 > > gisine ftgen 0, 0, 4096, 10, 1 > > instr 1 > ktrig_audio metro (140/60) * 4 > schedkwhen ktrig_audio, 0, 1, "looper", 0, (60/(140 * 4)) > endin > > instr looper > > kenv linseg 1, p3, 0 > ipch random 300, 400 > a1 oscili kenv, ipch, gisine > outs a1, a1 > endin > > </CsInstruments> > ; ============================================== > <CsScore> > > i1 0 200 > > </CsScore> > </CsoundSynthesizer> > > I tested this on my Linux box with Csound 5.16 and Csound 5.18. Both produce > identical results. > > The jitter will consistently happen at around 2:09, even with ksmps=1, where > you will begin to hear noticeable gaps in the triggered output. > > Any idea what is happening? > > Thanks, > > -P 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"