+ FX: improve behavior when removing latent plug-ins from Monitoring FX/Record Input FX + MIDI editor: improve undo behavior with multiple context and various actions [t=136814] + Mixer: fix track label index invalid after duplicate if not in TCP [t=177395] + Routing: filter out invalid send-to-self on project load [p=1687479] # Notation editor: fix incorrect beaming when processing rhythm pattern exceptions [p=1687353] # Notation editor: fix note insert/selection when zoomed in
__________________ 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.
I think it's like a sixth sense now.. I've not checked Landoleet for days and then I get pre 7 either that or no one else checks any more..
__________________ 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.
I'm seeing that with the MIDI editor both open or closed. Having said that, flushing FX should have the same effect as note-offs, so meh corner case...
-> Preferences default Metronome output: NOT "Use all project master outs" (sending to different hardware outs)
Result: Metronome won't play through Monitor FX chain at all (even if told so)!
Hmm, those options all are working as expected here (setting outputs in preferences, then if metronome-via-monitoring-FX is enabled, it is routed appropriately). Just make sure your monitoring FX chain has enough channels to match the physical output you selected (e.g. if you select outputs 3/4, increase your monitoring FX chain to be 4 channels).
I'm seeing that with the MIDI editor both open or closed. Having said that, flushing FX should have the same effect as note-offs, so meh corner case...
Hmm, those options all are working as expected here (setting outputs in preferences, then if metronome-via-monitoring-FX is enabled, it is routed appropriately). Just make sure your monitoring FX chain has enough channels to match the physical output you selected (e.g. if you select outputs 3/4, increase your monitoring FX chain to be 4 channels).
function set note ends to start of next note is not working properly
Reaper 5.18
...
Reaper 5.21pre7
...
This is not a bug - the behavior of the Action changed in 5.20:
Quote:
Originally Posted by schwa
Quote:
Originally Posted by juliansader
It seems that the action will not shorten a note if it means cutting the note by more than half - am I correct? (I assume this is a deliberate feature to prevent, for example, arpeggiated chords ending up as 1/64 notes.)
Yes, exactly.
Several other users have also asked about this change, so it may be a good idea for Cockos to include two flavors of the Action: one that doesn't cut note lengths by more than half, and one that does.
EDIT: Other alternatives might also be useful, such as "shorten to less than half, but not to less than grid value".
Last edited by juliansader; 05-31-2016 at 01:07 AM.
This was the behavior prior to 5.20 if the notes were even one MIDI tick apart:
That seems clearly not what anybody would want, so we changed the behavior to not shorten the note beyond half its original length. We could reduce that threshold to 25% perhaps?
That seems clearly not what anybody would want, so we changed the behavior to not shorten the note beyond half its original length. We could reduce that threshold to 25% perhaps?
There needs to be a way to determine how much leeway that action has, I'd say. Or a pop-up dialog explaining why the action wouldn't work on current note selection?
function set note ends to start of next note is not working properly
Reaper 5.18
Reaper 5.21pre7
Can confirm there is an oddity involved with this issue:
I've also experienced this since the 5.20pres, amongst some other oddities. The command will extend the notes correctly, however if there are overlapping notes, it will sometimes not shrink\expand them correctly to be legato.
I need to pull up the newest 5.21 pre, but there was another issue that seemed connected to this one in regards to how the midi editor was handling quantization. In larger sessions. sometimes the quantization algorithm will forget where the note ends were supposed to be and cause sporadic behavior. Looking at the patch notes, this may have been an unrelated issue and might've been fixed already.
x64 Windows VST bridging seems broken in 5.21.
I cannot reload all VST effects correctly in some older projects using more than 2GB memory.
Some are left off-line and cannot reload correctly anyway.
(ex. Soundtoys EffectRack)
Under such memory usage, most VST (or stock) cannot be inserted correctly. All are left offline in the insert slot.
I really appreciate the work of developers Reaper, but strange decision to change the behavior of the functions to which users have become accustomed. Imagine for example that you have in the car window button suddenly begin to include heated seats))
I really appreciate the work of developers Reaper, but strange decision to change the behavior of the functions to which users have become accustomed. Imagine for example that you have in the car window button suddenly begin to include heated seats))
The function was changed because it was not working properly in some cases, and the devs are obviously willing to lend an ear to user input and improve the behavior even further. This is cause for cheer, not complaint.
media explorer bug from december still hanging around :)
I haven't mentioned it again for a while as I thought I'd wait till most of the cool notation stuff was out the way first
There's a bug Jeffos was looking at with the media explorer shortcuts section (on the left side)
whereby using any absolute input device (like a wacom pen or a touchscreen) would get the shortcut you click on "stuck" to the mouse pointer if you clicked on a shortcut without waiting a good second or so before moving the mouse pointer again.
If you move to fast after clicking a shortcut, It's as if Reaper gets stuck in "reorganise your shortcuts" mode (where you can drag the shortcut around).
I expect it's because of how fast you can accidentally go from a normal click to a drag click on these input devices and that there's no "safe area" around the shortcuts to tolerate any small movements whilst clicking a shortcut which means that reaper thinks you want to drag rather than click.
I hope there's a fix for this as it's subconsciously made me change my behaviour in normal windows explorer as well now as I keep fearing I'll accidentally drag a folder on top of another one.
__________________ 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.
also devs, please consider adding the ability to use the "control" modifier in media explorer as a way of letting reaper know we want to "copy when importing" so that we can have normal drag when not using the modifier and copy when we are.
That way, we don't need a pop up dialog box or like me. toggle a toolbar button every time we import things (which is a lot here)
It would make a big difference to work flow for sound designers
Thanks.
__________________ 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.
Last edited by musicbynumbers; 06-01-2016 at 10:14 AM.
x64 Windows VST bridging seems broken in 5.21.
I cannot reload all VST effects correctly in some older projects using more than 2GB memory.
Some are left off-line and cannot reload correctly anyway.
(ex. Soundtoys EffectRack)
Under such memory usage, most VST (or stock) cannot be inserted correctly. All are left offline in the insert slot.