Hi all,

I've been playing with sub-instruments and just upgraded to cs6. There
seems to be something not being initialised when they are loaded. If
there are linseg opcodes, they return 0 and expseg immediately goes to
0.

Running the sub-instrument directly before in the score seems to fix
this. See the attatched csd. If the "basic_tone" score line is
included then both notes have the pitch glide. If the "basic_tone"
line is commented out then you get a static tone (the linseg envelope
doesn't run).

I'm using csound 6 on linux built from git pulled today.

Regards,
 Joel

Hi Joel,

I think I've got it fixed.  The issue was that the subinstr init code
was not updated for local ksmps. I copied some code from the user
opcode init code that seems to have done the trick. If you could pull
from GIT and try with the latest that'd be great.

Victor and John: if you could review that change, I'd appreciate it!

Thanks!
steven


On Mon, Jul 22, 2013 at 11:33 AM, Steven Yi  wrote:
> Hi Joel,
>
> I'm about to get on a flight, so can't test this at the moment. It sounds
> like a bug though. Could you enter a bug in the bug tracker on sourceforge?
> If someone hasn't taken a look at it, I'll look into it when I get to Warsaw
> tomorrow. Feel free to assign to me (kunstmusik) when entering the ticket.
>
> Thanks!
> Steven
>
>
> On Monday, July 22, 2013, Joel Ross wrote:
>>
>> Hi all,
>>
>> I've been playing with sub-instruments and just upgraded to cs6. There
>> seems to be something not being initialised when they are loaded. If
>> there are linseg opcodes, they return 0 and expseg immediately goes to
>> 0.
>>
>> Running the sub-instrument directly before in the score seems to fix
>> this. See the attatched csd. If the "basic_tone" score line is
>> included then both notes have the pitch glide. If the "basic_tone"
>> line is commented out then you get a static tone (the linseg envelope
>> doesn't run).
>>
>> I'm using csound 6 on linux built from git pulled today.
>>
>> Regards,
>>  Joel
>>
>> 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"
>>
>>
>

Hi Steven,

As far as I can tell, its working fine now. Thanks!
I tested it with the instruments I was working on before and they also work.
About the tracker. If I had a sourceforge account, would it let me
file reports? I couldn't see how to do it.

Regards,
 Joel

On 28 July 2013 13:03, Steven Yi  wrote:
> Hi Joel,
>
> I think I've got it fixed.  The issue was that the subinstr init code
> was not updated for local ksmps. I copied some code from the user
> opcode init code that seems to have done the trick. If you could pull
> from GIT and try with the latest that'd be great.
>
> Victor and John: if you could review that change, I'd appreciate it!
>
> Thanks!
> steven
>
>
> On Mon, Jul 22, 2013 at 11:33 AM, Steven Yi  wrote:
>> Hi Joel,
>>
>> I'm about to get on a flight, so can't test this at the moment. It sounds
>> like a bug though. Could you enter a bug in the bug tracker on sourceforge?
>> If someone hasn't taken a look at it, I'll look into it when I get to Warsaw
>> tomorrow. Feel free to assign to me (kunstmusik) when entering the ticket.
>>
>> Thanks!
>> Steven
>>
>>
>> On Monday, July 22, 2013, Joel Ross wrote:
>>>
>>> Hi all,
>>>
>>> I've been playing with sub-instruments and just upgraded to cs6. There
>>> seems to be something not being initialised when they are loaded. If
>>> there are linseg opcodes, they return 0 and expseg immediately goes to
>>> 0.
>>>
>>> Running the sub-instrument directly before in the score seems to fix
>>> this. See the attatched csd. If the "basic_tone" score line is
>>> included then both notes have the pitch glide. If the "basic_tone"
>>> line is commented out then you get a static tone (the linseg envelope
>>> doesn't run).
>>>
>>> I'm using csound 6 on linux built from git pulled today.
>>>
>>> Regards,
>>>  Joel
>>>
>>> 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"
>
>

HI Joel,

I think that yes, if you login with an account, you should be able to
enter an item into the tracker.  If you go to the Ticket button and
rollover, there should be a menu option for "Csound6-bugs".  From
there, there should be a button on the left hand side that says "+
Create Ticket".

Glad that's fixed your problem!

steven


On Sun, Jul 28, 2013 at 2:46 PM, Joel Ross  wrote:
> Hi Steven,
>
> As far as I can tell, its working fine now. Thanks!
> I tested it with the instruments I was working on before and they also work.
> About the tracker. If I had a sourceforge account, would it let me
> file reports? I couldn't see how to do it.
>
> Regards,
>  Joel
>
> On 28 July 2013 13:03, Steven Yi  wrote:
>> Hi Joel,
>>
>> I think I've got it fixed.  The issue was that the subinstr init code
>> was not updated for local ksmps. I copied some code from the user
>> opcode init code that seems to have done the trick. If you could pull
>> from GIT and try with the latest that'd be great.
>>
>> Victor and John: if you could review that change, I'd appreciate it!
>>
>> Thanks!
>> steven
>>
>>
>> On Mon, Jul 22, 2013 at 11:33 AM, Steven Yi  wrote:
>>> Hi Joel,
>>>
>>> I'm about to get on a flight, so can't test this at the moment. It sounds
>>> like a bug though. Could you enter a bug in the bug tracker on sourceforge?
>>> If someone hasn't taken a look at it, I'll look into it when I get to Warsaw
>>> tomorrow. Feel free to assign to me (kunstmusik) when entering the ticket.
>>>
>>> Thanks!
>>> Steven
>>>
>>>
>>> On Monday, July 22, 2013, Joel Ross wrote:
>>>>
>>>> Hi all,
>>>>
>>>> I've been playing with sub-instruments and just upgraded to cs6. There
>>>> seems to be something not being initialised when they are loaded. If
>>>> there are linseg opcodes, they return 0 and expseg immediately goes to
>>>> 0.
>>>>
>>>> Running the sub-instrument directly before in the score seems to fix
>>>> this. See the attatched csd. If the "basic_tone" score line is
>>>> included then both notes have the pitch glide. If the "basic_tone"
>>>> line is commented out then you get a static tone (the linseg envelope
>>>> doesn't run).
>>>>
>>>> I'm using csound 6 on linux built from git pulled today.
>>>>
>>>> Regards,
>>>>  Joel
>>>>
>>>> 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"
>
>