TrackFX_SetParam() normalized even when Reaper has better param knowledge?

[DeBased]

I'm trying to set several plugin's delay time in milliseconds, rather than normalized 0-1. I was hoping TrackFX_SetParam() would do it, but it still uses 0-1 for the plugins I've tried (Echoboy, Guitar Rig's Quad Delay).

What's strange is that Reaper will show actual millisecond values for those delays in automation lanes - so it has a deeper knowledge of the parameters' units and ranges:



So why does TrackFX_SetParam() not accept actual millisecond values here?

[junh1024]

R doesn't actually have deep knowledge of the units iirc.

Here's my guess: You set the normalized 0-1 value, what the VST passes to the DAW is only a string for aesthetic value, not actualy directly programmable via the aesthetic "units". This wirks for humans users doing manual automation, but not programmers.

[DeBased]

Right, that possibility ocurred to me too. Doesn't VST3 add deeper parameter descriptions? Unfortunately I haven't worked with VST code.

I want this as I like delays syncing to tempo, but I like them to drift off a little, which no plugin I've seen supports. So I've written a JS that takes the tempo and allows you to modify it, and it spits out a millisecond delay value. I tried applying this via parameter modulation, but of course it's not only 0-1, but also plugins tend to use non-linear parameter ranges. So to apply the ms value correctly would mean reverse-engineering that for every plugin - doable, but sucks and not a universal solution.

The other approach would be to lie to plugins about the project tempo somehow, then all tempo-syncing plugins could be sync-drifted automatically. But that's probably not possible without modifying Reaper?

Actually that would be a good FR, per-plugin instance tempo-modification.

[DeBased]

FR posted.

If anybody can think of another way, let me know.

[DeBased]

This is my workaround JS script approach: http://forum.cockos.com/showthread.php?p=1846538