If you are enjoying this content, we would LOVE your LIKE and SUBSCRIBE to help us reach more people interested in immersive audio!!! Posting new videos weekly! Thank you!!!
Thanks so much for watching!!! I use the external Dolby Renderer for two main reasons: first, its extended monitoring capabilities (studio is 9.1.4), and second more fold down - re-rendering options.
All I see is the sample rate issues all systems have between System and DAW/APP rates..... I never, ever use the system output though the same Audio I/O thats music apps access..... This happened even way back with Protools and system access... The amount of studios I installed systems in from D24 , through to HDX ect, all was exactly on par with issues not even running Digi hardware,,, Maybe im wrong, but Im still running a Apogee Ensemble... (2 actually) , with logic, PT's ect... And anytime im using those dedicated audio apps, they have FULL Control over the hardware... My own setup has my Mac "System" audio seperate, set to Digital ... I have a Optical to COAX SPDIF convertor, so I done lose the options of both the ADAT i/o on the units... Theres an SRC option.... So no matter what ever the "Audio App" SR settings, it doesnt fight with system settings.... Sure... Is this the issue ? Who knows? Bad code, whether Apogee's implementation., or Dolby's.. TLDR ? Keep System output separated to the IO direct driver access, as Ive suggested.,.. Let me know... At least, I guarantee , you'll find where the issue is...
The Renderer does not follow the master clock (in my case the Symphony I/O mkII) so, sometimes--and that is the "weird" part but hey! it's software!!--when you go in to change it it "explodes!." Made it part of my workflow to be checking all my sample rates in anything that is open and haven't had any issues (thankfully!!). Thanks for watching and for your thoughtful and informative comment!!!
@@thelivingroomstudios Yeh, it wasnt so much a problem solve for your issues, Its just problematic problems ive experienced with System wide drivers accessing both System i/o and dedicated access to the same I/O.. Alas, Im still running a Mac Pro Maxed out... Thus stuck on Big Sur for the ensemble support.... Just thought those experiences can create the same issues (sample rate ones) across different apps with also system access.. Ive subbed.. so will keep on enjoying your content... Beers & Cheers from Oz.
@@thelivingroomstudios To add... Its obviously a Dolby Rendering app bug... It Should lock onto word clock/sample rate ect.... Be interesting to send them an email to see what their thoughts are...
If you are enjoying this content, we would LOVE your LIKE and SUBSCRIBE to help us reach more people interested in immersive audio!!! Posting new videos weekly! Thank you!!!
Hi, why do you use Dolby render when in logic you have the render built-in thx I I enjoy very much your videos
Thanks so much for watching!!! I use the external Dolby Renderer for two main reasons: first, its extended monitoring capabilities (studio is 9.1.4), and second more fold down - re-rendering options.
All I see is the sample rate issues all systems have between System and DAW/APP rates.....
I never, ever use the system output though the same Audio I/O thats music apps access..... This happened even way back with Protools and system access...
The amount of studios I installed systems in from D24 , through to HDX ect, all was exactly on par with issues not even running Digi hardware,,,
Maybe im wrong, but Im still running a Apogee Ensemble... (2 actually) , with logic, PT's ect... And anytime im using those dedicated audio apps, they have FULL Control over the hardware...
My own setup has my Mac "System" audio seperate, set to Digital ... I have a Optical to COAX SPDIF convertor, so I done lose the options of both the ADAT i/o on the units... Theres an SRC option.... So no matter what ever the "Audio App" SR settings, it doesnt fight with system settings.... Sure... Is this the issue ? Who knows? Bad code, whether Apogee's implementation., or Dolby's..
TLDR ?
Keep System output separated to the IO direct driver access, as Ive suggested.,.. Let me know... At least, I guarantee , you'll find where the issue is...
The Renderer does not follow the master clock (in my case the Symphony I/O mkII) so, sometimes--and that is the "weird" part but hey! it's software!!--when you go in to change it it "explodes!." Made it part of my workflow to be checking all my sample rates in anything that is open and haven't had any issues (thankfully!!). Thanks for watching and for your thoughtful and informative comment!!!
@@thelivingroomstudios Yeh, it wasnt so much a problem solve for your issues, Its just problematic problems ive experienced with System wide drivers accessing both System i/o and dedicated access to the same I/O..
Alas, Im still running a Mac Pro Maxed out... Thus stuck on Big Sur for the ensemble support....
Just thought those experiences can create the same issues (sample rate ones) across different apps with also system access..
Ive subbed.. so will keep on enjoying your content...
Beers & Cheers from Oz.
@@thelivingroomstudios To add... Its obviously a Dolby Rendering app bug... It Should lock onto word clock/sample rate ect.... Be interesting to send them an email to see what their thoughts are...
@@Rhythmattica beers & cheers it is!!! (need it with 35/95 degrees out here today!!!).
@@Rhythmattica dealing with the Renderer is like dealing with an 80s tape machine! It's a love-hate thing!!! Hahaha!!!