Ask Justin Frankel

justin = { main feed , music , code , askjf , pubkey };

Ask Justin Frankel
No reasonable question unanswered since 2009!

Suggested topics: programming, music, sleep, coffee, etc.

Note: please do not ask questions about REAPER features, bugs or scheduling, use the forums instead.

[back to index] | [unreplied] | [replied] | [recent comments] | [all]

Question: hey Justin. I'm just contributing fairly deep features to CSI, and wondered if you can expose the IReaperControlSurface::Run() frequency to Preferences? 30Hz is pretty low, both for fader update rates (eg. for surfaces that don't support fader interpolation, although I've just worked around that) as well as input accuracy/resolution.
Asked by DeBased (90.252.255.x) on April 22 2021, 8:30pm
Reply on April 22 2021, 9:18pm:

You can set your own timer and run things more often if you want

Comments:

Posted by DeBased (90.252.255.x) on April 22 2021, 10:43pm:
(sorry for the Reaper Q, tried to follow up with 'ignore, I'll repost on forum' but the system wouldn't allow it). interesting, right now I'm doing fader output interpolation on a thread, I could extend that for IO generally. but exposing it would benefit other surface code too.

Posted by helgoboss (92.212.0.x) on April 23 2021, 4:56pm:
Correct me if I'm wrong but even you do things in your own thread, this won't help with getting the current REAPER state faster to the surface or vice versa. Because you'll always have to wait for the next main thread cycle anyway to get/set new values.

Posted by Justin on April 23 2021, 7:00pm:
I imagine the 30Hz is fast enough precision, the surface just needs interpolated output to be smooth enough?

Posted by DeBased (90.252.255.x) on April 24 2021, 1:47am:
@helgoboss, no it does seem to help (implemented it today) as the surface code queries the MIDI events and outputs them from/to Reaper. So the more often you do that, the finer-grained/less bunched up the values will be. I've also added a LAN protocol for a specific surface (Behringer XTouch) which bypasses reaper and communicates directly via UDP (as does the CSI OSC code), so there are definite gains there too. @Justin, for output probably yes, but input should be significant (precision/latency).

Posted by DeBased (90.252.255.x) on April 24 2021, 1:48am:
.. but need to test properly.

Posted by helgoboss (92.212.0.x) on April 24 2021, 8:24am:
@DeBased Mmh, is that safe? AFAIK for most REAPER functions, calling them from a thread which is not the main thread is unsafe (even when read-only)? If I'm wrong about that, I would be happy to know (and adjust reaper-rs).

Posted by helgoboss (92.212.0.x) on April 24 2021, 8:49am:
My guess is that this applies: stackoverflow.com/questions/358029...
Posted by Justin on April 24 2021, 1:10pm:
Definitely do not call most of the REAPER API via another thread. Instead, use SetTimer() and create a timer that runs at a faster rate (e.g. every 10ms) and call things from that.
Posted by Airon (77.191.10.x) on April 25 2021, 8:45am:
Good interpolation will definitely be a help for guys like me, who do very fast fader moves on dialogue
Posted by Airon (77.191.10.x) on April 25 2021, 8:46am:
Good interpolation will definitely be a help for guys like me, who do very fast fader moves on dialogue. That is, once this is actually possible with
Posted by Airon (77.191.10.x) on April 25 2021, 8:48am:
Sorry for the double post. iPad troubles. ..... Reaper has some problems recording these kinds of moves from control surfaces as well as old Protools did from an Ethernet controller 20 years ago.
Posted by helgoboss (92.212.0.x) on April 25 2021, 1:24pm:
Ah cool, learned something. Didn't know the timer can run faster than IReaperControlSurface.Run() and is allowed to call REAPER functions. Great!
Posted by DeBased (90.252.255.x) on May 2 2021, 10:52pm:
On Windows at least I seem to have zero issues running from my own Run() thread. A second independent thread does the fader interpolation, again MIDI output appears threadsafe with no glitches. I'll look into timers.
Posted by DeBased (90.252.255.x) on May 2 2021, 10:54pm:
My point doing this is that when I recently came to surfaces fresh, I didn't understand why they are treated as low-priority input devices. They are human-expression devices like any other MIDI devices, ideally they should be recorded the same (sample accurate etc). Not just for precision but latency, eg. time-critical punch ins, mutes etc.
Posted by DeBased (90.252.255.x) on May 2 2021, 11:10pm:
FYI, my CSI mod's Run() tops out at just under 100 Hz on my system (CSI relies heavily on polling state from Reaper, some of that could be optimised). That should help with recording precision/latency. And my fader output interpolation is around 300Hz max with USB/LAN (~100Hz max via classic MIDI). On my Behringer X-Touch (which doesn't interpolate faders) it went from a grinding noisy mess to almost butter smooth. I'm hoping to release a beta on the Reaper forum within a week or so (will post link).

Comment:

    Your Name:   -- Site Owner's Name:  (for human-verification)

    Comment:

[back to index] | [unreplied] | [replied] | [recent comments] | [all]