[Dexter Andrada]

You can use AE to make the conversion to NTSC HD to PAL HD. Maybe other cna chime on on the proper settings.

good luck

[Dexter Andrada]

Full screen playback on your single monitor without any additional icons or playback controls is not possible.

This was an old feature of Premiere 4.2 and its variants. During those days the option for full screen playback was done via your CRT monitor which is patched to a VTR deck. The audio out of the computer and the CRT monitor with full screen playback enable is connected to a VTR deck (VHS). Crude way to output to tape and very buggy.

Fast forward to today, if you want full screen you connect the firewire to your A/D Converter then attach the composite out to your monitor.

[Dexter Andrada]

Maybe it has something to do with the PAL/NTSC Setting?

Did you guys agree on the proper setting for this as well?

[Dexter Andrada]

I think is a manual process with CS3, with CS4 since the Adobe Media Encoder is a separate application, you can do batch conversion.

[Dexter Andrada]

There is a no render approach to that.

Edit your video, when completed, either put your timecode on the top most layer, and adjust as necessary. This is let us say sequence_1

Next make a new sequence_2. drag the first sequence_1 that you are previously working on. Then select sequence_1 on the timeline of sequence_2, choose speed duration. Click reverse.

That will reverse your timecode. Caveat, as well as your edited video.

Of course you can prepare reversed timecode by doing the seq within a seq trick as well.

Good luck

[Dexter Andrada]

Have you tried selecting the IN and OUT of your timeline? That is one trick that might work.

Also you can try checking the handles of the export option covers the entire timeline.

And lastly, you can try Adobe Dynamic Link to Encore. This will bring your timeline into Encore, giving you the ability to see if indeed the entire timeline is being seen properly.

good luck

[Dexter Andrada]

What gear do you have? I have seen this in low powered computers, even if they were running 64bit win7.

[Dexter Andrada]

The issues in your problem comes with the combination of your gear.

1. Windows Vista 32bit – (at boot up it can easily eat up 1.2gig of memory) I suspect you have to get the proper 64bit drivers to make it run as 64bit
2. MP4 footage – this is a beast in CPU usage. And if you pile up the layers with effects, etc. boom out of memory on playback. You will be able to play back MP4 better with 64bit OS, even if your using CS3

3. Shared USB connection – even if your running everything of a USB 2.0 drive, it would be better if your project files was in the internal drive, then have your scratch disks on another internal drive, then still have your footage in your USB 2.0 disks. So the access on the USB will be only when you playback your raw footages. But honestly that is not optimal. But maybe your situation forces you to work on that environment. Also i do hope you didn’t daisy chain them drives. Regarding the two clips you imported, i suggest just move it to the internal drive.

4. Tweaked System – did you properly configure your system? Just selecting it within premiere is not enough. Since your working with HD, your cache, temp folders, your scratch disks, your background services, etc. etc. should be properly setup. From placing it in the correct folder, to properly allocating virtual memory. This things matter in a limited 32bit environment.

These are the concerns on your hardware, that i hope if you had the time, you will give it the necessary adjustment.

Now on to your problem. Here are options that you can use to solve your issues.

1. Open new project, import your existing project. Then import one sequence at a time, if succesful, then save this project as PROJECT_SEQUENCE1. Then move on to making a new project. Do the same approach. If successful, save as PROJECT_SEQUENCE2. Do this for all 17sequences. This will eat up approximately 2-3 hrs.

2. Hunt for the problematic clip/s – Assuming you are able to open your project, offline all your files then manually link it file by file. Also make sure to delete your media cache and other premiere generated temp files. So when you place your newly link clip, it will conform. When successful on every stage, make sure you save in a different project everytime. Very time consuming, but it is important to hunt for the problematic clip/s

3. Your project file – the 5mb project file is relatively small. I would assume you are just starting or maybe on the first 20-30% of the edit workload. Usually once your at the end of your project the premiere project files would jump up to 20-30mb sizes. So if this is the case, your edits are still manageable to repeat. So its just a matter of asking your self what is more important given the time you have left on your hands.

Maybe you can convert everything to DV-AVI first before you continue editing, or maybe you can first solve your hardware problem. Your time left will dictate that.

4. Volume of sequences – having a 17 sequence project in premiere pro is a major major memory hog. If you really really wanna work in this manner, i suggest start first with the first chapter, save that as one project, then when completed, move on to chapter 2. And once you are at the end of your edit, you can combine all 17 projects into one project. Of course, when that happens, you will surely be hit with low system memory again. But at least you will be able to finish it per chapter.

You need take time out to first fix your issues prior to taking in more jobs. Lest you will have more of these problems. The guys above have chirped in the starting foundations for you. And besides, you don’t need to buy a new system. Just fix your existing one.

In the end if your project was all DV quality, there would be no issues on your workstation. And you can still work with your 32bit system. But in the HD world its a no go.

good luck