[Mike Smith]

I’m taking it he no longer wants an NTSC project / NTSC output?

If he used firewire capture the footage will be (should be) unaffected and should play back normally in a native (PAL) timeline.

If it was not firewire DV capture, he or you may have to recapture the footage using the batch capture facilities, and link a project to the new files.

What version of Premiere is he using?

[Mike Smith]

Thanks Steve.

I feel that’s helpful information and advice for us here, and I’d guess for a lot of folks visiting these boards.

And it augurs well for Adobe Studio on Vista, when it eventually launches ..

[Mike Smith]

Why not manage the transfer from the Mac end – you can see your data drive from the Mac desktop and from there copy it to your networked Windows machine.

[Mike Smith]

What does the “bad frame” look like? From your description, it sounds like one field is from the outgoing shot, one from the incoming – is that right?

These single frames – did you spot these while viewing the programme – a 1-frame mix is surely invisible? Or were they only discovered on a frame-by-frame look in the edit suite?

If they don’t present a problem to viewers, why worry? Or are you saying that there is a visible “frame flash” on each cut? If there is on transfer, and there wasn’t on source, then you have a dud transfer… .

Of course in PAL land, video is usually upper field first, except for DV and spinoff, which are lower field first. Could this be related ..?

[Mike Smith]

One of your bigger problems may be budgeting. If they’re not finishing the building for two years, how many “interim versions” are you going to do before that – or are you not going to look at it until the building is finished?

I’d guess you might want a couple of early “tests” to validate process / show up any probs to you and client.

I’d also guess it will save you a whole lot of time if you resize in PPro – otherwise you really probably want a batch processing script in Photoshop or your resizing will take forever.

You could simply drop shorter lengths of stills ( a week at a time?) into timelines, set your speed acceleration and render a rescale then .. if you’se skipping lots of frames then that’s lots of resizing you don’t have to do/

And of course in two years time, you’ll maybe be delivering this on BluRay or HD DVD in high definition ….

AND you’ll be using PPro 3 on a 64 bit Vista system with bags of RAM, so a heavy stills sequence might not slow you down too much!

I’ve timelapsed successfully here with PPro. I found it necessary to edit the source footage a fair bit to keep things interesting.

[Mike Smith]

Can you not use the JVC HD100 camera to downconvert, and capture as DV ? That might give you better results faster than trying to scale in PPro.

[Mike Smith]

PAL widescreen is 16:9 with fat pixels, so your file frame size info sounds good; don’t know why QT player isn’t recognising any widescreen flag and displaying as intended.

[Mike Smith]

Isn’t it a Windows thing that non-Media Center versions of Windows (most) don’t play back MPEG 2 files unless there’s 3rd party DVD player software installed ?

[Mike Smith]

Would it be worth rescuing an old manual typewriter, filming it, then reversing b/w and messing round with the image in AE afterwards … complete with smoke smouldering out of the page ..?

[Mike Smith]

https://www.blackmagic-design.com/support/software/