|
|
|
12-20-2016, 04:55 PM
|
#1
|
Human being with feelings
Join Date: Jun 2009
Location: South, UK
Posts: 14,214
|
v5.31pre1-December 20 2016
December 20 2016
+ FX: ignore monitoring FX windows when cascading other FX windows
+ Lyrics: fix initial size of lyrics.lua window [p=1772058]
+ MIDI editor: add some notation actions to piano roll note context menu
+ MIDI editor: display notation data in a lane in the piano roll
+ MIDI editor: edit text/sysex events on right-click, rather than delete
+ MIDI editor: fix display of captured CC event value
+ MIDI editor: fix various cases when note edits extend the media item
+ MIDI editor: ignore double note-on or note-off messages when opening editor
+ MIDI editor: respect event filter and mark selected events in raw MIDI viewer window
+ MIDI editor: update snap-to-key checkbox when switching MIDI items [t=183393]
+ Notation editor: add "remove" button to tuplet dialog
+ Notation editor: add action to identify chords on grid
+ Notation editor: add support for manually entering chord notation
+ Notation editor: fix chord notation sometimes not being visible immediately after entering
+ Notation editor: improve chord detection
+ Notation editor: include user-defined chords (loaded from MIDI editor key snap dropdown when identifying chords
+ Notation editor: increase space between staves
+ Notation editor: notation events follow notes rather than preceding, may affect user scripts/plugins that read notation messages
+ Notation editor: support "chart" clef (no notes, just beat markings and chord/other notation)
+ ReaFIR: add new improved default quality mode (previous behavior is now legacy 2007-2016 mode)
+ ReaFIR: decreased CPU use
+ ReaScript: support ending multiple submenus at once [t=184858]
+ VSTi: experimental support for custom articulation maps, to map REAPER notation to keyswitches or VST3 expression
+ WavPack: large file reading support
+ WavPack: upgrade to v5
+ Notation editor: support per-note text ornaments
# Notation editor: avoid collisions between tempo changes and project markers
# Notation editor: fix tuplet snap dance
# Notation editor: store custom notehead information as plain text
# ReaVerb: optimize spectrogram code, improve range
__________________
subproject FRs click here
note: don't search for my pseudonym on the web. The "musicbynumbers" you find is not me or the name I use for my own music.
|
|
|
12-20-2016, 05:02 PM
|
#2
|
Human being with feelings
Join Date: Dec 2012
Posts: 13,333
|
Cubase sucks Thank you Devs for such nice things!
|
|
|
12-20-2016, 05:26 PM
|
#3
|
Human being with feelings
Join Date: Apr 2012
Location: Christchurch, New Zealand
Posts: 482
|
Thanks for this update.
Having the most relevant notation actions in the piano roll is most appreciated.
I like the new plain text notehead format; it just made a couple of my glyph-parsing helper functions redundant. Per-note text ornaments are a nice touch too.
I found the Artic button in the VSTi header. Any clues as to the format for these ReaperArticulationMap files?
Also, my plugins are still receiving notation events before the note...?
|
|
|
12-20-2016, 06:11 PM
|
#4
|
Administrator
Join Date: Mar 2007
Location: NY
Posts: 15,747
|
Quote:
Originally Posted by ijijn
I found the Artic button in the VSTi header. Any clues as to the format for these ReaperArticulationMap files?
|
Hm, the installer packaged the file but didn't install it, sorry about that.
Go to the Options menu, Show REAPER resource path, and in that directory create a directory called ArticulationMaps.
Put this file in the new directory, and rename it to sample.ReaperArticulationMap.
(Annoyingly, the forum software has a character limit on allowed extensions, so I can't just attach it with the right name. We will probably change the official extension to ReaperArticMap or something because of this.)
One the directory is created and the file is in there, it should show up as an option to choose when you click the Artic button on the VSTi window. The sample file explains the file format but doesn't define any articulations, you'll need to make a copy with a new name and add articulations specific to whatever virtual instrument you are working with.
|
|
|
12-20-2016, 06:27 PM
|
#5
|
Human being with feelings
Join Date: Jun 2011
Posts: 603
|
Thanks for all these updates.
Bug : identified chords are not following note position changes.
Bug : Best suggestion shouldn't be "C/A Chord" for notes "a c e". It must be "Am chord"
Bug : Reaper can't identify some basic chords "Xsus4 , Xsus2"
Please see the attacherd gifs.
Last edited by mehmethan; 08-13-2023 at 03:07 PM.
|
|
|
12-20-2016, 06:34 PM
|
#6
|
Administrator
Join Date: Mar 2007
Location: NY
Posts: 15,747
|
Quote:
Originally Posted by mehmethan
Bug : identified chords are not following note position changes.
|
They will, but you have to select the chord notation along with the notes.
|
|
|
12-20-2016, 06:51 PM
|
#7
|
Human being with feelings
Join Date: Jan 2009
Posts: 1,030
|
Looking forward to trying out the articulation mapper.
A couple of thoughts and feature requests:
1. Some libraries don't utilize keyswitches or CC for articulation mapping, so users have to use different MIDI channels. That being said, can you include "channel" in trigger_type? I'm pretty sure there is a JS effect that converts keyswitches to channels, but it would be nice to have this in the articulation mapper.
2. Can we have the option to add or subtract values for articulations? For example, let's say we have a note with with an accent. The current CC 7 value is set to 50.
note articulation accent : cc 7 64
The resulting output currently is CC 7 64
Maybe if we had something like this:
note articulation accent : cc 7 +20
The output would be cc 7 70 (50 + 20). Does that make sense? I think it would be a pretty useful feature.
|
|
|
12-21-2016, 12:50 AM
|
#8
|
Human being with feelings
Join Date: Apr 2012
Location: Christchurch, New Zealand
Posts: 482
|
Quote:
Originally Posted by schwa
Hm, the installer packaged the file but didn't install it, sorry about that.
Go to the Options menu, Show REAPER resource path, and in that directory create a directory called ArticulationMaps.
Put this file in the new directory, and rename it to sample.ReaperArticulationMap.
(Annoyingly, the forum software has a character limit on allowed extensions, so I can't just attach it with the right name. We will probably change the official extension to ReaperArticMap or something because of this.)
One the directory is created and the file is in there, it should show up as an option to choose when you click the Artic button on the VSTi window. The sample file explains the file format but doesn't define any articulations, you'll need to make a copy with a new name and add articulations specific to whatever virtual instrument you are working with.
|
Thanks for the very detailed explanation. I look forward to giving it a go!
|
|
|
12-26-2016, 12:01 PM
|
#9
|
Human being with feelings
Join Date: Dec 2016
Location: Finland
Posts: 197
|
Quote:
Originally Posted by vitalker
Cubase sucks Thank you Devs for such nice things!
|
Really? Or its about people who cant afford it??
|
|
|
12-26-2016, 01:20 PM
|
#10
|
Human being with feelings
Join Date: Dec 2012
Posts: 13,333
|
Quote:
Originally Posted by Germps112
Really? Or its about people who cant afford it??
|
Do you know what sarcasm stands for?
|
|
|
12-20-2016, 05:09 PM
|
#11
|
Human being with feelings
Join Date: Jan 2012
Location: North East UK
Posts: 493
|
Quote:
Originally Posted by musicbynumbers
December 20 2016
+ VSTi: experimental support for custom articulation maps, to map REAPER notation to
|
This is very exciting!!!!
How do we access this feature?
Last edited by reddiesel41264; 12-20-2016 at 05:18 PM.
|
|
|
12-20-2016, 05:25 PM
|
#12
|
Human being with feelings
Join Date: Jun 2009
Location: South, UK
Posts: 14,214
|
Thanks devs!
Some really awesome stuff here!
Much appreciate the expression and midi editor support!
__________________
subproject FRs click here
note: don't search for my pseudonym on the web. The "musicbynumbers" you find is not me or the name I use for my own music.
|
|
|
12-20-2016, 06:26 PM
|
#13
|
Human being with feelings
Join Date: Jun 2007
Posts: 528
|
Quote:
Originally Posted by reddiesel41264
This is very exciting!!!!
How do we access this feature?
|
Indeed! Great stuff! Please make this also work with bank and program changes!
|
|
|
12-20-2016, 05:42 PM
|
#14
|
Human being with feelings
Join Date: Jun 2007
Location: Terra incognita
Posts: 7,670
|
Lots of notation editor stuff, great, thanks. Question to testers/users:
Quote:
Originally Posted by musicbynumbers
+ MIDI editor: display notation data in a lane in the piano roll
|
Seems to work at least for everything under Dynamics and Chords. But both Text (under Dynamics) and Chords (Identify chords on editor grid) will appear with the pretext "Text" in the piano roll Notation lane. Would it make sense for the identified chords appear with text "Chord" instead?
Quote:
+ MIDI editor: update snap-to-key checkbox when switching MIDI items [t=183393]
|
Works now correctly between items, thanks for the fix.
Last edited by xpander; 12-20-2016 at 05:52 PM.
|
|
|
12-20-2016, 07:00 PM
|
#15
|
Human being with feelings
Join Date: Jan 2009
Posts: 1,030
|
Quote:
Originally Posted by musicbynumbers
December 20 2016
+ VSTi: experimental support for custom articulation maps, to map REAPER notation to keyswitches or VST3 expression
+ Notation editor: support per-note text ornaments
|
This is a pretty cool update, but these two are my favorite additions by far. Thanks!
|
|
|
12-21-2016, 02:35 AM
|
#16
|
Human being with feelings
Join Date: Feb 2016
Posts: 99
|
Quote:
Originally Posted by musicbynumbers
December 20 2016
+ VSTi: experimental support for custom articulation maps, to map REAPER notation to keyswitches or VST3 expression
|
Yes! I've been waiting for that. Thank you!
|
|
|
12-21-2016, 10:15 AM
|
#17
|
Human being with feelings
Join Date: Aug 2011
Location: Los Angeles, CA
Posts: 308
|
Quote:
+ MIDI editor: display notation data in a lane in the piano roll
+ VSTi: experimental support for custom articulation maps, to map REAPER notation to keyswitches or VST3 expression
|
Absolutely great stuff, thanks for these!
|
|
|
12-22-2016, 03:02 AM
|
#18
|
Human being with feelings
Join Date: Jul 2009
Posts: 3,714
|
Quote:
Originally Posted by musicbynumbers
+ Notation editor: notation events follow notes rather than preceding, may affect user scripts/plugins that read notation messages
|
I am concerned about scripts/plugins that *write or move* notation messages, and in particular how to sort such events:
At present, the ReaScript function MIDI_Sort is too dangerous to use, since it fails on certain unsorted notes and turns them into extended notes. MIDI_Sort can sort notation messages, though.
I have therefore instead been trying a workaround, namely using OnCommand to call the MIDI editor's built-in Actions (such as Invert selection) to invoke the MIDI editor's own MIDI sorting. Unfortunately, the MIDI editor actions are dangerous too: While these actions can properly sort unsorted notes, they cannot sort notation events: If a notation text event is not pre-sorted exactly correctly, the MIDI editor simply deletes the event.
Will notation events that are written according to pre-v5.31 standards be deleted by v5.31's MIDI editor and vice versa?
Would it be possible to combine the best features of the ReaScript sorting algorithm and the MIDI editor algorithm, so that both are safe to use with notes as well as notation events?
* The MIDI editor should sort notation events instead of deleting them, and
* MIDI_Sort should sort notes similar to how the MIDI editor does it, to avoid extended notes.
Last edited by juliansader; 12-22-2016 at 05:05 AM.
|
|
|
Thread Tools |
|
Display Modes |
Hybrid Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -7. The time now is 05:12 AM.
|