WO2001090871A2 - A system and method of providing for the control of a music player to a device driver - Google Patents

A system and method of providing for the control of a music player to a device driver Download PDF

Info

Publication number
WO2001090871A2
WO2001090871A2 PCT/US2001/016230 US0116230W WO0190871A2 WO 2001090871 A2 WO2001090871 A2 WO 2001090871A2 US 0116230 W US0116230 W US 0116230W WO 0190871 A2 WO0190871 A2 WO 0190871A2
Authority
WO
WIPO (PCT)
Prior art keywords
music
graphical interface
items
player
renderer
Prior art date
Application number
PCT/US2001/016230
Other languages
French (fr)
Other versions
WO2001090871A3 (en
Inventor
Jeremy Chaney
Original Assignee
Realnetworks, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Realnetworks, Inc. filed Critical Realnetworks, Inc.
Priority to AU2001263299A priority Critical patent/AU2001263299A1/en
Publication of WO2001090871A2 publication Critical patent/WO2001090871A2/en
Publication of WO2001090871A3 publication Critical patent/WO2001090871A3/en

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/16Sound input; Sound output
    • G06F3/162Interface to dedicated audio devices, e.g. audio drivers, interface to CODECs
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46Multiprogramming arrangements
    • G06F9/54Interprogram communication
    • G06F9/542Event management; Broadcasting; Multicasting; Notifications
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0481Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
    • G06F3/0482Interaction with lists of selectable items, e.g. menus
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F2209/00Indexing scheme relating to G06F9/00
    • G06F2209/54Indexing scheme relating to G06F9/54
    • G06F2209/545Gui
    • GPHYSICS
    • G10MUSICAL INSTRUMENTS; ACOUSTICS
    • G10HELECTROPHONIC MUSICAL INSTRUMENTS; INSTRUMENTS IN WHICH THE TONES ARE GENERATED BY ELECTROMECHANICAL MEANS OR ELECTRONIC GENERATORS, OR IN WHICH THE TONES ARE SYNTHESISED FROM A DATA STORE
    • G10H2220/00Input/output interfacing specifically adapted for electrophonic musical tools or instruments
    • G10H2220/091Graphical user interface [GUI] specifically adapted for electrophonic musical instruments, e.g. interactive musical displays, musical instrument icons or menus; Details of user interactions therewith
    • G10H2220/101Graphical user interface [GUI] specifically adapted for electrophonic musical instruments, e.g. interactive musical displays, musical instrument icons or menus; Details of user interactions therewith for graphical creation, edition or control of musical data or parameters
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S715/00Data processing: presentation processing of document, operator interface processing, and screen saver display processing
    • Y10S715/961Operator interface with visual structure or function dictated by intended use
    • Y10S715/965Operator interface with visual structure or function dictated by intended use for process control and configuration
    • Y10S715/97Instrumentation and component modelling, e.g. interactive control panel

Definitions

  • the field of the invention relates to music renderers. More particularly, the field of the invention relates to providing music items to music renderers. Description of the Related Technology
  • MP3 MPEG Audio Layer 3
  • CDs typically render music at about 1400 kilobits per one second of stereo music.
  • data from a CD to another data format, such as
  • the size of the data can be shrunk by a factor of about 12 without significantly sacrificing the quality of the music.
  • the user can, via a playback device program, play, edit, or copy the downloaded music. Furthermore, from the personal computer, the user can download the music to a portable music player so that the downloaded music can be played wherever the user travels.
  • Portable music players such as the Diamond Rio 500, allow individuals store up to two hours of digital-quality music and up to 32 hours of spoken audio programs.
  • the Diamond Rio includes 64MB onboard memory, expandable to 96MB with removable flash cards. Most music players provide a certain core group of features, such as playing and recording music.
  • optional features can include: providing compact diskette "burning", providing storage library hierarchies for music items, associating notes with music items, etc.
  • the features are not supported by many legacy playback device programs.
  • the playback device programs are redesigned by the provider of the playback device program to provide support for the new features.
  • the redesign takes time.
  • the new version of the music player must be transmitted to the user. Both of these events are an inconvenience for the user.
  • One embodiment of the invention comprises a method of providing a customized graphical interface, the method comprising executing a music player that displays a graphical interface comprising information about music items, and displaying a customized graphical interface for managing the music items, wherein the content of the customized graphical interface is defined by a device driver for a music renderer, and wherein the displaying of the customized graphical interface is in response to an event occurring during the execution of the music player.
  • Another embodiment of the invention comprises a system for providing a customized graphical interface, the system comprising a music player for displaying one or more graphical interfaces that comprise information about music items, a music renderer, and a device driver for sending music items to the music renderer, wherein the device driver displays a customized graphical interface for managing the music items, and wherein the content of the customized graphical interface is defined by the device driver.
  • Another embodiment of the invention comprises a system for providing a customized graphical interface, the system comprising means for executing a music player that displays a graphical interface comprising information about music items, and means for displaying a customized graphical interface for managing the music items, wherein the content of the customized graphical interface is defined by a device driver for a music renderer, and wherein the displaying of the customized graphical interface is in response to an event occurring during the execution of the music player.
  • Another embodiment of the invention comprises a method of providing a customized graphical interface, the method comprising executing a music player that displays a graphical interface comprising information about a plurality of music items, wherein the graphical interface comprises one or more textual elements describing an aspect of the music player, and receiving a request from a device driver to change the textual element.
  • Another embodiment of the invention comprises a system for providing a customized graphical interface, the system comprising a music player displaying a graphical interface comprising information about a plurality of music items, wherein the graphical interface comprises one or more textual elements describing an aspect of the music player, the music player adapted to receive requests from a device driver to rename the textual elements.
  • Another embodiment of the invention comprises a method of controlling a music player, the method comprising executing a music player that plays music items upon a request from a user, receiving a request from a device driver to disallow playback of the music items, and suspending playback of the music items on the music player.
  • Figure 1 is a high level block diagram illustrating one embodiment of a network configuration that may be used in connection with a music system, the music system comprising a server computer, a client computer, a music player, a music renderer controller, a plurality of music renderers, and a plurality of the device drivers that are associated respectively with selected ones of the music renderers.
  • Figure 2 is block diagram illustrating the relationship between the music renderers of Figure 1 and a plurality of storage devices that are associated with the music renders.
  • Figure 3 is a block diagram illustrating a plurality of interfaces between the music controller of Figure
  • Figure 4 is a screen display illustrating an exemplary control panel for organizing the music items that are maintained by the client computer of Figure 1.
  • Figure 5 is a flowchart illustrating a process of utilizing the music player of Figure 1.
  • Figure 6 is a screen display illustrating an exemplary customized window that is displayed by one of the device drivers of Figure 1.
  • a user communicates with a computing environment which may include a client computer 104, a network 120, music renderers 126A-126N, and a music server 128.
  • the client computer 104 and each of the music renderers 126A-126N has an associated input and output device.
  • the input device may be a keyboard, rollerball, pen and stylus, mouse, voice recognition system, or predesignated switches or buttons.
  • the input device may also be a touch screen associated with an output device. The user may respond to prompts on the display by touching the touch screen. Textual or graphic information may be entered by the user through the input device.
  • the output device can comprise a speaker, a display screen, a printer, or a voice synthesizer.
  • the client computer 104, the music server 128, and the music renderers 126A-126N may each have any conventional general purpose single- or multi-chip microprocessor such as a Pentium ® processor, a Pentium ® Pro processor, a 8051 processor, a MIPS ® processor, a Power PC ® processor, or an ALPHA ® processor.
  • the microprocessor may be any conventional special purpose microprocessor such as a digital signal processor.
  • the client computer 104, the music server 128, and each of the music renderers 126A-126N may each be used in connection with various operating systems such as: UNIX, LINUX, Disk Operating System (DOS), VxWorks, PalmOS, OS/2, Windows CE, Windows 3.X, Windows 95, Windows 98, and Windows NT.
  • operating systems such as: UNIX, LINUX, Disk Operating System (DOS), VxWorks, PalmOS, OS/2, Windows CE, Windows 3.X, Windows 95, Windows 98, and Windows NT.
  • the music renderers 126A-126N can comprise a stationary device, such as a stereo system, or, alternatively, a portable device, such as a Diamond RIO, a RCA Lyra, a portable radio, or a personal display adapter.
  • the client computer 104 comprises a network interface 140, an electronic music player 144, a music renderer controller 148, and device drivers 152A-152M.
  • the network interface 140 communicates with a control program of the music server 128 via the network 120.
  • a user can communicate with the music server 128 to download and play songs via the output device of the client computer 104.
  • a user can organize the songs according to subject matter and also download the songs to one of the music renderers 126A-126N.
  • a device driver is a software program, module, procedure, or executable, that is capable of communicating with a music renderer, the device driver being adapted to "plug- in" and be operably connected to the music player 144.
  • the music renderer controller 148 controls communications between the music player 144 and the device drivers 152A-152M.
  • the music renderer controller 148 comprises a device integration application program interface (DIAPI) that provides a predefined interface for communicating with the device drivers 152A-152M.
  • DIAPI device integration application program interface
  • the DIAPI is based upon the Component Object Model (COM), which was developed by Microsoft Inc. of Redmond Washington.
  • COM Component Object Model
  • the client computer 104 includes a network browser that is used to access the music server 128.
  • the music renderers 126A-126N includes a network browser and can connect directly to the network 120.
  • a user that is accessing the client computer 104 may utilize the network browser to remotely access a control program that is executing at the music server 128.
  • the user can electronically request, via the network browser, the music server 128 to transmit selected music items from the music server 128 to the client computer 104.
  • the music items can either be a music track, a folder comprising multiple music tracks, or some other logical grouping of musical sounds.
  • the electronic request from the client computer 104 ( Figure 1) can correspond to one of any number of network protocols.
  • the electronic request comprises a Hypertext Transfer Protocol (HTTP) request.
  • HTTP Hypertext Transfer Protocol
  • the network configuration 100 can include large numbers of such devices, e.g., millions. It is also noted that only one music server 128 is shown, the network configuration 100 can include a large number of such servers. Furthermore, the music server 128 can include a number of computers that work collaboratively to provide music in response to requests from the client computer 104.
  • the network 120 may include any type of electronically connected group of computers including, for instance, the following networks: a virtual private network, a public Internet, a private Internet, a secure Internet, a private network, a public network, a value-added network, an intranet, and the like.
  • the connectivity to the network may be, for example, remote modem, Ethernet (IEEE 802.3), Token Ring (IEEE 802.5), Fiber Distributed Datalink Interface (FDDI) or Asynchronous Transfer Mode (ATM).
  • the network 120 may connect to the client computer 104, for example, by use of a modem or by use of a network interface card that resides in the client computer 104.
  • control program of the music server 128, the network interface 140, the music player 144, the music renderer controller 148, and the device drivers 152A- 152M may each comprise various sub-routines, procedures, definitional statements, and macros.
  • Each of the foregoing modules may be separately compiled and linked into a single executable program.
  • the processes that are performed by selected ones of the modules may be arbitrarily redistributed to one of the other modules, combined together in a single module, made available in a shareable dynamic link library, or partitioned in any other logical way.
  • the music player 144 and the music renderer controller 148 are integrated into a single executable module.
  • the device drivers 152A-125N are maintained in a dynamic link library that is separate from the music player 144 and the music renderer controller 148.
  • the music renderer controller 148, and the device drivers 152A-152M may be written in any programming language such as C, C++, BASIC, Pascal, Java, and FORTRAN and ran under the well-known operating system.
  • C, C++, BASIC, Pascal, Java, and FORTRAN are industry standard programming languages for which many commercial compilers can be used to create executable code.
  • the control program of the music server 128, the network interface 140, the music player 144, the music renderer controller 148, and the device drivers 152A-152M can be either an "application program", reside as part of the operating system for the device, or can reside partly in both.
  • Figure 2 is a block diagram illustrating the relationship between the music renderers 126A-126N and a plurality of storage devices 204A-204T.
  • the storage devices 204A-204T may be integrated with one or more of the media renderers 126A-126N or alternatively, connected directly or indirectly to the client computer 104.
  • the storage devices 204A-204T can comprise non-volatile random access memory, flash memory, or a mass storage, such as is found in a hard drive.
  • each of the storage devices 204A-204T is associated with a device object, e.g., one of the device drivers 152A-152M. Furthermore, in this embodiment, each of the storage devices 204A-204T is associated with a storage object.
  • the device object defines an interface for transmitting music items to the music renderer.
  • the storage object defines an interface for performing storage functions on the associated storage device.
  • Figure 3 is a block diagram illustrating certain API's of the device drivers 152A-152M.
  • the music renderer controller 148 can communicate with the device drivers 152A-152N. Since the API's are predefined and may be made publicly available, a device manufacturer can develop music renderers and device drivers for integration and connection to the music renderer controller 148 and the music player 144.
  • each of the device drivers 152A-152M provides one or more of the following interfaces: a window pane interface 304, a command interface 308, and a customize interface name interface 312. By invoking or "calling" one of the entry points, the music renderer controller 148 and the device drivers
  • the device drivers 152A-152M can communicate with each other. It is noted that depending on the embodiment, the device drivers 152A-152M may have additional or fewer interfaces than are illustrated in Figure 3.
  • a device driver may invoke the identify window interface 304 to provide the music player 144 a pointer to a window object.
  • the music player 144 may invoke the window object to perform various functions on a graphical interface, e.g., window, such as requesting the music player 144 to resize the graphical interface, hide the graphical interface, or display the graphical interface.
  • a device driver can seamlessly integrate any new control, notification, windows into the music renderer that, depending on the features of the music renderer, may be required.
  • the device driver can implement and display a general information window.
  • the general information window may comprise general information about a music renderer and contains "links" to additional information about the music renderer.
  • the generation information window could also provide contact information for obtaining support for the music renderer.
  • the device driver can display the following information: statistical information about the music renderer, advertisements, technical information, and flight recorder logs of past actions.
  • the device driver can provide controls for the music renderer. As non- limiting examples, the device driver can provide: searching capabilities for music items, associate notes with music items, and advanced editing controls.
  • the music player 144 invokes the window(s) that are provided by the device drivers 152A-152M upon the occurrence of pre-defined events.
  • the events can include: receiving a request to transmit a music item to one of the music renderers, the passage of a predetermined period of time, and receiving the request of a user.
  • a device driver may invoke the command interface 306 to send one or more predefined commands to the music player.
  • the predefined commands include enabling playback and disabling playback.
  • a device driver can inform the music player 144 of its intentions. For example, the process of "burning" a compact diskette is very time intensive and if the process is interrupted, the resulting audio compact diskette becomes useless.
  • a CD-burning device driver can inform the music player 144 that the CD burner is about to start a burn and that the music player 144 should stop and disable playback of all music until the process is complete.
  • a device driver may invoke the customize interface name interface 312 to customize any button, control, or textual element that is displayed by the music generator.
  • a button for "begin transfer" does not describe the process of burning a CD.
  • the device driver for the CD burner can rename the button to something more descriptive such as "begin CD burn.”
  • each of the device drivers can only rename those buttons, controls, or textual elements that are associated with transmitting data to and from the music renderer that is controlled by the device driver.
  • Figure 4 is an exemplary screen display 400 that is presented to a user by the music player 144 ( Figure 1) via an output device of the client computer 104.
  • a user may: (i) play music that resides either on the client computer 104 or one of the music renderers 126A-126N; (ii) copy or move music items from the client computer 104 to one of the music renderers 126A-126N; (iii) copy or move music items from one of the music renderers 126A-126N to the client computer 104; (iv) copy or move music items from one music renderer to another music renderer; (v) install new music renderers; (vi) organize music into playlists; and (vii) download music from the music server 128 ( Figure 1).
  • the screen display 400 includes a library window 404 and an information window 408.
  • the library window 404 includes a hierarchical graphical library tree 412 that organizes and classifies the music on the client computer 104 and the music renderers 126A-126N.
  • the hierarchical graphical library tree 412 is comprised of a plurality of graphical nodes, each of the nodes (except root nodes) having one parent node and zero or more children nodes. Each of the nodes has an associated icon and/or text that is displayed to the user.
  • the icon and/or text of a node identifies a classification that is associated with each of the children of the node. For example, as is described in further detail below, a node can be used to group music items according to author, album, or subject matter.
  • the hierarchical graphical library tree 412 includes three root nodes, namely, a master library node 416, a playlist node 420, and a music renderer node 424.
  • the master library node 416 has four children, namely, an artist node 428, an album node 432, a genre node 436, and an all tracks node 442.
  • the children of the artist node 428 are nodes that identify the names of various authors. For example, as is shown in Figure 4, the user has music tracks from two different authors: Anastasia Khitul and the Blues Fools. By selecting one of the children nodes of the artist node 428, the user is presented via the information window 408 a list of all of the tracks that are associated with the selected artist.
  • the children of the album node 432 are nodes that identify the names of each of the albums that are maintained by the music player 144. As defined herein, an album is association of music or sound tracks. By selecting one of the children nodes of the album node 428, the user is presented via the information window 408 a list of all of the tracks that are associated with the selected album.
  • the children of the genre node 436 identify the names of one or more genres of music.
  • the children of the genre node 436 can include: blues, classical, rock and roll, country, hip hop, etc.
  • the user is presented in the information window 408 a list of all of the tracks that are associated with the selected genre.
  • the all tracks node 442 of the genre node 428 the user is presented in the information window 408 a list of all of the tracks that are maintained by the music player 144.
  • the playlist node 420 has as its children each of the playlists that have been created by the user of the client computer 104. As defined herein, a playlist is defined as a logical grouping of songs. Upon selecting one of the children nodes of the playlist node 420, the user is presented in the information window
  • a list of all of the tracks that are associated with playlist The user can select a particular playlist and request the music player 144 to render each of the tracks that are associated with the playlist.
  • the music player 144 Upon selecting a new playlist button 440, the music player 144 enters a playlist mode wherein the user is allowed to prepare a new playlist, the new playlist associating together selected tracks that are maintained by the music player 144.
  • the music renderer node 424 has as its children a group of nodes that are each respectively labeled with the names of the music renderers 126A-126N. Upon selecting one of the children nodes of the music renderer node 424, the user is presented in the information window 408 a list of all of the tracks that are maintained by the selected music renderer. Using one of the input devices of the client computer 104, the user can copy or move one of the nodes and all of the descendants of that node from a first part of the hierarchical graphical library tree to another. For example, the user can move all of the tracks that are associated with a blues genre node to a portable device.
  • the user can copy a playlist from the client computer 104 to one of the music renderers 126A-126N by selecting the playlist and "dragging" the playlist via one of the input devices of the client computer 104 to one of children of the music renderer node 424.
  • the term dragging refers to manipulating a graphical object on a display from a first location to a second location.
  • FIG. 5 is a high level flowchart illustrating a process for managing music items on the music renderers 126A-126N.
  • the music player 144 communicates with the music renderer controller 148 to request that all of the music renderers be initialized.
  • the music renderer controller 148 proceeds to a step 504.
  • the music renderer controller 148 initializes any pre-registered device drivers.
  • the music player 144 displays to a user a control window, such as is shown in Figure 4.
  • the control window allows the user to perform various acts with respect to the music items that are stored on the client computer 104 and on the music renderers 126A-126N.
  • the music player 144 can, depending on the user's preference, proceed to either the steps 512, 516, 520, or 524.
  • the user can move or copy music tracks amongst the client computer 104 and the music renderers 126A-126N.
  • the user can: (i) move or copy one or more selected music items from the client computer 104 to one of the music renderers 126A-126N; (ii) move or copy one more selected music items from one music renderer to another music renderer; or (iii) more or copy music items from one of the music renderers 126A-126N to the client computer.
  • a transfer screen 600 upon requesting to transfer music items to or from one of the music renders, a transfer screen 600, such as is shown in Figure 6 is displayed to the user.
  • the transfer screen 600 comprises a music transfer window 602 and a control portion 604.
  • the music transfer window 602 lists the music items that are stored in a mass storage device on the client computer 104. Using an input device, one or more of the music items shown in the music transfer window 602 may be selected by the user.
  • the control portion 604 is maintained by the device driver for the respective window.
  • the device driver for the respective music renderer can display customized control icons for the music renderer. It is noted that the identify window pane interface 304 can be used in other contexts with respect to the music renderer and the music player 144.
  • the control portion 604 comprises a play button 608, a stop button 612, a begin transfer button 616, re-size window buttons 618, and an import button 620.
  • Selecting the play button 604 starts playback of a selected music item shown in the music transfer window 602.
  • Selecting the stop button stops playback of the selected music item.
  • Selecting begin transfer button 616 begins the transfer of data from the mass storage device to the music render.
  • Selecting the resize window buttons 618 causes the size of the control portion 604 to be increased or decreased.
  • Selecting the import button 620 allows the user to import a music item from a selected location in the client computer 144.
  • the buttons, text, and fields, shown in the control portion 622 are for exemplary purposes, and that each device driver can customize the control portion depending on the requirement of the music renderer that is being managed by the device driver.
  • a device driver can customize the text that is shown by the music player 144. For example, in one embodiment of the invention, during the transfer of a music item from the client computer 144 to one of the music renderers 126A-126N, the state of the transfer is displayed to the user. By invoking the customize interface name interface 312, the device driver can rename the description of the state Upon copying the music items to a selected music renderer, the music items are automatically transcoded and transcrypted depending on the requirements of the selected music renderer. For example, assume the user desires to copy one or more music items from the client computer 104 to the music renderer 126B.
  • the client computer 104 maintains the music items as MP3 format and the music renderer 126B stores music items according to a proprietary format.
  • the user indicates his desire for copying the selected music items by dragging the selected music items to the respective node of the music renderer in the hierarchical classification tree 412 ( Figure 4).
  • the device driver reformats the music items to the appropriate format and transmits the formatted music item to the respective device driver for the selected music renderer 126B. It is noted that if the music items was a group of music tracks, i.e., a folder, the music player 144 formats each of the music tracks within the group before transmitting the tracks to the device driver.
  • the device driver then stores the tracks according to any preferences that have been specified by the user, e.g., with or without lyrics, with graphical icons, etc.
  • the process flow then returns to the step 508, whereby the user can select another option, or alternatively, stop the music player 144.
  • the process flow proceeds to a step 516.
  • the music player 144 plays via an output device of the client computer 104 one or more music items that have been selected by the user.
  • the process flow then returns to the step 508, whereby the user can select another option, or alternatively, stop the music player
  • the process flow proceeds to a step 520.
  • the user can request to install a new music renderer.
  • the user upon the request to install a new music renderer, the user is provided a list of music renderers that are supported by the music player 144.
  • the music player 144 may automatically or, alternatively, upon a user request, retrieve a list of music renderers that are supported by the music player 144.
  • the music player 144 identifies the location of a device driver for the selected music renderer. The location of the device driver for the selected music renderer can either be provided by the user or alternatively be maintained by the music server 128.
  • the client computer 104 requests another computer that is connected to the network 120 to transmits the device driver to the client computer 104.
  • the music player 144 requests the user to insert program storage device, such as a compact diskette, so that the music player 144 may copy the device driver to the client computer 104.
  • the device driver is dynamically linked to the music renderer controller 148. Furthermore, the music player 144 registers the device driver in an internal registry so that the music player 144 will initialize the device driver upon future invocations of the music player 144. The process flow then returns to the step 508, whereby the user can select another option, or alternatively, stop the music player 144.
  • the music player 144 enters a playlist mode that allows the user to organize the music items on the client computer 104 and the music renderers 208A-208N.
  • the user can group selected music items into a playlist.
  • the process flow then returns to the step 508, whereby the user can select another option, or alternatively, stop the music player 144.
  • a music renderer controller 148 that is designed to communicate with device drivers by a predefined interface, i.e., the DIAPI, one or more new device drivers can be added at later date and can communicate with the music player 144.
  • the interface to the music player 144 is independent on the particular characteristics of each of the music renderers 126A-126N.
  • the DIAPI of the music renderer controller 148 gives the music renderer manufacturers flexibility to define what actions can be performed with respect to the music renderer. Furthermore, by using the DIAPI, changes in firmware of one of the music renderers 126A-126N do not necessitate changes in the electronic music player 144. If additional features are provided with respect to one the music renderers 126A-126N, a new device driver may be created to communicate with the music renderer controller 148 and thereby allow the user to take advantage of such new features without requiring a re-design of the music player.

Abstract

One embodiment of the system comprises an electronic music player (144) that is connected to a plurality of music renderers (126A...N) via device drivers (152A...M) via a music renderer controller (148). The music renderer controller (148) comprises a device integration application program interface for providing a standard interface for communicating with each of the device drivers (152A...M). Each of the device drivers (152A...M) manage a selected music renderer (126A...N). The device drivers (152A...M) can display a graphical interface for displaying notifications, customized controls, links to websites, or any other type of information desired by the manufacturer of the device driver. The device drivers (152A...M) can also customize the interfaces of the music render to rename textual elements that are displayed by the device driver. Furthermore, the device drivers (152A...M) can command the music player (144) to suspend and resume playback of music items during selected periods.

Description

A SYSTEM AND METHOD OF PROVIDING FOR THE CONTROL OF A MUSIC PLAYER TO A DEVICE DRIVER
Background of the Invention Field of the Invention
The field of the invention relates to music renderers. More particularly, the field of the invention relates to providing music items to music renderers. Description of the Related Technology
With the advent of new music storage formats, such as MPEG Audio Layer 3 (MP3), the music industry has seen a remarked increase with respect to individuals using their home computer for playing music and individuals purchasing new types of music renderers, such as portable music devices, for playing music.
Using these new music storage formats, it is possible to shrink the sound data from sources such as a compact diskette (CD) without sacrificing sound quality. CDs typically render music at about 1400 kilobits per one second of stereo music. However, by converting data from a CD to another data format, such as
MP3, the size of the data can be shrunk by a factor of about 12 without significantly sacrificing the quality of the music.
Many individuals use the Internet to find and download music in these new formats to their personal computer. At the personal computer, the user can, via a playback device program, play, edit, or copy the downloaded music. Furthermore, from the personal computer, the user can download the music to a portable music player so that the downloaded music can be played wherever the user travels. Portable music players, such as the Diamond Rio 500, allow individuals store up to two hours of digital-quality music and up to 32 hours of spoken audio programs. The Diamond Rio includes 64MB onboard memory, expandable to 96MB with removable flash cards. Most music players provide a certain core group of features, such as playing and recording music.
However, other than the core group, it is difficult to predict all of the features that will be supported by the music players. As hypothetical examples, optional features can include: providing compact diskette "burning", providing storage library hierarchies for music items, associating notes with music items, etc. Thus, since these features are not anticipated, the features are not supported by many legacy playback device programs. To overcome this problem, as new features are introduced, the playback device programs are redesigned by the provider of the playback device program to provide support for the new features. Disadvantageously, the redesign takes time. Furthermore, the new version of the music player must be transmitted to the user. Both of these events are an inconvenience for the user.
Thus, there is a need for a music player that can take advantage of newly developed features of music renderers. Furthermore, the music player should not have to be redesigned to support the new features. Summary of the Invention One embodiment of the invention comprises a method of providing a customized graphical interface, the method comprising executing a music player that displays a graphical interface comprising information about music items, and displaying a customized graphical interface for managing the music items, wherein the content of the customized graphical interface is defined by a device driver for a music renderer, and wherein the displaying of the customized graphical interface is in response to an event occurring during the execution of the music player.
Another embodiment of the invention comprises a system for providing a customized graphical interface, the system comprising a music player for displaying one or more graphical interfaces that comprise information about music items, a music renderer, and a device driver for sending music items to the music renderer, wherein the device driver displays a customized graphical interface for managing the music items, and wherein the content of the customized graphical interface is defined by the device driver.
Another embodiment of the invention comprises a system for providing a customized graphical interface, the system comprising means for executing a music player that displays a graphical interface comprising information about music items, and means for displaying a customized graphical interface for managing the music items, wherein the content of the customized graphical interface is defined by a device driver for a music renderer, and wherein the displaying of the customized graphical interface is in response to an event occurring during the execution of the music player.
Another embodiment of the invention comprises a method of providing a customized graphical interface, the method comprising executing a music player that displays a graphical interface comprising information about a plurality of music items, wherein the graphical interface comprises one or more textual elements describing an aspect of the music player, and receiving a request from a device driver to change the textual element.
Another embodiment of the invention comprises a system for providing a customized graphical interface, the system comprising a music player displaying a graphical interface comprising information about a plurality of music items, wherein the graphical interface comprises one or more textual elements describing an aspect of the music player, the music player adapted to receive requests from a device driver to rename the textual elements.
Another embodiment of the invention comprises a method of controlling a music player, the method comprising executing a music player that plays music items upon a request from a user, receiving a request from a device driver to disallow playback of the music items, and suspending playback of the music items on the music player.
Brief Description of the Drawings Figure 1 is a high level block diagram illustrating one embodiment of a network configuration that may be used in connection with a music system, the music system comprising a server computer, a client computer, a music player, a music renderer controller, a plurality of music renderers, and a plurality of the device drivers that are associated respectively with selected ones of the music renderers.
Figure 2 is block diagram illustrating the relationship between the music renderers of Figure 1 and a plurality of storage devices that are associated with the music renders. Figure 3 is a block diagram illustrating a plurality of interfaces between the music controller of Figure
1 and each of the device drivers of Figure 1.
Figure 4 is a screen display illustrating an exemplary control panel for organizing the music items that are maintained by the client computer of Figure 1.
Figure 5 is a flowchart illustrating a process of utilizing the music player of Figure 1. Figure 6 is a screen display illustrating an exemplary customized window that is displayed by one of the device drivers of Figure 1.
Detailed Description of Embodiments of the Invention The following detailed description is directed to certain specific embodiments of the invention. However, the invention can be embodied in a multitude of different ways as defined and covered by the claims. In this description, reference is made to the drawings wherein like parts are designated with like numerals throughout.
Referring to Figure 1, an exemplary network configuration 100 of the music system of the present invention will be described. A user communicates with a computing environment which may include a client computer 104, a network 120, music renderers 126A-126N, and a music server 128. The client computer 104 and each of the music renderers 126A-126N has an associated input and output device. For example, the input device may be a keyboard, rollerball, pen and stylus, mouse, voice recognition system, or predesignated switches or buttons. The input device may also be a touch screen associated with an output device. The user may respond to prompts on the display by touching the touch screen. Textual or graphic information may be entered by the user through the input device. The output device can comprise a speaker, a display screen, a printer, or a voice synthesizer.
The client computer 104, the music server 128, and the music renderers 126A-126N may each have any conventional general purpose single- or multi-chip microprocessor such as a Pentium® processor, a Pentium® Pro processor, a 8051 processor, a MIPS® processor, a Power PC® processor, or an ALPHA® processor. In addition, the microprocessor may be any conventional special purpose microprocessor such as a digital signal processor. Furthermore, the client computer 104, the music server 128, and each of the music renderers 126A-126N may each be used in connection with various operating systems such as: UNIX, LINUX, Disk Operating System (DOS), VxWorks, PalmOS, OS/2, Windows CE, Windows 3.X, Windows 95, Windows 98, and Windows NT.
The music renderers 126A-126N can comprise a stationary device, such as a stereo system, or, alternatively, a portable device, such as a Diamond RIO, a RCA Lyra, a portable radio, or a personal display adapter. Still referring to Figure 1, the client computer 104 comprises a network interface 140, an electronic music player 144, a music renderer controller 148, and device drivers 152A-152M. The network interface 140 communicates with a control program of the music server 128 via the network 120. As is discussed in further detail below, using the music player 144, a user can communicate with the music server 128 to download and play songs via the output device of the client computer 104. Furthermore, using the electronic music player 144, a user can organize the songs according to subject matter and also download the songs to one of the music renderers 126A-126N. As defined herein, a device driver is a software program, module, procedure, or executable, that is capable of communicating with a music renderer, the device driver being adapted to "plug- in" and be operably connected to the music player 144. The music renderer controller 148 controls communications between the music player 144 and the device drivers 152A-152M. The music renderer controller 148 comprises a device integration application program interface (DIAPI) that provides a predefined interface for communicating with the device drivers 152A-152M. Using the DIAPI, programmers can develop new device drivers 152A-152M for integration within the client computer 104. In one embodiment of the invention, the DIAPI is based upon the Component Object Model (COM), which was developed by Microsoft Inc. of Redmond Washington. The DIAPI is described in further detail below with reference to Figure 3.
In one embodiment of the network configuration 100, the client computer 104 includes a network browser that is used to access the music server 128. In another embodiment of the invention, the music renderers 126A-126N includes a network browser and can connect directly to the network 120. A user that is accessing the client computer 104 may utilize the network browser to remotely access a control program that is executing at the music server 128. The user can electronically request, via the network browser, the music server 128 to transmit selected music items from the music server 128 to the client computer 104. The music items can either be a music track, a folder comprising multiple music tracks, or some other logical grouping of musical sounds. The electronic request from the client computer 104 (Figure 1) can correspond to one of any number of network protocols. In one embodiment of the invention, the electronic request comprises a Hypertext Transfer Protocol (HTTP) request. However, it is to be appreciated that other types of network communication protocols may be used.
It is noted that although only one client computer 104 and three music renderers 126A-126N are shown in Figure 1 , the network configuration 100 can include large numbers of such devices, e.g., millions. It is also noted that only one music server 128 is shown, the network configuration 100 can include a large number of such servers. Furthermore, the music server 128 can include a number of computers that work collaboratively to provide music in response to requests from the client computer 104.
The network 120 may include any type of electronically connected group of computers including, for instance, the following networks: a virtual private network, a public Internet, a private Internet, a secure Internet, a private network, a public network, a value-added network, an intranet, and the like. In addition, the connectivity to the network may be, for example, remote modem, Ethernet (IEEE 802.3), Token Ring (IEEE 802.5), Fiber Distributed Datalink Interface (FDDI) or Asynchronous Transfer Mode (ATM). The network 120 may connect to the client computer 104, for example, by use of a modem or by use of a network interface card that resides in the client computer 104.
As can be appreciated by one of ordinary skill in the art, the control program of the music server 128, the network interface 140, the music player 144, the music renderer controller 148, and the device drivers 152A- 152M may each comprise various sub-routines, procedures, definitional statements, and macros. Each of the foregoing modules may be separately compiled and linked into a single executable program. However, it is to be appreciated by one of ordinary skill in the art that the processes that are performed by selected ones of the modules may be arbitrarily redistributed to one of the other modules, combined together in a single module, made available in a shareable dynamic link library, or partitioned in any other logical way. For example, in one embodiment of the invention, the music player 144 and the music renderer controller 148 are integrated into a single executable module. Furthermore, for example, in another embodiment, the device drivers 152A-125N are maintained in a dynamic link library that is separate from the music player 144 and the music renderer controller 148. Furthermore, the control program of the music server 128, the network interface 140, the music player
144, the music renderer controller 148, and the device drivers 152A-152M may be written in any programming language such as C, C++, BASIC, Pascal, Java, and FORTRAN and ran under the well-known operating system. C, C++, BASIC, Pascal, Java, and FORTRAN are industry standard programming languages for which many commercial compilers can be used to create executable code. Furthermore, the control program of the music server 128, the network interface 140, the music player 144, the music renderer controller 148, and the device drivers 152A-152M can be either an "application program", reside as part of the operating system for the device, or can reside partly in both.
Figure 2 is a block diagram illustrating the relationship between the music renderers 126A-126N and a plurality of storage devices 204A-204T. The storage devices 204A-204T may be integrated with one or more of the media renderers 126A-126N or alternatively, connected directly or indirectly to the client computer 104. For example, the storage devices 204A-204T can comprise non-volatile random access memory, flash memory, or a mass storage, such as is found in a hard drive.
In one embodiment of the invention, each of the storage devices 204A-204T is associated with a device object, e.g., one of the device drivers 152A-152M. Furthermore, in this embodiment, each of the storage devices 204A-204T is associated with a storage object. The device object defines an interface for transmitting music items to the music renderer. The storage object defines an interface for performing storage functions on the associated storage device.
Figure 3 is a block diagram illustrating certain API's of the device drivers 152A-152M. Using the API's, the music renderer controller 148 can communicate with the device drivers 152A-152N. Since the API's are predefined and may be made publicly available, a device manufacturer can develop music renderers and device drivers for integration and connection to the music renderer controller 148 and the music player 144.
As is shown in Figure 3, each of the device drivers 152A-152M provides one or more of the following interfaces: a window pane interface 304, a command interface 308, and a customize interface name interface 312. By invoking or "calling" one of the entry points, the music renderer controller 148 and the device drivers
152A-152M can communicate with each other. It is noted that depending on the embodiment, the device drivers 152A-152M may have additional or fewer interfaces than are illustrated in Figure 3.
A device driver may invoke the identify window interface 304 to provide the music player 144 a pointer to a window object. The music player 144 may invoke the window object to perform various functions on a graphical interface, e.g., window, such as requesting the music player 144 to resize the graphical interface, hide the graphical interface, or display the graphical interface. Advantageously, a device driver can seamlessly integrate any new control, notification, windows into the music renderer that, depending on the features of the music renderer, may be required.
For example, if desired, the device driver can implement and display a general information window. The general information window may comprise general information about a music renderer and contains "links" to additional information about the music renderer. The generation information window could also provide contact information for obtaining support for the music renderer. As other non-limiting examples, the device driver can display the following information: statistical information about the music renderer, advertisements, technical information, and flight recorder logs of past actions. Furthermore, for example, the device driver can provide controls for the music renderer. As non- limiting examples, the device driver can provide: searching capabilities for music items, associate notes with music items, and advanced editing controls.
The music player 144 invokes the window(s) that are provided by the device drivers 152A-152M upon the occurrence of pre-defined events. As examples, the events can include: receiving a request to transmit a music item to one of the music renderers, the passage of a predetermined period of time, and receiving the request of a user.
Referring again to Figure 3, a device driver may invoke the command interface 306 to send one or more predefined commands to the music player. In one embodiment of the invention, the predefined commands include enabling playback and disabling playback. Advantageously, a device driver can inform the music player 144 of its intentions. For example, the process of "burning" a compact diskette is very time intensive and if the process is interrupted, the resulting audio compact diskette becomes useless. Using the command interface 306, a CD-burning device driver can inform the music player 144 that the CD burner is about to start a burn and that the music player 144 should stop and disable playback of all music until the process is complete. A device driver may invoke the customize interface name interface 312 to customize any button, control, or textual element that is displayed by the music generator. For example, a button for "begin transfer" does not describe the process of burning a CD. Thus, the device driver for the CD burner can rename the button to something more descriptive such as "begin CD burn." In one embodiment of the invention, to prevent a renaming conflict between two of the device drivers, each of the device drivers can only rename those buttons, controls, or textual elements that are associated with transmitting data to and from the music renderer that is controlled by the device driver.
Figure 4 is an exemplary screen display 400 that is presented to a user by the music player 144 (Figure 1) via an output device of the client computer 104. Using the screen display 400, a user may: (i) play music that resides either on the client computer 104 or one of the music renderers 126A-126N; (ii) copy or move music items from the client computer 104 to one of the music renderers 126A-126N; (iii) copy or move music items from one of the music renderers 126A-126N to the client computer 104; (iv) copy or move music items from one music renderer to another music renderer; (v) install new music renderers; (vi) organize music into playlists; and (vii) download music from the music server 128 (Figure 1).
The screen display 400 includes a library window 404 and an information window 408. The library window 404 includes a hierarchical graphical library tree 412 that organizes and classifies the music on the client computer 104 and the music renderers 126A-126N. The hierarchical graphical library tree 412 is comprised of a plurality of graphical nodes, each of the nodes (except root nodes) having one parent node and zero or more children nodes. Each of the nodes has an associated icon and/or text that is displayed to the user. The icon and/or text of a node identifies a classification that is associated with each of the children of the node. For example, as is described in further detail below, a node can be used to group music items according to author, album, or subject matter.
In one embodiment of the invention, the hierarchical graphical library tree 412 includes three root nodes, namely, a master library node 416, a playlist node 420, and a music renderer node 424. Furthermore, in one embodiment, the master library node 416 has four children, namely, an artist node 428, an album node 432, a genre node 436, and an all tracks node 442. The children of the artist node 428 are nodes that identify the names of various authors. For example, as is shown in Figure 4, the user has music tracks from two different authors: Anastasia Khitul and the Blues Fools. By selecting one of the children nodes of the artist node 428, the user is presented via the information window 408 a list of all of the tracks that are associated with the selected artist.
The children of the album node 432 are nodes that identify the names of each of the albums that are maintained by the music player 144. As defined herein, an album is association of music or sound tracks. By selecting one of the children nodes of the album node 428, the user is presented via the information window 408 a list of all of the tracks that are associated with the selected album.
The children of the genre node 436 identify the names of one or more genres of music. For example, the children of the genre node 436 can include: blues, classical, rock and roll, country, hip hop, etc. Upon selecting one of the children nodes of the genre node 428, the user is presented in the information window 408 a list of all of the tracks that are associated with the selected genre. Upon selecting the all tracks node 442 of the genre node 428, the user is presented in the information window 408 a list of all of the tracks that are maintained by the music player 144.
The playlist node 420 has as its children each of the playlists that have been created by the user of the client computer 104. As defined herein, a playlist is defined as a logical grouping of songs. Upon selecting one of the children nodes of the playlist node 420, the user is presented in the information window
408 a list of all of the tracks that are associated with playlist. The user can select a particular playlist and request the music player 144 to render each of the tracks that are associated with the playlist.
Upon selecting a new playlist button 440, the music player 144 enters a playlist mode wherein the user is allowed to prepare a new playlist, the new playlist associating together selected tracks that are maintained by the music player 144.
The music renderer node 424 has as its children a group of nodes that are each respectively labeled with the names of the music renderers 126A-126N. Upon selecting one of the children nodes of the music renderer node 424, the user is presented in the information window 408 a list of all of the tracks that are maintained by the selected music renderer. Using one of the input devices of the client computer 104, the user can copy or move one of the nodes and all of the descendants of that node from a first part of the hierarchical graphical library tree to another. For example, the user can move all of the tracks that are associated with a blues genre node to a portable device. Furthermore, for example, the user can copy a playlist from the client computer 104 to one of the music renderers 126A-126N by selecting the playlist and "dragging" the playlist via one of the input devices of the client computer 104 to one of children of the music renderer node 424. As is appreciated by one of ordinary skill in the art, the term dragging refers to manipulating a graphical object on a display from a first location to a second location.
Figure 5 is a high level flowchart illustrating a process for managing music items on the music renderers 126A-126N. Before starting at a start step 500, the user has executed the music player 144. The music player 144 communicates with the music renderer controller 148 to request that all of the music renderers be initialized. After starting at a step 500, the music renderer controller 148 proceeds to a step 504. At the step 504, the music renderer controller 148 initializes any pre-registered device drivers.
Next, at a step 508, the music player 144 displays to a user a control window, such as is shown in Figure 4. The control window allows the user to perform various acts with respect to the music items that are stored on the client computer 104 and on the music renderers 126A-126N. From the step 508, the music player 144 can, depending on the user's preference, proceed to either the steps 512, 516, 520, or 524. At the step 512, the user can move or copy music tracks amongst the client computer 104 and the music renderers 126A-126N. For example, the user can: (i) move or copy one or more selected music items from the client computer 104 to one of the music renderers 126A-126N; (ii) move or copy one more selected music items from one music renderer to another music renderer; or (iii) more or copy music items from one of the music renderers 126A-126N to the client computer. In one embodiment of the invention, upon requesting to transfer music items to or from one of the music renders, a transfer screen 600, such as is shown in Figure 6 is displayed to the user.
The transfer screen 600 comprises a music transfer window 602 and a control portion 604. The music transfer window 602 lists the music items that are stored in a mass storage device on the client computer 104. Using an input device, one or more of the music items shown in the music transfer window 602 may be selected by the user.
The control portion 604 is maintained by the device driver for the respective window. By utilizing the identify window pane interface 304 (Figure 3), the device driver for the respective music renderer can display customized control icons for the music renderer. It is noted that the identify window pane interface 304 can be used in other contexts with respect to the music renderer and the music player 144.
As is shown for exemplary purposes in Figure 6, the control portion 604 comprises a play button 608, a stop button 612, a begin transfer button 616, re-size window buttons 618, and an import button 620. Selecting the play button 604 starts playback of a selected music item shown in the music transfer window 602. Selecting the stop button stops playback of the selected music item. Selecting begin transfer button 616 begins the transfer of data from the mass storage device to the music render. Selecting the resize window buttons 618 causes the size of the control portion 604 to be increased or decreased. Selecting the import button 620 allows the user to import a music item from a selected location in the client computer 144. The buttons, text, and fields, shown in the control portion 622 are for exemplary purposes, and that each device driver can customize the control portion depending on the requirement of the music renderer that is being managed by the device driver.
Furthermore, a device driver can customize the text that is shown by the music player 144. For example, in one embodiment of the invention, during the transfer of a music item from the client computer 144 to one of the music renderers 126A-126N, the state of the transfer is displayed to the user. By invoking the customize interface name interface 312, the device driver can rename the description of the state Upon copying the music items to a selected music renderer, the music items are automatically transcoded and transcrypted depending on the requirements of the selected music renderer. For example, assume the user desires to copy one or more music items from the client computer 104 to the music renderer 126B. Furthermore, assume the client computer 104 maintains the music items as MP3 format and the music renderer 126B stores music items according to a proprietary format. The user indicates his desire for copying the selected music items by dragging the selected music items to the respective node of the music renderer in the hierarchical classification tree 412 (Figure 4). If the music item should be converted, the device driver reformats the music items to the appropriate format and transmits the formatted music item to the respective device driver for the selected music renderer 126B. It is noted that if the music items was a group of music tracks, i.e., a folder, the music player 144 formats each of the music tracks within the group before transmitting the tracks to the device driver. The device driver then stores the tracks according to any preferences that have been specified by the user, e.g., with or without lyrics, with graphical icons, etc. The process flow then returns to the step 508, whereby the user can select another option, or alternatively, stop the music player 144.
Referring again to the step 508 (Figure 5), if the user requests to play one of the music items, the process flow proceeds to a step 516. At the step 516, the music player 144 plays via an output device of the client computer 104 one or more music items that have been selected by the user. The process flow then returns to the step 508, whereby the user can select another option, or alternatively, stop the music player
144.
Referring again to the step 508, if the user requests to install a new device, the process flow proceeds to a step 520. At the step 520, the user can request to install a new music renderer. In one embodiment of the invention, upon the request to install a new music renderer, the user is provided a list of music renderers that are supported by the music player 144. In this embodiment, the music player 144 may automatically or, alternatively, upon a user request, retrieve a list of music renderers that are supported by the music player 144. Upon the selection of a music renderer, the music player 144 identifies the location of a device driver for the selected music renderer. The location of the device driver for the selected music renderer can either be provided by the user or alternatively be maintained by the music server 128.
In one embodiment, if the device driver is not on the client computer 104, the client computer 104 requests another computer that is connected to the network 120 to transmits the device driver to the client computer 104. In another embodiment, the music player 144 requests the user to insert program storage device, such as a compact diskette, so that the music player 144 may copy the device driver to the client computer 104.
Once the device driver is in the client computer 104, the device driver is dynamically linked to the music renderer controller 148. Furthermore, the music player 144 registers the device driver in an internal registry so that the music player 144 will initialize the device driver upon future invocations of the music player 144. The process flow then returns to the step 508, whereby the user can select another option, or alternatively, stop the music player 144.
At the step 524, the music player 144 enters a playlist mode that allows the user to organize the music items on the client computer 104 and the music renderers 208A-208N. The user can group selected music items into a playlist. The process flow then returns to the step 508, whereby the user can select another option, or alternatively, stop the music player 144. Advantageously, by providing a music renderer controller 148 that is designed to communicate with device drivers by a predefined interface, i.e., the DIAPI, one or more new device drivers can be added at later date and can communicate with the music player 144. The interface to the music player 144 is independent on the particular characteristics of each of the music renderers 126A-126N.
The DIAPI of the music renderer controller 148 gives the music renderer manufacturers flexibility to define what actions can be performed with respect to the music renderer. Furthermore, by using the DIAPI, changes in firmware of one of the music renderers 126A-126N do not necessitate changes in the electronic music player 144. If additional features are provided with respect to one the music renderers 126A-126N, a new device driver may be created to communicate with the music renderer controller 148 and thereby allow the user to take advantage of such new features without requiring a re-design of the music player.
While the above detailed description has shown, described, and pointed out novel features of the invention as applied to various embodiments, it will be understood that various omissions, substitutions, and changes in the form and details of the device or process illustrated may be made by those skilled in the art without departing from the spirit of the invention. The scope of the invention is indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.

Claims

WHAT IS CLAIMED IS:
1. A method of providing a customized graphical interface, the method comprising: executing a music player that displays a graphical interface comprising information about music items; and displaying a customized graphical interface for managing the music items, wherein the content of the customized graphical interface is defined by a device driver for a music renderer, and wherein the displaying of the customized graphical interface is in response to an event occurring during the execution of the music player.
2. The method of Claim 1, wherein the customized graphical interface is a window having at least one control object.
3. The method of Claim 2, wherein the control object is a button.
4. The method of Claim 1 , wherein managing the plurality of music items comprises an act that is selected from the group comprising: playing a music item, copying a music item from a first location to a second location, and recording a music item.
5. The method of Claim 1 , wherein the event comprises receiving a request to transfer a music item from a storage device associated with the music player to a music renderer.
6. A system for providing a customized graphical interface, the system comprising: a music player for displaying one or more graphical interfaces that comprise information about music items; a music renderer; and a device driver for sending music items to the music renderer, wherein the device driver displays a customized graphical interface for managing the music items, and wherein the content of the customized graphical interface is defined by the device driver.
7. The system of Claim 6, wherein the customized graphical interface is a window having at least one control object.
8. The system of Claim 7, wherein the control object is a button.
9. The system of Claim 6, wherein managing the plurality of music items comprises an act that is selected from the group comprising: playing a music item, copying a music item from a first location to a second location, and recording a music item.
10. The system of Claim 6, wherein the event comprises receiving a request to transfer a music item from a storage device associated with the music player to a music renderer.
11. A system for providing a customized graphical interface, the system comprising: means for executing a music player that displays a graphical interface comprising information about music items; and means for displaying a customized graphical interface for managing the music items, wherein the content of the customized graphical interface is defined by a device driver for a music renderer, and wherein the displaying of the customized graphical interface is in response to an event occurring during the execution of the music player.
12. The system of Claim 11 , wherein the customized graphical interface is a window having at least one control object.
13. The system of Claim 12, wherein the control object is a button.
14. The system of Claim 11, wherein managing the plurality of music items comprises an act selected from the group comprising: playing a music item, copying a music item from a first location to a second location, and recording a music item.
15. The system of Claim 11, wherein the event comprises receiving a request to transfer a music item' from a storage device associated with the music player to a music renderer.
16. A method of providing a customized graphical interface, the method comprising: executing a music player that displays a graphical interface comprising information about a plurality of music items, wherein the graphical interface comprises one or more textual elements describing an aspect of the music player; and receiving a request from a device driver to change the textual element.
17. A system for providing a customized graphical interface, the system comprising: a music player displaying a graphical interface comprising information about a plurality of music items, wherein the graphical interface comprises one or more textual elements describing an aspect of the music player, the music player adapted to receive requests from a device driver to rename the textual elements.
18. A method of controlling a music player, the method comprising: executing a music player that plays music items upon a request from a user; receiving a request from a device driver to disallow playback of the music items; and suspending playback of the music items on the music player.
19. The method of Claim 18, additionally comprising: receiving a request from the music driver to allow playback of the music items; and resuming playback of the music items on the music player.
20. The method of Claim 18, additionally comprising burning a compact diskette with one or more of the music items, wherein the burning occurs subsequent to subsequent playback of the music items, and wherein resuming playback of the music items occurs subsequent to burning the compact diskette.
PCT/US2001/016230 2000-05-22 2001-05-18 A system and method of providing for the control of a music player to a device driver WO2001090871A2 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU2001263299A AU2001263299A1 (en) 2000-05-22 2001-05-18 A system and method of providing for the control of a music player to a device driver

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US09/577,257 2000-05-22
US09/577,257 US7237198B1 (en) 2000-05-22 2000-05-22 System and method of providing for the control of a music player to a device driver

Publications (2)

Publication Number Publication Date
WO2001090871A2 true WO2001090871A2 (en) 2001-11-29
WO2001090871A3 WO2001090871A3 (en) 2002-04-04

Family

ID=24307936

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2001/016230 WO2001090871A2 (en) 2000-05-22 2001-05-18 A system and method of providing for the control of a music player to a device driver

Country Status (3)

Country Link
US (5) US7237198B1 (en)
AU (1) AU2001263299A1 (en)
WO (1) WO2001090871A2 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9952824B2 (en) 2000-05-22 2018-04-24 Intel Corporation System and method of providing for the control of a music player to a device driver

Families Citing this family (62)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CA2201909C (en) 1994-10-12 2006-05-02 Technical Maintenance Corporation Intelligent digital audiovisual playback system
US7424731B1 (en) 1994-10-12 2008-09-09 Touchtunes Music Corporation Home digital audiovisual information recording and playback system
US7188352B2 (en) 1995-07-11 2007-03-06 Touchtunes Music Corporation Intelligent digital audiovisual playback system
US8661477B2 (en) 1994-10-12 2014-02-25 Touchtunes Music Corporation System for distributing and selecting audio and video information and method implemented by said system
FR2753868A1 (en) 1996-09-25 1998-03-27 Technical Maintenance Corp METHOD FOR SELECTING A RECORDING ON AN AUDIOVISUAL DIGITAL REPRODUCTION SYSTEM AND SYSTEM FOR IMPLEMENTING THE METHOD
FR2769165B1 (en) 1997-09-26 2002-11-29 Technical Maintenance Corp WIRELESS SYSTEM WITH DIGITAL TRANSMISSION FOR SPEAKERS
US20020002039A1 (en) 1998-06-12 2002-01-03 Safi Qureshey Network-enabled audio device
FR2781582B1 (en) 1998-07-21 2001-01-12 Technical Maintenance Corp SYSTEM FOR DOWNLOADING OBJECTS OR FILES FOR SOFTWARE UPDATE
FR2781580B1 (en) 1998-07-22 2000-09-22 Technical Maintenance Corp SOUND CONTROL CIRCUIT FOR INTELLIGENT DIGITAL AUDIOVISUAL REPRODUCTION SYSTEM
FR2781591B1 (en) 1998-07-22 2000-09-22 Technical Maintenance Corp AUDIOVISUAL REPRODUCTION SYSTEM
US8028318B2 (en) 1999-07-21 2011-09-27 Touchtunes Music Corporation Remote control unit for activating and deactivating means for payment and for displaying payment status
US8726330B2 (en) 1999-02-22 2014-05-13 Touchtunes Music Corporation Intelligent digital audiovisual playback system
FR2796482B1 (en) 1999-07-16 2002-09-06 Touchtunes Music Corp REMOTE MANAGEMENT SYSTEM FOR AT LEAST ONE AUDIOVISUAL INFORMATION REPRODUCING DEVICE
US7895610B1 (en) * 2000-01-18 2011-02-22 Koninklijke Philips Electronics N.V. System and method for displaying information on the screen of a user interface device under the control of a digital audio playback device
FR2805377B1 (en) 2000-02-23 2003-09-12 Touchtunes Music Corp EARLY ORDERING PROCESS FOR A SELECTION, DIGITAL SYSTEM AND JUKE-BOX FOR IMPLEMENTING THE METHOD
FR2805060B1 (en) 2000-02-16 2005-04-08 Touchtunes Music Corp METHOD FOR RECEIVING FILES DURING DOWNLOAD
FR2805072B1 (en) 2000-02-16 2002-04-05 Touchtunes Music Corp METHOD FOR ADJUSTING THE SOUND VOLUME OF A DIGITAL SOUND RECORDING
FR2808906B1 (en) 2000-05-10 2005-02-11 Touchtunes Music Corp DEVICE AND METHOD FOR REMOTELY MANAGING A NETWORK OF AUDIOVISUAL INFORMATION REPRODUCTION SYSTEMS
FR2811175B1 (en) 2000-06-29 2002-12-27 Touchtunes Music Corp AUDIOVISUAL INFORMATION DISTRIBUTION METHOD AND AUDIOVISUAL INFORMATION DISTRIBUTION SYSTEM
FR2811114B1 (en) 2000-06-29 2002-12-27 Touchtunes Music Corp DEVICE AND METHOD FOR COMMUNICATION BETWEEN A SYSTEM FOR REPRODUCING AUDIOVISUAL INFORMATION AND AN ELECTRONIC ENTERTAINMENT MACHINE
AU2002224573A1 (en) * 2000-07-14 2002-02-05 Infinite Broadcast Corporation Multimedia player and browser system
FR2814085B1 (en) 2000-09-15 2005-02-11 Touchtunes Music Corp ENTERTAINMENT METHOD BASED ON MULTIPLE CHOICE COMPETITION GAMES
US7277765B1 (en) 2000-10-12 2007-10-02 Bose Corporation Interactive sound reproducing
FR2822627B1 (en) * 2001-03-22 2003-06-20 Wavecom Sa RADIOCOMMUNICATION MODULE HOSTING AND EXECUTING CUSTOMER SOFTWARE, AND CORRESPONDING METHOD FOR IMPLEMENTING CUSTOMER SOFTWARE
US8332895B2 (en) 2002-09-16 2012-12-11 Touchtunes Music Corporation Digital downloading jukebox system with user-tailored music management, communications, and other tools
US7822687B2 (en) 2002-09-16 2010-10-26 Francois Brillon Jukebox with customizable avatar
US9646339B2 (en) 2002-09-16 2017-05-09 Touchtunes Music Corporation Digital downloading jukebox system with central and local music servers
US10373420B2 (en) 2002-09-16 2019-08-06 Touchtunes Music Corporation Digital downloading jukebox with enhanced communication features
US8103589B2 (en) 2002-09-16 2012-01-24 Touchtunes Music Corporation Digital downloading jukebox system with central and local music servers
US11029823B2 (en) 2002-09-16 2021-06-08 Touchtunes Music Corporation Jukebox with customizable avatar
US8584175B2 (en) 2002-09-16 2013-11-12 Touchtunes Music Corporation Digital downloading jukebox system with user-tailored music management, communications, and other tools
US8151304B2 (en) 2002-09-16 2012-04-03 Touchtunes Music Corporation Digital downloading jukebox system with user-tailored music management, communications, and other tools
US20050114374A1 (en) * 2003-04-04 2005-05-26 Juszkiewicz Henry E. User interface for a combination compact disc recorder and player system
US7249147B2 (en) * 2003-04-04 2007-07-24 Gibson Guitar Corp. Combination compact disc recorder and player system
US8028323B2 (en) 2004-05-05 2011-09-27 Dryden Enterprises, Llc Method and system for employing a first device to direct a networked audio device to obtain a media item
US20060167574A1 (en) * 2004-06-08 2006-07-27 Takashi Kawakami Data transmission system, data transmission method, and data transmission program
US20060167956A1 (en) * 2005-01-27 2006-07-27 Realnetworks, Inc. Media content transfer method and apparatus (aka shadow cache)
CN100370437C (en) * 2005-09-30 2008-02-20 迈世亚(北京)科技有限公司 Method for duplicating music data
CN100351820C (en) * 2005-09-30 2007-11-28 迈世亚(北京)科技有限公司 Method for duplicating musical composition in CD into MP3 realplayer
US8156433B2 (en) * 2006-09-05 2012-04-10 Villanova University Embodied music system
US9171419B2 (en) 2007-01-17 2015-10-27 Touchtunes Music Corporation Coin operated entertainment system
US9330529B2 (en) 2007-01-17 2016-05-03 Touchtunes Music Corporation Game terminal configured for interaction with jukebox device systems including same, and/or associated methods
US9953481B2 (en) 2007-03-26 2018-04-24 Touchtunes Music Corporation Jukebox with associated video server
WO2009035691A2 (en) * 2007-09-11 2009-03-19 Realnetworks, Inc. Apparatus, system and methods for controlling the presentation of media content
US8332887B2 (en) 2008-01-10 2012-12-11 Touchtunes Music Corporation System and/or methods for distributing advertisements from a central advertisement network to a peripheral device via a local advertisement server
US10290006B2 (en) 2008-08-15 2019-05-14 Touchtunes Music Corporation Digital signage and gaming services to comply with federal and state alcohol and beverage laws and regulations
US8818941B2 (en) 2007-11-11 2014-08-26 Microsoft Corporation Arrangement for synchronizing media files with portable devices
US8849435B2 (en) 2008-07-09 2014-09-30 Touchtunes Music Corporation Digital downloading jukebox with revenue-enhancing features
US9292166B2 (en) 2009-03-18 2016-03-22 Touchtunes Music Corporation Digital jukebox device with improved karaoke-related user interfaces, and associated methods
US10564804B2 (en) 2009-03-18 2020-02-18 Touchtunes Music Corporation Digital jukebox device with improved user interfaces, and associated methods
CA2754990C (en) 2009-03-18 2015-07-14 Touchtunes Music Corporation Entertainment server and associated social networking services
US10719149B2 (en) 2009-03-18 2020-07-21 Touchtunes Music Corporation Digital jukebox device with improved user interfaces, and associated methods
US20110202843A1 (en) * 2010-02-15 2011-08-18 Robert Paul Morris Methods, systems, and computer program products for delaying presentation of an update to a user interface
US20110191677A1 (en) * 2010-01-29 2011-08-04 Robert Paul Morris Methods, systems, and computer program products for controlling play of media streams
US8422858B2 (en) 2010-01-21 2013-04-16 Robert Paul Morris Methods, systems, and computer program products for coordinating playing of media streams
EP2597608A1 (en) 2010-01-26 2013-05-29 Touchtunes Music Corporation Digital jukebox device with improved user interfaces, and associated methods
US10397639B1 (en) 2010-01-29 2019-08-27 Sitting Man, Llc Hot key systems and methods
US20120158891A1 (en) * 2010-12-21 2012-06-21 Microsoft Corporation Techniques for universal representation of digital content
GB2522772B (en) 2011-09-18 2016-01-13 Touchtunes Music Corp Digital jukebox device with karaoke and/or photo booth features, and associated methods
US11151224B2 (en) 2012-01-09 2021-10-19 Touchtunes Music Corporation Systems and/or methods for monitoring audio inputs to jukebox devices
US9921717B2 (en) 2013-11-07 2018-03-20 Touchtunes Music Corporation Techniques for generating electronic menu graphical user interface layouts for use in connection with electronic devices
TWI722981B (en) 2014-03-25 2021-04-01 美商觸控調諧音樂公司 Digital jukebox device with improved user interfaces, and associated methods

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5559301A (en) * 1994-09-15 1996-09-24 Korg, Inc. Touchscreen interface having pop-up variable adjustment displays for controllers and audio processing systems
US5902947A (en) * 1998-09-16 1999-05-11 Microsoft Corporation System and method for arranging and invoking music event processors
US5908997A (en) * 1996-06-24 1999-06-01 Van Koevering Company Electronic music instrument system with musical keyboard

Family Cites Families (49)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2856004B2 (en) 1992-11-02 1999-02-10 ヤマハ株式会社 Electronic musical instrument system program update method
US5559307A (en) 1994-06-30 1996-09-24 Thomas & Betts Corporation Twist-on connector having improved finger grip wings
US5711672A (en) * 1994-07-01 1998-01-27 Tv Interactive Data Corporation Method for automatically starting execution and ending execution of a process in a host device based on insertion and removal of a storage media into the host device
JP3446372B2 (en) 1994-11-14 2003-09-16 ソニー株式会社 Digital data recording / reproducing apparatus and method
JPH08241565A (en) * 1995-03-03 1996-09-17 Toshiba Corp Portable computer
US5832298A (en) * 1995-05-30 1998-11-03 Canon Kabushiki Kaisha Adaptive graphical user interface for a network peripheral
JP2998612B2 (en) 1995-06-06 2000-01-11 ヤマハ株式会社 Music generator
US5655006A (en) * 1995-12-14 1997-08-05 U S West, Inc. Automated system and method for voice processing
US5864868A (en) 1996-02-13 1999-01-26 Contois; David C. Computer control system and user interface for media playing devices
US5839095A (en) * 1996-06-07 1998-11-17 Liu; Johny Multimedia control center for controlling peripheral devices of a personal computer
US6148346A (en) * 1996-06-20 2000-11-14 Peerless Systems Imaging Products, Inc. Dynamic device driver
KR100280783B1 (en) * 1996-08-20 2001-02-01 윤종용 Remote control device and remote control method of computer system
US5773741A (en) 1996-09-19 1998-06-30 Sunhawk Corporation, Inc. Method and apparatus for nonsequential storage of and access to digital musical score and performance information
FR2753868A1 (en) * 1996-09-25 1998-03-27 Technical Maintenance Corp METHOD FOR SELECTING A RECORDING ON AN AUDIOVISUAL DIGITAL REPRODUCTION SYSTEM AND SYSTEM FOR IMPLEMENTING THE METHOD
US5959944A (en) * 1996-11-07 1999-09-28 The Music Connection Corporation System and method for production of customized compact discs on demand
US5911044A (en) * 1996-11-08 1999-06-08 Ricoh Company, Ltd. Network image scanning system which transmits image information from a scanner over a network to a client computer
US5831613A (en) 1997-01-06 1998-11-03 Apple Computer, Inc. Removable storage media stop/eject system for personal computers
US5990884A (en) * 1997-05-02 1999-11-23 Sony Corporation Control of multimedia information with interface specification stored on multimedia component
US6243725B1 (en) * 1997-05-21 2001-06-05 Premier International, Ltd. List building system
CA2401726C (en) * 1997-06-25 2010-10-19 Richard James Humpleman Browser based command and control home network
CA2769736C (en) * 1997-07-09 2013-05-14 Advanced Audio Devices, Llc Device for editing and non-volatile optical storage of digital audio
JP3528524B2 (en) * 1997-07-10 2004-05-17 ソニー株式会社 Recording / reproducing apparatus, recording / reproducing method, and recording medium
US6591247B2 (en) * 1997-08-08 2003-07-08 Prn Corporation Method and apparatus for distributing audiovisual content
JP4078691B2 (en) * 1997-09-19 2008-04-23 ソニー株式会社 Recording / reproducing control system, recording / reproducing control method, and recording / reproducing control apparatus
US6441830B1 (en) * 1997-09-24 2002-08-27 Sony Corporation Storing digitized audio/video tracks
US6671567B1 (en) 1997-11-21 2003-12-30 Dictaphone Corporation Voice file management in portable digital audio recorder
JP3796944B2 (en) * 1998-02-25 2006-07-12 ソニー株式会社 Reproduction method, recording medium, and computer
JPH11242873A (en) 1998-02-26 1999-09-07 Sony Corp Recording and reproducing device
US6426778B1 (en) * 1998-04-03 2002-07-30 Avid Technology, Inc. System and method for providing interactive components in motion video
US6118450A (en) * 1998-04-03 2000-09-12 Sony Corporation Graphic user interface that is usable as a PC interface and an A/V interface
US6081855A (en) * 1998-04-15 2000-06-27 Oak Technology, Inc. Digital versatile disc playback system with flexible input interface
US6417869B1 (en) * 1998-04-15 2002-07-09 Citicorp Development Center, Inc. Method and system of user interface for a computer
US6393430B1 (en) * 1998-05-08 2002-05-21 Sony Corporation Method and system for automatically recording music data files by using the hard drive of a personal computer as an intermediate storage medium
EP0982732A1 (en) 1998-08-24 2000-03-01 Saehan Information Systems Inc. Portable MP3 player having various functions
US6452609B1 (en) * 1998-11-06 2002-09-17 Supertuner.Com Web application for accessing media streams
US6892350B1 (en) * 1999-01-22 2005-05-10 Yamaha Corporation Audio system with customization of information display
US20020194260A1 (en) * 1999-01-22 2002-12-19 Kent Lawrence Headley Method and apparatus for creating multimedia playlists for audio-visual systems
US6577735B1 (en) 1999-02-12 2003-06-10 Hewlett-Packard Development Company, L.P. System and method for backing-up data stored on a portable audio player
US6377530B1 (en) * 1999-02-12 2002-04-23 Compaq Computer Corporation System and method for playing compressed audio data
US6356971B1 (en) * 1999-03-04 2002-03-12 Sony Corporation System for managing multimedia discs, tracks and files on a standalone computer
US6345279B1 (en) 1999-04-23 2002-02-05 International Business Machines Corporation Methods and apparatus for adapting multimedia content for client devices
US7020704B1 (en) * 1999-10-05 2006-03-28 Lipscomb Kenneth O System and method for distributing media assets to user devices via a portal synchronized by said user devices
JP2001110171A (en) * 1999-10-13 2001-04-20 Sony Corp Device and method for recording and reproduction, terminal device, transmitting and receiving method and storage medium
US6192340B1 (en) * 1999-10-19 2001-02-20 Max Abecassis Integration of music from a personal library with real-time information
US20020055934A1 (en) 2000-01-24 2002-05-09 Lipscomb Kenneth O. Dynamic management and organization of media assets in a media player device
US6248946B1 (en) * 2000-03-01 2001-06-19 Ijockey, Inc. Multimedia content delivery system and method
US6772212B1 (en) 2000-03-08 2004-08-03 Phatnoise, Inc. Audio/Visual server
CA2775674C (en) * 2000-03-31 2017-01-24 United Video Properties, Inc. Interactive media system and method for selectively preventing access to trick play functions
US7237198B1 (en) 2000-05-22 2007-06-26 Realnetworks, Inc. System and method of providing for the control of a music player to a device driver

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5559301A (en) * 1994-09-15 1996-09-24 Korg, Inc. Touchscreen interface having pop-up variable adjustment displays for controllers and audio processing systems
US5908997A (en) * 1996-06-24 1999-06-01 Van Koevering Company Electronic music instrument system with musical keyboard
US5902947A (en) * 1998-09-16 1999-05-11 Microsoft Corporation System and method for arranging and invoking music event processors

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9952824B2 (en) 2000-05-22 2018-04-24 Intel Corporation System and method of providing for the control of a music player to a device driver

Also Published As

Publication number Publication date
US8650487B2 (en) 2014-02-11
US20110154202A1 (en) 2011-06-23
US7237198B1 (en) 2007-06-26
US20140129940A1 (en) 2014-05-08
AU2001263299A1 (en) 2001-12-03
US20180203664A1 (en) 2018-07-19
WO2001090871A3 (en) 2002-04-04
US9952824B2 (en) 2018-04-24
US20080134051A1 (en) 2008-06-05

Similar Documents

Publication Publication Date Title
US20180203664A1 (en) System and method of providing for the control of a music player to a device driver
US20050240297A1 (en) System and method of providing music items to music renderers
EP2126726B1 (en) Browser interpretable document for controlling a plurality of media players and systems and methods related thereto
EP0871939B1 (en) Flexible hyperlink association system and method
US8479240B2 (en) Remote management system for at least one audiovisual information reproduction device
US20080235588A1 (en) Media player playlist creation and editing within a browser interpretable document
KR101076904B1 (en) Programming interface for a computer platform
US7181468B2 (en) Content management for rich media publishing system
US20060195864A1 (en) Portable media device interoperability
US20060253547A1 (en) Universal music apparatus for unifying access to multiple specialized music servers
US20050262449A1 (en) Online service switching and customizations
US20080235142A1 (en) System and methods for obtaining rights in playlist entries
JP2002514331A (en) Computer-implemented method for generating a virtual file for sharing information in a physical information file
US5781902A (en) Method, computer program product, and system for extending the capabilities of an existing process to store and display foreign data
EP1612706B1 (en) Content storage device
US5781900A (en) Flexible hyperlink association system
JPH08306167A (en) Method for storing data in storage medium, reproducing device of storage medium, and information management device of storage medium using storage medium, and use method of storage medium
KR20000071986A (en) Suppling method and system of music data file
JP2003099302A (en) Document conversion service method, document data structure, storage medium and information processor
JP2003099263A (en) Data structure of document, storage medium, and apparatus and system for information processing
JP2000075867A (en) Communication karaoke sing-along machine, music data delivery apparatus and recording medium
WO2006093828A2 (en) Improved portable media device interoperability
WO2008069996A1 (en) Software application/process to auto-fill portable audio device with content

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AE AG AL AM AT AT AU AZ BA BB BG BR BY BZ CA CH CN CR CU CZ CZ DE DE DK DK DM DZ EE EE ES FI FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
AK Designated states

Kind code of ref document: A3

Designated state(s): AE AG AL AM AT AT AU AZ BA BB BG BR BY BZ CA CH CN CR CU CZ CZ DE DE DK DK DM DZ EE EE ES FI FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A3

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP