TAL-Drum (v2.6.1)
-
gentleclockdivider gentleclockdivider https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=203660
- KVRAF
- 6458 posts since 22 Mar, 2009 from gent
There is something that is rather confusing in taldrum , is that slice markers are still shown when they are totally not necessary
Take the following example .
Load a drumloop in pad one , go to slice mode and set it 8
-Now click "apply to pads ' , the sample is now copied to the other 7 pads and the start-end adress of each sample is adjusted (according to the slice position )
What's really confusing is that each pad still has slice markers embedded , which are totally not necessary anymore
Take the following example .
Load a drumloop in pad one , go to slice mode and set it 8
-Now click "apply to pads ' , the sample is now copied to the other 7 pads and the start-end adress of each sample is adjusted (according to the slice position )
What's really confusing is that each pad still has slice markers embedded , which are totally not necessary anymore
Eyeball exchanging
Soul calibrating ..frequencies
Soul calibrating ..frequencies
-
- KVRer
- 29 posts since 29 Aug, 2007
Every pad which got a slice refers to the same source loop and there's the same "slice-pattern" left in all these pads, right? That can be still necessary and is even mandatory when you want to drag this pattern as MIDI to your host DAW.gentleclockdivider wrote: ↑Fri Apr 12, 2024 12:34 pm There is something that is rather confusing in taldrum , is that slice markers are still shown when they are totally not necessary
Take the following example .
Load a drumloop in pad one , go to slice mode and set it 8
-Now click "apply to pads ' , the sample is now copied to the other 7 pads and the start-end adress of each sample is adjusted (according to the slice position )
What's really confusing is that each pad still has slice markers embedded , which are totally not necessary anymore
-
gentleclockdivider gentleclockdivider https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=203660
- KVRAF
- 6458 posts since 22 Mar, 2009 from gent
Do you guys think the follwoing is a bug ?
When a portion of a sample is set to loop mode ,(picture 1 ) ,
then when assigning a modulation envelope, it should also loop between the loop start and end address but it doesnt' , the modulation envelope just plays through the end .
When a portion of a sample is set to loop mode ,(picture 1 ) ,
then when assigning a modulation envelope, it should also loop between the loop start and end address but it doesnt' , the modulation envelope just plays through the end .
Eyeball exchanging
Soul calibrating ..frequencies
Soul calibrating ..frequencies
-
gentleclockdivider gentleclockdivider https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=203660
- KVRAF
- 6458 posts since 22 Mar, 2009 from gent
Forget about the previous post , it’s indeed better that the mod envelope remains uncoupled from the loop points
Eyeball exchanging
Soul calibrating ..frequencies
Soul calibrating ..frequencies
-
- KVRian
- 512 posts since 27 Oct, 2004
When using more than one sample on a pad, the pad overview still shows the first sample only as a waveform on that pad, instead of the waveform that results from the union of all samples on that pad. It would be great if this could be changed, as I find it very confusing right now when using lot's of layering.
-
- KVRer
- 29 posts since 29 Aug, 2007
More precise, it just shows the selected sample as a waveform. For me, that makes sense, since all the above parameters affect only this selected sample-layer (map), unless you select more than one. But if such a multi-selection would be reflected in the waveform as well, this would be great indeed. Hope that's not too effortful to program something like this.fladd wrote: ↑Sun Apr 14, 2024 12:23 pm When using more than one sample on a pad, the pad overview still shows the first sample only as a waveform on that pad, instead of the waveform that results from the union of all samples on that pad. It would be great if this could be changed, as I find it very confusing right now when using lot's of layering.
In addition, a quick way to select all layers at once would be a breeze!
To use the mapping-edit-features like pad-edit-features, if needed.
-
- KVRian
- 512 posts since 27 Oct, 2004
For me it always shows the first sample. What I select in the edit screen does not affect which waveform is shown in the grid at all. This is on the newest version.orbeater wrote: ↑Mon Apr 15, 2024 9:52 pmMore precise, it just shows the selected sample as a waveform. For me, that makes sense, since all the above parameters affect only this selected sample-layer (map), unless you select more than one. But if such a multi-selection would be reflected in the waveform as well, this would be great indeed. Hope that's not too effortful to program something like this.fladd wrote: ↑Sun Apr 14, 2024 12:23 pm When using more than one sample on a pad, the pad overview still shows the first sample only as a waveform on that pad, instead of the waveform that results from the union of all samples on that pad. It would be great if this could be changed, as I find it very confusing right now when using lot's of layering.
In addition, a quick way to select all layers at once would be a breeze!
To use the mapping-edit-features like pad-edit-features, if needed.
-
- KVRer
- 29 posts since 29 Aug, 2007
My bad, had overlooked that you meant the pad overview.
I wrote about the edit view.
What you wrote, i can confirm that behaviour and would like a change as you mean it as well.
-
- KVRer
- 29 posts since 29 Aug, 2007
...seems some silent updates made by TAL.
Main improvement is stated as "Smaller plugin state". Indeed the project files are much smaller now, and it seems it starts a bit faster as well.
Solid careful maintenance!
Main improvement is stated as "Smaller plugin state". Indeed the project files are much smaller now, and it seems it starts a bit faster as well.
Solid careful maintenance!
-
- KVRian
- 1127 posts since 7 Dec, 2017
I agree, it's nice he keeps improving and updating. I do wish there was some way to be notified of the updates though other than having to check the product page daily.
-
neverbeeninariot neverbeeninariot https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=350084
- KVRian
- Topic Starter
- 985 posts since 3 Feb, 2015 from UK
Updates from the last few changelogs (since 2.3.3 / 08.04.2024).
Version 2.5.2 / 16.05.2024
* Minor fixes and improvements.
Version 2.5.1 / 07.05.2024
* Minor fixes.
Version 2.5.0 / 02.05.2024
* Smaller plugin state.
* +-48 semitones tune range.
* Minor fixes.
Probably be another one along any minute...
Version 2.5.2 / 16.05.2024
* Minor fixes and improvements.
Version 2.5.1 / 07.05.2024
* Minor fixes.
Version 2.5.0 / 02.05.2024
* Smaller plugin state.
* +-48 semitones tune range.
* Minor fixes.
Probably be another one along any minute...
-
- KVRer
- 29 posts since 29 Aug, 2007
Yeah, now the KVR product page has noticed the recent update, but there are frequently updates that didn't get there. I wonder why.
Meanwhile, i'd like to mention, the pictures and description text for Tal-Drum on KVR are quite outdated. Just saying.
Meanwhile, i'd like to mention, the pictures and description text for Tal-Drum on KVR are quite outdated. Just saying.
- KVRian
- 1385 posts since 17 Jul, 2007 from Riversland Valhalla
Version 2.5.3 / 24.05.2024
- Stereo, left and right sample channel options for mapping.
- Fix in the MIX view with multi-selection.
- Labels show up on MIX view sliders under some conditions fixed.
- Show all mapping layers on the pad over blended.
-
- KVRer
- 29 posts since 29 Aug, 2007
Whoat? Another one. Great News!phreaque wrote: ↑Fri May 24, 2024 11:00 am Version 2.5.3 / 24.05.2024
- Stereo, left and right sample channel options for mapping.
- Fix in the MIX view with multi-selection.
- Labels show up on MIX view sliders under some conditions fixed.
- Show all mapping layers on the pad over blended.