Dear all,

I am having trouble using the connect opcode to create a signal flow
with multiple instances of the same instrument (an 'effect').

With the code below I would expect to hear a short reverb in the left
speaker, and a longer reverb in the right speaker. However, I hear a
long reverb in both speakers.

I am trying to avoid having to duplicate instruments (imagine a big
instrument 2) - if this is really not possible with the connect
opcode, could someone recommend an alternative approach?
(I have tried also the mixersend opcode, with no luck)

Best regards,
Søren



-odac



sr = 44100
ksmps = 32
nchnls = 2

connect 1, "leftout", 2.1, "leftin"
connect 1, "leftout", 2.2, "leftin"

connect 2.1, "leftout", "outputleft", "leftin"
connect 2.2, "leftout", "outputright", "leftin"

alwayson 2.1, 0.21
alwayson 2.2, 0.91
alwayson "outputleft"
alwayson "outputright"

instr 1
    asig vco2 12000, 440.0
    outleta "leftout", asig
endin

instr 2
    asig inleta "leftin"
    asig reverb asig, p4
    outleta "leftout", asig
endin

instr outputleft
    asig inleta "leftin"
    outs1 asig
endin

instr outputright
    asig inleta "leftin"
    outs2 asig
endin



i1 0 0.5
i1 1 0.5
e 2



Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

The signal flow graph opcodes are not designed for per instance
connections. I have not been able to figure out how to implement such
connections.Nor did I envision or test fractional instrument numbers.

You can achieve what you want by creating instruments named 2_1 and
2_2 but with some duplication of instr code.

I will give some thought to whether the scheme can be made to work
with fractional instrument numbers.

Regards,
Mike

-----------------------------------------------------
Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com


On Sat, Apr 30, 2016 at 2:27 PM, Søren Jakobsen  wrote:
> Dear all,
>
> I am having trouble using the connect opcode to create a signal flow
> with multiple instances of the same instrument (an 'effect').
>
> With the code below I would expect to hear a short reverb in the left
> speaker, and a longer reverb in the right speaker. However, I hear a
> long reverb in both speakers.
>
> I am trying to avoid having to duplicate instruments (imagine a big
> instrument 2) - if this is really not possible with the connect
> opcode, could someone recommend an alternative approach?
> (I have tried also the mixersend opcode, with no luck)
>
> Best regards,
> Søren
>
> 
> 
> -odac
> 
> 
>
> sr = 44100
> ksmps = 32
> nchnls = 2
>
> connect 1, "leftout", 2.1, "leftin"
> connect 1, "leftout", 2.2, "leftin"
>
> connect 2.1, "leftout", "outputleft", "leftin"
> connect 2.2, "leftout", "outputright", "leftin"
>
> alwayson 2.1, 0.21
> alwayson 2.2, 0.91
> alwayson "outputleft"
> alwayson "outputright"
>
> instr 1
>     asig vco2 12000, 440.0
>     outleta "leftout", asig
> endin
>
> instr 2
>     asig inleta "leftin"
>     asig reverb asig, p4
>     outleta "leftout", asig
> endin
>
> instr outputleft
>     asig inleta "leftin"
>     outs1 asig
> endin
>
> instr outputright
>     asig inleta "leftin"
>     outs2 asig
> endin
>
> 
> 
> i1 0 0.5
> i1 1 0.5
> e 2
> 
> 
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>         https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Hi Mike!

Your opcodes are really useful and it would be a great we didn't have
to duplicate the instruments (in my case it would be quite a lot of
code to maintain doubly).

Regarding the design, I was a bit confused about how to use the mixing
opcodes together with 'connect'. I think a more natural way to
integrate the two might be to allow multiple ins and outs (not just
left/right) for any instrument in the flow.

Thanks for the help.
Søren

On 4/30/16, Michael Gogins  wrote:
> The signal flow graph opcodes are not designed for per instance
> connections. I have not been able to figure out how to implement such
> connections.Nor did I envision or test fractional instrument numbers.
>
> You can achieve what you want by creating instruments named 2_1 and
> 2_2 but with some duplication of instr code.
>
> I will give some thought to whether the scheme can be made to work
> with fractional instrument numbers.
>
> Regards,
> Mike
>
> -----------------------------------------------------
> Michael Gogins
> Irreducible Productions
> http://michaelgogins.tumblr.com
> Michael dot Gogins at gmail dot com
>
>
> On Sat, Apr 30, 2016 at 2:27 PM, Søren Jakobsen  wrote:
>> Dear all,
>>
>> I am having trouble using the connect opcode to create a signal flow
>> with multiple instances of the same instrument (an 'effect').
>>
>> With the code below I would expect to hear a short reverb in the left
>> speaker, and a longer reverb in the right speaker. However, I hear a
>> long reverb in both speakers.
>>
>> I am trying to avoid having to duplicate instruments (imagine a big
>> instrument 2) - if this is really not possible with the connect
>> opcode, could someone recommend an alternative approach?
>> (I have tried also the mixersend opcode, with no luck)
>>
>> Best regards,
>> Søren
>>
>> 
>> 
>> -odac
>> 
>> 
>>
>> sr = 44100
>> ksmps = 32
>> nchnls = 2
>>
>> connect 1, "leftout", 2.1, "leftin"
>> connect 1, "leftout", 2.2, "leftin"
>>
>> connect 2.1, "leftout", "outputleft", "leftin"
>> connect 2.2, "leftout", "outputright", "leftin"
>>
>> alwayson 2.1, 0.21
>> alwayson 2.2, 0.91
>> alwayson "outputleft"
>> alwayson "outputright"
>>
>> instr 1
>>     asig vco2 12000, 440.0
>>     outleta "leftout", asig
>> endin
>>
>> instr 2
>>     asig inleta "leftin"
>>     asig reverb asig, p4
>>     outleta "leftout", asig
>> endin
>>
>> instr outputleft
>>     asig inleta "leftin"
>>     outs1 asig
>> endin
>>
>> instr outputright
>>     asig inleta "leftin"
>>     outs2 asig
>> endin
>>
>> 
>> 
>> i1 0 0.5
>> i1 1 0.5
>> e 2
>> 
>> 
>>
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>         https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here
>

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Multiple ins and outs are possible using arrays. But I don't see it in the manual. I will send you an example.

Regards,
Mike

Correction:

The outletv and inletv opcodes send and receive arate arrays. I will
make sure they get back into the manual.

One insrument definition may contain any number of inlets and outlets,
which may have any names that are valid Csound strings.

The attached files demonstrate this, although the system is a bit
complex at first sight. It is a system for spatializaing audio that
uses both UDOs and the signal flow graph opcodes, with a demo csd.
Array inlets and outlets and used to send b-format Ambisonic
multi-channel, spatialized audio.

Hope this helps,
Mike

-----------------------------------------------------
Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com


On Sun, May 1, 2016 at 9:32 AM, Michael Gogins  wrote:
> Multiple ins and outs are possible using arrays. But I don't see it in the
> manual. I will send you an example.
>
> Regards,
> Mike
>
> On May 1, 2016 5:08 AM, "Søren Jakobsen"  wrote:
>>
>> Hi Mike!
>>
>> Your opcodes are really useful and it would be a great we didn't have
>> to duplicate the instruments (in my case it would be quite a lot of
>> code to maintain doubly).
>>
>> Regarding the design, I was a bit confused about how to use the mixing
>> opcodes together with 'connect'. I think a more natural way to
>> integrate the two might be to allow multiple ins and outs (not just
>> left/right) for any instrument in the flow.
>>
>> Thanks for the help.
>> Søren
>>
>> On 4/30/16, Michael Gogins  wrote:
>> > The signal flow graph opcodes are not designed for per instance
>> > connections. I have not been able to figure out how to implement such
>> > connections.Nor did I envision or test fractional instrument numbers.
>> >
>> > You can achieve what you want by creating instruments named 2_1 and
>> > 2_2 but with some duplication of instr code.
>> >
>> > I will give some thought to whether the scheme can be made to work
>> > with fractional instrument numbers.
>> >
>> > Regards,
>> > Mike
>> >
>> > -----------------------------------------------------
>> > Michael Gogins
>> > Irreducible Productions
>> > http://michaelgogins.tumblr.com
>> > Michael dot Gogins at gmail dot com
>> >
>> >
>> > On Sat, Apr 30, 2016 at 2:27 PM, Søren Jakobsen 
>> > wrote:
>> >> Dear all,
>> >>
>> >> I am having trouble using the connect opcode to create a signal flow
>> >> with multiple instances of the same instrument (an 'effect').
>> >>
>> >> With the code below I would expect to hear a short reverb in the left
>> >> speaker, and a longer reverb in the right speaker. However, I hear a
>> >> long reverb in both speakers.
>> >>
>> >> I am trying to avoid having to duplicate instruments (imagine a big
>> >> instrument 2) - if this is really not possible with the connect
>> >> opcode, could someone recommend an alternative approach?
>> >> (I have tried also the mixersend opcode, with no luck)
>> >>
>> >> Best regards,
>> >> Søren
>> >>
>> >> 
>> >> 
>> >> -odac
>> >> 
>> >> 
>> >>
>> >> sr = 44100
>> >> ksmps = 32
>> >> nchnls = 2
>> >>
>> >> connect 1, "leftout", 2.1, "leftin"
>> >> connect 1, "leftout", 2.2, "leftin"
>> >>
>> >> connect 2.1, "leftout", "outputleft", "leftin"
>> >> connect 2.2, "leftout", "outputright", "leftin"
>> >>
>> >> alwayson 2.1, 0.21
>> >> alwayson 2.2, 0.91
>> >> alwayson "outputleft"
>> >> alwayson "outputright"
>> >>
>> >> instr 1
>> >>     asig vco2 12000, 440.0
>> >>     outleta "leftout", asig
>> >> endin
>> >>
>> >> instr 2
>> >>     asig inleta "leftin"
>> >>     asig reverb asig, p4
>> >>     outleta "leftout", asig
>> >> endin
>> >>
>> >> instr outputleft
>> >>     asig inleta "leftin"
>> >>     outs1 asig
>> >> endin
>> >>
>> >> instr outputright
>> >>     asig inleta "leftin"
>> >>     outs2 asig
>> >> endin
>> >>
>> >> 
>> >> 
>> >> i1 0 0.5
>> >> i1 1 0.5
>> >> e 2
>> >> 
>> >> 
>> >>
>> >> Csound mailing list
>> >> Csound@listserv.heanet.ie
>> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> >> Send bugs reports to
>> >>         https://github.com/csound/csound/issues
>> >> Discussions of bugs and features can be posted here
>> >
>> > Csound mailing list
>> > Csound@listserv.heanet.ie
>> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> > Send bugs reports to
>> >         https://github.com/csound/csound/issues
>> > Discussions of bugs and features can be posted here
>> >
>>
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Thanks for the help, Mike. I was not able to run your code, but the
opcodes work perfectly:)
Best,
Søren

On 5/1/16, Michael Gogins  wrote:
> Correction:
>
> The outletv and inletv opcodes send and receive arate arrays. I will
> make sure they get back into the manual.
>
> One insrument definition may contain any number of inlets and outlets,
> which may have any names that are valid Csound strings.
>
> The attached files demonstrate this, although the system is a bit
> complex at first sight. It is a system for spatializaing audio that
> uses both UDOs and the signal flow graph opcodes, with a demo csd.
> Array inlets and outlets and used to send b-format Ambisonic
> multi-channel, spatialized audio.
>
> Hope this helps,
> Mike
>
> -----------------------------------------------------
> Michael Gogins
> Irreducible Productions
> http://michaelgogins.tumblr.com
> Michael dot Gogins at gmail dot com
>
>
> On Sun, May 1, 2016 at 9:32 AM, Michael Gogins 
> wrote:
>> Multiple ins and outs are possible using arrays. But I don't see it in
>> the
>> manual. I will send you an example.
>>
>> Regards,
>> Mike
>>
>> On May 1, 2016 5:08 AM, "Søren Jakobsen"  wrote:
>>>
>>> Hi Mike!
>>>
>>> Your opcodes are really useful and it would be a great we didn't have
>>> to duplicate the instruments (in my case it would be quite a lot of
>>> code to maintain doubly).
>>>
>>> Regarding the design, I was a bit confused about how to use the mixing
>>> opcodes together with 'connect'. I think a more natural way to
>>> integrate the two might be to allow multiple ins and outs (not just
>>> left/right) for any instrument in the flow.
>>>
>>> Thanks for the help.
>>> Søren
>>>
>>> On 4/30/16, Michael Gogins  wrote:
>>> > The signal flow graph opcodes are not designed for per instance
>>> > connections. I have not been able to figure out how to implement such
>>> > connections.Nor did I envision or test fractional instrument numbers.
>>> >
>>> > You can achieve what you want by creating instruments named 2_1 and
>>> > 2_2 but with some duplication of instr code.
>>> >
>>> > I will give some thought to whether the scheme can be made to work
>>> > with fractional instrument numbers.
>>> >
>>> > Regards,
>>> > Mike
>>> >
>>> > -----------------------------------------------------
>>> > Michael Gogins
>>> > Irreducible Productions
>>> > http://michaelgogins.tumblr.com
>>> > Michael dot Gogins at gmail dot com
>>> >
>>> >
>>> > On Sat, Apr 30, 2016 at 2:27 PM, Søren Jakobsen 
>>> > wrote:
>>> >> Dear all,
>>> >>
>>> >> I am having trouble using the connect opcode to create a signal flow
>>> >> with multiple instances of the same instrument (an 'effect').
>>> >>
>>> >> With the code below I would expect to hear a short reverb in the left
>>> >> speaker, and a longer reverb in the right speaker. However, I hear a
>>> >> long reverb in both speakers.
>>> >>
>>> >> I am trying to avoid having to duplicate instruments (imagine a big
>>> >> instrument 2) - if this is really not possible with the connect
>>> >> opcode, could someone recommend an alternative approach?
>>> >> (I have tried also the mixersend opcode, with no luck)
>>> >>
>>> >> Best regards,
>>> >> Søren
>>> >>
>>> >> 
>>> >> 
>>> >> -odac
>>> >> 
>>> >> 
>>> >>
>>> >> sr = 44100
>>> >> ksmps = 32
>>> >> nchnls = 2
>>> >>
>>> >> connect 1, "leftout", 2.1, "leftin"
>>> >> connect 1, "leftout", 2.2, "leftin"
>>> >>
>>> >> connect 2.1, "leftout", "outputleft", "leftin"
>>> >> connect 2.2, "leftout", "outputright", "leftin"
>>> >>
>>> >> alwayson 2.1, 0.21
>>> >> alwayson 2.2, 0.91
>>> >> alwayson "outputleft"
>>> >> alwayson "outputright"
>>> >>
>>> >> instr 1
>>> >>     asig vco2 12000, 440.0
>>> >>     outleta "leftout", asig
>>> >> endin
>>> >>
>>> >> instr 2
>>> >>     asig inleta "leftin"
>>> >>     asig reverb asig, p4
>>> >>     outleta "leftout", asig
>>> >> endin
>>> >>
>>> >> instr outputleft
>>> >>     asig inleta "leftin"
>>> >>     outs1 asig
>>> >> endin
>>> >>
>>> >> instr outputright
>>> >>     asig inleta "leftin"
>>> >>     outs2 asig
>>> >> endin
>>> >>
>>> >> 
>>> >> 
>>> >> i1 0 0.5
>>> >> i1 1 0.5
>>> >> e 2
>>> >> 
>>> >> 
>>> >>
>>> >> Csound mailing list
>>> >> Csound@listserv.heanet.ie
>>> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> >> Send bugs reports to
>>> >>         https://github.com/csound/csound/issues
>>> >> Discussions of bugs and features can be posted here
>>> >
>>> > Csound mailing list
>>> > Csound@listserv.heanet.ie
>>> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> > Send bugs reports to
>>> >         https://github.com/csound/csound/issues
>>> > Discussions of bugs and features can be posted here
>>> >
>>>
>>> Csound mailing list
>>> Csound@listserv.heanet.ie
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> Send bugs reports to
>>>         https://github.com/csound/csound/issues
>>> Discussions of bugs and features can be posted here
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>         https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here
>

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here