Chris Knight
Forum Replies Created
-
Is the shakiness going up and down, or left and right?
-
In 5.5, you can just right-click a file (even in the Media Browser, where it’s a huge time-saver) to create a sequence based on its properties.
-
I would quit Premiere before doing this. I would also trash the Encoded Files folder as well. It won’t harm your project, as Premiere will just rebuild the files when needed.
The reason I suggest importing into a new project, is because it might remove an issue in the nested sequence. Sort of like when someone in Star Trek gets healthy when they’re beamed from one place to another. Odd, but effective.
-
Sounds like a buggy nested sequence…when you edit Multicam in CS4, it has to render the audio from the merged camera tracks into a single file. That is what is rendering, but something is causing it to hiccup. I never encountered this in CS4, so I never looked into it.
Try importing the sequences into a new project and try again – this should purge the preview files, and hopefully you’ll be good to go.
-
I do this often, and it’s not hard at all. As long as the media follows the project file (which you should also be copying back and forth), you’ll be fine. You may have to relink media every time you jump from laptop to desktop, but if you have decent file management skills, this process should be painless.
-
[Tom Durham] “> When I select a timeline preset for DSLR, it says the codec is MPEG I-frame. Is that the “editing” version of H264?
If memory serves, it’s MPEG-2, and these files are only for preview purposes in the timeline. You can change it to other codecs if you want.
> When I throw different footage of different codecs on my sequence, and then go to output, does it first render the whole thing to the sequence codec, and then over to my output codec? Or does it take the source files and bump directly over to the output codec? Seems like the latter would preserve quality better.
The latter is the default. You can also set it up to use the files generated during previewing to create the output file. Not necessary for most things.
> Finally, unless I am “matching sequence settings,” no matter I do I can’t get the export settings to say anything other than 720×480 for my output size… and so it letterboxes my 1080 sequence into an SD file.”
Pick a format, pick a preset, then modify the settings to suit your needs. You can visually preview the AR results with the two tabs on the left side of the export window. Save as a new preset if you think you’ll be making the same modifications over and over.
-
You can access P2 mxf files individually, by using the Media Browser. It’s a much better solution (for most things) than importing entire P2 folders.
After you’ve created the new sequence, and it looks squished, did you then go to the file in the project window, and interpret the footage to a different AR (1.5)?
Are you importing these files from their original P2 folders (copied staight from the P2 media), or did you log and transfer via FCP?
-
Where are you running into the error? Have you tried opening Media Encoder, and importing just one sequence from the project?
-
Interpreting the footage to 1.5 should do the trick. You can always drop the clip onto the NEW ITEM icon in the project bin, and it will conform the timeline to your clip info. However, the correct procedure would be to get the clips straight from the P2 data folders. I edit P2 all day long, and only encounter goofy AR issues when I get handed clips that were processed via FCP.
-
Honestly, the best solution is to do this when you load a project. It will stop loading at a point it can’t locate something, and you’ll be prompted to find it. Once you’ve located that first clip(in Windows 7, you can use the search box in the top right corner), it (usually) finds the rest. If you have terrible file management skills, it may keep asking you.