Flux

The Equalizer, certainly the best known audio processing tool. It’s everywhere, in your car, in your phone, in your hi-fi system (if you happen to still have one), etc. It is certainly one of the easiest effects to identify, while being a tough one to master.

In this article we will talk about digital equalizers, how they work and how you can improve your mixing process with them.

Equalization is a tool that allows changing the timber of an audio signal. Basically, it is a sophisticated volume control that can target certain parts of the spectrum. So we can boost bass or trebles, cut mediums, etc. Basically EQs are built with a certain number of filters.

Equalizers have a long history that we are not going to cover in the article. We will focus on parametric EQ. Equalizers are classified as parametric when their target frequency and quality factor can be adjusted by the user. This is mostly the kind of EQ we are using when mixing or mastering.

These parametric EQs have three main controls :

• The frequency; which changes the target area of the audio spectrum
• The gain; defining how much we want to add or remove the frequency range we have selected
• The Q factor (or bandwidth); which sets how wide the processed band is. A high Q factor is a small bandwidth. A little Q factor is a wide bandwidth.

Sometimes you can also change the order of the filter. The higher the order, the steeper the filter’s curve is.

We also use four main filter shapes :

• The bell shape. It only boosts or cuts a certain part of the spectrum centered around the set frequency.
• The shelves. It boosts or cuts everything above (high shelves) or below (low shelves) the set frequency.
• The low pass. Let only pass frequencies below the set frequency.
• The high pass. Let only pass frequencies above the set frequency.

Without entering into too much detail about digital signal processing, there are two main types of filters; filters which have finite impulse response, and those who have an infinite impulse response. Let’s clarify this.

You may have heard the words “impulse response” when talking about reverberation. In this context, an impulse response is the reaction of a specific room to an impulse. In simple words, if you clap your hands in a cathedral, and record the reaction of the space to the clap, you will get an impulse response, which is really, just an audio sample.

If we were able to clap our hands inside a digital filter, and record its output, we would also get an impulse response. The good news is that we actually have a way to do that, and it’s called a Dirac.

A Dirac is a very specific type of signal. Theoretically, it is an impulse as short as possible. In practice, you can imagine an audio file filled with zero, except for one sample that is at full scale.

So back to our filters. To simplify the question, let’s admit that filters that have infinite impulse response (IIR) have the property to be real time, they do not add any latency. Filters that have a finite impulse response have the property of having a linear phase shift, equivalent to a certain latency. Again, let’s clarify this point.

Phase in audio is a complex subject. If you listen to the world around you, you will not perceive the phase. We start to perceive it when it changes in time or when you listen to two correlated signals.

Correlated signals are simply signals that are close enough together. For example, two microphones that are recording the same instrument at the same time.

We often talk about the phase shift, and we need a reference point to measure it and to hear it. There is some very well-known sources of phase issues :

• Using multiple microphones to record the same instrument
• Filters

All analog and digital IIR filters generate some amount of phase shifting. This means that, when you are EQing the snare top microphone with an IIR equalizer, you are generating a phase shift which changes the sound of the top mic with the bottom one and even the overheads.

The phase distortion generated by equalizer is totally solved when using FIR filters, or phase linear EQ.

So now that we know that analog and digital IIR introduce phase shifting on the signal, you may think, “OK from now on, let’s only use linear phase EQ”. And I can understand the idea, but sadly, in the world of physics, everything comes at a certain price.

It’s true that linear phase EQ does not alter the phase relationship between microphones, but they have two major issues. The first one, they add tons of latency. It’s not always a big deal when mixing, but for a live mixing desk or for headphone cues, it is not acceptable. Linear phase EQ also has the very bad habit of creating a pre-ringing effect.

What is “pre-ringing” you may ask? Well, first of all, we will admit that all audio filters have a post-ringing effect. Remember that impulse response we’ve talked about? When we “clap in a filter”, using a Dirac, we get a response that has some length. The filter kind of “oscillates” if you want. Post-ringing is not an issue, it really is how filtering works. It is not really audible because it is masked by the input signal itself.

Pre-ringing on the other hand is much more audible, because it happens before the input signal onset. At this point, you may scratch your head thinking that filtering is about time traveling. Unfortunately, no it’s not. But the good news is that we can delay things. If you remember correctly, we said before that linear phase EQs add “tons of latency”. So because there is this delay, we can hear the consequence of the filter before the input signal. And thanks to the delay compensation of our DAWs, everything stays in sync.

Filters that generate content before the input signal have a mathematical existence, but not a physical one. They are said to be non-causal (because the effects precede the causes).

Pre-ringing generates an effect comparable to a “reverse” effect, and it smooths out the transients. If the filter works in low frequencies, the pre-ringing will increase. To reduce the pre-ringing we need to use a longer impulse response, and thus, increase the latency.

I admit that these previous parts may be very confusing. But in practice, it’s not very complicated.

Linear phase EQ has too many drawbacks to have a common practical usage. Also, even the linear phase advantage is quite marginal. Let’s go back to our snare top mic we want to EQ. The phase offset generated by the bell and shelves filter is marginal and its effect on timber is hidden in the filter itself.

The graphs above shows the magnitude and phase response of the same filter curve blend with the dry signal (50%). The first one is a minimal phase filter, the second one a phase linear filter. Notice that the main difference in the magnitude is the difference in the bandwidth of the filter. The phase response of the minimal phase EQ tends to make filter curves narrow. So if you can simply compensate for that effect by having a smaller Q factor.

When it comes to low pass or high-pass filters, the discussion is not the same. The phase offset generated by these filters is much more important, and thus, we have a severe effect on timber.

This is why I often advise people to only use IIR equalizer, and to use shelves filters instead of high pass to clean their track. If a high-pass filter is really required, I would use it on a bus, where all the correlated signals get summed into, to avoid any phase distortion.

We consider that correlated signals are signals from the same instrument recorded in the same room at the same time. Bleed between microphones can also cause some correlation.

If you have read the previous part, you should have an idea of the answer. First, and this may be controversial, but there is a strange habit to high pass everything. It’s not that rare to see the idea that we should “clean” the low end of each and every track. Which is strange because there is rarely anything at all there. So why even bother ? Moreover, when we start to use many high-pass filters on many correlated signals, it can create some really funky phase interactions.

As previously said, a low shelf filter seems like a better alternative for this kind of application. I would also strongly recommend to only treat the low end (or anything really) if you hear something there.

I personally prefer to use a high-pass filter to improve the phase interaction between several microphones. Depending on the order of the high pass, the phase shift will increase or decrease.

• At first order (6 dB/oct), we register a phase shift of 90° at the cutoff frequency.
• At order 2 (12 dB/oct), we find a 180° phase shift at the cutoff frequency.
• At order 3 (18 dB/oct), we find a 270° phase shift.
• At order four (24 dB/oct), we come back at 360°

Be careful, the higher the order, the more chaotic the phase rotation becomes.

If you add the order of the high pass with the polarity switch of the mixing channel, you start to have a nice phase adjustment tool. It’s even better if you happen to use the Evo Channel, which features a high-pass filter with a selectable order, and a phase adjustment dial to go from anywhere from -180° to 180° phase shift.

We often see this advice on the internet that we should prefer cutting things we don’t like instead of boosting frequency. Another approach is possible, though.

Critical listening is the best tool to sharpen when mixing, combining that with a bit of common sense we can simply say that :

• If we find that there is a disturbing frequency in the signal, we can remove it with an EQ cut.
• If we lack something in the signal, we can emphasize this area with an EQ boost.

As a general guideline, we tend to favor greater Q-factor for cuts and smaller ones for a boost.

In the extremes of the spectrum, I tend to avoid shelves for boosting, as it tends to push too many frequencies upfront. Bells offer more precision. On the other hand, a shelve filter is very efficient to smooth out too much high-end and to remove harshness.

When we search for advice on the internet for learning how to EQ, we often find this method : take a narrow band bell EQ, give it a good amount of gain and sweep around the spectrum to find something that you don’t like. Once it’s founded, simply cut it.

To be honest, I think it is a terrible method. I don’t know if you experience the same thing as me, but when I’m listening to a bell filter, with a narrow band, boosted, nothing sounds right to me.

I would rather propose another method. Listen carefully to the signal you want to process. Listen to it in the mix (don’t use the solo button). Pay attention to interaction with other instruments if some sources are masking each other. Pay attention to things you’d like to improve in the timber. Eventually, you can take some notes. Then, for each problem you want to solve, you will make a bet. For example, if I found a resonating frequency on an electric guitar that is disturbing, I will say to myself, “I think it is at 300 Hz”. Then, I set my equalizer to 300 Hz, to give it a boost to emphasize this area. If it’s there : good job! You can now cut it. If it’s not there, go back to a flat response and repeat the whole process. Is the problem higher or lower from what we’ve just heard?

When we bet on a wrong frequency, it’s worth trying an octave lower or higher. We often target the wrong harmonic. Also, if you can directly cut instead of boosting, it’s a good improvement exercise too.

The advantage of this method is that you actually train your ear to detect certain frequencies. With repetition you will get the right frequency faster and faster.

Also, It is now very common to have a spectrum analysis tool directly embedded in the user interface. The Evo Channel and Evo EQ feature the same praised spectrum analyzer found in the FLUX:: Analyzer. On a single channel, a frequency analyzer can give some precious information. We can instantly see the harmonic content of a signal and target the right spot for our treatment. While it should not replace the ears, it can be a great tool for beginners.

Equalizer is one of the most used tools in audio production. The form we mostly use as audio professionals is the parametric EQ. Equalizer is built upon filters, whose numbers and shape depends on the usage. In the digital world, there are two main digital filter types : IIR (Infinite Impulse Response) and FIR (Finite Impulse Response). We tend to associate the first type with minimal phase EQ (similar to their analog counterpart) and the second type with linear phase EQ.

While linear phase EQ sounds like a major improvement, it actually has too many drawbacks to be a solid alternative for minimal phase EQ. Actually, filter results on correlated sources are pretty similar between minimal phase and phase linear EQ, as long as you use bells or shelf filters. For high pass and low pass filters, they should be used with caution due to their important phase shift.

Critical listening is the best approach to sound equalization. One should always interrogate himself about the nature of the problem he is listening to. The “sweep and boost” technique often found on the internet seems like a bad strategy as it does not help to identify the problem and it does not improve the ear of the mixer.

The post Tech Tips – How to use an EQ appeared first on FLUX:: Immersive.

If you’ve ever been involved with anything in some way related to sound, you certainly have heard about compression. It is one of the most used effects, along with the equalizer. There is also a ton of content available about compressors, about different types, different clones, about comparisons between hardware and digital versions, and a lot of other things, and it may be a bit tricky to understand what it is that is actually going on with compression.

In this article we will try to summarize the common practice of knowledge on compression and compressors.

Before tackling down the usage for compression, we have to explain the dynamic range of a signal. It is the difference between the loudest peak and the noise floor. We usually like to have a good amount of dynamic to leave the musical intention intact and the noise inaudible.

It’s a fact that some signals have too much dynamic variation, very common when dealing with a voice. There’s large variations in levels when we talk or sing, and it is even worse at a few inches from a microphone. Historically, the only solution to smooth out the unwanted dynamic, is either to put the microphone further away, or to ride the fader up and down in sync with the performance.

The origin of compression came with the idea to automate the process of fader riding, basically, a compressor is a device that lowers the volume when it gets too loud. By doing so, it reduces the dynamic range of the signal, hopefully by removing only the unwanted variations. Devices of this kind started to appear for the first time sometime back in the 1940s.

It is important to note that a compressor does actually make the signal quieter, until you decide to compensate for the gain reduction. We can also safely conclude that a compressor reduces the loud part of the signal (and not the opposite).

Compressors can be used at many points of the signal path, on single channels, on instrument buses, or even directly on the master bus.

At this point, having an effective routing solution can drastically simplify the question where. One simple solution is to sum everything that makes sense together. For example, on drums, if we have two mics on the kick, two mics on the snare and a pair of overhead, we could sum the two kick microphones in one bus, do the same for the two snare channels, and finally sum the kick bus, the snare bus, and the overhead, together inside a final drum bus.

Now, if I hear a dynamic issue on the snare, I can apply a compressor on the snare bus. If I hear another one on the microphone inside the kick, I can apply a compressor on the right channel, and so on.

It is sometimes seen that a compressor is any kind of device that reduces the dynamic range of a signal. There are in fact two possibilities here; you can either lower its loudest part, or do the opposite and amplify the lowest part of a signal. This second method is much less common but can lead to very effective results. At FLUX:: we call compression everything that does downward compression, and we call it de-expansion with everything that does upward compression. You can achieve upward compression with Solera, Alchemist or Pure DExpander.

The recording technique has a strong impact on the dynamic. The closer the microphone is to a sound source, the bigger the instantaneous dynamic of a source is. So, the heavy use of compressors in modern music is very much due to the generalization of close-miking technique. In more acoustic styles of music, like orchestral recordings, compressors are much less prominent because the recording technique deployed tends to favor microphones further away from the instruments.

The usual suspects found on a compressor, are these four parameters :

• The threshold (dB); when the signal is louder than the level of the threshold, the compressor starts to reduce the gain.
  
• The ratio; which determines the strength of the compressor. A 4:1 ratio means that when the signal exceeds the threshold by 4 dB, the output signal only sees an increase of 1 dB.
  
• The attack time, which determines how long the compressor takes to reach the set ratio once the signal exceeds the threshold.
  
• The release time, which determines how long the compressor takes to return to 0 dB of gain reduction once the signal goes under the threshold.

Faster time constant produces more harmonic distortion, while slower ones are more transparent but also less efficient.

There are more parameters that can be discussed about compressors, these will be tackled in another article.

There is a common perception that a well-set compressor should be inaudible. While it certainly has some truth, it is also very misleading for newcomers.

How could we be satisfied with a mixing procedure if we can’t hear it? Of course we need to hear the effect of a compressor, otherwise, we should just remove it from the audio processing chain!

The rule of thumb is that, as long as we want a transparent dynamic management of an instrument, we should only hear the proper dynamic processing without the artifact of compression.

Despite the myriad of compressor models, we can easily distinguish four main usages for a compressor :

• Reduce the crest/peak of a signal (peak compression)
  
• Reduce the mean level of variation (RMS compression)
  
• Creating a “glue” effect on a bus (Bus compression)
  
• Using compression as an effect

For peak compression, we want to use compressors that have a fast behavior. In other words, we want them to be quite sensitive to transients, to be able to catch them.

⚠️ Peaks are amplified with closer microphone placement

For RMS compression, we are looking for the opposite behavior. We prefer compressors with a “slow” behavior. This type of compressors are not very sensitive to transients, so they are best suited to work on the global variation of the signal.

For bus compression, we usually prefer faster compressors too, but which are also capable of being gentle with the signal. As for special effects, there are really not many guidelines as long as the sonic result is enjoyable. Usually, the dirtier the compressor gets, the funnier it is.

Before talking about feedback or feedforward compressors, we should look at a simple diagram of a compressor.

There are two main blocks in a compressor; a detection block, also called sidechain, and a processing block, also called gain reduction circuit.

If the sidechain is fed by the input signal, then the compressor is said to be in feedforward mode. If the sidechain is fed by the output signal, then the compressor is said to be in feedback mode.

⚠️ In feedback mode, the feedback loop usually starts after the make-up gain stage. So the output volume has a strong impact on the compression!

Analogue compressors are generally designed in feedback, because it is an easier way to build them. The feedback loop also introduces some kind of retroaction which tends to limit overcompression.

Feedforward is technically considered as better, because the quantity of gain reduction does not affect the gain reduction itself. They are more predictable and sometimes easier to handle, they can also easily over compress the signal.

We have used the words fast and slow to describe the behavior of a compressor above. These words do not really relate to the attack or release time, but much more to the RMS window (or RMS size).

The RMS size is how smoothed the signal is in the detection circuit of the compressor. A short RMS size (5-10 ms) will produce a compressor very sensitive to crest and transient. A long RMS size (40 ms and above) will produce a compressor less sensible to peak and more adequate to follow the global level variation of the signal.

This RMS size has a very strong impact on the sonic characteristic of a compressor.

We often encounter the term program dependent to qualify a compressor. This means that the nature of the input signal will alter some parameters of the compressor.

Pretty much all analogue compressors are program dependent. Their release time can vary a lot depending on the input signal, or, their ratio can be greater as the input signal voltage grows, etc. It’s really more a design constraint than a feature, but it happens to be quite pleasant, sonically speaking.

On the other hand, it is very easy to design a very predictable compressor in the digital domain. But sometimes, these designs can sound a bit dull compared to their analogue counterparts. This is why most modern digital compressors also implement many program dependent features.

Most FLUX:: compressors allow the user to set the knee size (the knee makes the ratio dependent on the input level) or to have an automatic release based on the input signal crest factor. Even the ratio can be made dependent on the crest factor! And if the FLUX:: compressor you own doesn’t let you set all of this manually, you will find a mode selector, like on Evo Channel or Evo Comp, that changes all these settings under the hood for you.

There are different ways to build an analogue compressor. Each of these buzzwords refer to particular technologies of gain reduction circuit.

The first technology known to build compressors is the so-called Vari-Mu. They involved a tube as a voltage-controlled gain reduction device. These kinds of compressors tend to have time constant on the slower side and a soft knee. So the hotter the input signal is, the harder the compression is.

The natural evolution of tube compressors was to replace the tube with a field-effect-transistor once they have become available. FET compressors are generally closer to a hard knee while still having a bit of a progression between no compression and full ratio. They also allow for a much quicker time constant. Their main drawback (or joy, depending on your goal) is their high harmonic distortion level. They tend to be more appropriate for peak compression.

The FET compressors were rapidly replaced by VCA. While all previous technologies mentioned are built around voltage controlled amplifiers, VCA are analogue processors specifically designed for signal amplification. They usually offer a versatile range of control at a low harmonic distortion cost. They also have the nice advantage of being very small and have allowed mixing desks of the 80s to have one compressor per channel.

Optical compressors appeared in the 50s. It’s based on an electronic optic cell. They have the reputation to be quite slow and clean compressors. The release time is very program dependent. This unit also has a rather soft knee and a frequency-dependent ratio. They are more suited for RMS compression.

One should be careful at characterizing the usage of one component to determine the sonic nature of the whole device. We should never forget that in such complex systems, the topology of the circuit is very important too.

We can often find settings that allow blending the unaffected signal (dry) and the compressed signal (wet) together. It is called parallel compression. The idea is to set a very aggressive peak compression and to blend it back with the original signal to recover some of the natural dynamic.

This is a very colorful and effective processing, which tends to bring low-level information in front of the mix. If you struggle to find the right settings, try a compressor with a short RMS size, with a very short attack (< 3ms) and release (< 60ms) time. Then, lower the threshold so that a good amount of signal will be processed. Increase the ratio up to taste. It will sound like a lot, that’s the goal! We will recover some air by bringing the dry signal in.

We have talked extensively about analogue compressors, but they aren’t that often seen nowadays. Like many other types of processing, many analogue processing has moved to digital counterparts, first for cost-effectiveness reasons, and also because of simpler workflows.

In digital sound processing, there are far fewer constraints on what we can do compared to the analogue world. It is then easy to build compressors with many settings (user accessible or not), like FLUX:: plug-ins.

This makes digital compressors way more versatile than their analogue counterparts. It sometimes makes them more difficult to learn, but realistically, you could replace a whole collection of compressors with just Evo Comp or Evo Channel, for example. In fact, it’s not very difficult to imitate famous analogue compressors.

There are also some things that can’t (or can very rarely) be done with analogue compressors. For example, a look ahead option allows delaying the signal in the processor section and can create a zero attack time while keeping a smooth envelope (and a low distortion). Such an option is common on digital compressors.

⚠️ Lookahead also add latency in the whole audio system. Be careful, depending on what you are doing!

Compressors are audio processors that are designed to reduce the dynamic of a signal. Most of the time they lower the signal when it goes above a certain threshold (downward compression). Sometimes, they can also amplify the signal when it goes below a certain threshold (upward compression).

There are basically two main usages for compressors, peak and RMS management. For peak compression, we prefer compressors with fast attack, fast release and short RMS windows. For RMS compression we prefer compressors with slower attack and release and longer RMS windows. The first categories often relate to FET or VCA compressors, while the second one relates more with Opto and Tube compressors.

Digital compressors have the advantage of being very flexible and can be adapted to pretty much any mixing situation. They can be both very clean and predictable, or very dirty and dependent on the input signal. One full featured one can replace a whole collection of compression devices. They also have the strong advantage of looking ahead, which allows for clean zero attack time.

The post Tech Tips – How to use a Compressor appeared first on FLUX:: Immersive.

Meung-Sur-Loire, France – Janvier 2023

FLUX:: Immersive, pionnier dans la conception de plug-in audio, l’analyse et les outils de production audio immersifs, est aujourd’hui fier d’annoncer la sortie du pack de plugins EVO:: SERIES PACK. Le EVO:: SERIES PACK comprend les formats les plus utilisés par les développeurs de logiciels tels que Avid Technology AAX (Native, DSP et VENUE), AU (Apple ®), VS3 (Merging Technologies) et VST2&3 (Steinberg).

Fort du succès de l’EVO:: Channel, le channet strip ultime, le nouveau EVO:: SERIES PACK complète l’EVO:: Channel avec 4 nouveaux plugins EVO:: pour couvrir l’ensemble des besoins du mixage en live et en studio.

• EVO:: Comp – Compression
• EVO:: EQ – Equalizer et Spectrum Analyzer
• EVO:: In – Phase
• EVO:: Touch – DeEssing, Sustain, Transient Shaping et Expanding

Chacun de ces plugins comprend le système unique EVO Drive, introduit dans l’EVO:: Channel, conçu pour ajouter une saturation douce et une chaleur à la source.

Au cœur de la série EVO::, on retrouve la simplicité et l’efficacité, ainsi qu’une proposition sonore unique, signée par le célèbre ingénieur du son Yves Jaget (The Jeff Healey Band, Star Academy France, Zazie, Jonny Lang, etc).

Tous les plugins de la série EVO::, y compris EVO:: Channel, offrent désormais une interface utilisateur redimensionnable. De plus, le multicanal étant au cœur de l’activité de FLUX:: Immersive, tous les plugins de la série EVO:: prennent désormais en charge 16 canaux, ce qui permet la prise en charge des formats de production multicanaux tels que Sony 360 ™, Dolby Atmos ™, Auro 3D Audio et bien d’autres.

Tous les produits incluent un an d’assistance et de mise à niveau.

MSRP : $149 / 145€

Offre de lancement : $99 / 95€

PAGES PRODUIT
https://www.flux.audio/project/evo-series/
https://www.flux.audio/project/evo-series-pack/

Toutes les dernières versions de FLUX::, incluant le FLUX:: Center, sont compatibles de macOS 10.14 (Mojave) à macOS 13.1 (Ventura) et Windows 10 & 11 64-bit. L’ancienne version 21.12, et les versions antérieures, restent disponibles dans le FLUX:: Center disponible ici : https://www.flux.audio/download/

A propos de FLUX:: Immersive

FLUX:: Immersive s’est forgé une réputation de leader dans la création de logiciels de traitement audio avec l’idée maîtresse de concevoir des outils techniquement innovants et inspirants pour les ingénieurs du son, et sans compromis sur la qualité audio. La société a toujours été à l’avant-garde du développement de solutions logicielles pour l’industrie audio professionnelle, prenant notamment en charge le traitement multicanal depuis plus d’une décennie. Ses produits sont fréquemment utilisés pour l’enregistrement surround, la post-production de films, le son immersif en direct et en installation, et dans diverses autres applications.

The post FLUX:: Immersive Présente le nouveau EVO:: Series Plugin Pack appeared first on FLUX:: Immersive.

Meung-Sur-Loire, France – Janvier 2023

FLUX:: Immersive, pionnier dans la conception de plug-in audio, l’analyse et les outils de production audio immersifs, est aujourd’hui fier d’annoncer la sortie de la mise à jour majeure 23.1 pour l’ensemble de ses plugins. Cette mise à jour comprend les formats les plus utilisés par les développeurs de logiciels tels que Avid Technology AAX (Native, DSP et VENUE), AU (Apple ®), VS3 (Merging Technologies) et VST2&3 (Steinberg).

Cette mise à jour concerne TOUS les plugins et bundles antérieurs proposés par FLUX::. Tous les plugins et bundles de plugins achetés en 2022 recevront cette mise à jour gratuitement, dans le cadre du contrat SLA de support et de mise à jour pendant un an proposé par FLUX::.

La mise à jour FLUX:: 23.1 inclut désormais la compatibilité native avec la nouvelle gamme de machines Apple Silicon (processeurs Apple ARM)l. Et, au-delà du support tant attendu du format VST3, les plugins intègrent les dernières avancées et incluent une interface utilisateur redimensionnable.

Le multicanal étant au cœur de l’activité de FLUX:: Immersive, tous les plugins de traitement supportent désormais 16 canaux, à l’exception de Ircam Trax, Ircam Verb Session, et des outils stéréo, qui restent à 2 canaux. En outre, le limiteur True Peak Elixir, récemment mis à jour, prend désormais en charge 32 canaux, ce qui améliore ses capacités de prise en charge des formats de production multicanaux tels que Sony 360 ™, Dolby Atmos ™, Auro 3D Audio, ainsi que NHK 22.2 et au-delà.

Nouveaux packs de plugins

La mise à jour des plugins 23.1 est une mise à jour majeure qui introduit deux nouveaux packs de plugins.

EVO:: Series Pack

EVO:: Series Pack – Le EVO:: Series Pack est basé sur le succès de tranche de console EVO:: Channel, qui est maintenant complétée par EVO:: Comp, EVO:: EQ, EVO:: IN et EVO:: Touch. Ces 4 nouveaux modules sont disponibles dans tous les formats et sont compatibles avec la technologie Avid AAX DSP / VENUE. Chacun de ces modules comprend le système unique EVO Drive conçu pour ajouter une saturation douce et de la chaleur à la source. Le multicanal étant au cœur l’activité de FLUX:: Immersive, tous les plugins EVO:: prennent en charge jusqu’à 16 canaux.

MSRP : $149 / 145€

Offre de lancement : $99 / 95€

PAGES PRODUIT
https://www.flux.audio/project/evo-series/
https://www.flux.audio/project/evo-series-pack/

Ultimate Plugin Pack

FLUX:: Ultimate Plugin Pack – Le FLUX:: Ultimate Plugin Pack remplace le Full Pack 2.2 et inclut maintenant tous les plugins FLUX:: Series, EVO:: Series (5 plug-ins), Ircam Verb, Ircam Verb Session, et Ircam HEar. Un pack de plugins d’une valeur totale de 1 686 $, désormais proposé à un prix plus compétitif que jamais.

MSRP : $699 / 679€

Offre de lancement : $499 / 485€

PAGE PRODUIT
https://www.flux.audio/project/ultimate-plugin-pack/

Toutes les dernières versions de FLUX::, incluant le FLUX:: Center, sont compatibles de macOS 10.14 (Mojave) à macOS 13.1 (Ventura) et Windows 10 & 11 64-bit. L’ancienne version 21.12, et les versions antérieures, restent disponibles dans le FLUX:: Center disponible ici : https://www.flux.audio/download/

Toutes les informations sur les versions peuvent être trouvées ici :
https://www.flux.audio/flux-23-1-plugin-update/

A propos de FLUX:: Immersive

FLUX:: Immersive s’est forgé une réputation de leader dans la création de logiciels de traitement audio avec l’idée maîtresse de concevoir des outils techniquement innovants et inspirants pour les ingénieurs du son, et sans compromis sur la qualité audio. La société a toujours été à l’avant-garde du développement de solutions logicielles pour l’industrie audio professionnelle, prenant notamment en charge le traitement multicanal depuis plus d’une décennie. Ses produits sont fréquemment utilisés pour l’enregistrement surround, la post-production de films, le son immersif en direct et en installation, et dans diverses autres applications.

The post FLUX:: Immersive annonce la mise à jour 23.1 – Avec le support D’Apple Silicon ARM Native & VST3 appeared first on FLUX:: Immersive.

Meung-Sur-Loire, France – January 2023

FLUX:: Immersive, pioneers in audio plug-in design, analysis, and immersive audio production tools, is today proud to announce the release of the EVO:: SERIES PACK. The EVO:: SERIES PACK includes the most supported formats from a software developer such as Avid Technology AAX (Native, DSP and VENUE), AU (Apple ®), VS3 (Merging Technologies) and VST2&3 (Steinberg)

Building on the success of the EVO::Channel, the Ultimate Channel Strip, the new EVO:: Series is complementing the EVO Channel with 4 new EVO:: plugin modules for the fundamentals of live and studio mixing.

• EVO:: Comp – Compression
• EVO:: EQ – Equalizer and Spectrum Analyzer
• EVO:: In – Phase
• EVO:: Touch – DeEssing, Sustain and Transient shaping and Expanding

Each of these modules include the unique EVO Drive system, introduced in the EVO Channel, designed to add soft saturation and warmth to the source.

At the core of the vision of EVO, is simplicity and efficiency with a unique sound proposition, signed by prolific mixing engineer, Yves Jaget (The Jeff Healey Band, Star Academy France, Zazie, Jonny Lang, etc.).

All the EVO Series plugins, including EVO Channel, now offer a resizable user interface allowing users to select their desired aspect ratio to resize the UI. Multichannel being at the core of FLUX:: Immersive, all the EVO Series plugins now support 16-channels enhancing the support for multichannel production formats such as; Sony 360 ™, Dolby Atmos ™, Auro 3D Audio and the likes.

All products include 1 year of support & upgrade SLA

MSRP: $149 / 145€

Introduction Offer: $99 / 95€

PRODUCT PAGES
https://www.flux.audio/project/evo-series/
https://www.flux.audio/project/evo-series-pack/

All FLUX:: latest releases including the FLUX:: Center are supported from mac OS 10.14 (Mojave) to OS 13.1 (Ventura) or Windows 10 & 11 64-bit. The legacy 21.12 version, and prior versions, remain available in the FLUX:: Center available here: https://www.flux.audio/download/

About FLUX:: Immersive

FLUX:: Immersive has established a reputation as a leader in the creation of audio processing software, with the core idea to design inspiring technically innovative tools for sound engineers, with no compromise on the audio quality. The company has always been at the forefront of the development of software solutions for the professional audio industry, supporting multichannel processing, which for over a decade has been frequently used for multichannel surround recording, movie post-production, immersive live & installation sound, and in various other applications.

The post FLUX:: Immersive Introduces new EVO:: Series Plugin Pack appeared first on FLUX:: Immersive.

Meung-Sur-Loire, France – January 2023

FLUX:: Immersive, pioneers in audio plug-in design, analysis, and immersive audio production tools, is today proud to announce the release of their 23.1 major plugin update. This plugin update includes the most supported formats from a software developer such as Avid Technology AAX (Native, DSP and VENUE), AU (Apple ®), VS3 (Merging Technologies) and VST2&3 (Steinberg)

This update provides update paths to users of ALL prior plugins and bundles ever made by FLUX:: . All plugins and plugin bundles purchased in 2022 will receive an upgrade at no charge, as part of the FLUX:: 1-year support and upgrade SLA contract.

The FLUX:: 23.1 plugin update includes ARM support with a universal binary, running on both Apple silicon and Intel-based computers. Beyond the long-awaited support for VST3, the plugins are now updated to the latest compatibility and include a scalable user interface allowing the user to define the aspect ratio in order to resize the plugin UI.

Multichannel being at the core of FLUX:: Immersive, 16-channel support is now offered for all processing plugins, with the exception of; Ircam Trax, Ircam Verb Session, and Stereo tools, which all remain in 2 channels. In addition, the recently updated True Peak limiter Elixir now supports 32 channels, enhancing the capabilities for multichannel production formats such as; Sony 360 ™, Dolby Atmos ™, Auro 3D Audio all the way to s NHK 22.2, and beyond.

New Plugin Bundles
The 23.1 plugin update is a major update which introduces two new plugin bundles.

EVO:: Series Pack

EVO Series Pack – The EVO Series Pack is based on the success of the EVO:: Channel, which is now complemented by EVO:: Comp, EVO:: EQ, EVO:: IN, and EVO:: Touch, 4 new modules available in all formats and compliant for Avid Technology AAX DSP / VENUE. All modules include the Unique EVO Drive system designed to add soft saturation and warmth to the source. Multichannel being at the core of FLUX:: Immersive, all EVO plugins support up to 16-channels.

MSRP: $149 / 145€

Introduction Offer: $99 / 95€

PRODUCT PAGES
https://www.flux.audio/project/evo-series/
https://www.flux.audio/project/evo-series-pack/

Ultimate Plugin Pack

FLUX:: Ultimate Plugin Pack – The FLUX:: Ultimate plugin pack supersedes the Full Pack 2.2 and now includes all FLUX:: Series plugins, EVO:: Series (5 plug-ins), Ircam Verb, Ircam Verb Session, and Ircam HEar. A plugin bundle of a total value of $1,686, now offered at a more competitive price than ever.

MSRP: $699 / 679€

Introduction Offer: $499 / 485€

PRODUCT PAGE
https://www.flux.audio/project/ultimate-plugin-pack/

All FLUX:: latest releases, including the FLUX:: Center, are supported on mac OS 10.14 (Mojave)to OS 13.1 (Ventura) or Windows 10 & 11 64 bit. The legacy 21.12 version, and prior versions, remain available in the FLUX:: Center.New FLUX:: Center is available here https://www.flux.audio/download/

All release information can be found here
https://www.flux.audio/flux-23-1-plugin-update/

About FLUX:: Immersive

FLUX:: Immersive has established a reputation as a leader in the creation of audio processing software, with the core idea to design inspiring technically innovative tools for sound engineers, with no compromise on the audio quality. The company has always been at the forefront of the development of software solutions for the professional audio industry, supporting multichannel processing, which for over a decade has been frequently used for multichannel surround recording, movie post-production, immersive live & installation sound, and in various other applications.

The post FLUX:: Immersive Announces 23.1 Plugin Update – Now with Apple Silicon (ARM) Native and VST3 appeared first on FLUX:: Immersive.

In the previous two articles in this series, True Peak limiting and Loudness processing, and Limiter Theory – Knowing your tools, we’ve been talking about the general usage of limiters, and explained limiting processing in more detail. Now we will continue with some examples of different workflows that are used with a limiter.

If you are in a hurry, skip down to the TL;DR section of this article to get a summary, as well as a video explanation of the subject.

The very final step

You for sure got this by now; a limiter should be at the very last stage that the signal you are processing is passing through, the ideal place being at the very end of the master bus.

If you are not looking for a huge loudness in your mix, one single limiter will be more than enough. Otherwise, doing all the gain reduction necessary to get a very loud mix with only one limiter is often problematic. This is where many mastering engineers are using multiple limiters and process the peak reduction little by little.

There’s a similar concept to this in the Elixir called Stage, which is exactly like having several Elixir instances in a chain. For example, with Stage set to 4, it is like having four Elixirs chained in a row, and the gain reduction is then applied uniformly between all the stages based on the threshold value.

The best practice while processing a mix with a limiter, is to do it at a constant level. If your limiter automatically compensates for the volume loss of the crest being cut off, it will be more difficult to understand if the limiter is working too hard. So, while you are adjusting the limiter, always compensate with the output level to get the same loudness as the input signal. Once you are satisfied with the result, you can then remove the attenuation.

For example, using the Elixir limiter, if you have set an input gain of 5 dB, lower the threshold with 4 dB and activate the Make Up option, you then would have to lower the output gain to 9 dB to match the input level.

Loudness is better

If you want even more loudness from your mix, you may want to try the following tricks:

• Having the right balance between tracks helps tremendously. It’s a good thing to examine this first, it can eventually be solved by a stem mastering approach.
• You may need to reduce or remove the channel link of your limiter to avoid over limiting.
• Manage the low end of your mix. The more bass heavy the mix is, the harder it will be to get high loudness. Here, an EQ and multiband compressor will be your friends.
• Some parallel compression with a look ahead to avoid peak amplification can help you to increase the RMS level of the mix. We have two presets built on this idea in the Syrah compressor, called Parallel Enhancer Loud, and Parallel Enhancer Soft.
  

• You could also try to combine different types of limiters, for example, insert a multi-band limiter followed by a single band one. We also have a preset designed for this use case in the Alchemist plug-in called 5-bands: Limiter.
  

But be careful to not end up becoming a loudness war casualty, remember that loudness is not a necessity. Loudness may seem fun at first glance, but it will quickly damage everything that has been meticulously created at the recording and mixing stage.

Immersive audio and limiting

If you are doing immersive audio work, you may be wondering how to best apply limiting processing on content with more than two channels.

When working with classic surround formats like 5.1, 7.1, or even Dolby Atmos beds (5.1.2, 7.1.4, etc.), you will need a limiter that can handle as many channels as there are present in the surround bus. The Elixir plug-in is designed for this, and offers the possibility to process up to 16 channels simultaneously.

In this case, the channel link feature becomes useful. If you have spent time creating an immersive audio sound scene, you don’t want to arm it at the mastering stage. But engaging the channel link sometimes creates over compression. The Elixir features a dynamic mode that will process transients just like there is no channel link but the rest of the processing will be applied identically to all of them.

In case you are dealing with ambisonic streams, then you should always have all the channels linked together without any optimization of any kind (no dynamic mode for Elixir!). It is due to the fact that ambisonic channels are not mapped to any particular speaker, and making gain reduction on only some of them can really harm the sound stage after the decoding. Thanks to Elixir’s 16 channels, it can handle ambisonic streams up to the third order. But be careful after the decoding stage, it may generate audio peaks that cross the threshold.

When mixing in Dolby Atmos, you are dealing with an object-based mixing. Here the conversation becomes complex, because there is, to this day, no easy way to master an object-oriented mix. If you really want to have a final limiter, you will have to only mix with beds. The main issue is that it does limit you to 7.1.2 format. Otherwise, you can try to limit on the object directly, but it will be time consuming and heavy on the processor.

TL;DR

A limiter is used last in the effect chain. If another plug-in is inserted after, there’s a big risk that the level guarantee of the limiter is compromised.

Originally, only a limiter was used on the master, but sound engineers notice that chaining multiple limiters could lead to a more transparent result. With Elixir it is the equivalent of using the stage control.

Modern mastering techniques tend to favor stem processing. Multiple files are sent to mastering, each one of them corresponding to a main bus in the mixing session. Limiting can be applied directly on this bus.

For immersive content, a multi-channel limiter such as Elixir can be used on different kinds of bus size, from quadraphonic to 3rd order ambisonic. For channel-based bus (quadraphonic, 5.1, 7.1.2, etc.), channel-link control helps to find compromise between preservation of sound localization and over-processing. When dealing with ambisonic streams, the channel link should always be on (100% and no auto mode for Elixir).

When dealing with Dolby Atmos, limiting can be used on buses and on objects, but there is no easy way, for now, to link parameters to simplify the workflow.

The post How to Use a Limiter, Part 3 – Advanced processing and Dolby Atmos mastering appeared first on FLUX:: Immersive.

In the previous article in this series, we initiated a conversation about limiting in order to get a rough idea of what limiting is, and what it’s doing. Now we will take a deep dive into the limiter’s gut and get our hands dirty!

If you are in a hurry, skip down to the TL;DR section of this article to get a summary, as well as a video explanation of the subject.

Definition

A limiter is a very particular kind of device, bridging the gap between more conventional compression processing and saturation. There is a common definition stating that a limiter is a compressor with a ratio above 10:1. This means that if your input signal exceeds the threshold by 10 dB, there will only be 1 dB above the threshold at the output.

But this definition is not satisfactory for the kind of limiter we use at the end of the mastering chain, more commonly known as a True Peak Limiter.

True peak limiting means that at the very moment where a sample has a value superior to the threshold of a limiter, it will be caught by it. You can think of it as a compressor with an attack and an RMS window equal to zero.

Now, True Peak Limiters also have an infinite ratio, which is also a very important point; an audio sample cannot exceed the threshold. Think of it as a kind of warranty implied by a mastering limiter. If you have set the threshold to -1 dBTP, the audio signal will never go beyond this value. This is why a limiter could also be seen as a saturation processor, because it hard clips the input signal. Theoretically, you could replace a limiter by a clipper to get the same kind of warranty, but the sonic results will most probably be problematic and quite undesirable.

Family picture

Let’s look at what happens to very simple signals when we send them through a limiter. We will first look at the spectrum analysis of a sine wave at a frequency of 440 Hz, with the FLUX:: Elixir limiter on and off. The oscillator generates the tone at a -6 dBTP level, and Elixir has its threshold set at -9 dBTP. So, we should see a perfect -3 dB of gain reduction when Elixir is on.

Maybe you are wondering if there is any difference between the two previous pictures. And yes, there is a small 3 dB difference between the two peaks, which means that we did not add any saturation in the process.

Now, to make it a bit closer to sound we will have to handle with limiters, let’s modulate the amplitude of the sine wave. For this we have simply added a tremolo with a frequency of 4 Hz. It goes from unity gain to -inf dB.

Now, we can see that there are some additional frequencies here. These are added by the fact that the limiter is engaged and disengaged by the amplitude modulation, and its envelope adds some harmonic distortion. What should be kept in mind is that the harder the peak is, the more saturation will be added.

If you use them right, you could get a light version (none True Peak) of Elixir using FLUX:: Alchemist, Solera or Pure Compressor plugins. engage the infinite ratio option, set the delay to the same value as the attack, then play with the release and hold time to get the desired result.

Smoothing the clipping

To prevent and reduce any distortion added by a limiter, we use the envelope very much like a compressor.

Attack settings

Didn’t we say that a limiter has an attack of 0 ms? Well, not exactly. What we want to be sure of is that no sample can exceed the threshold. Using an attack of 0 ms is a solution but it also generates additional saturation that we want to avoid. So what could we do about it ? This is where lookahead comes in handy.

A lookahead, as the name implies, allows the algorithm to look ahead, before the signal. So, if we know in advance when the signal will pass the threshold, we could then manage to open the envelope before that happens.

Remember, because it is still, unfortunately, impossible to go back in time, lookahead will add latency to the signal.

Another way to understand it is to look at a block diagram of a limiter.

There is a detection circuit that will tell when the signal passes the threshold. In a traditional compressor this moment will trigger the envelope applied by the processing block. So, in this regard, the processing in a limiter is always kind of late. Now, the lookahead is a simple delay at the input of the processing stage.

This attack time allows for a softer clipping of the signal. It is not often seen as a parameter on the user parameter, but almost all modern True Peak limiters have this hidden under the hood. In Elixir, the attack time also depends on the input signal, to achieve a more musical result.

Release settings

The release time is more straightforward to understand than the attack time, as it is the same thing as in a compressor. The release time is the time for a limiter to completely stop processing the signal once the signal goes back below the threshold. It has a strong impact on the quality of a limiter.

• Set it fast to get a snappy result, with a more saturated character
• Set it slow to get a softer result, with a more compressed or pumping character

As for the attack time, the release in Elixir is dependent on the input signal.

Is True-Peak really True-Peak ?

A True-Peak limiter will always guarantee that you never exceed its threshold. At least, as long as you never do any kind of sample rate conversion after the processing!

Remember, in a digital audio workstation (DAW), we work with a digital representation of sound. To do so, we have sampled the audio signal at a certain sample rate (44.1 kHz, 48 kHz, 96 kHz, 192 kHz, etc.). So it is possible that the original signal had, between two samples, a value of higher value. After a resampling, this value may appear and generate a value above the threshold of the limiter. This phenomenon is known as intersample peak.

To prevent this effect, many limiters use oversampling. It is often hidden under the name intersample peak detection. Using oversampling will increase the resolution of the limiter and prevent intersample peaks from passing through. In Elixir, the oversampling only happens in the detection algorithm, while always being in sync with the processing algorithm.

TL;DR

A limiter is a dynamics processor. It bridges the gap between compression and saturation. A mastering grade limiter is characterized by an infinite ratio and a true-peak detection. This guarantees that a signal will never exceed the threshold of the limiter.

Because a limiter has a very strong behavior in regard to the input signal, it can generate distortion. To prevent it as much as possible, plug-in constructors use a complex envelope strategy involving looking ahead with attack time, and often give the user a way to control the release time.

Alas, oversampling is often used in limiters to prevent intersample peaks from passing through the limiter.

Next article in this series
Part 3 – Advanced processing and Dolby Atmos mastering

The post How to Use a Limiter, Part 2 – Limiter Theory – Knowing your tools appeared first on FLUX:: Immersive.

Limiter processing is one of the hot topics on the internet about sound processing. Its close relation with mastering and loudness leveling makes it an unmissable tool for sound and music production.

In this first article, in a series of three, we will have a very basic look at limiters to help the less experienced to sort out what’s going on. In the next article we will go much deeper, so stay tuned!

If you are in a hurry, skip down to the TL;DR section of this article to get a summary, as well as a video explanation of the subject.

What is a True-Peak limiter, and are there different types of limiters?

The most common definition of a limiter, is to consider a limiter being a compressor with a ratio superior to 10:1. During this series of articles, we will assess that what we call a limiter is a True-Peak limiter, which has more constraints than the previously mentioned type of limiter.

The limiters we are interested in here, the true-peak limiters, are dynamic tools specifically designed to reduce audio crest, very much like a safety guard preventing any clipping from the digital to analog stage. Thanks to the peak reduction it is possible to use such a limiter to increase the loudness of the input signal.

Why the need for limiting?

The very last process of music production is to set the overall level, or loudness, of a mix. Limiting is the only safe way to amplify the loudness of a mix, but it comes at a cost.

A limiter will cut the crest of the signal to create some headroom to allow amplifying the rest of the signal. The cost of limiting is a loss of dynamic and an additional distortion.

The true-peak level is the actual level of the samples, or of the waveform if you prefer. The loudness is closer to our sound perception and smooth out quick sound variation because they do not matter that much in our perception of sound loudness.

Using a limiter also provides the guarantee to never clip the digital-to-analogue stage. This is a very important safeguard and explains why there is always a limiter at the end of the chain, even if it doesn’t do much.

Limiting will always come at the cost of more saturation added to the signal, but in a very much more transparent way than just cranking the output gain and clip the converters. Clipping the converter is considered as a technical error (even if some popular master does clips at the converting stage).

When is there a need for limiting ?

If you want to make a mix louder without clipping the digital-to-analogue converter way beyond the red, you will need a limiter. The limiter will reduce the peak and provide you with headroom to amplify the whole gain without clipping the output stage.

Limiting is also often needed to conform a mix to certain norms. For example, most music streaming platforms will refuse a mix with a true-peak level higher than -1 dBTP.

Is limiting mandatory ?

Limiting is mandatory in the sense that a mix should never exceed 0 dBFS. So using a limiter with a threshold at 0 dBFS will always prevent that from happening. Most of the time, the different target platforms (streaming, broadcast, etc.) ask for mixes that do not exceed -1 dBFS.

Increasing the loudness of a mix is never mandatory. Maybe we will create a debate here, but loudness in music production is very much an aesthetic decision. So, to continue with these controversial topics; a louder mix does not sound better than a quiet one. Actually, it sounds less dynamic and more distorted. Also, there are no norms in music diffusion. Each and every platform has its way to handle the loudness of submitted audio files.

For example, we often encounter the idea that a good deliverable should have a loudness of -14 LUFS-I with a true peak never exceeding -1 dBTP . This value comes mainly from the Spotify guidelines. But, it is not entirely exact, as Spotify offers different loudness targets for their customers. There is a loud (-11 LUFS-I), normal (-14 LUFS-I) and quiet mode (-19 LUFS-I). Apple has recently moved from -16 LUFS-I to -18 LUFS-I and before 2022, YouTube normalized loudness at -12 LUFS-I (now -14 LUFS-I). So which one should we choose? The common consensus is around -14 LUFS-I because it covers the biggest user base.

Then, what happens with a file that is above the target? If a file is submitted with a loudness target above the recommendation of the platform, the file volume will be simply dropped by the number of dB necessary to match the recommendation. So the process is transparent to what you’ve mixed and mastered.

If a file is lower than the target, most of the streaming services do nothing about it. The file will simply be quieter than the other one. YouTube used to be an exception before 2022, but Spotify in loud mode will limit the content to match the -11 LUFS-I target.

So how do we handle this mess? It seems there are three possible solutions.

• Follow the most common recommendation, aka Spotify (-14 LUFS at -1 dBTP)
• Align on the loudest one to make sure that no processing will affect your work (at the detriment of the dynamic range)
• … Don’t care about it?

Actually, the last point is the one defended by the author. Loudness and more importantly dynamic range is not only a technical thing, it is also an aesthetic choice. Some genres of music have built their aesthetic on very compressed and saturated sound, where others want to have all the accessible dynamics.

As a general guide, we will simply assume that it is a best practice to never exceed -1 dBTP. Also, it is preferred to have the loudest peak of a program, or a song, to always hit this -1 dBTP target.

TL;DR

Mastering limiters are designed to reduce the crest of a mix and allow it to increase its loudness. Their true-peak characteristic allows them to never let a sample cross the threshold.

Limiting should always be used to prevent a mix from clipping the digital-to-analogue converter. However, due to the many different loudness targets found in the streaming services, it is difficult, if not impossible, to “go-to” recommendation as for the loudness of a track. It seems to be more an aesthetic choice than a technical one, at least, in the music industry.

Appendix

dB ? dBFS ? LUFS ? What is it all about ?

There are quite a few acronyms and concepts to explain around sound pressure level and how it is measured. Because sound is a mechanical wave, the primary way to measure the sound pressure level is to measure how the pressure evolves in a space.

First, the relation between sound pressure, and how we experience the sound level, is not linear. For example, when the sound pressure is doubled, we do not perceive a sound twice as loud. In fact, to have a sense for a sound being twice as loud, we need to multiply the pressure by ten. This is why we express the sound pressure level in decibels, which is a logarithmic scale that is much closer to our perception. When the sound pressure is doubled, there is a gain of +3 dB. When the pressure is multiplied by ten, there is a gain of +10 dB.

Depending on the field of interest, there are many different units built around the decibel scale. The one that is used in digital sound is the dBFS, or decibel full scale. In the digital domain, sound is represented by samples, whose amplitude can take absolute values between 0 and 1. The number of actual values that a sample can take between 0 and 1 is defined by the quantification (16 bits, 24 bits, etc.). But this is a linear scale, and thus, it does not correspond to our perception of sound. The dBFS solves this problem. A value of 1 in linear corresponds to 0 dBFS, a value of 0 in linear corresponds to -inf in dBFS (-96 dB at 16 bits, -144 at 24 bits, etc.).

Now that we have a scale that behaves closely to our perception, we need to find a way to measure sound loudness. Here, a peak measurement (the value of each actual sample in digital sound) is not a good candidate, because fast sound variation in volume does not matter that much in how we perceive loudness. Also, the frequency has a strong impact on how loud a sound seems. This is why engineers have proposed the loudness unit.

There are different time windows for the loudness measurement : momentary, short-term, long and integrated, which correspond to the following citation from the EBU Tech 3341:

1. The momentary loudness uses a sliding rectangular time window of length 0.4 s. The measurement is not gated.

2. The short-term loudness uses a sliding rectangular time window of length 3 s. The measurement is not gated. The update rate for ‘live meters’ shall be at least 10 Hz.

3. The integrated loudness uses gating as described in ITU-R BS.1770-4. The update rate for ‘live meters’ shall be at least 1 Hz.

In the music industry, it is the integrated value that is used as a reference for streaming services.

Next article in this series
Part 2 – Limiter Theory – Knowing your tools

The post How to Use a Limiter, Part 1 – True Peak limiting and Loudness processing appeared first on FLUX:: Immersive.

Les 22 et 23 novembre l’équipe de FLUX:: est heureuse de vous retrouver au salon JTSE à Paris. Au-delà de notre stand, où nous présenterons les derniers développements du moteur audio immersif SPAT Revolution et notre prochaine mise à jour du FLUX Analyzer, des démonstrations quotidiennes seront disponibles dans une configuration studio spécialement conçue pour l’occasion.

Dock Haussmann, Mezzanine #9

Courtes présentations quotidiennes
Mardi 11:30, 14:30, 16:30, 18:30
Mercredi 10h30, 13h30, 15h30

La 26ème édition des JTSE se tiendra les 22 novembre (de 9h30 à 20h) et 23 novembre (de 9h30 à 18h) aux Docks de Paris Porte de la Chapelle avec une vaste gamme d’exposants dans les différents domaines de l’industrie : rigging, éclairage, audio, scénique, supports, sièges, etc.

Votre passe visiteur gratuit est disponible ici

The post FLUX:: Immersive vous attend pour la 26ème édition du JTSE à Paris appeared first on FLUX:: Immersive.