Keith Koby
Forum Replies Created
-
Agreed. No problems with these prores sources inside of fcpx, only outside.
-
My bad. Ok – so after fcpx or qtx “conversion”, it plays nicely. It sounds like a qt atom type of thing that is not in the non-apple originating prores files.
And as you posted earlier, no problems with these files in fcpx, just outside.
-
An engineer that works for me says he found a thread about mavericks and quicklook no longer using third party codecs or qt to decode.
Doesn’t explain the prores files not originating from fcpx or those over 1GB in file size if those are related to the problem.
Oliver – it surprises me that if you save the qtx converted file, that it too has the quicklook problem. I’m curious if we open a converted file with qtx, will it convert again.
-
QT 7 plays the files. It is installed but it doesn’t affect Quicklooks ability to play or not play the files.
On further examination it looks like fcpx exported files are ok in quick look and qt player x. It’s our source prores files which come from vantage or episode that are the issue.
-
Figured out one relinking problem. Two of the video files had tildes in the file name… Seems link 10.1.1 and/or mavericks has a problem with symlinks with tildes.
So when fcpx upgraded the event and projects to Libraries those files might have been offline already. Second problem, the original was in a sparse disk bundle, so the upgraded library lands there… When we would attempt to copy the Library bundle over to the san “projects” folder, the copy would fail with an error -50 in the finder. From there we jumped over to terminal to copy the Library.bundle over with a cp -RP. The terminal copy gave us the error feedback that these two symlinks couldn’t be copied.
We changed the file names in the finder to get rid of the accented letters. Then we went back to opening the original conversion which lives inside the sparse disk bundle, and relinked those two files to the renamed files. Then the Library.bundle could be copied to where we wanted it, no problem.
-
There’s a major push among IT types to get the datacenter out of their facility and house all data in the cloud (amazon). They have transcoding there. This is different though because it requires a major investment in house. Post infrastructure guys like and dislike this Anywhere idea. I think most post guys recognize we aren’t ready for the cloud as well.
The pros are obvious and for us, with the weather and transit breakdowns, it’s interesting.
The cons are the price tag and that us post guys like to see our actual clips playing to a reference monitor and not flash like proxies on a laptop monitor.
edit: prematurely posted… it happens to everybody. don’t deny it.
-
[Frank Gothmann] “Don’t know, many different labs with presumably very different set-ups and infrastructures. I have seen it also from clients who said it was a simple internal drive to external Firewire drive copy action.”
No I mean at your facility.
-
[Frank Gothmann] “Up till now we thought it was a dropout related to failing error correction on HDCAM-SR decks, bad cabeling, disks etc. but it’s just weird that it’s always Prores QT, always during the first two or three minutes, never in the middle or the end, and that it’s with all big labs happening time and time again under the same conditions. “
Do all of these files hit the same storage? Does the storage have some kind of flash or ssd cache before it hits spinning disk?
-
By the way – I saw something like this a few years back on our old xsan storage where it was one particular drive that was failing but not reporting itself as failing so it would just write a few bad Bytes(?) of data that would give us weird looking artifacts on the prores files. The funny thing is, the problem would only exhibit itself on ProRes HD files. Not on ProRes SD or even on DVCPRO HD or anything else. It was like the chunk of data being delivered to the one particular drive on that raid was just big enough with ProRes HD to trigger the symptom. We wouldn’t see it with smaller data rates written to the same storage. Some of the artifacts look similar to what you are seeing, but we would not get those big green hits. That is definitely more severe than what we saw.
-
Haven’t seen anything here, but we are using xsan. We receive a lot of prores from studios and the various hollywood labs. Every output file gets visually QC’d and we haven’t caught that. (Output vod files with a glitch would prompt us to go back and check the mezz.)