may execute program instructions stored in storage 120 to implement the functions performed on and in buffer 122 to process the incoming audio files. Buffer processor 114 may be directed by audio signal processor 118 to perform buffer 122-related functions. It is understood that storage 120 may be made of one or more storage devices locally or remotely situated relative to one another. In some embodiments, storage 120 may comprise logical or virtual links or pointers that uniquely identify one or more physical address including the data of interest or the address where the data of interest is to be stored.

In a general example, through audio stream interface 116, audio stream processor 102 receives “N” number of audio stream files from audio sources 108 where “N” is an integer value. Before storing the audio stream files in buffer 122, buffer processor 114 concatenates a set of the received audio streams to generate a concatenated audio stream. The set may be one or more, up to and including N, number of audio streams. Before storing the received audio streams in the buffer 122, buffer processor 114 further generates N−1 (or one less than the total number of audio streams in the set of audio streams) audio stream separators for the N audio stream files. For example, in system 100, buffer processor 114 may generate an audio stream separator for every two adjacent audio streams of the concatenated audio stream to generate a single audio stream payload, such as single audio stream payload 110. The total number of audio stream separators is therefore typically one less than the total number of audio streams of a concatenated audio stream. Each audio stream separator delineates a beginning of a next audio stream and an end of a preceding audio stream. In some embodiments, buffer processor 114 generates audio stream separators after storing the received audio streams in the buffer 122.

In the example of FIG. 1, three audio stream separators are generated for the three audio stream files received from sources 108. That is, the set of audio stream files equals N received audio stream files. It is understood that for a different number of sources a corresponding different number of audio stream separators may be generated by buffer processor 114.

In some embodiments, buffer processor 114 stores the concatenated audio stream in the buffer 122 and then adds the audio stream separators as delineations markers between each two adjacent stored audio files of a concatenated audio file. In some embodiments, buffer processor 114 first adds the audio stream separators to the concatenated audio stream while the concatenated audio stream is stored in a location other than buffer 122, for example storage 120, and upon completion of processing (generating the single audio stream payload 110), buffer processor 114 transfers the generated payload to buffer 122 for transmission to ASR services 104.

In the example of FIG. 1, buffer processor 114 concatenates the three audio stream files with an audio stream separator between every two adjacent audio streams of the concatenated audio stream in buffer 122 to generate the single audio stream payload 110, each audio stream separator delineating a beginning of a next audio stream and an end of a preceding audio stream separators. Upon generating and inserting all (N−1) audio stream separators into the three audio streams, buffer processor 114 stores the three audio streams with inserted audio stream separators, collectively forming the single audio stream payload 110, in buffer 122. As previously indicated, each audio stream of a concatenated audio stream is separated from a next or adjacent audio stream by an audio stream separator between every two adjacent audio streams of the concatenated audio stream in buffer 122, forming the single audio stream payload 110. For example, audio stream 112 is separated from an immediately previous and adjacent audio stream, shown directly below stream 112 with dashed hashed lines, by an audio stream separator, and an immediately preceding audio stream to the previous audio stream, shown by opposite cross hashed lines immediately below the previous audio stream (in buffer 122), is separated from the previous audio stream by another audio stream separator. In this respect, an audio stream separator is inserted between every two adjacent audio streams of the concatenated audio stream in the buffer 122 to generate the single audio stream payload 110, each audio stream separator delineating a beginning of a next audio stream and an end of a preceding audio stream of a concatenated audio stream.

In an embodiment, audio stream processor 102 receives the N audio streams from sources 108 during a set time window. The size of buffer 122 may be based on a duration of the time window. In some embodiments, the buffer size may be based on a multiple of the maximum audio stream duration. For example, where three audio streams of 3, 5, and 8 seconds in duration are received by audio stream processor 102, the buffer size must be large enough to accommodate a time window of 16 seconds.

Under the direction of audio signal processor 118, audio signal processor 118 or buffer processor 114, as the case maybe, transmits the single audio stream payload 110 for transcription of each of the N audio file speech content- (of each audio stream) to-text content, through audio stream interface 116, to ASR services 104. In response, audio stream processor 102, through audio stream interface 116, receives a transcription of each of the speech content of the N audio streams in the form of a single text content file from ASR services 104. The received text file may include the text content of all N audio files delineated with the audio stream separators. In the case where a set of audio files that includes less than N number of audio files is included in the payload, the received text file includes a number of text files corresponding to the set number of audio files. Audio stream processor 102 may then perform extraction of, or solicit an independent device or service, to perform extraction of relevant text information from one or more of the N text content files.

Audio stream processor 102 may transmit and receive data to and from ASR services 104 in various manners. For example, communications between audio steam processor 102 and ASR services 104 may be implemented through a wireless or wired network, such as WiFi and local area network (LAN), respectively.

In some embodiments, the size of buffer 122 is based on a time window duration. That is, the speech content of each audio stream may have an associated duration and the buffer size maybe based on a multiple number of a maximum speech content duration among the durations of the speech content of the set of audio streams. The maximum duration may correspond to a minimum base transcription service price. That is, transcription charges for transcription of received audio streams may be based on the maximum audio stream duration.

In some disclosed methods, upon receipt of a transcribed text file from a STT (or ASR) service, or during post-STT service processing, each text content of a corresponding audio stream is separated from adjacent text files of corresponding adjacent audio streams in the single payload text file by the audio stream separators. As with pre-STT audio file processing, each delinaeated text file corresponds to an independent audio source.

Prior to the transmission of payload 110 for transcription, for each audio stream, buffer processor 114 may make a determination as to whether the audio stream can be transmitted in its entirety during the time window and based on the determination, a remaining set of audio streams may be saved for transmission with a subsequent single audio stream payload. For example, in the event one or more audio streams of a current set of audio streams are not received in their entirety during the time window, the one or more audio streams of the current set that are not received in their entirety may be saved in the buffer or other storage locations to be processed and transmitted to the ASR service with a subsequent payload while audio streams received in their entirely during the time window and/or previously scheduled for transmission with a current payload may be transmitted with the current payload. The subsequent audio stream payload may be made of another set of audio streams in the N audio streams or a set of audio streams in an N+1 (or N plus a number greater than one) audio streams, left-behind audio streams (not previously received in their entirety during a corresponding time window or previously scheduled for transmission with a current payload) of a previous payload, or a combination. Accordingly, the current single audio stream payload may exclude the remaining set of audio streams.

Transmitting a single audio stream payload, such as payload 110, for transcription may be performed immediately following processing the last audio stream of a time window but no later than an end of a wait time, the wait time starting from a request for onboarding the buffer with one or more of the N audio streams and ending at a subsequent request to re-onboard the buffer with a next audio stream (of the same or a new set of N number of audio streams). Alternatively, transmitting a single audio stream payload for transcription may be performed immediately following processing the last audio stream of a time window but no later than an end of a wait time, the wait time starting from a request for onboarding the buffer with one or more of the set of N audio streams and ending at a subsequent request to re-onboard the buffer with a next audio stream (of the same or a new set). In some embodiments, transmitting a single audio stream payload for transctiption may be performed after processing a predetermined number of audio streams regardless of a time window or it may based on a time window and a predetermined number of audio streams. Transmitting may be performed despite buffer density to prevent noticeable delays in receiving the text file. Where the audio streams have different audio stream sizes, disclosed methods may transmit the payload at the end of the time window regardless of audio stream sizes.

In an embodiment, buffer 122 may be configured in a variety of buffer type implementations suitable for processing and storing audio streams. For example, buffer 122 may be a linear or circular buffer, a last-in-first-out or first-in-first-out buffer. The order of storing the audio streams may be based on or independent of the order in which the audio streams are received from audio sources.

FIG. 2 illustrates an overview system of time-based ASR services, in accordance with some embodiments of the disclosure. In FIG. 2, a time-based ASR services system is configured as a time-based ASR services system 200 to include an audio stream processor 202 receiving audio stream files from an audio source 208. Audio stream processor 202 is further shown to provide a compacted audio stream for audio-to-text services to ASR services 204. Each of ASR services 104 and 204 may be an ASR service suitable for processing audio signals. For example, ASR services 104 and 204 may be performed by any of various ASR service providers including, without limitation, Google LLC of Mountain View, CA and Amazon.com, Inc. of Seattle, WA.

Audio source 208 receives audio input 206, generally provided by a respective user who may be located around the world. Audio source 208 may receive non-user generated audio input. In a non-limiting example, audio source 208 may receive automated commands from one or more users, bots or machine-learning or artificial intelligence processing sources. In this respect, audio source 208 is analogous to the sources 108 of FIG. 1. Indeed, with the exception of functions and embodiments discussed herein or those of obvious variants, the system 200 is analogously configured as system 100.

In system 200, while one audio stream is presumed received by audio stream processor 202, it is understood that typically more than one audio stream may be received from the same or other sources. For example, audio stream processor 202 may receive three audio streams 222. In some embodiments, audio signal processor 218, audio stream interface 216, and storage 220 are configured as audio signal processor 118, audio stream interface 116, and storage 120, respectively, of FIG. 1.

In an exemplary operational scenario, audio stream processor 202 receives, through audio stream interface 216, an audio stream including speech content from audio source 208. Audio stream compactor 214, operating under the direction of audio signal processor 218, compacts the received audio stream to generate a compacted audio stream. Audio stream processor 202 transmits the compacted audio stream for transcription, through audio stream interface 216, to ASR services 204. In response to transmitting the compacted audio stream for transcription, audio stream processor 202, through audio stream interface 216, receives from ASR services 204 a text file with text content that is a transcription of the audio stream. Audio stream processor 202 may itself or through the solicitation of an independent device or service effect text content search of the returned text file for relevant information.

Audio stream compactor 214 may compact the audio stream from audio source 208 in a variety of manners. Done in any suitable manner, compacting an audio stream may remove non-meaningful voice and/or silence from the speech content of an audio stream while compacting the audio stream (or “audio file”) to increase the frequency of transmission of the audio stream to ASR services 204. Compacting the audio stream may comprise trimming the audio stream to remove excess speech content from the speech content of the audio stream. It is understood that more than one audio stream may be trimmed at any given time. In some embodiments, compacting includes trimming the audio stream of a second set of one or more audio streams to remove excess speech content from the speech content of each of the second set of audio streams. Trimming of the second set of audio streams may be performed where transcription charges for transcription of processed audio streams are transaction-based for improved improve cost-effectiveness, for example.

In some embodiments, audio stream compactor 214 performs audio stream compacting by use of lossy or lossless compression algorithms. For example, run-length encoding and decoding may be employed by implementing Lempel-Ziv (LZ) or Lempel-Ziv-Welch (LZW) algorithms. Audio stream compactor 214 may be configured in hardware, software or virtually.

In an embodiment, either or both audio streams of systems 100 and 200 may be encrypted for privacy and reliability reasons. In such cases, decryption may be necessary at a receiving end.

FIGS. 3A and 3B show an exemplary single audio stream payload part, in accordance with disclosed methods and embodiments. Analogous to audio stream payload 110, single audio stream payload 300 may be generated by audio stream processor 102 of FIG. 1 and stored in buffer 122 by buffer processor 114, as previously described relative to FIG. 1. FIG. 3A shows a part of exemplary single audio stream payload 300, built by an audio stream processor of disclosed methods and systems. Payload 300 is shown with three audio streams, audio stream “a”, audio stream “b”, and audio stream “c”. Each audio stream “a”-“c” includes two fields, an audio stream content 302 and an audio stream header 304. For example, audio stream content 302 comprises a series of audio stream contents 302a, 302b, and 302c, each from a unique and independent source or a combination of unique and independent sources, such as sources 108, as earlier described relative to FIG. 1. Audio stream header 304 is a series of audio stream headers, 304a, 304b, and 304c, each belonging to a corresponding audio stream “a”-“c”, respectively. Similarly, audio stream separator 306 is a series of audio stream separators, 306a-306c, each separating two adjacent audio streams of audio streams “a”-“c”. For example, audio stream separator 306a is shown to delineate audio stream “a” from a preceding audio stream (not shown in FIG. 3A), audio stream separator 306b is shown to delineate audio stream “a” from audio stream “b” (or audio stream content 302a and audio stream header 304b), and audio stream separator 306c delineates audio stream “b” from audio stream “c” (or audio stream contents 302b and audio stream header 304c).

In an embodiment, each separator 306a-306c is effectively an audio stream delineation indicator and may be implemented in a variety of manners. For example, each audio stream separator may be a flag, bit (or bytes), a particular memory address or a particular value, a pointer, linked list, or any other designator uniquely identifying the location between two adjacently situated independent audio streams.

Audio stream headers 304a-304c each describe aspects of a corresponding audio stream content. In a non-limiting example, an audio stream header may indicate an audio stream content transmission time, the time at which a corresponding audio stream content was transmitted by a corresponding audio source, or an audio stream length, the length of a corresponding audio stream or audio stream content, or whether or the type of encoding/decoding possibly employed prior to transmission and upon receipt of an audio stream, respectively. In this respect, audio stream header 304a includes information relating to audio stream content 302a of audio stream “a”; audio stream header 304b includes information relating to audio stream content 302b of audio stream “b”; and audio stream header 304c includes information relating to audio stream content 302c of audio stream “c”. While shown located at the beginning of each audio stream “a”, “b”, and “c”, in some embodiments, an audio stream header may be located at the end of or embedded within a corresponding audio stream.

Audio stream content may and typically does include meaningful voice information and non-meaningful voice or silent periods. Non-meaningful information may be the utterance of “Uh” or “Uhm” and a silent period may be a period where no voice or speech is audible or comprehensible.

In FIG. 3B, an exploded view of audio stream “b” of FIG. 3A is shown to include non-meaningful voice and/or silent audio content at 310 while meaningful speech content is shown at 312. In accordance with an embodiment, such as the system 200, audio stream compactor 214 of FIG. 2 would remove the non-meaningful voice and/or silent content parts of the audio stream (shown at 310 in FIG. 3B) while leaving the meaningful speech content 312 hence reducing the audio stream size of audio stream “b” by approximately 30% and increasing system efficiency by approximately 30%, for instance. In some embodiments, the net result is a reduction in ASR service expenses. In some embodiments, an audio stream may be further compacted by trimming at least some of the audio stream header. For example, while the identity of an audio source may remain relevant, the time of audio stream transmission may be a suitable candidate for removal.

In some embodiments, the system may determine the speech-to-text service based on incoming audio streams, such as those from audio sources 108 of FIG. 1 or 208 of FIG. 2. FIG. 4 depicts an illustrative flowchart of a process for determining a STT (or ASR) service approach based on incoming audio streams. In FIG. 4, a process 400 is shown in flowchart form for determining an appropriate STT service based on an analysis of incoming audio streams. In some embodiments, process 400 may be implemented by the audio signal processor 118 of FIG. 1 or the audio signal processor 218 of FIG. 2. It is understood that other suitable signal processor or computing devices may implement the steps and determinations of process 400.

At step 402, an N number of audio streams are received, for example by audio stream processor 102 or 202, of FIGS. 1 and 2, respectively. Next, at 404, a determination is made as to whether the incoming audio streams are to be time-based STT serviced. If at 404, the determination is made to service the audio streams using a time-based approach (“Yes” at 404), process 400 continues onto to step 408 and a time-based STT service approach, for example, like the STT service approach of FIG. 2, is implemented. Otherwise (“No” at 404), process 400 proceeds to 406 where a second determination is made. At 406, the determination is based on a transaction-based service approach. If at 406, a determination is made to implement a transaction-based service approach (“Yes” at 406), process 400 proceeds to step 410 where a transaction-based STT service, such as that of FIG. 1, is implemented. If the determination at 406 yields a negative outcome (“No” at 406), process 400 may resume to process a next batch of N audio streams starting from step 402. In some embodiments where other forms of STT services are available, process 400 may proceed to test for other services after the determination at 406 yields a negative result instead of continuing from step 402. Process 400 may end upon testing for all available STT services or process 400 may resume from step 402 when test for all available STT services is exhausted.

In some embodiments, the order of steps and determinations of process 400 may be changed. For example, the determinations at 404 and 406 may be swapped such that the process tests for a transaction-based approach prior to testing for a time-based approach.

The determination to proceed with a transactional versus a time-based approach may rest, at least in part, on a number of audio stream- or environment-related factors. For example, if the average audio stream size of N number of audio streams exceeds a threshold, process 400 may choose a time-based service approach. In a slow network environment, a transactional-based service approach may be better suited. In some embodiments, determining whether at least one of the audio streams requires transaction-based speech-to-text services is simply based, at least in part, on the ASR services 104 cost-structure. In some embodiments, determining whether at least one of the audio streams requires transaction-based speech-to-text services is based, at least in part, on the size of the time window for receiving the N number of audio streams.

FIG. 5 depicts an illustrative flowchart of a process for determining a transaction-based STT service approach. In FIG. 5, a process 500 is shown in flowchart form for determining a transaction-based STT services approach. The steps and determinations of process 500 will be described relative to FIG. 1 but it is understood that process 500 or any derivations thereof may be equally applicable to embodiments other than that of FIG. 1.

At step 502, in FIG. 5, N number of audio streams, each with speech content, are received during a specified time window. Speech content of each of the N audio streams is analogous to audio stream content 302a, 302b and 302c of FIG. 3A. Audio stream interface 116 may receive 3 audio streams from sources 108, as previously described relative to FIG. 1.

Next, at 504, a determination may be made by buffer processor 114 or audio signal processor 110 as to whether the ASR service to-be-performed is transaction-based or not and if not (“No” at 504), process 500 ends at 516. Otherwise (“Yes” at 504), process 500 continues to step 506. In some embodiments, instead of ending at 516, process 500 may test for other types of ASR services, such as a time-based service or still other services, as described relative to FIG. 4.

At step 506, buffer processor 114 generates N−1 audio stream separators and process 500 next implements step 508. At step 508, buffer processor 114 or audio signal processor 110 concatenate the N audio streams into a buffer, such as buffer 122, to generate a single concatenated audio stream. Process 500 subsequently performs step 510. At step 510, the audio stream separators generated at step 506 are inserted into the concatenated audio stream of step 508 to generate a single audio stream payload in buffer 122. It is understood that while buffer 122 is shown as a single buffer unit or device, buffer 122 may comprise more than one device, therefore, dispersing the single audio stream payload across multiple buffer devices. Next, after completion of step 510, at step 512, audio stream processor 102 transmits the single audio stream payload (such as payload 110) of step 510 from buffer 122 to an ASR service, such as without limitation, ASR service 104, through audio stream interface 116 for transcription.

Audio stream processor 102 may transmit the generated single audio stream payload for transcription immediately following the processing of the last or Nth audio stream. For example, audio stream processor 102 may transmit the single audio stream payload 110 after insertion of the N−1 audio stream separator into the concatenated audio stream.

In an embodiment, buffer processor 114 of audio stream processor 102 makes a request of audio signal processor 118 to onboard the next set of N audio streams onto buffer 110. Audio stream processor 102 may transmit the single audio stream payload no later than an end of a wait time, the wait time starting from a request for onboarding buffer 122 with one or more of the N audio streams and ending at a subsequent request to re-onboard buffer 110 with the next batch (or set) of N audio streams.

Buffer 122 may be filled to capacity upon building payload 110 but in some embodiments, payload 110 may not consume the entire capacity of buffer 122. For example, the time window for receiving all N audio streams may close before the buffer is full or the audio streams may be too short to fill buffer 122 to capacity. In some embodiments, audio stream processor 102 transmits payload 110 to ASR services 104 from buffer 122 despite the density of buffer 122 to prevent noticeable delay by ASR services 104 in receiving the text file.

The N audio streams from sources 108 may have different audio stream sizes. In some embodiments, payload 110 is transmitted when the specific time window ends despite the audio stream sizes. Prior to the transmitting step 512, in FIG. 5, audio signal processor 118 of audio stream processor 102 may determine, for each of the N audio streams, whether the audio stream can be transmitted in its entirety during the time window and based on the determination, audio signal processor 118 may then transmit only a subset of the N audio streams, those that have been received in their entirety while leaving a remaining subset of partially-received audio streams for future transmission.

FIG. 6 depicts an illustrative flowchart of a process for determining a time-based STT service approach. In FIG. 6, a process 600 is shown in flowchart form for determining a time-based STT services approach in accordance with disclosed methods. The steps and determinations of process 600 will be described relative to FIG. 2 but it is understood that process 600 or any derivations thereof may be equally applicable to embodiments other than that of FIG. 2.

At step 602, an audio stream is received from an audio source, such as source 208. The audio stream includes speech content, such as audio stream content 302a, 302b and 302c of FIG. 3A. The audio stream may be received through audio stream interface 216 of audio stream processor 202. At 604, the audio signal processor 218 determines whether ASR services are to be performed pursuant to a time-based approach. Audio signal processor 218 may make the determination at 604 based on various factors, such as but not limited to those discussed above. At 604, a determination may be based on whether at least one of the received audio streams requires time-based speech-to-text services. The foregoing determination may be based at least in part on an average size of N number of audio streams or an average size of the set of audio streams in an application receiving N audio streams.

If a time-based approach is determined not to be implemented (“No” at 604), process 600 ends at 612, otherwise (“Yes” at 604), process 600 continues to step 606. In some embodiments, the determination at 604 may be performed as described relative to FIG. 4.

At step 606, audio stream compactor 214 compacts the received audio stream and process 600 continues to step 608. Next, at step 608, audio signal processor 218 transmits the compacted audio stream, through audio stream interface 216, to ASR services 204 for transcription. At step 610, in response to transmitting the compacted audio stream to ASR services 204, audio stream processor 202 receives, from ASR services 204 through audio stream interface 216, a text file with text content of the of the audio stream speech content.

FIG. 7 is an illustrative block diagram showing an audio processing system, in accordance with some embodiments of the disclosure. In FIG. 7, audio processing system is configured as audio processing system 700 in accordance with some embodiments of the disclosure. In an embodiment, a part or the entirety of system 700 may be configured as either of systems 100, 200, of FIGS. 1, 2, respectively. Although FIG. 7 shows a certain number of components, in various examples, system 700 may include fewer than the illustrated number of components and/or multiples of one or more of the illustrated number of components.

System 700 is shown to include a server 702, a computing device 718, an audio stream processor 712, an ASR services 744, and a communication network 714. Each of the server 702, computing device 718, audio stream processor 712, and ASR services 744 is communicatively coupled to communication network 714. In an embodiment, server 702 may be configured as one or more network elements in communication network 714. In an embodiment, server 702 resides externally to communication network 714, as shown in FIG. 7.

In some embodiments, computing device 718 may be configured as all or part of one of the audio stream sources 108 of FIG. 1 or one of the audio stream sources 208 of FIG. 2. Alternatively, any of the sources 108 may form a part of computing device 718. In an embodiment, server 702 may be configured as audio stream processor 102 or audio stream processor 202.

Communication network 714 may comprise one or more network systems, such as, without limitation, an Internet, LAN, WiFi or other network systems suitable for audio processing applications. In some embodiments, system 700 excludes server 702 and functionality that would otherwise be implemented by server 702 is instead implemented by other components of system 700, such as one or more components of communication network 714. In still other embodiments, server 702 works in conjunction with one or more components of communication network 714 to implement certain functionality described herein in a distributed or cooperative manner. Similarly, in some embodiments, system 700 excludes audio stream processor 712 and functionality that would otherwise be implemented by audio stream processor 712 is instead implemented by other components of system 700, such as one or more components of communication network 714 or server 702. In still other embodiments, audio stream processor 712 works in conjunction with one or more components of communication network 714 or server 702 to implement certain functionality described herein in a distributed or cooperative manner.

Server 702 includes control circuitry 720 and server interface 722, and control circuitry 720 includes storage 724 and processing circuitry 726. Computing device 718, which may be a personal computer, a laptop computer, a tablet computer, a smartphone, entertainment equipment, or any other type of computing device, includes control circuitry 728, speaker 732, display 734, hardware interface 742, and computing device interface 736. Control circuitry 728 includes storage 738 and processing circuitry 740. Control circuitry 720 and/or 728 may be based on any suitable processing circuitry such as processing circuitry 726 and/or 740. As referred to herein, processing circuitry should be understood to mean circuitry based on one or more microprocessors, microcontrollers, digital signal processors, programmable logic devices, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), etc., and may include a multi-core processor (e.g., dual-core, quad-core, hexa-core, or any suitable number of cores). In some embodiments, processing circuitry may be distributed across multiple separate processors, for example, multiple of the same type of processors (e.g., two Intel Core i9 processors) or multiple different processors (e.g., an Intel Core i7 processor and an Intel Core i9 processor). In some embodiments, control circuitry 720 and/or control circuitry 728 are configured to implement an audio processing system, such as system 100 or system 200, or parts thereof, such as audio stream processor 102 and audio stream processor 202, and/or any plugins thereof, each of which is described above in connection with FIGS. 1, 2, respectively.

In some embodiments, audio stream processor 712 may be configured as audio stream processor 102 or audio stream processor 202, of FIGS. 1 and 2, respectively. In some embodiments where audio stream processor 712 is standalone, audio stream processor 712 may be directly communicatively coupled to computing device 718 and/or server 702. In some embodiments where audio stream processor 712 is standalone, audio stream processor 712 may be indirectly communicatively coupled to computing device 718 and/or server 702, through communication network 714. Similarly, audio stream processor 712 may be directly communicatively coupled to ASR services 744 or indirectly coupled to ASR services 744 through communication network 714. In some embodiments, ASR services 744 is analogous to ASR services 104 of FIG. 1 or ASR services 204 of FIG. 2.

In some embodiments, while not shown in FIG. 7, audio stream processor 712, as a standalone unit, may be configured with similar components as server 702 and/or computing device 718. For example, audio stream processor 712 may have a control circuitry analogous to control circuitry 720, a storage device analogous to storage 724 and a processing circuit analogous to processing circuit 726, and an interface analogous to interface 722. For example, storage 724 and storage 120 (FIG. 1) and/or storage 220 (FIG. 2) may be analogously configured. Processing circuit 726 and audio signal processor 118 (FIG. 1) and/or audio signal processor 218 (FIG. 2) may be analogously configured; and interface 722 and audio stream interface 116 (FIG. 1) and/or audio stream interface 216 (FIG. 2) may be analogously configured. In some embodiments, buffer processor 114 of FIG. 1 may be configured as processing circuit 726 and buffer 122 may be configured as storage 724. In a non-limiting operational example, one or more of the server interface 722, interface of the audio stream processor 712, hardware interface 742, and computing device interace 736 may send N number of audio streams to buffer 122 (FIG. 1).

Each of storage 724, storage 738, and/or storages of other components of system 700 (e.g., storages 120 and 220 and/or the like) may be an electronic storage device. As referred to herein, the phrase “electronic storage device” or “storage device” should be understood to mean any device for storing electronic data, computer software, or firmware, such as random-access memory, read-only memory, hard drives, optical drives, digital video disc (DVD) recorders, compact disc (CD) recorders, BLU-RAY disc (BD) recorders, BLU-RAY 3D disc recorders, digital video recorders (DVRs, sometimes called personal video recorders, or PVRs), solid state devices, quantum storage devices, gaming consoles, gaming media, or any other suitable fixed or removable storage devices, and/or any combination of the same. Each of storage 724, storage 738, and/or storages of other components of system 700 may be used to store various types of content, metadata, and or other types of data. Non-volatile memory may also be used (e.g., to launch a boot-up routine and other instructions). Cloud-based storage may be used to supplement storages 724, 738 or instead of storages 724, 738. In some embodiments, control circuitry 720 and/or 728 executes instructions for an application stored in memory (e.g., storage 724 and/or 738). Specifically, control circuitry 720 and/or 728 may be instructed by the application to perform the functions discussed herein. In some implementations, any action performed by control circuitry 720 and/or 728 may be based on instructions received from the application. For example, the application may be implemented as software or a set of executable instructions that may be stored in storage 724 and/or 738 and executed by control circuitry 720 and/or 728. In some embodiments, the application may be a client/server application where only a client application resides on computing device 718, and a server application resides on server 702.

The application may be implemented using any suitable architecture. For example, it may be a stand-alone application wholly implemented on computing device 718. In such an approach, instructions for the application are stored locally (e.g., in storage 738), and data for use by the application is downloaded on a periodic basis (e.g., from an out-of-band feed, from an Internet resource, or using another suitable approach). Control circuitry 728 may retrieve instructions for the application from storage 738 and process the instructions to perform the functionality described herein. Based on the processed instructions, control circuitry 728 may determine what action to perform when input is received from interface 736.

In client/server-based embodiments, control circuitry 728 may include communication circuitry suitable for communicating with an application server (e.g., server 702) or other networks or servers. The instructions for carrying out the functionality described herein may be stored on the application server. Communication circuitry may include a cable modem, an Ethernet card, or a wireless modem for communication with other equipment, or any other suitable communication circuitry. Such communication may involve the Internet or any other suitable communication networks or paths (e.g., communication network 714). In another example of a client/server-based application, control circuitry 728 runs a web browser that interprets web pages provided by a remote server (e.g., server 702). For example, the remote server may store the instructions for the application in a storage device. The remote server may process the stored instructions using circuitry (e.g., control circuitry 720) and/or generate displays. Computing device 718 may receive the displays generated by the remote server and may display the content of the displays locally via display 734. This way, the processing of the instructions is performed remotely (e.g., by server 702) while the resulting displays, such as the display windows described elsewhere herein, are provided locally on computing device 718. Computing device 718 may receive inputs from the user via computing device interface 736 and transmit those inputs to the remote server for processing and generating the corresponding displays.

A user may send instructions to control circuitry 720 and/or 728 using user input interface 736. Interface 736 may be any suitable user interface, such as a remote control, trackball, keypad, keyboard, touchscreen, touchpad, stylus input, joystick, voice recognition interface, a gaming controller, or other user input interfaces. In an embodiment, interface 736 is configured as at least a part of an audio source, such as audio source 108 or audio source 208. Interface 736 may be integrated with or combined with display 734, which may be a monitor, a television, a liquid crystal display (LCD), electronic ink display, or any other equipment suitable for displaying visual images. In an embodiment, display 734 may be a part of an audio source, such as audio source 108 or audio source 208.

Server 702 and computing device 718 may transmit and receive content and data via interfaces 722 and 742. For instance, interface 722 may include a communication port configured to receive audio streams via communication network 714, and/or to communicate payload and text file information to and from ASR services 744. Control circuitry 720, 728 may be used to send and receive commands, requests, and other suitable data using interfaces 722, 742, respectively.

In some embodiments, a part or the entirety of system 700 carries out the steps and determinations of the flowcharts of FIGS. 4