Posts made by Christoph Hart

https://forum.hise.audio/topic/429/load-font-example-please/10

Is the dynamics working on instrument plugins? And which host are you using?

HISE —help shows you the options for command line usage. I am using this for building projects on a build server.

It might be possible that it doesn‘t work on Linux because I only used it for macOS / windows so far.

https://forum.hise.audio/topic/626/discard-vs2015

You need to reinstall IPP with the VS2017 Extension.

Use the 2017 version

This and make sure you pull the master branch. I am doing a lot of work in progress stuff on the development branch which is not supposed to be used for "production".

No because it operates on synthesiser voices only.

Yes, sure a micro tuning script is a rather easy task. Just use an array of micro tuning detune values and apply this to incoming messages:

// This contains the microtuning values for each note in the scale
const var detuneValues = Content.addSliderPack("DetuneValues", 0, 0);
Content.setHeight(200);
detuneValues.set("height", 200);
detuneValues.set("min", -100);
detuneValues.set("max", 100);
detuneValues.set("stepSize", 1);
detuneValues.set("sliderAmount", 12);
detuneValues.set("width", 12 * 50);

// The Root Note for the microtuning table
const var rootSelector = Content.addComboBox("RootSelector", 650, 30);
const var rootNotes = ["C", "C#", "D", "D#", "E", "F", "F#", "G", "G#", "A", "A#", "B"];
rootSelector.set("items", rootNotes.join("\n"));

function onNoteOn()
{
    local r = rootSelector.getValue() - 1;
    local index = parseInt(Message.getNoteNumber()-r) % 12;
    Message.setFineDetune(detuneValues.getSliderValueAt(index));
    
}
function onNoteOff()
{
	
}
function onController()
{
	
}
function onTimer()
{
	
}
function onControl(number, value)
{
	
}

The user can resize the UI but in steps (125%, 150%, ...). Making it stepless would end up in plugin sizes of 102,38% and while it would still look OK when using only vectors, it would definitely mess up any image interpolation...

@d-healey said in IRCAM Modalys or PerColate ?:

Not that interesting to us but I noticed it has a super fast FFT that might be a good replacement for IPP @Christoph-Hart ?

LOL, the FFT was the first thing I swapped when I added WDL to HISE a few years ago.

Actually, WDL was lurking around in the HISE codebase for quite some time, but I've recently replaced it with the FFT Convolver library, which is faster and better code (the coding style of the WDL library is horrible).

Actually, the only viable replacement for IPP is FFTW, which is GPLed, or vDSP on iOS, so this will be the go-to FFT for Linux when I find the time to write wrappers for it.

What @d-healey said. The interpolation of images doesn't look too good across all platforms, but that's the sort of penalty you usually get when trying to make "scalable" UIs using images.

Hi,

actually I am also not 100% sure what's the correct behaviour for the slide value and I noticed you can change a lot settings in the ROLI dashboard app. But I agree the least invasive option is to leave the slide value where it is when releasing the key, so I'll probably change that

No but some bugs are more important than others and / or easier to fix.

Another possibility would be to use a note offset for the RR group. This works of course only for sample sets which don't span the entire keyboard (but for normal orchestral instruments with their limited range you should be fine).

Let's say you have 2 dynamic layers and 3x RR with a sample set that goes from C2 to B4 (3 octaves = 36 notes). Then you can map the RR1 group to the notes C-1 to B1, RR2 to C2 to B4 and RR3 from C5 to B7 and implement the RR logic like this:

reg octaveShift = 0;

function onNoteOn()
{
    local thisShift = (octaveShift-1) * 36;
    Message.setTransposeAmount(thisShift);
    octaveShift = (octaveShift + 1) % 3;
}

With 3 RR groups you have 127 / 3 = 42 note slots available using this trick.

It could actually use all channels to find the best loop point (just looking in the close mics might create clicks on the other channels).

Nice find!

The files AutoLooping.h and AutoLooping.cpp seem to be self-contained and could be used in another project (the rest of it depends on another GUI library called wxwidgets, which I don't want to embed for obvious reasons).

The library is GPL, so it should be no problem embedding it into the HISE Development code (it won't be included in compiled plugins, but that's OK, because by then you should have your loop codes).

There's much on my plate right now, but I'll take a look at it when I find the time (I was playing around with writing such an algorithm myself, because it's not too complicated, but this might be a viable candidate).

Nope, that's not on their feature list unfortunately so it's unlikely to happen...

Ask their support. They are super secretive about it so you won't get any information elsewhere.

this
|
V

@dustbro said in Compile errors ((:

Under FILE -> PREFERENCES , uncheck Use IPP before you compile your plugin

and:

https://github.com/christophhart/HISE#compiling-without-ipp-on-osx

Yes I totally fixed the hell out of that crash.
Just kidding still don‘t understand what caused this and what fixed this lol.

Ah good to know, thanks!

Ah ok in this case create the array in onInit and use the indexOf() method.

But don‘t mix GUI and Audio stuff. This has severe performance implications. What you need to do is to define this array as global, do the UI stuff in your deferred interface script (call Synth.deferCallbacks(true);) and the keyswitch logic in each script processor of your modules.