v5.50repre1 - August 8 2017

[musicbynumbers]

+ Project tabs: improved various behaviors when using background tabs [t=193849]
+ Undo: improve undo efficiency
+ VST: improve resize behavior of bridged plug-ins
+ VST: small improvement to scrollbar-sizing logic
# Automation item: fix stretching over tempo change marker [p=1872467]
# Automation items: fix transition at automation item boundaries when recording automation [p=1872432]
# Automation items: respect option to trim content behind automation items when inserting or duplicating [p=1872452]

[EvilDragon]

Originally Posted by musicbynumbers

+ VST: improve resize behavior of bridged plug-ins

It's better with NI Pro-53 now!

However I can still see the window resizing over two of my screens for like a quarter of a second or less, before it returns to its proper GUI size (when hiding/showing the keyboard in Pro-53). Enough to be noticeable.

Can it perhaps be further improved?

[EvilDragon]

It would be really nice if the sliders in AI properties window could have a fine-tune mode when holding Shift. Right now they can jump in values even with very small mouse movements (3, 4, or more units at a time, when I want precision of 1 unit). Sure we can type values, but for every fine-tune edit we might want? No thanks, it'd be much faster to just Shift+drag them.


Also, the square LFO waveform should really start at high level, not low level. All other waveforms start similarly.

[Robert Randolph]

Is it possible to fix this behaviour? (see original report:
https://forum.cockos.com/showpost.ph...6&postcount=10)



Because of this behaviour, if you're using looped pooled duplicates, it's possible to change your entire envelope by changing 1 point.

I am using AIs in production (yeah, I'm a masochist), and this actually can be quite a disaster if you have mixed looped/unlooped pooled duplicates, or just pooled duplicates.

[Robert Randolph]

Create unpooled duplicate creates extra undo step.

• Create an AI
• "Create unpooled duplicate"
• Undo

Instead of undoing the "Create unpooled duplicate" action, we are instead left with a single pooled duplicate. A second undo action is necessary to fully remove the newly created duplicate.

Expected behaviour:

Undo after "Create unpooled duplicate" removes the newly created AI entirely.

[schwa]

Originally Posted by Robert Randolph

Is it possible to fix this behaviour?

That behavior is by design. With a looped automation item, the last point in each loop iteration connects to the first point, even if those points are not at the start and end of the item. You can ensure that there is a start and end point at the automation item boundaries by gluing it prior to duplicating.

[Robert Randolph]

Gluing AIs can removes background points



A demonstation of when this matters:

• Turn on "Automation items connect to underlying envelope on right side"
• Create an AI
• Create envelope points to the left and right of the AI
• Create a point behind the AI that's lower the the AI end point values.
• Glue the AI

The points behind the AI are removed, and subsequently the envelope is changed despite only a change being made to the AI.

This happens no matter the status of the preference: "Remove points from underlying envelope when creating automation items"

Expected behaviour:

Gluing an AI should not change the background envelope, except perhaps when "Remove points from underlying envelope when creating automation items" is enabled.

[Robert Randolph]

Originally Posted by schwa

That behavior is by design. With a looped automation item, the last point in each loop iteration connects to the first point, even if those points are not at the start and end of the item. You can ensure that there is a start and end point at the automation item boundaries by gluing it prior to duplicating.

I understand, however...

https://www.youtube.com/watch?v=cDGlN6mluGA

Hopefully a reference to a cartoon from 1991 sways your opinion on the topic. If not, that's all I got.

[EvilDragon]

If it's by design it's probably not very likely to change at this point

If glueing is not wanted, perhaps a custom action to add edge points to AI could be useful instead? Then you could tweak the inside points of AI without changing the connection points to underlying envelope...

SWS/BR: Save edit cursor position, slot 01
SWS: Save time selection, slot 1
Envelope: Set time selection to automation item
Go to start of time selection
Envelope: Insert new point at current position
Go to end of time selection
Envelope: Insert new point at current position
SWS/BR: Restore edit cursor position, slot 01
SWS: Restore time selection, slot 1


Though this seems to insert the points both to underlying envelope, AND AI.

[Robert Randolph]

Originally Posted by EvilDragon

If it's by design it's probably not very likely to change at this point

If glueing is not wanted, perhaps an action to add edge points to AI could be useful instead? Then you could tweak the inside points of AI without changing the connection points to underlying envelope...

An action to add an edge points interpolated between the 2 closest points to the edge would fix the issue.... which gives me an idea.



Allows this:



It seems like it'd be useful to have actions to turn AI loop on and off separately, rather than just a toggle. It perhaps could make some custom actions more reliable.

(no clue why I called it 'interpolated' glue, since it's not. Whatever. Need caffeine.)

[schwa]

Originally Posted by Robert Randolph

An action to add an edge points interpolated between the 2 closest points to the edge would fix the issue

We can add that, no problem.

[SubbaseDnB]

havent used any of the pre-realease versions,waiting for full official version,but noticed that when using voxengo span 64bit it wont resize in the latest full official version of Reaper,is this fixed in these new versions?

[Justin]

*cough* could we all test VST resizing related stuff (and bridged VST resizing too) please? That's the reason this has gone repre1 from rc

[vitalker]

Originally Posted by musicbynumbers

+ VST: small improvement to scrollbar-sizing logic

It's broken.

[Neutronic]

Originally Posted by musicbynumbers

+ VST: small improvement to scrollbar-sizing logic

Justin, if it relates to this request then the scrollbars still overlay FX GUIs instead of appending to them. Vitalker's licecaps above illustrate the behavior very well.

[Justin]

Originally Posted by Neutronic

Justin, if it relates to this request then the scrollbars still overlay FX GUIs instead of appending to them. Vitalker's licecaps above illustrate the behavior very well.

It's not -- that line refers to the way reaper responds to VSTs that are requesting resizes themselves.

[EpicSounds]

what's with the name of this one?

[Embass]

Stretch left side: https://goo.gl/9iqXbh

Relative stretch: https://goo.gl/UF5ySC

Action Item: duplicate items: https://goo.gl/iakrzv

Insert point changes value: https://goo.gl/UdoZia

[EvilDragon]

Originally Posted by Justin

*cough* could we all test VST resizing related stuff (and bridged VST resizing too) please? That's the reason this has gone repre1 from rc

I already mentioned what I see with Pro-53, which is the only 32-bit VST that uses GUI resizing that I have.

[vitalker]

Originally Posted by Justin

It's not -- that line refers to the way reaper responds to VSTs that are requesting resizes themselves.

Watch please my video, where after double-clicking it resizes, but in a wrong way.

[EvilDragon]

Originally Posted by EpicSounds

what's with the name of this one?

REpeated PRErelease.

[Justin]

Originally Posted by EvilDragon

I already mentioned what I see with Pro-53, which is the only 32-bit VST that uses GUI resizing that I have.

Ah sorry I missed that!

That resize-big thing happens here with Kontakt bridged, too. I think it's because the plug-in is trying to resize the parent itself, which we then correct. I havent found a way to get around that (yet). Or maybe there's some other interaction which I haven't sorted... anyway.

[EvilDragon]

All good!

It's already much more usable than it was, since it returns to the proper GUI size. It's just the flickering that is a little bit annoying - and if it can be somehow alleviated, of course it'll be a good thing. If possible.

[hwhalen]

I'm installing the x64 version(s).

When I install the 5.50repre1 version my 32 bit plugins are all treated as being offline. If I rescan VSTs, they are not found.

So I reinstalled 5.40 and rescanned...all the 32bit VSTs were working fine.

Is there a new option or something else I've forgotten to do or have I done something wrong?

[Justin]

Originally Posted by hwhalen

I'm installing the x64 version(s).

When I install the 5.50repre1 version my 32 bit plugins are all treated as being offline. If I rescan VSTs, they are not found.

So I reinstalled 5.40 and rescanned...all the 32bit VSTs were working fine.

Is there a new option or something else I've forgotten to do or have I done something wrong?

Hmm is this Windows or macOS? If on Windows, did you accidentally uncheck installing bridging support?

What does 5.50rc12 do (on landoleet.org/old)?

[hwhalen]

Originally Posted by Justin

Hmm is this Windows or macOS? If on Windows, did you accidentally uncheck installing bridging support?

What does 5.50rc12 do (on landoleet.org/old)?

It's Windows 10 Pro 64 bit, I checked and bridging support is installed.
It does the same thing with 5.50rc12.

I'll try a fresh portable and see what happens.

[hwhalen]

A fresh portable of 5.50repre1 appears to work fine, I'll try to find what my problem is. Sorry to have bothered you.

[Robert Randolph]

+ VST: small improvement to scrollbar-sizing logic

So I am not sure if I understand this. I see scrollbars in other people's images, but when I resized a VST I get no scrollbars. Am I missing a setting somewhere?

---

Also this bug I reported a while ago is now fixed in 5.50: https://forum.cockos.com/showthread.php?t=190654

[Justin]

Originally Posted by Robert Randolph

+ VST: small improvement to scrollbar-sizing logic

So I am not sure if I understand this. I see scrollbars in other people's images, but when I resized a VST I get no scrollbars. Am I missing a setting somewhere?

---

Also this bug I reported a while ago is now fixed in 5.50: https://forum.cockos.com/showthread.php?t=190654

Ignore it, that changelog line is poorly named and probably does not apply to you.

[Dannii]

RePre!! Good one!

Just missed this one. I just shut down my studio for the day. I'll be back there in about 12 hours though and will give this new one a try then (if another one isn't already released by then!)

[PitchSlap]

Originally Posted by musicbynumbers

+ VST: improve resize behavior of bridged plug-ins

Working much better with Kontakt,thank you!

[Tale]

Originally Posted by Justin

*cough* could we all test VST resizing related stuff (and bridged VST resizing too) please? That's the reason this has gone repre1 from rc

Well, Arturia Farfisa V (on Win10) doesn't play well with resizing in REAPER(I mean via the resize menu option from within the plug-in), but I don't think this is new. The VST3 version has no scollbars whatsoever, and the VST2 version does have scrollbars, although the vertical scollbar is sometimes missing, and it flickers while scolling, often displaying a blank window.

Note that if you resize it down so that it fits on the screen, then you have no issues (because then it doesn't need scrollbars anyway).

[EvilDragon]

If you blow up the zoom so that it doesn't fit on the screen, it's kinda normal to expect the scrollbars, no?

[Tale]

Originally Posted by EvilDragon

If you blow up the zoom so that it doesn't fit on the screen, it's kinda normal to expect the scrollbars, no?

Yeah sure. I'm just saying that most users will likely select settings that will prevent scrollbars to begin with. Of course this might not always be possible, e.g. if the plug-in GUI is really large and doesn't have any resizing options, or if the smallest option is still too large.

[casrya]

Originally Posted by EvilDragon

If you blow up the zoom so that it doesn't fit on the screen, it's kinda normal to expect the scrollbars, no?

Yes, which is why it is a problem that the VST3 *doesn't* have any (even though the VST 2 does) when it is scaled such that it doesn't fit in the window bounds

But as Tale already said even though VTS2 has scrolling it flickers like crazy so is not a good option either unless you really need the scrolling to get a decent size GUI. Fortunately for me I can use the Arturia instruments without scrolling but it would be nice to have

[Kundalinguist]

Looking good, RPR.

[EvilDragon]

Well here's a person that didn't post here in a while!

[Kundalinguist]

Originally Posted by EvilDragon

Well here's a person that didn't post here in a while!

Hey ED. I was trying to bring down my "post to years registered" ratio. I don't want to hog this thread with a diversion, but I did want to say hello to those who remember me.

P.S. Reaper has been working great for me in Rewire mode to keep some older 32bit VSTs and VSTis alive. So yeah, YAY Reaper.

[Dannii]

This pre works the best by far for resizing to date. Kontakt in dedicated process with bridged GUI resizes fine here now apart from the full screen white flashing whilst dragging to resize. I can happily live with that until a complete fix is found though.

All my other resizable plugins seem to work well so far too.

Thumbs up from me.

Originally Posted by Kundalinguist

Looking good, RPR.

Welcome back stranger.

[EpicSounds]

only had a quick test but I gotta say I love the recent changes to AI LFO. Much easier to use now.

Thank you!