plugout/plugin multichannel????


    Oct 14 2019 | 3:08 am
    I'm trying to create a 13 channel communication between M4L devices with plugout/plugin but only the first 2 channels are working. is there some trick? I'd upload a patch but I'm literally just using plugout @chans 13, and plugin @chans 13 with sig~ and number~

    • Oct 14 2019 | 11:00 pm
      Are you using routing dictionaries to configure how plugin~’s input channels are assigned?
      For inter-device communication at signal-rate you could also assign a live.remote~ in master patch to a live.numbox parameter in the controlled patch.
    • Oct 14 2019 | 11:27 pm
      routing dictionaries? I have no clue what you mean. Nothing in docs as far as I can tell. Don't I just make a multichannel plugin~/out~ and send signals through?
    • Oct 15 2019 | 12:28 am
      no clue about routing [dict]s? this topic should give you a clue: https://cycling74.com/forums/syntax-for-setting-output_routing_type-to-live-object/replies/1#reply-5da4f9e39e4d0b3b9a1f990f it is the new way to use max for accessing live's track input and output routings and sub-routings. there are a couple more threads about it, beware not to confuse older ones that don't use the [dict] system, they have been deprecated since live 9.7
    • Oct 15 2019 | 12:41 am
      I think there's a miscommunication here. I was hoping to pass more than two channels from one device to the next in a signal chain. This appears to be about passing audio between tracks.
    • Oct 27 2019 | 10:59 pm
      Bump: Does this really not work?
    • Oct 28 2019 | 7:25 am
      to my knowledge no, ast least not in live 9. plugout sends the streams to the host - and the track only has 2 channels. even in pluggo this only worked when the host has 4 VST/AU channels in the track where the plug-in was inserted. multichannel in live requires live v.10.something, isn´t it? for a one-patch-one-song type of application using the path via live api might be best anyway. but i have no clue about this practice.
    • Oct 28 2019 | 8:27 am
      Weird! Seems awfully counterintuitive to say there's multichannel support but not have multichannel tracks.
    • Oct 28 2019 | 11:34 am
      there must be a way how it works (the way you tried it) because people are doing that with hoa and spat and all this. u have live v10? or 9.
    • Oct 28 2019 | 12:04 pm
      ableton always called it "multichannel" when an instrument could receive MIDI on more than one channel, har har. :)
    • Oct 28 2019 | 12:44 pm
      no I'm using v10.1.2 and 8.1.0
    • Oct 28 2019 | 1:04 pm
      then both options should work; via channel chooser/API - but also by making a multichannel setup. via API would mean that there is no direct connection between the plug-ins at all, your plugout 7 8 9 10 11 would be available as channel input in a live audio channel strip - and how you get from there into another device i dont know ... i am not a live user... but that should work in a similar fashion. ;)
    • Oct 28 2019 | 1:08 pm
      ah wait. you first have to choose the device where you want to send the track to, and only then you have access to selecting one of the available inputs of this device. it is a two stage process.