John-michael Seng-wheeler
Forum Replies Created
-
This is not standard behavior.
How are you sending the files back and forth between FCP and PP? You aren’t, by chance, importing the .mov files created by log and transfer into PP are you? I’ve never tried that but I know PP doesn’t work so well with Quicktimes with more then 2 audio channels.
-
Hey Aaron.
You shouldn’t get a Quadro.
the GTX580 (which is cheaper) is a lot faster for Premiere. Faster even then the Quadro 6000.
Save your money and get more speed….
-
How much RAM do you have?
-
Well, after you import it, you should make a sequence by dragging and dropping the file onto the new item button in the project panel. This will make a Sequence that matches the video exactly.
From there, you will be able to edit just like normal.
For export, just chose H.264 and set it to match.
Or, if you only need to render it for web, then skip Premiere entirely and just open the file in AME and Export.
-
You should always use the Media Browser to import your assets. The import function you were using before is still there from older versions, but it has been replaced by the media browser.
The import function won’t connect spanned AVCHD clips at all. P2 works, but (as you discovered) you get duplicate files.
Media Browser imports both perfectly.
-
Yes, you need to set the Codec Settings to match. That’s why you’re getting the weird scaling. It has something to do with the fact that the DNxHD codecs are being used through quicktime.
What’s happening to your currently is that PP is passing a correctly sized video to Quicktime, which is encoding it at 1080 regardless of the incoming signal. The “Codec Settings” button brings up a quicktime dialog box where you can tell quicktime what your want.
Basically, you need to tell both quicktime and Premiere Pro what you want separately, cause they don’t talk to each other.
-
Animation (as it’s name implies) is not meant for video, which could be the source problem you’re having.
Try Uncompressed or AVID 1×1, (which you’ll probably need to download from avid, it installs with the DNxHD quicktime codecs)
-
There is just such a utility: P2CMS, which was made by Panasonic. It does most (if not all) of what you’re looking for: It lets you view and selectively import MXFs, and perhaps rename them too.
Using the Program isn’t the most straight forward… I get the feeling it was badly translated from Japanese, but it does work.
The reason that you can’t simply rename P2 MXFs is because of the complex structure.
Every time you hit record, the camera creates 7 files with the same name. So that’s bad enough.
Also, however, the name of the file is also stored in several places in the xml file.But then, the moment you hit 4GB, you create 7 more files that have a new name but are part of the same clip. And then in the xml file you get a few references to the name of these new files, AND of the first file. (and the xml of the first file gets a reference to the name of the second file)
So to rename a P2 MXF clip you’d need to rename every reference to that name, which could number into the 20s on even relatively short clips.
-
I’ve been editing on Windows using mac formatted external disks via MacDrive almost exclusively. (I just switched to using ExFAT, which is probably what you should use too if you have the choice.)
MacDrive has given me absolutely no problems, so I will reiterate what Vince said… the only thing you can’t do on windows is render ProRes.
On the other hand, your GPU options on Windows are so much better that a Win7 PP machine can and will run circles around a Mac.
-
Note that the CUDA is actually doing what it can. The GPU usage is higher in test #2 because PP is using the GPU to do the downscaling. Test one is a test of encoding only, which is mostly CPU (as is apparent from the numbers)
You should disable CUDA (edit the txt file again to make sure it’s really disabled. ) and try test #2 again.