KVR Audio

martin_l · Post by **martin_l** » Mon May 16, 2016 5:55 pm

It does work, but the values represent the ones in the LED readout, which is 0-99.
Just one of the quirks of the JX-8P which uses 0-99 in the display, but 0-10 printed on the programmer.

Cheers,
Martin

Dandruff wrote:
martin_l wrote:They ARE implemented. This is actually default when using WDL-OL.

Cheers,
Martin
Ok, but it doesn't seem to work properly here.

REAPER 5.18 x64

Example:

"LFO Delay time" -> show as track envelope

Tooltip range = 0 to 99 (should be 0 to 10 as in GUI)
Rightclick envelope point -> "Set point value" gives a range of 0 to 1 (should be 0 to 10 as well)

Also as soon as you have active parameter envelopes in REPAER, the parameter readout in the GUI doesn't work properly anymore (tweaking fader with mouse doesn't show the parameter value readout properly).

Dandruff · Post by **Dandruff** » Mon May 16, 2016 5:59 pm

martin_l wrote:It does work, but the values represent the ones in the LED readout, which is 0-99.

Ok, didn't notice this.

Ok, the tooltip readout is correct then. But the Envelope point editing entry field is still using 0 to 1 range which should be 0 to 99 in this case.

martin_l · Post by **martin_l** » Mon May 16, 2016 6:02 pm

Dandruff wrote:
martin_l wrote:It does work, but the values represent the ones in the LED readout, which is 0-99.
Ok, didn't notice this.

Ok, the tooltip readout is correct then. But the Envelope point editing entry field is still using 0 to 1 range which should be 0 to 99 in this case.

Works for me. I get also the 0-99 range when adding and editing a point in the envelope.

(reaper 5.17/64 on Mac, will check 5.18 on Win later)

Cheers,
Martin

martin_l · Post by **martin_l** » Mon May 16, 2016 6:21 pm

martin_l wrote:
Dandruff wrote:
martin_l wrote:It does work, but the values represent the ones in the LED readout, which is 0-99.
Ok, didn't notice this.

Ok, the tooltip readout is correct then. But the Envelope point editing entry field is still using 0 to 1 range which should be 0 to 99 in this case.
Works for me. I get also the 0-99 range when adding and editing a point in the envelope.

(reaper 5.17/64 on Mac, will check 5.18 on Win later)

Edit: also tried 5.18/64 on Windows and it works correctly for me.

Cheers,
Martin

Dandruff · Post by **Dandruff** » Mon May 16, 2016 6:28 pm

martin_l wrote:Edit: also tried 5.18/64 on Windows and it works correctly for me.

Weird, here it doesn't:

martin_l · Post by **martin_l** » Mon May 16, 2016 6:38 pm

Dandruff wrote:
martin_l wrote:Edit: also tried 5.18/64 on Windows and it works correctly for me.
Weird, here it doesn't:

OK. I was looking at 'create envelope point'. I can also reproduce the behaviour you see, but I would rather suspect a reaper bug here. From the value displayed when simply moving an envelope point, you see that the plugin is reporting the correct values. And there is only one function which is called through the reaper extensions.

Do you know of a plugin which behaves correctly? I just tried Tyrell, and that also is wrong (even more messed up).

Cheers,
Martin

Dandruff · Post by **Dandruff** » Mon May 16, 2016 6:46 pm

martin_l wrote:Do you know of a plugin which behaves correctly?

All Voxengo plugins and also REAPER's own (ReaEQ for example) do it properly.

Maybe this https://www.voxengo.com/forum/ar/1926/?offset=0 helps.

Voxengo-Set-Point-Value.jpg

Numanoid · Post by **Numanoid** » Mon May 16, 2016 7:20 pm

Would be excellent if the dev updated the first post in the thread with the latest info on this plug.

Does the link there point to the latest version, I mean with v2.0 is the plug still in beta?

martin_l · Post by **martin_l** » Mon May 16, 2016 7:28 pm

Numanoid wrote:Would be excellent if the dev updated the first post in the thread with the latest info on this plug.

Does the link there point to the latest version, I mean with v2.0 is the plug still in beta?

Actually, the plugin is now out of beta. I uploaded a NEWS item to KVR news this weekend (which went life Sunday), and am currently waiting for an official developers forum for further discussions.

Maybe I just start a new thread here about the release, in case not every one got the KVR news.

Cheers,
Martin

bftucker · Post by **bftucker** » Mon May 16, 2016 7:39 pm

martin_l wrote:
Maybe I just start a new thread here about the release, in case not every one got the KVR news.

Cheers,
Martin

Good idea.

This thread documents the historical development.

It's been great watching you work! And CONGRATULATIONS on. 2.0!!

Mutant · Post by **Mutant** » Mon May 16, 2016 7:55 pm

*Not my video.
I just found it on YT and liked it enough to post here.

murnau · Post by **murnau** » Mon May 16, 2016 7:57 pm

Donated! Thank you!

resistor · Post by **resistor** » Mon May 16, 2016 9:55 pm

AUTO-ADMIN: Non-MP3, WAV, OGG, SoundCloud, YouTube, Vimeo, Twitter and Facebook links in this post have been protected automatically. Once the member reaches 5 posts the links will function as normal.

Great work on the plugin! Just wondering if you're planning on implementing support for 14-bit MIDI learn. For instance, the filter cutoff knob on my Bass Station II outputs messages using CC 16 and 48.

Here's a MIDI file with the data produced by sweeping the filter knob on the BSII:

https://www.dropbox.com/s/4mlow5mwzb20c ... t.MID?dl=0 (https://www.dropbox.com/s/4mlow5mwzb20c36/14bit.MID?dl=0)

Numanoid · Post by **Numanoid** » Mon May 16, 2016 9:59 pm

Why do users continue bumping this thread when the dev has started a new one for v2.0

Mutant · Post by **Mutant** » Mon May 16, 2016 10:01 pm

Because we rarely visit the Instruments forum, we just come here from our participated threads lists.

PG8X (inspired by the JX8P): new beta version uploaded