Libraries > Core

[Lindon]

@hisefilo Ok I will take a look - but I just tried it in a script FX slot assigning the relevent bits of function to the correct spot - onPrepareToPlay etc. - and yes it made strange sorta additive constant noise - I tried turning on the osc scope and HISE crashed - LOL...

OK tried your version - so a different strange (still not very pleasant) noise when you say sine not additive_synth - and less controllable from the interface...

[hisefilo]

@Lindon well this is something

. like a surprise box

[Lindon]

@hisefilo yeah but try saying this and the noise gets nicer...

function processBlock(channels)
{
    aasyn >> channels[0];
	//aasyn >> channels[1];
}

[lalalandsynth]

Is this for accessing the core Juce modules ?

[hisefilo]

@lalalandsynth I dont know yet LOL. The core library just shows 14 modules listed on my first post

[Christoph Hart]

@lalalandsynth said in Libraries > Core:

Is this for accessing the core Juce modules

Nope, it's just a collection of (very) basic DSP modules.

However I wouldn't spend too much energy on this system, it's most likely to be replaced entirely by scriptnode (and even if it stays in the codebase, the support will be minimal).

Most of the modules have a very limited usability in real world applications (I wrote most of them as proof of concept for the API, but since this approach never really took off, it's not worth trying to figure out how many parameters there are and what they do).

[hisefilo]

@Christoph-Hart mmmmm. you just killed my hope!!

I know Hise 3 will have scriptnode and snex. Meanwhile:
Whats's the recommendation to create a sinewave bank (for stacking upto 256 or 512 sinewaves) allowing to modulate for each, freq phase amplitude and envelope (frame based, or table based)?

[Christoph Hart]

What's "frame-based"?

TBH, a performance-critical module like a 512-voice additive synthesiser has to be coded in raw C++, with some low-level SSE accelerations in order to be competitive enough for a commercial-grade product.

[hisefilo]

@Christoph-Hart frame based was to say an amplitude value for each frame.

I see. mmmmmmmmm. To low level for me.

[A Former User]

Is very powerful with the supporting libraries.....well worth the rabbit hole.