Ableton Forum

I'm afraid it won't be Capture related. The best way would be to send in the crash report.

Yeah capture is amazing. Stuff like this is one of the reasons i love Ableton. Companies like to throw around the word innovative but this actually is. And it really coalesces with Ableton's philosophy of facilitating the free flow of creativity. This feature has been in Logic since v5, which is wh...

Since day one my music is different after hitting record. :mrgreen: My fingers lose 20% of their dexterity and I forget the chord sequence immediately that the record button is pressed. these days I have my FCB footpedals linked up so that really helps. A pedal for "record into selected clip&q...

what's the external? can you share it?

post_immediate_completion is the last call
https://github.com/chriskohlhoff/asio/b ... eduler.ipp

@Pinner you should probably check out the Midi version of B-Keeper and see if it works for you https://github.com/Venetian/B-Keeper/tree/master/BKeeper4Live/BKeeperMIDIProject are you windows or mac? I think I need to change a few things here before this works though. BeatSeeker might work on finger...

Sounds good. Send me some audio (without the gate), I can have a look/listen at what you're trying to track and maybe there could be an improvement? just a dropbox link or something. BeatSeeker should be flexible to adapt to drums but I'm interested to widen the material I can develop on. It's prett...

here's the code from BeatSeeker that grabs the footpedal from Push or Push2. <pre><code> ----------begin_max5_patcher---------- 3961.3oc2cs0iiZjE9YO+JPVqz9hSKpabYeaxFsQ4gHEo7zpnHKroZ2jfAKn bOSmnr+1WpKfAatT9BE3LRi6tAa747Um5bmC+4mVrbS5Wo4Ks9WV+h0hE+4m VrPbH9AVn96EK2G70swA4h21xD5WR27aKWIOEi9Ul3voIzMAI6...

Those settings are all fine. Main thing is, not zero. Only adjust response value. Ignore the reset. Latency refers to the latency between getting a click input and processing a kick drum audio signal and getting an event in. There are two ways to run B-Keeper. 1. Internal Click, which is pretty easy...

if you have a question, I could probably answer. In terms of setting up, I would just ignore most of the 'expert panel', but you definitely want to check you have decent parameter settings (just adjust the 'response' dial to a fairly high number).

I think you need to specify what device this is, what computer and version of Max. As I mentioned, I tried them all and they work fine. But your problem looks like something with viddll.

Here's a patch to look out for the Push pedal on second input. <pre><code> ----------begin_max5_patcher---------- 3974.3oc6csziqZjEdsu+JPVizrw4JpmTL6RlnIJKFoHkUihhrv1U6lDLXA3 9d6Dk+6S8.vfMXWfgxzildgcaddpu5Tm2b3O+zhkaR9JOaoy+v4WbVr3O+zh EpMI2vhheuX4gfutMJHScXK2bJOOId4J8tRNkGwyye+HWeMVtIHd+RmesX2Y 4uG...

what object is this from? It's the viddll engine that's the problem, not the IRCAMMAX 2. I tested all the objects and they're all fine.

https://cycling74.com/max7/#.V4eNwZN95TY

are you on Max 7?

use the max essentials midi monitor, ro something, to see - does it receive MIDI from the Roland?
ignore the song stuff first.

you can email me andrew.robertson@ableton.com

It could be that the problem here is the use of Windows and Direct X. Sometimes the default buffersize on windows is set to 8192, over a hundred milliseconds of latency. It may be the case that direct x requires quite large buffersizes generally - eg 2048 ~= 40 ms. In your case, can you use asio dri...