Eject Button for Log and Capture

Does anyone have a solution for ejecting tapes from the Log and Capture screen so the tape is ready to change when you get to the deck? This seems like a feature that would be really helpful for users using "Professional Decks". I have a BetaCamSP in one in NTSC and and one in PAL, a D-2 deck, a DNW-A45, a DigiBeta and a HVR-M35U. I use an AJA for I/O. Thanks

It's been on lots of request lists as I think it's in the Avid GUI.
But tape is dead so they're probably not going to bother. There's even been talk that Apple may (maybe even should) remove the whole log and capture interface as it's one of the oldest parts of the application and a major pain to rewrite to 64-bit. Third party apps, including the QT 7 player, can be used for tape capture.
Message was edited by: Tom Wolsky

Similar Messages

Can't get camera to play for log and capture.

Please help. I am in the middle of a huge project and I am stumped. I literally could log and capture without issue last night. Today, I can rewind and fast forward with log and capture, but when I press "PLAY" I get the spinning beach ball.
I have been using FCP for years (currently FCP 5.0). I am connected to a SONY TRV 18. I tried switching the camera out. I have restarted, trashed prefs, reinstalled FCP, tried the "Quicktime fix", and repaired permissions.
iMac G5 Mac OS X (10.4.6)

Glad it spontainiously corrected itself. If it happens again and you did not do a QT/OSX upgrade, you might try the FCP Rescue path.
Click Here, select the appropriate version of FCP Rescue (4 for FCP4.x - 5 for FCP5.x), download it, expand it and select TRASH.
This will delete your FCP preference files that might have become corrupted.
good luck.
x

Log and capture problems for HDV using FCP 5.0.1

I cant seem to get a picture in my log and capture browser when using HDV. The screen says my camera is connected, I see timecode correctly rolling in sync with my cameras timecode, I can use the controls, but no picture on the screen?
When I hit capture now, the capture screen pops up and gives a message "waiting for data from device".
we shot at 720p at 25fps, there is no capture preset for this in my version of FCP. Could this be the problem? Please help!!

Thanks for responding.
It's a mac osx 10.4.11 and a 2 ghz intel core duo. I'm using easy set up in final cut pro, but there is no option for hd fire wire basic (which apple support told me to look for). The only hd options are 1080i50, i60 and 720 p30. The other hd options are for the apple intermediate codec. When I use the easy set up for hd 1080i60, then go to log and capture, it doesn't give me the preview window to set in's out, batch capture etc. It only lets me capture straight from the camera and I have to manually stop it and start it which is a major pain. Plus the clips need to be rendered once I put them in a timeline. I've shot and edited on mini dv with final cut for nearly 7 years, but now that i've tried to upgrade and shoot hd mini dv, all of these problems have arrived in capturing. I'm starting to think my version of final cut pro (5.0.1) just doesn't work with hd, unless it's very time consuming. Any ideas?

External HD Ejects when I try and log and capture

As soon as I try to log and capture my external HD ejects. Any ideas?

Log and capture from what device?
Have you added a firewire card to the computer? If not, try it. It creates a second firewire bus and seems to solve a lot of these collisions during capture.
x

Perturbing FCP 7 Log and Capture Question

I tried to digitize some HDV footage this afternoon, in theway I’ve always done it, but now suddenly it doesn’t work. Details to follow, but first my rig:
Mac Pro (Nehalem 2009) running Snow Leopard 10.6.8, NOFIREWIRE 400 PORTS
Final Cut Studio 2 with FCP 7
Sony Z1U HDV/SD videocamera connecting to Mac Pro via i.linkcable (aka firewire); I am using this to ingest because I can’t afford a deckat the moment. I know about thewear on the heads, etc., etc.
OWC Mercury Elite-Al Pro external media drive connected tocomputer via eSATA.
Here’s the scenario (keeping in mind that I’ve done thiscountless times in the past with no problems):
I connect the Z1U to the OWC drive with a 4-pin to 6-pinstandard FW 400 cable. I do thisbecause the Mac Pro does not have any FW 400 inputs but the OWC drivedoes. So I am in effect“daisy-chaining” and perhaps this is the problem.
I turn on the camera.
I start up FCP. It tells me: “Unable tolocate the following external devices: HDV (1440 x 1080) 60i.” After hitting “check again” a fewtimes, I hit “continue.”
I load my new project, into which I want to bring all thiswonderful HDV footage of my friends’ wedding. And, as I have done so many times, I hit command-8 to bringup the log and capture window.
To my horror, it says, “Unable to initialize capturedevice. Device is not connected orthe capture preset is not setup [sic] correctly.” Etc., etc.
I have read many posts here and elsewhere on similarproblems, so let me say what I have done:
I check Easy Setup: It says HDV – 1080i60, which is what it should say.
My Audio/Video Settings are:
Sequence Preset: HDV 1080i60
Capture Preset: HDV
Device Control Preset: Sony HDV Firewire
Video Playback: None
Audio Playback: Default
So now I go to my camera. It is set to output HDV. Component says 1080i/480i. i.LINK Convert is off. Down Convert says Squeeze, but I assume that’s meaningless since thei.LINK Convert is set to off. A/V>DV Out is set to off.
None of this makes a lick of difference, as far as I cantell.
I shut off the camera and disconnect the cable, thenreconnect the cable and turn it back on. No help.
I trash my FCP preferences, start FCP again, redo myprefs. Nothing.
I hit the reset button on the Z1U. Nada.
I do all this and then reboot the computer. Bupkis.
The footage was definitely shot in HDV. I can play it fine on the camerascreen.
I check the cable, which is brand new; it is firmly in placeon both ends.
Okay, so now I turned off the camera, quit FCP, ejected theOWC drive and turned it off. Iunplugged the eSATA cable. I wentand got my MacBook Pro and connected it to the OWC drive with a FW 800 cable. The camera was still connected to theOWC media drive via the i.LINK cable. I turned on the drive; I turned on the MacBook Pro; I turned on theZ1U. I started up FCP, and here’swhat happened:
It worked perfectly. No problem recognizing the camera, noproblem controlling it from the L&C window.
You might say that this solves my problem. But I prefer to edit on my desktopcomputer, and I am irritated that I can’t figure out what’s wrong. My suspicions are that it must havesomething to do with the cabling. FCP is working just fine with the Z1U routed through my media drive, theOWC. The only differences are thatmy drive is not connected to the computer via eSATA but FW 800. I see no differences in the settings.
Any insights?
Thanks,
Giraut

From what you say, I would suggest that the OWC enclosure does not utilize/energize the firewire interface when it is using the eSata.
This is just a guess.
Connect the Drive/Camera to your desktop via the FW800 cable: Mac Pro > FW800 Cable > OWC enclosure >FW 6Pin to 4 Pin Cable > HDV Camera. The speed difference between eSata and FW should be minimal as in each case you are limited by the FW400 connection at the camera.
MtD

Logging and Capturing

As a result of this thread: http://discussions.apple.com/message.jspa?messageID=3857627#3857627
I did a test of various ways to capture footage into FCP. Sorry for saying this again but I’m new to FCP - after 20 some odd years editing with proprietary, Avid and Premiere Pro NLE’s. I mention this [again] because it is hard to teach an old dog new tricks, and some of the bias that I’ve gathered along the way might show up in the way I approached this.
I have four one hour HDV tapes recorded on a Sony HC1; I used the same camera that created the tapes to down convert and capture standard definition NTSC anamorphic DV. Each taped averaged about 70-80 clips.
Tape 1
The first tape I logged the clips using the controls in the log and capture window. Fairly straightforward, but the HC1 was not very responsive to the J/K/L keys and the image in the capture window was very low resolution during scrubbing and searching. This made the process of logging slower than it should be. Once logged, batch capturing was fairly quick [about 1:12:00:00 to capture a 60 minute tape] and pretty much what I expected.
This was not a very efficient way to capture 70-80 clips, a lot of time wasted with pre and post roll. If you had fewer, 20-50 this might be the better way to capture but for what I was doing this was my least favorite way.
Tape 2
After entering the clip information into the log window I hit K key and capture “Now” button and captured the entire tape. I was a little concerned at what would happen when timecode ran out at the end. Nothing happened, it stopped and the clip appeared in the capture bin – all was good.
Once captured I created a custom Browser window with only the columns I wanted to log and make subclips: [following Steve Braker’s instructions]
1) Loaded the master clip into the viewer.
2) Set in and out points for the first clip.
3) Command-U to create a subclip.
4) Re-named the subclip, added description and label.
5) Click in Viewer and
6) Repeated steps 2-5 until 70 clips later it was complete.
Steve suggested deleting or moving the master clip, however checking the folder in the finder where the master clip was store revealed that this process didn’t produce individual clips. Apparently the subclips are simply pointers to the master file so I didn’t delete it.
This process was surprisingly fast but I still ended up with a single file that was approximately 5GB’s which made this process almost useless for working with subclips in Motion2 for example.
Tape 3
Marked an [in and out] in 20 minute intervals to create three master clips for this reel.
1) Loaded the master clip part 1 of 3 into the viewer.
2) In the Mark menu selected DV Start/Stop
3) After FCP placed markers at the scene breaks I “clicked the disclosure triangle” next to the master clip to reveal all of the markers in the Browser.
4) Selected all of the markers to highlight them
5) Chose Modify>Make subclip after which the subclips appeared in the same bin as the master clip and markers [note* at this point I checked my hard drive to find there was still only one contiguous master file for these subclips.
6) Re-named each subclip, added description and label and then placed them in a separate bin and placed the subclips that I didn’t want to keep in a bin to be deleted. [temp trash]
7) Highlighted the subclips that I wanted to convert to Independent clips
8) Chose File>Media Manager
9) Chose Use Existing from the “Media referenced by selected clip” drop down.
10) Selected the “Delete unused media from selected clips.”
11) Chose Clip Names from the “Base media file names on” drop down (Oops, sorry that’s for a PC) pop-up menu.
12) Un-checked the “Duplicate selected clip and place into new project.” This placed the independent clips in the same folder on your hard drive as the master file for the subclips. I suspect although I did not test it that if I had this checked I could choose a different folder?
13) Held my breath and clicked OK!
14) That’s when FCP started treating me like a total idiot “are you sure you want to do this, you’d better be because there’s no going back. Are you really, really sure…” Anyway for me since this is the only project on this machine I didn’t even read the warnings [yes I am an impatient idiot] **** the torpedoes full steam ahead..
15) Done! NOT Quite yet. You’d think that since I un-checked the “Duplicate selected clip and place into new project,” that FCP would be smart enough to place the new clips in my project window. Didn’t happen, had to control click and import files.
This process requires a bit more explanation. I had 16 subclips that I converted to independent clips, after which I deleted all associated subclips and markers. When I imported files there were only seven clips in the folder where the master clips was saved [now deleted as part of this process].
On further inspection all of the footage that I wanted was there, HOWEVER, by using the DV Start/Stop to create markers and then using those markers to create subclips if there are two or more clips with continuous timecode it consolidates them into one contiguous clip thereby defeating the purpose of creating the subclips in the first place. I’m guessing but if I hadn’t deleted some of the subclips I didn’t want to convert I would have ended up with the same large file with a different name.
The manual recommends that you delete the master clip from the Browser before converting the subclips into individual clips. I was suspicious of the need to do this so I left it and after the conversion it did what I expected, became offline. It was a good thing because I could use it to recapture. Also, any logging with description and labels etc is history it is not included in the new independent clip.
Tape 3 Part 2
I won’t bore everyone with going through the steps I’ll just explain how this one was different.
1) I didn’t use the DV Start/Stop option, instead marked I/O separately leaving at least 2 frames between edits to make sure there was discontinuous timecode.
2) I also didn’t bother naming or logging at this point and left whatever ridiculous name the subclip process assigned.
3) The settings in the Media Manager were all set from the previous conversion hit OK [this time read the warnings which would have done nothing to correct the previous attempt].
4) 12 subclips went in and 12 new independent clips came out.
5) Once I had the new clips I logged and added descriptions and labels etc…
Although this sounds like a very convoluted process, and it is certainly much more difficult than it needs to be, by the fourth tape it was predictable and quite fast.
I will say though that because FCP consolidated any continuous clips without warning you really have to pay attention to detail. And it would be nice if we could use the log & capture window for this process so any descriptions, labels etc would be carried forward to the new clip.
Certainly not as easy to accomplish as it is in PPro but definitely possible. There might be more functionality that I just missed, if so please let me know. Anything that can be done to simplify this would be helpful.
Mac Pro. 5GB RAM. 1TB SATAII RAID 0. Mac OS X (10.4.8) FCP 5.1.2

When you delete the master clip from the browser, you aren't deleting the media file it referenced. So the subclips reference that same original captured QT movie, it's just not in your project.
It will work. try it. It's how I've been working for about 6 years now. I don't have problems with subclips at all doing anything I want to with them.
Subclips are nothing more than reference files that reference a portion of a master clip. A Master clip is nothing more than a reference to the media file that you're capturing... it's not the media it's a reference to it.
Subclips are how FCP was really intended to be logged I think. I don't like long captures at all, and would prefer to actually capture the way you did the first time... but because it takes longer, I usually don't have time to do things that way. However, if you do things that way, you can add descriptions etc. to the logged clip in the Log and Capture window, if that helps your workflow.
The responsivness you lack with your HDV camera is because it's HDV... HDV doesn't contain all of the pixels of every frame, so to see a single frame the computer has to do a lot of processing to show it to you. It's an MPEG stream, which uses whole frame information every 8 or 15 frames only. The rest of the frames are the difference between the frames only on the recorded tape, thus the work and slow response to HDV logging and capturing.
P2 on the other hand, would make ALL of this MUCH easier to deal with. For one thing, each take is an individual file, and it's an all I frame format so it's easier for the computer to deal with. It renders 8 times faster than HDV does... no "conforming" necessary.
Jerry

CAN NOT log and capture final cut pro

I have written 3 weeks ago... I NEED HELP...
I have Mac G5, Mac os X, 10.4.11 dual 2 ghz power 2 gb ddr sdram
I have external lacies plugged in, have NEVER had a problem log and capturing
until the most recent update with quick time...
Im very upset and need this resolved asap... please help...
I have repaired disks, gone to library / receipts, re downloaded quicktime 7 still nothing
when I try to log and capture, I see my dv playing as soon as I click on capture now
it stops and says... FILE ERROR: UNKNOWN FILE..
PLEASE PLEASE HELP.. too many jobs are due
thanks
Cindy Lambrakis

Rebuilding your startup disk involves erasing it and then reinstalling your software from scratch. If you've not done this in a while, I'd suggest you do it. Back it up first, then go for it.
In the mean time, you might try resetting your PMU button on your mac's motherboard. It's underneath the fan you can remove to install RAM. Unplug your Mac from power completely, then open it, remove the fan, and press the little round button there labled PMU. I've seen this fix up firewire problems.
Jerry

Fast Forward and Rewind keyboard shortcuts in Log and Capture

In FCP, I want to assign the Fast Forward and Rewind buttons (in the Log and Capture mode) to buttons on the keyboard. I've assigned the functions using the Keyboard Layout in the Tools menu but it doesn't seem to be working like it should. In Log and Capture when I use the mouse to press the Fast Forward button, FCP stops the miniDV deck and fast forwards the tape as fast as possible without showing any picture. However, when I invoke the keyboard shortcut I created all I get is the picture moving a few fames per second instead of the tape stopping and fast forwarding as fast as possible. The same happens with the Rewind keyboard shortcut as well. Any ideas as to why, and how I might be able to fix this?
The computer I'm currently working on is a Dual 2 GHz PowerMac G5, 2.5 GB RAM, Final Cut Studio (Final Cut Pro 5.0.4).
–Michael
Message was edited by: Michael Starks

When I press the fast forward or rewind button while logging a miniDV tape the video stops and then the tape fast forwards or rewinds at a MUCH faster rate than L or J ever give me. That is the behavior I am trying to get from a keyboard shortcut.
Not possible via keyboard shortcuts, unfortunately.
Even if you map the Rewind and Fast Forward functions to keys in a Custom Keyboard Layout - for those who didn't know, yes, there are specific commands for those functions even though they are not mapped by default - those shortcuts will not within the L&C window. We're stuck pressing the buttons.
Forgot to mention: the only time you're able to invoke the true fast forward or rewind function is using Shift-I/O (that is, Go to In Point or Out Point). Of course that only works if you have the necessary In/Out point set...

Unable to Log and Capture AND make FCP a boot disk

I am unable to go into Log and Capture mode in FCP 4. I can capture from firewire using I movie just fine so I know the sytem works. The minute I open Log and Capture from within FCP (with the JVC Mini-DV camera hooked up thru Firewire), it crashes. Help. I upgraded from FCP 3 to FCP 4 a couple years ago and it hasn't worked right since. Would re-installing the FCP 4 upgrade work? Also, my system works very sluggish. Please explain to me how I would make the veersion of FCP 4 my boot disk. I realize that I can't have the FCP 4 application and the media on the same drive but is there a way to partition one of my drives and make FCP one of the startup disks? Hope this isn't too confusing. Thanks.

First off, FCP 4 was darn unstable. FCP 4.5 is a free upgrade and is STILL the most stable version out there. FCP 5 is getting there.
Secondly, try:
Shane's Stock Tip Mantra: If the program was working fine, and now isn't, or just isn't working the way it should, the first things to do are:
1) Trash your FCP preferences. Download the appropriate version of FCP Rescue at http://fcprescue.andersholck.com/ and run it.
2) Open the Disk Utility and Repair Permissions.
As for partitioning the hard drive, that isn't necessary. Hasn't been since FCP 3.
Shane

Log and Capture in FCP 6.0.5 flash red frames

So I have been having a very odd and troubling issue during my log and capture stage in post production, whenever I try to import a tape into FCP I get this intermittent red colored frame that flashes for what I could only guess is a frame and it happens probably every ten frames or so; I've tried every combination of hardware troubleshooting from a different deck and camera, tapes from all different times and cameras and formats, different firewire cables and even different firewire ports.
Has anyone has any experience with this or even anything like this, and if so how can I make it stop, I have even tried that final cut maintenance program and basically everything short of a clean reinstall... do I really have to go that far!?

Some users have success with the newer drivers others not so fortunate.
Read through this thread:
http://discussions.apple.com/thread.jspa?threadID=2676952&tstart=0
Al

No Audio during Log and Capture

Hello, I have FCP 6.0 and am unable to hear my audio during log and capture. I have this problem on all 5 G5 Macs that I have, and have tried different editing docks and cables. I have used FCP for more than 5 years and have never had this problem. iMovie has audio during capture, so I am convinced that there is a pre-set in FCP that I don't have checked properly, but I've been over them many times and still have no answer. I searched past forums and didn't really find anything helpful to me.
My pre-sets are set to DV NTSC 48kHz and the playback pre-sets are set to default. I can hear audio of my clips after I log and capture, but I still need to hear audio during importing. I'm more confused than anything. If anybody has had this problem before or any suggestions for me, I'm all ears.
Thanks.
John

... as Bogie says.
However... this is a non-feature that dates back to slower CPU days... yet, still with all the different formats and such I (ME!!) I believe it's still good practice to leave it off.
Devoting as much CPU work to the capture process lessens the chance for something to go wrong. You can easily monitor the audio directly out of the deck as needed.
Sure -- octo cores need 30 apps open just to get your money's worth and I'm sure you won't have any issues using an 8th of one to send audio thru itself while the other 7 and 7/8ths are used for capture... but who wants to risk it?
Not me... I'm to old to change my ways.
Blast you FCP v1.2.5 on a beige G3 with 7gig and 15gig hard drive -- you taught me well.
CaptM

Log and capture freezes - please help

hi,
I'm using FCP 5 (studio). on G5 dual 2GH 1GB.
it has become a nightmare to log and capture. after few minutes from working with log and capture the applications freezes. I have to force quit FCP.
I trashed the preferences once, I re-installed, but the same thing is happening. I'm working on 2 projects, deadline is approaching.
I appreciate any helpful responses.
sz

Are you trying to record three video streams simultaneously? Or by a video amplifier, you mean a video switcher?
If you are using Capture Now, make sure you have set a capture limit. This is why:
When you use log and capture, the disk system is being asked by FCP to essentially "keep capturing until we tell you to stop ... and no, we don't know HOW much that will be either." It is stressful on the system to be continually wandering around looking for space to stuff those ones and zeros with out any sense of how many they have to accommodate. One solution available to the system is to allocate the ENTIRE empty space on the disk as the potential capture file. This essentially locks the machine as there is no headroom for basic disk operations.
However if you set a limit on capture now, say 60 minutes, the disk system can allocate the space and may seem to be less confused by the process. It still does not know EXACTLY how much you want, but it knows you will not want MORE THAN the limit and therefor can reduce some of the uncertainty.
Better yet is to record to a timecode addressable tape. This allows you to log the tape, then use batch capture. When you do this, the system knows EXACTLY how much space to allocate for each file and is very efficient.
Good luck.
x

Using a Mac Pro Lap top to log and capture.

I am traveling and working on a documentary. I purchased the Mac Book Pro with Final Cut, assuming there would be an IEEE1394 port for a hook up with my video camera. I am really kind of floored there isn't and no one I spoke to when I had it configured mentioned that even though I was like, "I'm buying this because I'm traveling and making a documentary." In the meantime, I am logging and capturing through my external Hard drive, connecting my camera to my hard drive and then my hard drive to my camera.
I am wondering if this is the most efficient way to do this? Also, I am wondering if this is compromising the quality of the image.
Any information you can help me with would be greatly appreciated.

Your MacBook Pro should have a Firewire 800 (9 pin) port. The MacBooks are the ones that don't have a Firewire port at all. You can use a Firewire cable with a 9 pin connector on one end and a 4 or 6 pin connector on the other.
You can also get an Firewire card for the express card slot. That would create a second Firewire bus on your Mac.
-DH

Is it possible to resize the log and capture window?

Hi,
Using Final cut pro, I would like to make my capture window a bit bigger while capturing. I am capturing footage via my Blackmagic Infinity card and get the input through an HDMI cable. I'm capturing in Apple Pro ress on 720p, 59,59 fps.
For a good overview of what I'm capturing at the moment, I would love to have a bigger capture window. For all I know, FC pro doesn't support the resizing of the log and capture window. Anyone an idea on how to solve this?
Thank you.

In my case, the capture window is adjustable if I am capturing SD (DVCAM) video. I can also use the scopes in this case. (Good if you are recording to disk, or using a laptop for monitoring.)
However, both features (adjustable capture window and scopes) are not available if capturing HD (HDV in my case) video.
Message was edited by: amarasme

Final Cut crash on 'Log and Capture' selection

Hi guys,
So I have a BlackMagic Decklink Extreme card installed, and hooked up to a Sony J-3 DigiBeta Deck.
When I attempt to 'log and capture' final cut crashes before the capture window pops up. This happens on all setup's (10-bit/8-bit/JPEG) when I have device control turned on (RS-422). If I turn off device control, the capture window opens normally, and I can do a capture now, which is no good to me for logging purposes, or doing offline edits.
So, my question: Is the device control crashing Final Cut due to the fact that Im using an intel mac with Final Cut 5.0.4? Can anyone confirm this for me? Or is there something I can do to fix this? Has anyone experienced this problem?
Device control works outside Final Cut, in BlackMagic Deck Control, so I know its not a card issue.
Im still waiting on a copy of Final Cut 2, its in the pipelines... but in the meantime if there is a quickfix to this, help would be much appreciated, as Final Cut 5.0.4 is otherwise extremely stable for me...
Thanks,

Some background:
720x480 is a non-square format. It can either be the equal of 640 x 480 (4:3) or 954 x 480 (16:9) depending on what you tell your editing software the incoming stream will be.
If you told FCP the incoming stream is DV/NTSC 4:3 and you are getting a pillarboxed image, FCP is thinking you are sending it a 16:9 version and is filling the the sides to keep the aspect ratio correct.
It would help to know a whole lot more about settings within FCP and what your mixer is putting out.
x

Eject Button for Log and Capture

Similar Messages

Maybe you are looking for