Forum Replies Created

Page 10 of 19
  • Erik Naso

    July 12, 2011 at 7:20 pm in reply to: Red Giant Colorista II with CS5.5

    [alex schwindt] “I’m needing to buy a MacBook Pro in the next couple of weeks, but I really need Colorista II and Premiere Pro to play nice together”

    They play better than before but Colorista II still will kick you in the shins every once in a while.
    It works better in FCP but I’m sure it will catch up. Please let Red Giant know that you want it to work better that’s the only way things get fixed if demand is high.

    Blog https://www.eriknaso.com
    My Vimeo Page https://vimeo.com/user626030
    Follow me on Twitter @ErikNaso

  • Erik Naso

    July 12, 2011 at 5:56 pm in reply to: What is the preferred IO for Premiere Pro?

    [Miro Segura] “In my Mac system preferences I set the audio out to “Headphones (Headphone port)”

    I’ll try that. Thanks!

    Blog https://www.eriknaso.com
    My Vimeo Page https://vimeo.com/user626030
    Follow me on Twitter @ErikNaso

  • Erik Naso

    July 12, 2011 at 5:53 pm in reply to: What is the preferred IO for Premiere Pro?

    [Tim Kolb] “Now that FCP users are switching, maybe we can get the attention that Premiere Pro needs to bring third party hardware support up to the level of legacy Final Cut.”

    Amen!

    Blog https://www.eriknaso.com
    My Vimeo Page https://vimeo.com/user626030
    Follow me on Twitter @ErikNaso

  • Erik Naso

    July 12, 2011 at 5:50 pm in reply to: What is the preferred IO for Premiere Pro?

    [Tom Daigon] “Hey Kona owners. AA recently released new Kona drivers 9.0.3 and Adobe plugins 9.0.1. Make sure you are up to date for the best performance.
    https://www.aja.com/support/konaNEW/kona-3-3x.php

    That’s what I’m running. Much better but not there yet.

    Blog https://www.eriknaso.com
    My Vimeo Page https://vimeo.com/user626030
    Follow me on Twitter @ErikNaso

  • Erik Naso

    July 12, 2011 at 5:49 pm in reply to: File won’t import into FCP – crashes FCP

    Can you scrub the clip in preview? Try in and outs maybe a 1/4 of the way into the clip. Keep trying to take chunks in.

    Blog https://www.eriknaso.com
    My Vimeo Page https://vimeo.com/user626030
    Follow me on Twitter @ErikNaso

  • Erik Naso

    July 12, 2011 at 4:39 pm in reply to: What is the preferred IO for Premiere Pro?

    I found the relationship with AJA and Premiere is not as solid as with FCP7. After trying both out for just playback to a broadcast monitor it seems its not as peppy with Ppro cs5.5. Some lag when playing timeline, audio drops sometimes. Little annoying stuff. 🙂

    Blog https://www.eriknaso.com
    My Vimeo Page https://vimeo.com/user626030
    Follow me on Twitter @ErikNaso

  • Erik Naso

    July 12, 2011 at 3:19 pm in reply to: Red Giant Colorista II with CS5.5

    [alex schwindt] “So let me make sure I’m understanding this right – does Colorista II work in Premiere Pro CS5.5? Specifically on a Mac?

    I’m in a similar position as Erik in that I need to find an NLE solution in this new post-FCP world, but Colorista II is a HUGE part of my workflow. I want Premiere Pro CS5.5 to be my solution moving forward, but if Colorista II doesn’t work that’s going to be a huge problem.

    Can anyone address this???”

    Red Giant seems to not have Colorista II as a single download. Its in the Magic Bullet Suite so I had to download the trial version of the suite. That gave me version 1.0.2 of Colorista II
    I unistalled Colorista II and launched the Magic Bullet Suite installer. Now the option for Premiere Pro CS5.5 appears.
    After installing I rebooted the Mac then launched Ppro. Much better now. No more blinking previews and for the most part much more responsive. Dynamic update to AJA out is much better. I find that Colorista II works better in the Color Correction workspace.I have clip in Program and Waveform in Reference all updating adjustments in realtime.
    Tonight I will be spending a few hours doing CC so for now it looks promising.

    Blog https://www.eriknaso.com
    My Vimeo Page https://vimeo.com/user626030
    Follow me on Twitter @ErikNaso

  • Erik Naso

    July 12, 2011 at 3:07 pm in reply to: Red Giant Colorista II with CS5.5

    [Tim Kolb] “I’m not sure that expecting a 64 bit program designed and released in 2011 to read the third party hardware settings from a 32 bit program with only minor structural changes since 2007 (when Adobe was current as CS3 with no multiple sequence settings within a single project) is a realistic expectation.

    I understand that Premiere Pro loading FCP projects is hugely helpful for FCP users who have decided they need to migrate, but Adobe has had 4 drops (CS3, CS4, CS5, CS5.5) since FCP was last really structurally upgraded. (Apple did not really present the 2009 changes as a major version upgrade and most of my colleagues who used FCP didn’t think of it that way either…)

    PPro does some things differently than FCP…that’s a given.”
    I dont have unreal expectations only a thirst for knowledge, and how I can work with and get Ppro to work best for me.
    If I could change the sequence settings from the XML FCP imported project I would be good to go, but they’re grayed out. By copying the clips to a new sequence that solved the problem. If there is a easier way I’m all ears. Thanks Tim.

    Blog https://www.eriknaso.com
    My Vimeo Page https://vimeo.com/user626030
    Follow me on Twitter @ErikNaso

  • Erik Naso

    July 11, 2011 at 10:39 pm in reply to: Red Giant Colorista II with CS5.5

    I would use AE but AE has no waveform so I don’t know if my adjustments are legal. I need that.

    Blog https://www.eriknaso.com
    My Vimeo Page https://vimeo.com/user626030
    Follow me on Twitter @ErikNaso

  • Erik Naso

    July 11, 2011 at 10:38 pm in reply to: Red Giant Colorista II with CS5.5

    Thanks I will send them a email.

    Blog https://www.eriknaso.com
    My Vimeo Page https://vimeo.com/user626030
    Follow me on Twitter @ErikNaso

Page 10 of 19

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