HISE multiple outputs

[d.healey]

Bump bump - how can I display the sum or average of all channels?

[Dan Korneff]

@d-healey I think I read somewhere that it's only available on the stereo out.

[d.healey]

@dustbro Oh that's a shame :(

[Dan Korneff]

@d-healey Shouldn't be impossible to do. Christoph might dedicate his time to the standalone (stereo) version, and these features haven't trickeld down to the plugin version yet.

[d.healey]

@dustbro I'm using the standalone version and routing my 3 mics all to 1/2 on the output, but they go to separate channels before that via simple gains. I think the Engine.getMasterPeakLevel() function doesn't give the actual output peak it gives the peak for the master containers channels 0 and 1.

[Dan Korneff]

@d-healey said in HISE multiple outputs:

I think the Engine.getMasterPeakLevel() function doesn't give the actual output peak it gives the peak for the master containers channels 0 and 1.

@Christoph-Hart Any chance we can gain access to the PeakLevel of all the channels? I would love to put output meters on all my samplers

[gorangrooves]

Hey @dustbro, how did you enable the multiple outputs in the plugin version of HISE?
Mine only shows a stereo output with no way to get 16 outs. I am using v 2.0.0 build 650 that @Christoph-Hart compiled and released a while back.
There is only a single version of plugin and it is called HISE x64. Are you loading something else that you compiled?

Thank you.

[Dan Korneff]

@gorangrooves you have to compile it from the source code.

[gorangrooves]

@dustbro Got you. Thank you! I'll do that.

[gorangrooves]

@dustbro How long ago did you compile the plugin version of HISE? I am not able to compile it from the latest master branch.

[Christoph Hart]

Just checked, still compiles, but I noticed that there is still the old VS2015 exporter present in the Projucer file, and if you export it as VS2015 project and then try to compile it with VS2017 it might cause all kinds of problems.

I've removed the exporter. Please pull the latest version and try again (now it should automatically choose the 2017 exporter).

[gorangrooves]

@Christoph-Hart I set the number of outputs for HISE plugin to 16 when compiling. Is that a maximum amount or will it do more if I change the number?

[Christoph Hart]

Just try it, but put on your safety helmet before you hit compile ;)

[gorangrooves]

@dustbro Thank you so much for the user-selectable multiple output script. I managed to implement it for all components and it works great.

[Dan Korneff]

@Christoph-Hart said in HISE multiple outputs:

standalone version doesn't not support multichannels. If you need multichannels, use the plugin version.

@Christoph-Hart Is there a plan to eventually incorporate multichannels in the standalone version?

[Christoph Hart]

Not really. What I could do is to add an "emulation" of multichannels to the HISE standalone app so that you can at least create multichannel plugins instead of using the plugin version of HISE for that. It would still use two stereo outs, but you could switch which pair in the multichannel setup is routed to the stereo output of the application to test if it works.

[ustk]

Would be cool! I don't like to use the plugin version for personal reasons mostly...

[Lindon]

@Christoph-Hart said in HISE multiple outputs:

Not really. What I could do is to add an "emulation" of multichannels to the HISE standalone app so that you can at least create multichannel plugins instead of using the plugin version of HISE for that. It would still use two stereo outs, but you could switch which pair in the multichannel setup is routed to the stereo output of the application to test if it works.

• did this happen at all?

[lalalandsynth]

Does a multichannel plugin automatically route everything to 1-2 if the user does not assign output channels ? So there is a choice whether to use multi channel or not ?

Or does it always route everything to 1-2 and then you can also get individual channels ? I guess that is the way to do it