Is any work being done on the ARM64 version on M1 Macs that allow for x86 VST3 instruments? They only show up under the regular VSTi lists, such as all the Artuira V Collection.
And is the separate "reaper_host_x86_64" thing going to always load from now on, or is this a temporary thing until things are worked out?
I know the ARM64 version is still in beta, so this is more just of a inquiry. REAPER runs fine under x86 mode via Rosetta 2...complete with the VST3i instruments.
If you go to preferences/VST and click the "re-scan" button, you can pick your x86_64 VST3 plug-ins and try to re-scan them, they should now scan in 6.30.
Well tohubohu, you shoud compare "apples to apples" as saying goes ... so you should have installed the same versions of plugins for both Reapers (and Reapers also the same, 64bit or 32bit both).
But while reading another posts here, maybe the difference is in bridging/firewalling the VST3i in v6.30.
If you go to preferences/VST and click the "re-scan" button, you can pick your x86_64 VST3 plug-ins and try to re-scan them, they should now scan in 6.30.
Didn't even think about doing that! That worked. It's one of those "of course, why didn't I think of that" moments.
I suggest that you check the operation of actions with "last touched parameters" or "last touched FX" when active Loudness Meter Peak/RMS/LUFS.
I'm watching:
If Loudness Meter Peak/RMS/LUFS active in monitoring FX, action FX: Show parameter modulation/link for last touched FX parameter - does not work.
Show/hide track envelope for last touched FX parameter - does not work.
I suggest that you check the operation of actions with "last touched parameters" or "last touched FX" when active Loudness Meter Peak/RMS/LUFS.
I'm watching:
If Loudness Meter Peak/RMS/LUFS active in monitoring FX, action FX: Show parameter modulation/link for last touched FX parameter - does not work.
Hi, I found a small regression in Tuner in this release. Label with note name has now a solid black background that covers fine tune indicator.
Hmm the change of putting the fine indicator behind the text rather than over it was intentional, but the text having a background is unintentional (and only on Windows, oops). Fixing!
local envelope = reaper.GetSelectedEnvelope(0)
local p, t, v, shape, tension, s = reaper.GetEnvelopePointEx(envelope, 0, 1)
reaper.SetEnvelopePointEx(envelope, 0, 1, 7, v, shape, tension, true, true)
reaper.Envelope_SortPointsEx(envelope, 0)
Hm I think there is something missing in your script, like if you want to move to start of time selection you need to get the time selection first. Also you are not getting the selected envelope point.
Code:
local envelope = reaper.GetSelectedEnvelope(0)
local count = reaper.CountEnvelopePoints( envelope )
local firstsel_index = 0
local p, t, v, shape, tension, sel = nil
for i = 0, count - 1 do
p, t, v, shape, tension, sel = reaper.GetEnvelopePointEx(envelope, -1, i)
if sel then
firstsel_index = i
break
end
end
local start, fim = reaper.GetSet_LoopTimeRange(false, false, 0, 0, false)
reaper.SetEnvelopePointEx(envelope, -1, firstsel_index, start, v, shape, tension, true, false)
For working inside automation items I havent mess much but this should get you in the way. Oh also I would avoind giving no sortin true in set envelopepoint ex as you can get strange results like
Hm I think there is something missing in your script, like if you want to move to start of time selection you need to get the time selection first. Also you are not getting the selected envelope point.
Code:
local envelope = reaper.GetSelectedEnvelope(0)
local count = reaper.CountEnvelopePoints( envelope )
local firstsel_index = 0
local p, t, v, shape, tension, sel = nil
for i = 0, count - 1 do
p, t, v, shape, tension, sel = reaper.GetEnvelopePointEx(envelope, -1, i)
if sel then
firstsel_index = i
break
end
end
local start, fim = reaper.GetSet_LoopTimeRange(false, false, 0, 0, false)
reaper.SetEnvelopePointEx(envelope, -1, firstsel_index, start, v, shape, tension, true, false)
For working inside automation items I havent mess much but this should get you in the way. Oh also I would avoind giving no sortin true in set envelopepoint ex as you can get strange results like
I say to the envelope point, move to 7th second...it doesn't. It goes where it pleases instead.
I don't know if I'm the only one but when rendering, the "Complete, Elapsed and Remaining" text starts shaking left to right when updating the values,and I feel it doesn't look "good" or "finished"
Edit: just to clarify, all my ".vst3" files are in a different location than "Common Files/VST3". They are in a different local folder, which in turn is part of the material I have backed up to the cloud.
Last edited by javiramallo; 07-06-2021 at 10:08 AM.
Hey devs here a feature request to the render stats.
it is for giving a log of the times/amount of the clips. As reaper seems to already be keeping track of where the render clipped. Would be nice to give as a list to the user.
Optionally and even cooler would be to add markers at the list time with the amount of clip in the name.
Dear Reaper devs, the addition of the loudness meters and tools is really great. Like, better than Izotope Insight 2 great when embedded in the MCP, all the good info is easily available at all times...without having to open the plugin window. I just wanted to say a big thank you.
Linear Mode
