Classifications

• • G—PHYSICS
  • G10—MUSICAL INSTRUMENTS; ACOUSTICS
  • G10L—SPEECH ANALYSIS TECHNIQUES OR SPEECH SYNTHESIS; SPEECH RECOGNITION; SPEECH OR VOICE PROCESSING TECHNIQUES; SPEECH OR AUDIO CODING OR DECODING
  • G10L19/00—Speech or audio signals analysis-synthesis techniques for redundancy reduction, e.g. in vocoders; Coding or decoding of speech or audio signals, using source filter models or psychoacoustic analysis
  • G10L19/04—Speech or audio signals analysis-synthesis techniques for redundancy reduction, e.g. in vocoders; Coding or decoding of speech or audio signals, using source filter models or psychoacoustic analysis using predictive techniques
  • G10L19/16—Vocoder architecture
  • G10L19/167—Audio streaming, i.e. formatting and decoding of an encoded audio signal representation into a data stream for transmission or storage purposes
• • G—PHYSICS
  • G10—MUSICAL INSTRUMENTS; ACOUSTICS
  • G10L—SPEECH ANALYSIS TECHNIQUES OR SPEECH SYNTHESIS; SPEECH RECOGNITION; SPEECH OR VOICE PROCESSING TECHNIQUES; SPEECH OR AUDIO CODING OR DECODING
  • G10L19/00—Speech or audio signals analysis-synthesis techniques for redundancy reduction, e.g. in vocoders; Coding or decoding of speech or audio signals, using source filter models or psychoacoustic analysis
• • G—PHYSICS
  • G10—MUSICAL INSTRUMENTS; ACOUSTICS
  • G10L—SPEECH ANALYSIS TECHNIQUES OR SPEECH SYNTHESIS; SPEECH RECOGNITION; SPEECH OR VOICE PROCESSING TECHNIQUES; SPEECH OR AUDIO CODING OR DECODING
  • G10L21/00—Speech or voice signal processing techniques to produce another audible or non-audible signal, e.g. visual or tactile, in order to modify its quality or its intelligibility
  • G10L21/02—Speech enhancement, e.g. noise reduction or echo cancellation
  • G10L21/0316—Speech enhancement, e.g. noise reduction or echo cancellation by changing the amplitude
  • G10L21/0364—Speech enhancement, e.g. noise reduction or echo cancellation by changing the amplitude for improving intelligibility
• • G—PHYSICS
  • G10—MUSICAL INSTRUMENTS; ACOUSTICS
  • G10L—SPEECH ANALYSIS TECHNIQUES OR SPEECH SYNTHESIS; SPEECH RECOGNITION; SPEECH OR VOICE PROCESSING TECHNIQUES; SPEECH OR AUDIO CODING OR DECODING
  • G10L25/00—Speech or voice analysis techniques not restricted to a single one of groups G10L15/00 - G10L21/00
  • G10L25/03—Speech or voice analysis techniques not restricted to a single one of groups G10L15/00 - G10L21/00 characterised by the type of extracted parameters
• • H—ELECTRICITY
  • H03—ELECTRONIC CIRCUITRY
  • H03G—CONTROL OF AMPLIFICATION
  • H03G11/00—Limiting amplitude; Limiting rate of change of amplitude
  • H03G11/008—Limiting amplitude; Limiting rate of change of amplitude of digital or coded signals
• • H—ELECTRICITY
  • H03—ELECTRONIC CIRCUITRY
  • H03G—CONTROL OF AMPLIFICATION
  • H03G3/00—Gain control in amplifiers or frequency changers
  • H03G3/002—Control of digital or coded signals
• • H—ELECTRICITY
  • H03—ELECTRONIC CIRCUITRY
  • H03G—CONTROL OF AMPLIFICATION
  • H03G7/00—Volume compression or expansion in amplifiers
  • H03G7/007—Volume compression or expansion in amplifiers of digital or coded signals

Definitions

• the present disclosure further relates to a method of encoding audio data and metadata for dynamic loudness adjustment and/or dynamic range compression into a bitstream.
• the present disclosure yet further relates to a respective decoder and encoder as well as to a respective system and computer program products. While some embodiments will be described herein with particular reference to that disclosure, it will be appreciated that the present disclosure is not limited to such a field of use and is applicable in broader contexts. BACKGROUND Any discussion of the background art throughout the disclosure should in no way be considered as an admission that such art is widely known or forms part of common general knowledge in the field. In playing back audio content, loudness is the individual experience of sound pressure.
• the loudness of dialogue in a program has been found to be the most crucial parameter determining the perception of program loudness by a listener.
• the average loudness is typically required for loudness compliance (for example, the CALM act in the US), and is also used for aligning dynamic range control (DRC) parameters.
• the dynamic range of a program is the difference between its quietest and loudest sounds.
• the dynamic range of a program depends on its content, for example, an action movie may have a different and wider dynamic range than a documentary, and reflects a creator's intent. However, capabilities of devices to play back audio content in the original dynamic range vary strongly.
• loudness management is thus a further key factor in providing optimal listening experience.
• the entire audio program or an audio program segment has to be analyzed and the resulting loudness and DRC parameters can be delivered along with audio data or encoded audio data to be applied in a decoder or playback device.
• loudness processing or levelling is used to ensure loudness compliance and, if applicable, potential dynamic range constraints depending on playback requirements. This approach delivers processed audio that is “optimized” for a single playback environment.
• a method of metadata-based dynamic processing of audio data for playback may include receiving, by a decoder, a bitstream including audio data and metadata for dynamic loudness.
• the method may further include decoding, by the decoder, the audio data and the metadata to obtain decoded audio data and the metadata.
• the method may further include determining, by the decoder, from the metadata, one or more processing parameters for dynamic loudness adjustment based on a playback condition.
• the method may further include applying the determined one or more processing parameters to the decoded audio data to obtain processed audio data. And the method may include outputting the processed audio data for playback.
• the metadata for dynamic loudness adjustment may include a plurality of sets of metadata, with each set corresponding to a respective (e.g., different) playback condition.
• determining the one or more processing parameters for dynamic loudness adjustment from the metadata based on a (specific) playback condition may include selecting, in response to playback condition information provided to the decoder, a set of metadata corresponding to the (specific) playback condition, and extracting the one or more processing parameters for dynamic loudness adjustment from the selected set of metadata.
• the playback condition information may be indicative of the (specific) playback condition or information derived therefrom.
• the metadata may be indicative of processing parameters for dynamic loudness adjustment for a plurality of playback conditions.
• said determining the one or more processing parameters may further include determining one or more processing parameters for dynamic range compression, DRC, based on the playback condition.
• the playback condition information may be indicative of a specific loudspeaker setup.
• the playback condition may include one or more of a device type of the decoder, characteristics of a playback device, characteristics of a loudspeaker, a loudspeaker setup, characteristics of background noise, characteristics of ambient noise and characteristics of the acoustic environment.
• the selected set of metadata may include a set of DRC sequences, DRCSet.
• each of the sets of metadata may include a respective set of DRC sequences, DRCSet.
• said determining the one or more processing parameters may be said to further include selecting, by the decoder, at least one of a set of DRC sequences, DRCSet, a set of equalizer parameters, EQSet, and a downmix, corresponding to the playback condition.
• said determining the one or more processing parameters may further include identifying a metadata identifier indicative of the at least one selected DRCSet, EQSet and downmix to determine the one or more processing parameters from the metadata.
• selecting the set of metadata may include identifying a set of metadata corresponding to a specific downmix. The specific downmix may be determined based on the loudspeaker setup.
• the metadata may include one or more processing parameters relating to average loudness values and optionally one or more processing parameters relating to dynamic range compression characteristics.
• each set of metadata may include such one or more processing parameters relating to average loudness values and optionally one or more processing parameters relating to dynamic range compression characteristics.
• the bitstream may further include additional metadata for static loudness adjustment to be applied to the decoded audio data.
• the bitstream may be an MPEG-D DRC bitstream and the presence of metadata may be signaled based on MPEG-D DRC bitstream syntax.
• a loudnessInfoSetExtension()-element may be used to carry the metadata as a payload.
• the metadata may comprise one or more metadata payloads, wherein each metadata payload may include a plurality of sets of parameters and identifiers, with each set including at least one of a DRCSet identifier, drcSetId, an EQSet identifier, eqSetId, and a downmix identifier, downmixId, in combination with one or more processing parameters relating to the identifiers in the set.
• said determining the one or more processing parameters may involve selecting a set among the plurality of sets in the payload based on the at least one DRCSet, EQSet, and downmix selected by the decoder, wherein the one or more processing parameters determined by the decoder may be the one or more processing parameters relating to the identifiers in the selected set.
• the decoder may comprise one or more processors and non-transitory memory configured to perform a method including receiving, by the decoder, a bitstream including audio data and metadata for dynamic loudness adjustment; decoding, by the decoder, the audio data and the metadata to obtain decoded audio data and the metadata; determining, by the decoder, from the metadata, one or more processing parameters for dynamic loudness adjustment based on a playback condition; applying the determined one or more processing parameters to the decoded audio data to obtain processed audio data; and outputting the processed audio data for playback.
• the metadata for dynamic loudness adjustment may include a plurality of sets of metadata, with each set corresponding to a respective (e.g., different) playback condition.
• determining the one or more processing parameters for dynamic loudness adjustment from the metadata based on a (specific) playback condition may include selecting, in response to playback condition information provided to the decoder, a set of metadata corresponding to the (specific) playback condition, and extracting the one or more processing parameters for dynamic loudness adjustment from the selected set of metadata.
• the playback condition information may be indicative of the (specific) playback condition or information derived therefrom.
• the method may further include generating the metadata for dynamic loudness adjustment based on the loudness processed audio data and the original audio data. And the method may include encoding the original audio data and the metadata into the bitstream.
• the metadata may include a plurality of sets of metadata. Each set of metadata may correspond to a respective (e.g., different) playback condition.
• the method may further include generating additional metadata for static loudness adjustment to be used by a decoder.
• said generating metadata may include comparison of the loudness processed audio data to the original audio data, wherein the metadata may be generated based on a result of said comparison.
• said generating metadata may further include measuring the loudness over one or more pre-defined time periods, wherein the metadata may be generated further based on the measured loudness.
• the measuring may comprise measuring overall loudness of the audio data.
• the measuring may comprise measuring loudness of dialogue in the audio data.
• the bitstream may be an MPEG-D DRC bitstream and the presence of the metadata may be signaled based on MPEG-D DRC bitstream syntax.
• a loudnessInfoSetExtension()-element may be used to carry the metadata as a payload.
• the metadata may comprise one or more metadata payloads, wherein each metadata payload may include a plurality of sets of parameters and identifiers, with each set including at least one of a DRCSet identifier, drcSetId, an EQSet identifier, eqSetId, and a downmix identifier, downmixId, in combination with one or more processing parameters relating to the identifiers in the set, and wherein the one or more processing parameters may be parameters for dynamic loudness adjustment by a decoder.
• the at least one of the drcSetId, the eqSetId, and the downmixId may be related to at least one of a set of DRC sequences, DRCSet, a set of equalizer parameters, EQSet, and downmix, to be selected by the decoder.
• the encoder may comprise one or more processors and non-transitory memory configured to perform a method including inputting original audio data into a loudness leveler for loudness processing to obtain, as an output from the loudness leveler, loudness processed audio data; generating the metadata for dynamic loudness adjustment based on the loudness processed audio data and the original audio data; and encoding the original audio data and the metadata into the bitstream.
• a fifth aspect of the present disclosure there is provided a system of an encoder for encoding in a bitstream original audio data and metadata for dynamic loudness adjustment, and a decoder for metadata-based dynamic processing of audio data for playback.
• FIG. 1 illustrates an example of a decoder for metadata-based dynamic processing of audio data for playback.
• FIG. 1 illustrates an example of a decoder for metadata-based dynamic processing of audio data for playback.
• FIG. 2 illustrates an example of a method of metadata-based dynamic processing of audio data for playback.
• FIG. 3 illustrates an example of an encoder for encoding in a bitstream original audio data and metadata for dynamic loudness adjustment.
• FIG.4 illustrates an example of a method of encoding audio data and metadata for dynamic loudness adjustment, into a bitstream.
• FIG. 5 illustrates an example of a device comprising one or more processors and non-transitory memory configured to perform the methods described herein.
• DESCRIPTION OF EXAMPLE EMBODIMENTS Overview The average loudness of a program or dialogue is the main parameter or value used for loudness compliance of broadcast or streaming programs. The average loudness is typically set to -24 or - 23 LKFS.
• this single loudness value representing the loudness of the entire program is carried in the bitstream.
• This value in the decoding process allows gain adjustments that result in predictable playback levels, so that programs play back at known consistent levels. Therefore, it is important that this loudness value is set properly and accurately. Since the average loudness is dependent on measuring the entire program prior to encoding, for real-time situations such as dynamic encoding with unknown loudness and dynamic range variation, this is, however, not possible. When it is not possible to measure the loudness of the entire file prior to encoding, a dynamic loudness leveler is often used to modify or contour the audio data prior to encoding so that it meets the required loudness.
• This type of loudness management is often seen as an inferior method to meet compliance, as it often changes the dynamic range intercorrelation in the audio content and may thus change the creative intent. This is especially the case when it is desired to distribute one audio asset for all playback devices, which is one of the benefits of metadata driven codec and delivering systems.
• audio content is mixed with the required target loudness, and the corresponding loudness metadata is set to that value.
• a loudness leveler might still be used in those situations as it will be used to help steer the audio content to the target loudness but it will not be that lecturactive“ and is only used to when the audio content starts to deviate from the required target loudness.
• methods and apparatus described herein aim at making real-time processing situations, also denoted as dynamic processing situations, also metadata driven.
• the metadata allow for dynamic loudness adjustment and dynamic range compression in real-time situations.
• the methods and apparatus as described advantageously enable: • Use of real-time loudness adjustment and DRC in MPEG-D DRC syntax; • Use of real-time loudness adjustment and DRC in combination with downmixId; • Use of real-time loudness adjustment and DRC in combination with drcSetId; • Use of real-time loudness adjustment and DRC in combination with eqSetId.
• a decoder can search based on the syntax a given payload for an appropriate set of parameters and identifiers, by matching the aforementioned settings to the identifiers.
• the parameters included in the set whose identifiers best match the settings can then be selected as the processing parameters for dynamic loudness adjustment to be applied to received original audio data for correction.
• multiple sets of parameters for dynamic processing multiple instances of dynLoudCompValue
• the metadata-driven dynamic loudness compensation in addition to correcting the overall loudness, can also be used to “center” the DRC gain calculation and application.
• Metadata-based dynamic processing of audio data Referring to the example of Figure 1, a decoder 100 for metadata-based dynamic processing of audio data for playback is described.
• the decoder 100 may comprise one or more processors and non-transitory memory configured to perform a method including the processes as illustrated in the example of Figure 2 by means of steps S101 to S105.
• the decoder 100 may receive a bitstream including audio data and metadata and may be able to output the unprocessed (original) audio data, the processed audio data after application of dynamic processing parameters determined from the metadata and/or the metadata itself depending on requirements.
• the decoder 100 may receive a bitstream including audio data and metadata for dynamic loudness adjustment and optionally, dynamic range compression (DRC).
• the audio data may be encoded audio data, the audio data may further be unprocessed. That is, the audio data may be said to be original audio data.
• the metadata may include a plurality of sets of metadata. For example, each payload of metadata may include such plurality of sets of metadata.
• the bitstream may be an MPEG-D DRC bitstream.
• the presence of metadata for dynamic processing of audio data may then be signaled based on MPEG-D DRC bitstream syntax.
• a loudnessInfoSetExtension()-element may be used to carry the metadata as a payload as detailed further below.
• the audio data and the metadata may then be decoded, by the decoder, to obtain decoded audio data and the metadata.
• the metadata may include one or more processing parameters relating to average loudness values and optionally one or more processing parameters relating to dynamic range compression characteristics.
• each set of metadata may include respective processing parameters.
• the metadata allows to apply dynamic or real-time correction. For example, when encoding and decoding for live real-time playout, the application of the “real-time” or dynamic loudness metadata is desired to ensure that the live playout audio is properly loudness managed.
• the decoder determines, from the metadata, one or more processing parameters for dynamic loudness adjustment based on a playback condition. This may be done by using the playback condition or information derived from the playback condition (e.g., playback condition information), to identify an appropriate set of metadata among the plurality of sets of metadata.
• a playback condition may include one or more of a device type of the decoder, characteristics of a playback device, characteristics of a loudspeaker, a loudspeaker setup, characteristics of background noise, characteristics of ambient noise and characteristics of the acoustic environment.
• the playback condition information may be indicative of a specific loudspeaker setup. The consideration of a playback condition allows the decoder for a targeted selection of processing parameters for dynamic loudness adjustment with regard to device and environmental constraints.
• the process of determining the one or more processing parameters in step S103 may further include selecting, by the decoder, at least one of a set of DRC sequences, DRCSet, set of equalizer parameters, EQSet, and a downmix, corresponding to the playback condition.
• the at least one of a DRCSet, EQSet and downmix correlates with or is indicative of the individual device and environmental constraints due to the playback condition.
• step S103 involves selecting a set of DRC sequences, DRCSet.
• the selected set of metadata may include such set of DRC sequences.
• the process of determining in step S103 may further include identifying a metadata identifier indicative of the at least one selected DRCSet, EQSet and DownmixSet to determine the one or more processing parameters from the metadata.
• the metadata identifier thus enables to connect the metadata with a corresponding selected DRCSet, EQSet, and/or downmix, and thus with a respective playback condition.
• the specific loudspeaker setup may be used to determine a downmix, which in turn may be used for identifying and selecting an appropriate one among the plurality of sets of metadata. In such case, the specific loudspeaker setup and/or the downmix may be indicated by the aforementioned playback condition information.
• the metadata may comprise one or more metadata payloads (e.g., dynLoudComp() payloads, such as shown in Table 5 below), wherein each metadata payload may include a plurality of sets of parameters (e.g., parameters dynLoudCompValue) and identifiers, with each set including at least one of a DRCSet identifier, drcSetId, an EQSet identifier, eqSetId, and a downmix identifier, downmixId, in combination with one or more processing parameters relating to the identifiers in the set.
• dynLoudComp() payloads such as shown in Table 5 below
• each metadata payload may include a plurality of sets of parameters (e.g., parameters dynLoudCompValue) and identifiers, with each set including at least one of a DRCSet identifier, drcSetId, an EQSet identifier, e
• each payload may comprise an array of entries, each entry including processing parameters and identifiers (e.g., drcSetId, eqSetId, downmixId).
• the array of entries may correspond to the plurality of sets of metadata mentioned above.
• each entry comprises the downmix identifier.
• the determining in step S103 may thus involve selecting a set among the plurality of sets in the payload based on the downmix selected by the decoder (or alternatively, based on the at least one DRCSet, EQSet, and downmix), wherein the one or more processing parameters determined in step S103 may be the one or more processing parameters relating to the identifiers in the selected set.
• the decoder can search a given payload for an appropriate set of parameters and identifiers, by matching the aforementioned settings to the identifiers.
• the parameters included in the set whose identifiers best match the settings can then be selected as the processing parameters for dynamic loudness adjustment.
• the determined one or more processing parameters may then be applied, by the decoder, to the decoded audio data to obtain processed audio data.
• the processed audio data for example live real-time audio data, are thus properly loudness managed.
• the processed audio data may then be output for playback.
• the bitstream may further include additional metadata for static loudness adjustment to be applied to the decoded audio data.
• Static loudness adjustment refers in contrast to dynamic processing for real-time situations to processing performed for general loudness normalization. Carrying the metadata for dynamic processing separately from the additional metadata for general loudness normalization allows to not have the “real-time” correction applied. For example, when encoding and decoding for live real-time playout, the application of dynamic processing is desired to ensure that the live playout audio is properly loudness managed. But for a non-real-time playout, or a transcoding where the dynamic correction is not desired or required, the dynamic processing parameters determined from the metadata do not have to be applied.
• the originally unprocessed content can be retained, if desired.
• the original audio is encoded along with the metadata.
• the dynamic loudness metadata distinct from the long-term loudness measurement/information, such as contentLoudness (in ISO/IEC 23003-4) as described above has some advantages. If combined, the loudness of the content (or what it should be after the dynamic loudness metadata is applied) would not indicate the actual loudness of the content, as the metadata available would be a composite value.
• the dynamic processing metadata may be used or stored for archive or on-demand services. Therefore, for the archive or on-demand services, a more accurate, or compliant loudness measurement, based on the entire program can be carried out, and the appropriate metadata reset. For use-cases where a fixed target loudness is used throughout the workflow, for example in a R128 compliant situation where -23 LKFS is recommended, this is also beneficial.
• an encoder for encoding in a bitstream original audio data and metadata for dynamic loudness adjustment and optionally, dynamic range compression, DRC is described which may comprise one or more processors and non-transitory memory configured to perform a method including the processes as illustrated in the steps in the example of Figure 4.
• step S201 original audio data may be input into a loudness leveler, 201, for loudness processing to obtain, as an output from the loudness leveler, 201, loudness processed audio data.
• step S202 metadata for dynamic loudness adjustment may then be generated based on the loudness processed audio data and the original audio data. Appropriate smoothing and time frames may be used to reduce artifacts.
• step S202 may include comparison of the loudness processed audio data to the original audio data, by an analyzer, 202, wherein the metadata may be generated based on a result of said comparison. The metadata thus generated can emulate the effect of the leveler at the decoder site.
• the metadata may include: - Gain (wideband and/or multiband) processing parameters such that when applied to the original audio will produced loudness compliant audio for playback; - Processing parameters describing the dynamics of the audio such as o Peak – sample and true peak o Short-term loudness values o Change of short-term loudness values.
• step S202 may further include measuring, by the analyzer, 202, the loudness over one or more pre-defined time periods, wherein the metadata may be generated further based on the measured loudness.
• the measuring may comprise measuring overall loudness of the audio data. Alternatively, or additionally, in an embodiment, the measuring may comprise measuring loudness of dialogue in the audio data.
• the original audio data and the metadata may then be encoded into the bitstream.
• bitstream may be an MPEG-D DRC bitstream and the presence of the metadata may be signaled based on MPEG-D DRC bitstream syntax.
• a loudnessInfoSetExtension()-element may be used to carry the metadata as a payload as detailed further below.
• the metadata may comprise one or more metadata payloads, wherein each metadata payload may include a plurality of sets of parameters and identifiers, with each set including at least one of a DRCSet identifier, drcSetId, an EQSet identifier, eqSetId, and a downmix identifier, downmixId, in combination with one or more processing parameters relating to the identifiers in the set, and wherein the one or more processing parameters may be parameters for dynamic loudness adjustment by a decoder.
• the at least one of the drcSetId, the eqSetId, and the downmixId may be related to at least one of a set of DRC sequences, DRCSet, a set of equalizer parameters, EQSet, and a downmix, to be selected by the decoder.
• the metadata may be said to include a plurality of sets of metadata, with each set corresponding to a respective playback condition (e.g., to a different playback condition).
• the method may further include generating additional metadata for static loudness adjustment to be used by a decoder.
• the methods described herein may be implemented on a decoder or an encoder, respectively, wherein the decoder and the encoder may comprise one or more processors and non-transitory memory configured to perform said methods.
• An example of a device having such processing capability is illustrated in the example of Figure 5 showing said device, 300, including two processors, 301, and non-transitory memory, 302.
• the methods described herein can further be implemented on a system of an encoder for encoding in a bitstream original audio data and metadata for dynamic loudness adjustment and optionally, dynamic range compression, DRC, and a decoder for metadata-based dynamic processing of audio data for playback as described herein.
• the methods may further be implemented as a computer program product comprising a computer-readable storage medium with instructions adapted to cause the device to carry out said methods when executed by a device having processing capability.
• the computer program product may be stored on a computer-readable storage medium.
• MPEG-D DRC modified bitstream syntax In the following, it will be described how the MPEG-D DRC bitstream syntax, as described in ISO/IEC 23003-4, may be modified in accordance with embodiments described herein.
• the MPEG-D DRC syntax may be extended, e.g. the loudnessInfoSetExtension()-element shown in Table 2 below, in order to also carry the dynamic processing metadata as a frame- based dynLoudComp update.
• another switch-case UNIDRCLOUDEXT_DYNLOUDCOMP may be added in the loudnessInfoSetExtension()-element as shown in Table 1.
• the switch-case UNIDRCLOUDEXT_DYNLOUDCOMP may be used to identify a new element dynLoudComp() as shown in Table 5.
• the loudnessInfoSetExtension()-element may be an extension of the loudnessInfoSet()-element as shown in Table 2. Further, the loudnessInfoSet()- element may be part of the uniDRC()-element as shown in Table 3.
• Table 4 loudnessInfoSet extension types New dynLoudComp(): Table 5: Syntax of dynLoudComp()-element •
• the drcSetId enables dynLoudComp (relating to the metadata) to be applied per DRC- set.
• the eqSetId enables dynLoudComp to be applied in combination with different settings for the equalization tool.
• the downmixId enables dynLoudComp to be applied per DownmixID.
• the dynLoudComp() element may also include a methodDefinition parameter (specified by, e.g., 4 bits) specifying a loudness measurement method used for deriving the dynamic program loudness metadata (e.g., anchor loudness, program loudness, short-term loudness, momentary loudness, etc.) and/or a measurementSystem parameter (specified by, e.g., 4 bits) specifying a loudness measurement system used for measuring the dynamic program loudness metadata (e.g., EBU R.128, ITU-R BS-1770 with or without preprocessing, ITU-R BS-1771, etc.).
• a methodDefinition parameter specified by, e.g., 4 bits
• a loudness measurement method used for deriving the dynamic program loudness metadata e.g., anchor loudness, program loudness, short-term loudness, momentary loudness, etc.
• a measurementSystem parameter specified by, e.g., 4 bits
• Such parameters may, e.
• Table 8 Syntax of loudnessInfoV2() payload
• the dynLoudComp()-element could be placed into the uniDrcGainExtension()- element.
• Table 9 Syntax of uniDrcGain()-element
• Table 10 Syntax of uniDrcGainExtension()-element
• Table 11 UniDrc gain extension types Semantics dynLoudCompValue This field contains the value for dynLoudCompDb. The values are encoded according to the table below. The default value is 0 dB.
• Table 12 Coding of dynLoudCompValue field Updated MPEG-D DRC Loudness Normalization Processing
• Such control may be provided by updating the MPEG-D DRC interface syntax to include an additional interface extension (e.g., UNIDRCINTERFACEEXT_DYNLOUD) which contains a revised loudness normalization control interface payload (e.g., loudnessNormalizationControlInterfaceV1()) as shown in the following tables.
• an additional interface extension e.g., UNIDRCINTERFACEEXT_DYNLOUD
• loudnessNormalizationControlInterfaceV1() e.g., loudnessNormalizationControlInterfaceV1()
• Table 19 Syntax of uniDRCInterfaceExtension() payload
• Table 20 Syntax of loudnessNormalizationControlInterfaceV1() payload
• processor may refer to any device or portion of a device that processes electronic data, e.g., from registers and/or memory to transform that electronic data into other electronic data that, e.g., may be stored in registers and/or memory.
• a “computer” or a “computing machine” or a “computing platform” may include one or more processors.
• the methodologies described herein are, in one example embodiment, performable by one or more processors that accept computer-readable (also called machine-readable) code containing a set of instructions that when executed by one or more of the processors carry out at least one of the methods described herein.
• Any processor capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken are included.
• processors may include one or more of a CPU, a graphics processing unit, and a programmable DSP unit.
• the processing system further may include a memory subsystem including main RAM and/or a static RAM, and/or ROM.
• a bus subsystem may be included for communicating between the components.
• the processing system further may be a distributed processing system with processors coupled by a network. If the processing system requires a display, such a display may be included, e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT) display. If manual data entry is required, the processing system also includes an input device such as one or more of an alphanumeric input unit such as a keyboard, a pointing control device such as a mouse, and so forth.
• the processing system may also encompass a storage system such as a disk drive unit.
• the processing system in some configurations may include a sound output device, and a network interface device.
• the memory subsystem thus includes a computer-readable carrier medium that carries computer-readable code (e.g., software) including a set of instructions to cause performing, when executed by one or more processors, one or more of the methods described herein.
• computer-readable code e.g., software
• the software may reside in the hard disk, or may also reside, completely or at least partially, within the RAM and/or within the processor during execution thereof by the computer system.
• the memory and the processor also constitute computer-readable carrier medium carrying computer-readable code.
• a computer-readable carrier medium may form, or be included in a computer program product.
• the one or more processors operate as a standalone device or may be connected, e.g., networked to other processor(s), in a networked deployment, the one or more processors may operate in the capacity of a server or a user machine in server-user network environment, or as a peer machine in a peer-to-peer or distributed network environment.
• the one or more processors may form a personal computer (PC), a tablet PC, a Personal Digital Assistant (PDA), a cellular telephone, a web appliance, a network router, switch or bridge, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine.
• machine shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein.
• a computer-readable carrier medium carrying a set of instructions, e.g., a computer program that is for execution on one or more processors, e.g., one or more processors that are part of web server arrangement.
• example embodiments of the present disclosure may be embodied as a method, an apparatus such as a special purpose apparatus, an apparatus such as a data processing system, or a computer-readable carrier medium, e.g., a computer program product.
• the computer-readable carrier medium carries computer readable code including a set of instructions that when executed on one or more processors cause the processor or processors to implement a method. Accordingly, aspects of the present disclosure may take the form of a method, an entirely hardware example embodiment, an entirely software example embodiment or an example embodiment combining software and hardware aspects. Furthermore, the present disclosure may take the form of carrier medium (e.g., a computer program product on a computer-readable storage medium) carrying computer- readable program code embodied in the medium. The software may further be transmitted or received over a network via a network interface device.
• carrier medium is in an example embodiment a single medium
• carrier medium should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions.
• carrier medium shall also be taken to include any medium that is capable of storing, encoding or carrying a set of instructions for execution by one or more of the processors and that cause the one or more processors to perform any one or more of the methodologies of the present disclosure.
• a carrier medium may take many forms, including but not limited to, non-volatile media, volatile media, and transmission media.
• Non-volatile media includes, for example, optical, magnetic disks, and magneto-optical disks.
• Volatile media includes dynamic memory, such as main memory.
• Transmission media includes coaxial cables, copper wire and fiber optics, including the wires that comprise a bus subsystem. Transmission media may also take the form of acoustic or light waves, such as those generated during radio wave and infrared data communications.
• carrier medium shall accordingly be taken to include, but not be limited to, solid-state memories, a computer product embodied in optical and magnetic media; a medium bearing a propagated signal detectable by at least one processor or one or more processors and representing a set of instructions that, when executed, implement a method; and a transmission medium in a network bearing a propagated signal detectable by at least one processor of the one or more processors and representing the set of instructions.
• any one of the terms comprising, comprised of or which comprises is an open term that means including at least the elements/features that follow, but not excluding others.
• the term comprising, when used in the claims should not be interpreted as being limitative to the means or elements or steps listed thereafter.
• the scope of the expression a device comprising A and B should not be limited to devices consisting only of elements A and B.
• Any one of the terms including or which includes or that includes as used herein is also an open term that also means including at least the elements/features that follow the term, but not excluding others. Thus, including is synonymous with and means comprising.
• a method of metadata-based dynamic processing of audio data for playback including processes of: (a) receiving, by a decoder, a bitstream including audio data and metadata for dynamic loudness adjustment; (b) decoding, by the decoder, the audio data and the metadata to obtain decoded audio data and the metadata; (c) determining, by the decoder, from the metadata, one or more processing parameters for dynamic loudness adjustment based on a playback condition; (d) applying the determined one or more processing parameters to the decoded audio data to obtain processed audio data; and (e) outputting the processed audio data for playback.
• EEE2 The method according to EEE1, wherein the metadata is indicative of processing parameters for dynamic loudness adjustment for a plurality of playback conditions.
• determining the one or more processing parameters further includes determining one or more processing parameters for dynamic range compression, DRC, based on the playback condition EEE4.
• the playback condition includes one or more of a device type of the decoder, characteristics of a playback device, characteristics of a loudspeaker, a loudspeaker setup, characteristics of background noise, characteristics of ambient noise and characteristics of the acoustic environment.
• process (c) further includes selecting, by the decoder, at least one of a set of DRC sequences, DRCSet, a set of equalizer parameters, EQSet, and a downmix, corresponding to the playback condition.
• process (c) further includes identifying a metadata identifier indicative of the at least one selected DRCSet, EQSet, and downmix to determine the one or more processing parameters from the metadata.
• the metadata includes one or more processing parameters relating to average loudness values and optionally one or more processing parameters relating to dynamic range compression characteristics.
• bitstream further includes additional metadata for static loudness adjustment to be applied to the decoded audio data.
• bitstream is an MPEG-D DRC bitstream and the presence of metadata is signaled based on MPEG-D DRC bitstream syntax.
• EEE10 The method according to EEE9, wherein a loudnessInfoSetExtension()-element is used to carry the metadata as a payload.
• each metadata payload includes a plurality of sets of parameters and identifiers, with each set including at least one of a DRCSet identifier, drcSetId, an EQSet identifier, eqSetId, and a downmix identifier, downmixId, in combination with one or more processing parameters relating to the identifiers in the set.
• each metadata payload includes a plurality of sets of parameters and identifiers, with each set including at least one of a DRCSet identifier, drcSetId, an EQSet identifier, eqSetId, and a downmix identifier, downmixId, in combination with one or more processing parameters relating to the identifiers in the set.
• process (c) involves selecting a set among the plurality of sets in the payload based on the at least one DRCSet, EQSet, and downmix selected by the decoder, and wherein the one or more processing parameters determined at process (c) are the one or more processing parameters relating to the identifiers in the selected set.
• process (c) involves selecting a set among the plurality of sets in the payload based on the at least one DRCSet, EQSet, and downmix selected by the decoder, and wherein the one or more processing parameters determined at process (c) are the one or more processing parameters relating to the identifiers in the selected set.
• a decoder for metadata-based dynamic processing of audio data for playback comprising one or more processors and non-transitory memory configured to perform a method including processes of: (a) receiving, by a decoder, a bitstream including audio data and metadata for dynamic loudness adjustment; (b) decoding, by the decoder, the audio data and the metadata to obtain decoded audio data and the metadata; (c) determining, by the decoder, from the metadata, one or more processing parameters for dynamic loudness adjustment based on a playback condition; (d) applying the determined one or more processing parameters to the decoded audio data to obtain processed audio data; and (e) outputting the processed audio data for playback.
• EEE14
• a method of encoding audio data and metadata for dynamic loudness adjustment, into a bitstream including processes of: (a) inputting original audio data into a loudness leveler for loudness processing to obtain, as an output from the loudness leveler, loudness processed audio data; (b) generating metadata for dynamic loudness adjustment based on the loudness processed audio data and the original audio data; and (c) encoding the original audio data and the metadata into the bitstream.
• EEE15 The method according to EEE14, wherein the method further includes generating additional metadata for static loudness adjustment to be used by a decoder.
• process (b) includes comparison of the loudness processed audio data to the original audio data, and wherein the metadata is generated based on a result of said comparison.
• process (b) further includes measuring the loudness over one or more pre-defined time periods, and wherein the metadata is generated further based on the measured loudness.
• EEE18 The method according to EEE17, wherein the measuring comprises measuring overall loudness of the audio data.
• EEE19 The method according to EEE17, wherein the measuring comprises measuring loudness of dialogue in the audio data.
• EEE20 is compared to the loudness processed audio data to the original audio data, and wherein the metadata is generated based on a result of said comparison.
• each metadata payload includes a plurality of sets of parameters and identifiers, with each set including at least one of a DRCSet identifier, drcSetId, an EQSet identifier, eqSetId, and a downmix identifier, downmixId, in combination with one or more processing parameters relating to the identifiers in the set, and wherein the one or more processing parameters are parameters for dynamic loudness adjustment by a decoder.
• An encoder for encoding in a bitstream original audio data and metadata for dynamic loudness adjustment comprising one or more processors and non-transitory memory configured to perform a method including the processes of: (a) inputting original audio data into a loudness leveler for loudness processing to obtain, as an output from the loudness leveler, loudness processed audio data; (b) generating the metadata for dynamic loudness adjustment based on the loudness processed audio data and the original audio data; and (c) encoding the original audio data and the metadata into the bitstream.
• EEE26. A computer program product comprising a computer-readable storage medium with instructions adapted to cause the device to carry out the method according to any one of EEE1 to EEE12 or EEE14 to EEE23 when executed by a device having processing capability.
• EEE27. A computer-readable storage medium storing the computer program product of EEE26.
• EEE 1 to EEE12 further comprising receiving, by the decoder, through an interface, an indication of whether or not to perform the metadata-based dynamic processing of audio data for playback, and when the decoder receives an indication not to perform the metadata-based dynamic processing of audio data for playback, bypassing at least the step of applying the determined one or more processing parameters to the decoded audio data.
• EEE29 The method according to EEE28, wherein until the decoder receives, through the interface, the indication of whether or not to perform the metadata-based dynamic processing of audio data for playback, the decoder bypasses at least the step of applying the determined one or more processing parameters to the decoded audio data.
• EEE31 The method of any one of EEE1 to EEE12, EEE28, or EEE29, wherein the metadata is indicative of processing parameters for dynamic loudness adjustment for a plurality of playback conditions, and the metadata further includes a parameter specifying a loudness measurement method used for deriving a processing parameter of the plurality of processing parameters.
• EEE31 The method of any one of EEE1 to EEE12, or EEE28 to EEE30, wherein the metadata is indicative of processing parameters for dynamic loudness adjustment for a plurality of playback conditions, and the metadata further includes a parameter specifying a loudness measurement system used for measuring a processing parameter of the plurality of processing parameters.

Landscapes

• Engineering & Computer Science (AREA)
• Physics & Mathematics (AREA)
• Signal Processing (AREA)
• Health & Medical Sciences (AREA)
• Audiology, Speech & Language Pathology (AREA)
• Human Computer Interaction (AREA)
• Computational Linguistics (AREA)
• Acoustics & Sound (AREA)
• Multimedia (AREA)
• Quality & Reliability (AREA)
• Tone Control, Compression And Expansion, Limiting Amplitude (AREA)
• Stereophonic System (AREA)
• Control Of Amplification And Gain Control (AREA)

Priority Applications (11)

Applications Claiming Priority (6)

Publications (1)

Family

ID=83283433

Family Applications (1)

Country Status (11)

Families Citing this family (1)

Citations (4)

Family Cites Families (2)

• 2022
  • 2022-08-24 US US18/685,413 patent/US20240355338A1/en active Pending
  • 2022-08-24 JP JP2024509353A patent/JP2024531963A/ja active Pending
  • 2022-08-24 IL IL310650A patent/IL310650A/en unknown
  • 2022-08-24 EP EP25221475.4A patent/EP4683218A3/en active Pending
  • 2022-08-24 EP EP22769496.5A patent/EP4392970B1/en active Active
  • 2022-08-24 AU AU2022332970A patent/AU2022332970A1/en active Pending
  • 2022-08-24 CA CA3230363A patent/CA3230363A1/en active Pending
  • 2022-08-24 ES ES22769496T patent/ES3059022T3/es active Active
  • 2022-08-24 WO PCT/US2022/041388 patent/WO2023028154A1/en not_active Ceased
  • 2022-08-24 KR KR1020247009065A patent/KR20240043809A/ko active Pending
  • 2022-08-24 MX MX2024002300A patent/MX2024002300A/es unknown
• 2024
  • 2024-02-21 CL CL2024000531A patent/CL2024000531A1/es unknown

Patent Citations (4)

Non-Patent Citations (2)

Also Published As

Similar Documents

Legal Events