Sean Oneil
Forum Replies Created
-
[Bill Stephan] “Canon HDV is 720P. Sony HDV is 1080i. Panasonic doesn’t do HDV — it does DVCPro HD (DVCPro 100MB). Welcome to the world of HDTV!”
Is Cannon 720 HDV the same as JVC 720 HDV? Will a JVC VTR playback Cannon tapes? I was thinking about getting this:
https://pro.jvc.com/prof/attributes/features.jsp?feature_id=01&tree=&itempath=null&model_id=MDL101457Sean
-
[Michael Black FCP] “Ok, that seems very strange to me. How can it not be either one? If it’s shooting in 24 frames… oh man, this is blowing my mind”
The actual CCD chip on the camera does not capture progressive scan. I don’t know the details, but what is says is that the end result after capturing it is virtually identical to 24p. They’re just being honest in the fact that it’s not a “true 24p” as far as the process in which it records to tape.
Presumably, you need firewire capture to take it in as 24p. Using pulldown-removal on SDI input may not work.
Sean
-
Hmmm, not sure about that. Maybe someone else has tried it.
-
No. You can’t edit any codecs in RT that aren’t officially supported by the RTExtreme engine.
Sean
-
Unless it specifically accepts 1080p signals, it will not work. And unfortunately almost all of the “1080p” sets fall in this category. This is a heavily discussed topic in home theater circles (check AVSforum).
The only TV sets I know of that will accept a true 1080p signal are some of the LCDs from Westinghouse, and the DLP sets from Hewlett-Packard. The Westinghouse sets are a steal. I actually have the 37″ at home. Milky blacks, but that’s expected from an LCD. For the incredible price, I can’t complain.
Sean
-
Decklink cards don’t need the the BMD codec on a Mac. In fact, they use the Apple Uncompressed codecs by default for everything except 4:4:4 dual-SDI capture. So most users don’t even need the BMD codec.
But I’m sure they’ll update their codec to UB by the time the non-beta version comes out (I have no inside info, just speculating).
Sean
-
Sean Oneil
August 21, 2006 at 6:11 pm in reply to: Raid question for uncompressed SD/SDI in FCP on Mac Pro.[iMan] “If so, what about HDCAM uncompressed footage for the future?”
I wouldn’t rely on it. I’ve tried uncompressed HD on a 4-drive SATA array. You’ll get dropped frames occassionally. 8-drive SATA is a better idea for that.
Or you could use 4 extra-fast drives, like 10k RPM. That should be fast enough.
-
Sean Oneil
August 21, 2006 at 6:02 pm in reply to: OT: Blackmagic Decklink Extreme and new MacPro system and FCP 5[Devin Crane] “but the lack of Professional Audio inputs”
What lack of professional audio inputs? Decklink Extreme has analog, SDI audio, and AES inputs.
-
You can capture the HDCam tapes as DV footage on the fly. Kona and Blackmagic cards provide this feature. Since you’re shooting at 29.97, the timecode will be the same. So you can do all you offline editing on the same timeline w/o rendering. When you do the finishing, you can rent the deck again and batch recapture the HD footage in HD.
Sean
-
I think I’m the only person alive who actually likes Media Manager. I think it’s great. Yes, various versions of FCP have had bugs (like when you couldn’t “delete unused media” from offline clips). But I’ve always liked it. It’s pretty straightforward. Copy, Recompress, Make Offline – these are all great, useful tools. They help you and force you to stay organized.
Back in the Media 100 days, it was much, much easier to up-rez. But that wasn’t a good thing. You had no control. You couldn’t even reconnect media.
MM aside, I’m actually getting really fed up with FCP and I totally understand some of the complaints. This past month, for the first time ever, I’ve wondered if going with FCP instead of Avid was a mistake. It feels like a snail now. In fact, the whole Macintosh experience just crawls. Everything is slow and unresponsive. 1-2 years ago it seemed pretty fast. But it hasn’t kept up. And FCP is the worst. Rendering is bad enough. But I even have large projects where the actual project takes 3-4 minutes just to open and 30 seconds just to do an autosave. This is totally unacceptable.
I hope the Mac Pro and Leopard will get things back on track.
Sean