@Lindon - No such luck! There's a lot of inconsistency from the old electronics, I suppose, and finding that perfect loop point on all the samples is not practical. There doesn't seem to be an automatic zero crossing snap in the UI either, which can be helpful.
working on the Sensel Morph, investigating HISE to see if it's a good fit for some projects
Posts made by pnyboer
RE: Crossfaded looping in sampler
MPE tile & MPE modulators disabled on project open
I've added several MPE modulators to my project. When I first load the archive or XML, they are all disabled. They also lose many of the properties I setup, for example, an MPE modulator for gain was setup with a special curve and to respond to Slide - but when I open, they are all defaults:
Related: In my interface, I have an MPE floating tile, but I'm having similar issues to the old thread here - MPE Floating tile problem
@A-Former-User mentioned he figured it out, but I'm having a hard time finding any documentation about it or the sample MPE project.
Links and Help appreciated!
Crossfaded looping in sampler
I'm playing with some pretty static waveforms from a vintage oscillator. I'd like to be able to get a continuous loop from the sample, which I've been able to do in other samplers (Bitwig for example) with these same samples. However, it doesn't really seem to crossfade the ends, it simply seems to fade in the beginning? There is a pronounced ducking on the loop.
Click fo Example audio of the ducking at loop points
Is there another way to get a seamless loop in the sampler?
RE: Notes on my first try....
@ossian1961 - I expected the "HISE.2.0.0.pkg" to install the 2.0 standalone - is that incorrect? I realize that best practice is to compile the standalone from source, but I'm just getting my feet wet!
@Lindon - thanks for the tips. The Archive format is what I was hoping for. When you save as XML, that doesn't seem to be the whole project - samplers, modulators, interface. It only seems to be the Master Chain. Is that correct?
RE: Notes on my first try....
Also unclear to me is how to save a project. I just quit HISE Standalone, and it gave me an error that it unintentionally crashed. When I reopened, and tried to open the project I created from following the tutorial, all the interface design was gone! Probably an RTFM situation!
Notes on my first try....
Here’s my notes.
After one try at the tutorial, I found that I should start with the latest release from GitHub, not from the downloads page on the HISE site:
The Mac package currently claims that it is version 2.0, but the About window in HISE Standalone shows “version 1.6.0 (19 Nov 2018).”
If you go through the tutorial, the Interface section is a bit wonky. This is addressed in the forum
Though, in the end, I was unable to make sense of the “FloatingTile” interface elements so I could add presets and keyboard. I will have to dig in more to understand those.
I was able to latch the Reverb Amount to the ReverbSendGain and the Room Size to the Reverb, which was all pretty neat. I didn’t bother fleshing everything else out - I just wanted a couple parameters to work.
Exporting to a VST was trickier!
In my settings, I always got an error that my BundleIdentifier of com.sensel.HISEtest was an incorrect format. I eventually just ignored it, and did not set it to default. I ended up setting it in Projucer anyway (see below).
I am on macOS Sierra, so I couldn’t use IPP. Disabling this was pretty confusing. I followed the instructions at https://github.com/christophhart/HISE, but every time I tried to export from HISE Standalone, it failed. I directly edited the Projucer file, but export always rebuilt it with the IPP paths enabled. I ended up compiling from Projucer, pressing the “Save and Open in IDE” icon and then building from Xcode. This created the Debug version of the plugin, but did not rebuild the regular version. This is unclear to me why it only created that one. I didn’t see any relevant errors.
I finally got to try out the plugin in Bitwig Studio 2.4. It gave the warning to find the samples, which was all very confusing - Part 5 of the tutorial seems to miss some steps about this.
I somehow eventually stumbled on the need to generate an hr1 file using “Export Samples from Installer” in HISE Standalone. Once I did that and was able to point my plugin to that file, the plugin worked. However, only the generators made sound. It wasn’t until I deleted the plugin and reloaded it in Bitwig 2.4 that I was able to hear the samples playback.
All that said, it’s pretty exciting to see how I can build a sample-based plugin pretty quickly with this. It a bit more work than Kontakt, but it’s definitely more powerful and will likely provide a better experience for end-users. The tutorials could use a bit of cleanup and extra links, but it's impressive that I got this far.
Looking forward to trying more!