1. Field of the Invention
In general, the invention relates to methods for beat synchronization between media assets, and, more particularly, to the automated creation of beat synchronized media mixes.
2. Description of the Related Art
In recent years, there has been a proliferation of digital media players (i.e., media players capable of playing digital audio and video files.) Digital media players include a wide variety of devices, for example, portable devices, such as MP3 players or mobile phones, personal computers, PDAs, cable and satellite set-top boxes, and others. One example of a portable digital music player is the iPod® manufactured by Apple Inc. of Cupertino, Calif.
Typically, digital media players hold digital media assets (i.e., media files) in internal memory (e.g., flash memory or hard drives) or receive them via streaming from a server. These media assets are then played on the digital media player according to a scheme set by the user or a default scheme set by the manufacturer of the digital media player or streaming music service. For instance, a media player might play media assets in random order, alphabetical order, or based on an arrangement set by an artist or record company (i.e., the order of media assets on a CD). Additionally, many media players are capable of playing media assets based on a media playlist. Media playlists are usually generated by a user, either manually or according to a set of user-input criteria such as genre or artist name.
Digital media assets can be any of a wide variety of file types, including but not limited to: MPEG-1 Layer 2, MPEG-1 Layer 3 (MP3), MPEG-AAC, WMA, Dolby AC-3, Ogg Vorbis, and others. Typically, media assets that have been arranged in media playlists are played with a gap between the media assets. Occasionally, more sophisticated media playing software will mix two media assets together with a rudimentary algorithm that causes the currently playing media asset to fade out (i.e., decrease in volume) while fading in (i.e., increasing in volume) the next media asset. One example of media playing software that includes rudimentary mixing between subsequent media assets is iTunes® manufactured by Apple Inc. of Cupertino, Calif.
However, there is a demand for more sophisticated mixing techniques between media assets than is currently available. For instance, no currently available media playing software is capable of automatically synchronizing the beats between two or more media assets.
Beat synchronization is a technique used by disc jockeys (DJs) to keep a constant tempo throughout a set of music. Beat synchronization is accomplished in two steps: beatmatching (adjusting the tempo of one song to the tempo of another) and beatmixing (lining up the beats of two beatmatched songs.)
Originally, beatmatching was accomplished by counting the beats in a song and averaging them over time. Once the tempo of the song (expressed in beats per minute (BPM)), was determined, other songs with the same tempo could be strung together to create a music set. In response to a demand for more flexibility in creating their music sets, record players (also known as turntables) with highly adjustable speed controls were employed. These adjustable turntables allowed the DJ to adjust the tempo of the music they were playing. Thus, a DJ would play a song with a particular tempo, and adjust the tempo of the next song such that the two songs could be seamlessly beatmixed together. A DJ would use headphones, a sound mixer, and two turntables create a ‘set’ of music by aligning the beats of subsequent songs and fading each song into the next without disrupting the tempo of the music. Currently, manually beatmatching and beatmixing to create a beat-synchronized music mix is regarded as a basic technique among DJs in electronic and other dance music genres.
However, dance club patrons are not the only people who value beat-synchronized music mixes. Currently, many aerobics and fitness instructors use prepared beat-synchronized music mixes to motivate their clients to exercise at a particular intensity throughout a workout. Unfortunately, using the techniques of beatmatching and beatmixing to create a beat-synchronized music mix requires a great deal of time, preparation, and skill, as well as sophisticated equipment or software. Thus, music lovers wishing to experience a dance club quality music mix must attend a dance club or obtain mixes prepared by DJs. In the case of fitness instructors who want to use beat-synchronized music mixes, rudimentary DJ skills must be learned or previously prepared beat-synchronized music mixes must be purchased to play during their workouts.
Currently, even in the unlikely event that a consumer is able to obtain a pre-selected group of beatmatched media assets (i.e., each media asset has the same tempo as the rest) from a media provider, the transitions between media assets are not likely to be beat-synchronized when played. This is because current media players lack the capability to beatmix songs together. Further, even if a group of songs has the same average tempo, it is very likely that at least some beatmatching will have to be performed before beatmixing can occur. Thus, there is a demand for techniques for both automated beatmatching and automated beatmixing of media.
Even professional DJs and others who desire to put together beat-synchronized mixes often have to rely on their own measurements of tempo for determining which songs might be appropriate for creating a beat-synchronized mix. In some instances, the tempo of a song might be stored in the metadata (e.g., the ID3 tags in many types of media assets), but this is by no means common. Thus there is a demand for automated processing of a collection of media assets to determine the tempo of each media asset.
It should be noted that, even in electronic music, which often has computer generated rhythm tracks, the tempo is often not uniform throughout the track. Thus, it is common for music to speed up and/or slow down throughout the music track. This technique is used, for example, to alter mood, to signal a transition to a song chorus, or to build or decrease the perceived intensity of the music. This effect is even more pronounced in non-electronic music, where the beat is provided by musicians rather than computers, and who may vary the speed of their performances for aesthetic or other reasons. For example, it common practice for a song to slow down as it ends, signaling to the listener that the song is over. Speed variations may be very subtle and not easily perceptible to human ears, but can be significant when creating a beat-synchronized music mix. Thus, conventional tempo measuring techniques which output a single number to represent the tempo of the track actually output an average BPM, which can be misleading to someone who is looking for a song segment (such as the beginning or end of a song) with a particular tempo. Thus there is a demand for more complete descriptions of tempo throughout a media asset.
Further still, not everyone who wants a beat-synchronized music mix is knowledgeable or interested enough to use tempo as a criterion for selecting media. Thus, there is a demand for creating a beat-synchronized music mix based on other, subjective or objective criteria, for example, the perceived intensity or genre of the music.
Accordingly, there is a demand for new methods for automatically selecting music or other media for and creating beat-synchronized media mixes. Further, there is a demand for the creation of a beat-profile for any given media asset, as opposed to conventional average tempo measurements.
The invention pertains for techniques for creating beat-synchronized media mixes, using audio and/or video media assets. More specifically, the invention pertains to techniques for creating beat-synchronized media mixes based on user related criteria such as BPM, intensity, or mood.
Beat-synchronized media mixes can be created for a wide variety of different events. The term ‘event’, in the context of this description, refers to a planned activity for which the media mix has been created. For instance, one possible event is a workout. If the user desires a ‘workout mix’ to motivate himself and/or pace his workout, then he can create a workout mix according to his specifications (e.g., workout mode). Another event is a party, where the user desires a party mix to keep her guests entertained. In this case, the party mix can be dynamically created as in automated disc jockey (auto DJ mode). Note that a beat-synchronized mix can be planned for any event with a duration. Further, a beat-synchronized mix can continue indefinitely in an auto DJ mode.
In one embodiment of the invention, the creation of a beat-synchronized media mix can be fully automated based on a user's high-level specification or can be more closely managed (e.g., manually managed) to whatever extent the user wishes. A ‘high-level’ specification from a user could be something as simple as specifying a genre or mood to use when creating the beat-synchronized media mix. Other high-level criteria that can be specified include artist names, music speeds expressed in relative terms (e.g., fast tempo), media mix duration, media mix segment durations, and numerical BPM ranges.
Should a user desire more control over the media mix, a more complete specification can be supplied. For instance, a music tempo can be specified over a period of time. Alternately, a playlist of music suitable for the creation of a beat-synchronized media mix can be specified. Further, a series of beat-synchronized media mixes can be created and strung together in mix segments. For instance, say a user wishes to create a workout mix that includes a warm-up mix segment at one tempo, a main workout mix segment at a second tempo, and a cool down mix segment at a third tempo. In one embodiment of the invention, three separate beat synchronized media mixes are created. Each of the three beat-synchronized media mixes becomes a mix segment of the workout mix. According to this embodiment of the invention, each mix segment of the workout mix is beat-synchronized. However, the transitions between subsequent segments are not beat-synchronized for aesthetic reasons due to the disparity in the tempo between the two segments. Alternately, if the user wishes, subsequent segments can be beat-synchronized between segments, even if the tempo disparity between the two segments is great. One way to beat-synchronize between two mix segments with widely different tempos is by partial synchronization. Ideally, partial synchronization occurs when the tempo of one mix segment is close to an integer multiplier of the tempo of other mix segment (e.g., double, triple, or quadruple speed.) In this case, the beats are synchronized by skipping beats in the faster mix segment. For example, if the tempo of the faster mix segment is twice the tempo of the slower mix segment, then each beat of the slower mix segment can be beatmatched to every other beat of the faster mix segment before beatmixing the two segments together. A second way to beat-synchronize two mix segments with widely different tempos is simply to gradually or rapidly change the tempo of the current mix segment to match the tempo of the upcoming mix segment just before the transition between mix segments.
In another embodiment of the invention, the media mix can be controlled by receiving data from sensors such as heartbeat sensors or pedometers. In this embodiment, music in the media mix can be sped up or slowed down in response to sensor data. For example, if the user's heart rate exceeds a particular threshold, the tempo of the media mix can be altered in real-time. In another example, if a pedometer is being used to track pace, the media mix can automatically adjust its tempo as a method of feedback to the listener.
In still another embodiment of the invention, a beat synchronized event mix is created by selecting a plurality of media assets, arranging the media assets into an unsynchronized media mix, determining the a profile of each of the media assets in the media mix, automatically beatmatching the beats of adjacent media assets in the media mix, and automatically beatmixing the beats of adjacent beatmatched media assets to create the beat-synchronized media mix. The media assets that can be used include both audio and video media. Examples of audio media assets include, but are not limited to: MPEG-1 Layer 2, MPEG-1 Layer 3 (MP3), MPEG-AAC, WMA, Dolby AC-3, and Ogg Vorbis. Media assets are selected based on a specific set of media asset selection criteria, which can include music speed or tempo, music genre, music intensity, media asset duration, user rating, and music mood. A beat synchronized event mix can be subdivided into one or more event mix segments. Each event mix segment can have its own selection criteria.
In another embodiment of the invention, a pair of media assets are beat synchronized by determining the beat profile of the first of the paired media assets, determining the beat profile of the second of the paired media assets, automatically adjusting the speed of the first of the paired media assets to match the speed of the second of the paired media assets, determining the beat offset of the second of the paired media assets, automatically offsetting the second media asset by the beat offset, and automatically mixing the pair of media assets together.
Other aspects and advantages of the invention will become apparent from the following detailed description taken in conjunction with the accompanying drawings which illustrate, by way of example, the principles of the invention.
The invention will be readily understood by the following detailed description in conjunction with the accompanying drawings, wherein like reference numerals designate like structural elements, and in which:
The invention pertains for techniques for creating beat-synchronized media mixes, using audio and/or video media assets. More specifically, the invention pertains to techniques for creating beat-synchronized media mixes based on user related criteria such as BPM, intensity, or mood.
Beat-synchronized media mixes can be created for a wide variety of different events. The term ‘event’, in the context of this description, refers to a planned activity for which the media mix has been created. For instance, one possible event is a workout. If the user desires a ‘workout mix’ to motivate himself and/or pace his workout, then he can create a workout mix according to his specifications (e.g., workout mode). Another event is a party, where the user desires a party mix to keep her guests entertained. In this case, the party mix can be dynamically created as in automated disc jockey (auto DJ mode). Note that a beat-synchronized mix can be planned for any event with a duration. Further, a beat-synchronized mix can continue indefinitely in an auto DJ mode.
In one embodiment of the invention, the creation of a beat-synchronized media mix can be fully automated based on a user's high-level specification or can be more closely managed (e.g., manually managed) to whatever extent the user wishes. A ‘high-level’ specification from a user could be something as simple as specifying a genre or mood to use when creating the beat-synchronized media mix. Other high-level criteria that can be specified include artist names, music speeds expressed in relative terms (e.g., fast tempo), media mix duration, media mix segment durations, and numerical BPM ranges.
Should a user desire more control over the media mix, a more complete specification can be supplied. For instance, a music tempo can be specified over a period of time. Alternately, a playlist of music suitable for the creation of a beat-synchronized media mix can be specified. Further, a series of beat-synchronized media mixes can be created and strung together in mix segments. For instance, say a user wishes to create a workout mix that includes a warm-up mix segment at one tempo, a main workout mix segment at a second tempo, and a cool down mix segment at a third tempo. In one embodiment of the invention, three separate beat synchronized media mixes are created. Each of the three beat-synchronized media mixes becomes a mix segment of the workout mix. According to this embodiment of the invention, each mix segment of the workout mix is beat-synchronized. However, the transitions between subsequent segments are not beat-synchronized for aesthetic reasons due to the disparity in the tempo between the two segments. Alternately, if the user wishes, subsequent segments can be beat-synchronized between segments, even if the tempo disparity between the two segments is great. One way to beat-synchronize between two mix segments with widely different tempos is by partial synchronization. Ideally, partial synchronization occurs when the tempo of one mix segment is close to an integer multiplier of the tempo of other mix segment (e.g., double, triple, or quadruple speed.) In this case, the beats are synchronized by skipping beats in the faster mix segment. For example, if the tempo of the faster mix segment is twice the tempo of the slower mix segment, then each beat of the slower mix segment can be beatmatched to every other beat of the faster mix segment before beatmixing the two segments together. A second way to beat-synchronize two mix segments with widely different tempos is simply to gradually or rapidly change the tempo of the current mix segment to match the tempo of the upcoming mix segment just before the transition between mix segments.
In another embodiment of the invention, the media mix can be controlled by receiving data from sensors such as heartbeat sensors or pedometers. In this embodiment, music in the media mix can be sped up or slowed down in response to sensor data. For example, if the user's heart rate exceeds a particular threshold, the tempo of the media mix can be altered in real-time. In another example, if a pedometer is being used to track pace, the media mix can automatically adjust its tempo as a method of feedback to the listener.
In order to create an event mix, event mix parameters 101 are entered into the event mix creator 105. These parameters can be manually entered by the user or can be pre-generated by, for instance, a personal trainer. Another input into the event mix creator 105 is user input 103. User input 103 can be, for example, a user selecting from a list of media assets that are available to create the event mix. Alternately, user input 103 can be the output of a heartbeat sensor or pedometer. Additionally, the event mix creator 105 can access a media database 109 and media content file storage 111 in order to create the event mix. According to one embodiment of the invention, the media database 109 is a listing of all media files accessible by the event mix creator 105. The media database 109 may be located, for example, locally on a personal computer, or remotely on a media server or media store. Online media databases can include databases that contain media metadata (i.e., data about media), such as Gracenote®, or online media stores that contain both metadata and media content. One example of an online media store is the iTunes® online music store. Media content file storage 111 can be any storage system suitable for storing digital media assets. For instance, media content file storage 111 can be a hard drive on a personal computer. Alternately, media content file storage 111 can be located on a remote server or online media store.
The event mix creation process 200 begins with acquiring 201 the event mix parameters for the desired event mix. In one embodiment of the invention, acquiring 201 is accomplished manually by the person wishing to create the event mix interacting with a software program that creates the event mix. In another embodiment, the event mix parameters are acquired 201 by loading a specification prepared previously by, for example, a personal trainer. Other sources of previously prepared event mix parameters can include, for example, downloadable user generated playlists, published DJ set lists, or professionally prepared workout programs. These parameters can include a wide variety of information that will be used in the creation of the event mix. Some appropriate parameters include a list of genres or artists to use in the event mix, the number of event mix segments in the event mix, the tempo of each event mix segment (expressed in relative terms such as intensity or absolute terms such as BPM), heart rate targets for use with a heart rate sensor during the event, or pace information in terms of steps per minute for a workout that includes walking or running. Other parameters are possible as well. Next, media assets are chosen 203 according to the event mix parameters. According to one embodiment of the invention, media assets are chosen from the user's media asset library, for example, the media assets on the user's hard drive. Alternately, the media assets are chosen 203 from an online media asset database or online media store. The media assets are chosen 203 such that they can be beatmixed and beatmatched without extensive tempo adjustment, if at all possible. For example, if the event parameters specify a tempo in BPM, then all media assets that are chosen 203 are similar in tempo to the specified tempo. The similarity of the tempo can be set by the user or preset in the software used to create the event mix. According to one embodiment of the invention, if the user's media collection does not have a sufficient number of media assets with tempos near the specified tempo, then media assets with greater tempo differences can be chosen 203. Alternately, if the user's media collection does not have a sufficient number of media assets with tempos near the specified tempo, then media assets with the specified tempo can be recommended for the user, and made available for purchase by the user from an online media store. The media assets that are made available can be selected based on tempo, genre, other user's ratings, or other selection criteria. For example, if other users have rated songs as “high intensity workout” songs suitable for workout mixes, and the user does not have those as a part of the user's media collection, then those songs can be made available for purchase. In still another embodiment of the invention, even if the user has a sufficient number of media assets within the specified tempo range, the user may obtain recommendations from an online media store for additional or alternate media assets for use in the event mix.
Once media assets have been chosen 203, they are beatmatched 205 according to the event parameters. In one embodiment of the invention, all media assets that have been chosen 203 are given a uniform tempo corresponding to the tempo given in the event mix parameters. In another embodiment, beatmatching 207 is performed gradually over the course of the entire event mix. Next, the beatmatched media assets are beatmixed 207 together. This is accomplished by lining up the beats between subsequent media assets such that they are synchronized over the mix interval (i.e., the time period when one media asset is fading out while the next is fading in,) and the event mix creation process 200 ends.
The beat profile determining process 300 begins with selecting 301 the first media asset in a collection of media assets. The collection of media assets can, for example, be the media assets chosen 203 in
The beatmatching process 400 begins with determining 401 a desired tempo. This determining 401 can be made, for example, by examining the event parameters acquired 201 in
The beatmixing process 500 begins with selecting 501 a first media asset of a pair of media assets that are to be beatmixed together. Next, a second media asset is selected 503. Third, the two media assets are beatmixed 505 together. As discussed above, beatmixing involves synchronizing the beats of the first and second media assets and then fading the first media asset out while fading the second media asset in. The time over which the first media asset fades into the second is the media asset overlap interval. Typically this media asset overlap interval is several seconds long, for example five seconds. Other media asset overlap intervals are possible.
The event mix creation process 600 begins by selecting 601 an event mix mode. As discussed above, the event can be any number of different types, for example a workout or DJ set. Thus, each event mix mode type corresponds to a type of event. Event mode types include, for example, a DJ mode, a workout mode, and a timed event mode. Other modes are possible. Next, event mix parameters are entered 603 in order to create the event mix. The event parameters can be, for example, the event parameters acquired 201, as described in
Next, the parameters for the first event mix segment are retrieved 605 so that the event mix segment can be constructed. The media assets to be used in the creation of the mix segment are then retrieved 607 and created 611. The creation 611 of the beat-synchronized event mix segment can correspond, for example, to the beatmatching 207 and beatmixing 209 described in
According to one embodiment of the invention, the completed event mix can be a ‘script’ that describes to a media player how to beat-synchronize a playlist of music. In another embodiment, the event mix is created as a single media asset without breaks. One advantage of this embodiment is that any media player can play the event mix even if it does not have beat-synchronization capabilities.
The beat-synchronization process 700 begins with the selection 701 of a first media asset, for example a music file or music video file, followed by the selection 703 of a second media asset. Next, the tempo of the first media asset is adjusted 705 to match the tempo of the second media asset. In a second embodiment of the invention (not shown), the tempo of the second media asset is adjusted to match the tempo of the first media asset. Once the tempo of the first media asset has been adjusted 705, the media overlap interval is determined 707. The media overlap interval is the time segment during which both media assets are playing—typically, the first media asset is faded out while the second media asset is faded in over the media overlap interval. The media overlap interval can be of any duration, but will typically be short in comparison to the lengths of the first and second media assets. The media overlap interval can be specified in software or can be a default value, for example five seconds.
In order to properly align the beats of the first and second media asset, the beat offset of the second media asset is determined 709 next. The beat offset corrects for the difference in beat locations in the first and second media asset over the media overlap interval. For instance, say the media overlap interval is 10 seconds. If, at exactly 10 seconds from the end of the first media asset, the second media asset starts playing, it is likely that the beats of the second media asset will not be synchronized with the beats of the first media asset, even if the tempo is the same. Thus, it is very likely that there will be a staggering of the beats between the two media asset (unless they accidentally line up, which is improbable.) The time between the beats of the first media asset and the staggered beats of the second media asset is the beat offset. Thus, in order to correctly line up the beats, the second media asset is offset 711 in time by the beat offset. Continuing with the example, say each beat in the second media asset hits one second later than the corresponding beat in the first media asset if the second media asset begins playing 10 seconds before the first media asset ends. In this case, the beat offset is one second. Thus, starting the second media asset one second earlier (i.e., 11 seconds before the first media asset ends), properly synchronizes the beats of the first and second media assets. Finally, the first and second media assets are mixed 713 together over the media overlap interval, for example by fading out the first media asset while fading in the second media asset.
The event mix segment creation process 800 begins with determining 801 the event mix segment tempo. In one embodiment of the invention, the event mix segment tempo is one of the event parameters acquired 201 as described in
The event mix creation process 800 continues by, selecting 809 the first media asset in the determined media asset order and determining 811 the selected media asset ending tempo. For example, the mix segment creation process 800 can have access to a beat profile of the selected media asset as determined by the beat profile determining process 300 described in
The event mix segment creation process 800 then determines 813 if there are more media assets in the media asset order. If there are more media assets in the media asset order, then the starting tempo of the next media asset in the starting order is determined 815 and used to adjust 817 the tempo of the currently selected media asset with the next media asset in the media asset order. The tempo adjustment 817 of the currently selected media asset can be, for example, the beat-synchronization process 700 described in
If, however, the decision 813 determines that there are no more media assets in the media asset order, then the event mix segment creation process 800 determines 821 the mix segment ending tempo. If the mix segment ending tempo is not specified, the mix segment ending tempo can default to the currently selected media asset ending tempo. Next, the ending tempo of the currently selected media asset is adjusted 823 as needed to match the mix segment ending tempo. As noted in the description of the tempo adjustment 817 above, the tempo adjustment 823 of the currently selected media asset can be, for example, the beat-synchronization process 700 described in
In
At time T0, song 1 begins at the BPM shown, at time T1, song 1 ends and song 2 begins. In order to beatmatch song 1 and song 2, a median BPM 903 is calculated for the transition point at T1. In this example, the median BPM is calculated by averaging the tempo of song 1 at T1 and the tempo of song 2 at T1. Similarly, median BPMs 905 and 907 are calculated at T2 and T3, at the transition points between song 2 and song 3, and the transition point between song 3 and song 4, respectively. At T4, an ending BPM 909 is shown, rather than a median BPM. In this example, the ending BPM 909 shown corresponds to the target BPM 901.
Note that, in
The media player 1000 also includes a user input device 1008 that allows a user of the media player 1000 to interact with the media player 1000. For example, the user input device 1008 can take a variety of forms, such as a button, keypad, dial, etc. Still further, the media player 1000 includes a display 1010 (screen display) that can be controlled by the processor 1002 to display information to the user. A data bus 1011 can facilitate data transfer between at least the file system 1004, the cache 1006, the processor 1002, and the CODEC 1012.
In one embodiment, the media player 1000 serves to store a plurality of media assets (e.g., songs) in the file system 1004. When a user desires to have the media player play a particular media asset, a list of available media assets is displayed on the display 1010. Then, using the user input device 1008, a user can select one of the available media assets. The processor 1002, upon receiving a selection of a particular media asset, supplies the media data (e.g., audio file) for the particular media asset to a coder/decoder (CODEC) 1012. The CODEC 1012 then produces analog output signals for a speaker 1014. The speaker 1014 can be a speaker internal to the media player 1000 or external to the media player 1000. For example, headphones or earphones that connect to the media player 1000 would be considered an external speaker.
The media player 1000 also includes a network/bus interface 1016 that couples to a data link 1018. The data link 1018 allows the media player 1000 to couple to a host computer. The data link 1018 can be provided over a wired connection or a wireless connection. In the case of a wireless connection, the network/bus interface 1016 can include a wireless transceiver.
In another embodiment, a media player can be used with a docking station. The docking station can provide wireless communication capability (e.g., wireless transceiver) for the media player, such that the media player can communicate with a host device using the wireless communication capability when docked at the docking station. The docking station may or may not be itself portable.
The wireless network, connection or channel can be radio frequency based, so as to not require line-of-sight arrangement between sending and receiving devices. Hence, synchronization can be achieved while a media player remains in a bag, vehicle or other container.
The media information pertains to characteristics or attributes of the media assets. For example, in the case of audio or audiovisual media, the media information can include one or more of: tempo, title, album, track, artist, composer and genre. These types of media information are specific to particular media assets. In addition, the media information can pertain to quality characteristics of the media assets. Examples of quality characteristics of media assets can include one or more of: bit rate, sample rate, equalizer setting, and volume adjustment, start/stop and total time.
Still further, the host computer 1102 includes a play module 1112. The play module 1112 is a software module that can be utilized to play certain media assets stored in the media store 1108. The play module 1112 can also display (on a display screen) or otherwise utilize media information from the media database 1110. Typically, the media information of interest corresponds to the media assets to be played by the play module 1112.
The host computer 1102 also includes a communication module 1114 that couples to a corresponding communication module 1116 within the media player 1104. A connection or link 1118 removeably couples the communication modules 1114 and 1116. In one embodiment, the connection or link 1118 is a cable that provides a data bus, such as a FIREWIRE™ bus or USB bus, which is well known in the art. In another embodiment, the connection or link 1118 is a wireless channel or connection through a wireless network. Hence, depending on implementation, the communication modules 1114 and 1116 may communicate in a wired or wireless manner.
The media player 1104 also includes a media store 1120 that stores media assets within the media player 1104. The media assets being stored to the media store 1120 are typically received over the connection or link 1118 from the host computer 1102. More particularly, the management module 1106 sends all or certain of those media assets residing on the media store 1108 over the connection or link 1118 to the media store 1120 within the media player 1104. Additionally, the corresponding media information for the media assets that is also delivered to the media player 1104 from the host computer 1102 can be stored in a media database 1122. In this regard, certain media information from the media database 1110 within the host computer 1102 can be sent to the media database 1122 within the media player 1104 over the connection or link 1118. Still further, playlists identifying certain of the media assets can also be sent by the management module 1106 over the connection or link 1118 to the media store 1120 or the media database 1122 within the media player 1104.
Furthermore, the media player 1104 includes a play module 1124 that couples to the media store 1120 and the media database 1122. The play module 1124 is a software module that can be utilized to play certain media assets stored in the media store 1120. The play module 1124 can also display (on a display screen) or otherwise utilize media information from the media database 1122. Typically, the media information of interest corresponds to the media assets to be played by the play module 1124.
Hence, in one embodiment, the media player 1104 has limited or no capability to manage media assets on the media player 1104. However, the management module 1106 within the host computer 1102 can indirectly manage the media assets residing on the media player 1104. For example, to “add” a media asset to the media player 1104, the management module 1106 serves to identify the media asset to be added to the media player 1104 from the media store 1108 and then causes the identified media asset to be delivered to the media player 1104. As another example, to “delete” a media asset from the media player 1104, the management module 1106 serves to identify the media asset to be deleted from the media store 1108 and then causes the identified media asset to be deleted from the media player 1104. As still another example, if changes (i.e., alterations) to characteristics of a media asset were made at the host computer 1102 using the management module 1106, then such characteristics can also be carried over to the corresponding media asset on the media player 1104. In one implementation, the additions, deletions and/or changes occur in a batch-like process during synchronization of the media assets on the media player 1104 with the media assets on the host computer 1102.
In another embodiment, the media player 1104 has limited or no capability to manage playlists on the media player 1104. However, the management module 1106 within the host computer 1102 through management of the playlists residing on the host computer can indirectly manage the playlists residing on the media player 1104. In this regard, additions, deletions or changes to playlists can be performed on the host computer 1102 and then by carried over to the media player 1104 when delivered thereto.
Additional information on music synchronization is provided in U.S. patent application Ser. No. 10/997,479, filed Nov. 24, 2004, and entitled “MUSIC SYNCHRONIZATION ARRANGEMENT,” which is hereby incorporated herein by reference.
The advantages of the invention are numerous. Different embodiments or implementations may, but need not, yield one or more of the following advantages. One advantage of this invention is that users may create beat-synchronized event mixes without specific knowledge of advanced beat-matching and beat-mixing techniques. Another advantage of the invention is that users may acquire pre-selected descriptions of event mixes that have been professionally selected by DJs, personal trainers, or other music aficionados.
While this invention has been described in terms of several preferred embodiments, there are alterations, permutations, and equivalents, which fall within the scope of this invention. For example, although the media items of emphasis in several of the above embodiments were audio media assets (e.g., audio files or songs), the media items are not limited to audio media assets. For example, the media item can alternatively pertain to video media assets (e.g., movies). Furthermore, the various aspects, embodiments, implementations or features of the invention can be used separately or in any combination.
It should also be noted that there are many alternative ways of implementing the methods and apparatuses of the present invention. For example, the invention is preferably implemented by software, but can also be implemented in hardware or a combination of hardware and software. The invention can also be embodied as computer readable code on a computer readable medium. The computer readable medium is any data storage device that can store data, which can thereafter be read by a computer system. Examples of the computer readable medium include read-only memory, random-access memory, CD-ROMs, DVDs, magnetic tape, optical data storage devices, and carrier waves. The computer readable medium can also be distributed over network-coupled computer systems so that the computer readable code is stored and executed in a distributed fashion.
It is therefore intended that the following appended claims be interpreted as including all such alterations, permutations, and equivalents as fall within the true spirit and scope of the present invention.
This application is a continuation of U.S. application Ser. No. 11/842,879, filed Aug. 21, 2007 now U.S. Pat. No. 8,269,093, entitled “METHOD FOR CREATING A BEAT-SYNCHRONIZED MEDIA MIX,” which is hereby incorporated herein by reference. This application also references U.S. patent application Ser. No. 10/997,479, filed Nov. 24, 2004, and entitled “MUSIC SYNCHRONIZATION ARRANGEMENT,” which is hereby incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
4674743 | Hirano | Jun 1987 | A |
4692915 | Moriya et al. | Sep 1987 | A |
4776323 | Spector | Oct 1988 | A |
4939611 | Connolly | Jul 1990 | A |
5137501 | Mertesdorf | Aug 1992 | A |
5267942 | Saperston | Dec 1993 | A |
5343871 | Bittman et al. | Sep 1994 | A |
5465729 | Bittman et al. | Nov 1995 | A |
5533947 | Tomlinson et al. | Jul 1996 | A |
5592143 | Romney et al. | Jan 1997 | A |
5662117 | Bittman | Sep 1997 | A |
5982573 | Henze | Nov 1999 | A |
5986200 | Curtin | Nov 1999 | A |
6001048 | Taylor | Dec 1999 | A |
6230047 | McHugh | May 2001 | B1 |
6344607 | Cliff | Feb 2002 | B2 |
6582342 | Kaufman | Jun 2003 | B2 |
6672991 | O'Malley | Jan 2004 | B2 |
6746247 | Barton | Jun 2004 | B2 |
6768066 | Wehrenberg | Jul 2004 | B2 |
6933432 | Shteyn et al. | Aug 2005 | B2 |
7038118 | Gimarc | May 2006 | B1 |
7078607 | Alfernass | Jul 2006 | B2 |
7081582 | Basu | Jul 2006 | B2 |
7156773 | Takai et al. | Jan 2007 | B2 |
7177672 | Nissila | Feb 2007 | B2 |
7207935 | Lipo | Apr 2007 | B1 |
7218226 | Wehrenberg | May 2007 | B2 |
7220911 | Basu | May 2007 | B2 |
7224282 | Terauchi et al. | May 2007 | B2 |
7525037 | Hansson et al. | Apr 2009 | B2 |
7592534 | Yoshikawa et al. | Sep 2009 | B2 |
7615702 | Becker et al. | Nov 2009 | B2 |
20010015123 | Nishitani et al. | Aug 2001 | A1 |
20010026413 | Kisaka et al. | Oct 2001 | A1 |
20010039872 | Cliff | Nov 2001 | A1 |
20030066413 | Nishitani et al. | Apr 2003 | A1 |
20030159566 | Sater et al. | Aug 2003 | A1 |
20030167908 | Nishitani et al. | Sep 2003 | A1 |
20040044291 | Yasushi et al. | Mar 2004 | A1 |
20040077934 | Massad | Apr 2004 | A1 |
20040089142 | Georges et al. | May 2004 | A1 |
20040127335 | Watterson et al. | Jul 2004 | A1 |
20040143193 | Nissila | Jul 2004 | A1 |
20040172481 | Engstrom | Sep 2004 | A1 |
20040252397 | Hodge et al. | Dec 2004 | A1 |
20040263337 | Terauchi et al. | Dec 2004 | A1 |
20050126370 | Takai et al. | Jun 2005 | A1 |
20050215397 | Watterson et al. | Sep 2005 | A1 |
20050215846 | Elliott | Sep 2005 | A1 |
20050233859 | Takai et al. | Oct 2005 | A1 |
20050249080 | Foote et al. | Nov 2005 | A1 |
20050252362 | McHale et al. | Nov 2005 | A1 |
20050288159 | Tackett | Dec 2005 | A1 |
20060000344 | Basu | Jan 2006 | A1 |
20060088228 | Marriott et al. | Apr 2006 | A1 |
20060102171 | Gavish | May 2006 | A1 |
20060107822 | Bowen | May 2006 | A1 |
20060111621 | Coppi et al. | May 2006 | A1 |
20060112808 | Kiiskinen et al. | Jun 2006 | A1 |
20060169125 | Ashkenazi et al. | Aug 2006 | A1 |
20060185502 | Nishitani et al. | Aug 2006 | A1 |
20060234832 | Toyama et al. | Oct 2006 | A1 |
20060243120 | Takai et al. | Nov 2006 | A1 |
20060272480 | Gimarc | Dec 2006 | A1 |
20060277474 | Robarts et al. | Dec 2006 | A1 |
20060288846 | Logan | Dec 2006 | A1 |
20070027000 | Shirai et al. | Feb 2007 | A1 |
20070033295 | Marriott | Feb 2007 | A1 |
20070044641 | McKinney et al. | Mar 2007 | A1 |
20070060446 | Asukai et al. | Mar 2007 | A1 |
20070074617 | Vergo | Apr 2007 | A1 |
20070074619 | Vergo | Apr 2007 | A1 |
20070079691 | Turner | Apr 2007 | A1 |
20070113725 | Oliver et al. | May 2007 | A1 |
20070169614 | Sasaki et al. | Jul 2007 | A1 |
20070186756 | Sano et al. | Aug 2007 | A1 |
20070261538 | Takai et al. | Nov 2007 | A1 |
20070270667 | Coppi et al. | Nov 2007 | A1 |
20080013757 | Carrier | Jan 2008 | A1 |
20080121092 | Drel et al. | May 2008 | A1 |
20080126384 | Toms et al. | May 2008 | A1 |
20080236369 | Sasaki | Oct 2008 | A1 |
20080236370 | Sasaki et al. | Oct 2008 | A1 |
20090272253 | Yamashita et al. | Nov 2009 | A1 |
Number | Date | Country |
---|---|---|
10188452 | Jul 1998 | JP |
2001299980 | Oct 2001 | JP |
2001306071 | Nov 2001 | JP |
2001307413 | Nov 2001 | JP |
2002073018 | Mar 2002 | JP |
2002298496 | Oct 2002 | JP |
2003177749 | Jun 2003 | JP |
2003177750 | Jun 2003 | JP |
2004113552 | Apr 2004 | JP |
Entry |
---|
Chapter 1 “Getting Started,” Traktor DJ Studio Ignite!, R.D. White, Course Technology Publishing, Jun. 2005. |
Chapter 4 “Mixing,” Traktor DJ Studio Ignite!, R.D. White, Course Technology Publishing, Jun. 2005. |
Professional DJ Software Now Available for PC, Mac OS 9.2, and Mac OS X. TRAKTOR DJ Studio 2.0 announcement, Native Instruments website on Feb. 24, 2003. |
Serato Scratch Live 1.7.4 Quick Start Guide, 2007. |
Serato Scratch Live 1.7.4 Release Notes, Serato.com, Oct. 3, 2007. |
Traktor DJ Studio 3 Welcome, native-instruments.com, accessed Aug. 30, 2013. |
Traktor DJ Studio 2 Quick Reference, native-instruments.com, accessed Aug. 30, 2013. |
Active MP3 DJ Studio, downloaded Oct. 28, 2004, http://www.multimediasoft.com/amp3dj/. |
ADXL311—Low Cost, Ultra Compact, ±2 g, Dual Axis Accelerometer, downloaded Nov. 22, 2004, http://www.analog.com/en/prod/0—764—800—ADXL311—00.html. |
Hokuriku, HDK Acceleration Sensor, ACSOIOB Specification, Nov. 11, 2011, pp. 1-2. |
Introducing GarageBand., downloaded Oct. 28, 2004, http://www.apple.com/ilife/garageband/. |
MK2001MPL (HDD1212) Hard Disk Drive, Product Specification, Toshiba Storage Device Division, Toshiba Corporation, Sep. 2000. |
N J Bailey, “Spectral manipulation with the Phase Vocoder,” Oct. 13, 1998, downloaded Oct. 20, 2004, http://sculptor.sourceforge.net/Sculptor/lj/node2.html. |
Nick Bailey, “Issue 54: Sculptor: A Real Time Phase Vocoder,” Oct. 1, 1998, Linux Journal. |
“Smooth 9.25HR Programs Designed for your Fitness Goals,” downloaded Oct. 28, 2004, http://www.treadmillbynet.com/smooth925—programs.htm. |
“Sony Walkman Celebrates 25m Anniversary Milestone With The Launch of a Hard Drive Music Player,” Sep. 29, 2004, Press Release, downloaded on Oct. 14, 2004, http://www.pcworld.idg.com.au/index.php/id;745457704. |
Steve, “OKI Claims Smallest 3-Axis Accelerometer,” Aug. 25, 2004, downloaded Oct. 14, 2004, http://robots.net/article/1269.html. |
Szabo et al., “The Effects of Slow-And Fast-Rhythm Classical Music on Progressive Cycling to Voluntary Physical Exhaustion”, Sep. 1999, The Journal of Sports Medicine and Physical Fitness, pp. 220-225, http://www.ncbi.nlm.nih.gov/pubmed/10573664. |
Toshiba MK6017MAP 6.0 GB IDE 2.5″ 9.5MM Notebook Hard Drive Specification, pp. 1-3, downloaded Apr. 29, 2003: http://shop.store.yahoo.comlnetcomdirect/tosmk6017map.html. |
“Traktor is the best Mp3 DJ Software,” downloaded May 25, 2005, http://www.dj-tips-and-tricks.com/mp3-dj-software.html. |
What is music?, downloaded Oct. 28, 2004, http://www.mfiles.co.uk/other-what-is-music.html. |
Number | Date | Country | |
---|---|---|---|
20130008301 A1 | Jan 2013 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 11842879 | Aug 2007 | US |
Child | 13599817 | US |