Eddie Kesler
Forum Replies Created
-
Just did. Wanted to make sure there was no other way first or that I was missing something on my end.
-
Thanks, David. I just tried it and Adobe ME says that “The source file appears to be corrupted. Please check that it is a valid file.”
Any other ideas??
Thanks,
Eddie -
-
I’m having a similar issue. I have a folder that contains several folders that each contain original QT H.264 files captured from a Canon 5D. It won’t let me bring them in using Log and Transfer. I downloaded what I hope is the latest release (CE1120X). It tells me:
“‘Ogilvy Atlanta_Zoosk Effie Video Files’ contains unsupported media or has an invalid directory structure. Please choose a folder whose directory structure matches supported media.”
The “Ogilvy…” folder is top-level directory that contains each Scene folder and the Scene folders contain the .MOV, .WAV and .THM files. Any ideas how to import this footage and make it ProRes422? I can use Compressor if need be, but I thought Log and Transfer was the way to go.
Any ideas? Thanks.
-
I did. It took me to the same page I was trying to find the plug in on. It doesn’t list it under MacOS. Is it embedded in one of those drivers?
-
-
Thanks Andreas. Sounds like there’s more to work out with the Alexa. I just wasn’t sure if it was FCP or ARRI being the culprit. I guess we’ll go through the same growing pains as we have done with the RED and every other new digital camera.
Along with the new non-linear Color Correctors and just finishers like Flame, etc.. using Media Manager would be an asset for this workflow. I hope we can get it to work.
Please post if you hear of any developments with the Alexa. We are strictly a post house and aren’t always brought in the mix for on set technology until it’s too late. If the producers would understand how much smoother the process would be if we could just have an extra conference call or two up front. In the film to SD only world we used to live in, things were much easier!
Thanks,
Eddie -
[Jeremy Garchow] “This is a mess. So you are saying that you can’t see ANY of the original Alexa files? They all have a -v?
Yes. Along with a sequence # for those that have duplicates.
(i.e. A004C001_101208_R1TZ-v
A004C001_101208_R1TZ-2-v)[Jeremy Garchow] “I don’t see how camera firmware is going to fix double system sound. “
Me either, but that’s what they said. Remember, it’s all digital.
[Jeremy Garchow] “This is all starting to sound like everything was mishandled as soon as the camera was turned on.”
Not necessarily. It’s a brand new camera and technology. We had issues with footage from RED when that first started to hit a couple years ago. Many of those issues are worked out. This was a big-budget shoot from a highly-reputable, LA production company. Not that we haven’t had problems in the past with other technologies or prodcos, but it wasn’t a bunch of amateurs.
[Jeremy Garchow] “Do you still have the original 4 drives and the separate audio?”
Yes, but it’s all been consolidated into my RAID at the beginning of the job last month. Once the sync issues were resolved, there really hasn’t been too many issues. The only other thing is that in my dynamic trimming of the merged clips in the timeline, it would offset what frame I was seeing in the trim window by 9 or 10 seconds. I worked around it, but it was annoying.
-
Most clips are merged, but there are several that were shot MOS and some is Phantom Footage that came from a different prodco with no audio. The Phantom files show up with thumbnails in the finder and open in QT easily. The rest do not – merged or not merged.
I think that the renaming at the end of all these clips is part of the reason that the colorist can’t import them. The other issue is the fact that FCP is giving me the #34 error on all the Alexa files.
As far as the audio, the prodco who shot the footage confirmed that there is a bug with the video and audio files being out of sync after we alerted them to the problem. They said there’s a patch for the camera that should fix it from here on out.
-
That’s not it. I have tons of files over 4GB on here already.
It’s not that I mind giving him 66GB of footage, but it’s a lot of leg work to manually look through the edl and find each take. Plus, I don’t want to miss one, etc… Media Manager’s function is made specifically to do this task, but something’s not working properly.