The present specification is related generally to the field of video games. More specifically, the present specification is related to systems and methods that dynamically generate and modulate music based on a player profile, a gaming event and/or a player reaction during the gaming events.
Multiplayer online gaming has seen explosive proliferation across the globe with access to a wide range of age groups. A key element of gameplay is the music played at different moments in the game to punctuate an event. For example, upon passing the finish line of a racing game, a celebratory song may be played. Upon finding treasure or passing a game level, the game may play an uplifting melody.
While many features of video games have become highly customizable, musical elements tend to be standardized across all players. For example, a player can customize the aesthetic look of his or her avatar or customize team members in a multiplayer game but, conventionally, is not able to customize musical elements for different gaming events. Some video games allow for the replacement of a soundtrack of a game with a player's own music, but such soundtrack replacement features do not provide for the dynamic change or modification of musical elements specific to a player and based on the actual gameplay.
Music and audio are areas of potential player customization that may be automated and personalized so that each individual player has a unique experience. Accordingly, there is need for systems and methods that generate and modulate music unique to individual players, e.g. specific to a level of the player's skill and/or experience, and based on one or more of gaming event(s) that a player encounters, the player's reaction(s), the player's response(s), the player's input(s) and/or the player's movement(s) during the gaming events. There is also a need for systems and methods that correlate generated and modulated music to the player's success or failure during gameplay and that use the correlation to improve the player's performance in future gameplay. By automating the process of what kind of music is being played and how the music is modulated, the video game may become more immersive, become more enjoyable and provide players with a wide variety of customizable features in order to enhance the overall user experience.
The following embodiments and aspects thereof are described and illustrated in conjunction with systems, tools and methods, which are meant to be exemplary and illustrative, and not limiting in scope. The present application discloses numerous embodiments.
In some embodiments, the present specification discloses a computer-implemented method of dynamically generating a music clip for rendering at each of a plurality of client devices corresponding to each of a plurality of players in a multi-player gaming network, wherein the multi-player gaming network comprises at least one game server in data communication with the plurality of client devices located remote from each other, the method comprising: receiving, in the at least one game server, player data corresponding to each of said plurality of players, wherein said player data is received from a plurality of game modules stored locally in each of the plurality of client devices; classifying, in the at least one server and using said player data, each of said plurality of players into one or more player profiles; generating, in the at least one game server, event data based on data indicative of a player's engagement with one or more virtual elements during gameplay and based on data associated with each of said one or more virtual elements; classifying, in the at least one server, the event data into two or more event profiles; generating the music clip based on at least one of the two or more event profiles and at least one of the one or more player profiles; and transmitting the generated music clip to at least one of the plurality of client devices.
Optionally, the music clip is generated by identifying a mood based on the at least one of the two or more event profiles and the at least one of the one or more player profiles.
Optionally, the music clip is generated by modulating one or more elements of a segment of audio data based on the identified mood. Optionally, the one or more elements comprise beat, meter, tempo, syncopation, rhythm, dynamics, melody, intensity, theme, harmony, chord, progression, consonance, dissonance, key, tonality, register, range, instrumentation, tone color, texture, monophonic, homophonic, polyphonic, imitation, form, pitch, duration, loudness, timbre, sonic texture or spatial location.
Optionally, the music clip is generated by selecting a segment of audio data based on the identified mood.
Optionally, the music clip is generated by implementing at least one machine learning model using the at least one of the two or more event profiles and the at least one of the one or more player profiles.
Optionally, additional music clips are generated by implementing at least one machine learning model using at least one of the plurality of players' responses during engagement with said one or more virtual elements.
Optionally, said data indicative of the player's engagement with said one or more virtual elements is received from a game module of the player's client device.
Optionally, said two or more player profiles comprise a beginner level of skill and/or experience, an enthusiast level of skill and/or experience, and an expert level of skill and/or experience.
Optionally, the two or more event profiles comprise a first event profile representative of a low value of the player's engagement, a second event profile representative of a medium value of the player's engagement, and a third event profile representative of a high value of the player's engagement.
In some embodiments, the present specification discloses a system for dynamically generating a music clip for rendering at each of a plurality of client devices corresponding to each of a plurality of players in a multi-player gaming network, wherein the multi-player gaming network comprises at least one game server in data communication with the plurality of client devices located remote from each other, the server comprising a plurality of programmatic instructions that, when executed: receive player data corresponding to each of said plurality of players, wherein said player data is received from a plurality of game modules stored locally in each of the plurality of client devices; classify each of the plurality of players into one or more player profiles; generate event data based on data indicative of a player's engagement with one or more virtual elements during gameplay and based on data associated with each of said one or more virtual elements; classify the event data into two or more event profiles; generate the music clip based on at least one of the two or more event profiles and at least one of the two or more player profiles; and transmit the generated music clip to at least one of the plurality of client devices.
Optionally, the plurality of programmatic instructions, when executed, generate the music clip by identifying a mood based on the at least one of the two or more event profiles and the at least one of the one or more player profiles.
Optionally, the plurality of programmatic instructions, when executed, generate the music clip by modulating one or more elements of a segment of audio data based on the identified mood. Optionally, the one or more elements comprise beat, meter, tempo, syncopation, rhythm, dynamics, melody, intensity, theme, harmony, chord, progression, consonance, dissonance, key, tonality, register, range, instrumentation, tone color, texture, monophonic, homophonic, polyphonic, imitation, form, pitch, duration, loudness, timbre, sonic texture or spatial location.
Optionally, the plurality of programmatic instructions, when executed, generate the music clip by selecting a segment of audio data based on the identified mood.
Optionally, the plurality of programmatic instructions, when executed, generate the music clip by implementing at least one machine learning model using the at least one of the two or more event profiles and the at least one of the one or more player profiles.
Optionally, the plurality of programmatic instructions, when executed, generate additional music clips by implementing at least one machine learning model using at least one of the plurality of players' responses during engagement with said one or more virtual elements.
Optionally, said data indicative of the player's engagement with said one or more virtual elements is received from a game module of the player's client device.
Optionally, the one or more player profiles comprise a beginner level of skill and/or experience, an enthusiast level of skill and/or experience, and an expert level of skill and/or experience.
Optionally, the two or more event profiles comprise a first event profile representative of a low value of the player's engagement, a second event profile representative of a medium value of the player's engagement, and a third event profile representative of a high value of the player's engagement.
The aforementioned and other embodiments of the present shall be described in greater depth in the drawings and detailed description provided below.
These and other features and advantages of the present specification will be further appreciated, as they become better understood by reference to the following detailed description when considered in connection with the accompanying drawings:
Music and audio are another area of video game features that may be highly customizable in an automated and personalized fashion so that each individual player has a unique experience. By automating the process of what kind of music is being played and to what intensity based on the situation, player experience, etc., music and audio can create more immersive and enjoyable gameplay experiences. By leveraging artificial intelligence (AI), an infinite combination of music and audio can be automatically generated to avoid having to manually create music/audio which then needs to be tagged for play based on different situational queues.
The present specification provides for various methods to dynamically generate music based on the video game situation and the responses of the video game player. In some embodiments, the present specification describes a method to leverage artificial intelligence (AI) to dynamically generate music based on the in-game environment, which may include, but is not limited to, physical objects, lighting, and non-playable characters (NPC). In some embodiments, the present specification describes methods to further modify and adapt AI-generated music dynamically based on video game player controller movements and game progression.
The present specification is directed towards multiple embodiments. The following disclosure is provided in order to enable a person having ordinary skill in the art to practice the invention. Language used in this specification should not be interpreted as a general disavowal of any one specific embodiment or used to limit the claims beyond the meaning of the terms used therein. The general principles defined herein may be applied to other embodiments and applications without departing from the spirit and scope of the invention. Also, the terminology and phraseology used is for the purpose of describing exemplary embodiments and should not be considered limiting. Thus, the present invention is to be accorded the widest scope encompassing numerous alternatives, modifications and equivalents consistent with the principles and features disclosed. For purpose of clarity, details relating to technical material that is known in the technical fields related to the invention have not been described in detail so as not to unnecessarily obscure the present invention.
In the description and claims of the application, each of the words “comprise” “include” and “have”, and forms thereof, are not necessarily limited to members in a list with which the words may be associated. It should be noted herein that any feature or component described in association with a specific embodiment may be used and implemented with any other embodiment unless clearly indicated otherwise.
The term “module” used in this disclosure may refer to computer logic utilized to provide a desired functionality, service, or operation by programming or controlling a general purpose processor. In various embodiments, a module can be implemented in hardware, firmware, software or any combination thereof. The module may be interchangeably used with unit, logic, logical block, component, or circuit, for example. The module may be the minimum unit, or part thereof, which performs one or more particular functions.
The terms “a multi-player online gaming environment” or “massively multiplayer online game” or “large-scale multiplayer online game” may be construed to mean a specific hardware architecture in which one or more servers electronically communicate with, and concurrently support game interactions with, a plurality of client devices, thereby enabling each of the client devices to simultaneously play in the same instance of the same game. In embodiments, it is preferable that the plurality of client devices number in the dozens, still preferably hundreds, and still preferably thousands. In one embodiment, the number of concurrently supported client devices ranges from 10 to 5,000,000 and every whole number increment or range therein. Accordingly, a multi-player gaming environment, massively multi-player online game, or large-scale multiplayer online game is a computer-related technology, a non-generic technological environment, and should not be abstractly considered a generic method of organizing human activity divorced from its specific technology environment.
It should be appreciated that while the systems and methods of the present specification are described with reference to a multi-player online gaming environment for ease of elucidation, this should in no way be considered limiting and that the systems and methods of the present specification are applicable for single player and offline games as well.
As used herein, the indefinite articles “a” and “an” mean “at least one” or “one or more” unless the context clearly dictates otherwise.
Overview
In various embodiments, a computing device includes an input/output controller, at least one communications interface; and a system memory. The system memory includes at least one random access memory (RAM) and at least one read-only memory (ROM). These elements are in communication with a central processing unit (CPU) to enable operation of the computing device. In various embodiments, the computing device may be a conventional standalone computer or alternatively, the functions of the computing device may be distributed across a network of multiple computer systems and architectures.
In some embodiments, execution of a plurality of sequences of programmatic instructions or code enable or cause the CPU of the computing device to perform various functions and processes. In alternate embodiments, hard-wired circuitry may be used in place of, or in combination with, software instructions for implementation of the processes of systems and methods described in this application. Thus, the systems and methods described are not limited to any specific combination of hardware and software.
Referring back to
In some embodiments, the one or more game servers 105 include or are in communication with at least one database system 150. The database system 150 stores a plurality of data such as, but not limited to, player identification and demographic data (such as, but not limited to, player ID, name, gender, nationality, and age), a plurality of player data, music and audio data, data associated with at least one machine learning model and game data associated with at least one game that is served or provided to the client devices 110 over the network 115. The database system 150 described herein may be, include, or interface to, for example, an Oracle™ relational database sold commercially by Oracle Corporation. Other databases, such as Informix™, DB2 (Database 2) or other data storage, including file-based, or query formats, platforms, or resources such as OLAP (On Line Analytical Processing), SQL (Structured Query Language), a SAN (storage area network), Microsoft Access™ or others may also be used, incorporated, or accessed. The database system 150 may comprise one or more such databases that reside in one or more physical devices and in one or more physical locations.
In some embodiments, the one or more game servers 105 may be implemented by a cloud of computing platforms operating together as game servers 105.
In accordance with aspects of the present specification, the one or more game servers 105 provide or implement a plurality of modules such as, but not limited to, a master game module 120 and a dynamic music generation module 140. In some embodiments, the one or more client devices 110 are configured to implement or execute one or more of a plurality of client-side modules that are same as or similar to the modules of the one or more game servers 105. For example, in some embodiments the client devices 110 execute a client-side game module 121.
Master Game Module 120
In embodiments, the master game module 120 implements a plurality of instructions or programmatic code to execute an online game to facilitate interaction of the players with the game. In embodiments, an instance of the executed online game may be synchronous, asynchronous, and/or semi-synchronous. The master game module 120 controls aspects of the game for all players and receives and processes each player's input, activities and interactions in the game. Thus, the master game module 120 hosts the online game for all players, receives game data from the client devices 110, and transmits updates to all client devices 110 based on the received game data so that the game, on each of the client devices 110, represents the most updated or current status with reference to interactions of all players with the game. The master game module 120 therefore transmits game data over the network 115 to the client devices 110 for use by the client game module 121 to provide a local version and a current status of the game to the players.
In embodiments, the master game module 120 generates and maintains server-side player data that is updated with client-side player data received from all client devices 110. Thus, the server-side player data is representative of a comprehensive set of player data encompassing what is occurring or what has occurred as a result of an interaction of all the players with the virtual environment of the game. In embodiments, the server-side player data is stored and updated in the at least one database system 150.
In some embodiments, the master game module 120 classifies the server-side data of all players into a plurality of predefined player profiles or categories such as, for example, expert, enthusiast and beginner wherein each player profile is indicative of a level of skill and/or experience of the player. Thus, the expert player profile represents a highest level of skill and/or experience, the enthusiast player profile represents a moderate or medium level of skill and/or experience and the beginner player profile represents a low or novice level of skill and/or experience. The number of player profiles or categories may vary in alternate embodiments. In some embodiments, the master game module 120 classifies the server-side player data of all players on a numerical scale of for example, 1 to 3, where 1 is representative of a highest level of skill and/or experience, 2 is representative of a moderate or medium level of skill and/or experience and 3 is representative of a low or novice level of skill and/or experience. In alternate embodiments, the numerical scale may vary in a range of, for example, 1 to 5, 1 to 10, all the way to 1 to n or any increment therein. It should be appreciated that the player's level of skill and/or experience could also vary throughout or within a game such that a player could be new to a certain gameplay experiences but very skilled in other gameplay experiences.
In some embodiments, the master game module 120 also stores and maintains, in the at least one database system 150, additional player data associated with a plurality of in-game virtual elements such as, but not limited to, virtual objects or items, characters, obstacles, platforms, lighting, topographical or terrain related features, regions or locations in the game map (collectively referred to hereinafter as ‘topographical elements’), and virtual status such as, for example, a level of the game.
In some embodiments, the additional player data is predetermined, pre-stored or pre-assigned to each of the plurality of in-game virtual elements and is indicative of at least one of: a) a level of difficulty, complexity or challenge associated with the virtual element, b) a level of significance or esteem associated with the virtual element, and c) a level of reward, advantage and/or reprimand associated with the virtual element. In some embodiments, the additional player data may be configured or determined in terms of points, rewards or advantage that the player may earn or forego depending upon an outcome of the player's interaction with or in the context of the plurality of virtual elements during game play. In some embodiments, the points, rewards or advantage earned or foregone translate into player data encompassing game-specific measure(s) or statistics indicative of the player's level of skill and/or experience.
In embodiments, the master game module 120 a) receives, from the game module 121, data indicative of player inputs/responses, engagements, interactions and position within the virtual environment of the game, and b) dynamically or in real-time determines composite player data based upon the pre-stored player data associated with each of the plurality of virtual elements that the player is currently engaged with, interacting with, immersed in or positioned in. In various embodiments, the composite player data is determined as an aggregate or a weighted aggregate of the pre-stored player data associated with each of the plurality of virtual elements.
Thus, the composite player data is indicative of a significance or value associated with the player's on-going interaction and/or situation within the gameplay. In some embodiments, the master game module 120 classifies the composite player data associated with the player into a plurality of predefined player profiles or categories such as, for example, into at least first, second and third merit categories wherein the first merit category (or crucial merit) is representative of interactions and/or situations of the highest, most significant or crucial value, the second merit category (or moderate merit) is representative of interactions and/or situations of moderate or medium value and the third merit category (marginal merit) is representative of interactions and/or situations of least or marginal value.
The number of categories may vary in alternate embodiments. In some embodiments, the master game module 120 classifies the composite player data of the player on a numerical scale of, for example, 1 to 3 where 1 is representative of interactions and/or situations of the highest, most significant or crucial value, 2 is representative of interactions and/or situations of moderate or medium value and 3 is representative of interactions and/or situations of least or marginal value. In alternate embodiments, the numerical scale may vary in a range of, for example, 1 to 5, 1 to 10, all the way to 1 to n or any increment therein.
Thus, in some embodiments, the master game module 120 pre-categorizes a player's in-game interaction or event as crucial, marginal or moderate as dictated by a game design. An interaction or event of marginal merit or value may be, for example, fighting and defeating a common, relatively weak enemy. An interaction or event of moderate merit or value may be, for example, completing a lengthy and somewhat challenging game puzzle. Finally, an interaction or event of crucial merit or value may be, for example, fighting and defeating a major boss which prevents any further game progression until the boss is defeated or unlocks a critical item in the game.
In some embodiments, a machine learning (ML) model is leveraged during a test phase of the game or during a live in-game environment with existing players to define categories for and/or categorize a plurality of interactions and events of the players based on how quickly the plurality of interactions or events are completed by the players or how many times the plurality of interactions or events must be replayed for the players to continue on with the game progression. In some embodiments, a hybrid approach is utilized wherein some interactions and events are pre-categorized but those interactions and events could be re-categorized using ML based on data collected from game testing or actual player interactions and events.
Thus, the master game module 120 generates and stores (in the at least one database system 150) player profile by categorizing a player in accordance to his level of skill and/or experience and merit profile by categorizing the interaction and/or situation that the player engages in during gameplay. In embodiments, the player profile is updated based on pre-programmed periodicity of updates to the server-side leaderboard data while the merit profile is updated in real-time or almost real-time as the player's interaction and/or situation progresses during the gameplay.
Game Module 121
On the client-side, each of the one or more client devices 110 implements the game module 121 that operates as a gaming application and implements a plurality of instructions or programmatic code to provide an interface between a player and the game. The game module 121 generates the interface to render a virtual environment, virtual space, or virtual world associated with the game and enables the player to interact in the virtual environment to perform a plurality of game tasks and objectives. The game module 121 accesses game data received from the master game module 120 to provide an accurate representation of the game to the player. The game module 121 captures and processes player inputs and interactions within the virtual environment and provides updates to the master game module 120 over the network 115.
In embodiments, the game module 121 captures and stores a plurality of client-side player data generated as a result of the player's interactions with the virtual environment of the game. The captured and stored client-side player data is communicated back or uploaded to the master game module 120 in real-time, periodically (such as through batch updates) during a gameplay and/or at an end of the gameplay. The game module 121 accesses updated or most current server-side player data from the master game module 120 and presents or displays the accessed server-side player data via one or more GUIs (Graphical User Interface) to the player.
In embodiments, the client-side player data is associated with a plurality of player related metrics, scoring, or statistics and/or in-game event data generated as a result of the player's interactions with the virtual environment of the game. In embodiments, the client-side player data comprises data such as, but not limited to, a) data related to a plurality of scoring events that occur during a match. For example, high scores, kills or captures, fastest time periods to achieve certain scores, clearance of specific game levels and/or the winning of specific matches by a set of ‘N’ number of top performing players, ranking of the player with reference to the top ‘N’ players and b) data associated with in-game events such as, but not limited to, the movement of the player throughout the virtual environment or topographical map of the game, interaction of the player's avatar with various virtual characters or elements in the game, virtual elements or items used and/or won, damage taken, perks acquired, number of times in a row (or not) that the player hits or misses a target or objective such as, for example, an enemy, number of times (or not) that the player attempts to get to a certain topographical position or location, the number of times the player dies and needs to continue from a previous checkpoint, or whether the player repeats a specific interaction or movement pattern. It should be appreciated that the client-side player data will vary depending upon the type, nature and objectives of the game and therefore encompasses any gameplay data relevant to and defined for a particular type of game and its objectives.
In the present specification, the player data is characterized as a) client-side player-specific data generated and stored at the client devices 110 (as a result of a player playing a game) and communicated back or uploaded to the master game module 120, and b) server-side player data stored at the master game module 120 as a result of processing of client-side player data received from all client devices 110 of all players. The server-side player data is updated with client-side player data received from all client devices 110 and therefore is representative of a comprehensive player data encompassing what is occurring or what has occurred as a result of an interaction of all the players with the virtual environment of the game.
Dynamic Music Generation Module 140
For a player engaged in gameplay, in a gaming session, the dynamic music generation module 140 receives the above-described player data either by querying the at least one database system 150 or by making a request to the master game module 120. In accordance with some aspects of the present specification, the dynamic music generation module 140 implements a plurality of instructions or programmatic code to enable dynamic and real-time a) generation of music dependent on the player data representative of a virtual interaction and/or situation that the player encounters or engages in during gameplay, wherein the generated music is rendered or played on the client device 110 of the player, and b) augmentation, adaptation, re-mixing or modulation of the generated music on the basis of the responses, inputs, controls or movements of the player during a progression, development or advancement of the virtual interaction and/or situation. It should be noted that in some alternate embodiments, the dynamic and real-time generation of music is random and not dependent on the player profile and/or merit profile. It should be appreciated that music generation is enabled at ‘commencement’ of a virtual interaction and/or situation while music augmentation, adaptation, re-mixing or modulation is enabled during and in accordance with how the virtual interaction and/or situation ‘progresses’. Also, in some embodiments, music may be generated by modulating a pre-stored music clip that acts as a ‘seed’ to the generation of music.
Thus, in some embodiments, the generation and modulation of music is based on a plurality of pre-recorded ‘seed’ music files, segments or clips pre-stored in the at least one database system 150. In various embodiments, the plurality of pre-recorded music or audio sample files may either be original compositions or licensed music with rights to modulation or re-mixing.
In some embodiments, music is generated and modulated by leveraging artificial intelligence (AI) comprising at least one machine learning (ML) model that trains on private and/or publicly available open datasets of music to learn to manipulate a plurality of music elements based on a plurality of programmed rules. In various embodiments, the ML model may be a deep learning network such as, but not limited to, at least one or a combination of perceptron neural network, feed forward neural network, radial basis neural network, deep feed forward neural network, convolutional neural networks (CNN), recurrent neural networks (RNN), long short-term memory (LS™) networks, gated recurrent unit neural network, variational auto-encoder neural network, denoising auto-encoder neural network, sparse auto-encoder neural network, Markov Chain neural network, Hopfield neural network, Boltzmann Machine neural network, Restricted Boltzmann Machine neural network, deep belief neural network, deconvolutional neural network, deep convolutional inverse graphics neural network, generative adversarial neural network, liquid state machine, extreme learning machine, echo state neural network, deep residual neural network, Kohonen neural network, support vector machine, neural turing machine, and auto-encoder neural networks. Non-limiting examples of open source ML models for music generation and modulation include Amper Music, Jukedeck, Magenta, DeepJazz, BachBot, and Gruv.
In various embodiments, music is generated/composed and modulated by dynamically manipulating one or more of a plurality of music elements such as, for example, beat, meter, tempo, syncopation, rhythm, dynamics, melody, intensity, theme, harmony, chord, progression, consonance, dissonance, key, tonality, register, range, instrumentation, tone color, texture, monophonic, homophonic, polyphonic, imitation, form, pitch, duration, loudness, timbre, sonic texture and spatial location to adjust for gameplay and enhance the player's gaming experience.
In some embodiments, a portion of the programmatic instructions related to the dynamic music generation module 140 is implemented on the one or more game servers 105 while another portion of the programmatic instructions may reside and be implemented on a player's game module 121. In some embodiments, specifically, programmatic instruction related to the at least one ML model reside and are implemented on a player's game module 121.
In various embodiments, in addition to the above-mentioned musical elements being dynamically modified, game data may be collected and collated from large numbers of players for many games, either individually or concurrently. The collected game data can be used to inform the AI of similar or dissimilar play patterns/gameplay interactions (that is, how a player interacts with the game), which can then be used to define how players subsequently react to variations of those musical elements in subsequent game events. Stated differently, the collected game data may be used to infer how different music affects how players play various scenarios in a game. Further, this approach may be used for offline game scenarios. During quality control and testing of a particular game, the system may aggregate a large number of repeat play-throughs of the same data. In this scenario, the AI can be used to create musical variations in advance, such that they are predetermined versus dynamic. The client software may then match player performance with the predetermined musical variations and subsequently play the appropriate music. The gameplay interactions, levels of performance, and combinations of these with modified music may be numerous and infinite in nature, necessitating technical approaches.
Table A, presented below, illustrates how four exemplary music elements—intensity, timbre, pitch and rhythm—may be manipulated dynamically (on a scale of very low, low, medium, high and very high) to generate eight exemplary moods of music.
In some embodiments, at least a subset of the plurality of music elements is manipulated to generate music based on at least two vectors: 1) the importance, value, or merit of a particular game event, interaction or situation and 2) the player's skill and/or experience profile. In one embodiment, the dynamic music generation module 140 receives, from at least one of the game module 121 or master game module 120, data indicative of a player's movement, interactions, or situation in a game in real-time—that is, data indicative of the merit or value of an interaction and/or situation that the player encounters during gameplay. The dynamic music generation module 140 also receives from one or more databases 150 player data indicative of the player's skill and/or experience profile, as previously described above. With both sets of data, the dynamic music generation module 140 determines a particular music category, as shown in
Once a music category is determined, such as happy, exuberant, energetic, frantic, anxious, sad, depressed, calm, or content, the dynamic music generation module 140 modulates, in real-time, one or more music elements of a segment of music (stored in the at least one database system 150) to achieve a clip of music corresponding to the determined category. For example, the beat, meter, tempo, syncopation, rhythm, dynamics, melody, intensity, theme, harmony, chord, progression, consonance, dissonance, key, tonality, register, range, instrumentation, tone color, texture, monophonic, homophonic, polyphonic, imitation, form, pitch, duration, loudness, timbre, sonic texture or spatial location of an audio clip may be modulated by the dynamic music generation module 140 to achieve the determined music category. Once done, the dynamic music generation module 140 transmits the newly composed music clip to at least one of the game module 121 or master game module 120 for use in the game, in association with the player's movement, interactions, or situation in real-time.
Referring to
When any of the beginner, enthusiast or expert players encounters an interaction and/or situation of crucial merit or value the music generated is perceptible, reflective, or indicative of a frantic mood, for example. When any of the beginner, enthusiast, or expert players encounters an interaction and/or situation of marginal merit or value the music generated is perceptible, reflective or indicative of a calm mood, for example. When a beginner player encounters an interaction and/or situation of moderate merit or value the music generated is perceptible, reflective or indicative of a frantic mood, for example. On the other hand, when an enthusiast or expert player encounters an interaction and/or situation of moderate merit or value the music generated is perceptible, reflective or indicative of an energetic mood, for example.
Considering, for illustrative purposes, a first-person shooter (FPS) game, any of the following exemplary virtual interactions and/or situations may be representative of a moderate merit profile: a close melee combat with an enemy boss, attacking multiple enemies with a sniper rifle or complex platform jumping maneuvers. Therefore, as illustrated in
On the other hand, when a player who may be profiled as an enthusiast or expert encounters or is confronted with any of the exemplary virtual interactions and/or situations, representative of a moderate merit profile, the dynamic music generation module 140 dynamically generates music indicative of an energetic mood that is transmitted over the network for playback at the player's client device.
Similarly, as illustrated in
In some embodiments, the dynamic music generation module 140 does not dynamically modify the pitch, rhythm, timbre, intensity, beat, meter, tempo, syncopation, dynamics, melody, theme, harmony, chord, progression, consonance, dissonance, key, tonality, register, range, instrumentation, tone color, texture, monophonic, homophonic, polyphonic, imitation, form, duration, loudness, sonic texture or spatial location of a musical clip but, rather, dynamically acquires one of a plurality of pre-recorded music or audio sample files stored in the at least one database system 150, which are pre-classified into a plurality of mood classifications such as, for example, the eight moods illustrated in Table A.
Accordingly, the dynamic music generation module 140 selects and transmits (for playback at the client device) a music or audio file from a mood classification that is pre-programmed to be indicative or reflective of the player profile and the merit profile of the interaction and/or situation being encountered by the player (as illustrated in
In some embodiments, the dynamic music generation module 140 may generate music based only on the player's profile or merit profile of an interaction and/or situation that the player encounters during gameplay. For example, the dynamic music generation module 140 may generate calm music for a beginner and frantic music for an enthusiast or an expert player. Similarly, the dynamic music generation module 140 may generate calm music when a player encounters an interaction and/or situation of marginal merit or value, energetic music when a player encounters an interaction and/or situation of moderate merit or value, and frantic music when a player encounters an interaction and/or situation of crucial merit or value, for example.
In alternate embodiments, the dynamic music generation module 140 may generate random music either through a random selection of the plurality of pre-recorded music or audio sample files pre-stored in the at least one database system 150 or by leveraging the at least one ML model that manipulates any subset of the plurality of music elements to dynamically generate random music.
Once the generated music is played on the player's client device, the dynamic music generation module 140 further augments, adapts, re-mixes or modulates the playing music in tandem with a progression of the virtual interaction and/or situation (gaming event). This is enabled, in some embodiments, by leveraging the at least one ML model. In some embodiments, music modulation is programmed to closely follow the player responses, inputs or controller movements by manipulating at least a subset of the plurality of music elements in accordance with a plurality of pre-programmed modulation rules. In some embodiments, music modulation is programmed to closely lead player responses, inputs or controller movements by manipulating at least a subset of the plurality of music elements in accordance with a plurality of pre-programmed modulation rules. In some embodiments, music modulation is programmed to first closely follow and later closely lead player responses, inputs or controller movements by manipulating at least a subset of the plurality of music elements in accordance with a plurality of pre-programmed modulation rules.
For example, in a FPS game the player may control an in-game character which is fighting a large enemy boss. New music is initially generated based on the in-game situation while the player is starting to fight the large enemy boss. The music then dynamically changes in the following two exemplary scenarios.
In a first exemplary scenario, the player may be an experienced video game player who quickly understands how to defeat the large enemy boss. The dynamic music generation module 140 receives game data indicating that the player is quickly defeating the boss and dynamically modulates the music to make the experience more intense. Also, in future enemy encounters, the music is dynamically modulated to reflect the experience of the player by heightening the music intensity for a more engaging gameplay experience.
In a second exemplary scenario, the player may be a new video game player or a beginner who has difficulty understanding how to defeat the large enemy boss. The dynamic music generation module 140 receives game data indicating that the player's character has been repeatedly defeated and dynamically modulates the music to make the experience less intense or provides audible leading cues when to attack the enemy or dodge an attack. Also, in future enemy encounters, the music is dynamically modulated to make the gameplay less intense or harrowing to make these encounters more enjoyable and less frustrating.
As further example, Table B illustrates exemplary music modulation during ‘progression’ of three exemplary virtual interactions and/or situations (that is, close melee combat with enemy boss (representing marginal merit of interaction and/or situation), attacking multiple enemies with sniper rifle (representing moderate merit of interaction and/or situation) and complex platform jumping (representing crucial merit of interaction and/or situation)) in a FPS gameplay by a beginner player profile. In an embodiment, music modulation is done by modulating three exemplary music elements of beat, tempo and duration. Also, music modulation is programmed to closely follow the player's responses, inputs or controller movements.
As another example, Table C illustrates exemplary forms of music modulation during ‘progression’ of the three exemplary virtual interactions and/or situations for an enthusiast or moderate player profile. Also, music modulation is programmed to closely follow the player's responses, inputs or controller movements.
As yet another example, Table D illustrates exemplary forms of music modulation during ‘progression’ of the three exemplary virtual interactions and/or situations for an expert player profile. Also, music modulation is programmed to closely follow the player's responses, inputs or controller movements.
Persons of ordinary skill in the art would appreciate that the three music elements (beat, tempo and duration), that have been manipulated in Tables B, C and D, are only exemplary and in no way limiting. Thus, in alternate embodiment a variety of different music elements may be manipulated in accordance with a plurality of mixing or manipulation rules and music elements.
In accordance with some aspects of the present specification, the dynamic music generation module 140 monitors, collects, associates/correlates and stores a plurality of data indicative of the player's success or failure, during gameplay, while a particular music composition and/or modulation was being rendered at the player's client device. In embodiments, the plurality of data may comprise statistics such as, but not limited to, number of times in a row (or not) that the player hits or misses an enemy, number of times in a row (or not) that the player attempts to get to a platform, dependency on the number of times the player dies and needs to continue from a previous checkpoint and dependency on whether the player repeats the same fighting or movement pattern.
In some embodiments, if the particular music composition and/or modulation are found to have a statistically significant correlation with the player's success in gameplay, the dynamic music generation module 140 is configured to enable generation of similar music compositions and/or modulations for the player and, in some embodiments, for other players as well. On the other hand, if the particular music composition and/or modulation are found to have a statistically significant correlation with the player's failure in gameplay, the dynamic music generation module 140 is configured to avoid generation of similar music compositions and/or modulations for the player and, in some embodiments, for other players as well.
At step 302, each music clip, in a primary dataset of pre-stored ‘seed’ music clips, is encoded in a format suitable for input into the ML model for training. In embodiments, each music clip is encoded in or represented by a data structure comprising a sequence of a plurality of music elements or notations of the music clip. In some embodiments, the data structure is a vector or matrix expressing the plurality of music elements or notations. In various embodiments, the plurality of music elements or notations may include at least a subset of elements such as, for example, beat, meter, tempo, syncopation, rhythm, dynamics, melody, intensity, theme, harmony, chord, note, progression, consonance, dissonance, key, tonality, register, range, instrumentation, tone color, texture, monophonic, homophonic, polyphonic, imitation, form, pitch, duration, loudness, timbre, sonic texture and spatial location. The expressed plurality of music elements or notations is in the form of string-based categorical data which is mapped to integer-based numerical data, in some embodiments.
For example, if the music clips in the primary dataset are MIDI (Musical Instrument Digital Interface) files then Music21, a Python toolkit, may be used to extract the music elements or notations of the MIDI files. Thereafter, the extracted music elements or notations, representing string-based categorical data, are mapped to integer-based numerical data such as, for example, one-Hot encoded data for input into the ML model.
Thus, each music clip is represented by a data structure expressing a plurality of music elements of the music clip as a sequence of numerical data. A data structure corresponding to each of the plurality of music clips is associated with the music clip and stored in the primary dataset.
At step 304, a first plurality of modulation data structures are generated and stored as various categories or classes of datasets. Each of the first plurality of modulation data structure expresses numerical values of one or more of a plurality of music elements or notations that need to be modulated in a music clip of the primary dataset. In embodiments, the first plurality of modulation data structures is associated with one or more moods of music (see Table A) determined on the basis of player profile (level of skill and/or experience of a player) and/or merit profile (category of interaction and/or situation that the player engages in during gameplay).
As a non-limiting example, with reference to Table A, a first dataset includes a plurality of modulation data structures expressing intensity, timbre, pitch and rhythm with a range of numerical values representative of a ‘happy’ mood of music, a second dataset includes a plurality of modulation data structures expressing intensity, timbre, pitch and rhythm with a range of numerical values representative of a ‘exuberant’ mood of music, a third dataset includes a plurality of modulation data structures expressing intensity, timbre, pitch and rhythm with a range of numerical values representative of a ‘energetic’ mood of music, a fourth dataset includes a plurality of modulation data structures expressing intensity, timbre, pitch and rhythm with a range of numerical values representative of a ‘frantic’ mood of music, a fifth dataset includes a plurality of modulation data structures expressing intensity, timbre, pitch and rhythm with a range of numerical values representative of a ‘anxious/sad’ mood of music, a sixth dataset includes a plurality of modulation data structures expressing intensity, timbre, pitch and rhythm with a range of numerical values representative of a ‘depressive’ mood of music, a seventh dataset includes a plurality of modulation data structures expressing intensity, timbre, pitch and rhythm with a range of numerical values representative of a ‘calm’ mood of music, and an eighth dataset includes a plurality of modulation data structures expressing intensity, timbre, pitch and rhythm with a range of numerical values representative of a ‘contentment’ mood of music.
At step 306, a second plurality of modulation data structures are generated and stored as various categories or classes of datasets. Each of the second plurality of modulation data structure expresses numerical values of one or more of a plurality of music elements or notations that need to be modulated in a music clip of the primary dataset. In embodiments, the second plurality of modulation data structures is associated with modulating music in tandem with “progression” of a virtual interaction and/or situation (see Tables B, C and D) of a player profile during gameplay.
As a non-limiting example, with reference to Tables B, C and D, a ninth dataset includes a plurality of modulation data structures expressing beat, tempo, and duration with a range of numerical values representative of first, second and third types (corresponding to, say, marginal, moderate and crucial virtual engagements) of virtual interaction and/or situation for a player profile of a beginner, a tenth dataset includes a plurality of modulation data structures expressing beat, tempo, and duration with a range of numerical values representative of first, second and third types of virtual interaction and/or situation for a player profile of an enthusiast, and an eleventh dataset includes a plurality of modulation data structures expressing beat, tempo, and duration with a range of numerical values representative of first, second and third types of virtual interaction and/or situation for a player profile of an expert.
At step 308, first and second inputs are provided to the ML model for training using a learning algorithm. In embodiments, the first input is a data structure associated with a music clip from the primary dataset. The music clip functions as ‘seed’ music data for subsequent modulation. In embodiments, the second input is a modulation data structure from the first and second plurality of modulation data structures and belonging to the first, second, third, fourth, fifth, sixth, seventh, eighth, ninth, tenth and eleventh datasets.
In some embodiments, the ML model is iteratively trained with all data structures of the music clips of the primary dataset provided as the first input one-by-one in combination with the first plurality of modulation data structures provided as the second input one-by-one. The training process is continued with the ML model being iteratively trained with all data structures of the music clips of the primary dataset provided as the first input one-by-one in combination with the second plurality of modulation data structures provided as the second input one-by-one. In embodiments, the ML model is trained for predefined epochs or iterations (say, for example, 250 epochs) with each batch of data structures that is propagated through the ML model.
In embodiments, the first input is provided to a plurality of input nodes of the input LSTM layer while the second input is provided to a plurality of modulatory or bias nodes of the input LSTM layer. In some embodiments, the number of input nodes is such that each of the plurality of music elements or notations of the input data structure is fed into an input node. Similarly, in some embodiments, the number of modulatory or bias nodes is such that each of the plurality of music elements or notations of the input modulatory data structure is fed into a modulatory or bias node.
In embodiments, the learning algorithm uses Categorical Cross Entropy as a Loss function of the model (that is, to calculate the loss for each iteration of the training) and Adaptive Moment Estimation, a variant of Gradient Descent, as an Optimizer of the model. Alternative embodiments may use RMSprop as an Optimizer of the model.
At step 310, the weights of ML model nodes developed during training are saved for subsequent use and loading into the model, when needed.
It should be appreciated that all datasets (primary, first, second, third, fourth, fifth, sixth, seventh, eighth, ninth, tenth and eleventh) are stored in the at least one database system 150 (
At step 322, the master game module 120 uses the server-side player data to classify or categorize each of the plurality of players into a plurality of player profiles. In some embodiments, the plurality of player profiles comprises first, second and third player profiles, wherein the first player profile is representative of a beginner level skill and/or experience, the second player profile is representative of an enthusiast level skill and/or experience and the third player profile is representative of an expert level skill and/or experience.
At step 324, the master game module 120 generates composite merit or event data based on data indicative of a player's engagement (that is, virtual interaction and/or engagement) with one or more virtual elements during gameplay and based on merit data associated with each of the one or more virtual elements. In embodiments, the merit data corresponding to each of the one or more virtual elements is pre-stored in the at least one database system 150.
At step 326, the master game module 120 classifies or categorizes the composite merit data of the player into a plurality of merit profiles. In some embodiments, the plurality of merit profiles comprises first, second and third merit profiles, wherein the first merit profile is representative of marginal value of the player's engagement, the second merit profile is representative of moderate value of the player's engagement and the third merit profile is representative of crucial value of the player's engagement.
At step 328, the dynamic music generation module 140 leverages at least one trained machine learning (ML) module to dynamically generate music based on the player's profile and/or merit data related to the player's engagement with one or more virtual elements during gameplay. In some embodiments, the at least one trained ML model is the one described and trained in the flowchart of
In accordance with some embodiments, the dynamic music generation module 140 determines a mood of music that needs to be generated based on the player's profile and/or merit data or profile. Thereafter, the module 140 feeds a data structure of a ‘seed’ music clip (selected from the primary dataset) as a first input and a relevant modulation data structure as a second input selected from a dataset corresponding to the determined mood. For example, the module 140 may determine that a ‘frantic’ mood based music needs to be generated since a player of ‘beginner’ profile is engaged in a gameplay of ‘moderate value’ (
At step 330, the dynamic music generation module 140 leverages the at least one trained machine learning module to modulate the generated music based on the player's responses or reactions during progression of the player's engagement with the one or more virtual elements during gameplay.
In accordance with some embodiments, the dynamic music generation module 140 determines a category of modulation that needs to be manifested based on the player's profile and a merit profile (marginal, moderate or crucial) of progression of the player's engagement with the one or more virtual elements during gameplay. Thereafter, the module 140 continues to feed the data structure of the ‘seed’ music clip (selected from the primary dataset at step 310 of
For example, the module 140 may determine that the player of ‘beginner’ profile who was engaged in gameplay of moderate merit or value (for example, attacking multiple enemies with sniper rifle) is losing and therefore may need to dynamically modulate the ‘seed’ music to make the experience less intense for the player. In other words, the module 140 may determine that the ‘seed’ music needs to be calm. Consequently, the module 140 selects a modulation data structure (from the second plurality of modulation data structures) associated with a music clip from the ninth dataset and feeds the modulation data structure as the second input to the at least one trained ML model. This results in the at least one trained ML model modulating the ‘seed’ music clip of the first input to generate or output a perceptibly calmer version of the ‘seed’ music. Also, the output modulated music may be programmed to closely follow the player's responses, inputs or controller movements, in some embodiments.
In some embodiments, the generation and modulation of music is based on the plurality of pre-recorded ‘seed’ music files and associated data structures as well as first and second plurality of modulation data structures pre-stored in the at least one database system 150. In various embodiments, the generation and modulation of music is accomplished by manipulating at least one of a plurality of music elements such as, but not limited to, beat, meter, tempo, syncopation, rhythm, dynamics, melody, pitch, theme, harmony, chord, progression, consonance, dissonance, key, tonality, register, range, instrumentation, tone color, texture, monophonic, homophonic, polyphonic, imitation, form, pitch, duration, loudness, timbre, sonic texture and spatial location.
In various embodiments, the data is aggregated and collated during quality control and testing of a game and/or from a large population of players engaged in actual gameplay across many instances of the game.
At step 404, the dynamic music generation module 140 accesses (from the at least one database system 150) and feeds or inputs the data indicative of at least the player's performance, play patterns and values of the plurality of music elements related to the music compositions and/or modulations rendered during each of the plurality of gameplays to at least one ML model. The at least one ML model is trained to recognize patterns and correlations amongst inputted data. In various embodiments, the at least one trained ML model or artificial neural network comprises one of a deep feed forward network, a perceptron network, a feed forward network, a radial basis network, a recurrent neural network, a long term memory network, a short term memory network, a gated recurrent unit network, an auto encoder network, a variational auto encoder network, a denoising auto encoder network, a sparse auto encoder network, a Markov chain network, a Hopfield network, a Boltzmann machine network, a restricted Boltzmann machine network, a deep belief network, a deep convolutional network, a deconvolutional network, a deep convolutional inverse graphics network, a generated adversarial network, a liquid state machine, an extreme learning machine, an echo state network, a deep residual network, a Kohonen network, a support vector machine network, a neural Turing machine network, or a convolutional neural network with transfer learning network.
In some embodiments, the at least one machine learning model is a deep learning feed-forward network such as a multilayer convolutional neural network (CNN). Persons of ordinary skill in the art would understand that each layer of the multilayer CNN has a weight matrix associated therewith that is determined during learning, also referred to as a training stage. In accordance with some embodiments, the CNN is trained using back propagation with gradient descent and using human-labeled set of training data.
At step 406, the at least one ML model generates output data that relates the player's performance and play patterns with one or more music elements related to rendered music compositions and/or modulation. In other words, the output data is indicative of which types of music compositions and/or modulations (expressed in terms of one or more music elements and the associated value ranges) lead to improved or reduced performance of the player during which play patterns, thereby providing insight on how rendered music actually affects game outcomes for the player. The dynamic music generation module 140 stores the generated output data for the player in the at least one database system 150. It should be appreciated that the stored output data for the player is continuously updated as more data is available for the player from future gameplays.
During a subsequent gameplay, at step 408, the dynamic music generation module 140 receives the player's play patterns in real-time, as monitored by the master game module 120 in communication with the game module 121. For an ensuing play pattern, the module 140 accesses the at least one database system 150 to retrieve stored output data (generated at step 406) indicative of at least one music composition and/or modulation (expressed in terms of one or more music elements and the associated value ranges) that leads to improved/enhanced player performance for the ensuing play pattern. Consequently, the at least one music composition and/or modulation is generated by the dynamic music generation module 140 for rendering at the player's game module 121, thereby “boosting” the player's performance by playing music having the right music elements and associated value ranges.
In embodiments, the methods and systems of the present specification allow for the rapid creation of music and audio that may not have been created manually. In addition, the methods and systems of the present specification can be used for cost savings as the tools and content generated may be used across multiple games within the same genre and franchise, multiple game platforms even with disparate brands, and multiple types of gameplay.
The above examples are merely illustrative of the many applications of the system and method of present specification. Although only a few embodiments of the present specification have been described herein, it should be understood that the present specification might be embodied in many other specific forms without departing from the spirit or scope of the specification. Therefore, the present examples and embodiments are to be considered as illustrative and not restrictive, and the specification may be modified within the scope of the appended claims.
The present specification relies on, for priority, U.S. Patent Provisional Application No. 62/868,538 entitled “Systems and Methods For Dynamically Generating And Modulating Music based On Gaming Events, Player Profiles and/or Player Reactions”, filed on Jun. 28, 2019, which is incorporated by reference herein in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
5530796 | Wang | Jun 1996 | A |
5561736 | Moore | Oct 1996 | A |
5563946 | Cooper | Oct 1996 | A |
5685775 | Bakoglu | Nov 1997 | A |
5706507 | Schloss | Jan 1998 | A |
5708764 | Borrel | Jan 1998 | A |
5736985 | Lection | Apr 1998 | A |
5737416 | Cooper | Apr 1998 | A |
5745678 | Herzberg | Apr 1998 | A |
5768511 | Galvin | Jun 1998 | A |
5825877 | Dan | Oct 1998 | A |
5835692 | Cragun | Nov 1998 | A |
5878233 | Schloss | Mar 1999 | A |
5883628 | Mullaly | Mar 1999 | A |
5900879 | Berry | May 1999 | A |
5903266 | Berstis | May 1999 | A |
5903271 | Bardon | May 1999 | A |
5911045 | Leyba | Jun 1999 | A |
5920325 | Morgan | Jul 1999 | A |
5923324 | Berry | Jul 1999 | A |
5969724 | Berry | Oct 1999 | A |
5977979 | Clough | Nov 1999 | A |
5990888 | Blades | Nov 1999 | A |
6014145 | Bardon | Jan 2000 | A |
6025839 | Schell | Feb 2000 | A |
6059842 | Dumarot | May 2000 | A |
6069632 | Mullaly | May 2000 | A |
6081270 | Berry | Jun 2000 | A |
6081271 | Bardon | Jun 2000 | A |
6091410 | Lection | Jul 2000 | A |
6094196 | Berry | Jul 2000 | A |
6098056 | Rusnak | Aug 2000 | A |
6104406 | Berry | Aug 2000 | A |
6111581 | Berry | Aug 2000 | A |
6134588 | Guenthner | Oct 2000 | A |
6144381 | Lection | Nov 2000 | A |
6148328 | Cuomo | Nov 2000 | A |
6185614 | Cuomo | Feb 2001 | B1 |
6201881 | Masuda | Mar 2001 | B1 |
6222551 | Schneider | Apr 2001 | B1 |
6271842 | Bardon | Aug 2001 | B1 |
6271843 | Lection | Aug 2001 | B1 |
6282547 | Hirsch | Aug 2001 | B1 |
6311206 | Malkin | Oct 2001 | B1 |
6334141 | Varma | Dec 2001 | B1 |
6336134 | Varma | Jan 2002 | B1 |
6337700 | Kinoe | Jan 2002 | B1 |
6353449 | Gregg | Mar 2002 | B1 |
6356297 | Cheng | Mar 2002 | B1 |
6411312 | Sheppard | Jun 2002 | B1 |
6426757 | Smith | Jul 2002 | B1 |
6445389 | Bossen | Sep 2002 | B1 |
6452593 | Challener | Sep 2002 | B1 |
6462760 | Cox, Jr. | Oct 2002 | B1 |
6469712 | Hilpert, Jr. | Oct 2002 | B1 |
6473085 | Brock | Oct 2002 | B1 |
6499053 | Marquette | Dec 2002 | B1 |
6505208 | Kanevsky | Jan 2003 | B1 |
6525731 | Suits | Feb 2003 | B1 |
6549933 | Barrett | Apr 2003 | B1 |
6567109 | Todd | May 2003 | B1 |
6618751 | Challenger | Sep 2003 | B1 |
RE38375 | Herzberg | Dec 2003 | E |
6657617 | Paolini | Dec 2003 | B2 |
6657642 | Bardon | Dec 2003 | B1 |
6684255 | Martin | Jan 2004 | B1 |
6717600 | Dutta | Apr 2004 | B2 |
6734884 | Berry | May 2004 | B1 |
6765596 | Lection | Jul 2004 | B2 |
6781607 | Benham | Aug 2004 | B1 |
6819669 | Rooney | Nov 2004 | B2 |
6832239 | Kraft | Dec 2004 | B1 |
6836480 | Basso | Dec 2004 | B2 |
6886026 | Hanson | Apr 2005 | B1 |
6948168 | Kuprionas | Sep 2005 | B1 |
RE38865 | Dumarot | Nov 2005 | E |
6993596 | Hinton | Jan 2006 | B2 |
7028296 | Irfan | Apr 2006 | B2 |
7062533 | Brown | Jun 2006 | B2 |
7143409 | Herrero | Nov 2006 | B2 |
7209137 | Brokenshire | Apr 2007 | B2 |
7230616 | Taubin | Jun 2007 | B2 |
7249123 | Elder | Jul 2007 | B2 |
7263511 | Bodin | Aug 2007 | B2 |
7287053 | Bodin | Oct 2007 | B2 |
7305438 | Christensen | Dec 2007 | B2 |
7308476 | Mannaru | Dec 2007 | B2 |
7404149 | Fox | Jul 2008 | B2 |
7426538 | Bodin | Sep 2008 | B2 |
7427980 | Partridge | Sep 2008 | B1 |
7428588 | Berstis | Sep 2008 | B2 |
7429987 | Leah | Sep 2008 | B2 |
7436407 | Doi | Oct 2008 | B2 |
7439975 | Hsu | Oct 2008 | B2 |
7443393 | Shen | Oct 2008 | B2 |
7447996 | Cox | Nov 2008 | B1 |
7467181 | McGowan | Dec 2008 | B2 |
7475354 | Guido | Jan 2009 | B2 |
7478127 | Creamer | Jan 2009 | B2 |
7484012 | Hinton | Jan 2009 | B2 |
7503007 | Goodman | Mar 2009 | B2 |
7506264 | Polan | Mar 2009 | B2 |
7515136 | Kanevsky | Apr 2009 | B1 |
7525964 | Astley | Apr 2009 | B2 |
7552177 | Kessen | Jun 2009 | B2 |
7565650 | Bhogal | Jul 2009 | B2 |
7571224 | Childress | Aug 2009 | B2 |
7571389 | Broussard | Aug 2009 | B2 |
7580888 | Ur | Aug 2009 | B2 |
7596596 | Chen | Sep 2009 | B2 |
7640587 | Fox | Dec 2009 | B2 |
7667701 | Leah | Feb 2010 | B2 |
7698656 | Srivastava | Apr 2010 | B2 |
7702784 | Berstis | Apr 2010 | B2 |
7714867 | Doi | May 2010 | B2 |
7719532 | Schardt | May 2010 | B2 |
7719535 | Tadokoro | May 2010 | B2 |
7734691 | Creamer | Jun 2010 | B2 |
7737969 | Shen | Jun 2010 | B2 |
7743095 | Goldberg | Jun 2010 | B2 |
7747679 | Galvin | Jun 2010 | B2 |
7765478 | Reed | Jul 2010 | B2 |
7768514 | Pagan | Aug 2010 | B2 |
7773087 | Fowler | Aug 2010 | B2 |
7774407 | Daly | Aug 2010 | B2 |
7782318 | Shearer | Aug 2010 | B2 |
7792263 | D'Amora | Sep 2010 | B2 |
7792801 | Hamilton, II | Sep 2010 | B2 |
7796128 | Radzikowski | Sep 2010 | B2 |
7808500 | Shearer | Oct 2010 | B2 |
7814152 | McGowan | Oct 2010 | B2 |
7827318 | Hinton | Nov 2010 | B2 |
7843471 | Doan | Nov 2010 | B2 |
7844663 | Boutboul | Nov 2010 | B2 |
7847799 | Taubin | Dec 2010 | B2 |
7856469 | Chen | Dec 2010 | B2 |
7873485 | Castelli | Jan 2011 | B2 |
7882222 | Dolbier | Feb 2011 | B2 |
7882243 | Ivory | Feb 2011 | B2 |
7884819 | Kuesel | Feb 2011 | B2 |
7886045 | Bates | Feb 2011 | B2 |
7890623 | Bates | Feb 2011 | B2 |
7893936 | Shearer | Feb 2011 | B2 |
7904829 | Fox | Mar 2011 | B2 |
7921128 | Hamilton, II | Apr 2011 | B2 |
7940265 | Brown | May 2011 | B2 |
7945620 | Bou-Ghannam | May 2011 | B2 |
7945802 | Hamilton, II | May 2011 | B2 |
7970837 | Lyle | Jun 2011 | B2 |
7970840 | Cannon | Jun 2011 | B2 |
7985138 | Acharya | Jul 2011 | B2 |
7990387 | Hamilton, II | Aug 2011 | B2 |
7996164 | Hamilton, II | Aug 2011 | B2 |
8001161 | Finn | Aug 2011 | B2 |
8004518 | Fowler | Aug 2011 | B2 |
8005025 | Bodin | Aug 2011 | B2 |
8006182 | Bates | Aug 2011 | B2 |
8013861 | Hamilton, II | Sep 2011 | B2 |
8018453 | Fowler | Sep 2011 | B2 |
8018462 | Bhogal | Sep 2011 | B2 |
8019797 | Hamilton, II | Sep 2011 | B2 |
8019858 | Bauchot | Sep 2011 | B2 |
8022948 | Garbow | Sep 2011 | B2 |
8022950 | Brown | Sep 2011 | B2 |
8026913 | Garbow | Sep 2011 | B2 |
8028021 | Reisinger | Sep 2011 | B2 |
8028022 | Brownholtz | Sep 2011 | B2 |
8037416 | Bates | Oct 2011 | B2 |
8041614 | Bhogal | Oct 2011 | B2 |
8046700 | Bates | Oct 2011 | B2 |
8051462 | Hamilton, II | Nov 2011 | B2 |
8055656 | Cradick | Nov 2011 | B2 |
8056121 | Hamilton, II | Nov 2011 | B2 |
8057307 | Berstis | Nov 2011 | B2 |
8062130 | Smith | Nov 2011 | B2 |
8063905 | Brown | Nov 2011 | B2 |
8070601 | Acharya | Dec 2011 | B2 |
8082245 | Bates | Dec 2011 | B2 |
8085267 | Brown | Dec 2011 | B2 |
8089481 | Shearer | Jan 2012 | B2 |
8092288 | Theis | Jan 2012 | B2 |
8095881 | Reisinger | Jan 2012 | B2 |
8099338 | Betzler | Jan 2012 | B2 |
8099668 | Garbow | Jan 2012 | B2 |
8102334 | Brown | Jan 2012 | B2 |
8103640 | Lo | Jan 2012 | B2 |
8103959 | Cannon | Jan 2012 | B2 |
8105165 | Karstens | Jan 2012 | B2 |
8108774 | Finn | Jan 2012 | B2 |
8113959 | De Judicibus | Feb 2012 | B2 |
8117551 | Cheng | Feb 2012 | B2 |
8125485 | Brown | Feb 2012 | B2 |
8127235 | Haggar | Feb 2012 | B2 |
8127236 | Hamilton, II | Feb 2012 | B2 |
8128487 | Hamilton, II | Mar 2012 | B2 |
8131740 | Cradick | Mar 2012 | B2 |
8132235 | Bussani | Mar 2012 | B2 |
8134560 | Bates | Mar 2012 | B2 |
8139060 | Brown | Mar 2012 | B2 |
8139780 | Shearer | Mar 2012 | B2 |
8140340 | Bhogal | Mar 2012 | B2 |
8140620 | Creamer | Mar 2012 | B2 |
8140978 | Betzler | Mar 2012 | B2 |
8140982 | Hamilton, II | Mar 2012 | B2 |
8145676 | Bhogal | Mar 2012 | B2 |
8145725 | Dawson | Mar 2012 | B2 |
8149241 | Do | Apr 2012 | B2 |
8151191 | Nicol, II | Apr 2012 | B2 |
8156184 | Kurata | Apr 2012 | B2 |
8165350 | Fuhrmann | Apr 2012 | B2 |
8171407 | Huang | May 2012 | B2 |
8171408 | Dawson | May 2012 | B2 |
8171559 | Hamilton, II | May 2012 | B2 |
8174541 | Greene | May 2012 | B2 |
8176421 | Dawson | May 2012 | B2 |
8176422 | Bergman | May 2012 | B2 |
8184092 | Cox | May 2012 | B2 |
8184116 | Finn | May 2012 | B2 |
8185450 | McVey | May 2012 | B2 |
8185829 | Cannon | May 2012 | B2 |
8187067 | Hamilton, II | May 2012 | B2 |
8199145 | Hamilton, II | Jun 2012 | B2 |
8203561 | Carter | Jun 2012 | B2 |
8214335 | Hamilton, II | Jul 2012 | B2 |
8214433 | Dawson | Jul 2012 | B2 |
8214750 | Hamilton, II | Jul 2012 | B2 |
8214751 | Dawson | Jul 2012 | B2 |
8217953 | Comparan | Jul 2012 | B2 |
8219616 | Dawson | Jul 2012 | B2 |
8230045 | Kawachiya | Jul 2012 | B2 |
8230338 | Dugan | Jul 2012 | B2 |
8233005 | Finn | Jul 2012 | B2 |
8234234 | Shearer | Jul 2012 | B2 |
8234579 | Do | Jul 2012 | B2 |
8239775 | Beverland | Aug 2012 | B2 |
8241131 | Bhogal | Aug 2012 | B2 |
8245241 | Hamilton, II | Aug 2012 | B2 |
8245283 | Dawson | Aug 2012 | B2 |
8265253 | D'Amora | Sep 2012 | B2 |
8310497 | Comparan | Nov 2012 | B2 |
8334871 | Hamilton, II | Dec 2012 | B2 |
8360886 | Karstens | Jan 2013 | B2 |
8364804 | Childress | Jan 2013 | B2 |
8425326 | Chudley | Apr 2013 | B2 |
8442946 | Hamilton, II | May 2013 | B2 |
8506372 | Chudley | Aug 2013 | B2 |
8514249 | Hamilton, II | Aug 2013 | B2 |
8554841 | Kurata | Oct 2013 | B2 |
8565906 | Alexander | Oct 2013 | B1 |
8607142 | Bergman | Dec 2013 | B2 |
8607356 | Hamilton, II | Dec 2013 | B2 |
8624903 | Hamilton, II | Jan 2014 | B2 |
8626836 | Dawson | Jan 2014 | B2 |
8692835 | Hamilton, II | Apr 2014 | B2 |
8721412 | Chudley | May 2014 | B2 |
8827816 | Bhogal | Sep 2014 | B2 |
8838640 | Bates | Sep 2014 | B2 |
8849917 | Dawson | Sep 2014 | B2 |
8911296 | Chudley | Dec 2014 | B2 |
8992316 | Smith | Mar 2015 | B2 |
9083654 | Dawson | Jul 2015 | B2 |
9152914 | Haggar | Oct 2015 | B2 |
9205328 | Bansi | Dec 2015 | B2 |
9286731 | Hamilton, II | Mar 2016 | B2 |
9299080 | Dawson | Mar 2016 | B2 |
9364746 | Chudley | Jun 2016 | B2 |
9525746 | Bates | Dec 2016 | B2 |
9583109 | Kurata | Feb 2017 | B2 |
9682324 | Bansi | Jun 2017 | B2 |
9764244 | Bansi | Sep 2017 | B2 |
9789406 | Marr | Oct 2017 | B2 |
9808722 | Kawachiya | Nov 2017 | B2 |
20090113448 | Smith | Apr 2009 | A1 |
20140344725 | Bates | Nov 2014 | A1 |
20160191671 | Dawson | Jun 2016 | A1 |
20180109820 | Pompa | Apr 2018 | A1 |
20180350144 | Rathod | Dec 2018 | A1 |
Number | Date | Country |
---|---|---|
768367 | Mar 2004 | AU |
2005215048 | Oct 2011 | AU |
2143874 | Jun 2000 | CA |
2292678 | Jul 2005 | CA |
2552135 | Jul 2013 | CA |
1334650 | Feb 2002 | CN |
1202652 | Oct 2002 | CN |
1141641 | Mar 2004 | CN |
1494679 | May 2004 | CN |
1219384 | Sep 2005 | CN |
1307544 | Mar 2007 | CN |
100407675 | Jul 2008 | CN |
100423016 | Oct 2008 | CN |
100557637 | Nov 2009 | CN |
101001678 | May 2010 | CN |
101436242 | Dec 2010 | CN |
101801482 | Dec 2014 | CN |
668583 | Aug 1995 | EP |
0627728 | Sep 2000 | EP |
0717337 | Aug 2001 | EP |
0679977 | Oct 2002 | EP |
0679978 | Mar 2003 | EP |
0890924 | Sep 2003 | EP |
1377902 | Aug 2004 | EP |
0813132 | Jan 2005 | EP |
1380133 | Mar 2005 | EP |
1021021 | Sep 2005 | EP |
0930584 | Oct 2005 | EP |
0883087 | Aug 2007 | EP |
1176828 | Oct 2007 | EP |
2076888 | Jul 2015 | EP |
2339938 | Oct 2002 | GB |
2352154 | Jul 2003 | GB |
3033956 | Apr 2000 | JP |
3124916 | Jan 2001 | JP |
3177221 | Jun 2001 | JP |
3199231 | Aug 2001 | JP |
3210558 | Sep 2001 | JP |
3275935 | Feb 2002 | JP |
3361745 | Jan 2003 | JP |
3368188 | Jan 2003 | JP |
3470955 | Sep 2003 | JP |
3503774 | Dec 2003 | JP |
3575598 | Jul 2004 | JP |
3579823 | Jul 2004 | JP |
3579154 | Oct 2004 | JP |
3701773 | Oct 2005 | JP |
3777161 | Mar 2006 | JP |
3914430 | Feb 2007 | JP |
3942090 | Apr 2007 | JP |
3962361 | May 2007 | JP |
4009235 | Sep 2007 | JP |
4225376 | Dec 2008 | JP |
4653075 | Dec 2010 | JP |
5063698 | Aug 2012 | JP |
5159375 | Mar 2013 | JP |
5352200 | Nov 2013 | JP |
5734566 | Jun 2015 | JP |
117864 | Aug 2004 | MY |
55396 | Dec 1998 | SG |
2002073457 | Sep 2002 | WO |
20020087156 | Oct 2002 | WO |
2004086212 | Oct 2004 | WO |
2005079538 | Sep 2005 | WO |
2007101785 | Sep 2007 | WO |
2008037599 | Apr 2008 | WO |
2008074627 | Jun 2008 | WO |
2008095767 | Aug 2008 | WO |
2009037257 | Mar 2009 | WO |
2009104564 | Aug 2009 | WO |
2010096738 | Aug 2010 | WO |
Number | Date | Country | |
---|---|---|---|
20200406144 A1 | Dec 2020 | US |
Number | Date | Country | |
---|---|---|---|
62868538 | Jun 2019 | US |