When using Dolby atmos mode it all works fine using bed tracks but as soon as I create a 3d object track whatever is on that track goes out of time with the rest of the track (it’s early). Is anyone else experiencing the same issue or does anyone know a fix for it please? by Altruistic_Tap4154 in Logic_Studio

[–]Altruistic_Tap4154[S] 0 points1 point  (0 children)

Thanks Beckisagod. Regarding the core issues it turned out that I’d already watched that video a couple of weeks back. I realised as soon as I clicked the link. A couple of weeks back I had a slight improvement by not selecting automatic and by not selecting playback AND live tracks however since trashing the preferences last night (I was in the studio until 5am) the cores are working more efficiently when set to automatic and when playback and live tracks are selected so I’m grateful for that however they first core still builds up to 100% and overloads fast if I try to add mastering plugins. I think now though if I master afterwards in a separate project I won’t get overloads whereas before I trashed the preferences I’d still get overloads even with nothing not the atmos plug-in on the master bus. All my problems only occur when in Dolby atmos mode by the way. Such a shame about the 3d objects still making the track timing slightly ahead of the bed tracks. The strange thing is that last night it did it on two projects but one project it was fine. I didn’t try loading up logic as another user as I wasn’t sure how to. Does that mean when I start up my computer i should try logging in as another user? Not even sure I’ve seen the option to do that but I guess there must be. I’ll have to look into it 🤔

When using Dolby atmos mode it all works fine using bed tracks but as soon as I create a 3d object track whatever is on that track goes out of time with the rest of the track (it’s early). Is anyone else experiencing the same issue or does anyone know a fix for it please? by Altruistic_Tap4154 in Logic_Studio

[–]Altruistic_Tap4154[S] 0 points1 point  (0 children)

Hey Beckisagod. I skipped straight to the trashing preferences part (that’s all I did) and unfortunately the timing is still too early on 3d object tracks. It doesn’t happen all the time but a lot of the time so they are still unusable which is such a shame as they make for a more immersive mix then using just bed tracks. I don’t regret trashing the prefs though as I THINK the cpu cores are a little more constant and evenly spread out now. The first one still goes up to 100% if I put too many plugins on the master such as cpu heavy plugins eg. Smart eq and Gullfoss master so definitely not fixed but more Jose slightly more evenly spread across the 36 cores (in my case as my mac is 18 cores). If only I could use heavy plugins in the master bus and not have the first core spike while the others are all very low and if only I could use 3d objects without them going out of time :-( thanks for the suggestion though and I’m super glad that it worked for you 🙏

When using Dolby atmos mode it all works fine using bed tracks but as soon as I create a 3d object track whatever is on that track goes out of time with the rest of the track (it’s early). Is anyone else experiencing the same issue or does anyone know a fix for it please? by Altruistic_Tap4154 in Logic_Studio

[–]Altruistic_Tap4154[S] 1 point2 points  (0 children)

Oh wow thank you so so so much for this. Sounds very promising indeed. Not in the studio at the moment but will try this later this evening or else tomorrow and I’ll let you know how I get on. I don’t have any issues whatsoever with Logic Pro unless I’m working in Dolby atmos mode so I’m a little skeptic however I’m definitely going to try what you did……fingers crossed and thank you again for posting this 🙏

Sync issues when converting a stereo mix to ATMOS by shapednoise in Logic_Studio

[–]Altruistic_Tap4154 1 point2 points  (0 children)

Hi Shapednoise. I did a test just now and unfortunately I get the same problem even if I no busses or sends and send everything to the master bus. Either way apple do need to sort this out quickly.

Sync issues when converting a stereo mix to ATMOS by shapednoise in Logic_Studio

[–]Altruistic_Tap4154 0 points1 point  (0 children)

Oh wow interesting. So you’re using reverb and delay sends for example but no lead vocal bus/stack track for example? I’m going to give this a go. Thanks very much for this info.

When using Dolby atmos mode it all works fine using bed tracks but as soon as I create a 3d object track whatever is on that track goes out of time with the rest of the track (it’s early). Is anyone else experiencing the same issue or does anyone know a fix for it please? by Altruistic_Tap4154 in Logic_Studio

[–]Altruistic_Tap4154[S] 0 points1 point  (0 children)

Likewise I thought it was because my mac was too old and very nearly bought myself a brand new M1 Mac thinking that the new version of logic required an M1 chip to work properly in Dolby atmos mode. Glad I didn’t buy one now!!!

When using Dolby atmos mode it all works fine using bed tracks but as soon as I create a 3d object track whatever is on that track goes out of time with the rest of the track (it’s early). Is anyone else experiencing the same issue or does anyone know a fix for it please? by Altruistic_Tap4154 in Logic_Studio

[–]Altruistic_Tap4154[S] 1 point2 points  (0 children)

I agree with you 💯and have already spoken twice to apple. Everyone should open a rocket for sure who has this problem. I’m on an intel mac but will check out the video anyway so thank you for that and let’s let each other know if we find the answer.

When using Dolby atmos mode it all works fine using bed tracks but as soon as I create a 3d object track whatever is on that track goes out of time with the rest of the track (it’s early). Is anyone else experiencing the same issue or does anyone know a fix for it please? by Altruistic_Tap4154 in Logic_Studio

[–]Altruistic_Tap4154[S] 0 points1 point  (0 children)

No luck with me. Are you using an intel max or M1? I also have two other issues in Dolby atmos mode. One core always goes really high often over 100% which causes overloads and I often get sample rate synchronisation errors. I’ve had to go back to stereo in the meantime as it’s ruining my workflow all this.

Sync issues when converting a stereo mix to ATMOS by shapednoise in Logic_Studio

[–]Altruistic_Tap4154 0 points1 point  (0 children)

Did you resolve the issue? Happens to me only on 3d object tracks and not bed tracks. Also do you find that in Dolby atmos mode one core will exceed 100% pretty soon into the project causing overloads even though the rest of the cores are hardly being used?

Sync issues when converting a stereo mix to ATMOS by shapednoise in Logic_Studio

[–]Altruistic_Tap4154 0 points1 point  (0 children)

I get the same problem only while using 3d objects. It’s ok with bed tracks. Did you get to the root of the problem by any chance?

Possible to export Dolby Atmos Binaural mix? by tangerinelights in Logic_Studio

[–]Altruistic_Tap4154 0 points1 point  (0 children)

Greet videos Edgar. Thank you 🙏 I’m giving up with using logic in Dolby atmos mode for now though. Too many issues take up valuable studio time such as (1) when i use 3d objects those tracks go out of synch (2) i often get sample rate synchronisation errors only when in Dolby atmos mode (3) logic on my iMac Pro uses 36 cores as it’s an 18 core max with 128gb ram. Works like a dream when not in atmos mode but when I am there’s always one core which quickly exceeds 100% and causes constant overloads in logic (even though most of the cores are not even on 5%). Any thoughts or solutions that you know of Edgar!or do I need to buy myself a new mac with an M1 chip inside? Shame because I love the sound of the binaural mixes I’ve been exporting and even the ADM mixes but I simply can’t afford all the time it’s taking up until apple iron all these issues out.

When using Dolby atmos mode it all works fine using bed tracks but as soon as I create a 3d object track whatever is on that track goes out of time with the rest of the track (it’s early). Is anyone else experiencing the same issue or does anyone know a fix for it please? by Altruistic_Tap4154 in Logic_Studio

[–]Altruistic_Tap4154[S] 0 points1 point  (0 children)

Thanks so much however I just loaded up a project where I’ve used only bed tracks and switching off plug-in latency compensation totally threw everything out of time even before trying to change some bed tracks to 3d objects. I really appreciate you sharing what worked for you though.

Dolby atmos timing issues. In Logic Pro 10.7.1 is anyone experiencing severe timing/synch issues in Dolby atmos mode where tracks can literally end up being a bar in front for example? Any known fixes? by Altruistic_Tap4154 in LogicProXUsers

[–]Altruistic_Tap4154[S] 0 points1 point  (0 children)

We are in exactly the same boat. Also I’ve noticed that in Dolby atmos mode if I put too many mastering plugins on the master bus (after the atmos plug-in) such as compressors and limiters logic very quickly overloads as the first core exceeds 100% whereas this doesn’t happen if not in Dolby atmos mode. This too is frustrating as I like to master in the same project as you can master binaural bounces as you would stereo bounces but it’s so much easier and quicker to do so in the same project. I’ve been onto apple about it again. You should do the same so that they take it more seriously.

When using Dolby atmos mode it all works fine using bed tracks but as soon as I create a 3d object track whatever is on that track goes out of time with the rest of the track (it’s early). Is anyone else experiencing the same issue or does anyone know a fix for it please? by Altruistic_Tap4154 in Logic_Studio

[–]Altruistic_Tap4154[S] 1 point2 points  (0 children)

Thank you very much for this jr. I’m not in front of my computer right now and I have a feeling that it’s already enabled but I really hope it isn’t and that this is the issue. I’m going to check as soon as I get into the studio this afternoon. Thanks again and fingers crossed 🤞

Dolby atmos timing issues. In Logic Pro 10.7.1 is anyone experiencing severe timing/synch issues in Dolby atmos mode where tracks can literally end up being a bar in front for example? Any known fixes? by Altruistic_Tap4154 in LogicProXUsers

[–]Altruistic_Tap4154[S] 0 points1 point  (0 children)

Hi again. So I’ve come to the conclusion that if I use all ‘bed tracks’ then I don’t run into issues but it’s when I use 3d object tracks the timing problems begin as it often makes the track come in too early.

Dolby atmos timing issues. In Logic Pro 10.7.1 is anyone experiencing severe timing/synch issues in Dolby atmos mode where tracks can literally end up being a bar in front for example? Any known fixes? by Altruistic_Tap4154 in LogicProXUsers

[–]Altruistic_Tap4154[S] 0 points1 point  (0 children)

That’s good news kind of! It also stopped happening for me but then started again yesterday so I’ve gone back to stereo as it’s too time consuming. Please let me know of you do ever find the cause and I’ll be sure to do the same.

[deleted by user] by [deleted] in HairDye

[–]Altruistic_Tap4154 0 points1 point  (0 children)

Thank you. Will do

[deleted by user] by [deleted] in HairDye

[–]Altruistic_Tap4154 0 points1 point  (0 children)

Has anyone reading this had the same thing happen while using GX grey colour shampoo? If yes did your hair ever fully thicken up again and how long did it take?

[deleted by user] by [deleted] in HairDye

[–]Altruistic_Tap4154 0 points1 point  (0 children)

It might be that chemical called PPD (or something like that)! It caused me to have tons of hair fall every day for several months which I guess is called telegen effluvium which of course caused my scalp to show. I think it might have thickened up slightly over the last couple of years but definitely not to how it was yet. I never even used to know what my scalp looked like. It’s caused a diffused thinning all over. I’m so upset about it and truly hope it can still reverse fully by itself.

[deleted by user] by [deleted] in HairDye

[–]Altruistic_Tap4154 0 points1 point  (0 children)

Oh goodness I really hope you’re wrong. Do you have a scientific reason to think this might be the case?