Start a new topic

Custom Drum Presets

Hi Artiphon,


Any updates on whether/when there will be added functionality to the Orba 2 app allowing for user-customizable drum presets? I realize there are only 2gb of space available, but would love even just 2-4 customizable preset slots on the desktop app where I could assign all 9 keys. I primarily use my Orba 2 for on-the-go songwriting, and having a drum kit that matches the sound(s) I'm going for would be huge.


I realize that in order for the functionality to fully transfer on iOS, the user would probably need to send the drum sample files with unmodified file names to the associated preset folder on their phone. I've already done this with custom bass presets from OrbaSynth and I don't think it would be a problem for anyone with mid-level technical prowess. I think this feature would exponentially boost the value of the Orba 2 for anyone interested in quick, on-the-go production.


I'm about to write another request/problem I'm having with OrbaSynth, which is otherwise incredibly useful from a production standpoint. Planning on making a youtube review video as well. Thanks for keeping the updates coming, super excited for what's to come!



1 person likes this idea

Sharing current state of my custom  HangDrum  D minor as well, based on Freepats hang drum samples.


  • It is a Drum preset, not Lead.
  • Has a working shaker with some default sound. (It does not record however)
  • Bump action is assigned to the d5 note, that could not fit into regular notes. Still thinking if I should reassign to some kind of a percussion instead, need to play for some time to understand what's better.
  • Preset  is not tunable, it is just D minor and that's it.
  • Supports finger muting, except for the "bump" note.Seems to be in tune


Lessons learned:


  • "Bump" action seems to be hardcoded  always to generate note 39 no mater what.

that's how I ended with tuning="36,37,38,44,40,41,42,43"/>  to be able to map a separate sample to bump.


  • Shaker seems to use some default sample, I did not specify it and it still works.


  • I still do not actually understand how indexes, noteThresholds , tuning , note and note_midi play together, mapping is cryptic to me, I still am quite confused.DrumPatch seems not to be vital for playing samples, SampleDrumPatch is enough. Probably it adds some functionality on top.


Known issues:

 

  • Still no velocity mapping, unfortunately.
  •  Shaker sounds do not record.  However, seems like it does not work even stock presets, there is a separate forum topic on that, at least for Orba1
  •  Sended midi notes are lazy garbage, just some notes from 36 to  44, it does not map to drum midi or played notes meaningfuly. If you need to use orba2 as a midi controller, use some another preset.



---

Use on your own risk, bla bla bla, this is an authorized tinkering with your precious hardware, and  this preset made by the guy who owns orba for less than a week.  I do not take any responsibility for any damage you can do to your orba, ears or mental state.


zip

1 person likes this

>> an authorized tinkering 
unauthorized, of course. Omg these uneditable posts. Sorry for offtopic complains, but it is a pain, as soon as I have habit of making multiple edits to any post I write.

Can't wait to try your preset! Yes editing is crap. You can copy the content of an old post, then delete it and re-paste the content into a new post.. But lame.

@Subskybox


I've checked out your preset and I love the velocity-defined samples  and possibility to do vibrato. (Not sure if it works for real-life Pan, but I know it is possible to do something similar with Rav Vast).


Finger muting seems to be a Drums exclusive feature at this point, but it would be nice if I am wrong, still trying to find any param responsible for that for Lead.



@Ignis32


I had a look at the Drum attributes and you are correct they seem exclusive to Drum Presets. For melodic sounds there were a few attributes that contained the word "Hold" and "Release" but I haven't messed with these yet.

I chose 3 levels of velocity for each pad but I have more samples and I could add more. I'm still undecided on this.

I'm curious if you installed manually or if the app allowed you to add?

As far as I remember, I'd installed it  with an app, more or less without problems.


BTW, I'd played quite a lot with your preset today, as it is cool. And it feels like it is a bit quieter than other presets around - had to set volume on max and reduce volume for others, to hear it in a mix.




Thanks, I'll take a look at the samples to see if they are recorded low. There might be some volume related attributes too for me to look at. The samples I found were recorded at 5-7 levels for each of the notes they recorded. So the ones at lower velocities are naturally quieter. I may want to try to normalize them a bit so the more quiet samples are closer to the louder ones.. Who knew developing a good Preset would be so much work.. I guess that's why Artiphon partnered with another company :)

I was wrong about samples format, Audacity lied to me, making some underhood conversion that I did not ask for. All that white noise was because I used 32bit float that Audacity showed me, and samples started working when I accidentally exported them in a correct format.


Actual format for the Orba2  samples is  PCM signed 16-bit little-endian 48000hz. as shown by https://www.metadata2go.com.
---
Sorry in advance for any people who will read my earlier post with invalid information that I cannot edit.


@Ignis32 

I had a chance to download your FreePatsHang Drum Preset and play with it a bit. Its Nice! I really like the muting feature and it seems to have some basic velocity that the notes get louder with more velocity. :) A few packaging suggestions.. It looks like most of the Preset images are 500px x 500px (but it probably doesn't matter since your image worked). I noticed that your folder in the SamplePools doesn't have a UUID but it appears to be standard for the User folder (see what happens when you use the app to make a custom sample preset). Also I think it will be best to wrap everything in a Common folder so that one can simply drag the Common folder into the Artiphon folder and install in one action. I'm curious what you used to generate UUID for the .artiPreset file since it contains the UUID in the file itself? I just grabbed the MD5 of the file with UUID="" and then once I had the hash value I inserted it back into the file.


I'm going to start a new Forum on the weekend: Orba 2 Preset Makers Forum. I think there is a lot to discuss there and still many things to figure out. I have lots of theories to discuss.. For example Drum Presets seem to support bends and flams :)

>> I'm curious what you used to generate UUID for the .artiPreset file since it contains the UUID in the file itself? 


Not sure at this point, but most probably I used md5sum of the main part of the preset name.

Like   {BlaBlaBla}_{md5sum(BlaBlaBla)}.artipreset


The same as for wav files that  was  {abc}.wav  -> {abc}_{md5sum(abc)}.wav


---


Mangled it by hand when could not replace old samples with new versions at some point, being unable to remove old. 


---


If we want to write down a guideline for safe UUID generation, we might think big, like what if hundreds of presets would be generated this way. And here it starts to be interesting.


As for wav files -  initially I've seen two ways here -  calculating md5sum for the file content, or for original sample filename without uuid.  


What is better depends on anwser on the question "do you really expect a new uuid each time when you modify a line in xml or update sample?" My answer is no, as I  during development I update preset and samples in place and want them to have the same names each time, therefore I would prefer generating uuid from filenames.


But both of these methods might generate already existing md5sum uuid, and who knows what side effects that could have.


One method fails if you use same favorite sample for different presets, another will fail for the same original filename - and generic  stuff like "shaker.wav" original sample appearing during different authors preset generation is quite probable


I would suggest using combination of  subDirectory name  + original_filename as a seed for checksum, like md5sum("PanDrum:D3ppf")


Same issue with artipreset uuid -  main preset name can be the same for different instruments. It could be PanDrum for  lead, PanDrum as drum.


Therefore i suggest Instrument_type+presetname, e.g.  md5sum("Lead:PanDrum")


>> I noticed that your folder in the SamplePools doesn't have a UUID but it appears to be standard for the User folder (see what happens when you use the app to make a custom sample preset).


I did not notice any problems with that yet, but still better to do the same as Artiphon does, so it makes sense. Will follow this convention next time.


>>  Also I think it will be best to wrap everything in a Common folder so that one can simply drag the Common folder into the Artiphon folder and install in one action


I do not see nor benefits nor downsides in each of the approaches particulary, but it will be obviously better for everyone to follow one single convention for the custom community presets packaging, to unify installation. You preset was first, so let's do it your way, and start with Common folder.

Will follow this as well.






I don't think there are really any standards for UUIDs that I can spot from Artiphon.. In the end, it doesn't matter as long as they are unique.. Even that doesn't matter so much since it seems like app.properties seems to handle duplicated UUIDs (think collisions/binary trees).

One point to mention is that the UUIDs they don't have to be correct (they are never validated by the app.. at least for now), so there is no need to update them during development.


The Common folder idea just lets you drag one folder into place and it will merge everything into your Artiphon Library. Otherwise, those who want to install Presets will have to drag in 3 folders into Common. Just trying to make it simple for non-technical people who just want to enjoy new sounds but not make them.

Login or Signup to post a comment