Patent Application
20080229918
This disclosure relates to audio devices and, more particularly, to audio devices that generate audio output based on musical instrument digital interface (MIDI) files.
Musical Instrument Digital Interface (MIDI) is a format used in the creation, communication and/or playback of audio sounds, such as music, speech, tones, alerts, and the like. A device that supports the MIDI format playback may store sets of audio information that can be used to create various “voices.” Each voice may correspond to one or more sounds, such as a musical note by a particular instrument. For example, a first voice may correspond to a middle C as played by a piano, a second voice may correspond to a middle C as played by a trombone, a third voice may correspond to a D# as played by a trombone, and so on. In order to replicate the musical note as played by a particular instrument, a MIDI compliant device may include a set of information for voices that specify various audio characteristics, such as the behavior of a low-frequency oscillator, effects such as vibrato, and a number of other audio characteristics that can affect the perception of sound. Almost any sound can be defined, conveyed in a MIDI file, and reproduced by a device that supports the MIDI format.
A device that supports the MIDI format may produce a musical note (or other sound) when an event occurs that indicates that the device should start producing the note. Similarly, the device stops producing the musical note when an event occurs that indicates that the device should stop producing the note. An entire musical composition may be coded in accordance with the MIDI format by specifying events that indicate when certain voices should start and stop. In this way, the musical composition may be stored and transmitted in a compact file format according to the MIDI format.
MIDI is supported in a wide variety of devices. For example, wireless communication devices, such as radiotelephones, may support MIDI files for downloadable sounds such as ringtones or other audio output. Digital music players, such as the “iPod” devices sold by Apple Computer, Inc and the “Zune” devices sold by Microsoft Corporation may also support MIDI file formats. Other devices that support the MIDI format may include various music synthesizers, wireless mobile devices, direct two-way communication devices (sometimes called walkie-talkies), network telephones, personal computers, desktop and laptop computers, workstations, satellite radio devices, intercom devices, radio broadcasting devices, hand-held gaming devices, circuit boards installed in devices, information kiosks, various computerized toys for children, on-board computers used in automobiles, watercraft and aircraft, and a wide variety of other devices.
In general, this disclosure describes techniques for processing audio files that comply with the musical instrument digital interface (MIDI) format. As used herein, the term MIDI file refers to any file that contains at least one audio track that conforms to a MIDI format. According to this disclosure, techniques are described for efficient processing of MIDI files using software, firmware and hardware. In particular, various tasks associated with MIDI file processing are delegated between software operating on a general purpose processor, firmware associated with a digital signal processor (DSP), and dedicated hardware that is specifically designed for MIDI file processing. Alternatively, the tasks associated with MIDI file processing can be delegated between two different threads of a DSP and the dedicated hardware.
The described techniques can be pipelined for improved efficiency in the processing of MIDI files. A general purpose processor may service MIDI files for a first frame (frame N). When the first frame (frame N) is serviced by the DSP, a second frame (frame N+1) can be simultaneously serviced by the general purpose processor. When the first frame (frame N) is serviced by the hardware, the second frame (frame N+1) can be simultaneously serviced by the DSP while a third frame (frame N+2) is serviced by the general purpose processor. Similar pipelining may also be used if the tasks associated with MIDI file processing are delegated between two different threads of a DSP and the dedicated hardware.
In either case, MIDI file processing is separated into pipelined stages that can be processed at the same time, improving efficiency and possibly reducing the computational resources needed for given stages, such as those associated with the DSP. Each frame passes through the various pipeline stages, from the general purpose processor, to the DSP, and then to the hardware, or from a first DSP thread to a second DSP thread, and then to the hardware. Audio samples generated by the hardware may be delivered back to the DSP, e.g., via interrupt-driven techniques, so that any post-processing can be performed prior to output of audio sounds to a user.
In one aspect, this disclosure provides a method comprising parsing MIDI files and scheduling MIDI events associated with the MIDI files using a first process, processing the MIDI events using a second process to generate MIDI synthesis parameters, and generating audio samples using a hardware unit based on the synthesis parameters.
In another aspect, this disclosure provides a device comprising a processor that executes software to parse MIDI files and schedule MIDI events associated with the MIDI files, a DSP that processes the MIDI events and generates MIDI synthesis parameters, and a hardware unit that generates audio samples based on the synthesis parameters.
In another aspect, this disclosure provides a device comprising software means for parsing MIDI files and scheduling MIDI events associated with the MIDI files, firmware means for processing the MIDI events to generate MIDI synthesis parameters, and hardware means for generating audio samples based on the synthesis parameters.
In another aspect, this disclosure provides a device comprising a multi-threaded DSP including a first thread that parses MIDI files and schedule MIDI events associated with the MIDI files, and a second thread that processes the MIDI events and generates MIDI synthesis parameters, and a hardware unit that generates audio samples based on the synthesis parameters.
In another aspect, this disclosure provides a computer-readable medium comprising instructions that upon execution by one or more processors, cause the one or more processors to parse MIDI files and schedule MIDI events associated with the MIDI files using a first process, process the MIDI events using a second process to generate MIDI synthesis parameters, and generate audio samples using a hardware unit based on the synthesis parameters.
In another aspect, this disclosure provides a circuit configured to parse MIDI files and schedule MIDI events associated with the MIDI files using a first process, process the MIDI events using a second process to generate MIDI synthesis parameters, and generate audio samples using a hardware unit based on the synthesis parameters.
The details of one or more aspects of this disclosure are set forth in the accompanying drawings and the description below. Other features, objects, and advantages will be apparent from the description and drawings, and from the claims.
This disclosure describes techniques for processing audio files that comply with a musical instrument digital interface (MIDI) format. As used herein, the term MIDI file refers to any file that contains at least one track that conforms to a MIDI format. Examples of various file formats that may include MIDI tracks include CMX, SMAF, XMF, SP-MIDI to name a few. CMX stands for Compact Media Extensions, developed by Qualcomm Inc. SMAF stands for the Synthetic Music Mobile Application Format, developed by Yamaha Corp. XMF stands for eXtensible Music Format, and SP-MIDI stands for Scalable Polyphony MIDI.
As described in greater detail below, this disclosure provides techniques in which various tasks associated with a MIDI file processing are delegated between software operating on a general purpose processor, firmware associated with a digital signal processor (DSP), and dedicated hardware that is specifically designed for MIDI file processing. The described techniques can be pipelined for improved efficiency in the processing of MIDI files.
A general purpose processor may execute software to parse MIDI files and schedule MIDI events associated with the MIDI files. The scheduled events can then be serviced by a DSP in a synchronized manner, as specified by timing parameters in the MIDI files. The general purpose processor dispatches the MIDI events to the DSP in a time-synchronized manner, and the DSP processes the MIDI events according to the time-synchronized schedule in order to generate MIDI synthesis parameters. The DSP then schedules processing of the synthesis parameters in hardware, and a hardware unit can generates audio samples based on the synthesis parameters.
The general purpose processor may service MIDI files for a first frame (frame N), and when the first frame (frame N) is serviced by the DSP, a second frame (frame N+1) can be simultaneously serviced by the general purpose processor. Furthermore, when the first frame (frame N) is serviced by the hardware, the second frame (frame N+1) is simultaneously serviced by the DSP while a third frame (frame N+2) is serviced by the general purpose processor. In this way, MIDI file processing is separated into pipelined stages that can be processed at the same time, which can improve efficiency and possibly reduce the computational resources needed for given stages, such as those associated with the DSP. Each frame passes through the various pipeline stages, from the general purpose processor, to the DSP, and then to the hardware. In some cases, audio samples generated by the hardware may be delivered back to the DSP, e.g., via interrupt-driven techniques, so that any post-processing can be performed. Audio samples may then be converted into analog signals, which can be used to drive speakers and output audio sounds to a user.
Alternatively, the tasks associated with MIDI file processing can be delegated between two different threads of a DSP and the dedicated hardware. That is to say, the tasks associated with the general purpose processor (as described herein) could alternatively be executed by a first thread of a multi-threaded DSP. In this case, the first thread of the DSP executes the scheduling, a second thread of the DSP generates the synthesis parameters, and the hardware unit generates audio samples based on the synthesis parameters. This alternative example may also be pipelined in a manner similar to the example that uses a general purpose processor for the scheduling.
The various components illustrated in
As illustrated in the example of
In accordance with this disclosure, device 4 implements an architecture that separates MIDI processing tasks between software, hardware and firmware. In particular, device 4 includes a processor 8, a DSP 12 and a MIDI hardware unit 14. Each of these components may be coupled to a memory unit 10, e.g., directly or via a bus. Processor 8 may comprise a general purpose processor that executes software to parse MIDI files and schedule MIDI events associated with the MIDI files. The scheduled events can be dispatched to DSP 12 in a time-synchronized manner and thereby serviced by DSP 12 in a synchronized manner, as specified by timing parameters in the MIDI files. DSP 12 processes the MIDI events according to the time-synchronized schedule created by general purpose processor 8 in order to generate MIDI synthesis parameters. DSP 12 may also schedule subsequent processing of the MIDI synthesis parameters by MIDI hardware unit 14. MIDI hardware unit 14 generates audio samples based on the synthesis parameters.
Processor 8 may comprise any of a wide variety of general purpose single- or multi-chip microprocessors. Processor 8 may implement a CISC (Complex instruction Set Computer) design or a RISC (Reduced Instruction Set Computer) design. Generally, processor 8 comprises a central processing unit (CPU) that executes software. Examples include 16-bit, 32-bit or 64-bit microprocessors from companies such as Intel Corporation, Apple Computer, Inc, Sun Microsystems Inc., Advanced Micro Devices (AMD) Inc., and the like. Other examples include Unix- or Linux-based microprocessors from companies such as International Business Machines (IBM) Corporation, RedHat Inc., and the like. The general purpose processor may comprise the ARM9, which is commercially available from ARM Inc., and the DSP may comprise the QDSP4 DSP developed by Qualcomm Inc.
Processor 8 may service MIDI files for a first frame (frame N), and when the first frame (frame N) is serviced by DSP 12, a second frame (frame N+1) can be simultaneously serviced by processor 8. When the first frame (frame N) is serviced by MIDI hardware unit 14, the second frame (frame N+1) is simultaneously serviced by DSP 12 while a third frame (frame N+2) is serviced by processor 8. In this way, MIDI file processing is separated into pipelined stages that can be processed at the same time, which can improve efficiency and possibly reduce the computational resources needed for given stages. DSP 12, for example, may be simplified relative to conventional DSPs that execute a full MIDI algorithm without the aid of a processor 8 or MIDI hardware 14.
In some cases, audio samples generated by MIDI hardware 14 are delivered back to DSP 12, e.g., via interrupt-driven techniques. In this case, DSP may also perform post-processing techniques on the audio samples. DAC 16 converts the audio samples, which are digital, into analog signals that can be used by drive circuit 18 to drive speakers 19A and 19B for output of audio sounds to a user.
For each audio frame, processor 8 reads one or more MIDI files and may extract MIDI instructions from the MIDI file. Based on these MIDI instructions, processor 8 schedules MIDI events for processing by DSP 12, and dispatches the MIDI events to DSP 12 according to this scheduling. In particular, this scheduling by processor 8 may include synchronization of timing associated with MIDI events, which can be identified based on timing parameters specified in the MIDI files. MIDI instructions in the MIDI files may instruct a particular MIDI voice to start or stop. Other MIDI instructions may relate to aftertouch effects, breath control effects, program changes, pitch bend effects, control messages such as pan left or right, sustain pedal effects, main volume control, system messages such as timing parameters, MIDI control messages such as lighting effect cues, and/or other sound affects. After scheduling MIDI events, processor 8 may provide the scheduling to memory 10 or DSP 12 so that DSP 12 can process the events. Alternatively, processor 8 may execute the scheduling by dispatching the MIDI events to DSP 12 in the time-synchronized manner.
Memory 10 may be structured such that processor 8, DSP 12 and MIDI hardware 14 can access any information needed to perform the various tasks delegated to these different components. In some cases, the storage layout of MIDI information in memory 10 may be arranged to allow for efficient access from the different components 8, 12 and 14.
When DSP 12 receives scheduled MIDI events from processor 8 (or from memory 10), DSP 12 may process the MIDI events in order to generate MIDI synthesis parameters, which may be stored back in memory 10. Again, the timing in which these MIDI events are serviced by DSP is scheduled by processor 8, which creates efficiency by eliminating the need for DSP 12 to perform such scheduling tasks. Accordingly, DSP 12 can service the MIDI events for a first audio frame while processor 8 is scheduling MIDI events for the next audio frame. Audio frames may comprise blocks of time, e.g., 10 millisecond (ms) intervals, that may include several audio samples. The digital output, for example, may result in 480 samples per frame, which can be converted into an analog audio signal. Many events may correspond to one instance of time so that many notes or sounds can be included in one instance of time according to the MIDI format. Of course, the amount of time delegated to any audio frame, as well as the number of samples per frame may vary in different implementations.
Once DSP 12 has generated the MIDI synthesis parameters, MIDI hardware unit 14 generates audio samples based on the synthesis parameters. DSP 12 can schedule the processing of the MIDI synthesis parameters by MIDI hardware unit 14. The audio samples generated by MIDI hardware unit 14 may comprise pulse-code modulation (PCM) samples, which are digital representations of an analog signal that is sampled at regular intervals. Additional details of exemplary audio generation by MIDI hardware unit 14 are discussed below with reference to
In some cases, post processing may need to be performed on the audio samples. In this case, MIDI hardware unit 14 can send an interrupt command to DSP 12 to instruct DSP 12 to perform such post processing. The post processing may include filtering, scaling, volume adjustment, or a wide variety of audio post processing that may ultimately enhance the sound output.
Following the post processing, DSP 12 may output the post processed audio samples to digital-to analog converter (DAC) 16. DAC 16 converts the digital audio signals into an analog signal and outputs the analog signal to a drive circuit 18. Drive circuit 18 may amplify the signal to drive one or more speakers 19A and 19B to create audible sound.
As shown in
Second processor (or thread) 12B includes a MIDI synthesis module 25, a hardware control module 26 and a post processing module 28. MIDI synthesis module 25 comprises executable instructions that cause second processor (or thread) 12B to generate synthesis parameters based on MIDI events. First processor (or thread) 8B schedules the MIDI events, however, so that this scheduling task does not slow the synthesis parameter generation by second processor (or thread) 12B.
Hardware control module 26 is the software control executed by second processor (or thread) 12B for controlling the operation of MIDI hardware unit 14. Hardware control module 26 may issue commands to MIDI hardware unit 14 and may schedule the servicing of synthesis parameters by MIDI hardware unit 14. Post processing module 28 is a software module executed by second processor (or thread) 12B to perform any post processing on audio samples generated by MIDI hardware unit 14B.
Once second processor (or thread) 12B has generated the synthesis parameters, MIDI hardware unit 14B uses these synthesis parameters to create audio samples, which can be post processed and then used to drive speakers. Further details of one implementation of a specific MIDI hardware unit 14C are discussed below with reference to
Importantly, the components shown in
In addition, MIDI hardware unit 14C may include a coordination module 32. Coordination module 32 coordinates data flows within MIDI hardware unit 14C. When MIDI hardware unit 14C receives an instruction from DSP 12 (
At the direction of coordination module 32, synthesis parameters may be loaded from memory 10 (
The instructions loaded into program RAM unit 44A or 44N instruct the associated processing element 34A or 34N to synthesize one of the voices indicated in the list of synthesis parameters in VPS RAM unit 46A or 46N. There may be any number of processing elements 34A-34N (collectively “processing elements 34”), and each may comprise one or more ALUs that are capable of performing mathematical operations, as well as one or more units for reading and writing data. Only two processing elements 34A and 34N are illustrated for simplicity, but many more may be included in MIDI hardware unit 14C. Processing elements 34 may synthesize voices in parallel with one another. In particular, the plurality of different processing elements 34 work in parallel to process different synthesis parameters. In this manner, a plurality of processing elements 34 within MIDI hardware unit 14C can accelerate and possibly improve the generation of audio samples.
When coordination module 32 instructs one of processing elements 34 to synthesize a voice, the respective processing element may execute one or more instructions associated with the synthesis parameters. Again, these instructions may be loaded into program RAM unit 44A or 44N. The instructions loaded into program RAM unit 44A or 44N cause the respective one of processing elements 34 to perform voice synthesis. For example, processing elements 34 may send requests to a waveform fetch unit (WFU) 36 for a waveform specified in the synthesis parameters. Each of processing elements 34 may use WFU 36. An arbitration scheme may be used to resolve any conflicts if two or more processing elements 34 request use of WFU 36 at the same time.
In response to a request from one of processing elements 34, WFU 36 returns one or more waveform samples to the requesting processing element. However, because a wave can be phase shifted within a sample, e.g., by up to one cycle of the wave, WFU 36 may return two samples in order to compensate for the phase shifting using interpolation. Furthermore, because a stereo signal may include two separate waves for the two stereophonic channels, WFU 36 may return separate samples for different channels, e.g., resulting in up to four separate samples for stereo output.
After WFU 36 returns audio samples to one of processing elements 34, the respective processing element may execute additional program instructions based on the synthesis parameters. In particular, instructions cause one of processing elements 34 to request an asymmetric triangular wave from a low frequency oscillator (LFO) 38 in MIDI hardware unit 14C. By multiplying a waveform returned by WFU 36 with a triangular wave returned by LFO 38, the respective processing element may manipulate various sonic characteristics of the waveform to achieve a desired audio affect. For example, multiplying a waveform by a triangular wave may result in a waveform that sounds more like a desired musical instrument.
Other instructions executed based on the synthesis parameters may cause a respective one of processing elements 34 to loop the waveform a specific number of times, adjust the amplitude of the waveform, add reverberation, add a vibrato effect, or cause other effects. In this way, processing elements 34 can calculate a waveform for a voice that lasts one MIDI frame. Eventually, a respective processing element may encounter an exit instruction. When one of processing elements 34 encounters an exit instruction, that processing element signals the end of voice synthesis to coordination module 32. The calculated voice waveform can then be provided to summing buffer 40, at the direction of another store instruction that causes summing buffer 40 to store that calculated voice waveform. The calculated voice waveform can be provided to summing buffer 40 at the direction of another store instruction during the execution of the program instructions. This causes summing buffer 40 to store that calculated voice waveform.
When summing buffer 40 receives a calculated waveform from one of processing elements 34, summing buffer 40 adds the calculated waveform to the proper instance of time associated with an overall waveform for a MIDI frame. Thus, summing buffer 40 combines output of the plurality of processing elements 34. For example, summing buffer 40 may initially store a flat wave (i.e., a wave where all digital samples are zero.) When summing buffer 40 receives audio information such as a calculated waveform from one of processing elements 34, summing buffer 40 can add each digital sample of the calculated waveform to respective samples of the waveform stored in summing buffer 40. In this way, summing buffer 40 accumulates and stores an overall digital representation of a waveform for a full audio frame.
Summing buffer 40 essentially sums different audio information from different ones of processing elements 34. The different audio information is indicative of different instances of time associated with different generated voices. In this manner, summing buffer 40 creates audio samples representative of an overall audio compilation within a given audio frame.
Processing elements 34 may operate in parallel with one another, yet independently. That is to say, each of processing elements 34 may process a synthesis parameter, and then move on to the next synthesis parameter once the audio information generated for the first synthesis parameter is added to summing buffer 40. Thus, each of processing elements 34 performs its processing tasks for one synthesis parameter independently of the other processing elements 34, and when the processing for synthesis parameter is complete that respective processing element becomes immediately available for subsequent processing of another synthesis parameter.
Eventually, coordination module 32 may determine that processing elements 34 have completed synthesizing all of the voices required for the current audio frame and have provided those voices to summing buffer 40. At this point, summing buffer 40 contains digital samples indicative of a completed waveform for the current audio frame. When coordination module 32 makes this determination, coordination module 32 sends an interrupt to DSP 12 (
Cache memory 48, WFU/LFO memory 39 and linked list memory 42 are also shown in
In accordance with this disclosure, any number of processing elements 34 may be included in MIDI hardware unit 14C provided that a plurality of processing elements 34 operate simultaneously with respect to different synthesis parameters stored in memory 10 (
Processing elements 34 may process all of the synthesis parameters for an audio frame. After processing each respective synthesis parameter, the respective one of processing elements 34 adds its processed audio information in to the accumulation in summing buffer 40, and then moves on to the next synthesis parameter. In this way, processing elements 34 work collectively to process all of the synthesis parameters generated for one or more audio files of an audio frame. Then, after the audio frame is processed and the samples in summing buffer are sent to DSP 12 for post processing, processing elements 34 can begin processing the synthesis parameters for the audio files of the next audio frame.
Again, first audio processing element 34A processes a first audio synthesis parameter to generate first audio information while a second audio processing element 34N processes a second audio synthesis parameter to generate second audio information. At this point, first processing element 34A may process a third audio synthesis parameter to generate third audio information while a second audio processing element 34N processes a fourth audio synthesis parameter to generate fourth audio information. Summing buffer 40 can combine the first, second, third and fourth audio information in the creation of one or more audio samples.
As shown in
At this point, while DSP 12 is processing the MIDI events for frame N (56), if there are more frames in the audio sequence (yes branch of 54), software executing on processor 8 begins servicing the next frame (55), i.e., frame N+1. Thus, while DSP 12 is processing the MIDI events for frame N (56), software executing on processor 8 parses MIDI files for frame N+1 (52), and schedules MIDI events for frame N+1 (53). In other words, stages 1 and 2 are performed simultaneously with respect to frame N and frame N+1.
Next, MIDI hardware unit 14 generates audio samples for frame N (57). At this point, DSP is processing the MIDI events for frame N+1 (56), and software executing on processor 8 is parsing MIDI files for frame N+2 (52) and scheduling MIDI events for frame N+2 (53). In other words, stages 1, 2 and 3 are performed simultaneously with respect to frame N, frame N+1 and frame N+2. This staged approach continues for each subsequent audio frame such that the audio frames pass through stages 1, 2 and 3 in a pipelined fashion. When frame N+1 is serviced by hardware unit 14, frame N+2 is serviced by DSP 12 and frame N+3 is serviced by general purpose processor 8. When frame N+2 is serviced by hardware unit 14, frame N+3 is serviced by DSP 12 and frame N+4 is serviced by general purpose processor 8, and so forth.
Once audio samples are generated for any given frame (57), post processing may be performed on that frame (58). DSP 12 may execute any post processing in response to an interrupt command from hardware unit 14. In this manner, DSP 12 handles not only the processing of MIDI events, but also any post processing that need to be performed on the generated audio frames.
Following the post processing for any frame (58), DAC 16 converts audio samples for the frame to an analog audio signal (59), which can be provided to drive circuit 18. Drive circuit 18 uses the analog audio signal to create drive signals that cause speakers 19A and 19B to output sound (60).
Various examples have been described. One or more aspects of the techniques described herein may be implemented in hardware, software, firmware, or combinations thereof. Any features described as modules or components may be implemented together in an integrated logic device or separately as discrete but interoperable logic devices. If implemented in software, one or more aspects of the techniques may be realized at least in part by a computer-readable medium comprising instructions that, when executed, performs one or more of the methods described above. The computer-readable data storage medium may form part of a computer program product, which may include packaging materials. The computer-readable medium may comprise random access memory (RAM) such as synchronous dynamic random access memory (SDRAM), read-only memory (ROM), non-volatile random access memory (NVRAM), electrically erasable programmable read-only memory (EEPROM), FLASH memory, magnetic or optical data storage media, and the like. The techniques additionally, or alternatively, may be realized at least in part by a computer-readable communication medium that carries or communicates code in the form of instructions or data structures and that can be accessed, read, and/or executed by a computer.
The instructions may be executed by one or more processors, such as one or more digital signal processors (DSPs), general purpose microprocessors, application specific integrated circuits (ASICs), field programmable logic arrays (FPGAs), or other equivalent integrated or discrete logic circuitry. Accordingly, the term “processor,” as used herein may refer to any of the foregoing structure or any other structure suitable for implementation of the techniques described herein. In addition, in some aspects, the functionality described herein may be provided within dedicated software modules or hardware modules configured or adapted to perform the techniques of this disclosure.
If implemented in hardware, one or more aspects of this disclosure may be directed to a circuit, such as an integrated circuit, chipset, ASIC, FPGA, logic, or various combinations thereof configured or adapted to perform one or more of the techniques described herein. The circuit may include both the processor and one or more hardware units, as described herein, in an integrated circuit or chipset.
It should also be noted that a person having ordinary skill in the art will recognize that a circuit may implement some or all of the functions described above. There may be one circuit that implements all the functions, or there may also be multiple sections of a circuit that implement the functions. With current mobile platform technologies, an integrated circuit may comprise at least one DSP, and at least one Advanced Reduced Instruction Set Computer (RISC) Machine (ARM) processor to control and/or communicate to DSP or DSPs. Furthermore, a circuit may be designed or implemented in several sections, and in some cases, sections may be re-used to perform the different functions described in this disclosure.
Various aspects and examples have been described. However, modifications can be made to the structure or techniques of this disclosure without departing from the scope of the following claims. For example, other types of devices could also implement the MIDI processing techniques described herein. Also, although the exemplary hardware unit 14C, shown in
The present Application for Patent claims priority to Provisional Application No. 60/896,455 entitled “PIPELINE TECHNIQUES FOR PROCESSING MUSICAL INSTRUMENT DIGITAL INTERFACE (MIDI) FILES” filed Mar. 22, 2007, and assigned to the assignee hereof and hereby expressly incorporated by reference herein.
| Number | Date | Country | |
|---|---|---|---|
| 60896455 | Mar 2007 | US |
