John Knowles
Forum Replies Created
-
What acceleration are you using in your Project Settings? Is it OpenCL, CUDA or “Software Only”? Also, let us know what version of OS X you’re running? Some of us with MBPs have had graphics card issues lately which has affected Premiere Pro. Also, what type of footage are you cutting?
JVK
-
Hi Peter,
Thanks for replying. I haven’t upgraded to 10.10.2 yet — I didn’t see anything in the notes about graphics card fixes so I left it alone. Do you have any official word from Apple or Nvidia that this combo is a “fix” or is it just that it works right now?
I’m willing to give it a shot on my laptop and test out the combo; we’ve had playback and crashing issues at work with CUDA on our new iMacs so I’ve moved those back to OpenCL. Hesitant to upgrade an OS in the middle of a job 🙂
JVK
-
I upgraded CUDA too and was getting terrible graphics issues on my 2014 MBP. Had to dump it entirely.
It was annoying too that the CUDA version listed in the system prefs wasn’t even the latest one listed on the site. And no release notes either.
JVK
-
The plot thickens!!
So it turns out it may not be an equipment issue. Our asst. editor just discovered that the raw footage timecode does match in Premiere Pro — BEFORE he sends it to PluralEyes to sync. When it comes back from PluralEyes it has altered the TC from the mixer with this offset. Happens randomly. I’ve opened a support ticket with Red Giant for now, hopefully this was just a software issue…
JVK
-
Tero, which CUDA driver are you running? I just looked online and saw 6.5.37 was available but my system prefs pane only showed 6.5.36 previously.
If you’re fully up-to-date, can you switch to OpenCL and see if it works better?
JVK
-
I output some sample clips today (I have some 23.98 MXF footage from a C300) and compared them. 2 minutes of 23.98 footage that’s converted to 29.97 (or nested in a new sequence) times out at 2 minutes and four frames. I think you’re right though, it’s probably the drop frame settings; I’ll double-check those when I’m back in the office.
-
The only reference to pulldown in the manual is for output via SDI, to convert 23.98 to 59.94 for broadcast preview.
It says it will shoot 29.97 progressive (30p) — have you ever shot at that frame rate? How does it compare to 24p?
JVK
-
That’s awesome, thank you Todd!
Yeah I’m looking into doing in on the post side, cutting everything at 23.98 and then making a 29.97 version for broadcast from that. Do you guys use any special calculation to get the frame count exact when you deliver? The length gets screwed up when you convert from 23.98 to 29.97
JVK
-
UPDATE:
I really don’t think the HDMI hot plugging had anything to do with it. Could have been coincidence, but was more likely the fact that I was trying to play the video from the RAID in 2 different applications at same time. That’s never been a problem before, but somehow that crashed the RAID? Still very odd. In any case, would love some ideas for how to get it mounted since usual methods aren’t working. Unfortunately because it’s SCSI I don’t have another machine I can easily test the RAID with.
-
HI Oki, thanks for the reply.
I think the issue is that the image I want to place on the phone is smaller than my comp. So how do I size it correctly? Should it be distorted, so that it looks “wrong” until the Mocha corner pin data is applied?
In other words, if my comp is 1920×1080, and the replacement screen on the phone is 600×1080, I should stretch the width of the replacement screen to be 1920? So that even if it looks wrong it will corner pin correctly?
JVK