v5.20pre15 - March 5 2016

[schwa]

v5.20pre15 - March 5 2016
+ Pan: support -6.02dB pan law [t=165955]
+ Project bay: detect junctions/symlinks/identical files when copying to project path
+ RF64: fixed slow parsing of large files
+ RF64: improve cue/region read/write
+ Sends/hardware outputs: fix non-boost pan laws for newer pan modes [p=1645781]
+ Wave64: cue read/write support
+ Wave: fix cue timing issues above 2 billion samples
# MIDI editor: deprecated storing different note names for separate MIDI channels on the same track
# Notation: add support for trill and mordent ornaments
# Notation: allow notes shorter than the display quantization setting
# Notation: change storage format (previously saved notation will not be displayed)
# Notation: display notation text events in list view for information purposes
# Notation: fix option to not display notes that are far off the staff when grand staff is used
# Notation: improve beam/flag drawing for 1/32 and shorter notes
# Notation: improved beaming with respect to meter
# Notation: sensible default grouping for various time signatures
# Notation: support editing phrases as a unit by clicking/dragging the phrase mark
# Notation: support starting new beam on any note
# Notation: support stretching crescendo/diminuendo marks

full changelog.


The highlighted change to the internal notation storage format means that any notation saved with projects prior to 5.20pre15 will no longer load with the projects. This old notation may appear in the MIDI event list as somewhat unreadable messages, even. This change doesn't affect the use of the notation editor at all.

Sorry for the inconvenience, but this is what prereleases are for.

[Victor_M]

Schwa, thank you very much for this wonderful handy improvements in notation editor.
With each update Reaper is getting better and better! )))

[IXix]

+ Pan: support -6.02dB pan law [t=165955]

That thread seems to be about something else.

[mpb2016]

Originally Posted by schwa

v5.20pre15 - March 5 2016

# Notation: add support for trill and mordent ornaments
# Notation: allow notes shorter than the display quantization setting

Thanx a lot for the ornaments and your incredibly fast work. Lots of love and support

[jsuttonmusic]

# MIDI editor: deprecated storing different note names for separate MIDI channels on the same track

Ahhh. I use this feature all the time. It's insanely useful for single track midi arranging. I find it faster and more creatively inspiring to keep all my midi data in the same track and arrange using hotkeys to switch channels and have the channels routed out to different plugins.

Maybe instead of removing this functionality, leaving some sort of toggle in for something like this would be better? One that can pick whether a single midi note name set applies to all channels or use individual channels?

[hamish]

What an exciting bag of additions to the Notation view and MIDI editing.

So glad to see beaming addressed and the ability to use the phrase mark as a selection handle. I hope to get some time over the next few days to re-make my test project in pre15.

[hamish]

Originally Posted by jsuttonmusic

Ahhh. I use this feature all the time.

Know what you mean. It's a great workflow, I hope multi-channel item note naming can stay in the post v5.20 editor.

[EvilDragon]

Yeah, an option for note names per MIDI channel should be added, instead of deprecating.

Or simply have separate actions for loading on all channels vs currently active channel? Isn't that how it used to be?

[Zephyrus]

heh, you linked to your private login

[Brado231]

I assume this build includes the extra things that were added to 5.16 that weren't in 5.20pre14?

[EvilDragon]

Of course.

[beingmf]

Originally Posted by IXix

That thread seems to be about something else.

Yeah - what kind of super secret illmuminati stuff is that???

[ELP]

1.
MIDI Files export is broken!!

Means exports(within Editor and as Arrange exports prexx to pre15)
produce corrupt MIDI Files, if MIDI events contains standard Key Signature messages.

example:
Key signature E Major

must be:

0xFF 0x59 0x02 0x04 0x00

but after export to MIDI the result is

0xFF 0x59 0x03 0x02 0x04 0x00

within Files

This would simply break MIDI Files!


2.
Key Signature from MIDI Files (import) do not work!

Standard Key Sig events are ignored from imported Files.(All REAPER Versions pre&stable)

---
1+2 both ways MIDI -as project... and reference to MIDI Files, broken!!
(together with Standard Key Sig events)

Thank you and greetings

[reddiesel41264]

I'm not sure if this was present in the previous version but the beginning of dynamics text are being cut-off. I've tried at various zoom levels.

[ijijn]

Originally Posted by schwa

# Notation: change storage format (previously saved notation will not be displayed)

Woooohooooo!!!! Such great stuff going on under the hood, and with some sweet channel loving too! Thank you so much for this and all of the other updates, of course.

I'm enjoying the logical, readable and usable text events, which run along the lines of:

NOTE <channelNumber> <pitchNumber> articulation <articulationType>
and
NOTE <channelNumber> <pitchNumber> clef <clefType>
and
NOTE <channelNumber> <pitchNumber> phrase <phraseNumber>

These are automatically stacked within the same string if multiple details apply to the same note, for example:

NOTE <channelNumber> <pitchNumber> articulation <articulationType> phrase <phraseNumber> clef <clefType>

Most terms seem to be lower case, except for the clefs, which seem to start with a capital (e.g. clef Treble). Maybe this could made be more consistent?

I imagine in the future, we'll be able to stack articulation types on the same note? This format is already flexible enough to accommodate it:

NOTE <channelNumber> <pitchNumber> articulation <articulationType1> articulation <articulationType2>

For anyone wishing to hook into this event format right away, here's what I've found from doing some quick experimentation with midirecv_str(offset, message):

message structure by [index]
----------------------------
[0]  => 255 (xFF) - text event
[1]  =>  15 (x0F) - 'REAPER notation' type of text event
[2]… => <the actual string body, as shown in the event list view>

The string is space-delineated, so you can use this to split it up easily into the various tokens/identifiers and number values you need. These number values are expressed as decimals in plain text, so they need to be given the old conversion treatment, either using the built-in match or similar, or your own wee algorithm if you prefer.

Schwa, naturally feel free to correct or clarify any of this.

Thanks again, this is hugely exciting!

ij

[schwa]

Originally Posted by ELP

produce corrupt MIDI Files, if MIDI events contains standard Key Signature messages

Fixing, thanks!

[schwa]

Originally Posted by reddiesel41264

I'm not sure if this was present in the previous version but the beginning of dynamics text are being cut-off.

What OS is this? For sure this is running pre15?

[Jae.Thomas]

does this sync up with the 5.16 branch

[hopi]

as regards the notation stuff with the ME... where are we at with XML files to date? Can we now or will will be able to import and export them?

[EvilDragon]

Originally Posted by schwa

# MIDI editor: deprecated storing different note names for separate MIDI channels on the same track

OK Scwha I just installed the previous prerelease. There were actions for loading note names just for active channel - they are now removed in pre15.

I urge you to bring back those actions, but remove them from the menus by default (as a sorta deprecation?). Some of us would still like to use note names per MIDI channel. Thank you!

[EvilDragon]

Originally Posted by hopi

as regards the notation stuff with the ME... where are we at with XML files to date? Can we now or will will be able to import and export them?

Not in 5.20.

[snooks]

I have to say that the display quantize is a regression for me. If however this is a temporary stepping stone towards a variable setting that will allow disallowing tiny notes then today is again a great day.

[ELP]

"Fixing, thanks"
Thank you, schwa

There is a little bug together with insert REAPER notation TEXT event.

First time insert "REAPER notation TEXT" at a new position within notation editor produce/capture
always wrong ASCII code


---
Why xml ^^ ...
Not necessary..

All necessary additional notation informations are later&now stored within a "stink" normal
MIDI file as REAPER Meta Events.
That is one absolute brillant way and unbelievable/incredible one novelty now.

The last 20 years or so, people spent there time to invent rather
"zig" new container formats,
instead of that to use,
which has properly been around for over 30 years now.
And in principle/really to endless extensions can be extended.
Standard MIDI Files.

Normally without any conflict to older/new progs/hardware,
Simply by the fact, that things which not known like unknown chunks/unknown metas etc.pp within the MIDI File,
!!according to standard rule / MIDI specification!!,
should be ignored/skipped.

However, when programs/hardware
already not adhere to basic MIDI specifications/standards,
that is not a problem with the specification/format as such, it is the problem of the manufacturer/Dev ..

There is no need of hundreds of new formats/container
which than mostly would never been one standard.

The other should simply learn/understand how to import/export
"standard" REAPER notation meta events from/to midi files ^^ ..


Very simple.

[reddiesel41264]

Originally Posted by schwa

What OS is this? For sure this is running pre15?

Yes definitely pre15, Windows 10 x64

[airon]

Originally Posted by schwa

+ Project bay: detect junctions/symlinks/identical files when copying to project path

Test I did :

• Empty session.
• Drop in audio file something.wav.
• Copy to project directory from project bay.
• Drop in audio file something.wav from different location, but identical in content and name
• Did copy to project directory from project bay
• The reference is changed to the existing file in the project directory. All good.

Second test :

• Empty session.
• Drop in audio file something.wav.
• Copy to project directory from project bay.
• Drop in audio file something.wav from different location, but DIFFERENT in content
• Did copy to project directory from project bay
• Error.

What should have happened:
File copied but named filename-01.wav or something like that, same as when you "Save As" a project with Copy All Media...

[DarkStar]

Originally Posted by schwa

v5.20pre15 - March 5 2016
# MIDI editor: deprecated storing different note names for separate MIDI channels on the same track

full changelog.

Originally Posted by EvilDragon

OK Scwha I just installed the previous prerelease. There were actions for loading note names just for active channel - they are now removed in pre15.

I urge you to bring back those actions, but remove them from the menus by default (as a sorta deprecation?). Some of us would still like to use note names per MIDI channel. Thank you!

Indeed, some of us need them. Just one example - to name different key-switches for the instruments on the different channels.

I wonder why they were removed? Some conflict with another feature?

[schwa]

Originally Posted by ELP

First time insert "REAPER notation TEXT" t a new position within notation editor produce/capture always wrong ASCII code

Fixing, thanks.

[schwa]

Originally Posted by DarkStar

Indeed, some of us need them. Just one example - to name different key-switches for the instruments on the different channels.

I wonder why they were removed? Some conflict with another feature?

The feature will be restored in the next build, though with a simplification: there will be a single action called "note name actions apply to the active channel only", rather than a separate actions for loading into the active channel vs loading for all channels, etc.

We're expanding the note name mapping to include mapping pitches and notation display, and it creates a lot of complexity to support multiple channel-specific actions for everything. So we thought we'd simplify things and see if anyone cared, which apparently they do So we'll restore the channel-specific feature, but hopefully in a way that doesn't make it too user-unfriendly as we expand the note mapping feature.

[DarkStar]

^^^^
Thank you, that makes sense.

PS: If I have "All channels" selected in the MIDI Editor, I still would like the note names to be loaded onto all the channels .

PS2: [Off-topic alert] as you are giving the Note Names a good ol' reworking can you consider adding names for the CC lanes too?

[EvilDragon]

Originally Posted by schwa

The feature will be restored in the next build, though with a simplification: there will be a single action called "note name actions apply to the active channel only", rather than a separate actions for loading into the active channel vs loading for all channels, etc.

Ah, so it will be a toggle, with reported on/off state, so we could toolbar it? That would be great, I think.


Names for CC lanes would be a-flipping-mazing, too.

[memyselfandus]

Awesome

[mpb2016]

I guess the "Display notes that are more than three ledger lines off the staff" option, is to be able to hide keyswitches?

The problem is that a got a piccolo going up to an E three lines up, just above these three lines, and at the same time keyswitches several octaves below. So i got to choose between seeing the notes and also the keyswitches or not seeing any of them.

I guess I could use 8va but Id prefer if there was an option to "Display notes that are X lines off the staff" or if the new midi meta event development might mean that an option to use something better than keyswitches is on the way?

[Dstruct]

Originally Posted by airon

Second test :

• Empty session.
• Drop in audio file something.wav.
• Copy to project directory from project bay.
• Drop in audio file something.wav from different location, but DIFFERENT in content
• Did copy to project directory from project bay
• Error.

Confirmed (with unsaved project).

FIXED (5.20pre16)

[kerryg]

Beaming now works as expected in 4/4 time - thanks Schwa!! I'm in a schedule crush but I'll test more time signatures as time permits.

[Xasman]

To reproduce:

1. In Project Settings - choose default pan law.
2. Create a new channel
3. Right-click on pan knob and select "Override default track pan law"
4. Select the new -6.02dB pan law and close the dialog
5. Re-open dialog

Result: Dialog now shows -6.0dB pan law (but the behaviour remains true to -6.02dB pan law

Expected result: same behaviour but dialog should still show -6.02dB

Next:
-
6. Re-select -6.02dB pan law and click the "Gain Compensation" checkbox (behaviour is correct, i.e. -6.02dB pan law with gain compensation applied)

7. Now deselect the "Gain Compensation checkbox"

Result: Behaviour reverts to uncompensated -6.0dB pan law

Expected result: Behaviour should revert to uncompensated -6.02dB pan law

[musicbynumbers]

Just a quick thing I've noticed since going to pre15 (although it might be there in earlier versions, can't check yet)

Whenever I use the "apply track fx as item" option, Reaper always has to redraw all the peak files for all items in the project.

That's the first time I've noticed it happening but will keep an eye on it and do further testing when I get time.

Anyone else seeing this?

[Dstruct]

Originally Posted by Xasman

To reproduce:

1. In Project Settings - choose default pan law.
2. Create a new channel
3. Right-click on pan knob and select "Override default track pan law"
4. Select the new -6.02dB pan law and close the dialog
5. Re-open dialog

Result: Dialog now shows -6.0dB pan law (but the behaviour remains true to -6.02dB pan law

Expected result: same behaviour but dialog should still show -6.02dB

Next:
-
6. Re-select -6.02dB pan law and click the "Gain Compensation" checkbox (behaviour is correct, i.e. -6.02dB pan law with gain compensation applied)

7. Now deselect the "Gain Compensation checkbox"

Result: Behaviour reverts to uncompensated -6.0dB pan law

Expected result: Behaviour should revert to uncompensated -6.02dB pan law

Didn't test the sound output but I can confirm the track pan dialog display issue.

FIXED (5.20pre16)

[Justin]

Fixing that pan law bug, thanks

[Win Conway]

If you are about to work on a note mapping overhaul, can we start to think about note rearranging, so if something was on C3 you could drag it down to be next to C2 (poor simple example, but you get the idea)
This is extremely useful for mapping samples and kits.
Also tied in to this is note removal, we have remove unused right now, but the ability to remove individual notes would be excellent (I actually recorded an ekit trigger last week that was across octaves and had sound variations throughout the octave, ball ache to edit is an understatement)

[Jae.Thomas]

oh man I would love that gpunk