There's many combinations you could try here.įinally, you could artificially change the response of the sound you have: bounce the instrument to an audio track at half speed, then speed up that track again with a time-stretch algorithm like élastique. (But again if “chopping” is an issue you could cheat by duplicating the track and erasing every other note in each copy.)Īnother approach I would consider is to leave the sound as-is, but add another faster-attacking one on top of it, feeding from the same MIDI input. This will only work if there's no reverb on the track. feed the audio signal into another synth plugin that doesn't create sound of its own, only opens up a gate. You could trim this back with an additional envelope – i.e. If the attack is so slow that this is not enough, then the pre-fade-in would probably become untenable. Try first with very little anti-delay – 15 ms may be enough. Of course, when the sounds start too early, it may also be off-putting. It may seem like that shouldn't be possible, but actually it is – protocols like VST have an option to signal how much delay a plugin incurs (typically because of some buffered FFT), and the DAW then automatically compensates by moving the MIDI events earlier under the hood. Most DAWs allow you to set this up, or else you can do it with various plugins. If none of that helps, the easiest fix might be to just move the track forward a little, best done by applying “negative delay”. Many instruments also respond faster when played in the upper dynamic range, so it could help to “play in louder” and then reduce the volume in mix. Even if it doesn't have a dedicated “attack” control, there may be other parameters that affect the reaction time, or for orchestral sounds maybe different “playing technique” layers. The very first thing should of course be trying to tweak the instrument itself.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |