Ableton Forum

While working in the arragement mode, everytime I duplicate the Midi notes I record, I keep getting the copied or duplicated midi notes in another tone... very high pitched! I am getting crazy.... I have been using Live for years and it is the first time this happens...

Anyone having the same problem?

Insanerktacodorado.
OSX 10.4.9, Live 6.0.7 Powerbook G4, 1.25ghz, Layla 24/96.

I am having the same problem, it is pissing me off!
This is my first go at a project using ableton as a production tool (I usualy use logic 7.2) as I only use Live for DJ or sketches for ideas.
I am going back to Logic and I dont think I will be trying live again for a while to "Make" music!
I am trying to copy a Midi part but the tone gets fucked up and goes down 3 octaves!!

carlito828 wrote:I am having the same problem, it is pissing me off!
This is my first go at a project using ableton as a production tool (I usualy use logic 7.2) as I only use Live for DJ or sketches for ideas.
I am going back to Logic and I dont think I will be trying live again for a while to "Make" music!
I am trying to copy a Midi part but the tone gets fucked up and goes down 3 octaves!!

Hey carlito828, hope anyone there knows how to fix this... or if it is only a bug in the 6.0.7 code, guess I will contact Ableton support on this....

hi all,
is this problem also occuring on tracks with one of Live's native devices?

Or only with 3rd party plugins..?

There is a known bug in Live 6.0.7 that destroys parameter automation in arrange when duplicating clips/notes with 3rd party plugins..

This bug is fixed in the latest beta version..

you can try the latest beta to see if this solves your problem..

cheers..

Poster wrote:hi all,
is this problem also occuring on tracks with one of Live's native devices?

Or only with 3rd party plugins..?

There is a known bug in Live 6.0.7 that destroys parameter automation in arrange when duplicating clips/notes with 3rd party plugins..

This bug is fixed in the latest beta version..

you can try the latest beta to see if this solves your problem..

cheers..

Hey Poster, thanks for the info man! the problem only happens with 3rd party plugins and I am glad to hear that it is already fixed in the latest beta. For the meanwhile I went back to work with Live 5.... I will wait until the next update is released to work with live 6 again.

Poster wrote:hi all,
is this problem also occuring on tracks with one of Live's native devices?

Or only with 3rd party plugins..?

There is a known bug in Live 6.0.7 that destroys parameter automation in arrange when duplicating clips/notes with 3rd party plugins..

This bug is fixed in the latest beta version..

you can try the latest beta to see if this solves your problem..

cheers..

It mostly occurs with 3rd party plugs BUT I have had it occur on one track with Live Simpler instrument. Ive noticed this bug the most frequently with plugs like Zebra, Octopus, Sonalksis Eq, Ohmicide, and many more.
The workaround id to click the LOck Envelope button when Moving or duplicating the midi clip. And then just copy and paste any other automation by hand using the copy/duplicate automation option.
I really hope this bug is truly fixed in the next point upgrade.

audiovoid wrote:

Poster wrote:hi all,
is this problem also occuring on tracks with one of Live's native devices?

Or only with 3rd party plugins..?

There is a known bug in Live 6.0.7 that destroys parameter automation in arrange when duplicating clips/notes with 3rd party plugins..

This bug is fixed in the latest beta version..

you can try the latest beta to see if this solves your problem..

cheers..

It mostly occurs with 3rd party plugs BUT I have had it occur on one track with Live Simpler instrument. Ive noticed this bug the most frequently with plugs like Zebra, Octopus, Sonalksis Eq, Ohmicide, and many more.
The workaround id to click the LOck Envelope button when Moving or duplicating the midi clip. And then just copy and paste any other automation by hand using the copy/duplicate automation option.
I really hope this bug is truly fixed in the next point upgrade.

Hi,

Have you tried the latest beta? It is available on the top post of this forum section. Any feedback would help.

Regards,
Amaury

Amaury wrote:

audiovoid wrote:

Poster wrote:hi all,
is this problem also occuring on tracks with one of Live's native devices?

Or only with 3rd party plugins..?

There is a known bug in Live 6.0.7 that destroys parameter automation in arrange when duplicating clips/notes with 3rd party plugins..

This bug is fixed in the latest beta version..

you can try the latest beta to see if this solves your problem..

cheers..

It mostly occurs with 3rd party plugs BUT I have had it occur on one track with Live Simpler instrument. Ive noticed this bug the most frequently with plugs like Zebra, Octopus, Sonalksis Eq, Ohmicide, and many more.
The workaround id to click the LOck Envelope button when Moving or duplicating the midi clip. And then just copy and paste any other automation by hand using the copy/duplicate automation option.
I really hope this bug is truly fixed in the next point upgrade.

Hi,

Have you tried the latest beta? It is available on the top post of this forum section. Any feedback would help.

Regards,
Amaury

Actually I've been holding off on installing the beta on my macbook because I have a bunch of important projects going and didn't want to potentially mess anything up.
But I may just go ahead and do it. I'm curious though. Can the beta exist alongside my regular installed version in osx? Or will it install over it? And , if so, SHOULD I instal right over the top of it or should I 1st uninstall my previous version?

Its gone into release already. Live 6.0.9

http://www.ableton.com/latest_versions

You can keep multiple versions of Live without a problem. Its always recommended to keep the version that "works" in case the update breaks something.

hoffman2k wrote:Its gone into release already. Live 6.0.9

http://www.ableton.com/latest_versions

You can keep multiple versions of Live without a problem. Its always recommended to keep the version that "works" in case the update breaks something.

Oh Wow. You're right. That update slipped right under my nose.
Installed it. Problem solved. Havn't played with it extensively enough to say if there's any other issues but so far it seems solid.
One project that I was working on seemed to be a little higher on the cpu meter than I remember it being, but that could be a number of things as well.
thanks hoffman.