I donīt know if itīs been addressed - most probably not, since this release came just after I reported it -, but I didnīt have any problem with Synth 1 at least up to dev1209a -. Since thereīs no mention of a fix, I report it again since itīs quite worrying for me - and probably also for many, many users who use Synth1 on a daily basis -.
I wonīt be able to test thoroughly right now, but I hope the issue can be easily nailed.
Hi,
CC selection follows note selection is not working anymore for me...It's the first time I notice in a while so it might be an older issue not strictly related to this release
Thanks
Best
-t
__________________
MacOS 10.15.7
Mac Pro 6-Core - 64GB ram
Motu M4
From V6 onwards, there seems to be a small adjustment in the writing of velocity in the piano window. The writing velocity follows the editing velocity before. This setting makes us very unaccustomed.
The setting in V5 is to follow velocity only when the note is clicked. Can I return the setting to V5?
As for the problem of note color, the default color is not obvious after the note is selected. When multiple notes are connected together, it will be mistaken as one note.
I have to change the note color. Here is a comparison between the default and custom colors.
Last edited by dangguidan; 12-29-2022 at 08:11 AM.
I don't think it needs a preference. It needs a behavioral update. One simple if clause: if close button started overlapping with a toolbar button, hide it. As soon as there's room to show close button without overlapping, show it again.
It needs a behavioral update. One simple if clause: if close button started overlapping with a toolbar button, hide it. As soon as there's room to show close button without overlapping, show it again.
Yes, and it is in official versions of Reaper. But Reaper doesn't remember pin state after hiding and showing pin button. It always unpinned after hiding.
From V6 onwards, there seems to be a small adjustment in the writing of velocity in the piano window. The writing velocity follows the editing velocity before. This setting makes us very unaccustomed.
The setting in V5 is to follow velocity only when the note is clicked. Can I return the setting to V5?
Sorry, Maybe I didn't make it clear.
Specifically, after I wrote a few notes, I swiped the mouse cursor over the match stick of velocity in CC lane to adjust the velocity of these notes. This action will not affect the velocity of the next written note in V5, but it will affect the velocity of the next written note in V6. I am not used to this setting now. Can I go back to V5?
Sorry, Maybe I didn't make it clear.
Specifically, after I wrote a few notes, I swiped the mouse cursor over the match stick of velocity in CC lane to adjust the velocity of these notes. This action will not affect the velocity of the next written note in V5, but it will affect the velocity of the next written note in V6. I am not used to this setting now. Can I go back to V5?
Ah sorry, I misread your comment. We'll revert this behavior for the next build.
I don't think it needs a preference. It needs a behavioral update. One simple if clause: if close button started overlapping with a toolbar button, hide it. As soon as there's room to show close button without overlapping, show it again.
What about the pin? I presume your comment also relates to pin as well as the close button.
v6.01+dev1213 - December 13 2019[list][*]# MIDI editor: add options to color unselected note body and/or border by theme color when using track or media item colors
What is the use case for 'color unselected note body by theme color when using track or media item colors'?
Isn't this hiding/overriding the track or media item colors in unselected notes?
What is the use case for 'color unselected note body by theme color when using track or media item colors'?
if someone wants all of their borders to be colored-by-track, but not the notes themselves, they could select this option.
it just fills out the color feature set nicely. i have been reflecting on how far REAPER's "color by track" capabilities have come when looking back at old bug reports. there was a time when color by track resulted in this:
now, it's really nicely implemented. the only lingering issue was brought up by gofer, where unselected notes are a darker version of the track color rather than the track color itself. this is problematic for, as someone else said, people who use different shades of the same track color to indicate different instruments from the same section (lighter shades of orange for violin down to darker for cello).
i don't experience this, because i'm using the same 8 colors across all projects, representing 8 channels of midi for 8 vsti tracks from my controller. my 8 colors are all very distinct, so i don't get bit by the above darkening issue. however, i will be overhauling my defaults and REAPER settings in general for 6.0 after my next project is finished...
__________________ mccrabney scripts: MIDI edits from the Arrange screen ala jjos/MPC sequencer
|sis - - - anacru| isn't what we performed: pls no extra noteons in loop recording
| - - - - - anacru|sis <==this is what we actually performed.
if someone wants all of their borders to be colored-by-track, but not the notes themselves, they could select this option.
I think that is not really a feasible or recommended option for any serious work.
For example, velocity and CC lanes are using note body colors only.
You would not be able to tell difference between tracks in velocity and CC lanes.
For example, velocity and CC lanes are using note body colors only.
ah, yeah that does look like it would be an issue for those using that option
__________________ mccrabney scripts: MIDI edits from the Arrange screen ala jjos/MPC sequencer
|sis - - - anacru| isn't what we performed: pls no extra noteons in loop recording
| - - - - - anacru|sis <==this is what we actually performed.