Roadmap to HISE 5

d.healey

@Christoph-Hart I decided to make a clean PR without the library in the commit history - https://github.com/christophhart/HISE/pull/755

You can download the .lib from my repo - https://github.com/davidhealey/HISE/tree/development/tools/fftw/windows

I intend to keep it in my fork since I'll always want it.

I added the windows sub-folder for the lib just in case in the future we ever need to put another version in there for some reason and keep them separate. But we could just put them in the fftw folder instead to save users the step of creating the sub-folder, let me know what you think?

Goodflow

Encountering a crash when using modulation assignments on UI controls with no assigned processorId.

Uncomment line 7 in the snippet
Hit Compile
Right click Knob1 and try assigning the LFO.

Same crash occurs if you try assigning via the ModulationMatrixController tile.

HiseSnippet 1595.3oc6YsraabCEkisYpsSaZRZPQQWMvnKbZScjrkUhQQgGaY6Tg3GBVJOZ6h.5YnjH7LjS4vwINEAnK599GzuitpO9C5mP6ptM+AsWRpGy3H+R4kaPzBAwm2CIO2ykWpZRgOMIQHQNS1X+XJx4cw02mqZWoMgwQUWA479XN8gQDkj8HEMQgVd+XRRBM.43L5szcxYhwPlOOcwkIgDtOseUHzcELe55rHlpes07tMKLbMR.sAKJSuK4U0WvqHBEo.fFEW.ES72kzhtIQ2sQvnuhjzF47o34mcN+RA2HX1Ymegx9jxzEZRZ1r3bAkJU9lKTbtEHktYYZg4QNma0.lRHqqH.5QNisrHX+5sEOjaMvcYIrcBo5BEQ0AKaqdMQXfdIpqEUoMKLnV2cpDDLo05uuMpce6J3MXArd02e+6hlFb6OhrafNijGdilCdEyBuBYf2.fjSFHMlERWBW2WxhU8aQimyiqxUTYSBbNkEJ19hF4IN3JBnGb0LQjcoqIgB8FwzkKT3ZtvWW8KlbR3rJQ4tGQ5ZoGteo6p7VLNcFeIEVOaHBRCIJlfugo8ompUnXGRXjHXp7i+1bwNEgg20vsnpJhnXAGJL8TlV0iv7iYRnPcwcWSUCl5ZSUmEEGRc0zQSGu90Ozt5ZLcyTtuFXtB9lBEcK9zWcxuexIl7IS5dvlZ1bfsogpTDFRkCrYMwVdTCbZdZzNT40f0eXJsWGgCu7LB7gyHxRX8s6bY5nfWkyTaES4GFMF0Y6Vyd5fJnqJC24Bc3N0CYATIhATj2Aa1TQF.2wo8u9me4m+MzcptBQQ5NMvLBVIlJUL8BvYE5dfDfkRNAdEZxtJQroucNgAQmi0nOpmJwObGu86Uv69dIJZbc1i6hHu+9w+3hV9XChDHRUCzZXIFFhlf.rRDv.6.Fe1NzPjh9H.EmCazyhxpo80+dDousQK6EwBBBo0DIL84YVktL7LyRICmDj7dFuSPWv5ejWrnCD633jyCU6ExA6teVI2WXJHmTHdIbMlxu8fw3HC.i.u3kAF6n69d3Ua1j5q5Cvwvqc+WNhrYM+3Vy+w3aYzz5uQAd..RncEa6I4cDAN+ySZfy3SbfyCJiL1ISF4Xh6M1Yt3dmTV6Gz4bxsWaIuB8sxEc9RVXhwqu1VFrY+0whlkYwhPhT29ZR52kR49YZebOMsnZeVk2O4cOxdzlBYTGs2dyz5zVvNP1ZZPAsX3he9YYf0iDBUaFuUdx1U7VWHhWkSfkdP1IoVaRhNdID0M2z.SaCwFDPnVVIT3ua1Fq1hKjTaL3r0WIMQIh5t.L28qNHzahy37s3xklA9z7yzeuPE3q415ES4SiVUwi9LejSL0DN9c6cjqYnmdp4XmLp4Q6eiNUHtGI7+AH9HCZM5a1As1Vjp.mX6cvA0lMSipCwI7of04bZn9RlNin84rkKnKabbo7.Sg+E9zowh5xNcZrX2FQ1I2dKvrq2KXWumGtMDmZRrzrZ+PSYWs6s6snPvR8oUwWsQH2xWAlugjvShEI4l35zHVC3poIYq7NITMieaM8ImRkfHGXSOcw0fE4.GSchJUZ3gKEIR44jKcF8sQtOibk3bR3SzEi1K1uJeOZHjkiAiWFxjnIIMT0s17b4MDbQbaAmkK751TvmoUKpLK1G3BZIkhjMr4U71lFRIYIseh25.YiH2vlYyvrWT7T+.CC775ivV35pc.cesmJy3ceKDqDUO.av5D3VcxHLaNLOuGW2MSBxG0Eop5cPe8g9zAYr41DdKpl1VkGmprkbvl7Yw3ByT.YxkEiKB+rJvTkJqhQAT+jnscrAjPLjIioKRsd8lvsvHgPOBpQgPGPNNZKsUp54zPfpJH1zMc5kR9Fpr6h7sg1OUoULdu2us2ScXL+AdIhCKF6m+f+3WWgFRxsQcOV.Dwt+ig3Mfnv1y2Z5TSN317KJ1ctnWGMWPujd8H5LnCiAq5bvWi53zdd5huU64ro1iNtO3x3dl9A6tL13Fe1FjWDWi7Zxw8URBRuoXiHhuT7.e6+VfV0abSMvdK27ezMAn3Akcy+2DX9DAIU7.e+7S0yLvYG1AN2vNvRC6.meXGX4gcf2XXG3MO9Apy4aoTkHx5+gPaTaU6ys4z6s9bFE8e7NdMTH

Is the new matrix_mod node scriptFX-only (as in not meant to be compiled to a hardcodedFX)? Also curious as to whether it's polyphonic-only like the "Matrix Modulator" module.

griffinboy

@Christoph-Hart

LFOs for custom parameters seems to be broken. The LFOs do nothing.

Does it work differently now?

Christoph Hart

@griffinboy Yes, that's the entire point of the update - you get complete control over the update rate and how the modulation is applied for each node, but I had to introduce a few breaking changes in the bridge between modulation and nodes for this (eg. the weird behaviour of switching to pan mode when the parameter range crosses zero). I'll write a "migration" guide with the necessary steps for bringing old projects up to speed soon, but in the meantime try changing the ExternalModulation property of the modulated root parameter in your scriptnode network before compiling as I would guess that this is most likely the thing that broke it for you.

griffinboy

@Christoph-Hart

Fantastic thank you looking forward to it.

I've just tested out the latest branch, it's exciting.
There is a disturbing issue I've found though, where one of my c++ synthesiser engines now aliases horribly, where it didn't in a previous version of Hise. I'm investigating it now. Strangely, a simple c++ sine synth doesn't have the same issue, I'm hoping I can track down what is the matter.

I'm rolling back Hise so that I can compare with an older build.
Maybe nothing is wrong with Hise, and it's due to some other mistake I've made. I'm hoping that's the case.

griffinboy

@griffinboy

*edit

The issue suddenly disappeared after clearing all the modules in the hise project and recompiling networks. I compiled the networks in an old build of Hise, then when opening the new build, everything was fixed. I have no clue at all what happened there. Maybe there was some issue caused by using an old hise project with a new version of Hise.

I was a few months behind after all.
How strange, sorry can't replicate the issue now!

griffinboy

@griffinboy

Okay I've replicated the issue. When compiling dsp networks as .dll in the new version of Hise (latest commit) something is wrong. My c++ oscillator aliases.

Wheras, when I compile in an older version of Hise
(HISE-6583025bbac9d7b4524de97e095dd2b85c6fd5be)
The node works as expected without any audio issues. It allows me to load this .dll in both builds of Hise. Which is odd too since there is a version mismatch.

I'm making a video one sec -

griffinboy

@griffinboy

@Christoph-Hart

Check this out!

Christoph Hart

Have you looked at the time-domain waveform? This should be visible there too and might give a better clue what went wrong.

You can also send over the node then I'll look if I can reproduce it but I can't think of anything that I've changed that might cause this.

griffinboy

@Christoph-Hart

I will send you the node if I can't find the cause.
I haven't had any luck yet, I'm going to download a few builds of hise and see where it went wrong.
I'm getting inconsistent behavior.

It may be tricky for you to troubleshoot my node, I doubt you want to sift through that code! It's a whole WT engine, 10 headers.

d.healey

@Christoph-Hart I saw you merged my fftw/ipp PR earlier, thank you :) Have you uploaded the FFTW library somewhere? I'm getting ready to update my videos with this new info.

Christoph Hart

@d-healey No but if you make a release on GitHub in the repo you linked above I can just link to the release page where people can download it.

d.healey

@Christoph-Hart Done, and I added the lib as an asset to make it easy.

Chazrox

I might have missed it....was there a date set for the next meet-up?

d.healey

@Chazrox Not yet

Chazrox

@d-healey sweet. Thanks.

Christoph Hart

Alright, guys, big documentation update just dropped that explains most of the things I've been working on the last month(s).

modulation system - matrix modulators & scriptnode bridge
wavetable synth - file drop & script controller including post FX processors
draggable filter panel - connect to any filter module

Have fun and let me know if you find anything weird.

d.healey

@Christoph-Hart Noice! Will have a read through this soon.

griffinboy

@Christoph-Hart

Awesome work, thank you very much.
Is there anything I should know about creating c++ nodes with sample accurate modulation, or is it the same as before?
(using parameters + hardcoded network)

Also, out of curiosity, is the new WT synth oversampled, and what kind of interpolation does it use at runtime? Looks fun! I see you took the FFT approach for the band limiting.

Allen

@Christoph-Hart
Thank you! That's awesome!
I'm ready to deep dive into the new wavetable engine!

Roadmap to HISE 5

28

1.8k

12.1k

105.7k