Mike Kahn
Forum Replies Created
-
Any chance you are rendering to and Avid Unity? This was an issue with one of the Unity drivers and has since been resolved with an update.
-
Can you give any more detail? What are your sequence settings, how are you compressing..
-
Try creating a new user account and opening FCP. Sometimes there are preferences that go bad that you don’t know about and simply creating a new user will fix this issue. If it does fix it, you can copy your files from one user to the other and delete the bad user.
-
If you are coming from tapeless media, you could do it two ways.
1) output to tape using a card to do the cross conversion and reingest
2) compressorMPEGStreamclip is a great program but won’t give you the best results IMHO.
-
Can you try using some other XDCAM media to see if it’s FCP or if it’s your media? I would try trashing the prefs, repairing permissions, etc. All that before a clean install of FCP. Usually it does not have to come to that.
-
FCP can only use 2g of RAM no matter how much is in your machine. It is recommended that you have at least 4g to use uncompressed HD so that the machine has 2g and FCP has the full 2g.
This is because FCP is still a 32bit program and 32bit programs can not use more then 2g of RAM ever. Once FCP goes 64bit then all that RAM can get utilized.
-
Have you tried using the “Non Controllable Device” setting? Choose your capture setting, ProRes422, and hit capture in the log and capture window.
-
Thanks Shane. I exported a self contained QT and placed it into the 59.94 sequence. The timings seem to be correct. I think I will continue with the 29.97 timeline for the majority of the episode and use this method simply for the credit bed and scroll. Much less confusing when having to do timings with producers and if anything has to be changed I won’t have to keep remaking the long self contained QT.
-
Lawrence,
Did you ever solve this problem? I am having the same issue. I do not have a blackburst gen hooked up as this is simply an edit machine. I get crackling sounds like you described intermittently and randomly through my speakers while editing. I have switched out my audio cables, audio mixer, and speakers and have narrowed it down to the card itself.
Mike