This content has been marked as final. Show 11 replies
Dude your talking about buying a new camera to match your editing system. The thinking should be the other way around. At least you had the smarts to wait for the trial instead of blind buying based on their advertising ("yeah that feature will come with an update" quoting a beta tester cause Adobe will not go on record about bugs that were known before release)
I don't don't like all the advise to buy a new camera when people come on the board wondering why they are having editing problems.
Batch capturing is a must. I learned with my first DVX. A hard drive can always fail and batch capturing is the smart way to go about it. Had to learn the hard way.
I've had minor issues with the M15 in CS3 as well,but more in terms of incorrect timecode, not failure to capture at all.
--"Even the adobe website say's so..."
What exactly does the Adobe website say about this and can you provide a link? I'm curious about this issue as well.
It's the third party compatibility page
just put in your product
Don't see your camera on the list. That's a pretty sad list BTW. So CS4 and CS3 support only twelve camera models? Only one Sony camera. Sony and Panasonic hate each other. That's why no P2 support with Vegas 8 (64-bit would've been awesome. I'd be editing on Vegas if they weren't only worried about Sony Camera's)
--"It's the third party compatibility page ..."
Wow, that is just *so* different from Adobe saying that Batch Capture "just doesn't work properly for CS3...and it doesn't work for CS4 either."
What are you trying to do and what is the result? What happens when you try to capture?
You do know that there is no HDV support in the trial version, yes?
Yes, I found out there is no HDV support on the trial version, which really makes it difficult to see if I want to purchase CS4.
When I batch capture it just keeps FF and RW past the in point then just skips to the next clip. I tried doing handles, a pre roll and nothing works. Maybe out of 20 logged clips one clip will capture.
The problem I've found when capturing from the M15 is that the deck does FF and REW at such high speed that it frequently overshoots the mark by as much as two minutes, and then ends up capturing about one minute off. I usually only discover this when I look at the captured clip and find it isn't at all what I said it was when I named it.
So I just take the clip offline and recapture. This usually works. Sometimes I will manually cue the deck up to about one minute before the "in" point, and this helps the deck/Premiere find the correct timecode.
Anyhow, that's my workaround. I have handles set at 150 frames and pre- and post-roll set to the same.
(But note this is for CS3, although I assume this part is the same with CS4.)
I am considering purchasing a Sony HVR-Z7U camera and I have just upgraded to the CS4 production package. Can Premier Pro read files from the Compact Flash card that comes with the camera? Or do I need to look elsewhere for a solution?
Update from Sony rep: I just got off the phone with the Sony Professional rep. and he said that the Compact Flash card has a file format of "m2t" ... whatever that is. He also said that the camera will capture video in CS3. Am I foolish to think it will also work in CS4?
I know some people with the camera so I guess the smart thing to do is get a sample file from them.
M2T does work with CS4, but it doesn't keep the time code. For me the time code is important. I'm lucky to have Final Cut Pro as well, and Sony made an import plug-in for FCP that keeps the time code and transforms the clip into a Quicktime file (a lot easier to work with). So I import clips through FCP then just import those QT clips to Premiere Pro CS4. This works out good. Sony needs to create the plugin for Premiere as well!!
From what I have been reading, m2t is very computer intensive and that I should be using CineForm's Neo Scene to convert the m2t file to an avi file which is less computing intensive. Does anyone have any thoughts about Neo Scene? (It only costs $129 so there's not much to loose).