Ableton Forum

I wonder if it would keep time if I was bangin' away on something else!

...wow, sorry. Had to say it.

party on!!

now worries,

HIT ME!

guess I am too tired these days....

well then.
its time for a little bump innit.

yur2die4 wrote:That B-Keeper looks flipping amazing. Where do you go from there? Artificial intelligence?? Scale detection? haha

yep, one step furthur down the line:

http://www.ableton.com/schwarzonator

I would think its the keyboard players job to keep Ableton in time! My drumer used to have an extra footpedal from a digi kit linked to the tap tempo it worked fine for us till he got some pimp ass in-ears and now plays to a click

No, No... its definitely the tambourine players job to keep time... definitely.

malutki wrote:

yur2die4 wrote:That B-Keeper looks flipping amazing. Where do you go from there? Artificial intelligence?? Scale detection? haha

yep, one step furthur down the line:

http://www.ableton.com/schwarzonator

Freaking awesome! Really cool plugin.

H20nly wrote:No, No... its definitely the tambourine players job to keep time... definitely.

HA AHAHAHH ARA .

Hate tambourines. They always sounds way too loud !!

But thanks for the advice.

Just got the B-Keeper installed lets see what it can do..............

garyboozy wrote:i wouldnt bother with circular logic, i found it way too difficult to use. as soon as you change up the tempo slightly, bringing it back down is a nightmare. not really the software's fault, more to do with humans wanting to keep in time with the music, not the other way round. ymmv, though.

Hey all,

I'm the developer of InTime. A quick note to say that if you experience the trouble garyboozy mentions above with InTime, adjust InTime's "Tracking Bias" setting. It's like bias for your sequencer; to adjust for latency in your system and your playing style. It's definitely harder to slow down smoothly than speed up, so you can adjust the bias to change InTime's sense of "now", making it easier to slow down.

InTime can track your playing even if you improvise, switch between 2- and 3-feels, and stop playing for a stretch. You don't have to even play a single downbeat if you don't want.

You don't have to be a great drummer or musician to use InTime, but you do have to have decent control of your tempo.

Check out some videos here: http://www.circular-logic.com/support/i ... ideos.html

Let me know if you have any questions.

-Michael

Just got an idea to move the tempo up and down. As far as on Windows anyways. You could easily write an autohotkey script to snap its focus on the bpm location and then map a keyboard, midi, or any device to send up and down keys! If you really want to get fine with it send shift up and down!

In M4L you could create a patch which would be triggered by two different midi notes, your up note and your down note.

It would get the tempo property of the song object. It would then add or subtract 1 to that value based on the input note.

You guys were also talking about mapping a knob to the tempo - I haven't done this before, but maybe you could create a program which would do the same thing as the M4L patch I described - it would just output midi to Ableton which you would map to the tempo in midi mappings. You could use MAX (full ver) or Pd to do such a thing....or anything with a MIDI library/interface. I assume the midi message is interpreted in a relative manner "go up one" opposed to "set tempo to 120", since there are 127 values which can't cover all tempos

If anyone is interested in the M4L patch, I could probably bang it up in a few minutes...and I've been at this for a week or two....so it's pretty simple.

sgreene wrote:In M4L you could create a patch which would be triggered by two different midi notes, your up note and your down note.

It would get the tempo property of the song object. It would then add or subtract 1 to that value based on the input note.

You guys were also talking about mapping a knob to the tempo - I haven't done this before, but maybe you could create a program which would do the same thing as the M4L patch I described - it would just output midi to Ableton which you would map to the tempo in midi mappings. You could use MAX (full ver) or Pd to do such a thing....or anything with a MIDI library/interface. I assume the midi message is interpreted in a relative manner "go up one" opposed to "set tempo to 120", since there are 127 values which can't cover all tempos

If anyone is interested in the M4L patch, I could probably bang it up in a few minutes...and I've been at this for a week or two....so it's pretty simple.

@sgreene
Yeah I'm still looking for a solution FOR triggering for one pad (tempo +1bpm) and another pad for (tempo -1bpm).
Is that possible for you to share stuff you did in M4L and having it run in my Live 8 (without the M4L's license). The would be Christmas in my heart my friend

THanks for looking

No, you have to buy max for live for any use.

If the solution could be created in Pd, it would be free to write and use.

sgreene wrote:No, you have to buy max for live for any use.

If the solution could be created in Pd, it would be free to write and use.

Really ? I thought I could run a plug-in created with Max just by using the Runtime from Cycling '74. I saw that on the page http://www.b-keeper.org:

You can download B-Keeper here as a zip file with instructions and everything else everything you need to get going. It has been created with Max/MSP and so requires you to download Max/MSP Runtime (choose Max/MSP Runtime 4.6.3) freely available from Cycling '74. B-Keeper is written as a Max/MSP application so uses the free Runtime environment in order to run.

Thanks for confirmations of anyone