Not being to solo 'input' tracks that are routed elsewhere?

Discuss music production with Ableton Live.
TomViolenz
Posts: 6854
Joined: Mon Dec 13, 2010 6:19 pm

Re: Not being to solo 'input' tracks that are routed elsewhere?

Post by TomViolenz » Wed Oct 30, 2013 6:31 pm

If Nocturn is unlocked, it should be "slavish" to wherever the BH is. Likewise, if you navigated to another track/device with the Nocturn, Push would also slavishly control the BH, as long as it's unlocked. That's why I don't think there's a master/slave dynamic,
That's very good news, so if I manage to make an xTrigger for locking and unlocking, I can achieve exactly what I wanted Yeah! :-)
(And I understood from the rest of your post, that this is not so difficult)
and I'm not saying that for some policitally correct level,
Lol, don't let this socialist world oppress you man, speak your mind freely :mrgreen:
What Ableton could update, and I think this has already been made as an FR but could be repeated, is to have a Hand per controller.
Just as each controller can have a different color box in session view (aka matrix), it could have a matching colored Hand on devices, at least just for locking for sake of organization. But let's have that go on a separate thread.
I think we already went over this in the Push Band scenario. I agree that this would be an awesome feature!
Anyway, I think you're worried over a potential situation you haven't been in before. Have you had 2 controllers at the same time?
:oops:
No I guess, I'm still a virgin there, but I have pretty precise plans of what I will do once I have the money together to buy Push, as you might have seen in that device parameter rearranging thread :)

regretfullySaid
Posts: 8913
Joined: Thu Apr 22, 2010 5:50 pm

Re: Not being to solo 'input' tracks that are routed elsewhere?

Post by regretfullySaid » Wed Oct 30, 2013 7:13 pm

Yes, I imagine you've studied Push enough to know how everything will work once you get it.

I'd like to make a point in general though that switching banks and locking/unlocking devices is not exclusive to Push or other controllers with custom scripts. Those options are available for you to set with Lives own User Remote Scripts.

All you need is 8 CCs for the macro knobs,
1 cc for previous bank
1 cc for next bank and
1 cc for lock/unlock

11 cc's on any controller with 8 knobs and 3 buttons.
ImageImage

TomViolenz
Posts: 6854
Joined: Mon Dec 13, 2010 6:19 pm

Re: Not being to solo 'input' tracks that are routed elsewhere?

Post by TomViolenz » Wed Oct 30, 2013 7:35 pm

shadx312 wrote:Yes, I imagine you've studied Push enough to know how everything will work once you get it.

I'd like to make a point in general though that switching banks and locking/unlocking devices is not exclusive to Push or other controllers with custom scripts. Those options are available for you to set with Lives own User Remote Scripts.

All you need is 8 CCs for the macro knobs,
1 cc for previous bank
1 cc for next bank and
1 cc for lock/unlock

11 cc's on any controller with 8 knobs and 3 buttons.
I guess I always depend on custom scripts because I don't really know which cc's I would choose to affect something...
Is there a general list? I've never seen something like this mentioned.
Or do you mean Midi assigning things in Live? I always hated how inflexible that is.

regretfullySaid
Posts: 8913
Joined: Thu Apr 22, 2010 5:50 pm

Re: Not being to solo 'input' tracks that are routed elsewhere?

Post by regretfullySaid » Wed Oct 30, 2013 8:51 pm

There is a folder called User Remote Scripts in your System User/Ableton directory. This isn't the same the Program directory. You might already have some directories inside the User Remote Scripts directory. there's a file called InstantMappings-HowTo.txt:
InstantMappings HowTo
=====================

With the file 'UserConfiguration.txt'provided in
this directory, you can create your own Instant
Mappings.

1. Create a directory in 'User Remote Scripts'.
The name of the directory will show up in the
list of Control Surfaces in Live.
Naming: The name of the directory should not
start with '_' or '.'.

2. Copy the the file 'UserConfiguration.txt' into
your directory. The name of the file needs to
remain unchanged.

3. Edit the copy to adapt it to your needs. The
comments in the file will tell you what to do.
Inside the custom directory you created, there is a file called UserConfiguration.txt:
# Config File for User-defined Instant Mappings

# We assume that the controls on your MIDI controller
# send CCs (except for pads). All controls that do not have
# an explicit channel setting are expected to use the
# global channel. CCs & Notes are counted from 0-127
# and channels from 0-15.

[Globals]
# The channel that the controller should send on
GlobalChannel: 8

# If your controller is connected via USB, replace ControllerName
# with the name of the respective port. Live will then try to
# recognize the ports for you when you select your Instant-Mappings
InputName: AxiomKnobs
OutputName: AxiomKnobs
# If your controller has pads that send notes, you can use them to
# play the visible pads in your DrumRacks. Just replace the -1 for
# the note (and channel) of the respective pad. The arrangement of
# the pads in the DrumRacks is as follows:
# 1 2 3 4
# 5 6 7 8
# 9 10 11 12
# 13 14 15 16
# (If you leave the channel of a pad at -1, Live will assume that
# the pad uses the global channel)
Pad1Note: -1
Pad2Note: -1
Pad3Note: -1
Pad4Note: -1
Pad5Note: -1
Pad6Note: -1
Pad7Note: -1
Pad8Note: -1
Pad9Note: -1
Pad10Note: -1
Pad11Note: -1
Pad12Note: -1
Pad13Note: -1
Pad14Note: -1
Pad15Note: -1
Pad16Note: -1
Pad1Channel: -1
Pad2Channel: -1
Pad3Channel: -1
Pad4Channel: -1
Pad5Channel: -1
Pad6Channel: -1
Pad7Channel: -1
Pad8Channel: -1
Pad9Channel: -1
Pad10Channel: -1
Pad11Channel: -1
Pad12Channel: -1
Pad13Channel: -1
Pad14Channel: -1
Pad15Channel: -1
Pad16Channel: -1

[DeviceControls]
# The Encoders will control the device parameters (you can also
# use knobs or sliders). Replace the -1's with the CCs sent by
# the respective controls on your controller. You can also set
# the channel for each controller if it differs from the global
# channel (if you leave the channel of an encoder at -1, Live
# will assume that the encoder uses the global channel).
Encoder1: 92
Encoder2: 93
Encoder3: 94
Encoder4: 95
Encoder5: 96
Encoder6: 97
Encoder7: 98
Encoder8: 99

EncoderChannel1: 8
EncoderChannel2: 8
EncoderChannel3: 8
EncoderChannel4: 8
EncoderChannel5: 8
EncoderChannel6: 8
EncoderChannel7: 8
EncoderChannel8: 8
# Enter the respective map mode for the encoders here. The following
# map modes are available:
# - Absolute
# - Absolute14Bit
# - LinearSignedBit
# - LinearSignedBit2
# - LinearTwoCompliment
# - LinearBinaryOffset
# - AccelSignedBit
# - AccelSignedBit2
# - AccelTwoCompliment
# - AccelBinaryOffset
# Consult the controller's documentation to find out which mode to use.
EncoderMapMode: Absolute
# Buttons used here are expected to not be toggles (i.e., sending
# value 0 every second time you press it).
Bank1Button: -1
Bank2Button: -1
Bank3Button: -1
Bank4Button: -1
Bank5Button: -1
Bank6Button: -1
Bank7Button: -1
Bank8Button: -1
NextBankButton: 117
PrevBankButton: 116
LockButton: 118


[MixerControls]
# Again enter the appropriate CCs for the respective controls.
# If all sliders use the global channel to send their data,
# you can leave the channels at -1. You can, of course, use
# encoders or knobs instead of sliders.
VolumeSlider1: -1
VolumeSlider2: -1
VolumeSlider3: -1
VolumeSlider4: -1
VolumeSlider5: -1
VolumeSlider6: -1
VolumeSlider7: -1
VolumeSlider8: -1
Slider1Channel: -1
Slider2Channel: -1
Slider3Channel: -1
Slider4Channel: -1
Slider5Channel: -1
Slider6Channel: -1
Slider7Channel: -1
Slider8Channel: -1
MasterVolumeSlider: -1
MasterSliderChannel: -1
Send1Knob1: -1
Send1Knob2: -1
Send1Knob3: -1
Send1Knob4: -1
Send1Knob5: -1
Send1Knob6: -1
Send1Knob7: -1
Send1Knob8: -1
Send2Knob1: -1
Send2Knob2: -1
Send2Knob3: -1
Send2Knob4: -1
Send2Knob5: -1
Send2Knob6: -1
Send2Knob7: -1
Send2Knob8: -1
TrackArmButton1: -1
TrackArmButton2: -1
TrackArmButton3: -1
TrackArmButton4: -1
TrackArmButton5: -1
TrackArmButton6: -1
TrackArmButton7: -1
TrackArmButton8: -1
VolumeMapMode: Absolute
SendsMapMode: Absolute

[TransportControls]
# The transport buttons are also expected not to be toggles.
StopButton: -1
PlayButton: -1
RecButton: -1
LoopButton: -1
RwdButton: -1
FfwdButton: -1

So, what channel do I have my User Remote Script set to?
ImageImage

TomViolenz
Posts: 6854
Joined: Mon Dec 13, 2010 6:19 pm

Re: Not being to solo 'input' tracks that are routed elsewhere?

Post by TomViolenz » Wed Oct 30, 2013 9:16 pm

Wow shadx, your always a throve of useful information! I will take my time to get into that.
Thanks :D

BTW: The user mapping for Lives devices in Push is out. Discussion here: viewtopic.php?f=55&t=198946&p=1562408#p1562408

regretfullySaid
Posts: 8913
Joined: Thu Apr 22, 2010 5:50 pm

Re: Not being to solo 'input' tracks that are routed elsewhere?

Post by regretfullySaid » Wed Oct 30, 2013 9:53 pm

No probs, maybe the User Remote Script thing isn't made so obvious by Ableton for noobs to notice :?

Anyway, I say good job on managing a very useful hack for making custom banks, that's a big deal!
ImageImage

TomViolenz
Posts: 6854
Joined: Mon Dec 13, 2010 6:19 pm

Re: Not being to solo 'input' tracks that are routed elsewhere?

Post by TomViolenz » Wed Oct 30, 2013 11:23 pm

Thanks! tedlogan was heavily involved as well. It was actually quite fun to do :-)


Wouldn't wanna do it all the time though. This is all just the means to an end!

Post Reply