v7.16+dev0610 - June 10 2024

[sockmonkey72]

v7.16+dev0610 - June 10 2024

• * Includes feature branch: Media Explorer time selection and grid improvements
• * Includes feature branch: option for arrange view grid to follow metronome pattern
• * Includes feature branch: fractional beats display option for ruler
• * Includes feature branch: Default 7.0 theme adjuster inclusion
• * Includes feature branch: up to 4 different click types/samples in metronome
• * Includes feature branch: render setting to preserve source media sample rate if possible
• * Includes feature branch: RGB profile tweak
• * Includes feature branch: improved UI for editing click pattern in metronome, time signature markers, and click source properties
• * Includes feature branch: improvements to grid spacing and labeling with compound time signatures
• * Includes feature branch: improved loudness peaks
• * Includes feature branch: global preference to crossfade left, center, or right when splitting
• * Includes feature branch: optionally display mouse position indicator line in arrange view
• * Includes feature branch: changes to lane recording settings and behavior
• * Includes feature branch: up-rank/down-rank takes and take markers
• * Includes feature branch: additional localization options
• * Includes feature branch: extended ASCII encoding for .wav file text metadata
• + Default theme: fix theme transport background color when pure black [p=2787054]
• + Default theme: prevent TCP track numbers clipping [p=2787902]
• # Mouse indicator: reduce flickering when snap is enabled

This thread is for pre-release features discussion. Use the Feature Requests forum for other requests.

Changelog - Pre-Releases

Generated by X-Raym's REAPER ChangeLog to BBCode

[daxliniere]

Mouse indicator is still very flickery, whether snap is on or off.

EDIT: ahh, it's really not coming out in the LICEcap, which looks basically flawless. Do I need to shoot some actual video?

[ovnis]

If it's like the shaky playback cursor problem, something tells me it's going to be impossible to fix.

[deeb]

* Includes feature branch: fractional beats display option for ruler

I think currently "fractional beats" is not a good name, since reaper is fractioning bars and not beats, so i think, as is, instead the name should be actually named "fractional bars".

I would like fractional beats tho (personally i have no use for bars and my mind thinks in a different way).

instead of display for 1/8t like:

1 1.2 1.3 1.4 1.5 1.6 1.7 1.8 1.9 1.10 1.11 1.12

Display Like this:

1.1 1.2 1.3 2.1 2.2 2.3 3.1 3.2 3.3 4.1 4.2 4.3

And would be good to remove the denominator /12 because it's very noisy

[Daodan]

While the metronome branch is here, I’ll remember one small but annoying thing. When repeat is turned on, but the loop is not set, and the cursor reaches the end of the project and playback starts over, the metronome sound is played twice, overlapping each other.

You can see when I remove loop points project starts to loop by itself and there is a glitch in metronome sound between loops.
that's what it sounds like
normal https://stash.reaper.fm/48754/Normal.mp3
glitched https://stash.reaper.fm/48755/Glitch.mp3

[cool]

It seems that the old bug has returned: in the previous version and in this one, combinations of mouse click and Ctrl or Shift do not work if you click on track elements (Meter, Volume, Pan). They work like regular clicks without a key. Tcp and Mcp.
On clicks on the background or label, these combinations work as expected.

[FeedTheCat]

With "Project start measure" at 0 and "Divide arrange view vertically when ruler displays beats" enabled.

[FeedTheCat]

Same settings as previous post (and shade every 4 measures), the shading still starts at measure 1 instead of 0.



Resetting the shade with a time signature marker also doesn't work as expected:

[EvilDragon]

Quick question: in MIDI editor event view, when adding a new event I see some "Port" event type. What is this and what's it used for? I'm not sure when this was added.

[FeedTheCat]

I'd like to suggest adding a new theme color for "Track background (vertical shading)". It's really hard to choose colors that work well for both orientations. In my experience most themes only look good with one of them. (you usually want higher contrast for vertical shading)

I'd also love to see an option to reset vertical shading at the beginning of regions (as ferropop suggested). Using time signature markers is fine but having it work automatically as a set-and-forget option seems really smart and would really be next-level. I can't think of a situation where this wouldn't work in any of my old projects.

[Tale]

Originally Posted by EvilDragon

Quick question: in MIDI editor event view, when adding a new event I see some "Port" event type. What is this and what's it used for? I'm not sure when this was added.

I don't know, but if I do this it consistently crashes REAPER (on macOS Sonoma):

1. Launch REAPER.
2. Add track.
3. Draw MIDI item.
4. Edit MIDI item in event list mode.
5. Insert 2 (or more) Port events.
6. Change to piano roll mode... Crash!

I also noticed that if you edit one of the port event after step 5, then all port events change to the new value.

EDIT: It also crashes on Windows 10. Do note that this is not new to this prerelease though; the current production version also crashes.

[smandrap]

Originally Posted by Tale

I don't know, but if I do this it consistently crashes REAPER (on macOS Sonoma):

1. Launch REAPER.
2. Add track.
3. Draw MIDI item.
4. Edit MIDI item in event list mode.
5. Insert 2 (or more) Port events.
6. Change to piano roll mode... Crash!

I also noticed that if you edit one of the port event after step 5, then all port events change to the new value.

EDIT: It also crashes on Windows 10. Do note that this is not new to this prerelease though; the current production version also crashes.

Confirmed on MacOS 12.6.8

Thread 0 Crashed:: reaper Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib        	    0x7ff802035ffe __pthread_kill + 10
1   libsystem_pthread.dylib       	    0x7ff80206c1ff pthread_kill + 263
2   libsystem_c.dylib             	    0x7ff801fb7d24 abort + 123
3   libsystem_malloc.dylib        	    0x7ff801e95357 malloc_vreport + 551
4   libsystem_malloc.dylib        	    0x7ff801e9852b malloc_report + 151
5   reaper_midi.dylib             	       0x1124ded9a MIDIFile_Context::populateNoteList(bool, bool) + 5370
6   reaper_midi.dylib             	       0x112486aac MIDIFile_Context::SetViewMode(HWND__*, int) + 412
7   reaper_midi.dylib             	       0x11246f890 MIDIFile_Context::editDlgProc(HWND__*, unsigned int, unsigned long, long) + 16320
8   reaper_midi.dylib             	       0x11246f890 MIDIFile_Context::editDlgProc(HWND__*, unsigned int, unsigned long, long) + 16320

[Justin]

Originally Posted by Tale

I don't know, but if I do this it consistently crashes REAPER (on macOS Sonoma):

1. Launch REAPER.
2. Add track.
3. Draw MIDI item.
4. Edit MIDI item in event list mode.
5. Insert 2 (or more) Port events.
6. Change to piano roll mode... Crash!

Hmm having trouble reproducing, can you give your reaper.ini? any deferred scripts running? a .gif of doing it too -- maybe we're inserting via diff actions?

I also noticed that if you edit one of the port event after step 5, then all port events change to the new value.

I did notice that if you change the value via the inline text editor (doubleclicking the column in the list editor), it doesn't stick (but not all port events change, none do?). fixing that.

[Tale]

Originally Posted by Justin

Hmm having trouble reproducing, can you give your reaper.ini? any deferred scripts running? a .gif of doing it too -- maybe we're inserting via diff actions?

You've got mail! I don't think I have any scripts running...

[EvilDragon]

So that's it, this even just reroutes all following events to a particular port?

Hmm, curious. Would be nice to also have it in CC lane area, then.

[Justin]

Originally Posted by EvilDragon

So that's it, this even just reroutes all following events to a particular port?

Hmm, curious. Would be nice to also have it in CC lane area, then.

AFAIK it's nothing interesting just some archaic MIDI message format that for some reason we support: http://midi.teragonaudio.com/tech/midifile/obsolete.htm