Charles Roberts
Forum Replies Created
-
SD60P is a weird half HDV/half EDTV mode, unsupported in FCP, but easily retreivable from the tapes and then transcoded to another format after conforming, with a couple of caveats. Its meant to be used for overcranking. Makes great partial frame plate for use in compositing in shake, AE, etc.
To get it into FCP, you need to
1) Google “FireWireSDK” and you’ll find a free developers set of applications from the Apple site.
2) snoop around in the disk image for the SDK and you’ll find an app called DVHS-Cap. Its an interface that plugs into a firewire device and controls and gets data streams from it.
3) use it with the camera or deck and capture the segments you want. It will save them as transport streams, not .movs
4) Get MPEG Streamclip (free), and use it to convert the transport streams from DVHS-Cap into some other format you can edit with. 48060P converts into SD formats very easily (not so much upressing horizontally to 16×9 for using with HD).
If you’re overcranking to get slow-mo, make sure you keep the frame rate in MPEG Streamclip at 60, then afterwards, open the quicktime movie in CinemaTools and conform it to 29.97 or 23.98, whichever you need.
It only seems like a long process the first time you do it. Its quite fast once you get the hang of it.
-
in most cases, with the exception of semi-rare ‘stream errors’, you can avoid this whole capture break annoyance simply by putting generous head and tail on each shot, and then logging and batch capturing from tape with generous handles. FCP and the br50u deck are totally fine with TC capture, but they are lousy with day/pause logging. The br50u plays very happily with FCP for DV25, HDV 720, even the 60P stuff in DVHSCapture. FCP even loves the RS422 controller through Decklink. Don’t stop anywhere near a camera pause on a tape when attempting to capture and your captures will generally be flawless. Don’t log and capture and eventually you’ll bawl like a baby, which is pretty much the case even if you aren’t working with JVC gear.
-
if it didn’t work well, then it wouldn’t work well for anyone, and it obviously is. When you put a fresh system disk in and re-installed, did you just re-install FCP and Studio or FCP and all the drivers for all those devices? When I said Mac OS and FCP, I meant check your system running only the base software with no third party anything. That’s the only thing apparently that you have going that most people don’t, the Kona, the Atto, etc.
Also, you were monitoring that hdv how? Out to DCDP or through Kona? If Kona, then maybe you haven’t chosen the right output profile in Video Output.
Good luck
-
yeah you’re within spec alright. And that probably only means one thing: software problem. The very next thing I’d test is get another drive for 50 bucks, switch it out with your present boot disk, install a fresh OS and FCP install and test it with no other software installed. If the problem is still around, (which is not gonna happen) then its a basic CPU hardware problem that Applecare should fix. If its gone, then I’d be looking at all that third party stuff on your system (just seeing Atto makes me wince when I think of the clusterf$%k SCSI card drivers have caused in Mac OS version over the past ten years. That’s the test I’d do. Then you can switch your original boot disk back in and decide how you want to deal with what you would now know is the problem. That’s all I got for ya man
-
if your 720P30 footage is sticking and skipping in your Viewer and Canvas then you’ve got something else going on. If your machine meets spec and you have plenty of RAM and not many apps running and you have lots of dedicated fast disks with plenty of free space on them, then other than OS problems, you shouldn’t be seeing spotty playback. Does any of the above not apply? If anything rings a bell, then that’s the first place I’d look.
Do the breakups always happen in the same place or is it random? IOW, is the captured media file damaged itself or is performance in playback causing the dropouts. I did have a client who had a lot of trouble exporting from an HDV sequence (sony 1080i) and her exports were giving her tons of spotty playback like you describe. She was exporting to QuickTime Conversion and doing her codec choice in that dialog box. Well, I put a stop to that immediately, had her export to File>Export>QuickTime Movie (self-contained but no recompression), then had her take that exported movie and run it through Compressor with the same settings and her problems vanished. In theory nothing should be different. But the difference between theory and reality is that in theory there no difference between the two, but in reality there is, ya dig?
Give it a try if you haven’t already.
Personally I don’t have much truck with all this web codec and low bandwidth business, so someone else will have to chime in if that don’t get it.
-
It has some wonkiness in the capture process that you have to prepare for before you capture, but other than that I’ve had no problems editing JVC at 24P natively. Make sure you put plenty of head and tail on every shot and then really log and capture rather than capture now and your problems will be rare if any. And take REALLY good care of your tapes as you transport them!
-
I hadn’t had a chance to test this with a 250. That’s so great…
-
24P from the HD250 is just like 24P from the HD100 and is supported. Its the 60P, either in 480P mode on the HD100 or 720P mode in the Hd200 or HD250 that isn’t supported, unless you jam it out through DVHSCap and MPEG StreamClip.
-
Actually, would that it were that easy, but Batch List imports don’t tag frame rates unless they are in the batch list columns, and even if they are included there, they are overridden by unchecking logged clip settings in Batch Capture. Changing Easy Setups and for that matter Audio Video Settings prior to importing a Batch List has no effect on the clips imported by the Batch List. The only thing it changes is the erroneous frame rate displayed in the Batch List menu item. Seriously, try it and you’ll see. One of the coolest things about Batch Lists is that its NOT limited to any codec or frame rate. It only requires name reel and timecodes.
If you’re skeptical, try the procedure earlier in the thread and you’ll see. In any event, FCP should not (and indeed does not) operate this way with a Batch List under any other codec, including DVCPRO HD. And for the record, tagged frame or not, 720P24 only has 23.976 TC. There are no extra TC frame numbers to reference under 29.97 or 30 or 60 settings.
-
I have a feeling your issue is not the same, unless you are only getting a single frame capture. The reason the master clip’s tc is changing in my issue is because after only capturing one frame of the logged clip, FCP stops capturing and seals up the media file, thus changing the media end from from its logged setting to what it ended up from a one frame capture. Problem of course is that that means a master clip gets changed without my consent!
I can tell its an FCP action too, because undo takes it back to offline clip with the original Media End tc value.
And I don’t have this problem EXCEPT with Batch lists, meaning the 720P part isn’t likely the issue, though I can’t honestly say what is. good luck with the D5 thang, Adcock is on the case, it’ll sort out.