Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro most buggy update ever: cc2014

  • most buggy update ever: cc2014

    Posted by Michel Gallone on October 5, 2014 at 8:00 am

    I need to complain about the June cc 2014 update . I started experiencing many crashes in premiere and ae. I read many treads about others in big problems too.

    Bottom line adobe must take much more care and not release updates when they are not ready. The features benefits are totally useless when the apps are so unstable

    I am actually looking at ways of asking for a refund for the l last 4 months.

    I will be forever anxious when updating from now on.

    Michel Gallone
    Sowatt Music sàrl
    Music Post and Shooting
    https://sowattmusic.com

    Larry Asbell replied 11 years, 7 months ago 6 Members · 6 Replies
  • 6 Replies
  • Steve Connor

    October 5, 2014 at 9:13 am

    What triggers these crashes? Are you Mac or PC? Is there any particular footage that crashes it?

  • Jim

    October 5, 2014 at 11:41 am

    I have to agree w/ Michel. I had all sorts of problems w/ 2014’s Dynamic Link AE to PPRo. Ultimately, Adobe support told me they had a problem w/ memory leak, and they were working on it. So I went back to CC (no issues there). Still waiting on fix. 2014 looks really good on paper, but at present it is useless to me.

    Cheers,
    Jim
    iMac, late 2013,
    10.95, 32GB RAM, 4GB VRAm,
    media on RAID

  • Michel Gallone

    October 5, 2014 at 12:52 pm

    It is mac os 10.8

    The issue has been identified both by users and by Adobe as been related to authorisations and also to preferences moving from cc to cc2014.

    The main solutions are:
    1. In (root HD)/Library/Application Support/Adobe/commun/Plug-Ins: Duplicate your 7.0 folder and rename it 8.0
    2. In your main HD info page (apple i) add your main user name and make it read write and apply to enclosed.
    3.The adobe team also did something in a remote session where they renamed some adobe files that i do not recall.

    I am still testing to see if it cured the issue

    Michel Gallone
    Sowatt Music sàrl
    Music Post and Shooting
    https://sowattmusic.com

  • Al Bergstein

    October 5, 2014 at 3:11 pm

    Interesting… I just did a large batch of duplicated short (3 to 10 minute) ‘films’ (really audio blogs with animated titles that all needed rendering) and sent them off to AME for rendering out to H.264 Vimeo. While it had to run overnight, it executed with no problems (which has not been true of previous AME batch jobs in earlier versions). I guess I’ve been luckier than most?

    Just for clarity, this is what my setup is:
    iMac 27″ 2013 model, 16GBs RAM, OSX 10.9.4
    Project and media all on OWC RAID 5 Striped with 400GB free at this point. Drive is eSata plugged into a TB converter box.
    Rendered out to esata single 1 TB drive, also chained into the TB port converter, and then both TB into individual TB ports on the iMac.

    I run the latest version of Pr (which I can’t remember right now). But it seems to be working fine here. Perhaps it’s been updated and fixed?

    Al

  • Kevin Monahan

    October 6, 2014 at 3:21 pm

    Hi Al,
    We had an update this morning. A lot of issues other people had is related to updating OS X 10.9.x.

    Thanks,
    Kevin

    Kevin Monahan
    Support Product Manager—DVA
    Adobe After Effects
    Adobe Premiere Pro
    Adobe
    Follow Me on Twitter!

  • Larry Asbell

    October 6, 2014 at 4:42 pm

    You “buried the lead” as they say. It looks like the update up this morning is the one with the IBC announced new features.

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