Start a new topic

Dolby Atmos Workflow

I need to clarify some questions about the signal Flow in ATMOS related in post-production ambients: 1.- Do i need always a RMU unit (Separated Computer with the Atmos Mastering Suite) to encode the ATMOS file? or is possible to make in the same Protools Computer with internal routing? 2.- What happen with the ATMOS file? where it is added or summed with the final Video File? Another Dolby Suite? or a Video Editing software? 3.- Which is the sync method of the 2 Computers (Protools & RMU)? SMPTE by LTC? EUCON or another protocol? 


Yes.

Adam, 

re: Your comment from 11 months ago:

   "The tool used for Dolby Digital Plus with Atmos Content or Dolby TrueHD is the Dolby Media Producer Suite"  


I would like to follow up...   

Can the Atmos content created with the encoder from the producer suite be fed directly into a 7.1.4 capable sound bar for QC ? (Say, on a thumb drive). 

Thanks. 

Mark

Thanks Andy; got back with Bill Stroupe and we are communicating. My issue is down to being able to discover the DAC 3202 on a Dante or AES67 network.

Hello babamac@mac.com

I had a look around to see what insight I could give - and found that you have/had an open case with our Cinema Support Group - that ticket may have closed - but it has been reopened and the support engineer you were communicating with indicated he would contact you.

Best Regards

Andy

I AM TRYING TO CONNECT TO THE DAC3202 VIA DANTE VIRTUAL SOUND CARD. THEN I FOUND OUT THE DAC3202 IS AES67 SO NOW I'M USING RAVENNA VIRTUAL SOUND CARD. THE DAC3202 IS NOT BEING DISCOVERED BY DANTE CONTROLLER OR BY MERGING ANEMAN CONTROLLER. HOW DO I CREATE THE SDP FOR THE DAC3202 DEVICE?

I would like to go from Dolby Atmos Renderer to a DAC3202. I got into the DAC3202 once but when I set it to DHCP I lost communication. I can't get to the web UI. Also it doesn't seem to recognize a thumb drive.

Is their any way to reset or restore defaults?

Thanks Ceri, much clearer now.


1 person likes this

Hi Adam, just noticed that V3.3 of the renderer will do this in a more simplified way. Will it work if my output from the renderer is a binaural file out of an Atmos mix?


I´m interested in using the Production Suite to master/remaster music stems in Dolby Atmos and then render for both binaural for headphones and Atmos with speakers. Can I use this new feature on V3.3 to generate MP4 files for delivery that address both?


No, the renderer's export to MP4 exports a file that is DD+JOC based and therefore does not contain the binaural metadata parameters. The exported file can be played on a device that decodes Atmos to headphones however so if you were to play the exported file on a Windows PC that has the Dolby Access/Headphone enablement then you'd decode Atmos over headphones binaurally. That same file if played on a consumer playback system that decodes Atmos to speakers will do that successfully also. 


I was reading with interest about the Atmos Music initiative, the integration with Amazon HD, the Echo Studio smartspeaker etc. but still in the dark about the mastering and delivery workflow for that purpose.


Could you delve more into this subject please? Thanks


Artists, producers and engineers will deliver BWAV ADM with an integrated loudness of -18LKFS (measured on a 5.1 rerender). This BWAV ADM should have no more than 1 second of silence before track start and end immediately after the track ends. The BWAV ADM should contain all relevant metadata including Binaural Render Mode metadata, as set in the Window>Binaural Render Mode, thus making the master suitable for encoding into headphone focussed codecs as well as the current speaker focussed codecs.


2.  Once you have a Dolby Atmos master file recorded it can be encoded to Dolby Digital Plus with Atmos Content (for streaming) or to Dolby TrueHD (for Blu-Ray).    The master files used for encoding can be .atmos,  or ADM.wav or IAB.mxf exported from the Renderer.    


The tool used for Dolby Digital Plus with Atmos Content or Dolby TrueHD is the Dolby Media Producer Suite.   There is also an enterprise command line tool available name the Dolby Encoding Engine for cloud and distributed encoding of Dolby Digital Plus with Atmos Content.


For streaming purposes the Atmos audio (Dolby Digital Plus with Atmos content - .ec3) is multiplexed with compressed video (.h264/.h265) to create an .mp4 which is segmented for streaming services delivery.   Dolby Encoding Engine can do this and there is also a command line open source mp4 multiplexer that Dolby has made available on Github.  


Hi Adam, just noticed that V3.3 of the renderer will do this in a more simplified way. Will it work if my output from the renderer is a binaural file out of an Atmos mix?


I´m interested in using the Production Suite to master/remaster music stems in Dolby Atmos and then render for both binaural for headphones and Atmos with speakers. Can I use this new feature on V3.3 to generate MP4 files for delivery that address both?


I was reading with interest about the Atmos Music initiative, the integration with Amazon HD, the Echo Studio smartspeaker etc. but still in the dark about the mastering and delivery workflow for that purpose.


Could you delve more into this subject please? Thanks


Hi Sebastian,


There is more information of what you can use to identify ADM Wav and the components that would identify it as Dolby Atmos.


The ADM atmos profile doc can be downloaded from here: https://developer.dolby.com/technology/dolby-atmos/adm-atmos-profile/


The includes looking for AXML as specified here: https://tech.ebu.ch/docs/tech/tech3285s5.pdf  (see section 4.2)   and also the Dolby specific dbms chunk.   This document is currently in review but will be posted to this site when it is available.


Hope this helps.


Best,

Adam

Hi Sebastian,   It depends how intelligent you need to the system to be.   The easiest thing to do would be to look at the channel count of the .wav.   Do you have any interleaved .wav if your workflow that go beyond 6 channels (5.1) or 8 channels (7.1 or 5.1+2)?   If not interrogating the channel count with MediaInfo for being more than 6 channels might be sufficient.    If not I'll need to get back to you.    There is an ADM validation component as part of our SIDKs but that might be overkill for your implementation.   I will get  back to you about other potential solutions.

Thanks,

Adam

Adam, short follow up question: Is there a way to tell from the metadata that an ADM file is a Dolby Atmos file? We're trying to build automatic workflows into our MAM system that need to tell if a file is a Dolby Atmos file or not.

We didn't find anything yet that can be used as a unique identifier.

Thanks,

Sebastian

Great, thanks for the info Adam!

Hi Sebastian,  


Not really.   It is personal preference and up to any given facility or company to decide what works best for them.


Archiving  a .atmos master file set means keeping four files around in a folder so perhaps more opportunity to misplace one.   On the positive they can be opened up in the Renderer for punch-in operations and rewriting downmix metadata without conversion.  


Archiving a ADM .wav means  only keeping track of a single file.   They can be readily imported as session data into Pro Tools.   The only downside is that these would need to be convert back to .atmos if you needed to perform a punch-in from the original Pro Tools session.   There is however the extra step of exporting an ADM .wav for export.


On balance I think ADM .wav is a better choice for deep storage.


Best,

Adam

Hi Adam,

short question: Is there any advantage in having the .atmos master file set as an archive master in to archiving an ADM WAV master?

Thanks,

Sebastian

Login to post a comment