Notifications
Clear all

How I can use my own Samples in Guru Sampler ?


Boerni
(@boerni)
Active Member
Joined: 2 years ago
Posts: 12
Topic starter  

Dear John and Shane,

I've a lot of own samples that I createt an I plan to make a Unifiy Library of it. How I can use *.wav Files or how I can convert to gsd Files ?

Thanks and kindest regards from Switzerland
Boerni


Quote
getdunne
(@getdunne)
Member Admin
Joined: 2 years ago
Posts: 3098
 

Hi Boerni,

Importing your own samples IS possible, but it's not a user-friendly process yet. See https://pluginguru.net/unify/manual/doku.php?id=sampler-import for all the details.


ReplyQuote
Boerni
(@boerni)
Active Member
Joined: 2 years ago
Posts: 12
Topic starter  

Hi Shane, ok .... but ... I‘m not a masochist 😆 I wait until the PRO Version is out 😉 


ReplyQuote
SSquared
(@ssquared)
Member
Joined: 2 years ago
Posts: 178
 

It's not too bad if you have one-shot samples.  The difficulty comes if you want to loop it.  You will need extra tools to figure out loop points.  It is a very raw experience (not user-friendly as Shane mentioned).

It is really fun to bring in your own samples.  I started sampling my old Korg.  I didn't get too far, though, before I had more important music work to get done.

Ableton Live 10, Omnisphere, Native Instruments (Pianos), Spire, Diva, SynthMaster, Alchemy 1.55, Addictive Keys, Unify


ReplyQuote
Nico Fyve
(@nico)
Eminent Member
Joined: 2 years ago
Posts: 48
 

A great sampler can get rather complicated very quickly:

Multi-sampled velocity (or other controller) layered one-shots also get tricky, when wanting to cross-fade between layers.

Cross-fades across loop-points are an awesome feature, also not readily found in less expensive samplers.

And then there are various implementations of auto-sampling - a really big time saver for creating more complex sample sets.

But feature rich also means complicated - at least judging by how complicated HALion 6 is. Kontakt doesn't even bother with sample creation - and it's the 500 lbs Gorilla, that everyone is trying to compete with and that has now numerous highly capable developers who crank out libraries.

So Shane has a lot to consider, if/when getting into sample creation - including what enough people will pay for.


As an experiment, some time ago, I tested how a workflow between HALion 6 for sampling (since it's a rather feature rich sample creation environment, and has reasonably good implementations of the above features) and the Unify Sampler for playback might work. It actually can be made into a reasonable workflow with a bit of Lua scripting in HALion to extract and generate the required parameters from HALion and some WAV file embedded data into the Unify Sampler dialect of sfz. -- However, conversion seemed a small part of the battle compared with feature differences.

Converting non-encrypted Kontakt libraries is more cumbersome, but possible, too

 


Side note: I found SFZ not very satisfying as a meta-data format for samplers. I've bumped into too many dialects and extensions not always easily recognized just by the data set. SFZ seems a case study in the perils of attempted standardization without an overwhelmingly accepted owner of the standard - whether it be a leading developer or a standards body. Or a standards body bullied by a powerful company. 😀 

And like in any standards discussion, the question arises very quickly, what's part of the standard, and what's considered a non-standard extension? And then the boundary tends to change over time (see the evolution of HTML and CSS), making life harder for everyone.

While dabbling in converting between sampler meta-data formats, it felt worse debugging code when converting between formats that use the same keywords, but those identical keywords are used in a different context context from each other. It's extra mental gymnastics compared to having entirely different terminology between environments.

 

Cubase 11 Pro, Win 10 Pro (x64), several different midi controllers


getdunne liked
ReplyQuote
Share: