Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro JKL shuttling issue with CS6 on Mac/Decklink

  • Kevin Monahan

    April 24, 2013 at 3:09 pm

    As I said, we do have a playback offset control for Premiere Pro Next. This will solved the problem from our side.

    Kevin Monahan
    Social Support Lead
    Adobe After Effects
    Adobe Premiere Pro
    Adobe Systems, Inc.
    Follow Me on Twitter!

  • Ray Tragesser

    April 24, 2013 at 7:08 pm

    Hi Mel,

    I am running a Mac 12 core machine with a Blackmagic Extreme HD card on CS-6.x and am happy with the overall performance of Premiere with an I/O card. With that said is it perfect…no, but compared to CS-5 or CS-5.5 without the new Mercury Transmit Engine it’s 1 million times better. I just tested my JKL experience on a 23.976 sequence with a combo of ProRes and Red Epic 5K raw and it was ok, certainly far from unusable.

    If you think about what the data path is from your GPU back into the computer and out through your i/o card there is going to be some inherent processing time delay. Is it going to be the same as having a third computer monitor setup and connected via DVI…no. Thats the trade off, if you need HD-SDI playback then a price has to be paid.

    Ray

  • Olivier Prudhomme

    December 11, 2013 at 7:18 pm

    same issue here with JKL lag and Kona

  • Garrett Breit

    March 8, 2016 at 2:48 pm

    I just had the JKL problem with our new Blackmagic UltraStudio SDI devices that we purchased. After going round and round with different drivers we finally found one that works great.

    Try rolling back to Desktop Video 10.3.7 to see if this helps at all. This fixed the sluggishness and freezing issues we were having on multiple systems. We are running Windows 10 and Premiere Pro CC v9.2. Dell T7910 workstations. All have 12 core 2.5GHz Intel Xeon processors, 64GB of Ram, 512GB solid state drives and an Nvidia K2200 4GB video card.

    Ultimately it was the 10.3.7 Desktop Video driver that fixed all of our problems with the device.

Page 2 of 2

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