I suspect that this modification caused a bug in the toggle MIDI editor.
Now the most obvious problem is that if the MIDI editor is maximized, when you switch to the main interface, and then switch back, the window will become smaller, but the icon in the upper right corner will show that it is currently maximized.
In addition, the previously activated item will lose its editable properties, and the activation will jump to the first item.
I believe you have received my email. Maybe I didn't express it clearly. I can simplify the demonstration again to make this question clearer.
And there is this special case with grace notes at the same pitch as the previous non-grace note. I've dealt with this myself before when scripting.
expected:
currently:
currently good:
The G whole note midi should be eaten a bit from its end which it is.
currently bad:
- the very first grace note is lost
- the whole note ideally should have its display note length altered to still show as a whole note even when its midi is eaten from the end
[b][*]+ Vertical zoom: overhaul, allow more fractional zoom
This overhaul was long needed and is a great step in the right direction! Thank you! Gives me hope that eventually smooth intertial zoom/scroll with touch based non-stepped scrolling peripherals will be supported.
I record track automation...what exactly does this mean ?
it means that track automation recording can be prevented from suffixing your automation performance with a "return value."
TLDR: these examples show recording in AI, but this also applies to "normal," param-dominating envelopes
before - note the trailing value ahead of the record cursor, bringing me back to the starting param value:
after - the envelope is recorded as performed, the last envelope point is square/chased and ends at record stop.
DR:
by default, REAPER inserts this surfing return value envelope point at the end (or slightly ahead) of your record cursor, bringing your envelope back up to the value it was when you started recording. while this may be a useful feature for recording something temporary, like volume attenuation where you want the envelope to return to a static baseline, it's inappropriate for (imo) most automation recording - i expected to be able to use record automation to set a value that extends from the record cursor til either project end or the next available envelope point. this is how recording MIDI CCs behave, and they served as a behavioral model for this new feature.
__________________ mccrabney scripts: MIDI editing directly from the Arrange screen, inspired by jjos/MPC style sequencers
The resizeable render window is a great addition, many thanks!
Now that we can click and select individual files in the render window, wouldn't it make sense to update the waveform display accordingly to match the selection too?
+ MIDI: add preference to disable CC/PC chasing when splitting MIDI items
Thanks for the update. Any chance we could add this option to playback, for which there is still no way to disable program change chasing on start/stop?
If there is and someone could correct me, that would be awesome too
+ MIDI: add preference to disable CC/PC chasing when splitting MIDI items
Thanks for the update. Any chance we could add this option to playback, for which there is still no way to disable program change chasing on start/stop?
If there is and someone could correct me, that would be awesome too
Options: Chase MIDI note-on/CC/PC/pitch in project playback
Options: Chase MIDI note-on/CC/PC/pitch in project playback
Haha! Awkward. Thanks so much Dangguidan! I can't believe it was there hiding in plain sight. I searched for this option and asked on the forum 18 months ago and could not find this setting. For my live show I ended up inserting dummy program changes that did nothing after the actual patch change to work around it. Time to take those out
Haha! Awkward. Thanks so much Dangguidan! I can't believe it was there hiding in plain sight. I searched for this option and asked on the forum 18 months ago and could not find this setting. For my live show I ended up inserting dummy program changes that did nothing after the actual patch change to work around it. Time to take those out
Ah - that makes sense. I couldn't quite believe I had missed it.
Great job Justin and Schwa. I find the little changes like this that I use every day more exciting than big new features Reaper just gets better and better.
Other than ctrl-a to ctrl-z, ctrl combination isn't recognized anymore. Same with the previous version and the regression bug was introduced last time.
Reaper's screensets used to save the MIDI item that is being edited with the screenset, which meant if you had a MIDI item selected & switched to a screenset with a MIDI editor, the MIDI editor would open the MIDI item you were viewing at the time when you saved the screenset.
Now the screensets behaviour has been overhauled and this is no longer the case, it just saves the MIDI editor window rather than for a specific item.
Does the new update play nicely with SWS Track Height A and Track Height B? I know that zoom features have borked this in the past, so I wanted to make sure before updating.
Does the new update play nicely with SWS Track Height A and Track Height B? I know that zoom features have borked this in the past, so I wanted to make sure before updating.
I installed latest version the other day, but it doesn't work on well on my PC.
Please, can you help me how to downgrade Reaper and get back to previous version which worked just fine?
but you should probably describe the issue so it can be fixed
It takes forever to open current projects, it takes a long time to open anything.
If I download some of the old version, will it automaticaly keep all the plugins I have installed now?
Another issue is that I'm not sure which was the previous version I used for a long time which worked just fine, that's why I asked if it's possible to simply "undo" the installation of latest version and downgrading to the previous one I was using.
It takes forever to open current projects, it takes a long time to open anything.
If I download some of the old version, will it automaticaly keep all the plugins I have installed now?
Another issue is that I'm not sure which was the previous version I used for a long time which worked just fine, that's why I asked if it's possible to simply "undo" the installation of latest version and downgrading to the previous one I was using.
Thank you
It should, yes. If you saved any projects with that version, just open it in any text editor and you'll see the number in first line.
v6.77 - March 01 2023
Linear Mode
