Hello Chi! Finally the AVB protocol which is needed for my new audio interface activates turbo boost at that moment, the interface is turned on. That brought the processor temperature quite high and the Flo Tools macro did the rest. Apple and Avid are searching for a solution. My work arround for mow is a tool called Turbo Boost Switcher.
So every thing is cool again and the 100ms delay is fine. Would be great to have it fort he Plug-in watcher, too. Thanks and best! / Martin -----Original Message----- From: [email protected] <[email protected]> On Behalf Of Chi Kim Sent: Friday, February 12, 2021 11:01 PM To: [email protected] Subject: Re: Observation - midi event list The problem is it would be extremely hard to track down this kind of things because so many variables. It could be because of MacOS, VoiceOver, Keyboard Maestro, Pro Tools, AppleScripte Engine, some other processors in your computers, or even possibly hardware difference, and so on. For example, Microsoft Teams kicks the fan really high and drains the battery like crazy in some cases on Mac, and it has been a few years since literally hundreds of people have been complaining about this all over the internet. Several possible solutions have been proposed by different people, but Microsoft wasn't able to fix it despite the popular demand during Pandemic. Unfortunately I don't have a bandwidth to tackle this. 100ms delay is not bad when you using it, and it only applies when you use the monitor. I think it's a good compromise. Having said that, let me know if you find something. Chi On 2/10/2021 9:31 AM, Martin (Punky) Sopart wrote: > Hello Chi! > > So wouldn't it be better to investigate why your system and my two ones > react so different, before slowing down the macros? > > Best! / Martin >> -----Original Message----- >> From: [email protected] <[email protected]> On >> Behalf Of Chi Kim >> Sent: Wednesday, February 10, 2021 4:43 AM >> To: [email protected] >> Subject: Re: Observation - midi event list >> >> The temperature did increase, but no, nothing like above 100 degrees. It >> went from around 75 to around 85. >> >> Also fan only increased only by like -50 rpm higher, I didn't hear much >> difference. >> >> Hopefully the new build works better on your system. >> >> >> Chi >> >> >> On 2/9/2021 6:24 AM, Martin (Punky) Sopart wrote: >>> Hello Chi! >>> >>> Thanks for helping here... >>> >>> Did I get you right, that you do not have this temperature behavior on >>> your >> system? >>> Best! / Martin >>>> -----Original Message----- >>>> From: [email protected] <[email protected]> On >>>> Behalf Of Chi Kim >>>> Sent: Monday, February 8, 2021 7:12 PM >>>> To: [email protected] >>>> Subject: Re: Observation - midi event list >>>> >>>> Hi Martin, >>>> >>>> >>>> Here's the build with a 100ms delay. >>>> >>>> https://github.com/flotools/flotools/archive/master.zip >>>> >>>> It's not signed, so you need to bypass the MacOS gatekeeper. >>>> >>>> >>>> Chi >>>> >>>> >>>> On 2/8/2021 12:49 PM, Chi Kim wrote: >>>>> Hi Martin and Slau, >>>>> >>>>> >>>>> On my system, temperature rises by about 10 degrees. >>>>> >>>>> Now, the script constantly monitors the control for any change without >>>>> breathing. >>>>> >>>>> I could insert a 100ms long breath before every check. Then the >>>>> temperature rises by about 5 degrees, but you'll notice 200ms delay >>>>> before the speech output. >>>>> >>>>> Would that be acceptable? >>>>> >>>>> Also I guess we need to think about doing the same thing to other >>>>> monitors such as plugin monitor, level meter monitor, and so on. >>>>> >>>>> >>>>> Chi >>>>> >>>>> >>>>> >>>>> >>>>> On 1/19/2021 4:54 AM, Martin (Punky) Sopart wrote: >>>>>> Hello Slau! >>>>>> >>>>>> Yes, I can remember something like that when using the Plug-in >>>>>> Monitor, but not that extreme when doing nothing and watching the >> cpu >>>>>> temperature rises to 100 degrees Celsius. >>>>>> Maybe the todays faster cpus and memory or the newer versions of >>>>>> Keyboard Maestro causes that. >>>>>> >>>>>> Thanks and best! / Martin >>>>>>> -----Original Message----- >>>>>>> From: [email protected] <[email protected]> >> On >>>>>>> Behalf Of Slau Halatyn >>>>>>> Sent: Monday, January 18, 2021 10:59 PM >>>>>>> To: PTAccess List <[email protected]> >>>>>>> Subject: Re: Observation - midi event list >>>>>>> >>>>>>> Hi Martin, >>>>>>> >>>>>>> We’ve changed nothing about that feature so it has probably always >>>> been >>>>>>> the case. In fact, the same thing happens when the Plug-in Monitor >>>>>>> is >>>>>>> engaged. Flo Tools is constantly scanning for any changes and the >>>>>>> CPU starts >>>>>>> to rev up it appears. Chi’s going to look into this to see if >>>>>>> there’s anything we >>>>>>> can do to improve the behavior. >>>>>>> slau >>>>>>> >>>>>>> >>>>>>>> On Jan 18, 2021, at 12:59 AM, Martin (Punky) Sopart >>>>>>> <[email protected]> wrote: >>>>>>>> Hello all! >>>>>>>> >>>>>>>> Yesterday I came back to some midi stuff in Pro Tools and realized >>>>>>>> that my >>>>>>>> Mac starts cooling very much, when using the Flo Tools feature to >> e.g. >>>>>>>> automatically announce a notes pitch. >>>>>>>> Even in "stop mode" and doing really nothing the temperature rises >>>> and >>>>>>>> rises... >>>>>>>> Setting Flo Tools to "no report" again normalizes the behaviour. >>>>>>>> >>>>>>>> Has this always been the case? Don't think so. >>>>>>>> >>>>>>>> Current Pro Tools and Keyboard Maestro under Catalina 10.15.7. >>>>>>>> Same when using the Keyboard Maestro version before the last >> one. >>>>>>>> Doublicated on two different Mac Books Pro. >>>>>>>> >>>>>>>> Thanks and best! / Martin >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> You received this message because you are subscribed to the >> Google >>>>>>> Groups "Pro Tools Accessibility" group. >>>>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>>>> send an >>>>>>> email to [email protected]. >>>>>>>> To view this discussion on the web visit >> https://groups.google.com/d/msgid/ptaccess/00a401d6ed5f%2408c0afd0%2 >>>>>>> 41a420f70%24%40cakewalker.de. >>>>>>> >>>>>>> -- >>>>>>> You received this message because you are subscribed to the Google >>>>>>> Groups >>>>>>> "Pro Tools Accessibility" group. >>>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>>> send an >>>>>>> email to [email protected]. >>>>>>> To view this discussion on the web visit >>>>>>> https://groups.google.com/d/msgid/ptaccess/9D227B37-B3C7-4BED- >>>> A0D3- >>>>>>> B6D4185672C1%40gmail.com. >>>> -- >>>> You received this message because you are subscribed to the Google >> Groups >>>> "Pro Tools Accessibility" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an >>>> email to [email protected]. >>>> To view this discussion on the web visit >>>> >> https://groups.google.com/d/msgid/ptaccess/MN2PR05MB6046CB7E68726E >>>> 983ECA8E8ECE8F9%40MN2PR05MB6046.namprd05.prod.outlook.com. >> -- >> You received this message because you are subscribed to the Google Groups >> "Pro Tools Accessibility" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/ptaccess/MN2PR05MB6046F96AAB7CA >> 2F576799D4BCE8D9%40MN2PR05MB6046.namprd05.prod.outlook.com. -- You received this message because you are subscribed to the Google Groups "Pro Tools Accessibility" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ptaccess/MN2PR05MB6046419BC5A081322F8440B9CE8B9%40MN2PR05MB6046.namprd05.prod.outlook.com. -- You received this message because you are subscribed to the Google Groups "Pro Tools Accessibility" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ptaccess/000a01d714df%24698bef80%243ca3ce80%24%40cakewalker.de.
