Forum Replies Created

Page 17 of 51
  • Erik Lindahl

    August 20, 2010 at 7:45 pm in reply to: After Effects Crashes on start

    Cheers, on the iPhone and the creative cow forum search gave me 0 hits on “AE CS5 MacOSX 10.6.4 crash”. Google found me some random sites (including my post here!) but not my particular issue. Will check out your link, thanks!

    ————————
    Erik Lindahl
    Freecloud Post Production Services
    http://www.freecloud.se

  • Erik Lindahl

    August 20, 2010 at 6:28 pm in reply to: After Effects Crashes on start

    I’ve searched but not found this particular issue or a solution.. 🙁

    ————————
    Erik Lindahl
    Freecloud Post Production Services
    http://www.freecloud.se

  • Erik Lindahl

    August 20, 2010 at 5:19 pm in reply to: After Effects Crashes on start

    Here’s a log:

    Process: After Effects [503]
    Path: /Applications/Adobe After Effects CS5/Adobe After Effects CS5.app/Contents/MacOS/After Effects
    Identifier: com.adobe.AfterEffects
    Version: 10.0 (10.0)
    Code Type: X86-64 (Native)
    Parent Process: launchd [117]

    Date/Time: 2010-08-19 14:10:32.129 +0200
    OS Version: Mac OS X 10.6.4 (10F569)
    Report Version: 6

    Interval Since Last Report: 177320 sec
    Crashes Since Last Report: 4
    Per-App Interval Since Last Report: 37636 sec
    Per-App Crashes Since Last Report: 1
    Anonymous UUID: 2C601891-D14E-496E-8832-1A8E04976F57

    Exception Type: EXC_BAD_ACCESS (SIGABRT)
    Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
    Crashed Thread: 0 Dispatch queue: com.apple.main-thread

    Application Specific Information:
    abort() called

    Thread 0 Crashed: Dispatch queue: com.apple.main-thread
    0 libSystem.B.dylib 0x00007fff88e593d6 __kill + 10
    1 libSystem.B.dylib 0x00007fff88ef9972 abort + 83
    2 U.dylib 0x0000000102a88867 U_LoadFrameworkBundle + 695
    3 libSystem.B.dylib 0x00007fff88e6b35a _sigtramp + 26
    4 ??? 0x00007fff5fbfd690 0 + 140734799795856
    5 ...e.AfterEffectsLib.framework 0x0000000100701b8e dvacore::utility::SearchLiveHelp(std::basic_string

  • Erik Lindahl

    August 20, 2010 at 1:47 pm in reply to: After Effects Crashes on start

    Can I find that log somewhere on the system easily?

    ————————
    Erik Lindahl
    Freecloud Post Production Services
    http://www.freecloud.se

  • Erik Lindahl

    August 20, 2010 at 12:58 pm in reply to: After Effects Crashes on start

    To add to the above I run the exact same installation at home on a very similar setup (Geforce 8800 instead of Radeon-card and no Kona-card). It hasn’t had these issues..

    ————————
    Erik Lindahl
    Freecloud Post Production Services
    http://www.freecloud.se

  • Erik Lindahl

    August 13, 2010 at 10:44 am in reply to: New Mac PRO

    Well if you’re on a 4K budget exluding RAM and so forth the “base systems” you can choose really include:

    – 6-core single CPU 3.33 Ghz MacPro with the Radeon 5870 1GB card ($3,899.00)
    – 8-core dual CPU 2.44 Ghz MacPro with the Radeon 5870 1GB card ($3,699.00)

    Why go 6-core?
    – Total of 19,98 vs 19,52 GHz. You can’t really count like that but I’d say in general this machine will be faster, esp. on tasks that only utilize 1-2 cores.

    Why go 8-core?
    – Possibility of more RAM (8 slots vs 4 slots). At a minimum I’d run these systems with 8GB of RAM but recommend 16GB or more.
    – Possibility of future Dual CPU upgrades
    – Possibility the memory architecture makes these machines in-favour speed-wise.

    With both machines I’d opt for the faster GPU. This will last you longer and as soon as OpenCL-savvy apps catch on things will be A LOT faster on the 5870 vs 5770. If I had a choice though I’d probably go for the 6-core machine and bump the RAM to 8-16GB.

    What’s a bit sad with the above is that I got my 8-core 2.8GHz MacPro from 2008 for below $3,000.00 with 8GB of RAM and the GF 8800 GTX included. Sure the new systems have somewhat better performance / GHz and they also have HT and Turbo but yeah.. Price / performance development has sort of gone backwards I’d say.

    ————————
    Erik Lindahl
    Freecloud Post Production Services
    http://www.freecloud.se

  • Erik Lindahl

    August 4, 2010 at 11:42 pm in reply to: Image Stabilizer

    I’d recommend you try a few different trail-versions if you can. These types of plugins can vary a lot in quality and can also have different stregths. Some faster, some slower, some more precise and so forth.

    ————————
    Erik Lindahl
    Freecloud Post Production Services
    http://www.freecloud.se

  • Erik Lindahl

    August 4, 2010 at 11:42 pm in reply to: Image Stabilizer

    I’d recommend you try a few different trail-versions if you can. These types of plugins can vary a lot in quality and can also have different stregths. Some faster, some slower, some more precise and so forth.

    ————————
    Erik Lindahl
    Freecloud Post Production Services
    http://www.freecloud.se

  • Erik Lindahl

    August 4, 2010 at 12:32 pm in reply to: Image Stabilizer

    Magic Bullet Steady has done a good jobb for me in After Effects and Final Cut Pro but it seems NOT to have support for Premier. Looking at Redgiantsoftware’s site they state “Not Available for CS5” so might not be the best horse to bet on.

    Have a look anyhow, perhaps send them a mail asking if / when you could see it come out:

    https://www.redgiantsoftware.com/products/all/magic-bullet-steady/

    Lock & Load works great in Final Cut Pro and is fast. I thought they where planning an AE-version and thus perhaps a Premier one but seems not so.. Again, doesn’t hurt to ask them

    https://www.coremelt.com/products/lock-and-load/lock-and-load-x.html

    Going from Lock & Load’s site they compare them selves to Bolris Optical Stablaizer which seems to be available for all host-apps out there, both Mac and Windows. I personally have zero experience with it however.

    https://www.borisfx.com/units/optical_stabilizer.php

    As someone pointed out you should use Mocha for stabilization also given this is a much more time consuming way of doing things, you gain a lot of control from going that route.

    Good luck 🙂

    ————————
    Erik Lindahl
    Freecloud Post Production Services
    http://www.freecloud.se

  • Erik Lindahl

    July 29, 2010 at 1:57 pm in reply to: Premiere CS5 will kill all!

    The Mercury Playback Engine is real…it works..
    I read some weary reports the performance is slaughtered if you work with an external monitor though a video-card (i.e. Kona 3 for example). Is this still the case?

    However, as the poster if anyone that finds a solid “move to Premier CS5” would be a lovely read-up. We’re an FCP based post-house at the moment but I’m open to other options. The main question though is WHY do you want to move to Premier? What isn’t working very smoothly for you today?

    I can say from my POV it’s:

    1. Speed.
    FCP sometimes suprices in speed and sometimes feels like a dead horse. This goes from simple things like real-time editing and effects, working and visualizing or even finalizing projects more in real-time. Color-correction, film-effects such as noise and grain and titling are things FCP doesn’t always excel at.

    Speed is however more than just “look mom, I got nice effects in realtime!” – speed can be workflow as well.

    2. Workflow
    We do a lot of AfterEffects work. Sending more complex comps here via Premier should be easier. What we however don’t want to loose is our current workflow we already have. The ability to capture and lay-out to tape (asaik you don’t even have deck-control built in), the ability to work with EDL’s to and from other post-facilites when working with for example film. We also do our fair-share of tracking using Mocha or work with external sources such as 3D. How does Premier work here? What format do you natively use across the apps? Don’t give me “you can use any native format” cause you don’t edit and finnish something in RED or h264.

    From my brief tests with the above it seem the FCP XML import works decent enough given FCP has much better performance on ProRes and RED media (given this was wrapped in QT-file so I presume that’s why). This does however open up more complex AE-comps from FCP way easier for our suites. Compared to CS4 it seems Adobe has cleaned the app upp a lot and it didn’t feel sluggish as their former editing candidate. But a proper case of the editor would be very interesting to read. On thing we would lack is Apples Color but you CAN use that given some XML-trick via FCP.

    ————————
    Erik Lindahl
    Freecloud Post Production Services
    http://www.freecloud.se

Page 17 of 51

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy