Dolby Atmos For Pro Tools: First Impression

[@issacnewton7846]

Hi Alex, Thank you so much for all your insights...Very useful, looking forward for the upcoming sessions..... Blessed Day.

[@Kharrari]

I cant wait to try this out.

[@Beniemacaulay]

The internal Dolby renderer has the I/O setting button on the renderer itself for quick access but I noticed that whenever you go into the I/O to adjust the binaural setting, play back stops which is not very convenient in my Opinion. Thank you for your videos btw I've learnt so much from your channel 🫶

[@christurbiville]

Loving the Renderer being baked into PT. I just wish they would have done what other DAWs have done and update some of the PT plugins to immersive formats, like reverb, delay, comp, eq, etc. Hopefully that will come in the next update.

[@DolbyAtmosMixing]

True.

[@gregoryivesdolbyatmosmusic]

Hah! I was hoping you would get to this! I have it installed, but been on a film mix so I have not had a sec to update. The new update however has been solid all around as was version 2023.9. Some nice additions. I like that Dolby removed the clustering process of spacial coding from rendering.

[@DolbyAtmosMixing]

Ha! That’s exactly why I showed it on the using the laptop before I completely messed up my IO configuration on my main machine ;)

[@ivodiastudio]

Brother, very good! Thank you for your videos

[@pletch]

Great videos! I discovered your channel today when exploring Dolby Atmos. Great content! What audio interface do you recommend for a home studio and mixing in Dolby?

[@DolbyAtmosMixing]

Thanks for tuning in. For starters, you’ll need a 16-channel output for 12 speakers along with a processor for room tuning, bass management, and speaker time alignment.

[@lucioardito4413]

finally protools has added rendering to its software! this will certainly give musicians and producers a way to develop this aspect of music. good video! good!

[@DolbyAtmosMixing]

Setting up the IO is so much easier this way and a great way to get started on mixing with headphones.

[@paulovmendes]

Thanks for the video Alex. The binaural settings plugin not working with the internal Renderer is a bit awkward in my opinion. I know this is a streamlined version of the DAR and we can´t have it all, but I think AVID and Dolby should allow this, as is not practical to go to I/O every time we want to change a binaural setting, in particular because we can´t do it on the fly. Also, not being able to use the Dolby panner is ridiculous too. As far as live loudness metering goes, well, it´s easy to route the 5.1loudness output into a PT Aux and insert a meter there. But to analyse offline, it´s like in the DAR, we need to print it first, in this case into a 5.1 track in PT, instead of the ADM print in the DAR. People with Sphere software, can route it to a 5.1 input and monitor loudness on the fly with the Sphere integrated LUFS meter instead of feeding the 5.1 out from the Renderer into an Aux in PT.

[@gasmusix]

Hi Alex, excellent information about atmos, a query with the new protools what would be the routing indicated to use protools in this new version with Sphere to have the monitoring for applemusic?

[@DolbyAtmosMixing]

Hey there! I haven't tried it yet, but it should be no different than when using the external renderer. You will need to assign the Pro Tools virtual sound card output to one of the inputs available in Sphere. This should work. Cheers.

[@gasmusix]

@@DolbyAtmosMixing yes that's what I thought, but for example I have a Focusrite Pro Red and now with the internal render in the protools output (playback engine) it goes directly to the Focusrite RED so Sphere is out, the interesting thing would be to have all the monitoring scheme that Sphere offers. I tried sending it to the sheper 16, 24 or 32 and in all cases the monitoring offered by the internal dolby rendering is binaural. I hope you can make a video about it, thanks.

[@sonexcellencea]

Can wait for the next video on this Thank you

[@PickUpGoliath]

A great step. Although the Dolby Atmos Panner plugin isn't supported, so you still need to use the Renderer if you're using that. I use the step sequencer in it a lot, so I'm still stuck with it for now.

[@Ein-Stuck]

Does the new implemented renderer work in the windows version of protols?

[@EdgMixing]

How do you decide what is talking to the internal renderer ? Is it the monitor path in the I/O ?

[@DolbyAtmosMixing]

It’s assigned from the track’s channel output. It can either go to a physical output from your audio interface, the 7.1.2 bed, or an internal bus. In the case of this video, I routed all the channels to the bed and showed how to route to a pair of objects to show the automation example. Hope this helps.

[@Vooced]

The Dolby Renderer has quite usefull speaker calibration features... Any of these in the PT Renderer? Or any way to output to a bus to be able to preprocess the speaker outputs?

[@gastonfederici5068]

Hello Alex, I'm intrigued by the new version of Pro Tools that features Dolby rendering. Could you please share details regarding whether this version includes the option to calibrate speakers, both in terms of gain and delay? I value your expertise and insights greatly. Thank you!

[@DolbyAtmosMixing]

Hello, no this version does not include the additional features that the standalone version does (room EQ, time alignment, bass management, export to MP4, etc)

[@gastonfederici5068]

thanks for your answer

[@moshuajusic1811]

What do you make of the change to object size? It used to be spread plus a volume increase, which makes sense and translated everywhere. Now it's a nasty comb filter effect with no volume increase, but only in Pro Tools binaural monitoring and "re-renders". I now have to export an ADM and import to Logic to check Dolby rendering as well. :/

[@menelaos1986]

Hi Alex, Thanks for this video. I think that all Pro Tools users are very excited that AVID has finally managed to integrate its renderer into the DAW, something that other DAW manufacturers have been doing for a long time. What bothers me at the moment is the fact that we need the paid Production Suite to be able to use the Music Panner or Binaural Setting plugin, for example. Maybe I'm doing something wrong, but the plugins need the information of the local host, which can then only connect via the External Renderer. I think it's an extreme pity that AVID doesn't simply take the step to swim with the other DAW manufacturers.

[@sambemixingrecordings]

thanks, I been messing with it off and own and a client asked about it tonight ... so I'm here lol..

[@RaphFLC]

And what do you think about the Dolby Atmos Renderer in Logic ? Because I don't remember seeing one of your video talking about Logic Pro.

[@toufanrecords]

Dolby Atmos buffer size for Binaural is 512 . and Airpod buffer size is 256 . Also , Air pod is stereo on I/O . do you have any suggestion ?

[@mixinginthebox]

TY

[@carloscarreno3774]

Saludos Bro!!! en Studio One es GENIAL.

[@MultiKulti]

How can someone use a calibration software like Sound Id with. this internal Renderer ? Or Sphere Software ?

[@DolbyAtmosMixing]

I would recommend Sonarworks reference ID, however I don’t think they support bass management so you’d need to figure that out in advance.

[@Anmonmon-lr8zl]

more video plz

[@dstagl]

You can't currently adjust internal renderer binaural settings in real-time. I think the best practice is to set a set of objects to each setting, and then assign those different objects in real-time.

[@x-pe4324]

alex deberías hacer también este contenido en español jajaja no domino mucho el ingles😁😁😁 . tengo pro tools y por falta de contenido en español no e podido aprovechar este nuevo formato 😅 . no se ni como empezar un proyecto desde cero . o si tienes otro canal en español . que enseñe este tipo de formato te lo agradesco 👍

[@DolbyAtmosMixing]

Hola gracias por tus comentarios. Mi español no lo mío tampoco jaja. Checa Hector de audio producción él tiene un buen canal sobre estos mismos temas.

[@AnthonyRodriguezOnline]

They lost me with not having the loudness analyzer lol…I love my ext dar

[@zaproductionss]

Que tal Alex, saludos desde Chile y te conocí gracias a Héctor de audioproducción, ayer estuve viendo tu vídeo donde muestras el proceso por partes, donde la primera es creación de tu plantilla y creas 5 auxiliares que vendría siendo la cama de tu sesión ¿con esta actualización ya no requerirías esos auxiliares enrutando todo al bed de la sesión? espero me puedas responder, saludos nuevamente PD: no se hablar ingles jejejeje pero se que entiendes el español pero adelante con los subtítulos en tus vídeos

[@garethde-witt6433]

Let’s face it Dolby Atmos is totally useless and impractical. You have to have a megabuck setup to listen to it and most people will listen on headphones because they can’t and will never be able to afford it. The mixes that are done for music suck no matters who produces them, it’s only real application is in movies where it shines. If you have vinyl forget it and I doubt there will be many CDs that will have it encoded. So people will be stuck with the imperfect streaming formats which will be unsatisfying. I personally don’t like it (my opinion ) I will never use it or listen to anything mixed in the format.

[@blinksy7201]

yeah, i thought the same thing with youtube in 2005. who would want to watch streaming video on the web. but here we are in 2023.

[@Dystopian84]

@@blinksy7201 in terms of practicality , you tube is like the polar opposite of Dolby Atmos so I think that it is a wrong analogy . What is currently going on with Atmos is more similar to what happened to NFTs

[@menelaos1986]

We said the same thing about CDs back then, that we'd rather stick with vinyl. People used to think the same thing about stereo. Times are changing and I think we should steer towards focusing on Dolby Atmos. In my opinion, however, the mixing engineer's workload changes significantly here, unless you just want to bounce a simple upmix and start an Atmos mix from scratch. Will the customer pay for this extra effort? (I'm only referring to the music here)