KejPi
Feature request: Different tuners for different muxes
Here's a bit of a daft idea I had, but I thought I'd mention it.
Would it be possible to connect 2 devices say via RTL-TCP and set them for certain frequencies? This could be useful for listening to stations from mux not close to you.
Maybe this is a bit too advanced, but here's the idea anyway:
Maybe under advanced settings:
Point RTL-TCP A to muxes 5A / 5B Point RTL-TCP B to muxes 5C / 5D etc.
Maybe this is a weird one, but would be cool! 😎
In another post, 2 days ago, I asked to have several profiles, because I have 2 RTL-TCP "servers", 1 local and 1 remote, and thanks to the developer (KejPi) answer, I got it running. Your idea would not work in case you have signals on same channel on both servers, like me. I have signals on 7A on both servers....
Well, in my theory you'd have assigned say 7A to one of the RTL TCP servers. Maybe a button could be added to switch between servers also.
This feature would mean significant application redesign. Essentially RTL-TCP with given IP address is considered as device. Having 2 different IP addresses means 2 different devices that can only be connected by user. Nevertheless I will keep this idea open as a potential future enhancement.
Yeah I completely get it 😄. It’s very much a niche . Would be very handy for mux operators though !.
Ryan
On Sun 31 Aug 2025 at 21:00, KejPi @.***> wrote:
KejPi left a comment (KejPi/AbracaDABra#242) https://github.com/KejPi/AbracaDABra/issues/242#issuecomment-3240375701
This feature would mean significant application redesign. Essentially RTL-TCP with given IP address is considered as device. Having 2 different IP addresses means 2 different devices that can only be connected by user. Nevertheless I will keep this idea open as a potential future enhancement.
— Reply to this email directly, view it on GitHub https://github.com/KejPi/AbracaDABra/issues/242#issuecomment-3240375701, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXQFX4YUZYMLN5N4UE4XFHD3QNH5DAVCNFSM6AAAAACFFFFGMSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTENBQGM3TKNZQGE . You are receiving this because you authored the thread.Message ID: @.***>