+ Glue: fix creating small items when glueing items that begin/end on partial sample boundaries [t=205783]
thanks!
Also, It seems now that if you have the midi editor docked under the arrange page and then close the midi editor. The arrange page no longer jumps to the top so thanks for this.
Although, it does seem to to scroll up a bit so that the item you were just in is just off the bottom of the screen. Better though than all the way to the top!
__________________ 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.
+ Keyboard: add option to allow the space key to be used for navigation in various windows [t=205757]
Is it possible to use keyboard shortcuts when envelope window, routing window and FX chain window are opened ? Actualy, we can't do nothing with shortcuts. But, yes, the space barre works pretty well !
Is it possible to use keyboard shortcuts when envelope window, routing window and FX chain window are opened ? Actualy, we can't do nothing with shortcuts. But, yes, the space barre works pretty well !
It would be awesome that our main shortcuts be always the master rather than obeying floating windows yes!
Thanks Justin, just read this morning on this original thread about the spacebar and couple hours later... fixed.. thanks!
from 17b: the action "open item in built in editor" behaves differently when triggered by mouse modifier vs by action.
it behaves as expected via mouse modifier.
when triggered by action, it opens the wrong item in focus. see gif, it opens the first track with a midi item instead of the track whose item was clicked/entered.
the other issue i posted in 17b is still there as well but i'm getting the memo that that's not the focus of this cycle
__________________ 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.
from 17b: the action "open item in built in editor" behaves differently when triggered by mouse modifier vs by action.
when triggered by action, it opens the wrong midi item.
it behaves as expected via mouse modifier.
when triggered by action, it opens the wrong item in focus. see gif, it opens the first track with a midi item instead of the track whose item was clicked/entered.
the other issue i posted in 17b is still there as well but i'm getting the memo that that's not the focus of this cycle
__________________ 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.
Seeing keyboard adjustments being made...
I was wondering if the standard keys for screensets (F7-F12 I guess) could be passed through in the FX Browser. I have it docked so whenever I want to change the screenset and the FX Browser has the focus, nothing happens.
from 17b: the action "open item in built in editor" behaves differently when triggered by mouse modifier vs by action.
it behaves as expected via mouse modifier.
when triggered by action, it opens the wrong item in focus. see gif, it opens the first track with a midi item instead of the track whose item was clicked/entered.
This is an instance where descriptions might be better than a .gif.
You are saying "If you run the open MIDI editor action with a single item selected, and the option to 'open all project MIDI' is set, then the first item (by track) is focused rather than the selected item". Fixing that...
Quote:
the other issue i posted in 17b is still there as well but i'm getting the memo that that's not the focus of this cycle
If you're going to say something here you should be more specific otherwise this comment will be effectively ignored.
I have the impression that all the improvements on the focus inside the midi editors have completely disappeared.
Here's my usual test project result:
If you can, instead describe this as "step 1) set options to x/y/z. 2) create MIDI item, ... step X: switch to this view. Expected behavior: X, actual behavior: Y". Watching the video I have no idea what's going on.
Hi Justin, thanks for your reply.
Sure. It’s the same test project with the same actions I used to help and report behaviours during the previous pre release cycle.
I didn’t think the video would be unclear, sorry about that...
Cursor is at bar 65, I just select the items, open the midi editor with a shortcut, switch to notation editor, then back to piano roll, then select the tracks in the track list. That’s it, I thought it would be pretty self explanatory.
the expected behaviour would be:
- to see the cursor
- to see the notes inside the items i selected
- to see a time range that revolves around the cursor position
The video shows of course the actual behaviour, which is:
- i don’t see notes,
- i don’t see the cursor
- the time range is far from even being close to the cursor
- selecting from the track list has no effect whatsoever
aha! i think i found the source of the bad behavior
using these settings:
double clicking midi items to select/open them results in the previously selected item being re-selected. watch as my selection follows my mouse as it double clicks other midi items:
this is why i have been having a problem with midi items becoming unselected from within the midi editor, and thereby inactive and un-editable.
from another angle: watch as i double click each midi item in sequence and see how the selection trails by 1. it seems to select a split second after i double click the next midi item.
my mouse modifier is default for double click
__________________ 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.
1. Nice. Opening with Project Sync is not auto zooming.
2. I seem to be able to maintain a core "visible only" workflow with the settings below. It will be nice to have some more control (actions, etc) over making things editable/visible on demand, but this is an improvement in my book for a basic setup. (Need to test more, certainly, especially switching the pref actions)
Code:
One editor per PROJECT
Behavior for "open..." [open all selected items]
[ ] Make secondary items editable when opened from arrange
[x] Avoid automatically setting MIDI items from other tracks editable
[ ] Active item follow selection changes in arrange
[ ] Selection linked to visibility
[ ] Selection linked to editability
(Need to test more, certainly, especially switching the pref actions)
Yeah, switching to this (and doing some stuff) and back to settings in previous post puts it in a state where you can't predict reliably if items will open as visible or editable.
Code:
One editor per PROJECT
Behavior for "open..." [open all selected items]
[x] Make secondary items editable when opened from arrange
[x] Avoid automatically setting MIDI items from other tracks editable
[ ] Active item follow selection changes in arrange
[ ] Selection linked to visibility
[ ] Selection linked to editability
---------------------------------------
edit:
I don't want these ON at all I believe:
Code:
[ ] Active item follow selection changes in arrange
[ ] Selection linked to visibility
[ ] Selection linked to editability
I want to click/select in arrange freely without losing Ed/Vis states in MIDI Editor, and double click to switch item in MIDI Editor without causing selection change in arrange. Maybe the linked actions might be useful in conjunction with some additional actions (select all visible items, etc) in the future, but right now they don't fit anything for me. (Edit 3- possible exception of toggling the third of those temporarily. Maybe. Not yet.)
With those settings in mind, both the top settings in this post and
Code:
[ ] Make secondary items editable when opened from arrange
[ ] Avoid automatically setting MIDI items from other tracks editable
seem unpredictable.
The following seems more solid from arrange double click than either of those two, but still can't return to settings in my first post in this thread (which is the one I like the most).
Code:
[x] Make secondary items editable when opened from arrange
[ ] Avoid automatically setting MIDI items from other tracks editable
I'm not talking about zoom at all, just Editability/Visibility.
-----------------
Edit 2:
Exploring
Code:
[x] selection linked to editabilty
And seeing the reselection behavior McCrabney reports. Also, the item which was formerly active may be left as E/V that doesn't correspond to what was desired based on arrange item selection before double click. A lot of times, can get it to a sensible result with additional performance of open action or something...
Finding
Code:
[x] Make secondary items editable when opened from arrange
[ ] Avoid automatically setting MIDI items from other tracks editable
Need to be opposing each other, like shown or reverse, rather than both the same. Indecipherable chaos otherwise.
--------------
edit 4:
Can't change these options back and forth, at least back to functionality of post #24. Reaper needs to be shut down, after resetting to those options, and restarted to get rid of lingering unwanted editability which will appear when switching items.
Checked with pre2 as well.
--------------
edit 5:
Pre3 seems to have had a positive effect on these matters.