|
|
|
05-16-2019, 02:40 AM
|
#1
|
Human being with feelings
Join Date: Oct 2017
Location: Black Forest
Posts: 5,067
|
v5.978+dev0515 - May 15 2019
v5.978+dev0515 - May 15 2019
- + Notation editor: draw slurs attached to the top or bottom of a chord
- + ReaScript: support opening files with spaces in the filename in external editors [t=219345]
- + Reascript: for automation items, CountEnvelopePointsEx, GetEnvelopePointEx, SetEnvelopePointEx, and DeleteEnvelopePointEx all use point index based on one full loop iteration (see documentation)
- # Global keyboard shortcuts: treat ReaScript/JSFX graphics windows as text fields [p=2134589]
# Removed multi-tremolo support (sorry bFooz)
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-16-2019, 02:44 AM
|
#2
|
Human being with feelings
Join Date: Oct 2017
Location: Black Forest
Posts: 5,067
|
Quote:
Originally Posted by _Stevie_
v5.978+dev0515 - May 15 2019
[*] # Global keyboard shortcuts: treat ReaScript/JSFX graphics windows as text fields [ p=2134589]
|
Works wonderfully! Thank you so much
|
|
|
05-16-2019, 02:52 AM
|
#3
|
Human being with feelings
Join Date: Jun 2015
Posts: 685
|
Quote:
Originally Posted by _Stevie_
[*] + ReaScript: support opening files with spaces in the filename in external editors [ t=219345]
|
Ahh, thanks!
Regarding hotkeys ignoring text fields, windows like Transient Detection Settings pass through hotkeys. So if you have actions bound to the numpad keys for example, and try to manually input values, those actions are inadvertently triggered.
EDIT: I went through all the "..." menu windows, but "Transient detection sensitivity/threshold: Adjust..." was the only one that let through hotkeys when editing text fields
Last edited by Sju; 05-16-2019 at 03:02 AM.
|
|
|
05-16-2019, 03:10 AM
|
#4
|
Human being with feelings
Join Date: Nov 2010
Posts: 2,436
|
Quote:
Originally Posted by _Stevie_
v5.978+dev0515 - May 15 2019[*]+ Reascript: for automation items, CountEnvelopePointsEx, GetEnvelopePointEx, SetEnvelopePointEx, and DeleteEnvelopePointEx all use point index based on one full loop iteration (see documentation)
|
Awesome - one problem only - GetEnvelopePointEx() always returns false for selectedOutOptional.
I presume this is because looped AI can have different point selection per iteration so this function now may break old scripts.
Thinking out loud, I think the most elegant solution would be just one function that translates old functions point id to single-iteration point id. Or yet another Ex2 set of these API functions? Or both?
I think having both translation function and Ex2 functions should cover it all and it will also keep old scripts working?
Last edited by Breeder; 05-16-2019 at 03:28 AM.
|
|
|
05-16-2019, 03:44 AM
|
#5
|
Human being with feelings
Join Date: Oct 2010
Location: Charleston, SC
Posts: 12,792
|
Quote:
Originally Posted by _Stevie_
v5.978+dev0515 - May 15 2019
- + ReaScript: support opening files with spaces in the filename in external editors [t=219345]
|
Fixed ! Thanks so much. Devs on to infinity.
|
|
|
05-16-2019, 05:45 AM
|
#6
|
Human being with feelings
Join Date: Aug 2015
Posts: 3,672
|
Quote:
Originally Posted by _Stevie_
v5.978+dev0515 - May 15 2019
[list][*]+ Notation editor: draw slurs attached to the top or bottom of a chord
|
looks good to me, guys
|
|
|
05-16-2019, 06:01 AM
|
#7
|
Administrator
Join Date: Mar 2007
Location: NY
Posts: 15,821
|
that's not a... chord
|
|
|
05-16-2019, 06:59 AM
|
#8
|
Human being with feelings
Join Date: Jun 2009
Location: Croatia
Posts: 24,798
|
Awesome 10000th post, schwa!
|
|
|
05-16-2019, 07:12 AM
|
#9
|
Human being with feelings
Join Date: Oct 2010
Location: Charleston, SC
Posts: 12,792
|
|
|
|
05-16-2019, 07:21 AM
|
#10
|
Human being with feelings
Join Date: Aug 2015
Posts: 3,672
|
haha. and now you know why i don't beta test the notation editor.
|
|
|
05-16-2019, 07:33 AM
|
#11
|
Human being with feelings
Join Date: Oct 2017
Location: Black Forest
Posts: 5,067
|
LOLz
|
|
|
05-16-2019, 08:35 AM
|
#12
|
Human being with feelings
Join Date: Jul 2010
Location: Slovakia
Posts: 2,588
|
Quote:
Originally Posted by mccrabney
looks good to me, guys
|
And no slur.
But the feature works well with slurs and chords.
mccrabney - what's that text? Does not look like a standard text event judging by its font size.
schwa - notice how in some cases the stem overflows the beam. Looks funny.
Last edited by bFooz; 05-16-2019 at 08:40 AM.
|
|
|
05-16-2019, 08:59 AM
|
#13
|
Human being with feelings
Join Date: Aug 2015
Posts: 3,672
|
sorry, bfooz and others - it was a joke. "slur" can refer to a disparaging term used for arbitrary ethnic groups. "honky" is one such term for white skinned people, among whom i am counted. i amused myself with the idea that DAW software would be programmed to launch slurs at its users.
i can't resist trying to make life a little more surreal.
carry on with your noble works.
|
|
|
05-16-2019, 09:37 AM
|
#14
|
Human being with feelings
Join Date: Jun 2009
Location: Croatia
Posts: 24,798
|
Sadly the impact of the joke is completely demolished when you have to explain it.
|
|
|
05-16-2019, 09:39 AM
|
#15
|
Human being with feelings
Join Date: Oct 2007
Location: home is where the heart is
Posts: 12,109
|
Quote:
v5.977+dev0509 - May 9 2019
+ API: skip hidden automatic edge attachment points when counting/getting/setting points in automation items
|
Maybe this broke (or got changed?) in this version?
dev0509 (correct imo):
same project in dev0515:
(Attach to underlying env. on both sides enabled + loop enabled, shows one loop iteration)
Code:
function msg(m)
return reaper.ShowConsoleMsg(tostring(m) .. "\n")
end
track = reaper.GetTrack(0,0)
env = reaper.GetTrackEnvelope( track, 0 )
ptCnt_underlEnv = reaper.CountEnvelopePointsEx(env, -1)
ptCnt_AI1 = reaper.CountEnvelopePointsEx(env, 0)
pointsTotal = ptCnt_underlEnv + ptCnt_AI1
reaper.ClearConsole()
msg("Points in underlEnv: " .. ptCnt_underlEnv)
msg("Points in AI1: " .. ptCnt_AI1)
msg("points total: " .. pointsTotal)
edit:
To clarify, I'm wondering about point count in underl. env., point count in AI seems ok.
Maybe the phantom points came back?
Last edited by nofish; 05-16-2019 at 09:48 AM.
|
|
|
05-16-2019, 09:45 AM
|
#16
|
Human being with feelings
Join Date: Jan 2014
Posts: 5,220
|
I thought it meant, "play like a 1930's upright piano in a seedy saloon after 4 tipples of rye".
|
|
|
05-16-2019, 09:58 AM
|
#17
|
Administrator
Join Date: Mar 2007
Location: NY
Posts: 15,821
|
Quote:
Originally Posted by nofish
Maybe this broke (or got changed?) in this version?
|
Oops! Re-fixed for the next build :/
|
|
|
05-16-2019, 11:03 AM
|
#18
|
Human being with feelings
Join Date: Oct 2007
Location: home is where the heart is
Posts: 12,109
|
Quote:
Originally Posted by schwa
Oops! Re-fixed for the next build :/
|
Thanks!
Adding to the AI API change brainstorming - while it certainly eases some things (when it comes to looped AIs) I think it also may make it harder to work with current visible points, as this API change now also catches the hidden points.
As one example (which I'm working on currently):
https://i.imgur.com/8ywrk46.gif
This worked before but now breaks as it also iterates through the invisible points (which we'd now have to check ourselves).
My idea would be something like this:
- count/get/set etc. all points as before
- adding two additional bool to AI envelope points:
- isInSource
- isVisible
So we could handle all cases arccodingly.
edit:
Not shown in the gif, but this and similar actions should of course also work not only for the source but all loop iterations (if the points are visible), so this would be another pro argument for a way to getting not only the points in the source (otherwise we'd have to 'construct' the points in the iterations ourselves) but all currently visible points as it was before I think.
Last edited by nofish; 05-16-2019 at 04:06 PM.
|
|
|
05-16-2019, 11:18 AM
|
#19
|
-blänk-
Join Date: Jun 2008
Posts: 11,359
|
Sorry about it, but I think the discussion about visuals of events in the piano roll can't be over yet.
With 0513 you tweaked the display of track/item color modes. While it did increase the visibility of selection of events, there has been a regression in terms of recognizability to which track (or item) an event belongs. There seems to be steps in the brightness an event in the Piano Roll can be displayed.
Here are two tracks which differ quite a lot in terms of brightness in the TCP. Each track has an unselected note and a few CC (in secondary items, to have equal circumstances for both tracks). Can you tell which note and which CC does belong to which track?
Ok, the MIDI display in the arrange view gives it away, but that isn't of much help in real situations...
This was no problem in earlier versions of Reaper, track colors were pretty faithfully displayed on unselected notes.
Another one:
Using brightness (almost) alone to indicate selection creates a problem which the next picture shows: Similar situation with slightly tweaked brightness. Tell me real quick, which note is selected?
While this post concentrates on track/item colors and notes, I run into the same problem creating a colormap with the goal to have event channels clearly distinguishable and of course I also want to know at a glance what is selected. I can't rely on brightness, because a selected event on one channel may look exactly like an unselected event on another channel. The very slight growth when selected just doesn't do the trick enough. Finding 16 different enough colors is already almost impossible, at the moment I kinda need to find 32 of them.
TLDR: Please, try to find some additional indication for event selection, like a border, or a change in shape.
|
|
|
05-16-2019, 01:13 PM
|
#20
|
Human being with feelings
Join Date: Jan 2007
Posts: 310
|
Quote:
Originally Posted by mccrabney
looks good to me, guys
|
Tears shooting from my eyes as I laughed for 3 minutes...
|
|
|
05-16-2019, 02:22 PM
|
#21
|
Human being with feelings
Join Date: Jan 2010
Posts: 201
|
Did I just walk into an episode of 30 Rock
|
|
|
05-16-2019, 02:26 PM
|
#22
|
Human being with feelings
Join Date: Jan 2007
Posts: 310
|
Quote:
Originally Posted by poplomop
Did I just walk into an episode of 30 Rock
|
You have to start on post #6...
|
|
|
05-16-2019, 03:44 PM
|
#23
|
Human being with feelings
Join Date: Jan 2010
Location: Kalispell
Posts: 14,759
|
Quote:
Originally Posted by EvilDragon
Sadly the impact of the joke is completely demolished when you have to explain it.
|
I'm sorry ED, I just couldn't resist, because I understood him perfectly.
|
|
|
05-16-2019, 05:01 PM
|
#24
|
Human being with feelings
Join Date: Nov 2010
Posts: 2,436
|
Quote:
Originally Posted by poplomop
Did I just walk into an episode of 30 Rock
|
Best show ever!
|
|
|
05-16-2019, 05:05 PM
|
#25
|
Human being with feelings
Join Date: Apr 2013
Location: France
Posts: 9,900
|
Quote:
+ ReaScript: support opening files with spaces in the filename in external editors [t=219345]
|
Finally Bug was here since the introduction of this feature.
|
|
|
05-17-2019, 02:39 AM
|
#26
|
Human being with feelings
Join Date: Nov 2010
Posts: 2,436
|
Quote:
Originally Posted by schwa
Oops! Re-fixed for the next build :/
|
Man, these AI are tough!
Envelope_Evaluate() is a terrific function, but it's more real-time-playback related and that is obvious now with AI.
Envelope_Evaluate() was used by extension developers and scripters to determine value at any given position. Now that we have both AI and underlying envelope it is not reliable anymore in a sense that we can't differentiate between values on underlying envelope and values in AI items or values in overlapping AI items.
Would it be too much to ask for API that lets us determine visible value at any given time position in underlying envelope or a specific AI? So we can determine both the final-outcome-value and the value which is drawn at a specific AI/underlying envelope?
|
|
|
05-17-2019, 06:04 AM
|
#27
|
Human being with feelings
Join Date: Jul 2009
Posts: 3,714
|
Muted CCs appear to block automation curves that connect surrounding unmuted CCs, and also change the color of the fill below the curve.
I suggest that muted CCs should instead be drawn as isolated lollipops without any automation curves, and should not affect the curves connecting surrounding unmuted CCs.
|
|
|
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 01:13 AM.
|