What's new

For Those of Us Considering Jumping from Kontakt to HISE

Okay so major updates are now coming in weekly doses, not monthly(well for this month at least):

Yesterday V3.5.1 was released, the major major major(did I say major?) update is time stretching / pitch shifting is now available.

So you get pitchshifting without time dilation and timestretching without pitch changes. Available as a feature of the Sampler and as a single audio file player.

So let me be the first to say welcome to all our new loop-content owning friends....and to let them know I have development slots available (well if I cant plug my services now and then....)
 
Not so fast :)

3.5.1 isn't released yet, I just wrote this version number in the docs so that I don't have to edit them later again. The time stretching is still very experimental so it might take another few days and feedback from developers until it's merged back into the main branch.
 
Not so fast :)

3.5.1 isn't released yet, I just wrote this version number in the docs so that I don't have to edit them later again. The time stretching is still very experimental so it might take another few days and feedback from developers until it's merged back into the main branch.
oops sorry - just obeying Obermeister Healey's commands...
 
@chrisboy

On your side it says:
To distribute your plugins you can either offer compiled binaries yourself or create a library for the free Libre Wave Rhapsody player, if you want to skip the compilation procedure.
Could you spell out for me what entails offering your own compiled binaries? My only real exposure to programming is less than two years ago with KSP (and GML), so I just don't know what that means at all.

But HISE looks cool, and over the long term I'd be interested in making the jump.
 
Could you spell out for me what entails offering your own compiled binaries?
You install Visual Studio on Windows, and XCode on MacOS. From within HISE you select to export your project and this will create a JUCE project that can then be compiled - turned into a plugin or standalone app.

This is tricky for a newbie (I struggled at first) but once you get the hang of it it's easy (until Apple releases an update anyway).

Next you need to codesign your plugin and build an installer (Whitebox Packages on Mac, InnoSetup on Windows). On MacOS you need to codesign and notarize the installer too. On Windows you don't need to codesign anything, but you should if you don't want your users to get popups telling them your installer is a virus. This stuff is a pain in the butt (and a bit expensive).

Once you get into a rhythm with this process it's not difficult and in fact you can use scripts to automate the whole process which makes it a one click procedure. But getting there is the hard part.

The first thing you should do though is compile HISE. Because compiling your projects is exactly the same process, so if you can compile HISE you should have no problem. I have some videos on YouTube showing this process.
 
and XCode on MacOS
Or VS Code on either, hehe. Lotsa devs really dislike XCode for... all sorts of reasons.

I also wouldn't really recommend Visual Studio on Win. It's old and sluggish. VS Code is way snappier. Visual Studio does have great debugging tools, but that would only be needed if somebody gets really serious about development. By and large, the debugging tools from the native C++ extension of VS Code are perfectly sufficient.
 
I actually love VS2022 + the Resharper extension, it‘s a beast. But yeah Xcode sucks so bad it‘s not even funny anymore.
 
@d.healey Thanks, that makes thinks a bit more clear.

On Windows you don't need to codesign anything, but you should if you don't want your users to get popups telling them your installer is a virus. This stuff is a pain in the butt (and a bit expensive).
How expensive roughly? This would need to be done and paid for per product, right?
 
@d.healey Thanks, that makes thinks a bit more clear.


How expensive roughly? This would need to be done and paid for per product, right?
No this is an annual payment. You need an Apple developer account, roughly $99 per year.

If you want to go down the Windows signing route you need to pay the cartel. The price keeps going up. There are various companies selling signing certificate, I went with this one - https://signmycode.com/comodo-ev-code-signing

If you're not a registered business though expect to have difficulty getting an EV certificate.
 
That does make the whole thing a bit more unsexy.
Releasing for your Rhapsody player would then bypass all of this with the "downside" of needing to put the source code on GitHub, did I got that right?
 
Releasing for your Rhapsody player would then bypass all of this with the "downside" of needing to put the source code on GitHub, did I got that right?
Well I think it's an upside :)

But no actually you can release a proprietary instrument with Rhapsody. However anyone will be able to view the source code because the format used by Rhapsody can be uncompressed back to the original HISE project. The samples are not affected by this, just the data.

Also, if you do make it open source, there is no requirement to put the source code anywhere public. However if someone asks for the source code you must give them access.
 
Ah ok. Well, as soon as I have a simple instrument again, I might go for the Rhapsody version, maybe make it for both Kontakt and Rhapsody (or even Decent Sampler too, while I'm at it :D)
 
Ah ok. Well, as soon as I have a simple instrument again, I might go for the Rhapsody version, maybe make it for both Kontakt and Rhapsody (or even Decent Sampler too, while I'm at it :D)
Send me a message if you need any help
 
This is not at all required. Surge is a signed binary on Windows and we didn't need to do any EV signing. At least IIRC. Lemme investigate.
EV is not required, but if you want EV then you need to be a business, last I checked
 
Top Bottom