Skip to main content
Participating Frequently
January 31, 2018
Question

Quadro K6000

  • January 31, 2018
  • 1 reply
  • 1739 views

Hi there,

My boss is looking to get me a Quadro to see if it'll alleviate a playback error I am experiencing in Premiere Pro (which I've posted here but was unable to get solved)

I have checked out the compatible cards for Premiere and see that the K6000 is supported - but when I go to Amazon or eBay and search for one I get so many hits and they all have slight variations in the name.

Can someone here give me a link to a solid Quadro K6000 that is compatible with Premiere Pro (latest CC version)

Bonus: Is the M6000 a higher end spec?

[Moderator note: moved to best forum.]

    This topic has been closed for replies.

    1 reply

    R Neil Haugen
    Legend
    January 31, 2018

    Three things would be nice to know ...

    1) what was the error you've been getting & couldn't solve?

    2) what's the hardware for the rest of the computer ... OS/CPU/RAM/GPU/vRAM, number/type of drives?

    3) the version of PrPro in number-dot-number format plus the media and effects you typically work with.

    Neil

    Everyone's mileage always varies ...
    Participating Frequently
    January 31, 2018

    My problem was outlined in an earlier post if you can search my post history. In a (big) nutshell, about 30% of the time when I pause playback my play head will be 1 frame ahead of where it is supposed to be -- then after a second or so it'll "hop" back one frame without my touching anything so that it's in the right place.

    You can see the effect here:

    Frame Hopping Back By 1 - YouTube

    If you pause at 16 seconds and check the timecode above the smiley face (this is the timecode that the client burned into the media) you can see it is as 01:04:05:22. Then look at the timecode in the little box on the left of the timeline and you can see it is at 01:04:05:21. That's the one frame difference. Then press play again and at 18 seconds  you'll see the media "hop" back 1 frame so that it is at 01:04:05:21 - the same as the little box.

    In the video, I am NOT scrubbing backwards one frame. I don't touch anything after pausing playback.

    I didn't demonstrate this in the video, but I can often go back 2-3 seconds, hit play and pause the media at the same point and there will not be a frame difference. So this isn't my media being out of sync. I've had this problem for years across two machines. There is no rhyme or reason I can discern that causes this. Sometimes I can go 5 minutes without incident, sometimes every time I pause for 5 minutes there is an incident of this.

    The film I am working on right now the media is an MP4. It's 317 MB. 1920x1080. 23.976.

    To make the timeline, after importing I right click and choose "new sequence from clip"

    My PC specs are:

    -  Windows 10 64Bit

    -  Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz (8 CPUs), ~4.0GHz

    -  G.SKILL Ripjaws 4 Series 16GB (2 x 8GB) 288-Pin DDR4 SDRAM DDR4 3000 (PC4 24000) Intel X99 Platform Extreme Performance     Memory Model F4-3000C15D-16GRBB

    -  NVIDIA GeForce GTX 1080

    - VRAM 8192MB

    - 1TB Solid State Drive.

    I just updated Premiere Pro through CC this or last week - so it's the latest. In my ABOUT PREMIERE PRO tab it reads: "Version 12.0.1 (build 69)

    I get sent my films as mp4 / h264. They vary in size, 250-400mb typically split.

    I don't use effects. I just playback the media and pause when dialogue starts / stops / the frame a scene changes (so you can imagine why the hopping effect is driving me crazy)

    I was looking into getting a Nvidea Quadro K6000, just trying to see if it is compatible with my mobo (ASUS Z170-A)

    Legend
    January 31, 2018

    I would not normally recommend this route, especially as the K6000 is a much older GPU that's based on the GTX 600 series technology.

    And I think that your issue might have been caused in part by using a GPU that's overmatched to your system's CPU: Most workflows use the CPU quite heavily, and it turned out that your CPU could not quite match the GPU in performance. Remember, in CUDA applications, a GPU that's overqualified relative to the CPU may actually cause more harm than good.