Sitala drum sampler, new release with multi-out and MIDI mapping

[scotchi]

So how does this find samples thing work? I can't for the life of me figure it out, and it doesn't seem to work automatically? That was also the biggest nuisance for version 1 for me.

If you load a project with a moved sample, we prompt to update it when the project is loaded. If you choose not to do that on load, it's possible from the GUI too.

[cuppa]

Hi
I'm not getting this missing samples message in reaper, should i perhaps uninstall version 1? Win 10 x 64, latest reaper x64
Thx

[scotchi]

Hi
I'm not getting this missing samples message in reaper, should i perhaps uninstall version 1? Win 10 x 64, latest reaper x64
Thx

Is it loading Sitala 1 or Sitala 2 in Reaper? (You should be able to tell by the look and feel, or check the about dialog.)

Sitala 1 and 2 use the same installation location and VST names, so normally it's pretty hard to have them installed side by side.

[scotchi]

I still think the ultimate drum sampler feature for working with one-shots is velocity > micro pitch and sample start point. Hopeful for V3?

Just to see if I understand you -- you mean the velocity controlling the sample start and pitch? Could you explain a bit more? Right now Sitala does use velocity to control the volume of playback, so that'd be a pretty big change.

We'd love to add velocity layers in general, and I could imagine something like that being part of it (e.g. "duplicate layer", then adjust one of those params). Part of what we're waiting to see is how well sales go this round to decide how much we can set our sights on for the next release.

[Hewitt Huntwork]

I still think the ultimate drum sampler feature for working with one-shots is velocity > micro pitch and sample start point. Hopeful for V3?

Just to see if I understand you -- you mean the velocity controlling the sample start and pitch? Could you explain a bit more? Right now Sitala does use velocity to control the volume of playback, so that'd be a pretty big change.

We'd love to add velocity layers in general, and I could imagine something like that being part of it (e.g. "duplicate layer", then adjust one of those params). Part of what we're waiting to see is how well sales go this round to decide how much we can set our sights on for the next release.

Sure. The velocity still controls the volume, but it also controls a very narrow pitch window and a very small sample start window. So, at lower velocities, not only is the volume lower, but the pitch is ever so slightly lower, and the start point of the sample is just a little bit later so you get a very tiny bit less of the attack. The overall effect brings one shot drum samples to life by creating small variations, but ones that are consistent with nature. A drum that is hit more softly would be a little bit lower in pitch (we're talking fractions of a semitone) and just a little less attack than a drum that is hit with full velocity. XO does this, and Atlas 2 (neither by default, you have to go in and monkey with the settings). Once you wrap your head around it, it's a cool effect.

[xbow]

Is it possible to save all the samples of a kit into a folder in 2.0?

This would probably convince me to pull the trigger and get a license. It would be very convenient to assemble kits from a large sample collection, or by slicing a loop, and then save the files to a folder that can be copied over to a hardware sampler.

[scotchi]

Is it possible to save all the samples of a kit into a folder in 2.0?

This would probably convince me to pull the trigger and get a license. It would be very convenient to assemble kits from a large sample collection, or by slicing a loop, and then save the files to a folder that can be copied over to a hardware sampler.

That's honestly something we've never been asked for. Right now there's no process to export all of the samples to a particular location, but Sitala kit files actually contain the samples, and Sitala kit files are just Zip files, so you can get basically there by creating a ".sitala" kit, renaming it to ".zip" and then unzipping it.

I also had a testing version sitting around where you could drag straight from Sitala pads into Finder or similar, but that didn't make it into the release (mainly because I forgot about it -- originally was trying for the iPad, but it didn't work there).

[xbow]

That's honestly something we've never been asked for. Right now there's no process to export all of the samples to a particular location, but Sitala kit files actually contain the samples, and Sitala kit files are just Zip files, so you can get basically there by creating a ".sitala" kit, renaming it to ".zip" and then unzipping it.

I also had a testing version sitting around where you could drag straight from Sitala pads into Finder or similar, but that didn't make it into the release (mainly because I forgot about it -- originally was trying for the iPad, but it didn't work there).

Thank you for the quick reply. Very helpful to know these are zip files. With 7Zip installed under Windows, the files don't even have to be renamed, you can right-click them and extract . (I just tried with a Sitala 1 kit).

So if I slice up a loop in the new version, will it save individual one shot files in the zip?

[scotchi]

So if I slice up a loop in the new version, will it save individual one shot files in the zip?

No, but that's because it's not designed to be an export function (it just happens to be useful for that), and trimming the samples doesn't make sense for the normal function of the slicer (where you could still select another slice, or use the same sample on multiple pads).

[Funky40]

So if I slice up a loop in the new version, will it save individual one shot files in the zip?

No, but that's because it's not designed to be an export function (it just happens to be useful for that),

this would be useful in a wolrd of one million samples on the SSD.
also, drag and drop to finder would be useful.
i bought sitala2 btw. today.

....nowadays, with that flood of plugins, samplers, ......plus ones own recorded samples, quick workflow is everything !
drag&drop samples around is my quickest workflow i could come up with.
Save all samples with the preset of any sampler is also mandatory, imho.


samplers which won´t deliver quick workflows, will lose the race on the market in my opinion. And thats also exactly a chance for the small developers. Feature creep is not everything ( which is what the big boys are doing, imho)

i like some functions of sitala ! it feels fluffy.
thats its strenght.
Please consider best sample handling to be part of what you plan to do.