openrazer
openrazer copied to clipboard
openrazer
Add Razer Tiamat 7.1 V2
Please merge my Nommo Pro/Chroma commit (#1061) first. The Razer Tiamat 7.1 V2 uses USB interface protocol 0x00 so I would like to use the interface protocol selection logic I added in that commit. This is just for reference right now.
If you'd rather I work it into razerkraken than razeraccessory let me know. The Tiamat is an interesting case as it is an analog headset (no USB audio interface) and the USB interface is only for the Chroma control. It differs from the Kraken headsets as it has a multi-zone lighting controller that uses the same extended protocol as other razeraccessory devices. The matrix layout is 1 row, 17 columns. The first 15 LEDs are the 15 controller dial LEDs, the 16th LED is the left ear LED, and the 17th LED is the right ear. It supports wave effect unlike the Kraken headsets. This is why I chose to put it in razeraccessory.
I tested custom, off, static, spectrum cycle, all breathing modes, and wave (left and right direction).
No daemon or udev yet.
Yes please use the razerkraken (should probably be renamed to razerheadset?) driver for this device. The distinction is honestly a bit useless for those devices (it makes sense for mice & keyboards because they really have special functionality) but as we currently have it, I'd like to keep them together.
Or you could merge razercore, razerkraken and razermousemat into razeraccessory :shrug: Or we can keep the PR this way if you don't want to do that :D
I'll look into the idea of combining them. I think it makes sense to merge all those drivers as the only features OpenRazer is providing for them is Chroma lighting. The headsets run on the standard usb audio driver (except for Tiamat which is analog) and the Nommo speakers are the same way and in razeraccessory.
I've merged razermousemat and razercore into razeraccessory, but now looking at razerkraken it is very different from the others. It looks like Krakens use their own protocol that is separate from the Razer standard and extended protocol sets.
The Tiamat 7.1 uses the Razer extended protocol and thus makes sense to go in with all the other devices in razeraccessory that use this extended protocol. I think it makes sense to keep the Krakens in their own driver due to this protocol difference, even if it means headsets being split across two drivers.
If this is OK and you still want to merge the drivers, I'll add the Tiamat to my merged drivers branch in razeraccessory and open a new PR.
My merged driver branch:
https://github.com/CalcProgrammer1/openrazer/tree/razeraccessory_merge
Sorry for the delay. The changes in the razeracessory_merge branch generally look fine so please make a PR with them. If you wish we can also merge this driver asap and then the driver merge later - whatever you prefer.
Are you still interested in working on this? Would be nice to get this included at some point, but it also needs daemon support.
Anything I can do? I just got a pair of these today. Very much a git noob, so probably only good as a lab rat for testing stuff.
@JustSomeGeek This would need some changes still for daemon support and maybe some other missing pieces. Would be great if you could pick this up since otherwise support won't come. See also https://github.com/openrazer/openrazer/blob/master/DEVELOPMENT.md