View Issue Details

IDProjectCategoryView StatusLast Update
0007192ardourbugspublic2020-04-19 20:18
Reporterunfa Assigned Totimbyr  
PrioritynormalSeverityminorReproducibilityrandom
Status closedResolutionfixed 
PlatformPC / LinuxOSLinux MintOS Version18 KDE5 64-bit
Product Version5.5 
Fixed in Version5.6 
Summary0007192: Splitting MIDI regions creates a mess
DescriptionWhen splitting a MIDI region between the notes, the first note after the splitting point is often removed.

This seems to depend on the distance of the splitting point from the note.

Some notes seem to be unaffected, some need a smaller distance from the splitting point to disappear, some disappear with a larger distance.

Also frequently the two new regions created during splitting overlap or leave a gap between them.

When moving these overlapping or gapped regions their contents seem to jump to different locations within the regions sometimes.
Steps To Reproduce1. Record a region with a lot of short notes on a MIDI track
2. Split the region multiple times between the notes (using the S key)
Additional InformationI've captured a short video that demonstrates what I experience:

https://youtu.be/I_ZvZwu5r-U

The newest version of Ardour where I experienced this is:

Ardour 5.5.72
"The Plateaux of Mirror"
(rev 5.5-72-ge97404c)
Intel 64-bit

Downloaded from build.ardour.org
TagsNo tags attached.

Activities

nick_m

2017-01-06 17:07

reporter   ~0019270

i had a difficult time reproducing this until i noticed you were using magnetic snap.

thanks for the report.

nick_m

2017-01-06 17:08

reporter   ~0019271

only happens with magnetic snap

unfa

2017-01-08 18:26

reporter   ~0019274

Wow, I didn't notice that I had magnetic snapping on at all. Good I recorded a video.

nick_m

2017-02-04 12:27

reporter   ~0019331

this should be fixed in current master (rework_snap branch was just merged).

nick_m

2017-02-12 14:32

reporter   ~0019370

can you confirm that this is fixed in 5.6?

timbyr

2017-02-26 13:18

developer   ~0019442

I just retested this with 5.6.171 and still seems to be resolved, so marking as such. If reporter thinks otherwise they can reopen.

system

2020-04-19 20:18

developer   ~0023701

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
2017-01-01 18:25 unfa New Issue
2017-01-06 17:07 nick_m Note Added: 0019270
2017-01-06 17:08 nick_m Note Added: 0019271
2017-01-06 17:08 nick_m Status new => confirmed
2017-01-08 18:26 unfa Note Added: 0019274
2017-02-04 12:27 nick_m Note Added: 0019331
2017-02-12 14:32 nick_m Note Added: 0019370
2017-02-13 10:14 timbyr Status confirmed => feedback
2017-02-26 13:18 timbyr Note Added: 0019442
2017-02-26 13:18 timbyr Status feedback => resolved
2017-02-26 13:18 timbyr Fixed in Version => 5.6
2017-02-26 13:18 timbyr Resolution open => fixed
2017-02-26 13:18 timbyr Assigned To => timbyr
2020-04-19 20:18 system Note Added: 0023701
2020-04-19 20:18 system Status resolved => closed