Notifications
Clear all
Topic starter
November 23, 2020 2:53 am
It seems that this new facility you have added for the Zampler library creates a way of creating patches with user samples.
If you just check one of the patch folders, there is an SFZ folder with this header:
//-----------------------------------------------------------------------------------
// sfz Definition File
//
// this file was created with SKYLIFE's SampleRobot Version 4.8
// for Camel Audio's "Alchemy".
//-----------------------------------------------------------------------------------
and wav files that correspond to the lines in the sfz file. For just 1 or 2 wav files, it seem that it could be done pretty easily.
November 23, 2020 2:59 am
This method is not new; it has been documented in the Unify manual for months: https://pluginguru.net/unify/manual/doku.php?id=sampler-import.
The only thing which has changed with the latest beta is that Unify now tolerates SFZ files with only region lines, and the lokey, hikey, and pitch_keycenter entries on the lines instead of requiring them to be on a separate group line.
Topic starter
November 23, 2020 4:01 am
November 23, 2020 6:23 am
... Unify now tolerates SFZ files with only region lines, and the lokey, hikey, and pitch_keycenter entries on the lines instead of requiring them to be on a separate group line.
whoa! - Thank you! That's a very welcome addition! I've done some scripting to convert (unencrypted) Kontakt sample libraries to the Unify sampler format and this change makes that Lua scripting simpler and probably less error prone.
Cubase 12 Pro, Win 10 Pro (x64), several different midi controllers
November 23, 2020 4:14 pm
Actually, the news gets better. WAV sample files often have the loop-start and loop-end points encoded in the WAV metadata (because tools like SampleRobot put them there). It didn't make it into the public Beta 61, but Guru Sampler can now decode this information, and loop the samples correctly event without loop_start and loop_end entries in the SFZ file. (If those entries are there, they will be override whatever may have been in the WAV metadata.)
November 23, 2020 6:01 pm
Woohoo! Thank you for the Guru Sampler updates. These updates may sound small but make a huge impact. I will try this out once it's released. I use Ableton Live's Sampler to create loop points. Hopefully they embed the points in the WAV file. I don't actually know yet.
Ableton Live 10, Omnisphere, Native Instruments (Pianos), Spire, Hammer + Waves, Heavyocity (Ascend and Mosaic Keys), Diva, SynthMaster, Alchemy 1.55, Addictive Keys, Unify
Nico Fyve reacted
November 23, 2020 8:10 pm
Actually, the news gets better. WAV sample files often have the loop-start and loop-end points encoded in the WAV metadata (because tools like SampleRobot put them there). It didn't make it into the public Beta 61, but Guru Sampler can now decode this information, and loop the samples correctly event without loop_start and loop_end entries in the SFZ file. (If those entries are there, they will be override whatever may have been in the WAV metadata.)
wow - super cool! Can't wait to try that, too (for more conversion scripting including from Steinberg's Halion 6).
Also love your approach to default to whatever is in the wav file metadata, but allowing overriding via the sfz file. That's powerful!
Cubase 12 Pro, Win 10 Pro (x64), several different midi controllers
