Your tracks with FX in Atmos - Dolby Atmos Mixing Tip No.3

[@GruberWerner]

Genial das ‚Beam Stacking‘ + Passe Thru 👌💯🔅🔆

[@shane_taylor]

This just opened up a whole new level of flexibility. Very innovative.

[@eddie3569]

Another great tip from Fiedler Audio.

[@RunningRedford]

Great tip. Thanks!

[@spane5mixline]

Dope

[@MrEarlabs]

Have been working with the DACE since a few weeks and it has been a great journey so far. Since you ask for questions, requests. etc. I have one : if i want complete overview of the soundsources in the soundfield I need to open all the beam windows. In Reaper Reasurround it is possible to see (with different colors for different channels) what sound is where. Is it possible to have some sort of window where we can see this?

[@fiedler-audio]

This feature is on our list, but for the full version of the Dolby Atmos Composer.

[@MrEarlabs]

@@fiedler-audio sorry. I do have the full version. Dace is the element version. My mistake. But very good news indeed!

[@thomaskoner1287]

super. how much latency per beam instance?thanks!

[@SamHocking]

Beam itself is zero latency. Composer generates 10.6ms latency for speaker output, 30.6ms for the binaural.

[@fiedler-audio]

@@SamHocking Not entirely correct, Sam. The actual latency (not the required block size) of the Composer is 32 samples if binaural is off or 993 samples if binaural is on (for 48 kHz). For 96kHz it will be more samples but somehow in the same region time wise.

[@SamHocking]

@@fiedler-audio I see, thanks for the clarification.

[@thomaskoner1287]

​@@fiedler-audiothanks

[@omicronsrule6565]

Hi, can we also render for traditional headphones in binaural . wav ?

[@fiedler-audio]

Yes. You can monitor and render for both headphones and speakers.