I own my digitone for one week now and I have a question about using one track for drums:
When I use p-locks for different drum sounds, is it possible to adjust the filter for the whole drum track at the same time?
Or is it possible to adjust the filter for every base drum sound (instead of adjusting every step and copy/past it)?
It seems, that the filter only affects the “main” sound of the track, not the p-lock sounds…
Thanks for your help!!
The only way I know how to do this is to program those sound to respond to Mod/Pitch wheel/expression/etc, and then use an external controller (or in my case, the digitone keys) to adjust those preassigned parameters. It’s a bit of a pain, but worth it. For instance, I often assign decay/release to one control, filter to another; and that way I have at least basic live control over all soundlocks in a drum track. For stuff not meant for performance, I still just use parameter locks. Thankfully with the func+yes preview, that’s a bit more manageable. Also, practice copy/pasting multi trigs, you will get faster.
However, I often do wish this were a feature. At the least for filter, envelopes, and FX.
It’s also possible to record parameters in Live Recording mode. Faster than plocks if you want to apply a setting to all trigs.
I don’t think this works for sound locks, which I believe was the main question, but agreed - it’s faster for general automation. It’s also impossible to do in a consistent/unmoving manner, and fills the pattern up with trigless trigs which personally I find a bit cluttering unless necessary.
The inability to live tweak soundlocks does make drum tracks on the digitone much more difficult than it needs to be, I’d at least like the option for a soundlock to be ‘locked’ (like it works currently, rejecting knob movements) or ‘free’ (responds to tweaks like any other trig, relative to the current value of that soundlock’s parameter, with or without recording active) but I don’t have hopes we will get that. Also, saving a parameter locked trig as a sound preset.
It does. Live recording makes similar plocks.
I use it essentially to add fx. Yes, you have to move the knob continuously, and you get trigless you can remove. Far from perfect.
I also planned to make modulation / aftertouch / pitchbend / velocity mod.
Velocity mod advantage : you can set your parameter mod with Trig page VEL for all trigs.
You can erase all Vel values with No+Vel in live recording. Vel to Vol off. Off course you loose velocity.
Unfortunately mod / aftertouch values are not saved. Would have been a workaround.
Yes, eventually the possibility to convert soundlocks to plocks, or unlock certain parameters…
I’d also love to be able to modify and assign soundlocks quickly, like holding a trig, turn level and assign to a slot, with the possibility to overwrite, save confirmation.
Thanks for your replies!
@dreamsaremaps : Using an external controller is a great idea. Maybe I should use a DT midi track. Great hint! Thanks!
@sezare56 : [edit] Oh, this is a great option! At first, it did not work, as my hihats had some hp filter. It seems, that all trigs need the same filter type. Works great! Thanks!
@sezare56 I’ll have to try this again. Maybe what I am thinking of is (if I recall correctly) simply adjusting a parameter (not in record mode), which for a lock will very briefly alter the sound but then will snap back to the locked state? Which makes sense, but I suppose if live recording alterations works, that may sometimes be a workable work around for performance. Will check how this works in practice shortly.
I would very much like a faster way to work with soundlocks. It would make what’s now a bit of a chore into a workflow that would (I believe) vastly increase the real world usability and power with the DN. Copying a plocked trig and pasting it into a preset would be huge. Similarly like was said to simply be able to hold a plocked trig and/or altered soundlock and save it to the soundpool, with the option of rewriting a currently used sound, simply by some key/turning the level knob combo or whatever makes the most sense would greatly speed things up and not fuck the flow up like it does currently. Go and save in the sound manager, send to the sound pool, select from held trig…that’s just way to much when you’re in the groove.
@DelayDude Using DT midi tracks to sequence DN modulation via the MW/PW/AT/BC controls is awesome. Gives you 4 plockable controls that can each morph 4 modulation settings on the DN, and it works based on how the sound was saved as preset/sound lock. It’s nice to set up some drums each with their own appropriate and unique mod settings for later use. I don’t know if the standard DN can respond to expression via an external controller, but at least on the keys version that’s another control that has 4 mod slots.
Agreed that velocity is a good way to access a mod group directly on the device when not needed. I often do find it (especially for percussion) more useful than volume velocity, so I will often disable that in the sound settings menu.
Also to note, when using PW to control a mod group, most of the time you’ll want to change the pitch wheel range to 0 to disable actual pitch changes. That’s an interesting control to use physically, as it of course snaps back to center. Also, I believe if sequencing PW from the digitakt, for instance, you’ll want your neutral position to be value 64 (I think?) and is bipolar from there +-; even on patterns where you want no change to the PW control, you may have to start that sequence with a value of 64 in order to avoid a different held over value if an earlier PW value hadn’t already been brought back to neutral. I’m not actually sure about this functionally, but in my head that may be necessary so something to check if you run into trouble.
Semi-related tangent: while you’re at it, using the DN’s MIDI tracks for additional channels to plock tracks on the DT is a nice option; can be turned on/off; can see the control moving on the DT screen; can add more plocking once the DT limit is reached; adds extra LFOs; etc. I wish the DT had mod groups like the DN, and also I wish both devices could just route their midi tracks straight to their regular tracks. At leas my now that MIDI loopback doesn’t cause crashes on pressing stop twice it’s a bit safer to do, but still think it’s a waste they can’t route internally just for instant additional LFOs. I find using an iPad and USB MIDI for easy loopback is a nice easy way to utilize loopback for these devices. Using them to control each other is super powerful, but it requires being on the right pattern all the time and sometimes makes a good case for synchronizing the devices via program change, even though I like to mix and match patterns between devices.
You can just hold down multiple keys and change p’s on them all you know? It doesn’t work in a few cases, but seems too most of the time.
@og_tea_boi Thanks - yes I know. But it is not as easy and fast, if the drum track has 64 steps.
@dreamsaremaps That´s awesome! Thank you so much for this tips! I definitely will use the midi tracks to plock the DT. I didn´t even think about the option of extra LFOs for the DT by using the midi tracks.
No prob, hope it helps! Honestly I find myself not taking the time to do a lot of these things in the majority of sessions, but I’ve tried to figure out the potential options for when the need arises! Guess I’m just lazy lol. Kinda want to go LFO and Mod wild right now, though! 
Good luck! Post any related tips you come up with in your explorations!
Yesterday I did a few patches with PB/AT/MW/BC control, it takes a lot of time.
Luckily you can copy / paste modulation pages. Then I decided to start from scratch and copy / paste sounds in order to keep mods. Possible to use midi loopback to control the 4 mods, add lfos (different dest/depth on different lock trigs, add PROB)
Procedure : import a sound in a track, do the mods, export the sound in a dedicated bank, then in the soundpool. I used same numbers for bank / soundpool.
You can export / replace directly in the soundpool, but guess you can’t use it in another projects. Any thoughts about the best way to organize the soundpool?
@DelayDude I also tried another approach : import a sound (kick), plock everything except filter, copy / paste trigs, import a new sound (snare), rinse and repeat.