|
Avid Pro Audio CommunityHow to Join & Post • Community Terms of Use • Help Us Help YouKnowledge Base Search • Community Search • Learn & Support |
#11
|
|||
|
|||
Re: M1 Mac Mini running Atmos Renderer 3.7.0
Quote:
|
#12
|
|||
|
|||
Re: M1 Mac Mini running Atmos Renderer 3.7.0
I'm running the entry-level M1 Mac Mini, 8GB Ram, 256GB SSD... The thing is literally yawning... I might have to find more things for this computer to do around here...
|
#13
|
|||
|
|||
Re: M1 Mac Mini running Atmos Renderer 3.7.0
Just for clarification, the ONLY way you can get 128 channels into DAPS is using the DAB. If you want to work in an eco-system that is more pro audio friendly, unfortunately, you have to upgrade to the DAMS license - and apparently, it is NOT upgradable... (you have to buy DAMS from scratch) I'm using Ravenna network, with Merging Anubis as monitor controller, HORUS is my DA, and all of the routing is via ANeMan. Right now, I'm happy with 32 channels feeding the renderer, but eventually, I'll bump up my license...
|
#14
|
|||
|
|||
Re: M1 Mac Mini running Atmos Renderer 3.7.0
Quote:
Can you clarify if you have tried selecting a 128 channel coreaudio device in DAPS? Unfortunately I only have a DAMS license on hand. A colleague has my DAPS license so I can't test it. In versions previous to 3.7, there has been ZERO difference in the way DAMS and DAPS handles coreaudio I/O. They are exactly the same piece of software, and you could access the full 128 channels of Coreaudio I/O in both, regardless of whether it is the virtual DAB coreaudio sound card, an RME Madi FX, Dante PCIe-R card, or even an aggregate device with 128 channels of I/O. The only real difference between a DAMS and DAPS license has been that a DAMS license unlocks more of the speaker and control room functionality (Room EQ, speaker arrays, etc, etc) in the software. Other than that, DAMS and DAPS is exactly the same piece of software. They use exactly the same installer. The limiting factor to hardware I/O has never been DAMS or DAPS. It has been Pro Tools. Versions prior to 2021.6 have a 32 channel limit on coreaudio I/O. You need HDX1 or HDN to get 64 physical I/O out of it. For 128 channels, you need HDX2. From version 2021.6 onwards, Avid increased the Coreaudio I/O limit to 64 channels, but you still need HDX2 minimum for 128 channels. Like I said, I suspect a lot of people are delivering content using DAPS and DAB. Particularly if it is film work being done in the box. That is because of the hardware requirements for 128 channels in Pro Tools. Doing it through hardware becomes a $10,000+ investment just to access stuff like video sync peripherals...
__________________
Pro Tools Ultimate 2024.3. OSX 13.6.5. Win 10. HD Native. Lynx AES16e. Lynx Aurora 16. i9-13900KF. ASRock Z690 Steel Legend. 64GB Ram. AMD Vega 64. BM Decklink. Dolby Atmos Renderer 5.2. Trinnov D-Mon. D-Command. |
#15
|
|||
|
|||
Re: M1 Mac Mini running Atmos Renderer 3.7.0
Quote:
I'll try yet again, but I'm quite sure than DAPS is ignoring incoming audio above 32 channels. I can see that the object metadata paths are connecting, but audio is not coming through above 32... |
#16
|
|||
|
|||
Re: M1 Mac Mini running Atmos Renderer 3.7.0
Quote:
What version of Pro Tools are you using?
__________________
Pro Tools Ultimate 2024.3. OSX 13.6.5. Win 10. HD Native. Lynx AES16e. Lynx Aurora 16. i9-13900KF. ASRock Z690 Steel Legend. 64GB Ram. AMD Vega 64. BM Decklink. Dolby Atmos Renderer 5.2. Trinnov D-Mon. D-Command. Last edited by LDS; 10-01-2021 at 09:34 PM. |
#17
|
|||
|
|||
Re: M1 Mac Mini running Atmos Renderer 3.7.0
Really, it would be great if Avid could either make it possible to author Atmos content without DAMS (this seems to be the case with Nuendo, no?), or allowed Dolby Audio Bridge to be used in conjunction with the HD (native) playback engine.
Having to use a separate CoreAudio interface in order to be able to use hardware inserts and DSP in Pro Tools seems like a kludge. I suppose there are the send/return plugins but from memory these had some issues with delay compensation?
__________________
https://lukehoward.com/ |
#18
|
|||
|
|||
Re: M1 Mac Mini running Atmos Renderer 3.7.0
Quote:
__________________
~Will |
#19
|
|||
|
|||
Re: M1 Mac Mini running Atmos Renderer 3.7.0
Quote:
__________________
Pro Tools Ultimate 2024.3. OSX 13.6.5. Win 10. HD Native. Lynx AES16e. Lynx Aurora 16. i9-13900KF. ASRock Z690 Steel Legend. 64GB Ram. AMD Vega 64. BM Decklink. Dolby Atmos Renderer 5.2. Trinnov D-Mon. D-Command. |
#20
|
|||
|
|||
Re: M1 Mac Mini running Atmos Renderer 3.7.0
You can export ADM from Pro Tools now though right? But you still need DAPS for monitoring. Does Nuendo handle monitoring as well?
__________________
https://lukehoward.com/ |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Dolby Atmos Renderer dropping out of record | Goombot | Avid Pro Mixing General Discussion | 2 | 07-28-2021 05:44 AM |
Atmos Renderer consultant? | DaveGross | Post - Surround - Video | 12 | 07-25-2021 02:03 AM |
Atmos Renderer buffer underrun | oldskool | Post - Surround - Video | 0 | 04-08-2021 11:07 AM |
Dolby Atmos Renderer file naming | Branko | Post - Surround - Video | 6 | 03-01-2020 01:43 AM |
Atmos HT Renderer | Norad155 | Post - Surround - Video | 0 | 04-02-2019 10:24 AM |