Imac si spegne durante utilizzo di Final cut pro x 10.1.3

[digit]

Vi incollo quello che ho letto sulla consolle un attimo prima che il computer si spegnesse durante l'utilizzo di Final Cut Pro x (ultima versione).

08/10/14 12:22:00,344 Final Cut Pro[757]: *** OpenGL error 0x0506 (invalid framebuffer operation) in function "GL_CHECK_CURRENT_ERROR"
08/10/14 12:22:25,512 Final Cut Pro[757]: CoreAnimation: warning, deleted thread with uncommitted CATransaction; set CA_DEBUG_TRANSACTIONS=1 in environment to log backtraces.
08/10/14 12:22:48,000 kernel[0]: process Final Cut Pro[757] caught causing excessive wakeups. Observed wakeups rate (per sec): 1991; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 1797517
08/10/14 12:22:48,761 ReportCrash[918]: Invoking spindump for pid=757 wakeups_rate=1991 duration=23 because of excessive wakeups
08/10/14 12:22:49,251 spindump[919]: Saved wakeups_resource.spin report for Final Cut Pro version 10.1.3 (251130) to /Library/Logs/DiagnosticReports/Final Cut Pro_2014-10-08-122249_iMac-di-Apple.wakeups_resource.spin
08/10/14 12:29:46,000 bootlog[0]: BOOT_TIME 1412764186 0

Ho dovuto staccare la spina ed attendere qualche minuto prima di riaccendere l'imac.
Sottolineo che utilizzo un hdd esterno tramite tunderbolt lacie D2 per l'editing video.

[digit]

un secondo prima che si spegnesse l'imac ,sulla consolle esce scritto questo:
08/10/14 12:22:48,761 ReportCrash[918]: Invoking spindump for pid=757 wakeups_rate=1991 duration=23 because of excessive wakeups

[Hammarby]

Sembra causato dal superamento dei wakeups ammessi.
Prova ad usare solo il disco interno, dato che thunderbirds non é altro che una estensione di pci-express
su linea seriale, non mi stupirei se il disco esterno e la scheda grafica, entrambi sullo stesso pci-express, non andassero in conflitto.

[Hammarby]

Aggiungo qualche informazione,
anzitutto, per saperne di piu apri il terminale e digita
syslog | grep -i "Wake reason"

Poi sembra dalle lamentele trovate in rete che la cosa sia nata con osx 10.9.2
Infine qualcuno scrive che aggiornando il software che generava il wakeup, il problema sia sparito.
Dulcis in fundo, uno dei tanti dice che la soluzione sta nel rimettere le preferenze di risparmio energia ai valori di default.

Di piu non so.

[digit]

Ok domani proverò un po' come mi avete detto e vi faccio sapere.
Grazie!

[digit]

ho provato a digitare nel terminale syslog | grep -i "Wake reason" ma non succede nulla.
Ora ho rimesso anche il risparmio energetico come default.
L'ultima prova sarà quella di fare un prossimo lavoro direttamente dall'hard disk interno.

[digit]

Allora... : ieri ho ripristinato il risparmio energetico.
Tutto bene fino alle sera dove un attimo prima di chiudere final pro x e spegnere il computer si e' riverificato il problema,spegnendosi completamente la macchina.

Questo e' quello che e' successo qualche secondo prima:

09/10/14 19:02:56,229 Final Cut Pro[319]: An instance 0x7fe04bc1af60 of class FFAnchoredCollection was deallocated while key value observers were still registered with it. Observation info was leaked, and may even become mistakenly attached to some other object. Set a breakpoint on NSKVODeallocateBreak to stop here in the debugger. Here's the current observation info:
<NSKeyValueObservationInfo 0x60001f44d1d0> (
<NSKeyValueObservance 0x6180030dae80: Observer: 0x60800014dec0, Key path: activeVariant, Options: <New: NO, Old: NO, Prior: NO> Context: 0x608000641260, Property: 0x6180004438d0>
)
09/10/14 19:02:59,248 Final Cut Pro[319]: An instance 0x7fe035b3ee50 of class FFAnchoredCollection was deallocated while key value observers were still registered with it. Observation info was leaked, and may even become mistakenly attached to some other object. Set a breakpoint on NSKVODeallocateBreak to stop here in the debugger. Here's the current observation info:
<NSKeyValueObservationInfo 0x60001f44d1d0> (
<NSKeyValueObservance 0x6180030dae80: Observer: 0x60800014dec0, Key path: activeVariant, Options: <New: NO, Old: NO, Prior: NO> Context: 0x608000641260, Property: 0x6180004438d0>
)
09/10/14 19:03:52,683 Final Cut Pro[319]: An instance 0x7fe021718f10 of class FFAnchoredCollection was deallocated while key value observers were still registered with it. Observation info was leaked, and may even become mistakenly attached to some other object. Set a breakpoint on NSKVODeallocateBreak to stop here in the debugger. Here's the current observation info:
<NSKeyValueObservationInfo 0x60001fc52ed0> (
<NSKeyValueObservance 0x6180030dae80: Observer: 0x60800014dec0, Key path: activeVariant, Options: <New: NO, Old: NO, Prior: NO> Context: 0x608000641260, Property: 0x6180004438d0>
<NSKeyValueObservance 0x6180030dae80: Observer: 0x60800014dec0, Key path: activeVariant, Options: <New: NO, Old: NO, Prior: NO> Context: 0x608000641260, Property: 0x6180004438d0>
<NSKeyValueObservance 0x6180030dae80: Observer: 0x60800014dec0, Key path: activeVariant, Options: <New: NO, Old: NO, Prior: NO> Context: 0x608000641260, Property: 0x6180004438d0>
)
09/10/14 19:04:03,312 Final Cut Pro[319]: CoreAnimation: warning, deleted thread with uncommitted CATransaction; set CA_DEBUG_TRANSACTIONS=1 in environment to log backtraces.
09/10/14 19:04:03,710 Final Cut Pro[319]: CoreAnimation: warning, deleted thread with uncommitted CATransaction; set CA_DEBUG_TRANSACTIONS=1 in environment to log backtraces.
09/10/14 19:04:05,673 Final Cut Pro[319]: An instance 0x7fe027b29dc0 of class FFAnchoredCollection was deallocated while key value observers were still registered with it. Observation info was leaked, and may even become mistakenly attached to some other object. Set a breakpoint on NSKVODeallocateBreak to stop here in the debugger. Here's the current observation info:
<NSKeyValueObservationInfo 0x60001f44d1d0> (
<NSKeyValueObservance 0x6180030dae80: Observer: 0x60800014dec0, Key path: activeVariant, Options: <New: NO, Old: NO, Prior: NO> Context: 0x608000641260, Property: 0x6180004438d0>
)
09/10/14 19:04:06,260 Final Cut Pro[319]: CoreAnimation: warning, deleted thread with uncommitted CATransaction; set CA_DEBUG_TRANSACTIONS=1 in environment to log backtraces.
09/10/14 19:04:19,484 Final Cut Pro[319]: *** OpenGL error 0x0506 (invalid framebuffer operation) in function "GL_CHECK_CURRENT_ERROR"
09/10/14 19:04:27,882 Final Cut Pro[319]: An instance 0x7fe027c0ab60 of class FFAnchoredCollection was deallocated while key value observers were still registered with it. Observation info was leaked, and may even become mistakenly attached to some other object. Set a breakpoint on NSKVODeallocateBreak to stop here in the debugger. Here's the current observation info:
<NSKeyValueObservationInfo 0x60001f44d1d0> (
<NSKeyValueObservance 0x6180030dae80: Observer: 0x60800014dec0, Key path: activeVariant, Options: <New: NO, Old: NO, Prior: NO> Context: 0x608000641260, Property: 0x6180004438d0>
)
09/10/14 19:04:29,780 Final Cut Pro[319]: CoreAnimation: warning, deleted thread with uncommitted CATransaction; set CA_DEBUG_TRANSACTIONS=1 in environment to log backtraces.
09/10/14 19:04:29,781 Final Cut Pro[319]: CoreAnimation: warning, deleted thread with uncommitted CATransaction; set CA_DEBUG_TRANSACTIONS=1 in environment to log backtraces.
09/10/14 19:04:29,781 Final Cut Pro[319]: CoreAnimation: warning, deleted thread with uncommitted CATransaction; set CA_DEBUG_TRANSACTIONS=1 in environment to log backtraces.
09/10/14 19:04:29,783 Final Cut Pro[319]: CoreAnimation: warning, deleted thread with uncommitted CATransaction; set CA_DEBUG_TRANSACTIONS=1 in environment to log backtraces.
09/10/14 19:04:34,566 Final Cut Pro[319]: CoreAnimation: warning, deleted thread with uncommitted CATransaction; set CA_DEBUG_TRANSACTIONS=1 in environment to log backtraces.
09/10/14 19:04:47,249 Final Cut Pro[319]: An instance 0x7fe02b2f69c0 of class FFAnchoredCollection was deallocated while key value observers were still registered with it. Observation info was leaked, and may even become mistakenly attached to some other object. Set a breakpoint on NSKVODeallocateBreak to stop here in the debugger. Here's the current observation info:
<NSKeyValueObservationInfo 0x60001f44d1d0> (
<NSKeyValueObservance 0x6180030dae80: Observer: 0x60800014dec0, Key path: activeVariant, Options: <New: NO, Old: NO, Prior: NO> Context: 0x608000641260, Property: 0x6180004438d0>
)
09/10/14 19:05:00,207 Final Cut Pro[319]: An instance 0x7fe02b2ea7e0 of class FFAnchoredCollection was deallocated while key value observers were still registered with it. Observation info was leaked, and may even become mistakenly attached to some other object. Set a breakpoint on NSKVODeallocateBreak to stop here in the debugger. Here's the current observation info:
<NSKeyValueObservationInfo 0x60001f44d1d0> (
<NSKeyValueObservance 0x6180030dae80: Observer: 0x60800014dec0, Key path: activeVariant, Options: <New: NO, Old: NO, Prior: NO> Context: 0x608000641260, Property: 0x6180004438d0>
)
09/10/14 19:05:01,638 Final Cut Pro[319]: An instance 0x7fe027c4f180 of class FFAnchoredCollection was deallocated while key value observers were still registered with it. Observation info was leaked, and may even become mistakenly attached to some other object. Set a breakpoint on NSKVODeallocateBreak to stop here in the debugger. Here's the current observation info:
<NSKeyValueObservationInfo 0x60001f44d1d0> (
<NSKeyValueObservance 0x6180030dae80: Observer: 0x60800014dec0, Key path: activeVariant, Options: <New: NO, Old: NO, Prior: NO> Context: 0x608000641260, Property: 0x6180004438d0>
)
09/10/14 19:05:04,302 Final Cut Pro[319]: *** OpenGL error 0x0506 (invalid framebuffer operation) in function "GL_CHECK_CURRENT_ERROR"

Questi problemi mi succedono solo e sopratutto durante il rendering di Final cut pro x.
Io sono andato bene finche' ho aggiunto un paio di giorni fa gli ultimi effetti di FxFactory . Non so' se e' una coincidenza o meno.

[Hammarby]

L'ultimo messaggio indica un errore grave nell'uso di OpenGL, oppure dentro OpenGL.
Io ho due sospetti, il primo è software, e ti chiederei di fare un esame di coscienza e cercare di capire se hai installato qualcosa prima che iniziassero i problemi,
per esempio un aggiornamento di OSX, un nuovo driver, una nuova configurazione eccetera.
Il secondo invece è il sospetto che la scheda grafica del tuo computer non sia raffreddata a sufficienza, per cui quando mandi la macchina a fare rendering pesante
il processore grafico va in tilt.

Fai prima l'esame del software.

[digit]

Ok , farò il primo tentativo.
Il secondo, credo che non rientra nelle mie possibilità.

[BOMI]

Save volevo segnalare che più volte all'apertura di Final Cut Pro 10.5.2 si spegne il computer, un Mac Pro 2020. sapreste se qualcuno ha risolto questa problematica ? Dopo il primo spegnimento mi permette di lavorare e la libreria Final Cut è in un SSD in Pci.