Faders are great for track levels. I haven’t used this one but looks like it might be perfect for this application. Very petite as well, just a hair wider than the DT
Exactly, the macro levels stay the same when changing a pattern. So if you set the amp level of a track to zero on all patterns and map amp level to a macro, it will always reflect the value you set with your knob/fader. I think parameter kits on DT II disable the preset settings on the tracks you want that to happen to, so they’ll keep the value of your orginal pattern and how you tweaked this one. Cool you mentioned this could be problematic btw, just wanted to clarify it’s not an issue imo.
1 Like
Aren’t there only 6 macros though? So you could only do this for 6 tracks?
Looks awesome
It’s a good point. Maybe I could set up so each song just works with one pattern and then I can just work the track using mutes and volume changes.
No problem, this limit is per track, not per pattern. You can assign several macros to each track (don’t know if it’s 6). Each macro can have four parameters. Each track can be mapped to a MIDI channel and each knob or fader on a Faderfox can be mapped to the same MIDI channel.
If you set eg mod wheel for track 1 (MIDI channel 1) to amp volume and fader 1 to MIDI channel 1 and MIDI CC 2 (mod wheel), it will control amp volume of track 1. You can replicate that across each track you want to assign volume fader to, and you would still be left with more macros per track than you have knobs or faders on a UC4.
2 Likes
So the macro levels stay the same when you change pattern? So I could set up 1 macro to control volume for each of the 16 tracks with an assigned MIDI channel controlled by whatever controller I choose and the volume wouldn’t change when I change patterns?
The Faderfoxes have that ‘snap to value’ function, or whatever it’s called, right?
Yes, exactly. But you have to set the amp volume of the tracks you want to control to zero on each pattern in order for this to work.
@Pablo76: Yes, but I don’t think this is of much help unless you create some kind of loop back from DT to Faderfox so that it gets the value from where it’s picking up. Don’t know if this would even work. But not necessary for the approach I’ve described.
