KVR Audio

Hank the Knife · Post by **Hank the Knife** » Sun Aug 16, 2015 1:53 am

Likewise; aciddose, thanks again for all the good work. I am really impressed by Reaper, I must say

Chris-S · Post by **Chris-S** » Mon Aug 17, 2015 9:44 am

Today I updated to Reaper5.

So far all works well.

Some little bug (on Win7):

The JS masterlimiter shows label "Look Ahead (és)" instead of "Look Ahead (ns)".
Same for label "Attack (és)".

Chris

EvilDragon · Post by **EvilDragon** » Mon Aug 17, 2015 9:46 am

You can easily edit that yourself in the JS script

Hardly classifies as a bug. It's supposed to show the mu symbol.

Chris-S · Post by **Chris-S** » Mon Aug 17, 2015 12:50 pm

Done. Changed it to "ns" (as it was in V4). But you are right, that it probably should be the mü symbol.
But it's not possible to enter special chars in the JS editor.

Ingonator · Post by **Ingonator** » Mon Aug 17, 2015 3:07 pm

Just installed the full version of Reaper 5 and was not aware that you have to pay an upgrade price if you have a Rweaper 4.x license.

As i got a few other major DAWs (e.g. Cubase 8, Live 9 ad Bitwig) and recently used Reaper mostly for plugin testing purposes (e.g. for Waldorf plugins) i do not think i'll purchase the upgrade and will stay with 4.78 after the demo/trial period for v5 expired.

EvilDragon · Post by **EvilDragon** » Mon Aug 17, 2015 3:12 pm

Chris-S wrote: But it's not possible to enter special chars in the JS editor.

Wait... this used to work in v4 just fine. I distinctly remember μs working in JS plugins. I guess it's a regression and Cockos needs to be informed of it.

EDIT: It's the encoding of the text file. It defaults to ANSI. If you convert the encoding to UTF-8, and then add μs instead of és, it is going to work just fine!

Ingonator wrote:Just installed the full version of Reaper 5 and was not aware that you have to pay an upgrade price if you have a Rweaper 4.x license.

No, you don't need to do that. If you have a 4.x license, you're good to go till 5.99. I had a 3.x license so I needed to upgrade.

Ingonator · Post by **Ingonator** » Mon Aug 17, 2015 3:20 pm

EvilDragon wrote:
Chris-S wrote: But it's not possible to enter special chars in the JS editor.
Wait... this used to work in v4 just fine. I distinctly remember μs working in JS plugins. I guess it's a regression and Cockos needs to be informed of it.

Ingonator wrote:Just installed the full version of Reaper 5 and was not aware that you have to pay an upgrade price if you have a Rweaper 4.x license.
No, you don't need to do that. If you have a 4.x licence, you're good to go till 5.99. I had a 3.x licence so I needed to upgrade.

I purchased the license back in 2009 when it was 3.x so i would have to buy an upgrade. As alraedy mentioned it would make no sense for me to spend money for it as recently i used Reaper only for plugin testing purposes.
Will use the evaluation of v5 to check my current plugins and then go back to 4.78.

EvilDragon · Post by **EvilDragon** » Mon Aug 17, 2015 3:21 pm

So you have a v3.x license. Why did you say that you have a v4.x license first, then?

It is mentioned very clearly on Reaper website that a license is valid for two full version cycles.

You can install v5 as portable application so that it doesn't mess your v4.78 config, so you can keep on testing.

Ingonator · Post by **Ingonator** » Mon Aug 17, 2015 3:26 pm

EvilDragon wrote:So you have a v3.x license. Why did you say that you have a v4.x license first, then? It is mentioned very clearly on Reaper website that a license is valid for two full version cycles.

You can install v5 as portable application so that it doesn't mess your v4.78 config, so you can keep on testing.

Kust re-checked teh text file where i stored the e-mail from 2009.

I seemed to have missed this:

Your license is valid for REAPER versions through v4.99

The first version i had used seemed to be v3.15.

Chris-S · Post by **Chris-S** » Mon Aug 17, 2015 5:55 pm

Why has the midi_eater JS plugin been removed from v5?

Chris-S · Post by **Chris-S** » Wed Aug 19, 2015 9:04 am

Ok, yesterday I've had the first crash in Reaper 5. Occured when loading the amp sim cortex stack.
But not reproducable.

Is there a way to find out if a crash is caused by the VST or by the host? logfile or so?

Chris

EvilDragon · Post by **EvilDragon** » Wed Aug 19, 2015 8:29 pm

If it's happened when loading a plugin, it's usually the plugin.

lfm · Post by **lfm** » Thu Aug 20, 2015 7:38 am

Chris-S wrote:Ok, yesterday I've had the first crash in Reaper 5. Occured when loading the amp sim cortex stack.
But not reproducable.

Is there a way to find out if a crash is caused by the VST or by the host? logfile or so?

Chris

Crashes out in Windows are accessible through EventViewer in administrative tools.

The crashed module is listed first and may be plugin.

But you cannot say for sure if cause is plugin, I have had situations where host is the cause still.

To narrow down which end, load into another host. If every other host loads without any issues it's probably to do with R5. Note that issue may not show itself exactly the same way - it may crash host when exiting in one host, or just sound funny, or crash on load other times crash when starting playback etc.

If bridging 32-bit, I suspect that bridging more has something to do with it. I've had plenty bridging issues is Reaper 4.x.

Chris-S · Post by **Chris-S** » Thu Aug 20, 2015 9:41 am

lfm wrote:Crashes out in Windows are accessible through EventViewer in administrative tools.

The crashed module is listed first and may be plugin.

But you cannot say for sure if cause is plugin, I have had situations where host is the cause still.

To narrow down which end, load into another host. If every other host loads without any issues it's probably to do with R5. Note that issue may not show itself exactly the same way - it may crash host when exiting in one host, or just sound funny, or crash on load other times crash when starting playback etc.

If bridging 32-bit, I suspect that bridging more has something to do with it. I've had plenty bridging issues is Reaper 4.x.

Thanks,

Code: Select all

Name der fehlerhaften Anwendung: reaper.exe, Version: 5.0.0.0, Zeitstempel: 0x55ca2d07
Name des fehlerhaften Moduls: OLDCAB_2.DLL, Version: 0.0.0.0, Zeitstempel: 0x42d2752c
Ausnahmecode: 0xc0000005
Fehleroffset: 0x0000d5d4
ID des fehlerhaften Prozesses: 0xb60

So the crash was caused by the plug (oldcab_2.dll).

I'm not using bridging (all 32 bits).

EDIT:

With following options (right click on the plug in FX window) the plugin doesn't crash:

Run as - Separate process
Embed bridged UI
Buggy plugin compat mode

BigMike · Post by **BigMike** » Thu Aug 20, 2015 7:43 pm

Chris-S wrote:Why has the midi_eater JS plugin been removed from v5?

This is actually an extremely valuable little tool I found when using The Finger or The Mouth from Native Instruments in Reaper. It stops anything from sending MIDI data, in the event you don't want it to. Interesting they removed it. It could get added back quite easily I'm sure.

I'm extremely happy that Reaper 5 is here.

Reaper 5?