Device Details

Device Overview

Name/Version: Trigger Finger 2.0
Author: ctignor  
Description: Now for 64-bit!

Full docs at:
http://www.wiresundertension.com/soft/doc/TriggerFinger/TriggerFinger-UsersGuide.pdf

Play your favorite synth or sampler by kicking a drum, plucking a string, or creating any other decidedly percussive acoustic racket. The louder you play, the louder your synth plays. As for what note it plays, pick one manually or better yet, provide your own set of pitches for it to cycle through with every hit. That’s right, composition meets electronic music you actually play with acoustic instruments.
 

Device Details

Tags effect, utility, other
Live Version Used: 10.11.6
Max Version Used: 7.3.6
Date Added: Feb 15 2016 18:35:03
Date Last Updated: Aug 04 2019 05:25:41
Device Type: audio_device
Download URL (report link) http://www.wiresundertension.com/soft/TriggerFinger-2.0.zip
License (more info): AttributionShareAlike


Comments

Thanks for this. I had hacked a coll instrument but has a few limitations. How long can your "cycle" of notes be? How many notes can your "coll" fit?
Also my instrument didn't have velocity response which in some situations you want a "dumb" velocity--always the same velocity.
Does this have responsive velocity only?

@Sinex5:

All great questions!

Answers below and check out http://www.wiresundertension.com/soft/doc/TriggerFinger/TriggerFinger-UsersGuide.pdf

for this info and more too.

"How many notes can your "coll" fit?"

I don't know of any upper bound on this. The amount of memory is trivial so unless coll itself has some arbitrary constraints I'd be surprised there'd be any practical ceiling here. I've personally used > 100 pitches myself.

That said, in practice, it's almost always more practical to keep these cycles smaller and more manageable. This is why the device supports breaking songs into different "cue" sections. That way you can organize your songs into more manageable cycles. From a live performance standpoint (the purpose of my devices) what if you get "off" by one while performing one of these cycles? Better that you're not off for the entire work and just a smaller section. Organization is key.

"in some situations you want a "dumb" velocity--always the same velocity"

So true.Too much velocity sensitivity can be super annoying. This device allows you to choose a range that maps input level to the 0-127 velocity range. You could use this to effectively pin the velocity to 127, then use M4L's built in velocity device to scale this to whatever you like. Note, you could use this second step for your instrument too - just use a "fixed" velocity in the utility provided with Live and send your notes to it.

I agree it would be good to add direct support for just fixing the velocity w/o going through these steps. Great though for the next version - thanks!

Ive been having a hard time getting this to work. I set up my midi buffer, which I can't tell if its working correctly. I wonder where the problem would be. On a separate note, I had the idea of merging a device such as this with a Markov chain which would use a table of probabilities yet be able to trigger it manually--I like the idea of probabilities as well as determined notes. Don't get me wrong this (once I get it to work) will 1. help me to understand Midi and colls or libraries as you have it here, and two allow me to perform more elaborate pieces including triggering rests (awesome by the way!)
Anyways thanks for this.

@Sinex5:

A common problem is setting up the virutal MIDI buffer.

Feel free to write me at ct [at] wiresundertension.com with some screen shots and I can try and get you there.

Hi there! Thanks so much for this plugin, it's exactly what I've been looking for. I use a crappy wooden stomp box (which I can now make sound like an actual kick!) but I want to set it up as a MIDI trigger mapped to toggle a clip on/off. There's not much about how to do it in the user guide and I'm still quite new at MIDI and Ableton, so was hoping I could get some instructions

Thanks again! (also I find the music you make incredibly awesome and inspiring)

Hi there! Thanks so much for this plugin, it's exactly what I've been looking for. I use a crappy wooden stomp box (which I can now make sound like an actual kick!) but I want to set it up as a MIDI trigger mapped to toggle a clip on/off. There's not much about how to do it in the user guide and I'm still quite new at MIDI and Ableton, so was hoping I could get some instructions

Thanks again! (also I find the music you make incredibly awesome and inspiring)

@timg:

Once the device is outputting MIDI it's easy to map these messages in Live to whatever you want using Live's great MIDI-mapping capability.

Make sure, as per the Users Guide, you have your virtual MIDI bus that TriggerFinger is sending to set-up to receive on "Remote" Input (The guide also specifies "Track" Input for sending midi for playing instruments on other tracks).

Then, simply MIDI map the clip you want to play to the note you want to use. This is most easily done using some other MIDI device (e.g. a keyboard). More on MIDI-mapping Live in the "Manual Mapping" section here:
https://help.ableton.com/hc/en-us/articles/209069249-Getting-Started-3-Setting-Up-Your-MIDI-Controller

Then when TriggerFinger triggers a MIDI note on the channel corresponding to the note/channel you MIDI mapped your clip to, it will trigger it just like any other MIDI event would.

@timg:

One further thing: I'm not sure if Live supports toggle on/off capability for triggering clips via MIDI. You might be better off putting your sound into a Drum Rack at a specific note and then using TriggerFinger to simply send notes to this track through the virtual MIDI bus as described in the Users Guide.

Awsome!
Made it work on with Ableton 9.7 32bit.
But.... I loaded the same project using Ableton 10 64bit and It did not work.
I'm on OSX 10.11.6 (El captain) using a mac Intel from 2009.

Please, could you tell me if it should work the same with Ableton 10 ?

I opened the device using Max4Live and I noticed that the midi output and input names were not the same as in Live 9. I mean Live 9 prints a list using the default virtual midi bus (IAC Driver Bus IAC 1) whereas in Live 10 it prints "IAC Driver track-remote bus" and "IAC Driver track bus".

I RTFM but could not find a tip relating to my problem.
Any advice?

Thx a lot

Ok, so sorry I RTFM once again and it is boldly written : "currently available only as a Mac OS device for 32 bit Live"
my fault.
Could you tell me if it should be complicated to make it work with 64bits? I'm a developer and I could give a try if you don't mind.
Let me know

Login to comment on this device.

[ browse device library ]