This disclosure is related to media processing systems and methods.
Media devices, such as digital video and audio players, can include multiple functions and capabilities, such as playing stored content, browsing and selecting from recorded content, storing and/or receiving content selected by a user, and the like. These various functions can often be grouped according to content types, e.g., movies, music, television programs, photos, etc. The functions can then be accessed through various user interfaces that are typically arranged in a hierarchal manner, having a “root” or “home” user interface at the top of the hierarchy. The user interface can include both graphical and textual features. It is desirable that the user interface conveys information to the user in an intuitive manner, and readily provides access to various functions.
Disclosed herein are systems and methods for presenting icons in an interface environment. In one implementation, a user interface includes a plurality of icons. At least one of the icons is arranged in a foreground position and the remaining icons are arranged in background positions in the interface environment. The foreground and background positions define a multidimensional path. One of the background positions defines a terminus position representative of a terminus of the multidimensional path, and the icons transition between the foreground position and the background positions along the multidimensional path.
In another implementation, an icon is displayed in a foreground position in a display area and one or more icons are displayed in one or more background positions in the display area. The icons are arranged according to a multidimensional path extending from a terminus, and transition to and from the foreground position and to and from the one or more background positions along the multidimensional path.
In another implementation, a system includes a processing device and a user interface engine. The user interface engine is executable by the processing device, and is configured to display icons in foreground and background positions in a user environment, and arrange the icons displayed in the foreground and background positions according to a multidimensional path in the user environment so that the multidimensional path intersects an edge of the user environment. The user interface engine is also configured to transition the icons through the foreground position and background positions along the multidimensional path.
The media data and related metadata may be provided by a single provider, or may be provided by separate providers. In one implementation, the media processing system 100 can be configured to receive media data from a first provider over a first network, such as a cable network, and receive metadata related to the video data from a second provider over a second network, such as a wide area network (WAN). Example media data include video data, audio data, content payload data, or other data conveying audio, textual and/or video data.
In another implementation, the media processing system 100 can be configured to receive media data and metadata from a computing device, such as a personal computer. In one example of this implementation, a user manages one or more media access accounts with one or more content providers through the personal computer. For example, a user may manage a personal iTunes® account with iTunes® software, available from Apple Computer, Inc. Media data, such as audio and video media data, can be purchased by the user and stored on the user's personal computer and/or one or more data stores. The media data and metadata stored on the personal computer and/or the one or more data stores can be selectively pushed and/or pulled for storage in the data store 102 of the media processing system 100.
In another implementation, the media processing system 100 can be used to process media data stored in several data stores in communication with a network, such as wired and/or wireless local area network (LAN), for example. In one implementation, the media processing system 100 can pull and/or receive pushed media data and metadata from the data stores over the network for presentation to a user. For example, the media processing system 100 may be implemented as part of an audio and video entertainment center having a video display device and an audio output device, and can pull media data and receive pushed media data from one or more data stores for storage and processing. At the entertainment center, a user can, for example, view photographs that are stored on a first computer while listening to music files that are stored on a second computer.
In one implementation, the media processing system 100 includes a remote control device 108. The remote control device 108 can include a rotational input device 110 configured to sense touch actuations and generate remote control signals therefrom. The touch actuations can include rotational actuations, such as when a user touches the rotational input device 110 with a digit and rotates the digit on the surface of the rotational input device 110. The touch actuations can also include click actuations, such as when a user presses on the rotational input device 110 with enough pressure to cause the remote control device 108 to sense a click actuation.
In one implementation, the functionality of the media processing system 100 is distributed across several engines. For example, the media processing system 100 may include a controller engine 112, a user interface (UI) engine 114, and one or more media engines 116-1, 116-2, and 116-n. The engines may be implemented in software as software modules or instructions, or may be implemented in hardware, or in a combination of software and hardware.
The control engine 112 is configured to communicate with the remote control device 108 by a link, such as a wireless infrared signal or radio frequency signal. The remote control device 108 can transmit remote control signals generated, for example, from touch actuations of the rotational input device 110 to the control engine 112 over the link. In response, the control engine 112 is configured to receive the remote control signals and generate control signals in response. The control signals are provided to the processing device 104 for processing.
The control signals generated by the control engine 112 and processed by the processing device 104 can invoke one or more of the UI engine 114 and media engines 116-1-116-n. In one implementation, the UI engine 114 manages a user interface to facilitate data presentation for the media engines 116-1-116-n and functional processing in response to user inputs.
In one implementation, the media engines 116 can include one or more content-specific engines, such as a movies engine, television program engine, music engine, and the like. Each engine 116 can be instantiated to support content-specific functional processing. For example, a movie engine to support movie-related functions can be instantiated by selecting a “Movies” menu item. Example movie-related functions include purchasing movies, viewing movie previews, viewing movies stored in a user library, and the like. Likewise, a music engine to support music-related functions can be instantiated by selecting a “Music” menu item. Example music-related functions include purchasing music, viewing music playlists, playing music stored in a user library, and the like.
The media processing system 100 of
The rotational input device areas 160, 162, 164, 166 and 168 are receptive to press actuations. In one implementation, the areas include a menu area 160, a reverse/previous area 162, a play/pause area 164, a forward/next area 166, and a select area 168. The areas 160-168, in addition to generating signals related to their descriptive functionalities, can also generate signals for context-dependent functionality. For example, the menu area 160 can generate signals to support the functionality of dismissing an onscreen user interface, and the play/pause area 164 can generate signals to support the function of drilling down into a hierarchal user interface. In one implementation, the areas 160-168 comprise buttons disposed beneath the surface of the rotational input device 110. In another implementation, the areas 160-168 comprise pressure sensitive actuators disposed beneath the surface of the rotational input device 110.
The processing device 150 is configured to receive the signals generated by the rotational input device 110 and generate corresponding remote control signals in response. The remote control signals can be provided to the communication subsystem 152, which can wirelessly transmit the remote control signals to the media processing system 100.
Although shown as comprising a circular surface, in another implementation, the rotational input device 110 can comprise a rectangular surface, a square surface, or some other shaped surface. Other surface geometrics that accommodate pressure sensitive areas and that can sense touch actuations may also be used, e.g., an oblong area, an octagonal area, etc.
Other actuation area configurations may also be used. For example, in another implementation, the remote control device 108 can also include a separate actuation button 170. In this implementation, the areas comprise a “+” or increase area 160, a reverse/previous area 162, a “−” or decrease area 164, a forward/next area 166, a play/pause area 168, and a menu area 170.
The media data can be received through the network 212 by one of the computing devices, such as computing device 208. The network 212 can include one or more wired and wireless networks, such as the Internet. The media data is provided by one or more content providers 214. For example, the content provider 214-1 may provide media data that is processed by the media processing system 100 and output through the output devices 206, and the content provider 214-2 may provide metadata related to the media data for processing by the media processing system 100. Such metadata may include episodic content, artist information, and the like. A content provider 214 can also provide both media data and related metadata.
In one implementation, the media processing system 100 can also communicate with one or more content providers 214 directly. For example, the media processing system 100 can communicate with the content providers the wireless network 202, the I/O device 203, and the network 212. The media processing system 100 can also communicate with the content providers 214 thorough other network configuration, e.g., through a direct connection to a cable modem, through a router, or through one or more other communication devices. Example communications can include receiving sales information, preview information, or communications related to commercial transactions, such as purchasing audio files and video files.
In another implementation, the media processing system 100 can receive content from any of the computing devices 206 and 208, and other such computing devices or data stores 210 available on the network 202 through sharing. Thus, if any one or more of the computing devices or data stores are unavailable, media data and/or metadata one the remaining computing devices or other such computing devices or data stores can still be accessed.
In one implementation, the media menu interface environment 300 includes a media menu 302 identified in part by an icon 304 in a title location and a title 306, e.g., “iTv.” The media menu 302 includes media menu items 310, 312, 314, 316, 318, 320 and 322, respectively entitled “Movies,” “TV Shows,” “Music,” “Podcasts,” “Photos,” “Settings,” and “Streaming.” The media menu 302 can also include a highlight indicator 324 that highlights a media menu item. In one implementation, the highlight indicator 324 is a graphical indicator that provides the effect of a diffused backlighting, e.g., a glow highlight that provides the appearance of a backlit surface beneath the highlighted menu item.
A highlight selection of a menu item by the highlight indicator 324 indicates that the menu item is eligible for a further selection action, e.g., eligible to be selected by actuating the select area 168 on the rotational input device 110. The highlight indicator 324 can be moved vertically, for example, by actuating menu area 160 and the play/pause area 164 on the rotational input device 110.
Upon the further selection, a process associated with the highlighted menu item is performed. In one implementation, selection of the media menu item 310 when highlighted generates a movie content menu environment for processing media data related to movies, such as movie previews and full-length movies. Selection of the media menu item 312 when highlighted generates a TV Shows content menu environment for processing media data related to television programs, such as program episodes. Selection of the media menu item 314 when highlighted generates a Music content menu environment for processing media data related to music, such as audio files and music video files. Selection of the media menu item 316 when highlighted generates a Podcasts content menu environment for processing media data related to podcasts. Selection of the media menu item 318 when highlighted generates a Photos content menu environment for processing media data related to photos, such as photographs and videos. Selection of the media menu item 320 when highlighted generates a settings menu environment for changing settings of the media system, such as setting restrictions and shared files. Selection of the media menu item 322 when highlighted generates a Streaming menu environment for identifying and selecting media data stored on data stores or computer devices accessible through a network, such as media data stored on computing devices 206 and 208 and data store 210 and accessible over the network 202 of
The media menu 302 can also include a child indicator 326 associated with a media menu item. The child indicator 326 indicates that one or more sub-menus or sub-items, e.g., folders, will become available or will be accessed upon selection of the corresponding media menu item.
The media menu interface environment 300 also includes media menu item abstractions that correspond to one or more of the media menu items. For example, the media menu item abstractions 330, 332, 334 and 336 correspond to media menu items 310, 312, 314 and 316, respectively. In one implementation, the media menu item abstractions are graphical representations of the content of corresponding media menu items. For example, the media menu item abstraction 330, which corresponds to the Movies media menu item 310, can be a movie icon. Likewise, the media menu item abstraction 332, which corresponds to the TV Shows media menu item 312, can be a television icon; the media menu item abstraction 334, which corresponds to the Music Media menu item 314, can be a music icon, etc.
In one implementation, the media menu item abstractions 330-336 are arranged such that at least one of the media menu item abstractions, e.g., icon 330, is in a foreground position, and the remaining the media menu item abstractions, e.g., icons 332-336, are in one or more background positions. The foreground and background positions define a multidimensional path 350, and the media menu item abstraction 336 is in a background position that defines a terminus of the multidimensional path. In one implementation, the terminus is at the edge 352 of the media menu interface environment 300.
In one implementation, the media menu item abstraction corresponding to a highlighted menu is displayed in the foreground position. For example, in
In another implementation, one or more of the media menu item abstractions in the background positions may be displayed with an effect, e.g., a blurring effect. The blurring effect can be used to further deemphasize the media menu item abstractions. For example, in
In another implementation, media menu item abstractions are sealed in size, for example, substantially or functionally proportionally to the proximity of the media menu item abstraction to the foreground position. For example, the media menu item abstraction 336 can be displayed at approximately 20% of full scale, and the media menu item abstraction 330 can be displayed at 100% of full scale.
In one implementation, changing the position of the highlight indicator 324 causes the highlight indicator to transition form a highlighted media menu item to a media menu item to be highlighted, e.g., an adjacent media menu item. The transition of the highlight indicator 324 likewise causes the media menu item abstractions to transition between the foreground and background positions along the multidimensional path 350 until the media menu item abstraction corresponding to the newly-highlighted media menu item is in the foreground position.
Because the media menu item abstraction 332 is transitioning from a background position into the foreground position previously occupied by media menu item abstraction 330, the media menu item abstraction 330 transitions out of the media menu interface environment 300, as indicated by directional arrow 364. In the example implementation shown in
In one implementation, the scale of the media menu item abstraction transitioning off the edge 352 of the media menu interface environment 300 can be increased to simulate a “fly by” effect. For example, the scale of the media menu item abstraction 330 can be proportionally increased from 100% to 150% of full scale as the media menu item abstraction 330 transitions from the foreground position to the edge 352 of the media menu interface environment 300.
The media menu item abstraction 330, which corresponds to the Movies menu item 310 which is to be highlighted by the highlight indicator 324, emerges from the edge 352 and back into the foreground position, as indicated by the directional arrow 374. In the example implementation shown in
Once the transitions indicated by the directional arrows 370, 372 and 374 are complete, the media menu interface environment 300 returns to the state as depicted in
Likewise, transitioning the highlight indicator 324 to the photos media menu item 318 will cause the media menu item abstraction 340 to transition into a background position and the media menu item abstraction 342 to transition further into the background positions, and will also cause the media menu item abstraction 338 to emerge into the foreground position.
Other processes can be implemented to illustrate a transition of a media menu item abstraction out of the media menu interface environment. For example, in one implementation, a media menu item abstraction is increased in size and fades out, simulating an effect of vertically launching from the media menu interface environment. In another implementation, a media menu item abstractions follows a straight path, or a linear path, from the foreground position out of the media menu interface environment. Other visual effects can also be used.
In another implementation, the media menu item abstractions can include a reflection effect. For example, the media menu item abstractions 332, 334, 336 and 338 include reflections 333, 335, 337 and 339. The reflection effect further emphasizes a multidimensional visual effect, and can be implemented in any of the implementations described herein.
In another implementation, the number of media menu item abstractions displayed along the multidimensional path 350 can vary depending on the size of the media menu item abstractions. For example, the media processing system 100 may normally display four media menu item abstractions; however, if the media menu item abstractions are increased or decreased in display size, the number of media menu item abstractions to be displayed can be decreased or increased, respectively.
In the example implementations described above, the transitioning of the media menu item abstractions corresponds to the transitioning of the highlight indicator 324, e.g., as the highlight indicator 324 transitions from one media menu item to the next, the media menu item abstractions likewise transition through the multidimensional path 350 in a substantially synchronous manner.
In another implementation, the media menu item abstractions do not transition until the highlight indicator 324 has settled on a media menu item and no further commands to transition the highlight indicator 324 are received. In yet another implementation, the media menu item abstractions and the highlight indicator 324 transition substantially instantaneously, e.g., within several video frames or within one video frame. Other transition animations may also be used.
Stage 402 arranges a foreground position and background positions in a display area according to a multidimensional path extending from a terminus. For example, the processing device 104 and/or UI engine 114 can arrange the media menu item abstractions according to the multidimensional path 350 of
Stage 404 displays one or more icons in the one or more background positions in the display area. For example, the processing device 104 and/or UI engine 114 can display one or more media menu item abstractions in one or more background positions.
Stage 406 displays an icon in the foreground position in the display area. For example, the processing device 104 and/or UI engine 114 can display one or more media menu item abstractions, e.g., media icons in foreground positions.
Stage 408 transitions icons from the foreground and background positions along the multidimensional path. For example, the processing device 104 and/or UI engine 114 can transition the media menu item abstractions as described with reference to
Stage 422 transitions an icon in the foreground position into a background position. For example, the processing device 104 and/or UI engine 114 can transition a media menu item abstraction from a foreground position to a background position.
Stage 424 transitions an icon in the background position nearest the terminus of the multidimensional path out of the display environment. For example, the processing device 104 and/or UI engine 114 can transition media menu item abstractions in the terminus position out of the display environment.
Stage 442 generates a selection menu defining a plurality of menu items. For example, the processing device 104 and/or UI engine 114 can generate the media menu 302 and media menu items 310-322.
Stage 444 displays the selection menu proximate to corresponding icons. For example, the processing device 104 and/or UI engine 114 can display the media menu 302 proximate to the media menu item abstractions 330-342.
Stage 446 highlights a menu item. For example, the processing device 104 and/or UI engine 114 can generate the highlight indicator 324 to highlight a menu item.
Stage 448 transitions an icon that corresponds to the highlighted menu item into the foreground position. For example, the processing device 104 and/or UI engine 114 can transition a media menu item abstraction into the foreground position.
Stage 462 receives a command to change the highlight indicator from a highlighted menu item to a menu item to be highlighted. For example, the processing device 104 and/or UI engine 114 can receive a command to change the highlight indicator 324 from a highlighted media menu item to a media menu item to be highlighted.
Stage 464 determines if the direction of the highlight indicator during transition is in a first direction or a second direction. For example, the processing device 104 and/or UI engine 114 can determine if the highlight indicator 324 is transitioning in an up direction or a down direction. While an example two direction method is described, other multi-directional methods for traversing more or less complicated paths can be used.
If the direction is in the first direction, stage 466 transitions the icon corresponding to the media menu item to be highlighted from a background position to the foreground position. For example, the processing device 104 and/or UI engine 114 can transition a media menu item abstraction from a background position to a foreground position.
If the direction is in the first direction, stage 468 transitions the highlighted icon in the foreground position off the display area. For example, the processing device 104 and/or UI engine 114 can transition a highlighted media menu item abstraction off the media menu interface environment 300.
If the direction is in the second direction, stage 470 emerges the icon corresponding to the media menu item to be highlighted into the foreground position. For example, the processing device 104 and/or UI engine 114 can emerge a media menu item abstraction into the foreground position.
If the direction is in the second direction, stage 472 transitions an icon in the background position off the display area. For example, the processing device 104 and/or UI engine 114 can transition a media menu item abstraction in the terminus position off the media menu interface environment 300.
The stages recited in the example processes of
The screenshots 502 and 504 of
The screenshot 506 of
In another implementation, only one media menu item abstraction is shown in the foreground position, and additional media menu item abstractions are not shown in the background position. In this implementation, the media menu item abstractions that to do not correspond to the highlighted menu item transition off the display area through the multidimensional path as described above, e.g., through the terminus position if transitioning into the background position, or by being displaced by a media menu item abstraction emerging into the terminus position and transitioning from the background into the foreground position. Accordingly, only the media menu item abstraction corresponding to the highlighted menu item is shown.
The apparatus, methods, flow diagrams, and structure block diagrams described in this patent document may be implemented in computer processing systems including program code comprising program instructions that are executable by the computer processing system. Other implementations may also be used. Additionally, the flow diagrams and structure block diagrams described in this patent document, which describe particular methods and/or corresponding acts in support of steps and corresponding functions in support of disclosed structural means, may also be utilized to implement corresponding software structures and algorithms, and equivalents thereof.
This written description sets forth the best mode of the invention and provides examples to describe the invention and to enable a person of ordinary skill in the art to make and use the invention. This written description does not limit the invention to the precise terms set forth. Thus, while the invention has been described in detail with reference to the examples set forth above, those of ordinary skill in the art may effect alterations, modifications and variations to the examples without departing from the scope of the invention.
Number | Name | Date | Kind |
---|---|---|---|
5619249 | Billock et al. | Apr 1997 | A |
5717879 | Moran et al. | Feb 1998 | A |
5822123 | Davis et al. | Oct 1998 | A |
5880768 | Lemmons et al. | Mar 1999 | A |
6006227 | Freeman et al. | Dec 1999 | A |
6335737 | Grossman et al. | Jan 2002 | B1 |
6448987 | Easty et al. | Sep 2002 | B1 |
6638313 | Freeman et al. | Oct 2003 | B1 |
6725427 | Freeman et al. | Apr 2004 | B2 |
6768999 | Prager et al. | Jul 2004 | B2 |
6944632 | Stern | Sep 2005 | B2 |
7292243 | Burke | Nov 2007 | B1 |
7362331 | Ording | Apr 2008 | B2 |
7363591 | Goldthwaite et al. | Apr 2008 | B2 |
20020033848 | Sciammarella et al. | Mar 2002 | A1 |
20020083469 | Jeannine et al. | Jun 2002 | A1 |
20020175931 | Holtz et al. | Nov 2002 | A1 |
20030110450 | Sakai | Jun 2003 | A1 |
20030117425 | O'Leary et al. | Jun 2003 | A1 |
20030142751 | Hannuksela | Jul 2003 | A1 |
20030174160 | Deutscher et al. | Sep 2003 | A1 |
20040008211 | Soden et al. | Jan 2004 | A1 |
20040100479 | Nakano et al. | May 2004 | A1 |
20040140995 | Goldthwaite et al. | Jul 2004 | A1 |
20040150657 | Wittenburg et al. | Aug 2004 | A1 |
20040261031 | Tuomainen et al. | Dec 2004 | A1 |
20050041033 | Hilts et al. | Feb 2005 | A1 |
20050044499 | Allen et al. | Feb 2005 | A1 |
20050091597 | Ackley | Apr 2005 | A1 |
20050160375 | Sciammarella et al. | Jul 2005 | A1 |
20050246654 | Hally et al. | Nov 2005 | A1 |
20050278656 | Goldthwaite et al. | Dec 2005 | A1 |
20060020962 | Stark et al. | Jan 2006 | A1 |
20060031776 | Glein et al. | Feb 2006 | A1 |
20060265409 | Neumann et al. | Nov 2006 | A1 |
20070162853 | Weber et al. | Jul 2007 | A1 |
20070288863 | Ording et al. | Dec 2007 | A1 |
20080062894 | Ma et al. | Mar 2008 | A1 |
20080065638 | Brodersen et al. | Mar 2008 | A1 |
20080065720 | Brodersen et al. | Mar 2008 | A1 |
20080066010 | Brodersen et al. | Mar 2008 | A1 |
20080066110 | Brodersen et al. | Mar 2008 | A1 |
20080092168 | Logan et al. | Apr 2008 | A1 |
20080122870 | Brodersen et al. | May 2008 | A1 |
Number | Date | Country |
---|---|---|
1469375 | Oct 2004 | EP |
1510911 | Mar 2005 | EP |
Number | Date | Country | |
---|---|---|---|
20080066013 A1 | Mar 2008 | US |