Note(s) at x.1.000 of clip not played

[gavindi]

I thought it was my imagination at first but its definitely happening.

I've imported a midi file and then I make clips of sections so I don't have to made the same edits ad-nauseum across the whole song.
I'm finding that the note at x.1.000 will constantly not play on various clips. Some will on other clips. But the ones that don't play constantly will never play.

That is until I move the midi note(s) to x.1.001, THEN, it WILL play!

Also, I've noticed that sometimes (only on certain clips) when changing the value to 001, another oddness happens.
Let's say I have a note at the start of a clip at 9.1.000 and it's not playing. On some clips, when I change the last value to 001 and press enter, I suddenly get 8.4.001 instead of 9.1.001. Other clips in the same track wont unexpectedly change the bar and beat measure and the tick changes as I'm trying to do with this work-around.

What is constant with both parts of this quirk is that either all notes at 1.000 do it or don't do both behaviours.

I wonder if splitting clips is scrambling note data somehow???

Something is not right here.

Gav

[gavindi]

Here's a bit more background information.

I imported a midi file that had 1 bar of silence at the beginning. I splitted all the clips to remove the one bar of silence and then selected all the clips (which now start at bar 2) and move them all to bar 1.

So before I started carving up all the clips, I've done a few splits and a bulk move.

Whether this starts to muddy the midi data or not, I don't know but I thought it may be worth mentioning.

Cheers,
Gavin

[Stuttaton]

Never start anything on beat 1.

[gavindi]

Never start anything on beat 1.

Haha. Funny.
It's a pretty annoying bug though since I have to adjust the ticks all the time.
Oddly, I don't think it happens with every imported midi either.

And when it does happen it even affect new notes entered on the first beat of the clip.

[Stuttaton]

Never start anything on beat 1.

Haha. Funny.
It's a pretty annoying bug though since I have to adjust the ticks all the time.
Oddly, I don't think it happens with every imported midi either.

And when it does happen it even affect new notes entered on the first beat of the clip.

I'm serious. It's been a rule ever since the first midi sequencer, not to put any notes on beat 1 of bar 1.

[dRowAudio]

We should be able to play notes on bar 1 beat one, does the behaviour experienced change with different synth or do all synth exhibit it?

If so, can you send us an example Edit file so we can see why the notes might not be being picked up? Please can you make this as minimal as possible otherwise it's extremely difficult to try and isolate the problem. Preferably a single track with a single MIDI clip with a single note. Thanks!

[gavindi]

Never start anything on beat 1.

Haha. Funny.
It's a pretty annoying bug though since I have to adjust the ticks all the time.
Oddly, I don't think it happens with every imported midi either.

And when it does happen it even affect new notes entered on the first beat of the clip.

I'm serious. It's been a rule ever since the first midi sequencer, not to put any notes on beat 1 of bar 1.

You've not read correctly then. It doesn't matter which bar the clip is on. Its the note on the first beat of the bar wherever that clip is.

And besides, it's a ridiculous rule you suggest that makes no sense I'm sorry to say. Regardless of which bar it is, the first even, its should not cause a technical fault within the software.

[gavindi]

We should be able to play notes on bar 1 beat one, does the behaviour experienced change with different synth or do all synth exhibit it?

If so, can you send us an example Edit file so we can see why the notes might not be being picked up? Please can you make this as minimal as possible otherwise it's extremely difficult to try and isolate the problem. Preferably a single track with a single MIDI clip with a single note. Thanks!

I'll send an edit that is currently causing this. 1.000 represents beat and tick. 1.1.000 would be bar, beat & tick, It can occur on ANY bar.

Do I just PM the file to you?

[Stuttaton]

Never start anything on beat 1.

Haha. Funny.
It's a pretty annoying bug though since I have to adjust the ticks all the time.
Oddly, I don't think it happens with every imported midi either.

And when it does happen it even affect new notes entered on the first beat of the clip.

I'm serious. It's been a rule ever since the first midi sequencer, not to put any notes on beat 1 of bar 1.

You've not read correctly then. It doesn't matter which bar the clip is on. Its the note on the first beat of the bar wherever that clip is.

And besides, it's a ridiculous rule you suggest that makes no sense I'm sorry to say. Regardless of which bar it is, the first even, its should not cause a technical fault within the software.

I'm speaking of experience. Historically, putting notes on beat 1 of bar 1 have been known to cause problems. Therefore I never do it. Maybe it works OK with today's software.
Putting notes on beat 1 on the first bar in a clip works. I do it all the time. The problem must have something to do with your copying and pasting.
There used to be a problem that a note on the first beat didn't sound the first time, when you looped the section between the in and out markers. But that seems to have been corrected. At least I haven't noticed it recently.

[gavindi]

Never start anything on beat 1.

Haha. Funny.
It's a pretty annoying bug though since I have to adjust the ticks all the time.
Oddly, I don't think it happens with every imported midi either.

And when it does happen it even affect new notes entered on the first beat of the clip.

I'm serious. It's been a rule ever since the first midi sequencer, not to put any notes on beat 1 of bar 1.

You've not read correctly then. It doesn't matter which bar the clip is on. Its the note on the first beat of the bar wherever that clip is.

And besides, it's a ridiculous rule you suggest that makes no sense I'm sorry to say. Regardless of which bar it is, the first even, its should not cause a technical fault within the software.

I'm speaking of experience. Historically, putting notes on beat 1 of bar 1 have been known to cause problems. Therefore I never do it. Maybe it works OK with today's software.
Putting notes on beat 1 on the first bar in a clip works. I do it all the time. The problem must have something to do with your copying and pasting.

As I said, it has nothing to do with the first bar!
Still, it's ridiculous what you suggest. The software should handle the first bat like any other.
It may be a problem with the software and not me and the issue may only exhibit itself under certain circumstances. So how about holding off on blaming me, huh? Let investigation happen.
Besides, even random copy/pastes (which this isn't) should not break basic functionality.
Anyway,you don't need to answer. I've PM'd a link to drowAudio so he can investigate.

Cheers,
G.

[gavindi]

I forgot to add that changing synths makes no difference.

[Stuttaton]

Could it be that there is controller data in the clip that causes this? Selecting and moving notes will normally not move controller data. Have you checked what data there is in the clip you import? You can use a tool like Midi-ox.

[gavindi]

Hey there Mr drowAudio,

I'm just wondering if you have had a chance to look at the export I gave you a link to. I'm curious if I'm somehow exploiting a issue or whether the playback worked for you or does as I described.

No pressure, I know you're a busy guy. Just asking...

Cheers,
Gavin