v5.971 - February 25 2019

vitalker · 02-25-2019, 11:10 AM

v5.971 - February 25 2019

+ ARA: fix adjusting plugin playback to project tempo when media item start position is not zero [p=2099289]
+ ARA: properly account for timing offset in certain situations [t=217606]
+ Dockers: improve dock/undock focused window action (always affect docked window before the docker that contains it, set focus)
+ JSFX: fix gfx_a2 default when drawing into secondary buffers [p=2099185]
+ ReaScript: gfx_a2 is always reset to 1 on each gfx frame
+ ReaScript: prevent possible crash when scripts terminating scripts [p=2090998]
+ ReaTune: fix per-take FX manual mode timing [t=217577]
+ ReaTune: fix take FX manual mode inconsistencies with global project offset
+ Video: fix YV12/YUY2 text rendering alignment with certain fonts/characters
+ Video: allow drawing text with larger font sizes (up to 700pt)
+ Video: improve playback performance with looped playback [p=2097954]

Generated by X-Raym's REAPER ChangeLog to BBCode

playtimer · 02-25-2019, 11:53 AM

Quote:

+ ARA: fix adjusting plugin playback to project tempo when media item start position is not zero [p=2099289]
+ ARA: properly account for timing offset in certain situations [t=217606

Awesome! Thanks for quick fixes

lexaproductions · 02-25-2019, 03:47 PM

Quote:

Originally Posted by vitalker

v5.971 - February 25 2019[*]+ ReaScript: prevent possible crash when scripts terminating scripts [p=2090998]

Thanks! It seems to be working now

vectorwarrior · 02-25-2019, 04:35 PM

Quote:

Originally Posted by vitalker

+ Video: improve playback performance with looped playback [p=2097954]

Hmm, by tweaking some parameters I've managed to get short looping videos to work ooookay, better than 5.97, but it still feels jankier (more underruns) than before the performance tweaks were added.

I'll keep trucking along, perhaps I'm working on a bad video right now.

musicbynumbers · 02-25-2019, 04:51 PM

Quote:

Originally Posted by vectorwarrior

Hmm, by tweaking some parameters I've managed to get short looping videos to work ooookay, better than 5.97, but it still feels jankier (more underruns) than before the performance tweaks were added.

I'll keep trucking along, perhaps I'm working on a bad video right now.

I managed to get short 2 second loops working by bringing cache down to 0.1 seconds.

I think it skips the first frame on loop but it's not bad

There's probably other issues from doing this that I'll have to see if they come up.

Justin
If this is not fixable (since newcomers who end up occasionally doing short loops will see it as broken not knowing about the video options potentially) then what about having an adaptive option for video cache that shrinks/expands the cache depending on the loop size?

D Rocks · 02-25-2019, 04:54 PM

Dam you must have broken tons of keyboards with the enormeous quantity of code lines that you write

thank you very much

Justin · 02-25-2019, 05:03 PM

Quote:

Originally Posted by musicbynumbers

I managed to get short 2 second loops working by bringing cache down to 0.1 seconds.

I think it skips the first frame on loop but it's not bad

There's probably other issues from doing this that I'll have to see if they come up.

Justin
If this is not fixable (since newcomers who end up occasionally doing short loops will see it as broken not knowing about the video options potentially) then what about having an adaptive option for video cache that shrinks/expands the cache depending on the loop size?

Hmm 2 second time-selection loops should work fine with a 1s cache. In fact it should work better with the longer cache. Or did you mean looped video items?

vectorwarrior · 02-25-2019, 05:12 PM

Quote:

Originally Posted by Justin

Hmm 2 second time-selection loops should work fine with a 1s cache. In fact it should work better with the longer cache. Or did you mean looped video items?

Yeah, I'm getting better results with a longer cache for these scenarios.

Dimson · 02-26-2019, 12:03 AM

When manually setting values, Event Filter loses notes.
I think this is due to the internal timing of the Reaper. The video shows that the notes are slightly shifted relative to the grid and the program does not allow you to set the note strictly on the grid.
But in general, the behavior returned as in version 5,963

musicbynumbers · 02-26-2019, 03:14 AM

Quote:

Originally Posted by Justin

Hmm 2 second time-selection loops should work fine with a 1s cache. In fact it should work better with the longer cache. Or did you mean looped video items?

That's strange then. I thought that too. A larger cache should have buffered all of those 2 seconds right.

It's when I loop reaper's arrange (not a looped video) for less than 2 seconds that I found only 0.1s cache worked and even then the first frame at the start of the arrange page loop was often stuck for that first frame or so. But it was pretty smooth in total.

For game stuff you often end up doing short loops like this when working on sound to animation.

I've pasted the video compression settings below if that helps. VLC version is 3.03

Length: 5:12.767
Video: 768x1024@60.03fps, Aspect=1.00, Decoding format=I420/YV12
Audio: 44100Hz 2ch 32bps

Using VLC decoder (v3.0.x)
Video: 768x1024, h264, 60.03fps
Audio: 44100hz, 32bps, 2ch, mp4a

Loaded from: C:\Program Files\VideoLAN\VLC

Reno.thestraws · 02-26-2019, 08:49 AM

Quote:

+ Dockers: improve dock/undock focused window action (always affect docked window before the docker that contains it, set focus)

Thank you JUSTIN!

Now we can : https://drive.google.com/open?id=173...PIXYvCFICRzW2D

Meo-Ada Mespotine · 02-26-2019, 10:56 AM

@Justin
I would love to use the opportunity to say thank you for you incredible work on the video-processor-stuff for 5.97+
The more I browsed through the fantastic docs, the more I thought "Wow, cool...this makes a lot possible!"

One final thing though, is there a way to get the Video Window-HWND on MacOS/Linux, when someone opened another window called "Video Window", like in a ReaScript, for example?
I could use the classname on Windows for getting it, but this isn't working on Mac/Linux.
With this problem solved, doing stable mouse-clickable guis in the Video Window would be possible completely

lou latch · 02-27-2019, 04:29 AM

I'm having a problem with some VST-plugins (AU version doesn't work either) in this build:

i can't use the plug-ins ''bx_digital V3'' and ''bx_digital V3 mix'' and ''bx_XL V2'' from Plugin Alliance anymore.

When loading projects (created with reaper 5.963/64 rev ca35f9) i get a ''Project Load Warning'': The following effects were in the project file and are not available. Reaper will keep... etc.

In the MCP they show red, in the FX-chain window it says ''The following effect plug-in could not be loaded:''

After doing
Preferences / Plugins / VST: Clear cache/re-scan
the plugins don't show up in the FX Browser anymore.
This is not the case with other plug-ins from the same company i have installed: bx_cleansweep V2, bx_dynEQ V2, bx_saturator V2 - these load and work as expected.

After going back to 5.963 and doing the ''Clear cache/re-scan'' everything works as before.

This is on mac os Sierra, 64bit.

If i can provide further info let me know. If i should test with a specific release in between, let me also know. Unfortunately i don't have time today to try them all, for now i reverted to reaper 5.963.

Thanks for reading.

europa_man · 03-01-2019, 08:25 AM

Quote:

Originally Posted by vitalker

v5.971 - February 25 2019

+ ARA: fix adjusting plugin playback to project tempo when media item start position is not zero [p=2099289]
+ ARA: properly account for timing offset in certain situations [t=217606]
+ Dockers: improve dock/undock focused window action (always affect docked window before the docker that contains it, set focus)
+ JSFX: fix gfx_a2 default when drawing into secondary buffers [p=2099185]
+ ReaScript: gfx_a2 is always reset to 1 on each gfx frame
+ ReaScript: prevent possible crash when scripts terminating scripts [p=2090998]
+ ReaTune: fix per-take FX manual mode timing [t=217577]
+ ReaTune: fix take FX manual mode inconsistencies with global project offset
+ Video: fix YV12/YUY2 text rendering alignment with certain fonts/characters
+ Video: allow drawing text with larger font sizes (up to 700pt)
+ Video: improve playback performance with looped playback [p=2097954]

Generated by X-Raym's REAPER ChangeLog to BBCode

I installed 5.97 and spend a few hours getting Melodyne working and then a few days later installed 5.971 and everything went to pieces.
All of a sudden Reaper was freezing up and taking like 5 minutes to load a simple project. It froze when I tried to Insert a new track.
Reboot after reboot.
I've never experienced this before?
I'm back to 5.965 again as a portable install.
I had to reinstall everything.
I'm spending hours dealing with this stuff. PAINFUL.
My updates have always gone smoothly before.

Rock solid is GONE in this latest version for me???

mabian · 03-01-2019, 08:36 AM

Quote:

Originally Posted by europa_man

I installed 5.97 and spend a few hours getting Melodyne working and then a few days later installed 5.971 and everything went to pieces.
All of a sudden Reaper was freezing up and taking like 5 minutes to load a simple project. It froze when I tried to Insert a new track.
Reboot after reboot.
I've never experienced this before?
I'm back to 5.965 again as a portable install.
I had to reinstall everything.
I'm spending hours dealing with this stuff. PAINFUL.
My updates have always gone smoothly before.

Rock solid is GONE in this latest version for me???

To be fair, this is the first Reaper update I can remember in which there's such tight integration with a third party product (Melodyne).
It would be interesting to see if other ARA hosts suffer from similar issues with Melodyne 4.2.1...

- Mario

Judders · 03-01-2019, 08:37 AM

Quote:

Originally Posted by lou latch

I'm having a problem with some VST-plugins in this build:

i can't use the plug-ins ''bx_digital V3'' and ''bx_digital V3 mix'' and ''bx_XL V2'' from Plugin Alliance anymore.

When loading projects (created with reaper 5.963/64 rev ca35f9) i get a ''Project Load Warning'': The following effects were in the project file and are not available. Reaper will keep... etc.

In the MCP they show red, in the FX-chain window it says ''The following effect plug-in could not be loaded:''

After doing
Preferences / Plugins / VST: Clear cache/re-scan
the plugins don't show up in the FX Browser anymore.
This is not the case with other plug-ins from the same company i have installed: bx_cleansweep V2, bx_dynEQ V2, bx_saturator V2 - these load and work as expected.

After going back to 5.963 and doing the ''Clear cache/re-scan'' everything works as before.

This is on mac (mojave) 64bit.

If i can provide further info let me know. If i should test with a specific release in between, let me also know. Unfortunately i don't have time today to try them all, for now i reverted to reaper 5.963.

Thanks for reading.

I've used all three of those plugins on v5.971/64 rev 2589a3 without issue on High Sierra.

frareinif · 03-02-2019, 07:41 AM

First day with 5.971, I notice stuttering on rendering, even after reboot. Playback needs half a second to start after pressing [SPACE]...

airon · 03-04-2019, 05:57 AM

Sidenote for the recent ReaComp improvements, the threshold control and how it reacts to incoming midi control: there's a serious control problem, and as a result I almost never use ReaComp in paid work.

The details are here (posted appropriately in the FR section):
https://forum.cockos.com/showthread.php?t=217986

4johnny · 03-05-2019, 09:27 AM

ARA worked the first day I inserted on a vocal track. Now when I open the same project, there is no audio on the vocal track where Melodyne was inserted. Once I disable the Melodyne plugin, I hear audio. I have re-installed both melodyne and Reaper and re-inserted the plugin on a vocal track and still no audio when Melodyne is active.

I also see an 'ARA save' bar pop up constantly, locking up my PC for a few seconds at a time.

europa_man · 03-08-2019, 07:26 AM

Quote:

Originally Posted by europa_man

I installed 5.97 and spend a few hours getting Melodyne working and then a few days later installed 5.971 and everything went to pieces.
All of a sudden Reaper was freezing up and taking like 5 minutes to load a simple project. It froze when I tried to Insert a new track.
Reboot after reboot.
I've never experienced this before?
I'm back to 5.965 again as a portable install.
I had to reinstall everything.
I'm spending hours dealing with this stuff. PAINFUL.
My updates have always gone smoothly before.

Rock solid is GONE in this latest version for me???

Friday - March 8th:
I just installed the latest version this morning - 5.972 as a portable install and everything seems to be working extremely well again.
Thank heavens!
Took about 10 minutes - went smoothly.

Plugins seem to be recognized, SWS installed again, my confirmation Imported and license.
Project loaded right up quickly.

Will be using over the weekend. Happy again.

lou latch · 03-10-2019, 05:17 AM

Quote:

Originally Posted by lou latch

I'm having a problem with some VST-plugins in this build:

i can't use the plug-ins ''bx_digital V3'' and ''bx_digital V3 mix'' and ''bx_XL V2'' from Plugin Alliance anymore.

... (post #13)

Actually, this is on OS Sierra (not Mojave) - sorry, i mixed it up with my laptop's OS.

Unfortunately the problem is still present in 5.972, REAPER doesn't find the plugins. Reinstalling the plugins doesn't help.

Going back to 5.963 works.

Justin · 03-11-2019, 06:49 AM

Quote:

Originally Posted by lou latch

Actually, this is on OS Sierra (not Mojave) - sorry, i mixed it up with my laptop's OS.

Unfortunately the problem is still present in 5.972, REAPER doesn't find the plugins. Reinstalling the plugins doesn't help.

Going back to 5.963 works.

If you use this build:

http://reaper.fm/files/5.x/reaper5972-oldsdk_x86_64.dmg

Do the plug-ins work in that build?

lou latch · 03-11-2019, 02:46 PM

Quote:

Originally Posted by Justin

If you use this build:

http://reaper.fm/files/5.x/reaper5972-oldsdk_x86_64.dmg

Do the plug-ins work in that build?

Thank you very much Justin, yes old sdk seems to work fine (could only test with a small project today, but i think if one plugin works, the others will too. I can't test properly tomorrow, will post an update on wednesday).

I guess this means the time has come to update my studio computer's os...

lou latch · 03-13-2019, 02:02 AM

Quote:

Originally Posted by Justin

If you use this build:

http://reaper.fm/files/5.x/reaper5972-oldsdk_x86_64.dmg

Do the plug-ins work in that build?

Quick update: as expected, with the old sdk build the plugins are found and load as usual. Thanks, again!

So, this means i will be fine downloading the newest rc 'oldsdk' version each time i want to install the up to date Reaper version, right?
And with newer OS the official release should work?

Judders · 03-13-2019, 02:10 AM

Quote:

Originally Posted by lou latch

Quick update: as expected, with the old sdk build the plugins are found and load as usual. Thanks, again!

So, this means i will be fine downloading the newest rc 'oldsdk' version each time i want to install the up to date Reaper version, right?
And with newer OS the official release should work?

As I said, I'm on High Sierra and have been using all 3 of those plugins in VST3 format without issue.

lou latch · 03-13-2019, 02:26 AM

Quote:

Originally Posted by Judders

As I said, I'm on High Sierra and have been using all 3 of those plugins in VST3 format without issue.

Yes, thanks for that info, i saw your reply last time. Good for you you didn't have a problem :-)
Maybe this means that some critical change has occurred between Sierra (my OS) and High Sierra (your OS).

I'm sure Justin knows about this, but i don't even know what sdk stands for (although i think i read about it in some pre-release thread).

If i update my OS i would prefer going to Mojave directly, so that i don't have to update again for a longer time.

For now i'm happy using the olsdk versions, or is there any bigger downside to it?

Judders · 03-13-2019, 02:32 AM

Quote:

Originally Posted by lou latch

Yes, thanks for that info, i saw your reply last time. Good for you you didn't have a problem :-)
Maybe this means that some critical change has occurred between Sierra (my OS) and High Sierra (your OS).

I'm sure Justin knows about this, but i don't even know what sdk stands for (although i think i read about it in some pre-release thread).

If i update my OS i would prefer going to Mojave directly, so that i don't have to update again for a longer time.

For now i'm happy using the olsdk versions, or is there any bigger downside to it?

I have no clue, sorry!

I'm still holding off on Mojave until there is a definite all-clear from every plugin developer in my fx folder.

Here's a list of compatibility statements from plugin developers:
https://www.pro-tools-expert.com/pro...?view_2_page=1

lou latch · 03-13-2019, 02:41 AM

Quote:

Originally Posted by Judders

I have no clue, sorry!

I'm still holding off on Mojave until there is a definite all-clear from every plugin developer in my fx folder.

Here's a list of compatibility statements from plugin developers:
https://www.pro-tools-expert.com/pro...?view_2_page=1

...that's why i'm still on Sierra, it rarely happens that everything just works after an OS update. Also besides from Plugins.

lou latch · 03-30-2019, 02:23 AM

Quote:

Originally Posted by lou latch

...And with newer OS the official release should work?

To answer my own question, or in case somebody runs into similar problems:

Installed Mojave and everything is fine with the regular Reaper Version.