Dino
Forum Replies Created
-
[Nick Price] “your problem might aslo be your decklink card. This is a known unsolved problem with decklinks”
Are you saying Decklink cards are a known source of memory leaks?
I would say I’ve seen this slowdown problem plenty with or without a card.
-
Exactly, what is that green frame? I didn’t put it there. It definitely doesn’t belong there and I can’t get it to go away. Anybody seen this before?
-
pre-stretched?
In the motion tab, scale to 133 and distort at 33. This stretches to fill the frame horizontally and pushes the top and bottom out of the frame to maintain the proper aspect for placing 4:3 material in a 16:9 frame. This is done directly to the subclip rather than the clip in a sequence. Individual subclips are tweaked for the best horizontal placement. By doing this ahead of time (with the cheaper labor of an assistant editor) the editor doesn’t have to worry about having to constantly adjust clips as the editing progresses. My personal preference would be to not worry about this until they are closer to a fine cut but the director doesn’t like seeing half the shots with side bars.
Regarding the frame being a title safe marker. I realize the image I posted doesn’t show it well (I’d get another one but I’m not at the location) the picture fills the entirety of the frame, the gray is actually the background of Final Cut. the green lines sort of make sense as the wireframe boundaries, except they’re not. You can see on the right edge that the box is inside the edge of the picture. I would chalk it up to a bad bug, I’m just hoping to find some confirmation and a nice workaround.
-
For starters, almost no application, Mac or Windows will make use of more that 3.5 or 4 gigs of RAM.
Now, if on a fresh launch of Media Composer, choosing to create a new project, you are showing memory usage of more than 2 or 3 percent, something is wrong with your system.
If you are opening a very large project and run into this, you have too many bins open or the bins are overloaded. Only open bins are placed into memory. A bin with 17 versions of a 3 hour sequence will take a lot of memory. Splitting up your versions into a few different bins and opening only the one you need will greatly reduce your memory usage.
In the future please note the program you are running and it’s version number.
-
Don’t y’all worry, it’s coming. The innovation I mean.
-
I think you will get an answer if you rephrase your question. It’s unclear as to what you are actually trying to do. You reference AAF though I think you think it something other than what it is commonly understood to be, maybe.
-
There is Apple Enterprise Sales: (877) 412-7753.
I don’t think your located in the USA though?
Perhaps there is something in here?
https://www.apple.cz/cze/footer/contact/ -
[Andras Sarkadi] “The machine I use is a 2.66 QuadCore MacPro connected to an Xserve SAN (so bandwidth can not be a problem)”
Bandwidth can absolutely be a problem. You make no mention of the storage size or type, number or users or how it is all connected. If you are using Apple Xserve RAIDs, uncompressed HD requires practically the full bandwidth of both sides of a unit. Your particular configuration and the number of users hitting the storage could very easily cause playback hiccups.
-
You make no mention of what version of Media Composer you are running or any system details at all. There were some buggy versions (prior to 3.0 I believe) for which fast import of DNxHD didn’t work.
-
[Michael Hancock] “If so, you’re probably seeing an interlace flicker.”
I agree on that. Interlaced video hates thin lines or crisp edges.
Sometimes a minor positioning adjustment can make the difference of where the edges lie in terms of hitting the right place in relation to the interlace. Also a slight blur can make a huge difference by providing a little dithering. I would always add a .3 gaussian blur to text and many graphics from photoshop or after effects before trying to make them video (SD). I can’t recall what options you have in the PIP border control.