Ableton Forum

When I have a clip that already has note data in it selected, and I click the Arm Session Recording button and play a few notes, it records very very short notes where ever the cursor happens to be, even though the transport is stopped.

Is that suppose to happen?

It doesn't do that in the previous version and I don't recall anything about step entry using a MIDI controller being mentioned in the manual... maybe I missed that though.

Hi no_barcode,

sorry but I do not yet understand what you mean. Can you explain it a bit more detailed in from of a step by step guide?
And / or can you send me a Live Set to demonstrate this problem?

regards,
/Alex

Hi Alex, I'm at work right now so I can't send you anything until a bit later.

But here's what I did, and I was able to reproduce it each time using the new beta:

1) Have two MIDI tracks with Simpler in each one. (I didn't try it with any other VSTis, so I don't know if it is specific to Simpler or not.)

2) Have a clip in the first MIDI track with MIDI note data recorded to it.

3) Do *not* have Live playing or recording.

4) Arm the first MIDI track.

5) Arm the second MIDI track, you may want to also click on an empty clip in the second MIDI track.

6) Arm the first MIDI track again.

7) With Live still not playing or recording, play some notes on a MIDI controller.

8) It should start "recording" very short MIDI notes in the clip, right where the transport/cursor is in the clip.

I think that's what I did... I'll double-check when I get home, though.

I just confirmed these steps and it will produce recorded notes just like I said...

Anyone else care to confirm this? I can't stand to have anymore problems that are supposedly related to my choice of audio interface or processor or a combination thereof... it will drive be mad. Crazy MAD! I TELL YOU!

just tried this , can´t see this happening tho . . .

Obineg wrote:just tried this , can´t see this happening tho . . .

Using the latest beta?

Anyone else who's using a Windows PC and the latest beta care to try this?

Two MIDI tracks with simpler in each one.
Record something to a clip in the first one.
Stop everything.
Arm the second, empty track.
Arm the first track again.
Play something on your MIDI controller.
It should record very very short notes, right where the "cursor" is in the MIDI clip on the first track.

C'mon people! How could this only happen on my machine? I feel much better about bugs when I'm not the only one experiencing them.

no_barcode wrote:When I have a clip that already has note data in it selected, and I click the Arm Session Recording button and play a few notes, it records very very short notes where ever the cursor happens to be, even though the transport is stopped.

Is that suppose to happen?

It doesn't do that in the previous version and I don't recall anything about step entry using a MIDI controller being mentioned in the manual... maybe I missed that though.

Same here! Really short notes get recorded (a couple of ticks long) in a clip that already has note data. Bug I think.

djsynchro wrote:

no_barcode wrote:When I have a clip that already has note data in it selected, and I click the Arm Session Recording button and play a few notes, it records very very short notes where ever the cursor happens to be, even though the transport is stopped.

Is that suppose to happen?

It doesn't do that in the previous version and I don't recall anything about step entry using a MIDI controller being mentioned in the manual... maybe I missed that though.

Same here! Really short notes get recorded (a couple of ticks long) in a clip that already has note data. Bug I think.

Yes! I knew it wasn't just me. However, I am going to have to claim this one djsynchro -- I was just here first, so, you know the saying: "finders keepers".

I would like this one named after me, please.

The no_barcode bug

djsynchro wrote:The no_barcode bug

That has a nice ring to it, doesn't it?

Hi no_barcode,

finally I got it. I needed some time to understand what you did mean with "cursor"

It is easy to reproduce:

1) Put a MIDI clip (empty or now) into a MIDI track and fire the clip
2) Stop the song via transport stop (Space-bar) so the MIDI clip still has its green arrow
3) Arm the MIDI track and the MIDI clip switch to record state indicated by the red arrow
4) Now play MIDI events from internal or external MIDI keyboard and these MIDI events will be recorded on the current playing position of this clip


We will take care of this,
just a bit patience

regards,
/Alex

Alex wrote:Hi no_barcode,

finally I got it. I needed some time to understand what you did mean with "cursor"

It is easy to reproduce:

1) Put a MIDI clip (empty or now) into a MIDI track and fire the clip
2) Stop the song via transport stop (Space-bar) so the MIDI clip still has its green arrow
3) Arm the MIDI track and the MIDI clip switch to record state indicated by the red arrow
4) Now play MIDI events from internal or external MIDI keyboard and these MIDI events will be recorded on the current playing position of this clip


We will take care of this,
just a bit patience

regards,
/Alex

Oops. Sorry about that Alex. You're quite right, describing it as "the current playing position" does make far more sense than saying cursor.

I'm not sure why I was I saying cursor. It made sense to me when I was writing it.

no_barcode,

Oops. Sorry about that Alex.

Don't worry. There is no reason to excuse for something.

I'm not sure why I was I saying cursor. It made sense to me when I was writing it.

Same for me. If I write something if feels mostly logical and understandable to me ... until I read it some hours later

regards,
/Alex

Hi folks,

this should be solved within the latest beta Live 5.0.3b6:
http://www.ableton.com/forum/viewtopic.php?t=31022

regards,
/Alex