@d-healey Thank you, I will figure it out how to use it, otherwise I'll come back to you again :)
You're very helpful, it's appreciated!

We‘ll definitely come to terms here. If you manage to contribute a working time stretching algorithm, I am more than happy to talk about exhanging licenses to use each other‘s work.

But apart from that the default licensing scheme for HISE is rather fair and if you‘re just want to go the GPL route to keep the startup investments down, there are smarter solutions. Write me an email then we discuss the terms.

@christoph-hart ok thank you..

God save the king @christoph-hart 🙌 :prince_medium-light_skin_tone: :prince_medium-light_skin_tone: 👑 👑
☺

@christoph-hart King... 👑 👑 👑 👑

Worth mentioning that the TimeSync value that is displayed on a label would also have to change between ms and time signature values on "SynctoHost" button control.

@Christoph-Hart Thanks for the fix!

Ah, now I know why I did this. The filter needs to divide the buffer in case of an incoming midi message, while the other master effects render the whole audio buffer at once.

Well I'll think about that Patreon thingie :)

@Dominik-Mayer: You don't need to require a Panel to have certain properties, just set it via scripting calls:

const var LinkPanel = Content.getComponent("LinkPanel"); LinkPanel.set("width", 100); LinkPanel.set("height", 20); LinkPanel.set("allowCallbacks", "Clicks only"); LinkPanel.setPaintRoutine(function(g) { g.setColour(Colours.cornflowerblue); // LOL // This method is bad (it squashes the text if the height doesn't match... //g.drawText("website.com", [0,0,100,15]); // Use this method instead g.drawAlignedText("website.com", [0, 0, this.getWidth(), this.getHeight()], "centred"); }); LinkPanel.setMouseCallback(function(event) { if (event.doubleClick) Engine.openWebsite("http://www.rbemis.com/orange/index.html"); });

Well, anything under Windows 7 and macOS 10.8 will not be able to load plugins build with HISE, so this is the only hard minimum requirement.

As soon as you use more samples than 5, add a SSD to the "Heavily recommended" list, as it really makes no sense anymore to stream samples from a spinning disk nowadays.

The rest is up to the complexity of the project as David said.

@hisefilo yes same. I think it's directly related to the bug I'm encountering with monolith files. When the plugin is initialized, it enters a state of unresponsiveness and times out. That forces Cubase to blacklist the plugin.

@christoph-hart I'm trying to use the MusicBox demo to check out the VU meter example code. Latest version of HISE (4/24/18) crashes on File -> Load new project.

you took me speed christoph

.hr1 is just only if you convert your wav samples to monolith.

Yes but for this use case there is the polyshaper which shapes the waveform on voice level and allows modulation.

Try it on a sine wave generator. You can get some really nice sounds out of it.

I do not know if it's the same thing. It is in the parameters under the name of "ui zoom factor".

@d-healey Thanks! I've been diving into the Interface Editor for the last couple days and am pretty happy with what I'm able to accomplish. And the linking widgets to parameter id's is a breeze.

But there are still some things I'll have to script and I'm unsure about how to go about it. For instance, say I setup a knob called "randomPitch" in the interface. I assign the processor id to "detuneRandom" (a Random Modulator in a pitch modulation module in the sampler container). I then assign the parameter id to "Intensity". Works. Great! But I don't want the knob to be able to go all the way 12. ;) This knob is for a chorus-y detuned effect, so I really only want it to have a range of +/- 50 cents. Well, I can sort of do this in the component specific properties by setting the "Max" field to .041 (1/24), but then the smallest step size available is .01....so not enough resolution for this type of control. So, I tried a little scripting. I put this in the onControl callback:

if(number==randomPitch) { const var detuneRandom = Synth.getModulator("detuneRandom"); detuneRandom.setAttribute(detuneRandom.Intensity, (value/24); }

where "randomPitch" is my widget id, and "detuneRandom" is my pitch random modulator module. A couple of questions about this:

Is the onControl callback the best place to put this script? I know from reading some of Christoph's posts, there are efficiency concerns with where to put scripts.

I also read on some post that the first value of the .setAttribute method should actually be an integer instead of a string? And that integer is an index of each modules parameter? Is there a way to to determine what index number pertains to what parameter?

Is this very simple code I thought would be easy, very wrong?

The plugin wrapper is just a discontinued approach to embed other JUCE AudioProcessors into HISE.

The Effect slot is a shell for an effect that can be used to dynamically hot swap effects using scripting calls to implement dynamic FX chains. The empty FX is just a null effect that sits in the effect slot until you load something interesting in it.

Thank you s much @Christoph-Hart Hise is growing so much. It will be capable of everything in dsp...

The appropriate structure of your instrument depends on what you want to do with the different samples. If you need to route them to different effects, use 3 samplers, otherwise one sampler with 3 RR groups.

I guess you have to write a control callback for the slider then and use Engine.getGainFactorForDecibels to convert to the required 0...1 range.