Abstract: A mobile device having an augmented reality user interface for use in controlling networked light modules. The mobile device can detect via a camera a light module and display an identification of the light module on a user interface such as a touch screen. A user can enter a command via the user interface such as a desired intensity or color for the light module. In response, the mobile device transmits a signal to the light module in order to control the operation of the module based upon the command.

Abstract: A favorite channel list for a media system is generated by observing the viewing, surfing, and recording habits of a user. The viewing habits may include the duration and frequency of viewing a channel. A user's surfing habits, including navigation habits of a guide, the method used for navigation to a channel, and information queries made during a surfing session may be used to determine which channels may be added to a favorites list. When the user has an ability to record a program and view the program later, the user's behavior in selecting programs for recording, and the behaviors of playing back and archiving recorded shows may also be used to identify favorite channels. In some embodiments, the favorites list may be customized for a user or node of a playback system, as well as time of day.

Abstract: Techniques are disclosed herein for a media center portal. One implementation includes displaying first content in an expanded state and second content in a contracted state. At least a portion of the first content is presented in a viewport. A request is received to expand the second content. The first content is contracted for display in the contracted state. The second content is expanded for display in the expanded state. The contracted first content is displayed while displaying the expanded second content. At least a portion of the second content is presented in a text reader when in the expanded state.

Abstract: A favorite channel list for a media system is generated by observing the viewing, surfing, and recording habits of a user. The viewing habits may include the duration and frequency of viewing a channel. A user's surfing habits, including navigation habits of a guide, the method used for navigation to a channel, and information queries made during a surfing session may be used to determine which channels may be added to a favorites list. When the user has an ability to record a program and view the program later, the user's behavior in selecting programs for recording, and the behaviors of playing back and archiving recorded shows may also be used to identify favorite channels. In some embodiments, the favorites list may be customized for a user or node of a playback system, as well as time of day.

Abstract: A favorite channel list for a media system is generated by observing the viewing, surfing, and recording habits of a user. The viewing habits may include the duration and frequency of viewing a channel. A user's surfing habits, including navigation habits of a guide, the method used for navigation to a channel, and information queries made during a surfing session may be used to determine which channels may be added to a favorites list. When the user has an ability to record a program and view the program later, the user's behavior in selecting programs for recording, and the behaviors of playing back and archiving recorded shows may also be used to identify favorite channels. In some embodiments, the favorites list may be customized for a user or node of a playback system, as well as time of day.

Abstract: Techniques are disclosed herein for a media center portal. One implementation includes displaying first content in an expanded state and second content in a contracted state. At least a portion of the first content is presented in a viewport. A request is received to expand the second content. The first content is contracted for display in the contracted state. The second content is expanded for display in the expanded state. The contracted first content is displayed while displaying the expanded second content. At least a portion of the second content is presented in a text reader when in the expanded state.

Abstract: Systems, methods and computer program products for allocating tuner resources to tuner consumers when a tuner conflict occurs. When the tuner resources of a system or network reside at a central server, the tuners are allocated to requesting consumers according to the priority of the tuner request and the current tuner priorities. A tuner request that has a higher priority than one of the current tuners is granted. The tuner is not taken from the consumer without warning, however. Tuner conflict is also prevented by lowering the respective tuner priorities as appropriate.

Abstract: Systems, methods, and computer program products for managing and prioritizing record events. A priority manager includes an event list that lists scheduled record events. Each event in the event list has a priority that is different from the other events in the event list. If some of the events conflict, such as when a tuning resource is lost and unavailable, then those events with the highest priority in the event list are recorded. A user can assign priority to events when they are scheduled or at a later time. This enables event conflicts to be resolved by the user when the events are initially scheduled. When an event conflict arises later, the conflict is resolved by the priority manager according to the relative priority of the events in the event list.

Abstract: Systems, methods, and computer program products for managing and prioritizing record events. A priority manager includes an event list that lists scheduled record events. Each event in the event list has a priority that is different from the other events in the event list. If some of the events conflict, then those events with the highest priority in the event list are recorded. A user can assign priority to events when they are scheduled or at a later time. This enables event conflicts to be resolved by the user when the events are initially scheduled. When an event conflict arises later, the conflict is resolved by the priority manager according to the relative priority of the events in the event list.

Abstract: Systems, methods, and computer program products for managing and prioritizing record events. A priority manager includes an event list that lists scheduled record events. Each event in the event list has a priority that is different from the other events in the event list. If some of the events conflict, then those events with the highest priority in the event list are recorded. A user can assign priority to events when they are scheduled or at a later time. This enables event conflicts to be resolved by the user when the events are initially scheduled. When an event conflict arises later, the conflict is resolved by the priority manager according to the relative priority of the events in the event list.