Beta Testers group

ustk

@ulrik A small precisions needed:

Do you need all resulting values at once or a unique value for a specific index?
And are the array values pre-defined or dynamic?

That would change a bit how you want to handle it...

ustk

@ulrik the question is: what's the size of your arrays?

if not too big (max 128?) you should be able to use slider packs
Above this, you might consider a third party node to which you send the data arrays with a cable, perform that simple operation in C++ (in the cable callback so you leave the process untouched)
Then you output the result to a third cable that you grab in the network. for the last part, I haven't done such a thing but it should be possible

d.healey

@Christoph-Hart @Dominik-Mayer I noticed the videos of mine on the HISE homepage are quite out of date. It might be a good idea to use a few from the Bootcamp instead.

ulrik

If I have some values in 2 arrays like this

tbl1 = [23, 300, 420, 570, 700];
tbl2 = [60, 200, 620, 880, 1200];

I also have a knob that has the range 0 -1.

If I would like to send the values between tbl1[0] and tbl2[0] (23 -> 60) in the knobs callback, I would write:

sendValue =  tbl1[0] + (tbl2[0] - tbl1[0]) * knob.getValue();

I will always go from tbl1 to tbl2, or vice versa, using the same index
How can I achieve this inside script node?
Where do I store the arrays, etc....

d.healey

@Yannrog Have you enabled the setting to embed audio files in the plugin?

Christoph Hart

@Yinxi nice catch. Today I learned that the loop end is inclusive in the audio chunk metadata :)

Curiously the loading function for the audio looper already had that correction:

if (metadata.getProperty(MetadataIDs::LoopEnabled, false))
{
	// add 1 because of the offset
	lr->loopRange = { (int)metadata.getProperty(MetadataIDs::LoopStart, 0), (int)metadata.getProperty(MetadataIDs::LoopEnd, 0) + 1 };
}

but the metadata parser of the sampler didn't use this yet, but the fix is trivial. Note that this will only apply to samples that you import and use the metadata information for extracting loop points - existing sample maps will not be altered as this would break any existing project.

it's always felt weird to me that there aren't any unit tests here.

There are quite a few unit tests in deterministic parts of the codebase (eg. the SNEX compiler is almost fully covered by unit tests), but the nature of audio software makes it super hard to cover DSP things like this.

d.healey

@dannytaurus Yes. The bundle format @HISEnberg mentioned only applies to MacOS (it is possible to make vst3 bundles for Windows but HISE/JUCE doesn't).

HISEnberg

@dannytaurus technically the VST3/AU are bundles that contain binaries and metadata (you can open them up and theres a bunch of subfolders/files).

But you should be good to go, just make sure Embed Audio Files and Embed Image Files set in the project settings (so they are distributed with the binary).

DanH

So this is actually the exact same crash report as a previous crash situation which has never really gone away. Occasionally and randomly happens when I'm moving the mouse across the UI / Sliders. Would love to get to the bottom of it!

Please let me know if you have any insight @Christoph-Hart

d.healey

@Yinxi said in Loop points clicking issue in HISE but not in other samplers:

You can try with this sample if you want, this one makes the issue very obvious.

Yes that one I hear it.

@Yinxi said in Loop points clicking issue in HISE but not in other samplers:

I’m wondering if I should add this thread to the bug reports list.

Yes make a bug report on github and link to this thread. It seems the import is off by 1 sample.

C	Christoph Hart
D	Dominik Mayer
O	oskarsh
O	Oli Ullmann
C	clevername27
G	griffinboy
H	HISEnberg
A	aaronventure
B	BM_FORUM
G	gorangrooves
C	crd
L	LeeC
Y	yall
M	Matt_SF
M	musictop
D	DanH
L	lalalandsynth
N	Natan
C	Casey Kolb
T	thomasmpcl

Beta Testers

Posts

Member List