Ableton Forum

Hi,

Alot of guys here seem to be NI Maschine users, so I thought I could ask this question here. I've tried to search if anyone else has had this problem, but couldn't find anything. I have a problem with NI Maschine; I've set it up so that it is using MIDI Program Changes to change scenes; this works fine. I work mostly in arrangement view and thus control scene changes in NI Maschine by MIDI clips; I put sync to off and tick retrigger on in NI Maschine.. now the problem ensues: I have a simple 8 bar loop with a kick on every 1/4; standard stuff. For some reason, the first kick when I change the scene is doubled.. i.e. it is played twice so it sounds almost like it has a chorus effect on it. The second and sequential kicks are fine; its only the initial kick that is a problem. This problem dissapears if I either

a) Turn Retrigger off
b) Set Sync to something else like 1/1, Scene etc.

But none of the solutions above are what I want. If anyone wants to test this out, here's how I can simply reproduce this:

1) New Song, 4/4. Create a new pattern with a simple kick on the first beat and set its length to 8/1. Put in a MIDI Clip at bar 13 in arrangement view in Ableton Live and set its program change so that it fires the scene that plays the clip. The first kick is for me clearly doubled at least.

This problem also goes away if you for example move the clip to start at bar 9 and set retrigger off.. but thats really not a good solution.. can anyone else verify this?

Sorry in advance for yet another Maschine thread on the Ableton boards...

I don't wanna be rude but, i'm not asking questions about my laptop or my pre-amps here.

Let's focus on the app Ableton Live I'm sure there is a bunch of maschine forums out there..

Peace

I know, I know... but the problem I'm having is that I don't actually know who's fault it is.. I mean, can this behaviour be reproduced in Logic? I dunno.. I only use Live and I *did* say I was sorry at least!

and there sure seems to be alot of NI Maschine users that also use Ableton Live so I mean, someone here must have experienced this no? Anyways, just ignore this thread if you don't have NI Maschine.. its not like its worth getting upset about

And Live does have a tendancy to skip back when you start playing sometimes at the start of a loop - which if it happens very quickly might result in a double note.

Anyway - this is a music and production subforum, not an ableton live forum - thankfully at least it aint full of amercian politics anymore and TBH - most quirks Ive had with plugins have usually been a Live specific quirk (back inthe days NI massive and Sylenth1 used to crash all the time for eg I remember it being quietly fixed in an update to Live).

I can confirm this behavior. I don't have a solution though, sorry.

I've never come across this even when I tried triggering Maschine from Live via program changes and MIDI notes. Just wanted to say people should seriously consider audio drag and drop from Maschine as a workflow alternative. I've found that dragging audio from Maschine makes me much more productive since it encourages making decisions and committing to it. And you can still make changes in Maschine and drag out the new audio so you still have full control.

@pedx1ng: Thanks for confirming this I can reproduce this quite easily and its really doing my head in

@delicioso: Actually I just tried to export to audio cause I could have sworn that the same behaviour was there (the first kick comes off wrong) last time I tried that but the audio loop turned out perfect.... Ideally I would want to stay "in the box" and not have audio drag, but at least its a workaround for now... thanks for making me check it

I hope they fix it though... I'll let NI and ableton know about this bug and hopefully they´ll sort it out

I have this problem w/ my Axiom, Roland V-drum and MPKmini anytime I enter a not it does a flam (a tiny not right before the longer note) I'm plugged in w/ USB and a Fast Track Pro. Doesn't matter same flamming. It is sucky. What version do you guys have? I'm still on 8.0.5. Was working fine for me till I found this. Maybe updating may be a good idea now.