This statement couldn’t be more accurate. I proved it with an update to a beta
of OS 10.12 on my 2012 MacBook Pro. I just created another thread on this. It
amazes me that it’s taken this long for Apple to get their act together when
building an OS.
> On Jun 28, 2016, at 5:50 AM, Kevin Reeves
This issue lands squarely in the lap of apple.
In apples finite wisdom, they are implementing protocols into their code
that start shutting down background processes to conserve power,
irregardless of whether or not it is a laptop plugged in, a desktop, etc.
In result, apps with tons of
e time scale fits what I've said here? Quite simply if I get it to a
>> >> point
>> >> when it works flawlessly again then I'm going to ignore said updates.
>> >>
>> >> If anything I've said here has sparked any further ideas or suggestions
>> >
nyone then I'm also keen to hear them.
> >>
> >> Hope this helps you in some way Rocco,
> >>
> >> Cheers,
> >>
> >> Alan,
> >> Oban, Scotland
> >>
> >> Sent from my iPhone
> >>
> >>>
m also keen to hear them.
>>
>> Hope this helps you in some way Rocco,
>>
>> Cheers,
>>
>> Alan,
>> Oban, Scotland
>>
>> Sent from my iPhone
>>
>>> On 15 Jun 2016, at 14:39, Phil Muir <i...@accessibilitytraining.co.uk>
>&g
>
>> Yup. Known bad RAM or faulty hardware components to do this kind of
>> thing
>> on Mac's.
>>
>> -----Original Message-
>> From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] On
>> Behalf
>> Of mcdiemert
>> Sent: 15 June 2016 14:
googlegroups.com] On Behalf
> Of mcdiemert
> Sent: 15 June 2016 14:04
> To: ptaccess@googlegroups.com
> Subject: Re: cpu overload messages, drop outs, and other random pro tools
> issues
>
> To add to this, I'd be curious how you're connecting your interface to the
> MBp?
> The
outs, and other random pro tools
issues
To add to this, I'd be curious how you're connecting your interface to the
MBp?
The only other time I experienced something like what you are
describing, turned out I had a bad piece of Ram in my Mac mini. Agree
with Slau here, deffinitly sounds hardware
To add to this, I'd be curious how you're connecting your interface to the MBp?
The only other time I experienced something like what you are
describing, turned out I had a bad piece of Ram in my Mac mini. Agree
with Slau here, deffinitly sounds hardware related. I believe there is
an apple test
Hi Rocco,
Sorry to hear about your troubles. For what it's worth, your subject line
implies that it's a Pro Tools issue and it certainly does affect Pro Tools but
it clearly sounds like it's a hardware/software issue with the 2014 machine and
El Capitan. You seem to have followed all of the
Hi all,
I’ve been having some strange issues with my machine and working with Pro Tools
the last few months and was hoping someone here either experienced something
similar or had suggestions for troubleshooting. All of this will take some
explanation, so please bear with me.
I have two
11 matches
Mail list logo
