Forum Replies Created

Page 11 of 129
  • Dennis Radeke

    May 10, 2015 at 9:58 am in reply to: BBC adopts FCP X for news editing

    Dave,

    You have to be a large company and most of the options were outlined in the link.

    To recap, there are three methods of buying, Individual, Teams and Enterprise. With each, the volumes (and minimums) increase as do the options and advantages.

    Dennis

  • Dennis Radeke

    May 9, 2015 at 10:08 pm in reply to: BBC adopts FCP X for news editing

    [Bill Davis] “The CC subscription requires an internet connection.”

    Enterprise customers such as the BBC have other several options. You can find out some more details here: Creative Cloud for Enterprise

  • [Scott Witthaus] “import every friggin folder as a bin” unless I missed something”

    Most times you want to assume to bring in a folder as a bin or preserve the folder structure. You also have use of the Media Browser for different workflows.

    [Scott Witthaus] “and title tool”

    You have three title tools. Built in, Photoshop and After Effects. If you don’t like one, there are two others. That said, I agree that the workflow of the built-in title tool could use some work.

  • Dennis Radeke

    May 8, 2015 at 1:35 pm in reply to: Premiere Pro CC 2014 keeps crashing on iMac

    [Bob Pierce] “It’s an on going CUDA problem.”

    There are some issues with it and while I generally recommend upgrading to the newest release, I would say that if you have a CUDA driver that is working with your system, stay with it for a while.

  • [Shane Ross] “In all politeness, of course.”

    I think at that kind of a wage, politeness may be politely kicked to the curb.

    Also – LOVE the JJ video snippet! Perfect!

  • Dennis Radeke

    May 5, 2015 at 3:31 pm in reply to: I really must be doing something wrong.

    [Alex Udell] “isn’t factoring the number of cores present in the CPU also a contributing factor?”

    Yes, for sure. I use the analogy of the # of cores being the cylinders of the engine and the amount of RAM as how much gas is going into the engine. If you’re not getting enough gas, you don’t go very fast.

  • Dennis Radeke

    May 5, 2015 at 12:05 pm in reply to: Prayers from the Church of X

    [Bret Williams] ” Lets not forget Adobe ditched the Mac platform for Premiere for years.”

    As explained here: a partial Premiere Pro history

  • Dennis Radeke

    May 5, 2015 at 11:49 am in reply to: I really must be doing something wrong.

    [Andy Edwards] “How come Premiere and AME default to almost maximum amount of RAM in the preferences when first run?”

    They don’t. I believe it will typically default to around 70% and round up or down to the nearest gigabyte. That is the nominal and best starting point to provide best performance for both OS and applications.

    I will have to dig in my email archives to remember (again) why lowering the RAM in some cases will help performance, but I do remember that it has to do with bottle necking – as you might expect.

  • [Messab Rakadle] “I haven’t tried speedgrad. Is that in the premiere or is that a plug in?”

    It is a part of Creative Cloud and included with your membership. It is a full on color grading tool with all the trimmings like masking, adjustment layers, primary, secondary grading, etc.

    However, if you just want grain or noise, than the tools you’ve already mentioned will also get the job done and probably more easily if you don’t know about Speedgrade.

  • Dennis Radeke

    May 4, 2015 at 12:06 pm in reply to: I really must be doing something wrong.

    Make sure your media cache is on a local drive and be sure to clear/clean your media cache first. This will cause a rebuild possibly of the media cache initially, but in order to troubleshoot this isn’t a bad thing. Also, trash your preferences as a good housekeeping measure.

    How much RAM have you allocated to Adobe apps in the preferences? Some times folks put too MUCH RAM to Adobe. Rule of thumb is to have 50-75% to Adobe and when you have problems, generally, put LESS RAM to Adobe. So for 32GB, I would probably have 18-20GB allocated for Adobe. If you put it to 26-28GB, then that is definitely a part of your problem.

    Are you using 3rd party I/O hardware? are you on the latest version of Premiere Pro? Spelling Premiere Pro the right way is tantamount to making it work correctly…Okay, maybe not – it’s just my pet peeve! 😉

    Also, 4K H264 media is a true bear to decode – think about the computational complexity of a 4k frame where most of the frames are not full frames – hard for even a great new Apple Macpro to compute. You could test performance by using Consolidate and Transcode feature in project management to see if performance improves that way. I think it might.

    Hopefully, some of the above helps you out.

    Best,
    Dennis – Adobe guy

Page 11 of 129

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