Forum Replies Created

Page 27 of 34
  • It wasn’t clear to me … does it have a diopter adjustment? Similar to what you have on the camera’s viewfinder?

    I’ve gotten old enough now that I can’t read without correction either.

    Sheesh.

  • Kevin Patrick

    October 25, 2011 at 3:02 pm in reply to: A few clues

    [Shane Ross] ” DVD Studio Pro…PRO DVD authoring app…killed.”

    Wasn’t that another Apple acquisition? I think the name of the company was Spruce. As I recall, it was one of the better authoring packages out there at that time. PC users lost out on that one.

    It’s one thing to back out of a market segment. It’s another to buy up companies and kill their products too. Not only am I taking my toys and going home, but I’m taking other kids toys with me too.

  • Kevin Patrick

    October 25, 2011 at 2:47 pm in reply to: FCP X & iTunes – performance issues

    I notice you are running Lion.

    Have you checked Activity Monitor? Which is maxing out? CPU or memory? FCP X typically takes up over 7 GB, at least for me. The performance issue I see is Inactive Memory usage slowly rises. It rises even if you aren’t actually doing something.

    Launch FCP X and the Activity Monitor. Watch Inactive Memory and it will probably start rising. Use FCP X and it seems to rise quicker.

    My understanding of Inactive Memory is that the OS sets it aside, typically when you quit an application. It’s keeps it in case you reopen the same app. Eventually, it’s supposed to release the memory. I’ve never seen Lion release any Inactive Memory. One time, I quite FCP X and all other applications and left my system on over night. I came back in the morning and Inactive Memory had consumed 20 of my 24 GB or memory.

    This appears to be a rather well discussed issue on Apple’s Lion Discussion board. I’ve tried some of the suggestions there. Use a new user account, to see if anything hiding in my Library was causing the issue, it’s kind of like a complete trashing of all preferences. I re-installed OS X Lion 10.7.2 Combo, sometimes this helps but it needs to be the Combo. Nothing changed. It’s not FCP X, because the Inactive Memory issue happens without FCP X running. Some suggested running in 32 bit mode, no thanks.

    The only way I’ve found to reclaim the Inactive Memory is reboot. I actually tried switching Users, but the Inactive Memory stays the same.

    I did come across a suggestion to use the purge command. I tried it out and it does appear to work. Even while using FCP X. But … using Terminal commands makes me nervous. The name itself sounds so permanent, Terminal. (I hum the Terminator theme music the entire time I use it)

  • Kevin Patrick

    October 25, 2011 at 1:16 pm in reply to: Just purchased Used EX1 – Questions

    Here’s where you can find FW for the camera. There is also a link on this site for Sony’s SW. XDCAM Browser and Transfer. I use Browser to make all my backups, retaining the BPAV file structure. I use Transfer to re-wrap the files to *.mov files. You don’t need to re-wrap them for PP. But you do need to do that for FCP 7 and FCP X.

    https://pro.sony.com/bbsc/ssr/micro-xdcam/resource.downloads.bbsccms-assets-micro-xdcam-downloads-XDCAMSoftwareDownload.shtml

    I believe the read me document explains how to install it, pretty easy.

    I use Sony’s SxS adapter:

    https://www.bhphotovideo.com/c/search?Ntt=sony+mead-ms01&N=0&InitialSearch=yes

    And Sony’s Memory Stick Pro Duo HX cards:

    https://www.bhphotovideo.com/c/search?Ntt=memory+stick+pro+hg+duo&N=0&InitialSearch=yes

    Sony also sells an SDHC card adapter, but they say it’s for emergency use only. I’m not sure why they say that. But, I went with the above items and have had no issues.

  • Of course not. I can’t imagine anyone else would either.

    Although, I’m not sure why you are asking me that question.

  • If my response implied that I in some way approve of censorship, then I did a poor job responding. (and that wouldn’t be the first time I did a poor job posting on the internet)

    Just to be clear, I don’t approve of censorship.

    I also don’t know why the post was pulled.

  • [Tim Wilson] “If I had seen it though, I personally would have turned it off in a heartbeat.”

    That’s good know. I agree with you, especially for the reasons you highlighted.

    No one knows why it was on Avid’s site. No one knows who put it there. It may not have been an Avid employee.

  • Kevin Patrick

    October 24, 2011 at 11:48 am in reply to: Advice Needed– FCPX Native Support and other things

    I’m not sure what your concerns are about re-wrapping files. I have been using Sony’s XDCAM EX format in FCP X. Sony’s XDCAM Transfer does a great and quick job of re-wrapping the files to *.mov. I’m not sure if XDCAM Browser does the same thing.

    I edit the re-wrapped media in FCP X on my early 2008 Mac Pro with an ATI 5770 card and 24 GB of memory and I have not had any issues. I leave background rendering off as well.

    I have not used Canon’s XF300 format, but when I was looking at it, there seemed to be some issues that needed to be addressed to make it easier inside FCP X.

  • Kevin Patrick

    October 24, 2011 at 11:42 am in reply to: FCPX – Video Stutter Problem After Import AVCHD

    First of all, on my system FCP X averages just over 7 GB of RAM usage. So, if you have 8 GB, this could be your issue. I have noticed others reporting issues, including performance that have gone away for them after upgrading RAM. Some of the cases they have upgraded to 16 GB.

    Also, are you running Lion?

    Have you looked at the Activity Monitor when you’re having these issues? I’ve recently posted an issue about memory usage with FCP X and Lion. At first I thought it was an issue specific to FCP X. But after finding more information on this topic, it may not be FCP X itself. It may be that applications like FCP X simply magnify the issue.

    The issue is that for some reason Inactive Memory usage seems to grow as you use FCP X. In my system, 24 GB of RAM, I’ve had Inactive Memory grow to over 5 GB, quite easily. When you combine this with FCP X’s memory needs it might just explain your playback stuttering. FCP X seems to love memory (being 64 bit I would assume so) and doens’t seem to be happy when it doesn’t get enough.

Page 27 of 34

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy