TAL-Drum

[emasters]

A bit confusing because where do the 600 samples reside?

If you haven't worked it out yet... When you click on the gear icon, it lets you set your root sample folder (like d:\samples\drums, or whatever - you an also download the presets from that windown too). Unnzip the "GB_TAL-Drum_Pack" folder to that location, then browse to it from inside the plugin.

The included sample pack is just a very small collection of classic drum machine samples, enough for the included trial preset kit, but I have plenty other interesting samples to play with : )

Thanks for the tip - though the process is confusing. It looks like a couple of the provided collections, include "Kit", "Midi" and "Samples" folders, one has kits and samples in the same folder (Empty Vessel) and one has a "Samples" folder and kits outside the Samples folder. Is it possible to share what the directory structure is ultimately supposed to look like across all the kits/sample sets supplied in the download? I understand how to setup the pointer to the top-level parent directory, but given multiple kit/sample collections, how is it organized underneath? It seems like it recognizes some, but not all of the kits/samples.

[mi-os]

Looks very promising. How does the 32 pads mode look like? All in one view or tabs? (edit: it's shown in the overview video at 4:00)

[emasters]

A bit confusing because where do the 600 samples reside?

If you haven't worked it out yet... When you click on the gear icon, it lets you set your root sample folder (like d:\samples\drums, or whatever - you an also download the presets from that windown too). Unnzip the "GB_TAL-Drum_Pack" folder to that location, then browse to it from inside the plugin.

The included sample pack is just a very small collection of classic drum machine samples, enough for the included trial preset kit, but I have plenty other interesting samples to play with : )

Thanks for the tip - though the process is confusing. It looks like a couple of the provided collections, include "Kit", "Midi" and "Samples" folders, one has kits and samples in the same folder (Empty Vessel) and one has a "Samples" folder and kits outside the Samples folder. Is it possible to share what the directory structure is ultimately supposed to look like across all the kits/sample sets supplied in the download? I understand how to setup the pointer to the top-level parent directory, but given multiple kit/sample collections, how is it organized underneath? It seems like it recognizes some, but not all of the kits/samples.

Got it sorted... mis-expectation on my part, about how it was supposed to work. Makes sense now.

[sQeetz]

Nice! Fast and intuitive. Demo'd for a while and bought it. Will use this one a lot
Would be nice if there was some basic editing in the sample recorder, though... (cut, copy, paste, undo)

[audiojunkie]

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

16/32 Pads
4 mappings per pad
Loop slicing
Modulation
Time Stretch
Recording (via sidechain)
and more..

https://tal-software.com//downloads/doc ... Manual.pdf



Currently in beta, and there's also a 20% discount available.

I'll be taking this for a test run this evening

Very cool! A new toy for Linux!

[audiojunkie]

I'd be curious to know which DAW folks who buy this are using.

For me, it will be on Reaper and Ardour (on Linux).

[andrewbrewer]

I really like this one! It can get very lo-fi, and I like some of the static and pre-computed feel of the effects. There are some audio glitches that I hope will be ironed out over time.

[neverbeeninariot]

Got it sorted... mis-expectation on my part, about how it was supposed to work. Makes sense now.

Glad you got it sorted!

For anyone else confused about this; When you set the root sample path in TAL-Drum, the plugin will use that as the start of a relative path for any samples you use in a kit. If you move to a new computer (for example), the root sample path can be different as long as the sub-directories are the same, and it will still be able to find any kit samples. For my setup, I just pointed it at the root of my Audio drive (D:); it looks a little like this:

D:\ <set as root folder in TAL-Drum>
D:\samples
D:\samples\TAL
D:\samples\TAL\Drum
D:\samples\TAL\Drum\emptyvessel
D:\samples\TAL\Drum\GB_TAL-Drum_Pack
D:\samples\TAL\Drum\Saif Sameer - TAL Drum
D:\samples\TAL\Drum\Solidtrax - TAL Drum
etc...

If, in the future, my Audio drive changed to E:\ then all I need to do is set the TAL-Drum root path to E:\ and keep the samples sub-folders the same and the plugin will still be able to create the correct relative path to find any samples in custom kits.

[Michael Sage]

Finally released !!!
I was a beta tester and thoroughly enjoyed it ( still do actually )
Patrick was so open to suggestions and feedback , and most importantly TAl Drum is awesome .
Tal is absolutely Top Notch stuff !

I was a beta tester too. Thanks to Patrick for bringing many of my ideas to TAL Drum.

[Lotuz2019]

Unlike TAL-Sampler and TAL-DAC it doesn't seem to have ADC and DAC Quality controls. It would be nice if those were added to the LO-FI section. TAL-DRUM has its own sound, but users might want to give it a different sound.

And if you could also save and load your own LO-FI configurations, that would be even better.

[Lotuz2019]

Does TAL-DRUM allow you to play a pad at various keys?

From the Battery 3 manual:

Key Range: These two fields determine the MIDI note range that will trigger
the current Cell. For example, a key range of C2-C2 means that the Cell will
play only upon receiving MIDI note C2. If set to C1-E1, then C1, C#1, D1,
D#1, and E1 will all trigger the Cell.

Tracking: When activated (lit) and the Key Range exceeds one note, all samples
in the current Cell will change pitch in response to the MIDI input. For
example, if the key range is C1-D1 and you play D1 with track On, the pitch
will be two semitones higher than if you had played C1. With Track disabled,
the sample’s pitch will be determined solely by its root key (as set in the Map
view) and the Tune knob.

[gentleclockdivider]

Finally released !!!
I was a beta tester and thoroughly enjoyed it ( still do actually )
Patrick was so open to suggestions and feedback , and most importantly TAl Drum is awesome .
Tal is absolutely Top Notch stuff !

I was a beta tester too. Thanks to Patrick for bringing many of my ideas to TAL Drum.

Same here , one of the requests I asked for was 32 pads and I bet other did too .
Overall a great beta experience , and a nice reward

[Dencheg]

Question: what's the added value for those who have TAL Sampler?
I happened to like some kits in Sampler a lot... isn't Sampler a superset (functionally) of the Drum?

[FapFilter]

- better for layering more stuff individually per pad
- each pad can have individual settings like envelopes, filtering, stretching, etc.
- it has more modern modulation options than just LFOs
- individual outs
- it samples
- oh and it has auto slice functions + MIDI pattern drag/drop to host
That‘s from the top of my head, but i only tested it briefly last night.

TAL Sampler is great, but it was never that great for druns. That‘s why people requested such a thing and now it“s here

[mcbpete]

Unlike TAL-Sampler and TAL-DAC it doesn't seem to have ADC and DAC Quality controls. It would be nice if those were added to the LO-FI section.

Was thinking the same thing - would be great to have a section to turn either a pad (or even the entire kit) into a virtual vintage MPC 60 like with the resampler section of TAL-Sampler ... maybe in v1 !