Denon DRA-395 confirmed on Denon/Receiver 12,-1 — including three functions with no prior public captures I could find

[ajplotkin]

codes/Denon/Receiver/12,-1.csv works on a Denon DRA-395 stereo receiver. Verified on the
unit with a Global Caché iTach IP2IR, sending one command at a time and reading the front panel.

Filing it because searches for the model come up empty. The database has no model index, so
there is no way to discover that this table applies to a DRA-395 — the codes were here the whole
time and nothing connects them to the model.

Confirmed working (names/numbers as they appear in that CSV):

Function	#
POWER ON	104
POWER OFF	122
SPEAKER A	106
SPEAKER B	105
VOLUME UP / VOLUME DOWN	77 / 76
MUTING / MUTE TOGGLE	75
INPUT V.AUX	91

For POWER ON (104), SPEAKER A (106) and SPEAKER B (105) I could find no published captures
of the device-12 versions — I checked LIRC's Denon remotes, Flipper-IRDB, and RemoteCentral
(whose Denon speaker discretes are the newer Denon-K AVR codes, a different protocol). I
generated them from the device-12 template and all three work, which is at least some
independent support for those three rows.

Two things that might be worth recording somewhere findable:

1. The classic DRA stereo receivers share device 12 — confirmed on the DRA-395, and the
   DRA-365R captures already in Flipper-IRDB decode to device 12 as well, while Denon's classic AVR sets use
   device 8 and newer AVRs use Denon-K. The sharing boundary is the product line, not the brand,
   and trying AVR codes on a DRA wastes a lot of time.
2. Nothing in the DRA-395's own documentation mentions this protocol, device 12, or any
   relationship to other Denon models.

Happy to submit this differently if there is a preferred way to record model → code-set
mappings.

[probonopd]

Thank you very much @ajplotkin. Could you please send a pull request? Thanks.

[ajplotkin]

Happy to — but I don't think there's anything for me to change, and I'd rather say so than send an empty PR.

All eight functions I confirmed are already in codes/Denon/Receiver/12,-1.csv, under exactly these names:

fn	name in the file
104	POWER ON
122	POWER OFF
106	SPEAKER A
105	SPEAKER B
77	VOLUME UP
76	VOLUME DOWN
75	MUTING / MUTE TOGGLE
91	INPUT V.AUX

So the codes were right all along. What I was reporting is narrower: there's no way for a DRA-395 owner to find that this file applies to their unit. I searched for the model and came up empty, tried the Denon AVR code sets first because that's what search results point at, and only got here by testing device 12 directly.

As far as I can tell the schema has nowhere to record that. index and codes/index are generated by updateIndex.py walking for .csv files, so they're path listings with no model field, and the filename convention is <manufacturer>/<devicetype>/<device>,<subdevice>.csv with no room for a model either.

So: if you'd like model→code-set mappings recorded somewhere — a models file, a README table, anything you'd accept — tell me the shape you want and I'll send a PR for it, starting with this one. If the answer is that irdb deliberately doesn't track models, that's a fine answer too and this issue can just be closed; anyone searching the model number will at least land on it.

(Separately, I've sent #221 for the Toshiba issue, which does have a real change.)