Todd Beabout
Forum Replies Created
-
We are having a similar problem with a GRaid2 drive on one of our systems. Are you by chance on Tiger?
The only way to correct the problem that we have found is a reboot. Seems to work fine after that, but is annoying for the editor for obvious reasons.
For us, when this happens we can’t even create a new folder from Finder. Is this the same with you?
-Todd Beabout
Vazda Studios -
Kevin,
We resolved our problem here and I wanted to post back what worked for us.
We gave the problem edit suite access to a different drive partition, and the problem went away. Thus we determined that the partition he was writing to was corrupted.
You might want to try to repair permissions on the drive you are writing to, or when time permits you might want to reformat the drive altogether and start over.
Hope this helps.
-Todd Beabout
Vazda Studios -
Hey Simon,
I just wanted to follow up with you because we finally resolved the problem.
We had a corrupt volume that this edit suite was writing to on our Terrablock. We gave that user access to a different partition and the problem went away.
I noticed that you were using a Huge array, but you might try either repairing permissions on that partition, or when time allows, you might want to consider reformatting the partition that you are working on.
I only mention this because the screenshots that you posted are look exactly like what we experienced.
BTW, nice work you do over there. Cool website too.
-Todd Beabout
Vazda Studios -
Just wanted to post back because there is another thread relating to this same problem here:
https://forums.creativecow.net/thread/8/987007
Simon, any luck resolving the problem on your end?
-Todd Beabout
Vazda Studios -
Hi,
This problem is very, very similar to one that we are experiencing here on one of our FCP suites. It has been discussed, but not resolved, in this thread:
https://forums.creativecow.net/thread/8/995096
Kevin, your description exactly matches what we are experiencing. One major difference is that we are actually getting these glitches on any 10-bit uncompressed, HDV, DV, basically any type of footage.
The glitches come and go at random, and are visible even in QuickTime when we open the source clip.
We are using Terrablock shared storage, AJA card for capture (LHe), newest version of QT, FCP 6.0.3, and his box is running Tiger.
Ummm… I guess that is about it. I’m about to install the latest Facilis server/client update just to rule that out, but it seems like a problem there would be affecting the other suites running from the same Terrablock.
-Todd Beabout
Vazda Studios -
Our footage is SD NTSC 29.97 from BetaSP and/or D-beta source captured through a Kona LHe component (beta) and SDI (d-beta). We also had the exact same problem yesterday with some HDV 1080/60i footage captured through FireWire into it’s native codec.
The same clips captured in a different room are OK. This problem is very, very weird.
The only other factor I can think of is that this problem box is running Tiger. We have 2 Tiger boxes and 2 Leopard boxes, but it doesn’t really seem like the OS would be affecting clips at random on just one of the Tiger boxes. We are planning an upgrade on these to Leopard soon anyways, so I’ll let you guys know if that for some strange reason cures the problem.
Jeremy, I haven’t tried the Cinema Tools thing yet but I will try to get in that room and reconform the clips to 29.97. That is if the glitches are there today. So strange…
-Todd Beabout
Vazda Studios -
Jeremy, our sequence is standard 525 NTSC 29.97. We are using ProRes 422 as both clip and sequence settings, even though I tried changing the sequence settings to 10-bit uncompressed to no avail.
ProRes is something that is newer to us, but we have switched over to doing a lot of projects in that format due to small file sizes, and fairly lossless quality (or so we thought).
I’m going to be trouble-shooting this one for a few days, so I will post back if I come up with something, Simon. I am kinda glad that this problem is happening somewhere else, only because 2+ people troubleshooting is certainly better than just me.
Simon, it also sucks that it appears the QuickTime update won’t fix the problem.
Let me know if you come up with anything.
-
One more thing…
Tried to switch the sequence to 10-bit, and problem persisted.
-Todd
-
We are also experiencing a similar issue here on our systems. Well, one particular workstation really.
These glitches appear completely at random, and not just on the external monitor, but in the Canvas, Viewer, and even in QuickTime when I open the source file.
Blowing the render will sometimes make the glitch go away, but then when we re-render it will show up somewhere else in time, and even another part of the screen. There might be more or less glitches each time we render, it’s a crap-shoot.
I’m going to update that workstation’s QuickTime version to 7.5 (on 7.4.5 now) at the end of the day today and hopefully that will help, but who knows.
It might be worth mentioning that we are running 4 FCP suites off a Terrablock shared storage. In this guy’s room there was a glitch on his screen (canvas). I match-framed it into the Viewer and the glitch was still there. Then I used “Reveal in Finder” and opened the file in QuickTime. Glitch still there. Then came into my edit suite and opened the QuickTime file. No glitch. Hmmm. Went back to his room, and the glitch has disappeared from his FCP project, but was STILL present on the source QuickTime that was open on his box. Shut QuickTime, reopened file and it was gone.
Baffling. Any thoughts?
I’ll let everyone know if the QT update helps. We are on FCP 6.0.3 BTW.
Thanks!
-Todd Beabout
Vazda Studios -
You will need a capture card that supports uncompressed input, such as an AJA Kona or Blackmagic card. Then you will need a DV deck that either has SDI or component out (this will need to match the input of your capture card).
Hook them up together and Final Cut will do the rest.
Of course there is a bit more to all of this, but that is the short answer.
-Todd Beabout
Vazda Studios