Todd Dalton
Forum Replies Created
-
Thanks Matt,
The problem is that that will work on one clip, either 4:3 or FHA. It’s when there’s multiple clips some of which are 4:3 and some FHA. Media Manager will only output *all* 4:3 clips or *all* FHA clips for the new sequence so the footage gets letterboxed or pillarboxed. I still can’t make it work and am giving up and having to finish the online using the client’s external drives. Which makes me feel daft for purchasing a raid array worth a couple of grand! 🙁
Shame on Apple (until such time as I’m proved wrong, that is!).
Todd.
-
Hi!
I’m running a similar system (in fact my Sonnet raid’s prob not as fast). ‘Fraid to say that I’ve never experienced dropped frames with either an external usb mixer or dragging the software sliders. How many realtime tracks are you generally trying to do? I don’t use over 8 (more of a legacy of my editing experience than anything)….
Or keep trashing your settings? 🙂
Todd.
-
Hi,
This might be a ‘dead’ thread but here goes: both my system and the other systems I’ve worked on with Aja Kona 3 cards in HD experience a 2 frame delay on the cross-converted output when going from HD>SD or visa-versa. I’ve always considered it a fact of life that it takes 2 frames for the Aja to do a conversion – which is fair enough. Almost all (if not all) purpose-built aspect ratio/standards convertors take a frame or two to process the picture.
Consequently it’s not possible to drop an individual shot in. You have to drop in the entire sequence from black to black.
Hope this helps and wasn’t too late! 🙂
Todd
-
Thanks Jeremy,
It was shot at 60fps. So it’s actually a setting on the VTR? The system frequency and all that?
Todd
-
Hi,
You mention the rendering in YUV, have you tried rendering in RGB (as in the timeline options page)? I’ve had similar where my graphics card couldn’t handle rendering certain fx in YUV – full green screens instead of colourful pictures and the like. Switching the option to RGB gave me an output… Not that it guarantees legalised pictures! Had to be careful about that 🙂
T
-
Never had to think about this, but off the top of my head wouldn’t nesting have a problem? If you were to (say) zoom in 200% on one of the clips on the track for framing reason (or to place an extremely large image in an SD sized sequence), then nest the track and zoom back 50% you’d end up with black borders around the edges as the nesting ‘truncates’ the frame to the sequence output size…. Hope that makes sense…!
Personally, I’d try Motion, AE or Combustion with each of the clips arranged in the layers one after the other and then use the camera to fly around…
Todd.
-
Maybe, just maybe (and it’s just a thought so I’ll happily accept I’m wrong!) the codec you’re using is one of those that comes with the video card you’re using, eg Aja-ProRes(HQ). So the QT might have some metadata that can restore the super-levels but only in FCP….. I can think of many reasons for this not to be the case, though. Either that or there’s a bit in the data word that’s being lost by the external software (I suppose that could be related to the idea of avoiding hardware accelerated codecs as mentioned). This is vague, I know, but my only suggestion is to look at using the codecs in the pull-down list that are only supplied by Quicktime when you install it; so keep to ProRes but make sure it’s Apple’s one…. Having said that I’ve got Combustion on my machine and have never noticed clipping, but my eyes aren’t what they were! 🙂
Hope this is of some help!
-
Thanks Todd!
Great info. I’ll upgrade in the next couple of days. I’ve got the Aja Kona 3 so I’m thinking the current (NDD) driver will be fine……
Todd.
-
Just thought I’d post a final update: the machine went off to the workshop and after much discussion between myself and my support, we realised what the matter was. The background to this solution is that I’ve set my machine up to be used by other freelance editors, so I thought I’d be really cunning and force people to use only one password free, non-administrative account. On top of that, I also put restrictions on which apps. could be run. I know, by and large, that non-admin can’t do anything too ruinous but disk utility can be run and an idle editor will drift through the applications folder!
Now it turns out, that the solution was to not use ‘parental controls’ on the account. With this control unchecked in the accounts pane FCP behaves loverly! 🙂 It’s probably trying to access something that gets automatically disabled with parental control but I didn’t see anything in the list that could look like it would stall FCP. I only unchecked the stuff like disk util and Safari, ichat, ical, etc.
To stop people getting to an app, I’ve created an ‘Admin Util’ folder inside Apps one and put a no-access for FCP USER account on the folder and it’s contents. Then I just drop the odd possibly-dangerous-in-bored-hands app in there and all is relatively safe! I hope. Thanks to all for their advice, though.
-
Cheers Mitch!
I emailed Aja last week (not Rudy in particular, though) but haven’t received a reply yet.
All these possible solutions are very interesting but sooooo confusing! 🙂 So many variables so little time!
Todd.