Premiere CS6 Still Image Issues?

[Beau Leland]

Here’s a screen cap of what I’m seeing. Crazy!

[Jon Barrie]

Video dpi is 72dpi.

You might want to downsize the 300dpi. It’s possible that its simply too much information (there are limitations).

– JB 🙂

Jon Barrie
Adobe Video Solutions Consultant ANZ
Jon’s YouTube Tutorial Page
follow Jon with twitter

[Beau Leland]

I understand that video is 72dpi, but when dealing with archival images in an HD project where one needs to scale up a great deal in order to focus on a small portion of the image, isn’t it necessary to use images with much higher resolution? Correct me if I’m wrong, but I don’t think 72 would get me there, would it? I’ve long used high res images in FCP, and seldom had this issue.

[Roger Hendrick]

I can use 8 bit 300dpi TIFFs with no issues. I can also use Dynamic Linked AE projects for 16bit TIFFs and they play in the Premiere timeline fine. My images are 6480×4320 @ 300dpi 8 bit.

I tested my setups here at my desk for you.

Premiere CS6 6.0.1

Windows 7 64 – 16GB RAM
i7-2600K @ 3.40GHz (over clocked to 4.5GHz)
GeForce GTX 570 (Mercury CUDA Enabled)

OSX 10.7.4 – 14GB RAM
2x3GHZ MacPro 3.1
Radeon 5770 (Mercury Software only)

When you import a 16bit TIFF there is an error regarding an unsupported video bit depth.

What you’re describing looks like purely a display card issue. Have you tried exporting your sequence to mov and seeing what comes out? Can you get video sized stills to show up in your UI? Have you enabled/disabled the Mercury hardware setting in your Project? Do AE linked projects show up?

Roger Hendrick
The Airship Factory
http://www.airshipfactory.com
HD Video Production – Blu-ray Authoring

[Tom Prigge]

Check that your images are RGB. Open them in Photoshop, convert, and save. It’s been my experience that pix meant for print won’t show up.

[Beau Leland]

[Roger Hendrick] “When you import a 16bit TIFF there is an error regarding an unsupported video bit depth.

What you’re describing looks like purely a display card issue. Have you tried exporting your sequence to mov and seeing what comes out? Can you get video sized stills to show up in your UI? Have you enabled/disabled the Mercury hardware setting in your Project? Do AE linked projects show up?”

I did receive the bit rate warning for one image, so I went in to photoshop and changed it to 8 bit, but it still doesn’t want to work. I haven’t tried exporting an MOV, but I will give that a try and let you know.

Earlier in the thread I posted a picture of my UI. That’s what it looks like when I try to load one of these images into the viewer. My mercury engine is fully enabled with my Quadro 4000. I’ve been able to stream 13 HD streams in a multicam at real time so I would think I definitely should be able to process these images.

I also had confirmed that these images were in RGB rather than CMYK. But hey, who knows, a whole weekend has gone by. Maybe my system has had some time to think about the sadness it’s caused me, and it will behave when I get to work today.

Thanks for all of your suggestions, everyone.

[Chris Borjis]

Sounds like CMYK issue to me.

I’ve found that if you have a sequence using lots of still images, premiere
generally doesn’t “like” for them to be much larger than 4k. They should
show up, but working with them can be sluggish.

At least that was the case with CS 6. 6.01 update might be better.

[Dan Madison]

I’m having the exact same issue with PP CS6. This is quite frustrating, as I edit a lot of still image videos where I need to key-frame movement and scaling across time. I never had this issue in FCP, even with very large, hi-res image files.

In my case, I can see the image clearly while scrubbing with the play-head, but as soon as I stop, the image either disappears or becomes a scrambled mess on the screen.

Interesting point here: This problem only started to occur AFTER I installed my Quadro4000 card.

[Tamlyn Bateman]

I also couldn’t see my pictures until I selected them all and selected ‘scale to frame size’. I’m assuming you’ve done this?

[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.