Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro 1.5 stills trouble

  • 1.5 stills trouble

    Posted by Troy Murison on May 16, 2006 at 9:15 pm

    My project consists of almost 5,000 still images (jpgs). For organizational
    reasons, I have made 7 ‘sub’ timelines so I can identify what shot sequences I want to
    use in my main cut. I applied a general resize to all clips by copy/paste attributes.
    I then rendered all timelines. Now I am copying/pasting groups of clips from one
    timeline to the main (in order to keep trimming/conforming options open) which doesn’t
    require rendering. BUT, when I decide to re-resize, crop or otherwise manipulate those
    copied clips in my main cut, I get the red render line (expected) AND the clip either disappears
    (black) or previews as solid green. When I try to render those areas, the render dialog
    briefly pops up and disappears without having rendered anything (clip, black or green).
    I have seen before on previous projects and have been able to just quit/restart and the
    problem fixes itself for a while. I have tried disconnecting my firewire device (Sony
    DSR 40) as well but did not help. Also, the project is 16:9 anamorphic NTSC as were
    others when I have experienced this. One mixed stereo audio clip only in the main timeline.

    I started this project before I had access to v2.0. I now have the upgrades
    available to me but I don’t know if it’s a good idea to upgrade mid project.

    Has anyone seen this before? If so, are there any known work-arounds? Thanks in advance
    for any thoughts!

    Troy Murison
    Seattle, WA

    Dell PWS 360 workstation
    P4 3.2 HT (on)
    2GB RAM
    Nvidia Quadro NVS (4.5.0.3 driver)
    Firewire I/O only (built-in)
    WinXP Pro, SP2
    Adobe PPro 1.5, AE 6.5, Encore 1.5, Audition 1.5, PS CS
    Sony DSR40 Firewire deck

    Troy Murison replied 20 years ago 3 Members · 8 Replies
  • 8 Replies
  • Aanarav Sareen

    May 16, 2006 at 9:21 pm

    1. The green/black stills issue is a known issue with version 1.5 Premiere Pro 2.0 eliminates this issue. However, if you reduce the dimensions of the stills, it will no longer be a problem in 1.5.

    2. If you have Premiere Pro 2.0, I would install it. Remember, it doesn’t install it over 1.5, so you can have both 1.5 as well as 2.0 installed on the same system. However, before you open your project in 2.0, make a copy of it, just in case.

  • Troy Murison

    May 16, 2006 at 9:29 pm

    Thank you so much for your quick response!

    My stills aren’t that large (964 x 640) and are only about 400k each.
    I’m suprised it’s a memory thing, although I do have a TON of stills,
    but not that many (150-ish) in my main timeline.

    I will install 2.0 and continue with a copy of my project file.

    Thanks again!!!

    Troy Murison
    Seattle, WA

  • Aanarav Sareen

    May 17, 2006 at 5:56 am

    Troy,
    Install the Premiere Pro 2.0 update and open up a copy of the project in 2.0 to see if the problem exists. If not, then you are all set. If

    Aanarav Sareen
    premiere@asvideoproductions.com

  • Troy Murison

    May 17, 2006 at 3:50 pm

    Thanks, I did that last night. However, the 1.5 project is COMPLETELY unstable in
    2.0. Crashes almost immediately. So I figured I would just export a EDL from the 1.5
    project and ‘manually’ re-conform my main cut. But 1.5 won’t export a EDL from that
    project. I even tried just one clip in a new timeline as a test. No good. It just gives
    a generic ‘EDL encountered problems with the clips’ sort of error w/o any clues. 2.0 will
    export the same clips as a EDL okay. Also tried to export AAF from 1.5 but it appears
    that it MUST be trying to export the entire project and all it’s sequences instead of
    just my main sequence (judging by how long it was taking to do either it or my test
    sequence of one clip). Also very annoying that I can’t export a AAF without media
    embedded. That’s true of 2.0 too as far as I can tell. So right now, I’m kinda
    screwed. I WAS planning to either continue in 2.0 or bail to FCP if only I could get
    ANY kind a metadata out of my original project. I did also try earlier auto-save
    versions of the 1.5 project just to rule out some wierd project file corruption, but
    with the same results.

    I think I will go back to the 1.5 project and delete everything except the
    main sequence and try a AAF of that, but I’m out of good ideas after that. I guess
    there’s no reason I can’t continue to edit in 1.5 as long as I don’t try to re-resize
    or modify the clips and just finish somewhere else IF I could only get the sequence
    metadata out….

    Any ideas?

    Thanks in advance!

    -Troy Murison
    Seattle, WA

  • Labrisher

    May 17, 2006 at 5:48 pm

    https://ppro.wikia.com/wiki/FAQ#Why_are_my_stills_showing_up_as_black_or_green.3F

    Take a look at this post. I’ve tried the black video “fix” but with erratic success. I eventually reduced the size of my stills and broke up the one large project into several smaller ones (each was a distinct leg of a trip.) However, this latter suggestion may not be suitable for your needs.

    Cheers

  • Troy Murison

    May 17, 2006 at 6:04 pm

    Thanks for the link. I found out a lot about this issue last night. Breaking it
    up isn’t exactly practical for this project, but technique noted for later projects
    if I choose to do them in PPro at all.

    I can accept that there was a bug (Adobe must have know for a long time though,
    right?) but I wish there were a few more fixes available between realeases for
    this type of thing. What happened to the days of “1.5.1c”? So I can deal for now
    IF I could just get the metadata out of my project and into the new project…

    What I’m finding is frustration with not only 1.5 but 2.0 in media managment and
    exporting/moving metadata around. After all, that’s all this program or any other
    editing program does at the most basic level. But if you can’t access that data
    in ways to help you out, then my time spent to date has been mostly a waste.

    I am realizing that if I had started in 2.0 to begin with I would be a much happier
    camper and the problem that’s forcing me now to 2.0 wouldn’t have happened. But
    that wasn’t an option, so here I am. It’s just revealing other issues with PPro
    for me.

    Thanks again to all who have helped!!

    -Troy Murison
    Seattle, WA

  • Labrisher

    May 17, 2006 at 9:48 pm

    This is a complete shot in the dark, but it may be worth a try. On the ASSUMPTION that fewer sequences mean less burden on memory requirement (hence avoiding the green/black screen effect) – and I don’t know that this is the case, I might hastely add – why not create 7 appropriately labeled Bins, move your stills to their corresponding Bins, then delete the subtimelines (sequences).

    As far as I can tell, edits and effects that you may have applied to the clips in the subtimeline will remain in the master timeline after you delete the subtimeline (assuming you copied them from the subtimeline, as you say you do). The separate Bins also serves to sort your stills, and you can view their content in icon view, or in the Source window where you can edit before bringing to master timeline, as was the function of the subtimelines.

    Try it and see — BUT ON A COPY OF YOUR PROJECT, naturally. And let us know if this works.

    Cheers

  • Troy Murison

    May 17, 2006 at 10:49 pm

    Thanks for the suggestion, I’ll give it a try. It will be a little bit of a
    hastle in this project as to really see what each sequence looks like, we need
    to see it in motion as the stills were shot in sequence with the intent of being
    a intervalometer-type effect. So looking at 5 different sequence of, say, 50 stills
    for each setup and choosing the right one or combination of several to make a
    keeper is much easier if done in the timeline and already ‘pre’-sized/rendered.

    The bin idea is good though, and I’ll try it. And, you’re right, less sequences
    does help. I eliminated all but my main sequence and the opening/closing/saving
    of the project file sped-up considerably. Still didn’t help in successfully getting
    the metadata out (the AAF of just that timeline took about 2 hours to build and I
    gave up on 2.0 importing it after about 2 hours). I think I can rebuild the project
    in about 6, so what’s 4 wasted hours… I had to try it…

    Thanks again to everyone for responding!

    -Troy Murison
    Seattle, WA

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