View Issue Details

IDProjectCategoryView StatusLast Update
0003133ardourbugspublic2020-04-19 20:14
Reporterdanboid Assigned Tocth103  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Target Version3.0-beta1 
Summary0003133: MIDI note placed on first beat of first bar doesn't get played
DescriptionMIDI note placed on first beat of first bar doesn't get played but subsequent notes do. Present in r7100.
TagsNo tags attached.

Relationships

related to 0003481 closedcth103 Only first MIDI note is played on first playback of sequence 

Activities

danboid

2010-05-25 09:30

reporter   ~0008023

I didn't describe this bug correctly and it still exists in 7155.

If you have a midi note(s) that begins on the first beat of a region, the first note(s) don't get played back if you start the playhead playing from the start of that region. If you move the playhead before the beginning of the region, the first note(s) within will get played.

danboid

2010-07-01 23:23

reporter   ~0008373

This is in my opinion now the most glaring and oft complained about bug with A3s MIDI playback as it stands and is still present in 7352

paul

2010-07-25 19:27

administrator   ~0008637

fixed in rev 7491 ... this was caused by applying global/transport declicking to MIDI as well as audio, and is fixed by not doing this (new method Amp::declick())

please confirm.

danboid

2010-07-25 22:57

reporter   ~0008640

Preeety much, yes!

With both phasex (ALSA MIDI synth) and bristol running via JACK MIDI under 7492 the first note on the first DOES get played now but unfortunately not the very first time you hit play. Every subsequent play the first note on the first bar does sound so its almost fixed.

Thanks Paul!

danboid

2010-07-26 21:06

reporter   ~0008657

moshisushi brought it to my attention that the first MIDI note in looped region gets dropped every cycle. I certainly hear/see this under 7498.

danboid

2010-08-05 18:30

reporter   ~0008727

Just been trying this again under 7546 and if I loop an edit range the first note of the range only gets played once every 4th cycle.

cth103

2010-08-11 02:30

administrator   ~0008801

Could you perhaps try again? 7582 contains a possibly-related fix.

danboid

2010-08-11 09:57

reporter   ~0008803

First note in a looped range still doesn't play except for on the first run-through under 7594. The 'VU meter' for the midi track bounces up on the first note as if it is being played on every cycle though.

cth103

2010-08-12 00:12

administrator   ~0008809

I'm having trouble reproducing this now. Could you perhaps attach a small example session (with the MIDI file) to this bug?

2010-08-12 07:10

 

loopprob.tar (40,960 bytes)

danboid

2010-08-12 07:13

reporter   ~0008814

Small example session uploaded. Creating this made me realise that simply pushing the loop playback button makes A3 think the file has changed, which seems strange.

cth103

2010-08-12 09:59

administrator   ~0008815

Thanks, that's reproduceable here.

cth103

2010-08-13 02:14

administrator   ~0008817

Fixed in SVN, I believe.

danboid

2010-08-13 08:49

reporter   ~0008820

Looping works fine now as far as the first note being played is concerned but should a session be flagged as being changed just because you push the 'Play loop range' button as that still occurs under 7614?

This issue has to remain open though as we still have the problem of the first note not being played on first run-through when just using the regular play button under 7614. First note does play fine on subsequent playback attempts however.

cth103

2010-08-13 11:34

administrator   ~0008822

I can't reproduce the first-note-not-played problem. Can you describe the exact steps you follow to trigger it, from loading the loopprob session?

danboid

2010-08-13 11:51

reporter   ~0008823

You won't experience this issue with the loopprob session because that session/track has already been played and this problem only occurs on newly created MIDI tracks on very first playback. Weird, I know!

You need to create a brand new MIDI track (doesn't need to be a new session), insert some notes (the first one being at the very start of the region) and make sure it is hooked up to output to a synth before you play it back. The first note plays back on subsequent attempts and also plays back fine if you save/ reload the session- it just on the very first time you play back a new MIDI track that the first note gets dropped.

cth103

2010-08-13 17:01

administrator   ~0008826

I can't reproduce this, unfortunately. Can you double-check with jack_midi_dump to make sure that it's not the synth's fault? (says he trying to shift the blame ;)

Where abouts are you putting the new region on the midi track? What are your grid settings when you are setting this up?

danboid

2010-08-13 19:38

reporter   ~0008827

Sorry Carl, my fault for not being specific enough but I can verify the missing note with jackmd.

Create a new MIDI track, set grid mode to Grid, grid units to Bars, push rewind to make sure you're at 0 then create the new region as near to 0 as you can. Then insert some notes with at least one note on the first beat- jack_midi_dump will show this note doesn't get played first time through.

danboid

2010-10-03 14:31

reporter   ~0009207

If you follow my instructions in the previous post under a recent svn, only the first note gets played but not subsequent ones on first playback but the first note has to start at 0.

danboid

2010-10-31 12:18

reporter   ~0009325

This bug should be resolved and 3481 reopened as the subject line matches the bug exactly.

Thanks!

cth103

2010-10-31 12:40

administrator   ~0009327

See notes.

system

2020-04-19 20:14

developer   ~0022059

Issue has been closed automatically, by Trigger Close Plugin.
Feel free to re-open with additional information if you think the issue is not resolved.

Issue History

Date Modified Username Field Change
2010-05-14 00:31 danboid New Issue
2010-05-25 09:30 danboid Note Added: 0008023
2010-06-08 22:19 cth103 cost => 0.00
2010-06-08 22:19 cth103 Target Version => 3.0-beta1
2010-06-08 23:22 cth103 Status new => confirmed
2010-07-01 23:23 danboid Note Added: 0008373
2010-07-25 19:27 paul Note Added: 0008637
2010-07-25 19:27 paul Status confirmed => feedback
2010-07-25 22:57 danboid Note Added: 0008640
2010-07-26 21:06 danboid Note Added: 0008657
2010-08-05 18:30 danboid Note Added: 0008727
2010-08-11 02:30 cth103 Note Added: 0008801
2010-08-11 09:57 danboid Note Added: 0008803
2010-08-12 00:12 cth103 Note Added: 0008809
2010-08-12 07:10 danboid File Added: loopprob.tar
2010-08-12 07:13 danboid Note Added: 0008814
2010-08-12 09:59 cth103 Note Added: 0008815
2010-08-13 02:14 cth103 Note Added: 0008817
2010-08-13 08:49 danboid Note Added: 0008820
2010-08-13 11:34 cth103 Note Added: 0008822
2010-08-13 11:51 danboid Note Added: 0008823
2010-08-13 17:01 cth103 Note Added: 0008826
2010-08-13 19:38 danboid Note Added: 0008827
2010-10-03 14:31 danboid Note Added: 0009207
2010-10-31 12:18 danboid Note Added: 0009325
2010-10-31 12:40 cth103 Relationship added related to 0003481
2010-10-31 12:40 cth103 Note Added: 0009327
2010-10-31 12:40 cth103 Status feedback => resolved
2010-10-31 12:40 cth103 Resolution open => fixed
2010-10-31 12:40 cth103 Assigned To => cth103
2020-04-19 20:14 system Note Added: 0022059
2020-04-19 20:14 system Status resolved => closed