Device Details

Device Overview

Name/Version: ProgramSelect 1.0
Author: amitmusician  
Description: UPDATES

Fixed crash on adding new tracks
Fixed more bugs

---------------------------------

I just started learning max4live and wanted to create a device that can help map program select messages from a midi controller to events like arming a track / changing chain selector values in Instrument Rack, etc.

This is my first attempt at building any max4live device, so I believe this will have many bugs.

Just create a midi track and load this device. You can see two midi mappable buttons to open the device in a popup.

You can see the device has 16 slots that can be configured to arm a group of tracks exclusively.

These 16 slots can be triggered by program-select messages from a midi controller. Also, you can midi map/ keymap to activate these slots.

There are two possible options for all the midi mapping/key mapping. One button should be used for mapping to the midi controller's switches, which send 0 when pressed and the highest value when released.

For mapping to note on messages or keyboard keys, use the non toggle mode button.

The first, last, previous, and next buttons are also midi mappable similarly. All the configuration gets saved as a part of the live set.

I have tried my best to observe track addition/deletion/move and fix the mappings.

There are three different modes of operation for each slot.
There is a tracks-only mode, where a group of tracks can be exclusively armed.

There is a param, only a mode. This can be useful for mapping to a chain selector in an instrument rack. When the program slot is activated, the track containing the instrument rack will get exclusively armed, and the chain selector will be set to the configured value.

Param mode can be combined with tracks mode to provide an easy way to layer additional tracks with an instrument rack.

Also, note. Exclusive arming only unarms tracks that are configured in some way in this device. This device will not unarm tracks that are not configured for any slot. This can be useful to work with different controllers, which are always on armed tracks and are not affected by this device.

As of now, this device works beautifully when used with the Nektar GXP49 which has 10 buttons dedicated to sending program select messages.
 

Device Details

Downloads: 155
Tags beta
Live Version Used: 11.2.5
Max Version Used: 8.3.3
Date Added: Oct 30 2022 05:08:39
Date Last Updated: Oct 30 2022 18:06:07
Average Rating (1) 3
Rate this device: (must be logged in to rate devices login)
Device Type: midi_device
URL (optional):
License (more info): Attribution

Device Files

Device File: ProgramSelect.amxd
 


Comments

I can't figure it out.

I can get the Set Selected Track button to populate the dropdown next to it.

But I can't get the other Set button to do anything.

Sending PC to the track's MIDI channel does nothing.

Do I need to assign the chain selector of the track's instrument rack?

I eventually got it to work after unmapping a Macro I had assigned to the chain selector. But the latency is much greater than just using the Macro for chain select, since I wanted to be able to "p-lock" program changes to specific notes.

I really just wanted a simple PC->Chain select device so if you can recommend one. Hopefully it would have lower latency.

Login to comment on this device.

[ browse device library ]