The following csd is crashing whenever I trigger instr 1 with my mdi keyboard:



-M1 --midi-key=4 --midi-velocity-amp=5 -m0d


; Initialize the global variables.
sr = 44100
ksmps = 32
nchnls = 2

massign 0, 1

instr 1
event_i "i", 2, 0, 10
endin

instr 2
a1 diskin2 "one.wav", 1, 0, 0
outs a1, a1
endin



f0 3600



I've tested both instruments separately and they work fine. This is
the error I get:

writing 512-byte blks of shorts to dac
SECTION 1:
Csound tidy up: Segmentation violation
pm_winmm_term called
begin closing open devices...

I'm running Csound 5.11 on windows.


Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

It is a bug with the --midi-** options. You need to 'consume' p4 and  
p5  (say i1 = p4 and i2 = p5) and then it does not crash. Or remove  
the options.
Thanks for the report.

Victor
On 19 Feb 2010, at 14:33, Rory Walsh wrote:

> 
> 
> -M1 --midi-key=4 --midi-velocity-amp=5 -m0d
> 
> 
> ; Initialize the global variables.
> sr = 44100
> ksmps = 32
> nchnls = 2
>
> massign 0, 1
>
> instr 1
> event_i "i", 2, 0, 10
> endin
>
> instr 2
> a1 diskin2 "one.wav", 1, 0, 0
> outs a1, a1
> endin
>
> 
> 
> f0 3600
> 
> 



Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Thanks for the speedy reply.

On 19 February 2010 14:44, Victor Lazzarini  wrote:
> It is a bug with the --midi-** options. You need to 'consume' p4 and p5
>  (say i1 = p4 and i2 = p5) and then it does not crash. Or remove the
> options.
> Thanks for the report.
>
> Victor
> On 19 Feb 2010, at 14:33, Rory Walsh wrote:
>
>> 
>> 
>> -M1 --midi-key=4 --midi-velocity-amp=5 -m0d
>> 
>> 
>> ; Initialize the global variables.
>> sr = 44100
>> ksmps = 32
>> nchnls = 2
>>
>> massign 0, 1
>>
>> instr 1
>> event_i "i", 2, 0, 10
>> endin
>>
>> instr 2
>> a1 diskin2 "one.wav", 1, 0, 0
>> outs a1, a1
>> endin
>>
>> 
>> 
>> f0 3600
>> 
>> 
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>


Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

I don't mind how fussy it is so long as there is a workaround. I
didn't see this info in the manual?

Rory.


On 19 February 2010 14:49, Iain McCurdy  wrote:
> Hi Rory,
>
> If you remove --midi-key=4 --midi-velocity-amp=5 (which aren't used anyway)
> from your CsOptions it doesn't crash. Alternatively if you add p4, p5 onto
> the event_i line it won't crash either. Obviously it's not ideal that
> event_i is fussy like this.
>
> Bye,
> Iain
>
>> From: rorywalsh@ear.ie
>> Date: Fri, 19 Feb 2010 14:33:44 +0000
>> To: csound@lists.bath.ac.uk
>> Subject: [Csnd] midi driven event instrument..
>>
>> The following csd is crashing whenever I trigger instr 1 with my mdi
>> keyboard:
>>
>> 
>> 
>> -M1 --midi-key=4 --midi-velocity-amp=5 -m0d
>> 
>> 
>> ; Initialize the global variables.
>> sr = 44100
>> ksmps = 32
>> nchnls = 2
>>
>> massign 0, 1
>>
>> instr 1
>> event_i "i", 2, 0, 10
>> endin
>>
>> instr 2
>> a1 diskin2 "one.wav", 1, 0, 0
>> outs a1, a1
>> endin
>>
>> 
>> 
>> f0 3600
>> 
>> 
>>
>> I've tested both instruments separately and they work fine. This is
>> the error I get:
>>
>> writing 512-byte blks of shorts to dac
>> SECTION 1:
>> Csound tidy up: Segmentation violation
>> pm_winmm_term called
>> begin closing open devices...
>>
>> I'm running Csound 5.11 on windows.
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>
> ________________________________
> Not got a Hotmail account? Sign-up now - Free


Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

I guess it's not event_i that is the culprit here, but the midi flags.  
It seems to be a nasty bug.

Victor
On 19 Feb 2010, at 14:54, Rory Walsh wrote:

> I don't mind how fussy it is so long as there is a workaround. I
> didn't see this info in the manual?
>
> Rory.
>
>
> On 19 February 2010 14:49, Iain McCurdy  wrote:
>> Hi Rory,
>>
>> If you remove --midi-key=4 --midi-velocity-amp=5 (which aren't used  
>> anyway)
>> from your CsOptions it doesn't crash. Alternatively if you add p4,  
>> p5 onto
>> the event_i line it won't crash either. Obviously it's not ideal that
>> event_i is fussy like this.
>>
>> Bye,
>> Iain
>>
>>> From: rorywalsh@ear.ie
>>> Date: Fri, 19 Feb 2010 14:33:44 +0000
>>> To: csound@lists.bath.ac.uk
>>> Subject: [Csnd] midi driven event instrument..
>>>
>>> The following csd is crashing whenever I trigger instr 1 with my mdi
>>> keyboard:
>>>
>>> 
>>> 
>>> -M1 --midi-key=4 --midi-velocity-amp=5 -m0d
>>> 
>>> 
>>> ; Initialize the global variables.
>>> sr = 44100
>>> ksmps = 32
>>> nchnls = 2
>>>
>>> massign 0, 1
>>>
>>> instr 1
>>> event_i "i", 2, 0, 10
>>> endin
>>>
>>> instr 2
>>> a1 diskin2 "one.wav", 1, 0, 0
>>> outs a1, a1
>>> endin
>>>
>>> 
>>> 
>>> f0 3600
>>> 
>>> 
>>>
>>> I've tested both instruments separately and they work fine. This is
>>> the error I get:
>>>
>>> writing 512-byte blks of shorts to dac
>>> SECTION 1:
>>> Csound tidy up: Segmentation violation
>>> pm_winmm_term called
>>> begin closing open devices...
>>>
>>> I'm running Csound 5.11 on windows.
>>>
>>>
>>> Send bugs reports to this list.
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
>>> "unsubscribe
>>> csound"
>>
>> ________________________________
>> Not got a Hotmail account? Sign-up now - Free
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
> "unsubscribe csound"



Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"