Guides

Start with the install , then declare a Player for each screen. The other guides cover one task each: map a controller whose codes nobody has written down, hand the idle screen to another program , record what a player is playing , and claim a GPU by what it decodes . The reference describes each resource.

Players, plays, and their pods explains the model behind these steps.

• Install the operator
• Declare a Player
• Map a new controller
• Hand the idle screen to another controller
• Record what a player is playing
• Claim a GPU by what it decodes