|
|
|
05-22-2019, 01:31 PM
|
#1
|
Human being with feelings
Join Date: Sep 2013
Posts: 657
|
v5.978+dev0522 - May 22 2019
v5.978+dev0522 - May 22 2019
- + ReaScript: extend GetLastTouchedFX() to support take FX [t=221165]
- + ReaScript: support basing functions that affect points in automation items on either one full loop iteration, or all visible points (see documentation)
- # MIDI editor: better handling of channels when using mouse modifier to move CC segment respecting time selection
- # MIDI editor: deprecate option to not select CC events on mouse click [p=2137798]
- # ReaScript: pass NULL to extensions for optional REAPER datatype pointers that scripts do not supply
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
|
|
|
05-22-2019, 02:18 PM
|
#2
|
Human being with feelings
Join Date: Sep 2013
Posts: 657
|
Quote:
+ ReaScript: extend GetLastTouchedFX() to support take FX [t=221165]
|
Thank you very much! Just did some preliminary testing and everything seems to work as expected. Will post an update if something crops up after I add it to a real script.
|
|
|
05-22-2019, 03:25 PM
|
#3
|
Human being with feelings
Join Date: Jan 2010
Location: Kalispell
Posts: 14,759
|
Quote:
# MIDI editor: deprecate option to not select CC events on mouse click [p=2137798]
|
Okay, now we can just click on the CC point and select it.
Also for the "Alt+LeftClick/Drag" I selected "Erase CC events" from the actions list and now I can just Alt+Click on the point and delete it.
|
|
|
05-22-2019, 06:18 PM
|
#4
|
Human being with feelings
Join Date: Sep 2013
Posts: 657
|
Justin, while testing the GetLastTouchedFX() addition I again stumbled upon an inconvenient behavior with its sibling GetFocusedFX().
As per API documentation the function "Returns [...] 0 if no FX window has focus" but it does not.
I read your post here that it should rather be called GetLastFocusedFX WhichIsStillOpen() but it doesn't return 0 even if all FX windows are closed.
Thought it would be appropriate to mention it here.
Last edited by Neutronic; 05-22-2019 at 08:08 PM.
|
|
|
05-23-2019, 05:18 AM
|
#5
|
Human being with feelings
Join Date: Oct 2007
Location: home is where the heart is
Posts: 12,110
|
While extension API is on the table, I thought it might be a good moment to mention about HWND support ( FR).
|
|
|
05-23-2019, 08:57 AM
|
#6
|
Human being with feelings
Join Date: Dec 2016
Posts: 880
|
Dear Devs
Justin and Schwa,
You two have been killing it lately with all the great new midi features. We're not worthy! We're not worthy!
|
|
|
05-24-2019, 09:55 AM
|
#7
|
Human being with feelings
Join Date: Nov 2008
Location: London, UK
Posts: 2,583
|
Lock Track Height doesn't always seem to be persistent, though I have no idea what's causing it. Sometimes it seems to forget it's state and becomes unlocked.
EDIT: It seems like the lock state is stored, but not recalled. Happens after some time, but I think also if you close and open the project. (not at studio now to check)
If a previously height-locked track acts unlocked, you can run the toggle lock action, but it doesn't lock until you toggle lock a second time.
(Separate actions for lock and unlock track height would be great, too, BTW.)
Last edited by daxliniere; 05-28-2019 at 04:46 PM.
|
|
|
05-24-2019, 10:55 AM
|
#8
|
Human being with feelings
Join Date: Apr 2016
Location: ASU`ogacihC
Posts: 3,921
|
Quote:
Originally Posted by daxliniere
Lock Track Height doesn't always seem to be persistent, though I have no idea what's causing it.
|
Heres one,.. If you call the action: 'View: Restore previous zoom level' one too many times (i.e. nothing left to restore) the locked tracks become unlocked, and 'lock track height' menu items are still checked.
|
|
|
05-24-2019, 12:52 PM
|
#9
|
Human being with feelings
Join Date: Nov 2008
Location: London, UK
Posts: 2,583
|
v5.978 release bug
Automation Item bug:
Enlarge a looped AI, then disable loop, 'end point' is still shown and you can't move automation points past it.
|
|
|
05-25-2019, 07:43 AM
|
#10
|
Human being with feelings
Join Date: Oct 2007
Location: home is where the heart is
Posts: 12,110
|
Quote:
Originally Posted by daxliniere
v5.978 release bug
Automation Item bug:
Enlarge a looped AI, then disable loop, 'end point' is still shown and you can't move automation points past it.
|
Hm, but media items practically behave the same forever, don't they?
|
|
|
05-27-2019, 03:19 PM
|
#11
|
Human being with feelings
Join Date: Nov 2008
Location: London, UK
Posts: 2,583
|
Quote:
Originally Posted by nofish
Hm, but media items practically behave the same forever, don't they?
|
Perhaps, but what is the point of extending an item if you can't use that space?
In an AI (and MIDI item), that blank space is editable whereas in an audio item you can't manually do anything with that space.
So I think they are different use cases and should act differently. An AI is more similar in form to a MIDI item than an audio item.
Also, that space is 'accessible' if you do the steps in a different order. (Disable loop then enlarge VS enlarge then disable loop.)
|
|
|
05-28-2019, 11:15 AM
|
#12
|
Human being with feelings
Join Date: Nov 2008
Location: London, UK
Posts: 2,583
|
Furthermore, if I have an audio item and I shorten it, then switch loop on, and lengthen it again, the lengthened part is not a loop. (which would actually be nice and congruent with the behaviour discussed here.)
|
|
|
Thread Tools |
|
Display Modes |
Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -7. The time now is 04:31 AM.
|