|
Avid Pro Audio CommunityHow to Join & Post • Community Terms of Use • Help Us Help YouKnowledge Base Search • Community Search • Learn & Support |
#1
|
||||
|
||||
Atmos Production Suite: Bugs or expected behavior?
Hi folks,
I've recently begun some experiments with the Atmos Production Suite (software renderer). As far as I can tell, I'm fully up-to-date with V3.0.2 of the renderer and PT 2019.5. I'm bumping into some behaviors I didn't expect and I think it's wrong. Whether to attribute this to Dolby or Avid is another question. For now, I'm just trying to determine if this is known. The most obvious issue is that track mute doesn't appear to work when a track is assigned to an object. I do know the tracks are properly attached to objects: they show up in the Dolby monitor, pan properly and so on. If they're in the bed, mutes work. As soon as they become objects, the mute doesn't work. The second issue is that sends (reverb, fx sends, etc) don't seem to work when a track is attached to an object. Again, if it goes to the bed the audio goes to the aux sends and is picked up by aux inputs. But when the track is attached to an object the send dries right up. Does this ring any bells anywhere? |
#2
|
||||
|
||||
Re: Atmos Production Suite: Bugs or expected behavior?
Dang! Found the answer deep in a Dolby forum. The Atmos send is pre-everything, so nothing else in the track (plugs, sends, etc) is part of the chain. I can work around it, but it sure makes things more 'interesting'
|
#3
|
||||
|
||||
Re: Atmos Production Suite: Bugs or expected behavior?
To a certain extent, I can accept the Sends issue, but plugins inserted on a track that is an object is out of my understanding...
I guess that unless you have a RMU (and pay the ripoff price for it), things are not easy as they should be...
__________________
Regards, Paulo M MAC Studio MAX M1_64 GB RAM_1TB SSD_MAC OS Ventura Protools Studio 2024.3 |
#4
|
||||
|
||||
Re: Atmos Production Suite: Bugs or expected behavior?
Quote:
I'm coming up with a workflow that's starting to make some sense. For each channel, it requires one extra bus and two aux channels (details later on if anybody's interested. But some of it has to do with my notions of accurate reverb). I'm really glad the old restrictions on bus and aux counts have gone away. |
#5
|
||||
|
||||
Re: Atmos Production Suite: Bugs or expected behavior?
Hello Exponential:
Something is wrong with your setup. You can definitely use plug-ins and sends on object tracks. Seems to me like you might be putting the Dolby Atmos sends on the audio track. They're not meant to be there. Check out the Dolby templates. The intended design is to use audio tracks that route to mono auxes that have the sends there. These auxes have Pro Tools outputs that go nowhere because the send is delivering to the Renderer. In object mode, sound flows to the aux. In bed mode, sound goes to a 7.1.2 aux with a send to the first ten inputs. And, the above paragraph refers to the Send/Return mode in DAPS. See my other thread about this mode vs. Dolby Audio Bridge.
__________________
Nathaniel Reichman Producer/Re-recording Mixer - New York Nathaniel Reichman | IMDB | LinkedIn |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Dolby Atmos Production Suite renderer on another computer | nedd | Post - Surround - Video | 7 | 04-24-2019 08:11 AM |
Dolby Atmos Production Suite Installer V 2.5 | tatoflores | Post - Surround - Video | 1 | 04-21-2019 09:46 AM |
Dolby Atmos Production Suite | garnoil | Post - Surround - Video | 2 | 03-13-2019 08:34 AM |
Dolby Atmos Production Suite | subhuffer | Post - Surround - Video | 20 | 03-10-2019 06:40 AM |
Dolby Atmos Speaker Snap not working using Production Suite | jamesa5454 | Post - Surround - Video | 3 | 11-02-2017 02:54 PM |