Hey, I was trying out TAL-Drum (amazing piece of software holy crap).
Anyone else is experiencing this same little bug I have?
When I'm in 16 pads mode, I drag and drop a sample but it gets put into the 2nd group.
So if I drop it into the 1st one, it goes into the 17th one, and I have to switch group again. Unless I manually drop the sample INTO the editor itself. It's a bit annoying, since I don't want to use the 32 pad setup (which solves the problem obviously). I wonder what the cause of the problem is

 

Tal always has poor implementation of good ideas. Ill play around with it more tomorrow and see if I can figure that out, as I just started playing with it too.. But I can't even figure out if it does round Robin.. Something that should be fairly easy to do.. As of yet, for me, nothing can compare to One Small Clue's Poise free mpc style drum sampler... It's so easy and well implemented. But for Tal, they could be So good.. But they suck at implementation. Like their TAL sampler... It's great.. But it only does 4 samples at once mapped across the keymap. Wtf is that?!

 

I had the same experience.
Dragging samples from the internal browser into slot 1 works fine, but dragging from FL Studio browser places it in slot 17 instead of slot 1.
I decided to try dragging and dropping from Windows explorer ... and that worked properly.
Then I tried using FL Studio browser again and now that works fine too.
I closed the project and opened a new one and now I can not reproduce that "bug".

It seems fine in Studio One...

Maybe it was something that got fixed by dragging in front Windows Explorer.
What DAW were you using and how did you drag in?

 

Im not having this on my PC I went to try to see if that happens in studio one and it's seems fine to me

 

I remember reading somewhere that Image Line states that if you run FL Studio with administrator rights that there could be drag and drop issues.

 

Edison uses a different way to drag and drop samples, maybe they implemented it for FL also?

 

Yes, I'm using FL Studio.
I checked the administrator priviliges thing, that always happens, but it doesn't seem to be the problem. I'll try to record so you have a better idea, but it's what @DoubleTake said. I tried from the system explorer but it has the same weird erratic behaviour.
It's not a big deal as I'll use the 32pads, the software is quite amazing and very useful for me.
@fleschdnb it appears round robin can be done, https://tal-software.com/products/tal-drum, but I think the strength of this software lies in its simplicity and effectiveness, IMHO!

Here's the little bug btw

 

I have tested TAL-Drum and everything works fine, see picture in file attachment.

The clicking in your video is a little too fast for my eyes.
Could it be that you want to use the same sample several times ?
Can you try this again with 7 different samples for example. first slot 1 then slot 2 then slot 3

(From the TAL-Drums instruction manual page 8) https://tal-software.com/products/tal-drum

TAL-Drum // Pad View
This is the default view when you open the plugin. It shows the browser on the left and the pads on the right. The pads show by default the sample name loaded in the first mapping inside the pad. It’s also possible to rename the pad with a click at the name on the bottom left above the pad name “PAD XX”:

A right-click on the pad opens a color dialog and lets you assign a pad color. It’s possible to switch pads with drag & drop. Holding CTRL while dragging a pad copies the pad mappings and the color to another pad.

The pad settings like the output, voice group and the MIDI KEY stay the same when moving or copying pads. You can also copy/paste pads from one instance to another using the copy/paste icons on the bottom of the pad. The pad also shows information like the voice group, and the assigned MIDI note. You can mute and solo pads with the M and S buttons.

A click on the pad triggers the pad. The I/II button on the top switches between the first 16 pads and the second pad page that contains the pads 17-32. You can also switch to the 32 pad mode where all 32 pads are visible at once.

 

Last edited: Apr 24, 2022

Normally explorer.exe is running in user context mode and not in admin context mode. Doesn't matter if an admin account is used!
So if a software is running with administrator rights then drag'n'drop will never work from explorer.exe (if i'm not completely wrong..^^).

 

@BEAT16 Don't worry about the video, just look at the first drag and drop. I put it into the PAD01, but it goes straight into PAD17

 

I have tested it myself as I described before, it works fine. Maybe you should try the whole thing again in peace, new project, load drum plugin and with another WAV sample set and run the whole thing a little slower.

 

I didn't have problems w/ drag'n'drop, but anyone know why the multi-out assignments keep getting reset (on load etcs) and have to be changed back 1 at a time? Makes the plugin freaking useless, essentially! Anyone know if there's a "lock" button or w/e? (I'm likely just being dumb!)

 

(From the TAL-Drums instruction manual page 9) https://tal-software.com/products/tal-drum

TAL-Drum
Bottom View

This view contains the most important parameters for the mapping. It shows the pad number and it’s possible to step through the pads with the arrow buttons or you can also select a pad with MIDI when MIDI SELECT is enabled. Enable the S button for solo mode and mute all other pads.

OUTPUT: The channel where you want to output the pad.
The plugin has 8 stereo outs. You may need to configure your DAW to use the outputs.

MIDI KEY: The MIDI note that is assigned to this pad. User LEARN to assign the key by your MIDI device.

VOICE GROUP: You can select a voice group for the pad and set a sample fade-out time for the voice stealing. The fade out time will introduce a delay for the next sound when voice stealing happens (the delay is exact the fade-out time).

You may set this value to zero for most sounds. It’s helpful to increase this value to avoid clicks for bass or kick samples when you don’t want that they overlap and play always only one voice.

The blue combo box values show the voice group settings (number of voices and the mode).

ONE-SHOT: When enabled, always the whole sample will be played.

 

Yeah, that's (I think) how many voices are played at once, RR etcs stuff. Edit: oh, never mind. I found what I was looking for. If anyone else has this (multi-out) problem, it's hidden in a drop-down in the loading menu: "assign sequenced outputs to first 16", at the top! (I never used it, didn't even realise there was a menu! eg: <| GB-NAME click here |> ) Very unintuitive! Prolly the most important button evah and hidden away, doesn't work as expected. Have to reload to reset to single channel output! smh

Also, default is 16 stereo outs, so manual is wrong, I guess?

Also the vertical "close" button in the edit window? Not easy / intuitive to find if you're looking for an "X"; inconsistent (illogical) shape, too! This makes the whole gui inconsistent, since they also use the standard X button in settings, ffs. Feels like they didn't game test the gui.

Another issue w/ the gui. There's no "hover over" info. So (for example) there's a button with the informative label "S", on the MAP part (edit window.) I thought this was (naturally) a solo button (literally ever other S button does this.) But it's not. It starts flashing. So I guess it's a sample button? Still have no idea.

 

Last edited: Apr 24, 2022

I find the interface very successful and simple. I can't agree with you there. Do you have a bad monitor?

 

Quite the opposite, 4k 65" TV. I am practically blind, tho, so :D Like I said, it's the inconsistency that's bad; X button for settings, then trying to find an X button on edit window? It's "CLOSE", which looks like any other (SAMPLE, LFO etcs) button, ffs - not even inverted colors.

Spoiler

(Looks like it's an extended part of ADSR, when you do notice it!)

Generally, though, I'd agree. The UI is good and uncomplicated for general workflow. The examples (finding multi-out options, hidden menu, mystery "S" button, no X button in edit window) are real problems, should never be? The output "button" (functionless) on the gui (bottom) needs to swap between multi / single output imo, saves (hidden) menu diving.

Blurry? vvv You're lucky you can set Windoze @ 100%! Try using the Windoze 225%-300% resize (display), and then resize TAL win to fit? Another issue!

 

Last edited: Apr 24, 2022

Why is your image blurrier ? Sharpness comparison

 

It looks like hot pixel garbage from the 90s if you set Windoze scaling to 300% (recommended setting for me) so that's another thing TAL should've game-tested before releasing! XD Also, the JUCE (?) framework seems to go wonky af at high scaling?

I'm talking about Windows>Home>Display>Scale and Layout, btw, not DAW scaling.

Spoiler

Comparison (not resized)

100% (windoze scaling / default)

300% Windoze scaling (for visually impaired)

 

Last edited: Apr 24, 2022

I'm at 196%, but I have glasses on too. Sight does, after all, diminish with age. I have installed many plugins from TAL and he really does a good job.

Many plugins from other manufacturers are not suitable for Studio One, because Studio has real HDPI, the other DAWs only enlarge, maybe you have the opportunity to have a look at Studio One. There you have more sharpness.

Developing Studio One, Part 1: High DPI graphics engine
https://blog.presonus.com/2015/05/28/developing-studio-one-part-1-high-dpi-graphics-engine/

 

Last edited: Apr 24, 2022

I think you've got a bit confused about scaling? (see above, there's literally never been a "196%" option! It's in 25 or 50% increments)

A lot of devs just ignore Win scaling, sometimes (Avenger; load vst2, set avenger to 200%, win scaling to ~300% = offscreen + undraggable bug) getting into an unrecoverable state w/o deep hotkey knowledge. JUCE does seem rly bad for this, moreso than just devs. But even the lovely, free DSP emu does a much better job, soo?

Anyway, hope the dev picks up on these things, cos it's a (potentially) great product, just a few things need ironing out! At least I discovered how to get around the multi-out thing, which means it's actually usable, now!

 

Last edited: Apr 24, 2022