Kevin Hamm
Forum Replies Created
-
Kevin Hamm
August 18, 2009 at 8:02 pm in reply to: FCP 7 Digital Delivery with Closed Captioning in HDI’m still having issues with this. I’m using a Sony DSR-45 via Firewire, and it’s not getting the line21 captioning at all. I’ve reset my .scc to be 00 based, rather than 1 based, and still it’s not showing up in output.
Any thoughts? I’m also testing the 00-based .scc file to see if it can still add the caption track to the Quicktime files, as we are going to do downloads and I want them captioned as well, but the timecode change may bunk it up, as that was working fine with the 01-based .scc file.
I’ll keep you informed, and if you have any other ideas, please let me know.
kev~!
Kevin Hamm
Video, Web, Print and coloring books. -
Kevin Hamm
August 17, 2009 at 7:52 pm in reply to: FCP 7 Digital Delivery with Closed Captioning in HDAha, thank you for the insight. I was both stuck and befuddled. I also wonder, what deck/cards are you using? I’m just using a Sony DVCAM deck and firewire connection, so I’m still going to test this shortly, but whatever you used would be helpful to know.
Thanks for filling this in. Thanks a bunch!
Kevin Hamm
Video, Web, Print and coloring books. -
Kevin Hamm
August 13, 2009 at 2:40 am in reply to: FCP 7 Digital Delivery with Closed Captioning in HD[Jason Livingston] ” If you saw our R&D expenses, or compare our prices to the fees typically charged by caption service companies, you probably wouldn’t think so. Our interface was designed by captioners for captioners and FCP users, drastically reducing the time and costs for preparing captions. We also offer the best support in the industry, which is why companies like Apple, Sony, NBC Universal, Fox, etc. rely on CPC’s expertise for their closed captioning needs. If you look in the new Final Cut Pro manuals under closed captioning, the only name you’ll see mentioned is MacCaption by CPC. “
I’ve seen the interface, it appears to have been designed for OS 9 and not updated with anything but pinstripes for OSX. And while looks isn’t really an issue, the fact that a system like yours, which appears to be built by buying up the competition and eliminating it to artificially keep your prices high on a tool used to make video entertainment accessible to those who are hard of hearing or deaf, causes me to feel less than trusting of you and your company.
As the information in the Closed Captioning track is, as you well know, text with timecode (608) or text with timecode and a stylesheet (708) there is no reason that it can’t be built digitally, without a separate box at all.
I’m not happy with the results of my research. I’m less happy with your attempt to defend your truly untenable position. It’s required because it’s the right thing to do; it should therefore be cheap and relatively easy because everyone, I repeat everyone should be using it. Your costs are proof that something is wrong, and I’m willing to bet it’s tied up in your propaganda.
But please, if you can prove me wrong, do so.
Kevin Hamm
Video, Web, Print and coloring books. -
Hey Devin, I’m wondering if you would be able to post about your workflow for closed captioning, and how it might change with FCP7? I’m doing a local college coaches show this year (something I did in 2007 as well) and have to have it CC’d, which is new. I’m researching and trying to figure it out, but it seems a mess from the get go, and I don’t have much time.
Anything would be helpful.
kev~!
Kevin Hamm
Video, Web, Print and coloring books. -
Ok, first off, Carbon V Cocoa is a non-starter. Several of the Pro Apps use Carbon and Cocoa libraries, and Final Cut most certainly does.
If you were able to open the project completely from the 2nd drive and it worked after you reconnected the media, it’s not Final Cut that is the problem. It’s most likely your 1st drive. In my experience, when a drive starts to fail, it’s subtle and causes weird bits, but programs like FCP that grab and hold onto so many large files tend to run into the errors faster and harder.
If you’ve heard your drive click-and-spin-up-then-down and your finder has stalled a bit, it’s definitely the drive failure. If you’re just having issues with it when this large project is on the drive, you may just have a bad sector.
Get DiskWarrior and test the drive, you’ll know then, but back your stuff up and off that drive just to save it.
Kevin Hamm
Video, Web, Print and coloring books. -
Kevin Hamm
March 7, 2008 at 6:02 pm in reply to: Audio sync problem bringing in video from VHS tape.Make your life easier, just replay the tape and capture the audio using the Headset out from the camera to the Mic port on your computer and recording in Quicktime. Then resync the audio and the video. Hopefully you have a slate or clapping or something to help you do that.
And yes, it’s probably a latency issue, although what and where is hard to tell. Is the JVC recording as it’s passing through?
kev~!
Kevin Hamm
Video, Web, Print and coloring books. -
Have you had any kernel panics with this machine? Even, actually most especially just a few and only when you really loaded up the system? If so, I’m seconding the advice about the memory sticks. Here’s an easy test: Open the computer and remove the outermost 2 sticks, one from each side. They have to be placed in tandem on each side, so you need to do 2 out, but once they are out, restart and try the render. It will be slower, but shouldn’t be so bad it’s unworkable. And if it crashes, swap the sticks, so that again you have just one set in there, one set out. Try once more.
If after that you’re still having problems, get your logs and get on with Apple about it. They can tell you if the memory of the Graphics card is bad, or if something else, like a firewire bus connection, is causing this problem.
kev~!
Kevin Hamm
Video, Web, Print and coloring books. -
Yep, and there are a few things. One, save a backup of your FCP project as it is now to another drive just as a precaution.
Then, double click on the clip in the timeline so that you throw it up in the viewer. If you’ve only got one new clip, this is simple, if you have more than one new clip area that you want rendered, just repeat it.
In the viewer, go to the basic motion tab and open the Drop Shadow settings. Click the checkbox to activate the drop shadow – this will usually cause a render to be needed. Now, change something else in the timeline – even something as simple as dragging this same footage beyond the end of your sequence. Then go back to the viewer, uncheck the Drop Shadow checkbox, and back in the timeline, delete the added footage. You should still need a render for the areas that you’ve chosen.
If that doesn’t work, you can always apply a LiveType title over the top of it, render it, delete the title, and re-render the bit.
Have a great one!
kev~!
Kevin Hamm
Video, Web, Print and coloring books. -
Just did this set up, and I’ve only got 2GB of RAM in my MBP. It works fine, can even play, scrub, start and stop, no issues. And I’ve got Safari, Mail, iTunes (with X-Men movie paused) Motion and System Profiler all running. I had SysProf open because I didn’t know if I had the same graphics card, but I do.
The only difference between our systems is QuickTime (other than RAM, but that’s not used for Motion, so it’s immaterial).
Update your QuickTime to 7.4.1 and you should be ok. Motion, after the last pro update, doesn’t play well with anything less, really.
Hope this helps!
kev~!
Kevin Hamm
Video, Web, Print and coloring books. -
Ah, so they do. Go for it!!
kev~!
Kevin Hamm
Video, Web, Print and coloring books.