Old 09-04-2016, 08:25 AM   #1
juliansader
Human being with feelings
 
Join Date: Jul 2009
Posts: 2,841
Default A Bestiary of MIDI Bugs for v5.25

Update v5.80 and v5.90: After a long, excruciating hiatus, MIDI bugs are being fixed again!

Our intrepid heroes, Schwa and Justin, have vanquished many a MIDI monster in v5.24. Will the upcoming v5.25 be the fabled, long-prophecied version in which all MIDI bugs are banished from Reaperland?

To aid our heroes on their quest, I have compiled this Bestiary of Bugs. I have not encountered or tested all of these bugs myself, so some of them may have fled since they were first reported, but most are definitely still roaming the lands.

For an older thread (that includes Feature Requests), please refer to MIDI - a summary of important pending things.


(Please do not report new bugs in this thread; rather, create a separate thread with a descriptive title.)


Bugs that affect ReaScript performance and user experience
Sluggishness: REAPER's audio engine is famously efficient and optimized. Sadly, the piano roll is the opposite, and it's getting worse and worse: v5.40 is THREE TIMES slower than v5.00! This negatively impacts ReaScript responsiveness:
Recent versions get terribly bogged down when multiple takes visible in MIDI editor
Standard toolbar arming cannot be used in CC lanes:
Actions armed by right-clicking toolbar button do not work in CC lane [Fixed!]


Multi-channel MIDI editing
Most of the channel-related bugs were fixed in v5.30. These somehow remain:
Bullets in channel dropdown list always show channel 1 being used [Fixed!]
Notes get deleted or extended when channel is changed to same channel as adjacent note [Fixed!]


Regions versus envelopes
Most of these bugs were fixed in v5.75!
Copying or moving regions messes up the tempo envelope [Fixed!]
Copying or moving regions messes up automation envelopes [Fixed!]
Moving regions drops multiple copies of existing tempo markers
If Allow trim of MIDI items is off, moving region across tempo change drops notes


Other tempo envelope and time signatures bugs
Important tip: As discussed here and here (and elsewhere), the tempo map can easily get screwed up if options such as the following are not carefully and correctly set:
* Timesig markers "Allow partial measures",
* Add edge points when ripple editing or inserting time,
* Timebase for tempo envelope,
* Timebase for MIDI items.
One of the most common complaints concerns timesig markers jumping around. This is usually the result of "Allow partial measures" = OFF, combined with Timebase for tempo = Time.

"Create new measure from time selection" alters tempo at *end* of time selection [Fixed!]
"Create measure from time selection" calculates wrong tempo if there is a tempo marker close to end of the time selection
"Insert empty space" deletes time signature at start of time selection [Fixed!]
Select/Copy/Delete "points in time selection" unreliable - depends on how time selection was drawn [No recent reports - perhaps fixed?]
Gradual tempo changes: gridline display/snapping and envelope pasting issues
Inserting new tempo point via right-click menu changes value/shape of previous point
Inserting square tempo point into linear envelope creates weird new timesig changes [Fixed!]
When copy/pasting points into tempo envelope, it always acts as if Timebase=Time
Time signatures with partial measures cannot be inserted when timebase=time


MIDI import and export
Certain time signatures cannot be exported to MIDI, but no warning is given
After importing XML, quantization makes notes disappear [Fixed!]
If project start time < 0, export only starts at time 0:0.000


Quantization and snapping
Quantize window applies wrong settings to non-active tracks [Fixed!]
Quantize moving items which are already on the beat [perhaps expired - no recent confirmations]
When just opened, Quantize window shows "Triplet", but "Straight" is applied
When using "CC selection follows note selection" to coordinate notes and CCs, CCs follow manual note movements but not note quantization [Fixed!]
Snapping to time position after linear tempo transition when the previous tempo marker does not fall on the grid
"Quantize notes position to grid" uses "Strength" setting from main Quantize window (for that we have the "Quantize ... last quantize dialog settings" actions)


MIDI note names
Note names not displaying in first track [Expired]
Midi note name files not merging when shift+click on recent list [Fixed!]
Actions and menu items to change CC names misleadingly refer only to "note names" [Fixed!]
CC names does not immediate update [Fixed!]


Stuck notes and missing note-offs
Record settings: Input quantize results in stuck MIDI notes
Stuck notes when playing MIDI through VSTi - perhaps due to reaperhost bridge? (and perhaps also reported here)
Note-off not sent when using replace/enclose and a note overlaps the start of the enclosing item
"Send all notes off to all MIDI outputs/plug-ins" action is unreliable
Stuck notes can be caused by doing certain unusual edits *during* playback


Mouse modifiers and editing actions
Win key is not available as modifier for mousewheel shortcuts [Fixed!]
Deselection: Mouse-click in CC lane still automatically deselects all events, even if "No action" is selected
Deselection: Left-click on MIDI note deselects all events, even if "No action" is selected
Velocity lane: "Erase event" mouse modifier does not work in velocity lane
Velocity lane: Cannot edit velocity of single note in a chord [Perhaps solved?]
Velocity lane: If drawing fast, some notes are skipped
Short notes: "Erase notes" with left-drag skips short or zoomed-out notes
Actions "Add previous/next note to selection" sometimes get stuck or slip notes Fixed!
14bit CCs: Unselected CCs disappear when range-selecting via shift-click [Fixed!]
14bit CCs: Ctrl-click in 14-bit CC lanes selects only the MSB CC, not the LSB CC [Fixed!]



(Continued in next post...)

Last edited by juliansader; 07-13-2019 at 03:56 AM.
juliansader is offline   Reply With Quote
Old 09-04-2016, 12:29 PM   #2
Mordi
Human being with feelings
 
Mordi's Avatar
 
Join Date: May 2014
Location: Norway
Posts: 570
Default

Wow, that's quite comprehensive. Great work!
Mordi is online now   Reply With Quote
Old 09-04-2016, 01:01 PM   #3
Sju
Human being with feelings
 
Join Date: Jun 2015
Posts: 686
Default

The toolbar context bug is still there apparently. (http://forum.cockos.com/showthread.php?t=137657)

Clicking on a docked MIDI toolbar button changes action context to Main.

Nice list btw! It seems to me like there are many small inconveniences/bugs in the MIDI editor, but I've learned to work around them. Gotta pay more attention and type them down and maybe report here.
Sju is offline   Reply With Quote
Old 09-04-2016, 08:16 PM   #4
lowellben
Human being with feelings
 
lowellben's Avatar
 
Join Date: Aug 2010
Location: They put me in a home.
Posts: 3,191
Default

Thank you for making this thread.
__________________
47.8% of statistics are made up.
lowellben is offline   Reply With Quote
Old 09-05-2016, 12:24 PM   #5
mccrabney
Human being with feelings
 
mccrabney's Avatar
 
Join Date: Aug 2015
Location: Obtoose, U.S.A.
Posts: 2,102
Default

yes, thanks for this summary. i've been watching your posts a lot (and scripts) and i think you're a very valuable person for those of us who use REAPER's MIDI editing functions. the following is not specifically addressed to you, but is regarding beta testing and REAPER forum etiquette in general:

don't take it personally that this thread got moved from Pre-release. my understanding is that the discussion there is strictly only for current pre cycle discussion. i've wrongfully posted there in the past and realize that it might seem like a good place to bring attention to the right people at the right time -- but the right people do read every single bug report posted. as such, the best possible thing you can do is exhaustively test bugs that affect you - multiple licecaps, multiple steps, multiple "and that's why this is bad" descriptions, etc. perhaps a "number of independent confirmations" could be referenced as well.
__________________
° using REAPER as host/arranger/sequencer to write instrumental beat music.
° striving for a loop-based, controller-centric midi recording/editing workflow.
° i am the fun kind of doomsday prepper, not the gun kind of doomsday prepper.
mccrabney is online now   Reply With Quote
Old 09-05-2016, 05:13 PM   #6
juliansader
Human being with feelings
 
Join Date: Jul 2009
Posts: 2,841
Default

Quote:
Originally Posted by mccrabney View Post
don't take it personally that this thread got moved from Pre-release. my understanding is that the discussion there is strictly only for current pre cycle discussion.
I posted in the Pre-release subforum since
1) the prototype thread, MIDI - a summary of important pending things, is in that subforum;
2) my compilation is not itself a bug report, but is intended as a discussion document for v2.25 pre-releases; and
3) I would like to update the thread during the 5.25 pre cycle.

Oh well, let's see how things go.
juliansader is offline   Reply With Quote
Old 09-11-2016, 01:07 AM   #7
snooks
Human being with feelings
 
Join Date: Sep 2015
Posts: 1,639
Default

Quote:
Originally Posted by juliansader View Post
Zooming bugs
MIDI editor auto-zoom bugs (constant unnecessary auto-zooming)
Fingers crossed for this in 5.25... the requests for controllable zoom go back years.
snooks is offline   Reply With Quote
Old 09-04-2016, 08:25 AM   #8
juliansader
Human being with feelings
 
Join Date: Jul 2009
Posts: 2,841
Default A Bestiary of MIDI Bugs for v5.25

Artefacts when gluing MIDI items
R4.78 creates CCs when Gluing...!
If using large PPQ, note position and length change by thousands of ticks when gluing


Event list needs some love
MIDI Event List not updating after changes in arrange view or other MIDI editors
MIDI editor event list mode: display update bug (selections)


Inline MIDI editor and arrange view
Drag Midi item from VSTi onto track: wrong piano roll notes mode in arrange view
Notes not displayed and not moving with item
MIDI Markers position not right in the arrange view if take has rate change
Weird barcode-like patterns are drawn over MIDI items
Inline Editor: Mousewheel shortcuts don't work, pass through the main window
Inline Editor: Zoom changes when duplicating or undoing


Notation editor
Tempo change and bar numbers overlay each other
Problems creating tuplets over tied notes
Display in Musical notation, blinking channel dropdown
Accidentals of chord overlay each other in unreadable mess [Improved]


Note preview and chasing
MIDI preview on new note, not working
Note preview doesn't "chase" notation text
Previewing notes in MIDI editor doesn't do MIDI chase (envelope automation gets chased, but not CCs)
MIDI item CC-chase doesn't respect "Reset all controllers" #121

Item length in MIDI editor
Editing item length in MIDI editor is buggy when the item length is shorter than 1/4 note and item properties are set to "loop item source"
A MIDI clip with a Rate > 1 does not loop correctly
Extending MIDI item over tempo marker causes misplaced notes


Explode by note row
"Explode MIDI item by note row (pitch)" leads to empty channels for E♭-1 and E-1 [FIXED!]
"Explode MIDI item by note row (pitch)" leads to note lengths being increased


Overlapping notes and infinitely extended notes
REAPER uses the standard specifications for MIDI files to store the data of MIDI items. According to the specifications, overlapping notes (with the same pitch and channel) are not valid. Many of REAPER's native actions, as well as scripts, will go haywire *without warning the user* when applied to overlapping notes.
Humanize removes overlapping notes, but incorrectly
Humanize function is affecting non-selected notes in a MIDI item


Copy/pasting and duplicating notes
The setting Autocorrect overlapping notes while editing is supposed to make editing safer, but is unfortunately buggy:
Pasting or duplicating note deletes non-overlapping adjacent note [Fixed!]
Pasted note disappears if it overlaps existing note


MIDI recording
MIDI ASIO Latency Compensation Problems
MIDI input quantize bugs (overlapping notes during recording)
MIDI overdub is cut off if it extends past first item into a second item


Display bugs in piano roll
Midi editor grid glitch and Erratic grid lines in MIDI Editor
MIDI editor displays bank select incorrectly when item looped
CCs disappear when events earlier in MIDI string go offscreen
No indication of source end when looping is disabled


Lyrics
On 32nd and 64th notes, the lyrics 'stepper' skips notes or get stuck
Lyrics 'stepper' skips note if it start slightly behind beat
After editing lyrics several times, sometimes they can't be deleted


Reascript bugs
Large state chunks are truncated by GetTrack/ItemStateChunk [Fixed!]
Using MIDI_InsertEvt to insert a Note On automatically insert a (wrong) Note Off (resulting in zero-length notes)
MIDIEditor_GetTake returns take object even if no take is active
MIDI_GetNote returns endppqpos different from visual appearance in editor
MIDI_DeleteNote ADDS note to another pitch
MIDI overlapping note issue


Zooming bugs
Double-clicking MIDI item doesn't open item fully expanded in MIDI Editor
MIDI Editor "Zoom to Content" ignores single row of high or low notes
MIDI editor auto-zoom bugs (constant unnecessary auto-zooming) [Fixed!]
Opening/closing docked MIDI Editor can cause irretrievable loss of arrange view vertical zoom


MIDI editor window management
Docked MIDI Editor not positioned correctly until resized
Toolbar buttons for child windows such as Event Properties and Humanize behave inconsistently
MIDI editor loses focus after closing script GUI or contextual toolbar
Shortcut key in docked MIDI editor doesn't work after clicking MIDI toolbar
Docked toolbar steals focus
MIDI editor resizes itself after creating new MIDI item

Child windows disappear offscreen: MIDI Problem Transpose and Selecting "View -> Transpose..." doesn't open the transpose dialog box
The disappearing window problem seems to involve two separate bugs:
* REAPER does not check the screen resolution before opening windows offscreen, and
* the "Cascade all floating windows" action does not work for some windows.
(This bug also affects non-MIDI windows such as the script/JSFX IDE, script GUIs, and the ReaScript console.)


Diverse
MIDI link parameter modulation: Parameter locked to last received MIDI CC value

MIDI feedback routing bug? (MIDI routing + audio feedback depends on track order)

MIDI editor: Actions that refer to "all" events are named incorrectly/inconsistently [Temporary workaround in thread]

MIDI Editor Key snap status incorrect after switching items

Undoing with Ctrl-Z causes notes to shorten, and cannot be undone [No RPP or MIDI for replication]

When very small sized, docked Virtual MIDI Keyboard octave transpose is buggy

Instrument definition file (.ins) parser bugs [FIXED!]

MIDI Editor Key snap status incorrect after switching items [FIXED!]

Strange doubling of MIDI events at top of FX chain when certain VSTs are added after

Last edited by juliansader; 07-13-2019 at 03:58 AM.
juliansader is offline   Reply With Quote
Old 09-21-2016, 12:19 PM   #9
noise_construct
Human being with feelings
 
Join Date: Nov 2015
Posts: 1,566
Default

Quote:
Originally Posted by juliansader View Post
Display bugs in piano roll
MIDI editor: Cannot grab note start to change length (various issues when notes start before item)[/url]
This was connected with the older behaviour with drawing note borders at item border (printing note start where it really wasn't), which has been fixed... sort of, the velocity handle start is still drawn at item border, but it's still much better now.

I don't think we should be able to grab note start from the item border, if the note starts earlier tbh.
noise_construct is offline   Reply With Quote
Old 09-22-2016, 01:37 AM   #10
ELP
Human being with feelings
 
Join Date: Apr 2014
Posts: 943
Default

BTW Stuck Notes and Stopping within the Range of the Note length

These can refers to overlapping Notes/Stopping within the range of overlapping Notes and some bad Plugin & also Hardware behaviors.

Some rare plugins and Hardware need for every overlapping "open"Note ON also one
Note Off event to "close" the Note ONs, which is not really the MIDI Standard.
One bad behavior VSTi is for example this newer Roland Sound Canvas VSTi.
So if you have three overlapping Notes, example "C4", and you stop the playback before the
"Normal" C4 Note Off events occur,
REAPER send one Note Off after pushing Stop for C4 instead of one for every open Note On in a row(as it would be if you not stop the playback in between Note ON to Note OFF.)
The result is that two #C4 Note OFF events for the same C4 Note are missing
and this VSTI example above get stuck.. -----meaning after Stop the playback in between overlapping Note ON/OFF..

I really thing many Stucks can only related to this VSTi/Hardware overlapping events behavior.
__________________
I hope you can understand me? Without german beer my written english is always very bad, with beer it becomes unbearable!.
Less is more! To much limited the own creativity.

Last edited by ELP; 09-22-2016 at 01:43 AM.
ELP is offline   Reply With Quote
Old 09-22-2016, 02:14 AM   #11
EvilDragon
Human being with feelings
 
EvilDragon's Avatar
 
Join Date: Jun 2009
Location: Croatia
Posts: 23,637
Default

So are we going to have a thread now for each point update? I don't think that's efficient.

You can rename the thread, you know? Edit the first post, it's right there.
EvilDragon is offline   Reply With Quote
Old 09-22-2016, 03:16 AM   #12
juliansader
Human being with feelings
 
Join Date: Jul 2009
Posts: 2,841
Default

Quote:
Originally Posted by EvilDragon View Post
So are we going to have a thread now for each point update? I don't think that's efficient.
Not necessarily. In this case, I just felt that the first thread's bug list was getting too long and overcrowded. Better to focus on current bugs than long-solved ones.

EDIT: I merged the threads.

Last edited by juliansader; 05-31-2018 at 02:46 AM.
juliansader is offline   Reply With Quote
Old 09-22-2016, 03:22 AM   #13
juliansader
Human being with feelings
 
Join Date: Jul 2009
Posts: 2,841
Default

Quote:
Originally Posted by ELP View Post
BTW Stuck Notes and Stopping within the Range of the Note length

These can refers to overlapping Notes/Stopping within the range of overlapping Notes and some bad Plugin & also Hardware behaviors.
If any of these bug reports regarding stuck notes have been fixed or solved, please let me know (in the relevant thread), so that I can mark the threads as fixed/solved/no bug.
juliansader is offline   Reply With Quote
Old 09-27-2016, 01:11 AM   #14
noise_construct
Human being with feelings
 
Join Date: Nov 2015
Posts: 1,566
Default

Quote:
MIDI editor window management
Various inconsistent behaviors of child windows: Event properties window does not deactivate toolbar button.
MIDI editor losing focus: MIDI Editor - no focus (the FR Keep MIDI editor focused after opening and closing popup windows touches on the same issue)
Can't replicate "MIDI Editor - no focus", but the focus remaining in dropdown menus (and not in MIDI editor) after using them still remains.

See #3 here http://forums.cockos.com/showthread....61#post1735461
noise_construct is offline   Reply With Quote
Old 09-27-2016, 01:21 AM   #15
juliansader
Human being with feelings
 
Join Date: Jul 2009
Posts: 2,841
Default

Quote:
Originally Posted by noise_construct View Post
Can't replicate "MIDI Editor - no focus", but the focus remaining in dropdown menus (and not in MIDI editor) after using them still remains.

See #3 here http://forums.cockos.com/showthread....61#post1735461
I will update the links in the first post.
juliansader is offline   Reply With Quote
Old 10-04-2016, 10:53 AM   #16
slum_x
Human being with feelings
 
Join Date: Jul 2014
Posts: 13
Default

Quote:
Originally Posted by ELP View Post
BTW Stuck Notes and Stopping within the Range of the Note length

These can refers to overlapping Notes/Stopping within the range of overlapping Notes and some bad Plugin & also Hardware behaviors.

Some rare plugins and Hardware need for every overlapping "open"Note ON also one
Note Off event to "close" the Note ONs, which is not really the MIDI Standard.
One bad behavior VSTi is for example this newer Roland Sound Canvas VSTi.
So if you have three overlapping Notes, example "C4", and you stop the playback before the
"Normal" C4 Note Off events occur,
REAPER send one Note Off after pushing Stop for C4 instead of one for every open Note On in a row(as it would be if you not stop the playback in between Note ON to Note OFF.)
The result is that two #C4 Note OFF events for the same C4 Note are missing
and this VSTI example above get stuck.. -----meaning after Stop the playback in between overlapping Note ON/OFF..

I really thing many Stucks can only related to this VSTi/Hardware overlapping events behavior.
I have the problem with stuck notes on my Nord Lead 4, Nord Wave, NI Kontakt (vst) so it sounds weird if this is solely af hardware/vst plugin problem.
slum_x is offline   Reply With Quote
Old 10-04-2016, 04:23 PM   #17
viper-2
Human being with feelings
 
viper-2's Avatar
 
Join Date: Jun 2013
Location: Charleston, SC
Posts: 115
Default

I am having an issue with the newest update not loading my controllers. My NanoKontrol2 and Presonus faderport have disappeared.
viper-2 is offline   Reply With Quote
Old 10-04-2016, 04:48 PM   #18
MikComposer
Human being with feelings
 
MikComposer's Avatar
 
Join Date: May 2012
Location: Brighton
Posts: 1,988
Default

Not sure if I see this in the list, but when you have two midi items, one short, and other long, with short on top somewhere in the middle, when you glue both, it will extend notes until they hit anther note or end of item.
__________________
My Royalty Free Music library
MikComposer is offline   Reply With Quote
Old 02-15-2017, 04:43 PM   #19
Lokasenna
Human being with feelings
 
Lokasenna's Avatar
 
Join Date: Sep 2008
Location: Calgary, AB, Canada
Posts: 6,466
Default

@juliansader - As per our discussion about it a week or two ago, I would suggest that In "Position and note length" mode, Quantize can not shorten notes is not actually Solved - the old behavior went away without any mention in the changelog, and it had already been available via "Note Ends" if memory serves.
Lokasenna is offline   Reply With Quote
Old 02-17-2017, 10:46 PM   #20
blumpy
Human being with feelings
 
blumpy's Avatar
 
Join Date: Sep 2016
Posts: 289
Default Video playback stunted after opening Subproject.

Video playback has been jerky the last few updates but it seems as if its only after opening a subproject. After that I have to restart reaper to fix.
blumpy is offline   Reply With Quote
Old 02-18-2017, 01:57 AM   #21
EvilDragon
Human being with feelings
 
EvilDragon's Avatar
 
Join Date: Jun 2009
Location: Croatia
Posts: 23,637
Default

And what has that to do with MIDI?
EvilDragon is offline   Reply With Quote
Old 02-20-2017, 11:14 AM   #22
Amack
Human being with feelings
 
Join Date: Feb 2017
Posts: 12
Default Adequate Bug Report

Quote:
Originally Posted by Amack View Post
I believe that Reaper does not properly compensate MIDI for ASIO audio interface latency. The delay applied to live MIDI inputs that trigger Internal Virtual Instruments (Vis) is apparently determined by the ASIO buffer size rather than by the interface’s reported input latency. Also, live MIDI outputs are delayed by the sum of the interface’s reported input and output latencies rather than just its reported output latency.

DAW audio inputs and outputs are delayed by the audio interface’s input and output latencies. Since MIDI inputs aren’t, Reaper apparently adds delay to MIDI inputs and outputs in an attempt keep things synchronized during monitoring, recording, and playback. As shown in the attachment, Reaper delays MIDI input track recordings and any associated MIDI outputs by the reported input latency of the audio interface, but (incorrectly) only delays the triggering of internal virtual instruments (Vis) by the interface’s buffer size equivalency. This causes internal VIs to be prematurely triggered by the difference between the interface’s input latency and its buffer size equivalency during monitoring and recording. Also, rather than properly delaying MIDI outputs by the reported output latency of the interface, Reaper delays them by the sum of the reported input and output latencies. External VIs triggered by these MIDI outputs would experience an extra delay equal to the reported input latency during monitoring, recording, and playback.

Test Procedure
For this demonstration, a Roland TD-15K V-drum served as a MIDI (via USB) and audio (via audio output) source. ASIO4ALL was used with the computer’s internal sound “card” as the audio interface. A 1st generation Focusrite Scarlett 6i6 was used as a MIDI loopback device.

A microphone was used to trigger one of the TD-15 drum pads. Although it was recorded on Track 8, the TD-15’s audio was used as the time reference instead because it was quite well synchronized with the TD-15’s MIDI.
TD-15 MIDI was recorded on Track 1. TD-15 Audio was recorded on Track 2 and monitored and externally looped back for recording on Track 3.
TD-15 MIDI also triggered a MT-PowerDrumKit VSTi on Track 4. The VSTi’s output was monitored and externally looped back for recording on Track 5.
TD-15 MIDI was also output to the 6i6 on Track 6 for monitoring, external loopback, and recording on Track 7.

Both recordings were configured to “Use audio driver reported latency”. The first was with ASIO4ALL reporting latencies reflective of the actual input and output latencies. The second was with ASIO4ALL reporting incorrect latencies to demonstrate the problems.

Test Results
Track 1’s second recording shows that the MIDI input recording was delayed 20 milliseconds (ms) * 48k Samples/second (S/s) = 960S from that on the first recording – consistent with the reported input latency (ASIO4ALL’s “Latency Compensation In:”) increase.

The approximately 64 S (1.333 ms) delay between Track 3 and 5 in the first recording suggest that the triggering of the VSTi that produced Track 5 was delayed by the ASIO Buffer Size equivalency (2048 S / 48k S/s = 42.667 ms) rather than the total reported input latency (2048 S + 64 S) / 48k S/s + 1 ms = 45 ms. (This version of ASIO4ALL has and reports an additional 1 ms of input and output “Buffer Offset” latency over what is shown on its control panel slider.) The fact that Track 5 in the second recording experienced no additional delay verifies that.

Tracks 6 on the first recording shows that the MIDI input to output delay was the sum of the input buffer size equivalency and the reported output latency (42.667 + 45 = 87.667 ms). The second recording shows an additional delay of ~ 30 ms delay. The corresponding increase in reported latencies between the two recordings was (1024 + 512 – 2*64) S / 48k S/s = 29.33 ms (within the measurement accuracy).
Did I submit this "bug" report adequately and correctly?
__________________
An Engineer with OCD
Amack is offline   Reply With Quote
Old 02-20-2017, 11:25 AM   #23
juliansader
Human being with feelings
 
Join Date: Jul 2009
Posts: 2,841
Default

Quote:
Originally Posted by Amack View Post
Did I submit this "bug" report adequately and correctly?
Thank you for the detailed report! I have moved the report and its replies to a separate thread MIDI ASIO Latency Compensation Problems (REAPER v5.33/x64 Windows10), and I added it to the Bestiary.
juliansader is offline   Reply With Quote
Old 02-20-2017, 01:52 PM   #24
Amack
Human being with feelings
 
Join Date: Feb 2017
Posts: 12
Default

Quote:
Originally Posted by juliansader View Post
Thank you for the detailed report! I have moved the report and its replies to a separate thread MIDI ASIO Latency Compensation Problems (REAPER v5.33/x64 Windows10), and I added it to the Bestiary.
Thank you sir! Please let me know if I can be of any further assistance.
__________________
An Engineer with OCD
Amack is offline   Reply With Quote
Old 02-21-2017, 04:43 PM   #25
X-Raym
Human being with feelings
 
X-Raym's Avatar
 
Join Date: Apr 2013
Location: France
Posts: 6,115
Default

@juliansader
Hi !
How can we sent you Private Message ?
X-Raym is offline   Reply With Quote
Old 04-25-2017, 01:50 PM   #26
Amack
Human being with feelings
 
Join Date: Feb 2017
Posts: 12
Default

Quote:
Originally Posted by juliansader View Post
Thank you for the detailed report! I have moved the report and its replies to a separate thread MIDI ASIO Latency Compensation Problems (REAPER v5.33/x64 Windows10), and I added it to the Bestiary.
I just posted some more information on that thread.
__________________
An Engineer with OCD
Amack is offline   Reply With Quote
Old 05-28-2017, 07:46 AM   #27
ChrisBlue
Human being with feelings
 
Join Date: May 2017
Posts: 215
Default Missing in Musical Notation

I am finding that sometimes when I punch-in with a pedal through the Nektar P1 when recording the Pianoteq5, there are apparent repeats of a note or chord in rapid succession like a quick echo (i.e. repeated almost instantaneously though only once ). I tried to edit this out by going into musical notation mode in the MIDI editor but there is no sign of the repeated note/chord so seemingly no way to remove it. Can anyone explain what's happening and suggest a solution please? Using 64 bit version of Pianoteq5 VSTi
ChrisBlue is offline   Reply With Quote
Old 09-10-2017, 07:46 AM   #28
midiman007
Human being with feelings
 
Join Date: Mar 2015
Location: New York
Posts: 200
Default Aftertouch Name

Ok I think I found an inconstancy in naming of midi events.
In the midi event view channel after touch is shown as channel after touch in the piano view it's named channel pressure.

Last edited by midiman007; 11-29-2018 at 11:39 AM.
midiman007 is offline   Reply With Quote
Old 09-17-2017, 05:28 PM   #29
midiman007
Human being with feelings
 
Join Date: Mar 2015
Location: New York
Posts: 200
Default

Quote:
Originally Posted by midiman007 View Post
Ok I think I found an inconstancy in naming of midi events.
In the midi event view channel after touch is shown as channel after touch in the piano view it's named channel pressure.
Thanks for the fix on pre 60.I thought this went unheard.

MIDI editor: label channel pressure messages consistently (not "channel aftertouch") p=1884306]

Please correct me if I am wrong but shouldn't it be called Channel Aftertouch?

I do not see Channel pressure on the midi cc list any where on the internet.

I think it should follow the industry standard midi names schema,

Also I think this might help from the thread I read that Justinlander was trying to move Reaper in the way of orchestration. Since that would be extensive wind instruments.

Last edited by midiman007; 09-17-2017 at 06:26 PM.
midiman007 is offline   Reply With Quote
Old 09-18-2017, 01:00 AM   #30
EvilDragon
Human being with feelings
 
EvilDragon's Avatar
 
Join Date: Jun 2009
Location: Croatia
Posts: 23,637
Default

Quote:
Originally Posted by midiman007 View Post
I do not see Channel pressure on the midi cc list any where on the internet.
You're not looking in the right places

https://www.midi.org/specifications/...f-midi-message

Polyphonic Key Pressure (Aftertouch)
Channel Pressure (Aftertouch)


So, the industry standard says it's fine to use both
EvilDragon is offline   Reply With Quote
Old 09-18-2017, 04:57 AM   #31
midiman007
Human being with feelings
 
Join Date: Mar 2015
Location: New York
Posts: 200
Default

Quote:
Originally Posted by EvilDragon View Post
You're not looking in the right places

https://www.midi.org/specifications/...f-midi-message

Polyphonic Key Pressure (Aftertouch)
Channel Pressure (Aftertouch)


So, the industry standard says it's fine to use both
OK thanks for the info.

Do you think we can add the parentheses?

Channel Pressure (After-touch)

I just checked Cakewalk and Cubase they are both listing it as aftertouch.
and before you make a wise crack emoji ( and stick your tongue out )
I know this is reaper but if other DAWs are saying aftertouch it might make sense to a user who migrates from Cakewalk or Cubase to reaper to stay in the naming schema.

( The object of software ( Reaper ) is not to confuse a user, it to make migration easier. )

Last edited by midiman007; 09-18-2017 at 06:01 PM. Reason: Adding a few things
midiman007 is offline   Reply With Quote
Old 12-14-2017, 07:24 AM   #32
juliansader
Human being with feelings
 
Join Date: Jul 2009
Posts: 2,841
Default

Yay! Lots of fixes for Regions vs Tempo bugs in v5.70!

A few bugs still remain, but hopefully these can quickly be mopped up.

Last edited by juliansader; 12-14-2017 at 09:16 AM.
juliansader is offline   Reply With Quote
Old 10-14-2017, 11:29 AM   #33
Paulo
Human being with feelings
 
Join Date: Apr 2017
Posts: 4
Default channel bug

I experience a new bug since version 5.50. When listening stereo playback in version 5.40 I could hear both channels. Since 5.50 I only get left channel (Windows 7 64 bits). Anyone get this bug too ?
Paulo is offline   Reply With Quote
Old 10-14-2017, 11:51 AM   #34
dimitris
Human being with feelings
 
Join Date: Nov 2008
Posts: 91
Default

Quote:
Originally Posted by Paulo View Post
I experience a new bug since version 5.50. When listening stereo playback in version 5.40 I could hear both channels. Since 5.50 I only get left channel (Windows 7 64 bits). Anyone get this bug too ?
Are you referring to your master output? Hmmm... Maybe check your Audio Device Output Range in Preferences. If by some reason this is set to From Output 1 to Output 1 of your audio device, you'd get signal only from the left channel.
dimitris is offline   Reply With Quote
Old 10-14-2017, 03:21 PM   #35
midiman007
Human being with feelings
 
Join Date: Mar 2015
Location: New York
Posts: 200
Default

Quote:
Originally Posted by Paulo View Post
I experience a new bug since version 5.50. When listening stereo playback in version 5.40 I could hear both channels. Since 5.50 I only get left channel (Windows 7 64 bits). Anyone get this bug too ?
I do not know what audio device you have I have a pro 40 and my outputs need to be selected. Outputs 1 and 2 check that. I have not had an issue with only hearing the left channel.
midiman007 is offline   Reply With Quote
Old 10-15-2017, 02:04 PM   #36
Paulo
Human being with feelings
 
Join Date: Apr 2017
Posts: 4
Default channel bug

Hi Dimitris and midiman007, you were right on the spot, I forgot to check the audio device output settings and they were set to "last = output 1". That was it. Thanks a lot !
Paulo is offline   Reply With Quote
Old 10-15-2017, 03:00 PM   #37
dimitris
Human being with feelings
 
Join Date: Nov 2008
Posts: 91
Default

You're welcome.
dimitris is offline   Reply With Quote
Old 10-15-2017, 03:57 PM   #38
midiman007
Human being with feelings
 
Join Date: Mar 2015
Location: New York
Posts: 200
Default

Quote:
Originally Posted by Paulo View Post
Hi Dimitris and midiman007, you were right on the spot, I forgot to check the audio device output settings and they were set to "last = output 1". That was it. Thanks a lot !
You are most welcome glad I could help.:-)
midiman007 is offline   Reply With Quote
Old 10-19-2017, 05:39 AM   #39
midiman007
Human being with feelings
 
Join Date: Mar 2015
Location: New York
Posts: 200
Default

Quote:
Originally Posted by juliansader View Post
If you are an adventurous bard, eager to gain experience points and level up, MIDI editing can be an exciting quest: Fight monstrous bugs! Find clever workarounds to mysterious and inexplicable phenomena!

Otherwise, Abandon all hope, ye who enter here. The piano roll has practically been abandoned by the devs, and bug fixes are few and far between.


Following on from A Bestiary of MIDI Bugs for v5.25.

(Please do not report new bugs in this thread; rather, create a separate thread with a descriptive title.)


Bugs that affect ReaScript performance and user experience
Sluggishness: REAPER's audio engine is famously efficient and optimized. Sadly, the piano roll is the opposite, and it's getting worse and worse: v5.40 is THREE TIMES slower than v5.00! This negatively impacts ReaScript responsiveness:
Recent versions get terribly bogged down when multiple takes visible in MIDI editor
Standard toolbar arming cannot be used in CC lanes:
Actions armed by right-clicking toolbar button do not work in CC lane


Multi-channel MIDI editing
Most of the channel-related bugs were fixed in v5.30. This one somehow remains:
Bullets in channel dropdown list always show channel 1 being used


Regions and the tempo envelope
Region moving/copying is completely unreliable if there are any tempo changes nearby. A major culprit is improper handling of edge points: When a region begins or ends with linear tempo segments, or is moved/copied into a linear segment, two points should be inserted at each edge point to preserve tempo envelope inside and outside region. REAPER fails to do so.
When moving/copying region, part to right of new region loses time signature (duplicate report)
Moving regions drops multiple copies of existing tempo markers
When duplicating regions, grid ends up out of sync
Moving region across tempo change drops notes
Copying/moving regions causes tempo changes and time sigs to lose beat positions, even if timebase=beats, whether using linear or square tempo changes.
Sometimes, REAPER does not realize that an edge point is actually inside the Region: Tempo marker on first beat of region does not move with region


Other tempo envelope and time signatures bugs
Important tip: As discussed here and here (and elsewhere), the tempo map can easily get screwed up if options such as the following are not carefully and correctly set:
* Timesig markers "Allow partial measures",
* Add edge points when ripple editing or inserting time,
* Timebase for tempo envelope,
* Timebase for MIDI items.
One of the most common complaints concerns timesig markers jumping around. This is usually the result of "Allow partial measures" = OFF, combined with Timebase for tempo = Time.

"Create new measure from time selection" alters tempo at *end* of time selection
"Insert empty space" deletes time signature at start of time selection
Select/Copy/Delete "points in time selection" unreliable - depends on how time selection was drawn
Gradual tempo changes: gridline display/snapping and envelope pasting issues
Inserting new tempo point changes value/shape of envelope
Inserting square tempo point into linear envelope creates weird new timesig changes
MIDI either exporting or importing tempo maps incorrectly
Ripple edit of tempo map persists after switching off ripple edit


Quantization and snapping
Quantize window applies wrong settings to non-active tracks
Quantize moving items which are already on the beat [perhaps expired - no recent confirmations]
When just opened, Quantize window shows "Triplet", but "Straight" is applied
When using "CC selection follows note selection" to coordinate notes and CCs, CCs follow manual note movements but not note quantization
Snapping to time position after linear tempo transition when the previous tempo marker does not fall on the grid
"Quantize notes position to grid" uses "Strength" setting from main Quantize window (for that we have the "Quantize ... last quantize dialog settings" actions)


MIDI note names
Note names not displaying in first track
Midi note name files not merging
Actions and menu items to change CC names misleadingly refer only to "note names"


Stuck notes and missing note-offs
Record settings: Input quantize results in stuck MIDI notes
Stuck notes when playing MIDI through VSTi - perhaps due to reaperhost bridge? (and perhaps also reported here)
Note-off not sent when using replace/enclose and a note overlaps the start of the enclosing item
"Send all notes off to all MIDI outputs/plug-ins" action is unreliable
Stuck notes can be caused by doing certain unusual edits *during* playback


Mouse modifiers and editing actions
Win key is not available as modifier for mousewheel shortcuts
Deselection: Mouse-click in CC lane still automatically deselects all events, even if "No action" is selected
Deselection: Left-click on MIDI note deselects all events, even if "No action" is selected
Velocity lane: "Erase event" mouse modifier does not work in velocity lane
Velocity lane: Cannot edit velocity of single note in a chord [Perhaps solved?]
Short notes: "Erase notes" with left-drag skips short or zoomed-out notes
When changing note length, mouse position and note edge sometimes don't match
Actions "Add previous/next note to selection" sometimes get stuck or slip notes


Artefacts when gluing MIDI items
R4.78 creates CCs when Gluing...!
If using large PPQ, note position and length change by thousands of ticks when gluing


MIDI editor window management
Docked MIDI Editor not positioned correctly until resized
Toolbar buttons for child windows such as Event Properties and Humanize behave inconsistently
MIDI editor loses focus after closing script GUI or contextual toolbar
Shortcut key in docked MIDI editor doesn't work after clicking MIDI toolbar
Docked toolbar steals focus
MIDI editor resizes itself after creating new MIDI item

Child windows disappear offscreen: MIDI Problem Transpose and Selecting "View -> Transpose..." doesn't open the transpose dialog box
The disappearing window problem seems to involve two separate bugs:
* REAPER does not check the screen resolution before opening windows offscreen, and
* the "Cascade all floating windows" action does not work for some windows.
(This bug also affects non-MIDI windows such as the script/JSFX IDE, script GUIs, and the ReaScript console.)


(Continued in next post...)
The piano roll has practically been abandoned by the devs, and bug fixes are few and far between.

Is this for real?
midiman007 is offline   Reply With Quote
Old 10-20-2017, 04:48 PM   #40
Tod
Human being with feelings
 
Tod's Avatar
 
Join Date: Jan 2010
Location: Just outside of Glacier National Park
Posts: 12,686
Default

Quote:
Originally Posted by midiman007 View Post
The piano roll has practically been abandoned by the devs, and bug fixes are few and far between.

Is this for real?
I don't know about that, but I have a number of issues with the ME. One is that the window does not scroll properly at all.

Usually when I start a new project it scrolls just fine, but for some reason, it don't take too long and it doesn't scroll any more.

I'm aware of the problem with the ME track list up, but even without it, it will not scroll. The biggest problem is that this is kind of a random thing.

Am I missing a preference somewhere?
__________________
Kontakt Vid Tutorials->Create Outputs / Create Templates -|- SMDrums Free drums -|- Elk Video Productions -|- Tod's Music
Tod is offline   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 05:10 AM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2019, vBulletin Solutions Inc.