Blackmagic Forum

Hi everyone:

I'm creating a Dolby Atmos mix in Fairlight. Mostly I use the "Dolby Atmos Send" in "Patch I/O" page to route my tracks to correct channels of the internal Dolby Atmos Renderer. In this workflow I can use Menu-Fairlight-Immersive Audio-Export Master File to export an ADM BWF master correctly.

However by reading tutorials I think I can try this:

1. Creates a bus with format "Dolby Atmos Master";
2. Assign buses and tracks to the out of this bus to route everything. In my comprehension to the tutorial, buses assigned to this bus will be considered as beds and tracks assigned will be considered as objects.

Based on my understanding, I think this is another type of workflow. Everything looks correct except when exporting the ADM BWF - The exported file is blank. It does recorded the info of the mix but just without any sound.

So now I'm wondering that is this way a correct workflow? If it is, what is my mistake? I can see that in the export window, the source is called "(My bus name) assign" instead of "Dolby Atmos Send Patching", and is greyed out so I can't change it. Thanks!

Please indicate Resolve version, operating system, and computer spec. Include this information in your signature to assist troubleshooting.

Any change routing via the Fairlight Mixer rather than Patch IO?

Can you include a link to the Atmos Project (.drp without media)?

izwb003 wrote:Hi everyone:

I'm creating a Dolby Atmos mix in Fairlight. Mostly I use the "Dolby Atmos Send" in "Patch I/O" page to route my tracks to correct channels of the internal Dolby Atmos Renderer. In this workflow I can use Menu-Fairlight-Immersive Audio-Export Master File to export an ADM BWF master correctly.

However by reading tutorials I think I can try this:

1. Creates a bus with format "Dolby Atmos Master";
2. Assign buses and tracks to the out of this bus to route everything. In my comprehension to the tutorial, buses assigned to this bus will be considered as beds and tracks assigned will be considered as objects.

Based on my understanding, I think this is another type of workflow. Everything looks correct except when exporting the ADM BWF - The exported file is blank. It does recorded the info of the mix but just without any sound.

So now I'm wondering that is this way a correct workflow? If it is, what is my mistake? I can see that in the export window, the source is called "(My bus name) assign" instead of "Dolby Atmos Send Patching", and is greyed out so I can't change it. Thanks!

If you have any chance to revert to v19.0.3.5, everything about Dolby Atmos seems good.
This issue started from the next release after v19.0.3.5 till now.

Reynaud Venter wrote:Please indicate Resolve version, operating system, and computer spec. Include this information in your signature to assist troubleshooting.

Any change routing via the Fairlight Mixer rather than Patch IO?

Can you include a link to the Atmos Project (.drp without media)?

I'm working with version 19.1.3 BUILD 7 on macOS Sequoia, M4 Pro MacBook Pro. Signature updated.

The problem seems will only happen when routing via Fairlight Mixer, while using Patch IO everything looks correct.

Here are two simple example .drp projects shows the problem - the "WithProblem" one uses the Fairlight Mixer to create routes and exports empty ADM BWFs, while the "WithoutProblem" one uses Patch IO and exports ADM BWFs correctly.

eviluess wrote:

izwb003 wrote:Hi everyone:

I'm creating a Dolby Atmos mix in Fairlight. Mostly I use the "Dolby Atmos Send" in "Patch I/O" page to route my tracks to correct channels of the internal Dolby Atmos Renderer. In this workflow I can use Menu-Fairlight-Immersive Audio-Export Master File to export an ADM BWF master correctly.

However by reading tutorials I think I can try this:

1. Creates a bus with format "Dolby Atmos Master";
2. Assign buses and tracks to the out of this bus to route everything. In my comprehension to the tutorial, buses assigned to this bus will be considered as beds and tracks assigned will be considered as objects.

Based on my understanding, I think this is another type of workflow. Everything looks correct except when exporting the ADM BWF - The exported file is blank. It does recorded the info of the mix but just without any sound.

So now I'm wondering that is this way a correct workflow? If it is, what is my mistake? I can see that in the export window, the source is called "(My bus name) assign" instead of "Dolby Atmos Send Patching", and is greyed out so I can't change it. Thanks!

If you have any chance to revert to v19.0.3.5, everything about Dolby Atmos seems good.
This issue started from the next release after v19.0.3.5 till now.

So... It sounds like a known bug? I cannot revert to previous version as I still have some projects to work with this version - maybe I have to wait for a fix update...

izwb003 wrote:

Reynaud Venter wrote:Please indicate Resolve version, operating system, and computer spec. Include this information in your signature to assist troubleshooting.

Any change routing via the Fairlight Mixer rather than Patch IO?

Can you include a link to the Atmos Project (.drp without media)?

I'm working with version 19.1.3 BUILD 7 on macOS Sequoia, M4 Pro MacBook Pro. Signature updated.

The problem seems will only happen when routing via Fairlight Mixer, while using Patch IO everything looks correct.

Here are two simple example .drp projects shows the problem - the "WithProblem" one uses the Fairlight Mixer to create routes and exports empty ADM BWFs, while the "WithoutProblem" one uses Patch IO and exports ADM BWFs correctly.

Atmos Example Projects.zip

eviluess wrote:

izwb003 wrote:Hi everyone:

I'm creating a Dolby Atmos mix in Fairlight. Mostly I use the "Dolby Atmos Send" in "Patch I/O" page to route my tracks to correct channels of the internal Dolby Atmos Renderer. In this workflow I can use Menu-Fairlight-Immersive Audio-Export Master File to export an ADM BWF master correctly.

However by reading tutorials I think I can try this:

1. Creates a bus with format "Dolby Atmos Master";
2. Assign buses and tracks to the out of this bus to route everything. In my comprehension to the tutorial, buses assigned to this bus will be considered as beds and tracks assigned will be considered as objects.

Based on my understanding, I think this is another type of workflow. Everything looks correct except when exporting the ADM BWF - The exported file is blank. It does recorded the info of the mix but just without any sound.

So now I'm wondering that is this way a correct workflow? If it is, what is my mistake? I can see that in the export window, the source is called "(My bus name) assign" instead of "Dolby Atmos Send Patching", and is greyed out so I can't change it. Thanks!

If you have any chance to revert to v19.0.3.5, everything about Dolby Atmos seems good.
This issue started from the next release after v19.0.3.5 till now.

So... It sounds like a known bug? I cannot revert to previous version as I still have some projects to work with this version - maybe I have to wait for a fix update...

After upgrading to the latest version (19.1.4), this issue persists. You might attempt downgrading to 19.0.3.5 to verify if Dolby Atmos functionality is restored. In my case, maintaining 19.0.3.5 remains the only viable solution for reliable Dolby Atmos operations.

izwb003 wrote:

Reynaud Venter wrote:Please indicate Resolve version, operating system, and computer spec. Include this information in your signature to assist troubleshooting.

Any change routing via the Fairlight Mixer rather than Patch IO?

Can you include a link to the Atmos Project (.drp without media)?

I'm working with version 19.1.3 BUILD 7 on macOS Sequoia, M4 Pro MacBook Pro. Signature updated.

The problem seems will only happen when routing via Fairlight Mixer, while using Patch IO everything looks correct.

Here are two simple example .drp projects shows the problem - the "WithProblem" one uses the Fairlight Mixer to create routes and exports empty ADM BWFs, while the "WithoutProblem" one uses Patch IO and exports ADM BWFs correctly.

Atmos Example Projects.zip

eviluess wrote:

izwb003 wrote:Hi everyone:

I'm creating a Dolby Atmos mix in Fairlight. Mostly I use the "Dolby Atmos Send" in "Patch I/O" page to route my tracks to correct channels of the internal Dolby Atmos Renderer. In this workflow I can use Menu-Fairlight-Immersive Audio-Export Master File to export an ADM BWF master correctly.

However by reading tutorials I think I can try this:

1. Creates a bus with format "Dolby Atmos Master";
2. Assign buses and tracks to the out of this bus to route everything. In my comprehension to the tutorial, buses assigned to this bus will be considered as beds and tracks assigned will be considered as objects.

Based on my understanding, I think this is another type of workflow. Everything looks correct except when exporting the ADM BWF - The exported file is blank. It does recorded the info of the mix but just without any sound.

So now I'm wondering that is this way a correct workflow? If it is, what is my mistake? I can see that in the export window, the source is called "(My bus name) assign" instead of "Dolby Atmos Send Patching", and is greyed out so I can't change it. Thanks!

If you have any chance to revert to v19.0.3.5, everything about Dolby Atmos seems good.
This issue started from the next release after v19.0.3.5 till now.

So... It sounds like a known bug? I cannot revert to previous version as I still have some projects to work with this version - maybe I have to wait for a fix update...

The latest version DaVinci_Resolve_Studio_20.0b1_Windows has this issue fixed!!

Hi everyone, I have used the AWS Media Convertion of Amazon to Create an MP4 File supporting Atmos Sound. The only issue with this is that when i played it back it sounded "weird" like it had been downmixed to 5.1 or something. I used MediaInfo to see what is going on, but it said "3-AC-3JOC(Dolby Digital Plus with Dolby Atmos)". I then, brought into DaVinci to see what was actually happening . In the Fairlight page it showed me 6 channels(5.1), instead of 12 for a 7.1.4 Dolby Atmos Master File. So now i cant really tell if i have done something wrong throughout the proccess or its just a Playback issue or DaVinci just doenst recognise that type of file. Can someone help me figure this out??

Odysseass wrote:Hi everyone, I have used the AWS Media Convertion of Amazon to Create an MP4 File supporting Atmos Sound. The only issue with this is that when i played it back it sounded "weird" like it had been downmixed to 5.1 or something. I used MediaInfo to see what is going on, but it said "3-AC-3JOC(Dolby Digital Plus with Dolby Atmos)". I then, brought into DaVinci to see what was actually happening . In the Fairlight page it showed me 6 channels(5.1), instead of 12 for a 7.1.4 Dolby Atmos Master File. So now i cant really tell if i have done something wrong throughout the proccess or its just a Playback issue or DaVinci just doenst recognise that type of file. Can someone help me figure this out??

It's good to know that DaVinci Resolve now imports E-AC3 with JOC, presenting it as a 5.1 audio stream. This is an improvement, as previous versions often wouldn't import these files at all.
However, as far as I know, there is currently no method to decode an E-AC3 file with JOC back into an ADM BWF file containing the original object movements. Therefore, I believe it's accurate to say that Resolve doesn't support this type of import if your goal is to retrieve or work with the original Atmos object data.