Roadmap to HISE 5

[Orvillain]

@Christoph-Hart said in Roadmap to HISE 5:

I think you must not touch the preprocessor definition in the source code

Just to clarify, I didn't edit any code. I'm talking about the setting here:

[Chazrox]

@d-healey modes?? Please share!

[d.healey]

@Chazrox said in Roadmap to HISE 5:

modes?? Please share!

What you talkin bout Willis?

[Chazrox]

@d-healey lol

[d.healey]

@Chazrox Trigger, Note, Loop

[clevername27]

@Christoph-Hart Meanwhile, I was fired by all three clients because of HISE bugs and secret ScriptNode documentation. sigh

[Lindon]

@d-healey said in Roadmap to HISE 5:

@Chazrox Trigger, Note, Loop

yeah but how do they work?

[Christoph Hart]

@Lindon just like the ableton one which I completely stole the feature list from.

[Lindon]

@Christoph-Hart LOL damn! I don't use Ableton I will have to go look it up...

[Lindon]

@Christoph-Hart

damn it again. A quick cursory look and this doesnt seem to resolve the "Note Generator sends Global envelope data to non listening voices" problem....

[Lindon]

@Lindon maybe I should go away and state this problem clearly - there may be another solution...

[Christoph Hart]

@Lindon The note generation must happen one level below the global modulator container. You have to make sure that every voice that receives the global envelope data is started by the same event ID as this is the most robust way of assigning voice indexes.

So if you have this setup:

master chain
   global modulator container
      AHDSR
   sine generator
      Arpeggiator
      GlobalEnvelope / MatrixModulator

it will not work because the arpeggiator will produce new events where the global modulator has no idea how to assign that to voices. But if you either move the global container and the sine wave into a new container or move the arpeggiator to the root level it should work correctly.

[Lindon]

@Christoph-Hart yeah but sadly no _ want the arp to be shared(able) between voices...see my post:

Global Envelopes - The "filtered" voices problem.

So I have a problem with Global envelopes...I'd really like to use them, but..in a multi-voice system they are problematic....here's why (perhaps someone kno...

Forum (forum.hise.audio)

[Orvillain]

I'm getting a crash when using .setEffect() on a hardcoded polyphonic fx module. I'm doing something like this:

                modeData["polyRMSlot"] = Synth.getSlotFX(modePath + "_polyRM");
                modeData["polyRMSlot"].setEffect("polyRingMod");

This is in the context of a loop, and modePath is the prefix of the name string.

But interestingly, the crash only happens whenever I call Builder.clear()

IE: On the first run, it doesn't crash. But if I try to rebuild the module tree, then it crashes.

Going to try to reproduce this in a new project.

[Orvillain]

@Orvillain @Christoph-Hart

Right, I've confirmed this. Here is a demo project. Created on Windows. Not sure if you need to recompile the networks or not.

BuilderClearTest.zip

Shared with Dropbox

Dropbox (www.dropbox.com)

If you load this, the first time all will be fine. If you then press F5 to recompile the project, it will crash. If you remove the call to setEffect() then it doesn't crash.

I get a read access violation on:

if(auto pitchChain = dynamic_cast<ModulatorChain*>(getParentProcessor(true)->getChildProcessor(ModulatorSynth::InternalChains::PitchModulation)))

Details:

Exception thrown: read access violation.
hise::Processor::getParentProcessor**(...) returned nullptr.

In this function:

void HardcodedPolyphonicFX::connectToRuntimeTargets(scriptnode::OpaqueNode& on, bool shouldAdd)

Hopefully that helps resolve the crash!

[Christoph Hart]

Hopefully that helps resolve the crash!

Nice one, it should be fixed now. I mean the builder docs says that you have to expect crashes but this is in fact a reproducable one :)

IPP

I made another attempt at this subject:

• IPP on macOS and Linux is completely gonzo. You can use FFTW on Linux and VDSP on macOS (and ARM doesn't even support IPP so that was not very useful anyways).
• The USE_IPP flag is now an internal flag and must not be set explicitely in any setting (in fact it will deliberately fail the compilation if it detects it being set from the outside). There are now only two things that determine whether IPP is used (on Windows only):

1. In order to compile HISE with IPP support, the projucer setting Exporters -> VS2022 -> Use IPP (One API) must be set to "Static Library". This is the default now so people who want to build HISE without IPP on Windows must turn this off explicitely (readme is updated to reflect this).
2. In order to compile your project with IPP, you must have compiled HISE with IPP following step 1 and then set the HISE setting Compiler Settings -> UseIpp to true. If you set this to true without HISE being compiled with IPP, it will throw an error (this is not really required but I think anything that boils down the ridiculous amount of scenarios is a good thing here). If the HISE setting UseIpp is true, it will automatically set the OneAPI setting in the autogenerated project file and subsequently set the internally used USE_IPP flag for the project compilation.

[d.healey]

@Christoph-Hart said in Roadmap to HISE 5:

IPP on macOS and Linux

Why not on Linux? It works well here. FFTW is only suitable for GPL projects.

[Christoph Hart]

@d-healey Is there a single non GPL project on Linux?

[Orvillain]

@Christoph-Hart

Thanks for the fix! I'll check it, but I'm seeing this now:

Is that meant to be a comment, or a jassert or something???

Oh wait, I think I get you now. I need to remove use_ipp..... brb....

[Christoph Hart]

@Orvillain nope that's expected. If you hit this thing, it means that you have somewhere defined USE_IPP to a value which causes all the weird stuff you're experiencing. Check all preprocessor definitions