-
1. Re: QT32 Server reported as "Not Responding" but working with AE 12.2.1.5 on OS X Mavericks
Szalam Jul 10, 2014 7:51 AM (in response to Nic-Coe)How does it behave with AE 13.0?
-
2. Re: QT32 Server reported as "Not Responding" but working with AE 12.2.1.5 on OS X Mavericks
Nic-Coe Jul 10, 2014 5:16 PM (in response to Szalam)Hey Szalam, I'm not using AE13 yet as we have to time our upgrades across many suites but I just did a quick test and it is doing the same, says it's "Not Responding" but seems to work. I've imported QT's and rendered .movs with both versions and all seems OK!
-
3. Re: QT32 Server reported as "Not Responding" but working with AE 12.2.1.5 on OS X Mavericks
Szalam Jul 11, 2014 7:39 AM (in response to Nic-Coe)That seems odd. Does it do that all the time with QuickTime playing or just when AE is running? What if you only have animated solids in your project and are rendering to something like a PNG sequence?
If things are working, I don't know that I would worry about it too much, but you could always look into troubleshooting QuickTime errors with After Effects Also, when upgrading OS's (versus a clean install), Macs tend to mess up permissions, so you might also look at fixing permissions problem that impedes start of Adobe applications
Again, if it's not broken, I don't know that we need to fix it...
-
4. Re: QT32 Server reported as "Not Responding" but working with AE 12.2.1.5 on OS X Mavericks
Nic-Coe Jul 13, 2014 5:28 PM (in response to Szalam)Hi Szalam, after I load AE and it makes the first call to quicktime (which I think is the Video Preview output) the Adobe QT32 Server process goes red in Activity Monitor and reports as "Not responding" but every thing works despite this. It is doing the same in both V12 and V13.
FYI I did a clean install when I updated to Mavericks but have repaired permissions anyway.
Weird huh?
-
5. Re: QT32 Server reported as "Not Responding" but working with AE 12.2.1.5 on OS X Mavericks
Szalam Jul 13, 2014 7:31 PM (in response to Nic-Coe)Nic-Coe wrote:
Weird huh?
Very. You might consider filing a bug report.