Razer Stream Controller (Loupedeck Live)

[ovehbe]

Razer Stream Controller Support & Extended Features Fork

Hi @RadiatorTwo,

First, thank you for creating LoupixDeck! Your work provided an excellent foundation for Linux/Windows support of these devices.

What I've Done

I've forked your repository and added comprehensive support for the Razer Stream Controller (which uses the same Loupedeck Live protocol). The fork is available at: https://github.com/ovehbe/LoupixDeck

Razer Stream Controller Support

• Full device implementation (VID: 1532, PID: 0d06)
• 6 rotary encoders (vs 2 on Live S)
• 8 physical buttons (vs 4 on Live S)
• 4×3 touch grid + 2 narrow side displays (60×270)
• Unified 480×270 display rendering with correct X-coordinate positioning
• Template-based configuration system

Additional Features Implemented

• Per-button vibration control: 28 haptic patterns, individually configurable per button
• Per-page global commands: Prefix/suffix commands for all buttons on each page
• Per-page wallpapers: Different backgrounds per page with independent opacity
• Enable When OFF: Keep specific buttons functional in OFF mode
• Touch sliding prevention: No multi-triggers when finger slides
• Silent page switching: Removed visual page indicators
• CLI enhancements: Device control from terminal
• Power management: Auto-clear on suspend/resume
• Device-specific configs: Separate config files for each device type

Important Limitation

⚠️ I have only tested this fork with the Razer Stream Controller. I do not have access to a Loupedeck Live S device, so I cannot verify that my changes haven't broken anything for the original device. While I've tried to maintain backward compatibility and keep the Live S controller separate, testing is needed.

Question: Next Steps?

I wanted to reach out to discuss how we should proceed:

Option 1 - Keep Separate:

• Maintain as a separate fork specifically for Razer Stream Controller users
• You continue focusing on official Loupedeck devices
• We can cross-reference each other's repos

Option 2 - Pull Request:

• I could create a PR with the Razer support and features
• Would require testing on Live S to ensure nothing breaks
• Could benefit both device communities

Option 3 - Collaborate:

• Merge device support while keeping features modular
• Shared codebase with device-specific controllers
• Community testing for both devices

Repository Status

Current state:

• Commit: 66d41c1
• Tag: v1.5
• Branches: Both main and master synced
• Documentation: Comprehensive README with examples
• Build: Includes automated build_release.sh script

I'm open to any approach you prefer! Again, thank you for the original work - it made this much easier to implement.

Best regards,
@ovehbe

[RadiatorTwo]

Great work!

But be aware, that because of the current event based system I ran into some problems.
Race Conditions, Event Chains, threading problems with ui and bad exception handling just to name a few.
Specifically I tried to fix the Elgato Keylight controls with some debounce logic and ended up locking the ui thread ...

I did plan to get rid of the events and implement something different to get a cleaner pipeline.
But currently don´t know exactly what it´ll be.
Maybe MediatR, maybe Rx.Net or just Threading.Channels...

And currently I don´t have the time.

[RadiatorTwo]

I did take a closer look at your fork now.

It works perfectly fine with the Loupedeck Live S.
But I had to remove the lines with _isDeviceOff, because I don´t see how to execute the System.DeviceOn or any other command when that variable is set to false on start.
Maybe I´m missing something.

I have also seen you did remove the Tray Icon and replaced it with a toggle through command.
Only tested it with KDE, Gnome and Hyprland so far.
MAybe it needs some sort of system detection.
But the implementation also wasn´t that great.

About your Collab question:

I think there should be one application and that you don´t have to decide to use one or the other.
Also with multi device support that would be better I guess.

But since I don´t have that much time currently to put into this, I think Option 3 would be best.
(It took me 3 days to even see your Fork ...)

If you want to keep it separate also fine by me.
This project was more of a personal endeavor, developed out of spite against Windows and Logitech...

[ovehbe]

First of all thanks a lot for reviewing the code throughly even so you are busy, and I agree about what you said, the implementations I've done arent really clean to be honest but I too didn't have much time to clean it as I am also a bit busy right now. For now I'll leave it as is until I find some time to clean and organize stuff, but for me it was a great project because I can use the device on linux as I'm physically incapable of using windows. Ones I make some changes and maybe even have a way to test the live s I'll let you know.