Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Dolby/Atmos coming to Mixbus
#21
I think you have to do some research about binaural listening stuff and immersive audio. Binaural works and not half bad if done properly. Keep in mind: you have only two ears don't you?

And yes there are headphones available which do atmos. The most common ones these days are the airpods. Works fine with mac ;p
2023 Mac mini m2pro with 32GB RAM with audient id44mk2
Reply
#22
(01-17-2024, 10:13 AM)arthie Wrote: And yes there are headphones available which do atmos. The most common ones these days are the airpods. Works fine with mac ;p

Dolby Atmos will play on any headphones. You only need specialised headphones (such as AirPods) for the dynamic head-tracking featue.
Intel | Ventura | www.brownsound.net
Reply
#23
Any headphone will perform binaural listening, that is true. So you either need a software which renders the atmos for you into the binaural stream or a hardware. The airpods are the ones which do atmos with macs build in stuff and probably the most commonly used to iTunes-Atmos-Music thing (that was what I wanted to point out with that post).
2023 Mac mini m2pro with 32GB RAM with audient id44mk2
Reply
#24
(01-17-2024, 10:13 AM)arthie Wrote: Binaural works and not half bad if done properly. Keep in mind: you have only two ears don't you?

Yes but our ears are sculpted to detect sounds coming from different directions - whereas sounds coming through a headphone or earpiece will only ever come from one direction. Stereo works by delivering different amounts of a sound to each headphone.

So if Dolby Atmos extends that somehow to emulate binaural sound, that's gotta be worth hearing !
Knowledge is knowing a tomato is a fruit...
Wisdom is knowing you don't put tomatoes in a fruit salad !!
Reply
#25
Didn't MixBus v9 just get released this summer. So MixBus v10 is coming soon?
Reply
#26
Johne: short answer: yes it does, that is what HRTF means by the way Wink

HRTF = Head Related Transfer Function, perhaps that helps understanding the science behind it, when writing the abreviation in long words.
2023 Mac mini m2pro with 32GB RAM with audient id44mk2
Reply
#27
I hope Harrison will implement the HRTF aspect - it sounds amazing  Cool

Now where did I put them old headphones ???
Knowledge is knowing a tomato is a fruit...
Wisdom is knowing you don't put tomatoes in a fruit salad !!
Reply
#28
if they do an option for binaural listening (which is kind of a must have for atmos in my opinion because for music it is for sure the most commonly used listening method by any customer), the HRTF thing will surely be part of it. We know Harrison for doing things the right way (not the fast one Wink ).
2023 Mac mini m2pro with 32GB RAM with audient id44mk2
Reply
#29
Greetings, All -

Here are my thoughts regarding MB/MB32C v10, Atmos, etc.

First... I would highly recommend that it is about time for Harrison to implement a "New Age" Product; call it Harrison MB ATMOS or whatever.
There, the focus can be all the current, and forthcoming multi-channel and spacial positioning output and "dummy head" recording aspects that
may or may be actually needed by upcoming recording engineers & producers. I feel that it is important to "break away" from the current
paradigm of input channels and STEREO outs so as to preserve it as a solid alternative for those who choose to remain in the L/R past.
I, for one, would remain solidly in this category of customers; I have no desire to be involved with multi-channel out sound production
at this point in my life. (I'm joining the "Tassy" movement.) But, be assured, I would be 100% supportive of any new processing tools
that would help me to improve my current MB/MB32C L/R channel productions so a continuation of those Product lines (v10, v11, etc)
would be fine by me.

Second... I also keep a candle in the window for the possible arrival of a mature MIDI based work environment.
Here, my preference would be for a MIDI Window (ala, CUE, REC)... as its own section in Mixbus, not as a set of expanded
channel lanes in the Editor. I feel this would better focus MIDI only related operations, and allow for a whole collection of
Hot-Keys and other custom command assignments to be defined - just for MIDI production efforts. And, just like for the CUE
section, all created (input) tracks should be carried over into the Editor & Mixer Windows where they can be dealt with in a consistent manner.

Ok... ATMOS... If, at the heart of ATMOS, is the concept where every input source should have the freedom to exist anywhere in the (post) mix,
then I cannot perceive how that would accomplished in the current buss assign paradigm; more destination definition for a 3D output space would be necessary.
This is one of my reasons for a new Harrison break-away Product (see above). Essentially, MB/MB32C would be one paradigm and MB ATMOS would be a
completely different other. I believe this would give Harrison/SSL a distinct advantage over other DAWS - No unessential "baggage" to carry forward. 
All the "lessons learned" in the current MB/MB32C Products can be applied without the concern for trying to assure that all current MB/MB32 functionality
remain supported. In the expanded 3D output model, a L/R only product should be "just another of the output choices", as should be 5.1, and 7.1.
In essence, solve general 3D and you've accomplished everything. 

Finally - moving current L/R Projects to 3D... 
Remember, the "only" thing you should need to do is STEM out all your L/R based tracks and other sources and then re-import them into the new 3D input stage.
There, each track and source would be assigned its own 3D mix position. Other than that there should be no concern whatsoever regarding past version session
or other DAW compatibility - STEMS are universally compatible.

So.... That's about everything I've been thinking about on this topic.
I'm eagerly looking forward to V10 and beyond!!!

Cheers!
Patrick
Reply
#30
(01-23-2024, 12:12 PM)PBuryk Wrote: First... I would highly recommend that it is about time for Harrison to implement a "New Age" Product; call it Harrison MB ATMOS or whatever.
There, the focus can be all the current, and forthcoming multi-channel and spacial positioning output and "dummy head" recording aspects that
may or may be actually needed by upcoming recording engineers & producers.
I feel that it is important to "break away" from the current paradigm of input channels and STEREO outs so as to preserve it as a solid alternative for those who choose to remain in the L/R past.
I, for one, would remain solidly in this category of customers; I have no desire to be involved with multi-channel out sound production
at this point in my life. (I'm joining the "Tassy" movement.) But, be assured, I would be 100% supportive of any new processing tools
that would help me to improve my current MB/MB32C L/R channel productions so a continuation of those Product lines (v10, v11, etc)
would be fine by me.

I have a very different attitude to this... I feel it is imperative for Harrison to encompass immersive mixing into the current 32C architecture.
Starting with the Series Ten, Harrison have had simultaneous stereo and multichannel bussing available to the mixing engineer.
To create a seperate product 'just' for multi channel does not make sense. I would prefer the alternative to be able to do a LR mix and then if needed 'open' that out for an immersive mix.

(01-23-2024, 12:12 PM)PBuryk Wrote: Second... I also keep a candle in the window for the possible arrival of a mature MIDI based work environment.
Here, my preference would be for a MIDI Window (ala, CUE, REC)... as its own section in Mixbus, not as a set of expanded
channel lanes in the Editor. I feel this would better focus MIDI only related operations, and allow for a whole collection of
Hot-Keys and other custom command assignments to be defined - just for MIDI production efforts. And, just like for the CUE
section, all created (input) tracks should be carried over into the Editor & Mixer Windows where they can be dealt with in a consistent manner.

Completely agree that for those who need MIDI functionality there needs to be more development... but just as you don't 'need' multichannel I don't 'need' MIDI. I would however argue that MIDI like multichannel needs to be in the one platform, not an add-on.
Just because I don't use a function does not mean it should be dropped or treated as a seperate product.

(01-23-2024, 12:12 PM)PBuryk Wrote: Ok... ATMOS... If, at the heart of ATMOS, is the concept where every input source should have the freedom to exist anywhere in the (post) mix,
then I cannot perceive how that would accomplished in the current buss assign paradigm; more destination definition for a 3D output space would be necessary.

Atmos brings an entirely different approach to the mixing process. Object based mixing by its nature does not involve the use of common bussing structures. Stemming a mix for M&E deliveries or for re-mixing in a film project can be achieved using meta data.
In reality a music mix might contain a couple of stereo Beds with the majority of tracks being positioned using Object.

(01-23-2024, 12:12 PM)PBuryk Wrote: This is one of my reasons for a new Harrison break-away Product (see above). Essentially, MB/MB32C would be one paradigm and MB ATMOS would be a
completely different other. I believe this would give Harrison/SSL a distinct advantage over other DAWS - No unessential "baggage" to carry forward. 
All the "lessons learned" in the current MB/MB32C Products can be applied without the concern for trying to assure that all current MB/MB32 functionality
remain supported. In the expanded 3D output model, a L/R only product should be "just another of the output choices", as should be 5.1, and 7.1.
In essence, solve general 3D and you've accomplished everything. 

One man's unessential "baggage" could be another's "go to" tool....

(01-23-2024, 12:12 PM)PBuryk Wrote: Finally - moving current L/R Projects to 3D... 
Remember, the "only" thing you should need to do is STEM out all your L/R based tracks and other sources and then re-import them into the new 3D input stage.
There, each track and source would be assigned its own 3D mix position. Other than that there should be no concern whatsoever regarding past version session
or other DAW compatibility - STEMS are universally compatible.

So.... That's about everything I've been thinking about on this topic.
I'm eagerly looking forward to V10 and beyond!!!

Cheers!
Patrick

Sorry but merely re-panning a number of stereo stems does not work.
One of the major reasons Cinema mixers use a Centre channel is screen width. In wide screen a phantom stereo image just does not work.
If you pan a special effect across the screen it dips in the middle if you don't have LCR panning. True multichannel also allows for incredible clarity and isolation.

I find it funny that the L+R 'only' crowd poo poo multi channel in much the same way as Mono was touted as the "God" with Stereo being work of the Devil...  Rolleyes
Macmini 8,1 | OS X 13.6.3 | 3 GHz i5 32G | Scarlett 18i20 | Mixbus 10 | PT_2024.3.1 .....  Macmini 9,1 | OS X 14.4.1 | M1 2020 | Mixbus 10 | Resolve 18.6.5
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)