This content has been marked as final. Show 14 replies
Convert the end result with something like Procoder to NTSC.
Are you looking to convert the raw footage to NTSC or to edit in PAL and make an NTSC version of the final edit?
In any case, I can likely get you better results than Procoder using only freeware tools. Let me know your intentions and I'll find the best workflow for you.
Thanks for the swift response lads, ideally id like to edit in PAL and convert to NTSC late in the final edit if possible.
thanks for the help
Hi Graham --
First the required tools (they are all very small, free and easy to install)
1.) AviSynth 2.5.7
2.) dv2film plugins for AviSynth (unzip and place the files in your AviSynth 2.5/plugins folder)
3.) DebugMode FrameServer plugin for Premiere Pro (be sure that you select the actual plugins folder during install... the default choice is usually not correct)
5.) Lagarith lossless codec
1.) Edit your sequences in an interlaced PAL preset within Premiere (as normal)
2.) Export your sequence as PAL using DebugMode FrameServer (720x576, 25 fps, lower field first). Choose "signpost.avi" as the filename.
3.) Create a new text file in Notepad, save it as "pal2ntsc.avs". Enter the following into the text document:
You can also try setting Type=6 for better (but slower) framerate conversion.
4.) Open the "pal2ntsc.avs" file you created in VirtualDub.
5.) In VirtualDub, choose Video>Fast recompress
6.) In VirtualDub, go to Video>Compression and select the Lagarith lossless codec
7.) In VirtualDub, choose File>Save .avi and call the file "ntsc_lossless.avi"
8.) Open Encore, create an NTSC project and import the "ntsc_lossless.avi".
9.) Author. Burn.
Canpus Procoder 3 does it all. You will need this due to the hidden items in AVIs, which Windows Media Player requires, to stop you watching AVI files with Windows. (I have deleted Windows Media player from my PCs as a result of this)
These seem to stop Canopus PC 2 from allowing CS3 files to work, so its yet more expemnse chnaging more external software and devices.
As usual the rip off gravey train forces you to spend thousnadas to do what you can already.
(I am NOT a VISTA user)
In the past I have edited in a PAL Project. Once complete I created a NTSC Project into which I imported the PAL Project (or an avi from the PAL project). Rendered it then..
Exported to an Encore NTSC Project directly from Premiere.
Has worked fine for me.
I'll second that. I've no flippin' idea what he's talking about.
> Exported to an Encore NTSC Project directly from Premiere. Has worked fine for me.
Well, this would depend on the material, I suppose... but, in general, I find the quality to be dismal when the Adobe products perform such conversions.
Did you actually watch the output on an NTSC monitor?
Thats why doing it with Canopus is the best job.
Canopus CS2 will not encode or deal with AVI Files made in CS3...WHY????
Thats why I had to upgarde to Canopus PC 3, so I could do what I already had done before with AVI Files made with PP 1.5.
What is the technical difference between AVI Files made with CS3 and those with older versions. Windows Media player would not play them either, so I have deleted Windows Media player as a bad job. Its always stuck in 4by3 anyway.
Surely an AVI file is an AVI file, no matter how or who makes it.
Why must Canopus PC 3 be required to do PP-CS3 AVIs.
>Surely an AVI file is an AVI file, no matter how or who makes it.
An AVI file is an AVI file, but the actual contents of an AVI file can vary wildly. An app like GSpot can tell you what is inside the AVI wrapper.
I wouldn't even say that Ruud, as there can be differences in the actual file structure that cause issues. Besides Type 1 and 2, there are also metadata and other file specifics that might be required for one program or another to work properly with any given file.