Michael
Forum Replies Created
-
You do not even need a Kona 3. All you need is a card with an HDMI or HDSDI output. Cineform muxes the eyes into a side-by-side image. As far as the card is concerned, it’s just another HD signal.
It’s the TV that “demuxes” the side by side image and produces a 3d image.
You do need the Kona 3 with some projection systems that require 2 separate streams.
And a warning: Cineform is $3k. There’s also “Stereo 3d Toolbox” that’s a plugin for FCP. It’s less expensive, but requires just about every shot to be rendered. And we all know how good FCP is about keeping track of renders.
Michael Heldman
Spot Welders -
Alan is right. It’s a pretty basic function and FCP should have it. It’s one of those features that Avid has had forever that I really miss in FCP. I’m sure there is a reason, deep in the ancient code of FCP, that this can’t be implemented now.
Let’s just hope that someone, deep inside the Kremlin…I mean, deep inside Apple Hdqts, is rewriting that code.
-
Michael
April 6, 2010 at 9:21 pm in reply to: using media manager with Soundtrack pro project on timelineIt’s gotta be a bug. Happens to me too when media managing projects with STAP files. So I have to render out all my STP work. Kinda negates the advantage of the “seamless” roundtrip.
-
If you can’t find a good use for it, how about donating it to a local school, church, Boys & Girls club, etc.? Good karma, you know.
-
Still trying to sort this out. I tried it without the isight attached, but ichat won’t open a video chat without a camera attached, and FCP won’t “share” unless a video ichat is already open. Hmmm
Michael
-
Good point. I’ll try it out an report back.
If you’re right, it would mean that the ichat share only works as advertised on computers with built-in cameras, or perhaps monitors with built in cams. And that’s a shame because I bet most of us don’t work with that kind of set up.
Thanks for the reply.
-
It never worked properly for me and many others, hence the workarounds. If it works for you, great. Maybe it’s been fixed in 6.03?
-
Not as far as I know. I think these buttons work in several other programs, including logic, and you can get lexan overlays to indicate what the do in any particular program. But not for FCP.
I’d love to be proven wrong about any of this. I wish the board had more functionality within FCP.
You might want to look into other brands of control surfaces. Behringer makes one that’s only $200. It works, but the faders make lots of noise as they fly around. I also hear Tascam has a good model that includes mic inputs with phantom power.
Search through the forum. There have been threads on this subject in the past.
-
I have the Mackie control surface.
You can use it to control level and pan. The mute and solo buttons, and the transport controls (including the jog wheel) work as well.
The rest of the buttons, as far as I’ve been able to learn, have no function within FCP.
-
Thanks for the virtually instantaneous responses from two of the experts.
Dang. I’m in a shared environment with several other stations. Projects move around. I suppose I could upgrade them all, but I usually wait a little longer after an update is released.
Any major problems with 6.0.3? I heard there were issues with a few HD formats, but these might not be relevant to us.
Thanks again.