[Bill Wilson]

Stefan, et. al.,
I just spent over an hour online with Apple Support regarding this issue. I went through all the obligatory “tests”. The resulting conclusion by Apple: It is a driver problem with the DeckLink product and I should call them (which I did first, by the way). Never mind that the problem exists regardless of whether it,s DeckLink, Kona, etc., or all the posts from users in Apple’s own form with the same problem / different I/O device, or the fact that everything worked perfectly until upgrading to Color 1.5. The tech would see no other option other than the DeckLink driver option. Furthermore, the Apple tech would not suggest a card to use that Apple would support. They only support the cards installed in the machine at purchase…which doesn’t work…and they say isn’t the problem. Purchasing a new graphics cards for my edit stations seem to be the only (expensive) answer according to the good folks on these forums, but then I have a system configuration that will not be supported by Apple (I am in the apple care program) according to the tech. The general public can not purchase the graphics cards currently being installed by Apple. I think it’s the GT200 series. I am very frustrated with Apple right now. How does one get past the online tech to talk to someone with at least a partially open mind?

Bill Wilson
SunDolphin Productions
Birmingham, Alabama

[Bill Wilson]

Add me to the list. Same problem with no video out using Color 1.5. I am using BlackMagic DeckLink HD Extreme. Worked fine until the FCS3 upgrade. I have the latest DeckLink software installed. This little problem is really backing up my edit log. Any resolution found by anyone?

Bill Wilson
SunDolphin Productions
Birmingham, Alabama

[Bill Wilson]

Hey Adam,
Thanks for your input. In my case, the files did have the .mov extension when I found them in capture scratch. And the every third clip anomaly is a real head-scratch-er. At any rate, I’ll continue to try to find the root cause. I will be sure and post it when I find it.
Thanks again.

Bill Wilson
SunDolphin Productions
Birmingham, Alabama

[Bill Wilson]

Hey Rafael,
Yes. I exported to QT and even carried the process all the way to DVD and the anamolies presisted. Deleting the render files, turning off the external video, re-rendering ALWAYS fixes the problem. A response from the Apple site forum suggested checking driver versions for the HD Extreme.

Bill Wilson
SunDolphin Productions
Birmingham, Alabama

[Bill Wilson]

I posted this in another thread, but it seems to apply here also:

I am just a FCP user and not familiar with the FCP code itself. However, I think the problem is, in fact, a memory leak. A “memory leak” happens when an application begins executing and starts reserving chunks of memory from the free memory pool. The applictaion keeps this memory reserved until it finishes, at which time it should release the reserved memory back into the free memory pool. If the application code does not cleanly release this reserved memory back into the free memory pool, it remains in the reserved memory pool indefinately. Thus, it appears to the system and all applications running on it that the amount of physical memory diminishes over time, hence the phrase “memory leak”. The only way to release this memory back into the free memory pool is to reboot the system.

I notice in the activity monitor that the “blue” memory slice (inactive memory) continues to grow the longer FCP is executing as the “green” slice (free memory) continues to shrink. The memory in the blue slice is “inactive” but is not available for use. Heavier renders requires FCP to reserve more memory. The next time a render is required, FCP reserves yet more memory from the free pool. After quitting FCP, the activity monitor still shows a very large blue slice (i.e. this memory is not released back into the free memory pool).

The symptoms described by some FCP users, along with the output from the activity monitor is certainly consistant with the notion of a memory leak.

As far as I know, there is nothing we as users can do to manage this other than periodic reboots. As mentioned in the post above, you can delay the symptoms by adding more memory, but the problem still exists and will eventually catch up with you.

As a side note, I also seem to notice that as the memory leak situation progresses on my MacPro, I begin to see unexpected results in render output. If I delete render files and reboot, all render outputs are as expected. Whether this is a symptom of the memory leak issue, or something else, I don’t know.

Bill Wilson
SunDolphin Productions
Birmingham, Alabama

[Bill Wilson]

I am just a FCP user and not familiar with the FCP code itself. However, I think the problem is, in fact, a memory leak. A “memory leak” happens when an application begins executing and starts reserving chunks of memory from the free memory pool. The applictaion keeps this memory reserved until it finishes, at which time it should release the reserved memory back into the free memory pool. If the application code does not cleanly release this reserved memory back into the free memory pool, it remains in the reserved memory pool indefinately. Thus, it appears to the system and all applications running on it that the amount of physical memory diminishes over time, hence the phrase “memory leak”. The only way to release this memory back into the free memory pool is to reboot the system.

I notice in the activity monitor that the “blue” memory slice (inactive memory) continues to grow the longer FCP is executing as the “green” slice (free memory) continues to shrink. The memory in the blue slice is “inactive” but is not available for use. Heavier renders requires FCP to reserve more memory. The next time a render is required, FCP reserves yet more memory from the free pool. After quitting FCP, the activity monitor still shows a very large blue slice (i.e. this memory is not released back into the free memory pool).

The symptoms described by some FCP users, along with the output from the activity monitor is certainly consistant with the notion of a memory leak.

As far as I know, there is nothing we as users can do to manage this other than periodic reboots. As mentioned in the post above, you can delay the symptoms by adding more memory, but the problem still exists and will eventually catch up with you.

As a side note, I also seem to notice that as the memory leak situation progresses on my MacPro, I begin to see unexpected results in render output. If I delete render files and reboot, all render outputs are as expected. Whether this is a symptom of the memory leak issue, or something else, I don’t know.

Bill Wilson
SunDolphin Productions
Birmingham, Alabama

[Bill Wilson]

We have been shooting with HD100UA’s (HD100 with the “A” formware upgrade) for about a year and a half. JVC representatives told me this is the same as the HD110. We have been using the Panasonic Master Quality the entire time. The reason we chose this tape is because of the dry lubricant used. As far as I know, they are the only ones using a dry lubricant. We have experienced a few frame drops, etc., but that is over a couple hundred tapes. We have ecperienced no reason to change the tape we use.

The recommendation to stick to one tape brand is a good one. Each time a tape is used in your camrea, it leaves a small about of the lubricant on the head. The problem with mixing brands is that different makers use different lubricants. Many times, these lubricants do not mix well causing problems on the heads.