Serious problem recording MIDI CC# data

pix · Post by **pix** » Sun Oct 30, 2005 5:57 am

I'm tired of posting this here.

There's a serious bug when recording midi CC# data into midi clips.

Somehow the data from previous clips is not erased and appears on new clips no matter what you do.

This is absolutly frustrating and makes it impossible to sequence external gear with it.

Can someone please tell me if there are workarounds?

Thanks

peeddrroo · Post by **peeddrroo** » Sun Oct 30, 2005 12:31 pm

can you give a step-by-step procedure for reproducing this?
that would be easier to see what your prob is.

pix · Post by **pix** » Tue Nov 01, 2005 7:02 am

OK,

pick up anything that sends midi CCs.

Start recording a midi clip and tweak a couple of knobs.

Stop and start recording another clip on the same midi track. Don't tweak anything this time.

Check the midi CC# info on the new track. You'll see that there's stored info there. It's like all CC#s tweaked previously are also saved in the new clip even if those knobs are not tweaked. And the "stuck" value is the last one tweaked in th efirst clip.

I really find strange that no one notices this. I think most users are not sequencing external gear. But this is a serious flaw. All clips should start clean.

Does this happen with you too?

Hedroom · Post by **Hedroom** » Wed Nov 02, 2005 1:08 pm

Yep. I started a thread about this here

http://www.ableton.com/forum/viewtopic. ... +midi+moog

I emailed Ableton about it but strangely they didn't appear to be able to reproduce it.

Email them about it and it will add credibility to the bug report.

It is a very annoying problem

Hedroom · Post by **Hedroom** » Wed Nov 02, 2005 1:10 pm

Haha. Just looked at the thread. Turned out it was you I was discussing it with!

pix · Post by **pix** » Wed Nov 02, 2005 11:02 pm

this is quite strange. It happens with everything I try. I guess most Live users are not using it to sequence external gear. Otherwise this had alrady been noticed.

henry ford · Post by **henry ford** » Thu Nov 03, 2005 6:18 am

ya , it happens with me too....i noticed it before but i thought thats the way they intended to implement it.....its probably useful to some people , more importantly did live 4.1.4 do the same thing ?

this whole 'we cant reproduce it' thing is making me SICK....day after day i check this forum hoping for a post from robert , or whoever , with news of an update.....

pix · Post by **pix** » Thu Nov 03, 2005 6:38 am

al last! someone that actually made the effort.

thanks!

I really can't imagine why this feature is useful. It actually records data in a fresh clip. It makes no sense. Imagine that you record some notes and then want to edit the paych you're working on.

You junt can't!

The patch jumps to the recorded state everytime the clip loops. All CCs are dumped and you patch is restarted. Really. I can't see why this could be implemented. Can you think of a reason?

henry ford · Post by **henry ford** » Thu Nov 03, 2005 1:49 pm

well....

it inputs the CC at whatever value the knob/fader was last at in the previous clip....so say it started recording the next clip with all the CC's set to 0...if you move the knob/fader the cc value would 'jump' to its position - and it would not follow the previous clip 'smoothly'.......i guess the idea is that they'd like each clips cc's to follow the position of the knobs or faders 'smoothly'.......... but this is actually counter-productive if you're just making a serious of different, independent clips/loops........as opposed to a continuous chain of clips

i'm guessing here.....it's not the way I work , and its a pretty intrusive assumption if indeed its implemented that way intentionally ..... but i can imagine someone finds it useful......as always , you could 'workaround' it by creating some empty clips with the CC'S at 0 and duplicating them , and use the OVERDUB function to write the notes (and new cc data)

but splashmas said
I emailed Ableton about it but strangely they didn't appear to be able to reproduce it.

??

anyways , for what its worth i'd like if it was possible to disable this

but i've not been emailing the abes about any further problems , i've done all i can to remedy the different problems here and there.....i'm just waiting for an update now.

another problem i've been having is that everytime i ARM a midi track , with midi input coming from 'all ins' .....it doesnt pick up the midi data im sending from my keyboard/controllers ......i have to manually select my interface first , and then switch it back to 'all ins' ...... what the hell is that all about..... the midi implementation reaks of something unpleasant - i think its the most important thing that needs to be addressed above all else......

pix · Post by **pix** » Thu Nov 03, 2005 8:08 pm

henry ford wrote:the midi implementation reaks of something unpleasant - i think its the most important thing that needs to be addressed above all else......

agreed. Even most of the PDC problems seem to be related with midi.