@yall So I think your core problem is you are trying to use the preset system (which has no inherent ordering - they're files in folders) for something its not designed to do - load sample maps in order.

@arminh
first open a cmd window.

then type %APPDATA%

-- does that return the value you think it should?

@Lindon oh hang on...this is in a HISE compile right? So cant set this for each project? bummer...

@alepan did you install IPP? Did you enable it in the preferences?

@d-healey oh cool....

@ustk said in The things we all want to see in HISE 3.0:

@Lindon

1 - There are flags for that in the Projucer already
2 - Why not to build 2 different versions of Hise you can keep together?
4 - Never had this error...

1 - where?
2 - 2 different versions? I'm currently working on 6 different projects - so it would get silly..

OK so lets not all add the same thing eh?

some additional stuff:

• Extra definitions for the "load or update samples" buttons - so those buttons we see when the user first starts the product and needs to open the hr1 and save the ch1 files somewhere. It'd be nice to have the ability to decide on which buttons we want to see - some users get confused and press the wrong button...

• Extra definition for the background colour of the "system" dialogs. those dialog boxes HISE throws up - including "wheres your hr1 file?" and "where do you want to keep stuff?" - I know we can do this in C++ in the source code - but I really really dont want to have to recompile HISE everytime as a first step I work on a different product

• it'd be REALLY nice if we didnt have to restart HISE after uncompressing the Hr1 files...

• Id really like to have the "Audio Interface not found" error handled somewhat more kindly. Basically (and I hope this happens to a few of us not just me) if the product cant find the audio interface defined in the settings I'd prefer it to say "Audio Interface not set".

OK so I'm pretty sure @Christoph-Hart is busy working on many things including HISE 3.0, and like everyone else I'm looking forward to it - no matter what it contains - but I thought might be useful to develop a list of the things this forum had asked for. Clearly having something in this list DOESNT mean its automatically going to get implemented but having it will be either a reminder (hint) to Christoph or allow him to say "nope no way".

So I will start with some of the things I've asked for or I remember being asked for:

1. Send/Receive FX - as @Christoph-Hart and I discussed here: https://forum.hise.audio/topic/1983/feature-request-the-case-for-bus-containers/6
2. MIDI out - I haven't tried this so it might already be there - but some meaningful API documentation would be nice.
3. Extensions - yep I'm pretty sure this is coming in some sort of form..
4. OS specific Load/Save dialog - like Kontakt - it opens a load or save dialog in the OS...so the user can navigate around and get "stuff" we want saved to/loaded from wherever they like.
5. User content(wav files) loading to Sampler maps - it took Kontakt more than 10 years to get to the point of doing this - now its a BIG DEAL there... so it'd be a big deal here too.
6. Time stretching - I think @d-healey has covered this - RubberBand is a candidate .

Ok I dont want to monopolise - so over to you all...

@alepan start here...

https://www.w3schools.com/js/default.asp (you can safely ignore all the web/browser stuff - you want the language structure.//syntax parts)

@mwplugs the definative documentation is available:

https://www.w3schools.com/js/js_objects.asp