Latest Development Builds

[elanhickler]

I cannot find range slider as an option.

[Christoph Hart]

The slider widget has a new mode (Knob, Horizontal, Vertical, Range)

[d.healey]

Are development builds still available?

[Christoph Hart]

Just go to the download page:

http://hise.audio/download.php

(I added a automatic build system and once in a while I upload a snapshot). These are the latest builds.

[d.healey]

The download link for the latest Windows build seems to be broken

[Christoph Hart]

Yes I need to build it first I'll upload it soon.

[Gragon]

The installer isn't working for me either - has it not been put up yet?

Edit: tried the previous one as well, and it gave me an error saying something along the lines of "cannot expand [something] 64" - is this only 64 bit at the moment? I'm trying to get it on my 32 bit Windows laptop.

[Christoph Hart]

Sorry guys, I was pretty busy the last days, but now it's online.

I am currently working mostly on OSX so the Windows builds are not as tested as the OSX ones right now. However I had to fix some Windows related crashes before uploading the new build.

Be aware that this is not a release candidate, but a current development state that is far from stable. I introduced a new event handling system that needed heavy rewriting of the internal architecture, so it is not unlikely that it will contain some broken use cases.

RE 32bit, you should be able to select only the 32bit components in the installer. I can install the 32bit versions on my win laptop (which is 64bit though, but I can't imagine that the installer application itself is 64bit)…

[attachment=0:29bdi250]Installer.gif[/attachment:29bdi250]

However, I hardly use the 32bit builds myself. 32bit is kind of deprecated in the sampling world and there are some technologies (memory mapping etc) that need to make use of the bigger adress space of 64bit (even if you don't load up >4GB of samples into your memory). That's why I am using a fallback solution for 32bit streaming which is much worse performance wise.

[d.healey]

Excellent! the download link is working now. Does this new event handling system give us access to the event IDs?

[Christoph Hart]

Kind of yes, but I didn't add fading volume or pitch by event ID yet (so it's pretty useless right now). But from here it is not much work to do so if you want to play around with this feature I might add it in the next build.

[d.healey]

Cool I look forward to experimenting with it

[Gragon]

Still not working for me… I'm on 32-bit Windows 8.1. Specs aren't that good but that shouldn't affect my ability to install things.

[Christoph Hart]

Googling the error message yields some problems with the installer (Inno Setup) when the system is 32bit.

I'll try to fix it (or I can build a 32bit only installer).

[Christoph Hart]

Alright. Build 643 should have a 32bit compatible installer (among other bug fixes, the last development version was extremely unstable). I also added the pitch & volume fade events.

[d.healey]

Amazing work, can't wait to test it out

[d.healey]

What are the function names for the new fade commands? I can't find them in the API list

[Christoph Hart]

I forgot to update the internal list. These are the function names:

/** Fades all voices with the given event id to the target volume (in decibels). */
Synth.addVolumeFade(int eventId, int fadeTimeMilliseconds, int targetVolume);

/** Adds a pitch fade to the given event ID. */
Synth.addPitchFade(int eventId, int fadeTimeMilliseconds, int targetCoarsePitch, int targetFinePitch);

targetCoarsePitch is in semitones and targetFinePitch is in cents.

It is currently using only linear fading. And if you fade to silence, the notes continue to play (although I could add something like Synth.killEvent(eventId).

[d.healey]

Thanks that's great. Perhaps you could add an extra argument for the functions to determine if the voice is killed or not after the fade completes?

[Levitanus]

Hello! I've just last night saw this project and very impressed. Thanks for you work!!! Now I would like to establish whole the process of compilation to test my tryings as they would be finalized (GUI, optimization e.t.c.). Now i found the 5th part of tutorial about building the compiller and link to the JUCE is not working. Can be used JUCE fromte master folder from github, or it should be downloaded separately from official repository, or you have to upload required version again?

[Christoph Hart]

Hi Levitanus and welcome to the Forum.

The fifth part of the tutorial is a bit dated and I heavily streamlined the compilation procedure since then.

Basically you just need Xcode / VS2015, the plugin SDKs and the complete repository of HISE (which now includes also the JUCE source code and the Projucer binary that is needed for compiling).

If you're on OS X, this is the current list of steps. If you're on Windows, the procedure should be almost the same - just replace "Xcode" with "Visual Studio 2015" :)

1. Get the tools

You’ll need:

• Xcode / Visual Studio 2015 Community,

• The source code of HISE: https://github.com/christophhart/HISE/archive/master.zip

• The latest build of HISE which I’ve just uploaded here:
  OS X: https://www.dropbox.com/s/7yazh959ksok9zv/HISE.zip?dl=0
  Windows: tba (or you can build it yourself from the GitHub repo).

For legal reasons, I can’t supply the SDKs of the different plugin architectures (VST / AAX), so you need to download them and extract them in the specified subfolder after you extracted the HISE source. There is a Readme file in the subdirectory tools/SDK that explains every step needed to get the missing SDKs. If you want to skip this step for now, just select AU as export option (the AU files are included in JUCE).

2. Setup HISE

Then you’ll need to setup a few things inside HISE (I assume you have setup a project properly and created a user interface script):

1. Your Project Settings (File -> Settings -> Project Properties)

• Project Name
• Version
• plugin code (something like ‚Abcd‘).

2. Your Company Settings (File -> Settings -> Company Properties)

• Company Name
• manufacture code (also something like ‚Abcd‘).

3. The compiler Settings (File -> Settings -> Compiler Properties)

• point HISE to the folder where you downloaded the HISE repository
• choose „Use IPP“: No (unless you have IPP already installed).

3. Export your preset

Now you should be able to export your instrument into any target (or just AU if you didn’t get the other SDKs) via File -> Export -> Export as Instrument. It'll open an terminal window and launch the compiler from there so you can watch it work :)

The compiled results should be available in the Binaries/Compiled subfolder of your project.

Let me know if this works for you.