[Beau Leland]

Ok, so I just got off the phone with Blackmagic, and the Decklink HD Extreme 2 is not supported in Mavericks. So there’s my problem.

Case closed.

Thanks!

Beau Leland
Editor, Oklahoma City

MacPro (5,1) 3.33GHz 6-Core
Mac OS Mavericks
Premiere Pro 7.2.1
32MB RAM
NVIDIA GeForce GTX 770 4096 MB
Decklink HD Extreme 2 Output

[Beau Leland]

Hi Peter,

I’ve looked, and here’s what I have in that folder…

“Blacklist Premiere Pro.txt” and then a folder for some FxFactory stuff. But that’s it.

I do have all of the presets for blackmagic within premiere but can’t get anything to output (except for Audio, but that’s via the system output which is set to blackmagic. I’ve tried 1080 at both 29.97 and 24p.

Thanks for your response, Peter.

Thanks!

Beau Leland
Editor, Oklahoma City

MacPro (5,1) 3.33GHz 6-Core
Mac OS Mavericks
Premiere Pro 7.2.1
32MB RAM
NVIDIA GeForce GTX 770 4096 MB
Decklink HD Extreme 2 Output

[Beau Leland]

Ok, so I’ve found a work around. By the time PE had quit working, my project had grown to be pretty large with lots and lots of sequences. I decided to duplicate my Premiere project and delete everything that I had already synced. Viola! That seemed to do the trick. Though I still think it’s a mighty stinky bug on Pluraleyes’ part.

Thanks!

Beau Leland
Editor, Oklahoma City

MacPro 3.33GHz 6-Core
Mac OS Mountain Lion
Premiere Pro 6.0.2
32MB RAM
Quadro4000 Graphics Card
Decklink HD Extreme Output

[Beau Leland]

[Ben Knight] “Beau, I was curious if you ever sorted your issues out… I’m having similar frustrations.”

Hi Ben,

While I don’t know that I’m still experiencing the same exact issues I reported in this thread, I do still experience difficulties than I would like when dealing with stills. I never really “solved” the issue, but Premiere has a way with being buggy one day, and not another. Hopefully you have some luck on your end.

Thanks!

Beau Leland
Editor, Oklahoma City

MacPro 3.33GHz 6-Core
Mac OS Mountain Lion
Premiere Pro 6.0.2
32MB RAM
Quadro4000 Graphics Card
Decklink HD Extreme Output

[Beau Leland]

Ok, so I decided to do an uninstall/reinstall, delete my preferences and create them again entirely from scratch.

Everything works like a charm. I wish that made me happy, but the fact remains that Premiere seems to have to be maintained constantly. This is the third major issue that I’ve had to resolve by uninstalling/reinstalling. Frankly that’s an extreme inconvenience, and can really kill productivity. I’m ready for Premiere to be the stable workhorse I know it can be.

Thanks again for all of your help Tom and Angelo.

Thanks!

Beau Leland
Editor, Oklahoma City

MacPro 3.33GHz 6-Core
Mac OS Mountain Lion
Premiere Pro 6.0.2
32MB RAM
Quadro4000 Graphics Card
Decklink HD Extreme Output

[Beau Leland]

Hi Tom,

Thanks for the additional advice. I had actually just cleared the media cache before I checked your post. And though overall system performance appears to be better, my playhead issue remains. I’ve checked and unchecked software only on my mercury playback engine, and the problem remains. I hadn’t tried the AJA software test, and apparently my drive is reading at about 250MB a second if I did the test correctly.

One interesting development is that I found if I advance one frame at a time using the left/right arrow keys and wait a beat, it will advance properly. But if I try to advance quickly, it has that glitch I mentioned above.

I’ve also included a video below of what my timeline looks like when the problem happens (all the time). You’ll see that the playhead just jumps right back to where it left off.

Thanks again for trying to help me troubleshoot, Tom. I’ve also posted in Adobe’s community forums. Hopefully we’ll get this figured out in one way or another.

Jumpy playhead with r3d footage

Thanks!

Beau Leland
Editor, Oklahoma City

MacPro 3.33GHz 6-Core
Mac OS Mountain Lion
Premiere Pro 6.0.2
32MB RAM
Quadro4000 Graphics Card
Decklink HD Extreme Output

[Beau Leland]

[Tom Daigon] “Set the right /Program monitor in PrP to 1/2 resolution. You should get better playback. If not try 1/4.”

Thanks Tom. I’m actually running both playback and paused resolution at 1/8th. I’ve tried 1/16th as well, but it didn’t really do any better. To clarify, this isn’t really a traditional playback issue where the system can’t really keep up. That is indeed what I experience when I crank it up to Full res playback. This is different. It’s almost like a buffer issue or something.

Here’s an example (lengthy description, but I hope portrays it accurately): If I play a sequence from say zero seconds to the ten second mark and then stop and decide I want to skip ahead to the 20 second mark, I’ll click on the 20 second mark to position the playhead there and press play via the spacebar or L key. But rather than playing from there, the playhead will want to jump back to where it left off at the 10 second mark. Likewise, it behaves the same way no matter where I want to stop and reposition the playhead. Sometimes I’m able to remedy the problem by doing a quick scrub of the point at which I want the playhead to start. It’s almost behaving like a streaming web video in which you would try to skip ahead while watching, but the video keeps kicking you back to the point where the buffer is.

The fact of the matter is that I can still edit, and once the playhead begins playing, playback is fine. It’s just a horribly annoying issue that affects my efficiency, and every editor knows how frustrating it can be when software doesn’t work at the speed of thought. An issue like this simply shouldn’t be.

And briefly, one other symptom of this problem (I’m assuming is related) is that I’m not able to navigate frame by frame accurately. If I want to adjust an edit to the accuracy of a frame (which is obviously a common practice for an editor), the program monitor isn’t responsive to frame by frame advancement using the left and right arrow keys. I can hear the audio advancing, but the visuals don’t advance. It’s similar to how one would navigate through a clip that’s been conformed from 24fps to 30fps in that certain frames would be duplicated. That isn’t the issue here, but that’s kind of how it’s behaving.

I know this is a lot to describe via text on here, and I hope I’m describing the issues thoroughly. It’s always nice when I’m searching for troubleshooting issues to come across people who are having similar issues. Hopefully this post will serve as some help to others who may be experiencing similar issues, or at least let them know they aren’t alone. Premiere Pro is a fantastic program, and 6.0.2 seems to be much more stable, but they still have some work to do to make it truly unstoppable.

Thanks!

Beau Leland
Editor, Oklahoma City

MacPro 3.33GHz 6-Core
Mac OS Mountain Lion
Premiere Pro 6.0.2
32MB RAM
Quadro4000 Graphics Card
Decklink HD Extreme Output

[Beau Leland]

I’m using a 12TB RAID 5 system from Other World Computing connected via eSata, BUT, a second look at my energy savings and I found that the drives weren’t kept from going to sleep. I unchecked that, and we’ll see if it makes a difference.

Thanks again for your help, Angelo.

Thanks!

Beau Leland
Editor, Oklahoma City

MacPro 3.33GHz 6-Core
Mac OS Mountain Lion
Premiere Pro 6.0.2
32MB RAM
Quadro4000 Graphics Card
Decklink HD Extreme Output

[Beau Leland]

Thanks for the tips, Angelo. I actually haven’t done any rendering yet, so all of my yellow bars are still there. I haven’t rendered because Adobe states that if you have yellow bars, it’s not actually necessary to render to have proper playback. Maybe that’s not the case after all.

I’m leaning toward option one. Regarding option two, I’m actually already playing at 1/8 resolution, so I don’t think that’s the issue. And option three isn’t really an option for me since I’m already a week into the cut. Plus, the whole idea of using Premiere is to capitalize on not having to transcode.

Two things though, that I want to double check. Regarding option one, I should leave the preview files at ProRes proxy, and just render out the yellow bars? And finally, would the fact that Premiere is automatically resizing my 5k footage (shot at an aspect of 2:1) to a 1080 equivalent have any impact on this situation? I’ve found that even when I “Create Sequence from Clip” my dimensions are still 1920×810 rather than 5120×2160. Is this just Premiere’s way of dealing with this footage to make it editable, or should it be giving me the actual dimensions if I tell it to?

UPDATE: I actually just tried the render method using ProRes Proxy, and the issue persists. Hmmmm. Maybe it’s just a bug. Thoughts?

Thanks again for your input!

Thanks!

Beau Leland
Editor, Oklahoma City

MacPro 3.33GHz 6-Core
Mac OS Mountain Lion
Premiere Pro 6.0.2
32MB RAM
Quadro4000 Graphics Card
Decklink HD Extreme Output

[Beau Leland]

Yeah, I’ve just about everything. The thing is, there doesn’t seem to be one specific issue that causes the bug. It seems that just about every time I work with stills in PP, I have to restart the app multiple times.