Bug? Copy of an external Midi file won't edit correctly

worldwideweary · 11-12-2019, 11:36 AM

Steps to reproduce:

Import an external .MIDI file onto track
Ctrl+Drag that media item to another track so that there are two instances
Open up second instance in MIDI Editor
Attempt to draw some notes

Result: The lengths of the new notes are defaulting into a minuscule length and not taking drag-lengths from the mouse.

It also doesn't matter which copy of the imported midi file is edited: after multiple instances are in place, this seems to happen upon any instance.

Has anyone else experienced this, or can this be done fine by anyone without such behavior? Maybe there's a setting that needs to be changed for this to work properly? Otherwise this appears to be an error in the way Reaper is handling multiple instances of the same external midi file and should be reported after verification.

Here's a quick proof of what happens with click-dragging in the MIDI-Editor:

schwa · 11-12-2019, 01:21 PM

Thanks for the report, fixing for the next build.

That bug dates from 2011!

worldwideweary · 11-12-2019, 05:04 PM

Quote:

Originally Posted by schwa

Thanks for the report, fixing for the next build.

That bug dates from 2011!

Nice.
Slightly interested as to how it's known that a bug is from a certain era? Either way, good luck with the fix.

schwa · 11-12-2019, 07:48 PM

In general, we try to figure out where a bug came from by either looking at the code repository log (blame), or by testing old versions until we find the last version that worked correctly (bisect). This bug is pretty special in that it's very old, clearly describable, and so obviously wrong that it's amazing it hasn't been reported before. (It's not the default behavior to import .mid files as file references, so I guess it's less common than I would have thought.)

worldwideweary · 11-12-2019, 08:37 PM

Quote:

Originally Posted by schwa

In general, we try to figure out where a bug came from by either looking at the code repository log (blame), or by testing old versions until we find the last version that worked correctly (bisect). This bug is pretty special in that it's very old, clearly describable, and so obviously wrong that it's amazing it hasn't been reported before. (It's not the default behavior to import .mid files as file references, so I guess it's less common than I would have thought.)

Okay, thanks for the information.

And although working with external .midi files might be rare, it's most definitely worth keeping and upgrading if need be. Many softwares don't seem to have this functionality for some reason.

11-12-2019, 11:36 AM	#1
worldwideweary Human being with feelings Join Date: Mar 2015 Posts: 51	Bug? Copy of an external Midi file won't edit correctly Steps to reproduce: Import an external .MIDI file onto track Ctrl+Drag that media item to another track so that there are two instances Open up second instance in MIDI Editor Attempt to draw some notes Result: The lengths of the new notes are defaulting into a minuscule length and not taking drag-lengths from the mouse. It also doesn't matter which copy of the imported midi file is edited: after multiple instances are in place, this seems to happen upon any instance. Has anyone else experienced this, or can this be done fine by anyone without such behavior? Maybe there's a setting that needs to be changed for this to work properly? Otherwise this appears to be an error in the way Reaper is handling multiple instances of the same external midi file and should be reported after verification. Here's a quick proof of what happens with click-dragging in the MIDI-Editor: Last edited by worldwideweary; 11-12-2019 at 11:53 AM.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

11-12-2019, 01:21 PM	#2
schwa Administrator Join Date: Mar 2007 Location: NY Posts: 16,494	Thanks for the report, fixing for the next build. That bug dates from 2011!

11-12-2019, 07:48 PM	#4
schwa Administrator Join Date: Mar 2007 Location: NY Posts: 16,494	In general, we try to figure out where a bug came from by either looking at the code repository log (blame), or by testing old versions until we find the last version that worked correctly (bisect). This bug is pretty special in that it's very old, clearly describable, and so obviously wrong that it's amazing it hasn't been reported before. (It's not the default behavior to import .mid files as file references, so I guess it's less common than I would have thought.)