TAL-Drum

[gauderbock]

You can have the samples anywhere you like.

Can you have multiple sample locations?

Yes, just 'star' a directory in the browser and it shows up at the top.

[pierb]

Can you have multiple sample locations?

Yeah. You can navigate all your drives for samples.

You can also remember favorite folders. These are the colored labels on top of the browser you can see here:

[simmo75]

Thanks guys.

[a-type]

Finally had a chance to properly test TAL-Drum in a project, and wow it's great. So much smart functionality, and it sounds awesome! You can hear that TAL-Sampler pedigree.

Anyone else find the browser column too narrow? Or the fonts there too large? Some of the longer filenames from sample packs get truncated, and it doesn't look like there's a way to adjust the font size or make the file tree column wider. This would be great to have! (or maybe it's there already and I'm missing it?)

[backtomusic]

Version 0.9.95 / 11.04.2022 is out, one of my requests in on it

• Possible click fixed when hiss is enabled.
• Drag and drop multiple files from explorer/finder in pad view.
• Minor fixes.

Drag and drop multiple files, now we can drop the entire kit from XO's export into TAL-Drum for example.

[zvenx]

....
Drag and drop multiple files, now we can drop the entire kit from XO's export into TAL-Drum for example.

What a fantastic idea..
I just did it and it worked seemlessly..


rsp

edit: i removed the audio, realised that XO was processing the samples and I only dragged over the raw ones.. sorry about that.

rsp

[neverbeeninariot]

V1.0.0 Released (no changes from previous RC)

https://tal-software.com/products/tal-drum

https://www.kvraudio.com/product/tal-dr ... l-software

[kobal]

nice, a other great tal plugin , congrats !

[Caine123]

does someone have vice / Nuance and compared it with this plugin?

[stash98]

Congrats to TAL for the 1.0 release! This is a drum machine with tons of character in it.

[fladd]

Can someone explain to me how to

(1) save a drumset in a self-contained way, such that it can be shared with other users?

(2) save the drumset in the DAW project directory (e.g. in REAPER), such that when I move the DAW project directory (e.g. to another computer), the samples and the references to them are intact?


I tried to first save the preset, then do "Copy samples to (preset) directory..."), then reload samples, saved again, but whatever I do, the .taldrum file contains absolute paths, which will only work on a single system.

[audiojunkie]

Can someone explain to me how to

(1) save a drumset in a self-contained way, such that it can be shared with other users?

(2) save the drumset in the DAW project directory (e.g. in REAPER), such that when I move the DAW project directory (e.g. to another computer), the samples and the references to them are intact?


I tried to first save the preset, then do "Copy samples to (preset) directory..."), then reload samples, saved again, but whatever I do, the .taldrum file contains absolute paths, which will only work on a single system.

Good question. I'm interested in knowing the solution to this as well.

[anttimaatteri]

A drum synth by TAL that would be something.

That's what I was hoping for when I read the thread title. I have too many drum samplers already. But a TAL drum synth would've been very tempting.

set it directly next to the u-he drum synth! (which is taking some more years i guess)

[neverbeeninariot]

Can someone explain to me how to

(1) save a drumset in a self-contained way, such that it can be shared with other users?

(2) save the drumset in the DAW project directory (e.g. in REAPER), such that when I move the DAW project directory (e.g. to another computer), the samples and the references to them are intact?

Good question. I'm interested in knowing the solution to this as well.

Both can be done in just a few steps.

I added a 'user' folder inside the TAL-Drum Factory folder but this could be any location on your machine, and under there are separate folders for Kits, and for Samples.

..\some_path\DC\
..\some_path\DC\Kits\
..\some_path\DC\Samples\<kit_name>\

I use the 'Copy Samples to Directory...' option for my library, although you could use 'Copy Samples to Preset Directory' but this gets messy IMO (see note 1 below).

So,

Create self-contained kits

1. Create a new kit, lets say it's an awesome CR8000 kit
2. Save the kit preset to "..\DC\Kits\CR8000.taldrum"
3. 'Copy Samples to Directory...' and save the samples to "..\DC\Samples\CR8000\" (first creating the CR8000 folder)
4. Save the kit again. The paths will be updated relative to the kit preset (I think this is the step you are missing)

<snippet from CR8000.taldrum>
<mapping path="..\Samples\CR8000\CR8000 Kick.wav" ... which is relative to my Kits folder

As long as you maintain the Kit presets to Samples folder structure, it should work on any computer. I can now zip and share my 'DC' folder and it's all self-contained. This is basically how the Factory library works.


DAW project localisation

1. Save the kit preset to the current project folder e.g. "..\some_path\My_Project\Drums\"
2. 'Copy Samples to Preset Directory' (see note 2 below)
3. Save the kit again to update the relative paths to the samples

Now the kit should move with the project (for Reaper at least, I can't speak for the portability of other DAW's projects)

Note 1 - To keep things neater, there's nothing to stop you creating a separate folder for each kit preset and then using 'Copy Samples to Preset Directory', but the extra folder means an extra double-click to get to the actual preset when browsing.

Note 2 - You don't need to create separate 'kit' and 'samples' folders in a DAW project as there may only be 1 or 2 kits used in each project, so mixing presets and samples in one folder isn't such a management problem.

[audiojunkie]

Nice! Thanks!