Commit arrangement loses first midi note

[musekamp]

I haven't used the Arranger Track for a few months but I don't remember seeing this issue before.

I find I can easily reproduce it with these steps in a new project:
- insert midi track
- add a few notes, make sure the first on starts at 1:01:000
- create an arranger section for the first few measures
- add the section to an arrangement
- Commit Arrangement to Project
- the first note seems to disappear every time -- if it starts right on the first beat, if I shove it over a bit, it's fine

Can anyone please verify that this is not something in my configuration?
Thanks,
Walt

UPDATE: taking a closer look at this I see that when the arrangement gets committed, every midi event gets moved one tick earlier. So I guess events at 1:01:000 have nowhere to go,

 

Edited February 26, 2022 by musekamp
more info

[Byron Dickens]

If you give yourself one or two measures of count in, that won't happen.

[musekamp]

1 hour ago, bdickens said:

If you give yourself one or two measures of count in, that won't happen.

Thanks for the suggestion! I made a section of the count in and kept it as the first part of my arrangement and nothing got lost.

Yes, then I nudged everything one tick later. I know 1 tick isn't much but I feel better with all the events back where they were originally

[msmcleod]

@musekamp - I can't reproduce this issue using the steps provided.

Can you post two copies of the project where this is happening ( before & after the issue ) so we can look into it?

[musekamp]

Thanks for looking into this. Here's the before and after project files. Using the current version of Cakewalk.

(Sorry I PMed you the files before I realized I could just attach them here.)

Here's what the event list looks like before and after:

CommitArrangement-after.cwp CommitArrangement-before.cwp

Edited March 18, 2022 by musekamp
add version

[musekamp]

@msmcleod It looks like this might be pilot error after all.

After a tip from @Heinz Hupfer in the question thread I see that this seems to be related to my overlap threshold setting.

Not sure how I should have it set but I'll have to read up on the Arranger enhancements that I ignored the first time around!

 

Edited March 18, 2022 by musekamp

[msmcleod]

Ok, tracked down the issue - if "Select Events with Sections" is turned off in the select module,  commit arrangement doesn't work properly - this is the cause of everything being off by 1 tick.

I'll fix the commit arrangement command for the next release to ensure this is switched on for the duration of the commit command, but in the meantime, please ensure this is switched on before committing an arrangement:


 

[musekamp]

@msmcleod great that you tracked it down so quickly! And awesome to hear that you already have a fix lined up.

I remember turning that setting off a while ago when I was copying and pasting some section heading labels.

Thanks again!