Re: couple of issues; Hotspots causing pt to "SWOD"

2017-10-01 Thread Steve Sparrow
Hi chuck, i’ve only upgraded my machine to high sierra the other day. hot spots worked great with pt 12 in yosemite but at this point the main thing i am finding is that i can create hot spots. But when i close the session i can not return to any hot spot when reopening the session. It’s like

Re: couple of issues; Hotspots causing pt to "SWOD"

2017-10-01 Thread CHUCK REICHEL
Hi Steve, It seems to be kind of random whether or not you half to reset the hotspots in pt 12 and el cap. Have you or anybody noticed sometimes when trying to return to a hotspot that PT locks up "busy"? Also are you able to return to a hotspot in the tracks table? This has been a real "bug"

Re: couple of issues

2017-10-01 Thread Steve Sparrow
hi chuck. yeah that’s what i have been doing. If that’s they only way, i’m fine with that. Talking about hot spots. it looks like the hot spots don’t remain when i close the session and re open. Do i really have to set the hot spots up every time i open the session. I know this was talked about

Re: couple of issues

2017-10-01 Thread CHUCK REICHEL
Hi Steve, Try setting a hotspot on the track you want to jump back to. Then just go back to that hotspot. :) HTH Chuck "God does not play dice with the universe" "Albert Einstein’ On Oct 1, 2017, at 3:11 PM, Steve Sparrow wrote: > Hey guys. i know this has been talked about at length, but

Re: couple of issues

2017-10-01 Thread Steve Sparrow
Hey guys. i know this has been talked about at length, but never really followed it closely. As we know. currently with voice over, when you close a plugin v o returns to the top of the track view. then i have to scroll through all the tracks to get back to the track i was working on. I was

Re: couple of issues

2017-10-01 Thread Steve Sparrow
flo tools is up and running again. version 8.2 of k m runs great. So far high sierra is been very good to me. My system seems very stable. my only small bug bare is the v o annoying behaviour after closing a plugin. But we know about that. It would be excellent if apple could address this at