Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jitlib: Ndef(\y).play(numChannels:2) causes error #1113

Closed
miguel-negrao opened this issue May 20, 2014 · 5 comments
Closed

Jitlib: Ndef(\y).play(numChannels:2) causes error #1113

miguel-negrao opened this issue May 20, 2014 · 5 comments
Labels
bug Issues that relate to unexpected/unwanted behavior. Don't use for PRs. comp: class library SC class library

Comments

@miguel-negrao
Copy link
Member

Ndef('y')
ERROR: binary operator '+' failed.
RECEIVER:
   nil
ARGS:
Instance of Array {    (0xef399c8, gc=44, fmt=01, flg=00, set=02)
  indexed slots [2]
      0 : Integer 0
      1 : Integer 1
}
   nil
PATH: /home/miguel/Development/SuperCollider/supercollider/SCClassLibrary/JITLib/ProxySpace/InBus.sc
CALL STACK:
    DoesNotUnderstandError:reportError   0x408d988
        arg this = <instance of BinaryOpFailureError>
    Nil:handleError   0x10c2ac88
        arg this = nil
        arg error = <instance of BinaryOpFailureError>
    Thread:handleError   0xddddbe8
        arg this = <instance of Thread>
        arg error = <instance of BinaryOpFailureError>
    Object:throw   0xfe28b68
        arg this = <instance of BinaryOpFailureError>
    Object:performBinaryOpOnSomething   0x8ebdcf8
        arg this = nil
        arg aSelector = '+'
        arg thing = [*2]
        arg adverb = nil
    BusPlug:playToBundle   0x8ebe638
        arg this = <instance of Ndef>
        arg bundle = <instance of MixedBundle>
        arg out = nil
        arg numChannels = 2
        arg group = <instance of Group>
        arg multi = false
        arg vol = nil
        arg fadeTime = nil
        arg addAction = nil
    BusPlug:play   0x8ebe888
        arg this = <instance of Ndef>
        arg out = nil
        arg numChannels = 2
        arg group = nil
        arg multi = false
        arg vol = nil
        arg fadeTime = nil
        arg addAction = nil
        var bundle = <instance of MixedBundle>
    Interpreter:interpretPrintCmdLine   0x8ed1178
        arg this = <instance of Interpreter>
        var res = nil
        var func = <instance of Function>
        var code = "Ndef(\y).play(numChannels:2)"
        var doc = nil
        var ideClass = <instance of Meta_ScIDE>
    Process:interpretPrintCmdLine   0x840ad28
        arg this = <instance of Main>
^^ The preceding error dump is for ERROR: binary operator '+' failed.
RECEIVER: nil

This was not the case in sc 3.6. Shouldn't 'out' default to zero somewhere ?

@miguel-negrao
Copy link
Member Author

Also,

Ndef(\x, { SinOsc.ar([200,500]) * 0.1 }).play(0,2)

plays both channels to channel 0:

NODE TREE Group 0
   1 group
      1000 group
         1001 temp__0x_0
           gate: 1 fadeTime: 0.019999999552965 out: 4
      1002 group
         1003 system_link_audio_1
           doneAction: 2 out: 0 in: 4 vol: 1 level: 1 lag: 0.050000000745058 gate: 1 fadeTime: 0.019999999552965
         1004 system_link_audio_1
           doneAction: 2 out: 0 in: 5 vol: 1 level: 1 lag: 0.050000000745058 gate: 1 fadeTime: 0.019999999552965

Isn't it supposed to play a stereo output to output channels 0 and 1 ? From memory I think that's how it was working in 3.6...

@telephon
Copy link
Member

definitely it should …

@telephon
Copy link
Member

The OSC message looks OK:

[ "#bundle", 15503069409855398668, 
  [ 21, 1002, 1, 1 ],
  [ 9, "system_link_audio_1", 1003, 1, 1002, "out", 0, "in", 4, "level", 1, "fadeTime", 0.02, "vol", 1 ],
  [ 9, "system_link_audio_1", 1004, 1, 1002, "out", 1, "in", 5, "level", 1, "fadeTime", 0.02, "vol", 1 ]
]

@jamshark70
Copy link
Contributor

Coincidentally enough, I've just encountered an issue (recent git) where sclang appears to be sending the right OSC messages to create synths, but the controls end up with default values. Reported on the mailing list.

It may very well be the same thing.

Wasn't there some re-factoring recently of synth control initialization?

@telephon
Copy link
Member

Yes, it was, I've reverted the corresponding merge in b629767

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issues that relate to unexpected/unwanted behavior. Don't use for PRs. comp: class library SC class library
Projects
None yet
Development

No branches or pull requests

3 participants