New feature: Release Start
-
@Christoph-Hart Does this work?
HiseSnippet 1404.3ocyX8rTaaDFeElMM3lloISNzC8fNR5jRsv1XxjoSLXrCzfAOVjL4lmEoU3cPZWMqVQhalL8ZdK5qPeD56PeD5wdIuAseqj.IY7jXbojxAPe+S6O88+kARgCMJRHQFUOZRHEYbGr8DtZbmwDFGs2NHi6h6ShTToYJqsmDRhhntHCiJOSyvXkkQI+7gmtMwmvcn4rPnWJXNz8YALUN2AseNy2uGwkdDKnf1MZumif2Q3KhA7TAWCERbNkbB8.hVskvncIQiQFeG9wMaZQb8Z4YU25wG654Pq2p1FMZsNo4lddspY0ntaKuF.HuUWWlRHsUDEMBdoaKbmXOV7Zd5A7RVD6XeplvBYCmbJaTmwLe2Am6bhPHC7fbWUkTW0Cv8YtrK3m6x95DAl4VTzoYrzGCRVWAHYT.RKmBo6gscjrPUtDMd9R7dbHB5QfXSQnjpKx3OwcDfBb0ZAjSo8j.wEFr5F0p8HS3WO7IUq1i4Ssm.YCAq4KHtceCIHzmtE79TQqpUvKl6nXBtofefPQOju5Cq91pqT8cUMmVjm2LkoQhT36SkyTrNiQ9wLbUdbvwT4iLOi3GSuPQvCU1seq4ys6j5XJnnfuGmoNLjlQ2S36pcm5mubPBk4Ygmdwd6PTDcbKiGnWHUpXZ3XrC8LnRIMJtBdGZzoJQHTqboPLjbIbi8IpxYb5ZwLAf+nTXVGK4QL0jh0pWgzvZezzv4Eh2COfobFOaLtzLvH3o9u.iYEueEtqmG0QkCvkw8d0hVoV6JWoVMqRENS8gemLRyduxZl0nuGmmrGJogDI8Hw.exjUiRJBGBX7QlG6KbN0l8yzKWgDlBgs0ZrpyXBmS8iVjBI70T+KzPQrhwOoOQIYuAduGDGXCs9cncxPGvyXIcMTJcMMsNuvlxcSH9a3mLgVZZiLgVmK7Zr76aSEdersRRIA.vsSb7osXgvYJk00wDxv4dB4.IU2IVGxyU62aucLjbKKy82ZmbTaEHh4kNqLjOjFRIJn9rfM2t8vgOSJhCm1pO7zjp4ijvDZvUTTvgbJjNnJ9M1QJhh7fOmj2UTQQChkmn8U4bFROiJiJyCRMJlTniyuHhpSAYNmm+jqcxoT6HRRZHr1PBs0TzqOEc8onaLEcyon2XJ5V4zSWhLmyZ5SBGPfOwBZtMKKKCjkxobe9BpNi1N25yvNKWOCK9LNOqTy5UNGi1LcTnK+LnbC3nw38g1DdjXe04bKW52WvEgiEblS4jaHY8jSnxhXelePaoTPsUNmGzdH0mRhxqNe+ezdeFmRjkqYuR9hq9JlyLd8M3T3Zp6WY9uIts77E29DacccrSRk4Zmjqc79YX+j40cc2rgblvIJU+ObGy6fSZEapmbdSBuahMYNekMcUY1yIKzXTgx0SdRVi1Glc5WLcMBVDPCIXpDJcQw.8jDr1asBNfHYAGSPSMjW+w2m4LP.dLnnP6ZvOAYSNil1ooBd8BizIAAjRtUizCBJuFJz6ArLdiln8EOmNI64cYYO2xB3+RMhScG6xxH9EsSMETY2xBt4Y5+FfeD+1ACO7m514nQ8Nb+c5N7c8S+J9gr+NZLSM5v3r9ri5UeT.0cTMq0dM4LzNwg9LGHdqyJ1W7ZpDNQgCjY7pjjljH7ABY.wGVdJqf8EggyTO6K17FY7E3FMrpACwg199L0X39svsh0N45MpuQyFMtPx9T9IpwHiaiWud8FsVG1.zOV+ksL962rvYOfRNUe28lMVqUyVVVahxF.jV8Ado+5Wugx8BHNRwHmzKFny.ucBGvKvShIqf6qoMsPIWVnXBX.rUwHGmxupKY35Kpg0WTCarnF1bQMbiE0vVKpga9oMTuz2VwJQP53ODp+ftosUL5dQakJn+A.7DcGlNote that you need the example assets from the snippet browser (Tip of the day: this is a neat way of checking things with a generic samplemap).
EDIT: You have to load it twice. The first time the samplemap cannot be found because it's loaded before the asset manager is initialised from the script. UX powerhouse!
-
@Christoph-Hart It tells me it can't find the monolith. I have downloaded the assets - well I think I have, where are they downloaded to? I notice the downloader seems to glitch out at the extraction phase so maybe something went wrong.
-
Ah I just reminded myself of the snippet browser docs, seems the assets are in my snippets folder. But the snippet you posted is failing to find the monolith.
Seems like it's looking in a "My first project" path which isn't where my snippets are stored.
I've copied the files over manually and now the snippet loads, and the release trigger works as expected. Do I have to compress my samples to a monolith in order for the release start to work?
-
@d-healey no, it should work in all configurations (I haven‘t explicitely tested multimics but there shouldn‘t be a problem).
-
@Christoph-Hart I'm using multi-mics, I'll do some more tests and see what I can find
-
@Christoph-Hart It works with a single mic, but multi-mic seems to break it.
-
This post is deleted! -
Bump bump
-
@d-healey Fixed now, I just forgot to add the code for the multimic sample voices.
But nice of you to upload marimba samples that are processed by the
Waveshaper OF DEATH
I almost blew my ears the first time :)
-
@Christoph-Hart said in New feature: Release Start:
Waveshaper OF DEATH
Ooops :) It's actually the the natural sound, it's a really cool instrument with buzzing membranes in each resonator.
-
-
What would be the best way to temporarily disable the behavior on a per-event basis? When scripting legato, you sometimes want the sustain to go to a release sample, sometimes to a legato sample.
-
@Simon I've discussed the same issue with Christoph and I believe he is working on a solution but for now use a separate sampler for releases - actually there are a few advantages to this so I'll probably keep on doing it this way for most of my libraries.
-
Stopping by to say hi! It's been a while.
@Christoph-Hart I'd like to point out one crucial detail regarding release notes, which I tackled in my software with the hi-hat open/closed release notes.
It is not enough to just have a release note for a sample. For the playback to sound natural, the gain of the release sample must match that of the main portion of the sample at the moment when a note is released.
So, if you release a note when the peak is at -15db, the release note gain should not be the same as when you release the note with a peak at -30db.When I say that "it should match," I do not mean necessarily that the release note must be played at the same gain value as the main sample when released (eg. -15db sample peak with -15db peak of release note). I think that the overall balance (main sample/ vs release) needs to be adjusted by ear, as I have done, but a simple formula can get a good ratio between main sample and release note. Adjustment by ear is to get an overall loudness of all release notes in the sampler.
When done properly, any released note sounds natural.
-
Read the link, Release Start already includes exactly what you're describing!
-
@Simon oh, sweet! Thank you for that. Then, the feature is truly wonderful
-
If I play a note and release quickly I get a kind of pop sound as the release is triggered. I've tried various start options and adjusting the gain envelope but it doesn't seem to change it.
Also, is there a way to toggle the releases feature on/off? I'm thinking some users prefer to disable release triggers.
-
I'm at the release trigger stage of my current project and would like to use this nice shiny feature. In this post I'm just going to summarise some of the things we've discussed so far and suggest a couple of extra.
-
It should be possible to disable/enable release triggers via scripting, preferably per event - per sampler or globally would be ok but less flexible.
-
During legato transitions releases should optionally be disabled - depending on how 1. is implemented we could manage this ourselves via scripting.
-
If it's disabled during legato it doesn't necessarily mean it should be disabled when chords are played, so some kind of optional chord detection is required - again if 1. is flexible enough we can handle all these weird scenarios ourselves.
-
Although we already have various volume matching modes, it would be good to be able to dynamically add a gain offset via scripting which is applied after the matching.
-
Currently if I hold a note so it played through the sample and past the release start, when I release the note it will jump back to the release start point. I don't think this should happen, I think it should just turn the note off and the envelope can take over - unless the sustain pedal is down.
More generally, how should sustain pedal be handled? Currently it doesn't seem to affect the releases. I think in some cases we might want the note to not reach the release as long as the sustain pedal is down (assuming the sample is looped).
@Christoph-Hart If any of this is beyond the intended scope of the feature, let me know and I'll just carry on with my current system.
-
-
@d-healey nope this are all good suggestions - I‘ll add a script API method to disable release triggers per voice using the event ID - this should be enough for most of your feature requests, the other things are minor issues that I can fix easily.
-
@Christoph-Hart said in New feature: Release Start:
per voice using the event ID - this should be enough for most of your feature requests,
Yeah I think that is a great idea :) thanks.
