This might have been covered but did you maximize both edit and mix windows?
> On Apr 22, 2020, at 12:28 PM, Toby Davey <[email protected]> wrote: > > Hi Slau, > Again thanks for all your help. > Yep I know 8GB of RAM is low in Avid's terms for PT but for what I am doing > i.e. not making music it is probably fine until I end up with over 20 tracks! > Sorry the ‘one for’ did not mean ’14’ but one item in system dialogues for KM > applications. i should have expalined it better. > I am running the most up-to-date version of Catalina on my Mac. > Thanks for clarifying the items on your Edit window in the demo - just trying > to rule out things just in case as it sounded like your Edit window was > different to mine. > As you say the reading out of level metres is more important in the Mix > window. So happy to use my sort of work around if I need to read the levels > in the Edit window for now. > Thanks for the offer of a call to do a walk through but I think for the > moment I will save a call for another time as I suspect it might be something > related to available memory. > If I get lucky and win the Lottery and upgrade my Mac to a higher spec model > with much more RAM I will find out for sure whether it is a memory issue. > As always thanks for your kind help. > Cheers > Toby > > > > > > >> On 22 Apr 2020, at 17:21, Slau Halatyn <[email protected]> wrote: >> >> Hi Toby, >> There's a lot to cover here. Inserting comments within text below. >> On Apr 22, 2020, at 6:38 AM, Toby Davey <[email protected]> wrote: >>> >>> Hi Slau, >>> Thought it would be easier writing an email rather than a long voice >>> message in the WatsApp group. >>> One first quick question - Does Flo Tools with KM eat up a bit of memory >>> when they are running alongside PT as my MacBook Pro only has 8GB of Ram? >> >> Toby, I believe the required memory is 16 GB so 8 gB is most definitely >> under-powered as far as Avid is concerned. >> >>> I had some strange things happening last night when trying to see what was >>> going on with FT, KM and PT, I had some alerts about low memory pop up a >>> few times and I closed all programmes apart from PT, KM and EU that was >>> running in the background, did a couple of re boots of my MacBook which did >>> seem to stop the low memory alerts popping up. >>> When I did launch PT and when FT kicked in I did get an audio alerts to say >>> that ‘I needed to check that in VO utilities that the tick box had to be >>> ticked to allow VO to access programmes on my Mac’, very strange as I have >>> never unticked this tick box in VO. >> >> Not sure which operating system you're running but it was an issue under >> High Sierra that the checkbox for controlling VoiceOver with AppleScript had >> to be unchecked then checked again and then rebooted or something to that >> effect. I skipped High Sierra altogether. >> >>> I checked to see if any system alerts were running as you suggested but >>> nothing apart from one for ‘Applications running in KM. Which I don’t >>> think is actually a pop up just something that is running in the >>> background. >> >> I have no idea what you mean by 14 applications running in Keyboard Maestro. >> Keyboard Maestro doesn't run applications. If you meant 14 macros running, >> that sounds strange to me. Not sure what you're looking at. >> >>> Had another go with PT and FT in the Edit window but still could not get it >>> to work. >>> Decided to leave it for the night and sleep on it and have another go this >>> morning. >>> So this morning started again, booting up my MacBook, etc. >>> Still not able to get FT to work in the Edit window. >>> Decided to launch the FT installer again just in case something was missing >>> from the install. The install launched all OK. When Launching PT again, I >>> had a FT audio alert about the VO tick box again for allowing VO to access >>> programmes on my Mac, went into VO utilities, tick box as usual was ticked >>> to allow VO to access programmes on my Mac, decided to un tick it and then >>> re tick it just in case. >>> When I got into PT I went through the same procedure that you did in your >>> audio demo. In your demo it sounded like when you were on the level metre >>> before activating FT inspector that the level was read out automatically >>> when you were playing the track. I did not initially get any level metre >>> reading out with VO, but when I used VO and the arrow keys VO did read out >>> the levels, not sure if that was what you were doing or whether the levels >>> were being read out automatically when you were on the level metre. >> >> I was moving right then moving back. Eventually, I was just pressing VO f3 >> to read the contents of the VoiceOver cursor while focused on the level >> meter. >> >>> Stopped interacting with the track, turned the inspector on and did the >>> same as you did in your demo but still no FT read out when inspector was on >>> and pressing ‘L’. >>> So I decided to go into the Mix window to check to see if FT was reading >>> out the level metres in the Mix window and yes all seemed to be fine in the >>> Mix window like before. >>> Now this is the strange bit as when I went back into the Edit window and >>> did as before I was now able to get FT to read out the level metre readings >>> with inspector on and pressing ‘L’, etc. >>> I then decided to exit out of PT shut down my MacBook and re boot and try >>> this all again to see if wen I am in PT and first go to the Mix window and >>> then into the Edit window will FT work again. >>> Yep and surprise, surprise it did work again but only in the Edit window if >>> i go into the Mix window first and then back into the Edit window. >>> All very strange! >> >> I'll agree that it's strange since it works in both places for me. >> >>> I did notice in your demo that when you went from the bottom of the Edit >>> window and did a read to the left that you went straight from the 50 to the >>> ’track list show / hide’ button and currently in the Edit window of PT on >>> my MacBook I go from 50 and then there are buttons for ’show / hide clip >>> list’, ’show / hide docked midi editor’ and then ’show / hide track list’, >>> not sure if this has any affect on the issue. >>> Not totally sure if or how to remove those extra buttons and whether they >>> might be affecting things but might be worth me having a look. >> >> Correction: I did not go straight from the bottom right to the Track List >> Show/Hide button. I did pass the clips List and Docked MIDI Editor buttons. >> It probably happened very quickly but they're visible. They can't be hidden. >> They are always there as a method of showing and hiding the respective >> tables. >> >>> not sure if it might be a memory / processor issue but I would have not >>> thought that FT would be using up quite so much processor / memory just to >>> read out the metre levels but maybe with having KM running it is using more >>> processor and memory when performing tasks but the Mix / Edit window thing >>> as above would rule that out maybe. >> >> Flo Tools takes up virtually no processing power. Keyboard Maestro, the >> same. I don't know why you're getting CPU overload but I'd say the 8 GB of >> rAM is the first suspect. Lastly, I'd say that it's probably not worth >> worrying about using Flo Tools to check levels in the Edit window. Levels >> are something you'd normally worry about while tracking or mixing which >> you'd do in the Mix window anyway. I understand your wanting to figure it >> out for the sake of simply knowing what's going on and I'm happy to try and >> troubleshoot it in real time this afternoon if you'd like. Contact me >> directly and we'll figure out a mutually convenient time window. >> >> Cheers, >> Slau >> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "Pro Tools Accessibility" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/ptaccess/N-x6rNVjaNI/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/ptaccess/B434173C-7AC3-4794-A034-3A905F535223%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/3A6B8DD6-F34C-439A-A3E0-52542AC998C9%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/DD17E192-A75C-4576-8654-0A7767BA4995%40tznet.com.
