Thanks. I'll drop you an email in a bit.

Yeah I thought as much about the blurring - just gotta work out a decent way to slice and chop everything up always in even numbers

Well I have a template file I use when I create buttons that has all the states labelled on separate layers so it's never an issue. The only time I do the 1- trick is when I'm getting graphics from someone else and it's not really a big deal for me. I would be handy to have a flip feature I guess but I don't think it's going to be a deal breaker for most people - especially if they're coming from a Kontakt background

Yes I'll do that.

Currently it's right click :)

Yes. I'll put it on the Todo list.

Good to know, thanks.

Here is the most recent build:

Link Preview Image HISE_1005.rar

Shared with Dropbox

favicon

Dropbox (www.dropbox.com)

Also you might want to check what executable is associated with .hip files. This might lead you to the old version.

So yeah, it would be just a function for quick preview and setting up the start/end/loop points in the sample editor, so the playback should be separate from any of the modulation/gain/effects of that sampler module - just raw playback of the sample, modified by the settings you set up in the sample editor itself (volume, pan, pitch, loop/xfade).

Oh, another thing: Mouse wheel horizontal zoom to the waveform would be very useful if these workflow conveniences are implemented.

Cheers

To be fair i'm still waiting on licencing info before i learn too much, then i will look in to compiling and any turorials and such.

Excellent!

Aha! thanks, that makes perfect sense to me now. No I don't need a sample start one - at the moment anyway :)

Ah that's good to know. I shall play around with the filters some more. I'm just experimenting with various things at the moment to improve my dynamics crossfades.

Thanks :D off to build now!

Brilliant, I shall do as you suggest and I think it will solve the issue.

The problem I see here is that you have to define the tempo with one value only (so it can be connected to one parameter).

But to be honest, it is nothing more than a lookup table of factors to determine the time and you can implement a system like this for yourself pretty easily.

Yeah, there are only two, but since you can morph a panel into a button with just a few lines of code I'd like to keep the button rather simple.

I think this would be a case where it's better to just use a multidimensional array - the MidiList is a pretty small container which gets it's performance / usability advantages by limiting on numbers (its even not storing floating point, but simple 16bit integers). Making its slots dynamically resizable would defeat any performance advantage - you just end up with another multipurpose container type like the array :)

It would also be helpful if we could retrieve the current purged/loaded status of a mic position