# Volume repeat with FLIRC USB v2 when remote button held down

**URL:** <https://community.roonlabs.com/t/volume-repeat-with-flirc-usb-v2-when-remote-button-held-down/326504>\
**Category:** Verox \[formerly RoPieee\]\
**Created:** [October 24, 2026, 5:06pm UTC](https://community.roonlabs.com/t/volume-repeat-with-flirc-usb-v2-when-remote-button-held-down/326504 "2026-10-24T17:06:17Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Giles\_W](https://community.roonlabs.com/user_avatar/community.roonlabs.com/giles_w/32/384257_2.png) [@Giles\_W](https://community.roonlabs.com/u/Giles_W)\
**Post date:** [October 24, 2026, 5:06pm UTC](https://community.roonlabs.com/t/volume-repeat-with-flirc-usb-v2-when-remote-button-held-down/326504/1 "2026-10-24T17:06:17Z")

</div>

Is there _any_ way to have repeat volume up/down commands sent to the Roon server when a volume button on a remote is kept pressed?

I only see a single volume step via Verox, whereas when the FLIRC is connected to a Windows box the volume ramps continuously while the remote button is held down.

According to any AI this is a longstanding limitation in the underlying OS but I just thought I’d ask to see if there was any new news.

---

<div class="post-metadata">

**Author:** ![spockfish](https://community.roonlabs.com/letter_avatar/spockfish/32/5_5575768a8748004e209b776fc1b2916d.png) [@spockfish](https://community.roonlabs.com/u/spockfish)\
**Post date:** [October 24, 2026, 6:27pm UTC](https://community.roonlabs.com/t/volume-repeat-with-flirc-usb-v2-when-remote-button-held-down/326504/2 "2026-10-24T18:27:53Z")

</div>

Good question, and it’s not really an OS limitation. Verox’s remote handler gets only “pressed” and “released” from the input layer. Repeating a held key is left to the software, and we only act on “pressed”, so you get one step per press. Windows repeats held keys for you, which is why the same FLIRC ramps there.

We’ll add that: hold volume up/down, and after a short pause the volume keeps stepping until you let go, with a safety limit so a stuck key can’t run the volume up. It’s planned for after the next release, as part of a rework of the remote handling. You can follow it here: [[Feature]: Keep changing the volume while a remote's volume button is held · Issue #12 · verox-audio/verox-issues · GitHub](https://github.com/verox-audio/verox-issues/issues/12)

---

<div class="post-metadata">

**Author:** ![Giles\_W](https://community.roonlabs.com/user_avatar/community.roonlabs.com/giles_w/32/384257_2.png) [@Giles\_W](https://community.roonlabs.com/u/Giles_W)\
**Post date:** [October 24, 2026, 8:28pm UTC](https://community.roonlabs.com/t/volume-repeat-with-flirc-usb-v2-when-remote-button-held-down/326504/3 "2026-10-24T20:28:59Z")

</div>

Brilliant. Thanks Harry for such a prompt response.

---

<div class="post-metadata">

**Author:** ![Giles\_W](https://community.roonlabs.com/user_avatar/community.roonlabs.com/giles_w/32/384257_2.png) [@Giles\_W](https://community.roonlabs.com/u/Giles_W)\
**Post date:** [October 25, 2026, 12:23pm UTC](https://community.roonlabs.com/t/volume-repeat-with-flirc-usb-v2-when-remote-button-held-down/326504/4 "2026-10-25T12:23:17Z")

</div>

It would be handy for the user to be able to configure the volume ramp speed while the remote button is held, and possibly also the ‘safety limit’ as the overall delta for the ramp if the release event gets lost.

A further, unrelated, option could allow the user to adjust the size of a single volume step as an alternative to the current 1%.

You may already be thinking along such lines of course. 🙂

---

<div class="post-metadata">

**Author:** ![spockfish](https://community.roonlabs.com/letter_avatar/spockfish/32/5_5575768a8748004e209b776fc1b2916d.png) [@spockfish](https://community.roonlabs.com/u/spockfish)\
**Post date:** [October 29, 2026, 7:16pm UTC](https://community.roonlabs.com/t/volume-repeat-with-flirc-usb-v2-when-remote-button-held-down/326504/5 "2026-10-29T19:16:39Z")

</div>

Good suggestions, thanks. I’ve added them to the issue so they’re considered when we rework the remote handling.
