[Troy Murison]

Hi Tim,

I just created a ‘offline’ file in a new PPro 2.0 project
that was set to be a NDF project and got similar problems.
I created a offline clip with a reel number and tc set to
the following:

Media Start 01:00:00:00
Media End 01:00:30:00
Media Dur 00:00:29:29

These are the immediate resulting clip values in the bin
(still in NDF project):

Media Start 01;00;03;18
Media End 01;00;33;17
Media Dur 00;00;30;00

With a DF project, the same in points were used (; indicated
that it was DF) and the clip’s points tracked fine, even after
I then changed the project’s settings to NDF. However, subsequent
newly created NDF offine files with the project set to NDF
showed the same problem.

Again, I had no media in the project, standard 48k DV 29.97 NTSC
4:3 project setting to start. Don’t know what the results would
be with captured clips from tape that have mixed format TC
as I don’t have anything lying around and it’s late.

Just to be sure I also tried a Adobe SD-SDI project setting on
one machine too with the same results.

I had given up on 1.5 with all it’s messed-up TC problems, and
to be honest the (few) tests I have done to this point in 2.0
have been mostly okay (not perfect though) but these tests have
involved conforming EDLs created in Avid and FCP, which 1.5
would totally hose-up. At least 2.0 gets that mostly right in
my limited experience. But, I must say that this is very
distrubing that these kinds of issues have not been properly
addressed. I thank you for bringing it to my attention before
I counted on it to do a offline project. I’m sure others will
chime in and I am hoping there’s a simple fix or something I’m
overlooking, but…

I guess I don’t have any answers or help for you, but know that
on my machines (I tried the same test on two) exhibit exactly the
same results. I thought(hoped?) maybe I could disprove that 2.0
was the culprit and that starting the project in 1.5 was the
problem, but I guess not…

Sorry to give you this news… Good luck,

-Troy Murison
Seattle, WA

[Troy Murison]

I have noticed the same. Thought maybe it was just my imagination.
So I just did a test with similar much slower results vs. 1.5 render
using Three Way Color Corrector effect. Can this be right?
I have also noticed rendering stills is slower as well (not to the
extent that CC is slow though) but I have not done a true test,
so that may well be my imagination.

-Troy Murison
Seattle, WA

[Troy Murison]

It seems that you have the same/similar problem I have…

I posted a couple of days ago about the green/black screen render/preview bug in 1.5
which arose from large amounts of stills and cuts in timelines. I recreated the entire
project after upgrading to 2.0. Did clean install of XP, etc. Everything was fine up
to a point. Then I started having black (only, no green) renders and previews come up
again in 2.0 but usually it will go away after fiddling with some controls in the motion
tab and forcing PPro to re-render. But sometimes not. A restart of the app will solve
this most of the time too, but it seems to me that the 1.5 bug isn’t QUITE fixed. This
doesn’t really help you, Nathan, but I understand your struggles…

A couple of folks from Adobe were here yesterday and I demonstrated this issue and some
others to them. They seemed genuinely suprised at this one and that it seems very similar
to the 1.5 issue they thought was fixed. Eliminated GFX card, RAM, HD and other hardware
related issues, it SEEMS to be down to PPro. At least at this stage of my project,
I am able to work around it.

Good luck with your project!!! And thanks to all that helped in my previous posts!

Just for the curious, my project is now up to 5500-plus still images as sources, and
I know I’m really pushing PPro to it’s limit (other systems would buckle too, I suspect)
and in general, I’m very impressed with 2.0’s handling of the size/complexity of this
edit. Just a couple of nagging things I guess…

-Troy Murison
Seattle, WA

[Troy Murison]

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

[Troy Murison]

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

[Troy Murison]

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

[Troy Murison]

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

[Troy Murison]

Rich,

Sorry for the delay- too busy and forgetful mind here….
Your post on Adobe’s site reminded me. Here’s what I found
today and posted on Adobe forums as well:

I was able to import a short list from Avid Express Pro. Here’s
what worked for me:

In Avid, I exported my bin as Avid ALE
Rename that file with a .txt extension instead of .ALE
In PPro, go to Project/Import Batch List and select the .txt file

That was it- in my case it worked. I didn’t expect it to work though
because the ALE and PPro’s requirements for formatting are different.

ALE goes like this:
Clip name, Start time, end time, Tape name, drive

PPro batch lists go like this:
Tape name, Start time, End time, Clip name

When I imported the ALE, the drive information from the ALE was placed
in the Log Note column of the PPro project window.

What I figured I would do if this did not work was to open the ALE
file using Excel, re-arrange the columns to the PPro batch order, save
it as a .txt file and then import that. I didn’t try that, and I’m
out of time, but that could be an option as well.

Good luck, I hope this helps!!!!

-Troy Murison
Flying Spot
Seattle

[Troy Murison]

Thanks for the reply.
I have will submit a request!

-Troy Murison
Flying Spot
Seattle, WA

[Troy Murison]

Steven,

This works great (copy/past attributes) until you later decide that
you want to change (globally) the brightness. My thinking WAS that
you could change one, copy it, then paste attributes. But of course
you get a duplicate of every effect that you had in the copied clip
on the clips you pasted to (ie. two brightness effects). I think
PPro needs a ‘remove attributes’ option for selected clips to avoid this.
I often run into this problem and I prefer to work w/copy & paste to
keep EDL info straight later on down the line (avoid nesting).
Unless I am missing a function or a way to work around this…

Any thoughts?

Thanks!!

-Troy Murison
Flying Spot
Seattle, WA