Phillip Todd
Forum Replies Created
-
Hi Mike,
+1 to what Bill Bruner said.
I sold my 7D due to moire issues and bought a hackable GH1 many moons ago. I progressed on the the GH2 and have been very happy. I don’t have plans for the GH3 until I can get one side-by-side (and the time) and can check out if the lack of moire is as good as the GH2 (the GH3 has a Sony sensor, different than the multi aspect ratio GH2 sensor). There are a lot of desirable features on the GH3. the 12-35 f2.8 looks good too.
I will add that the shorter flange focal distance of the MFT format (and the NEX format) allow you to use a multitude of 3rd party manual focus glass via cheap adapters (inf. is usually off, but, you’ll focus off the display, so it’s less of an issue). This opens up many creative opportunities as older glass achieves different looks out-of-the-box in a way filters in post cannot (easily).
A final note: DSLRs have CMOS sensors and have a rolling shutter. This makes handheld telephoto shots look like you were shooting off a boat, or any shot with a little vibration, and there’s not much in post that can fix it. CCD based video cameras have a global shutter and you don’t have this problem (nor the advantage of the CMOS sensor).
Phillip Todd
Cinematographer -
Hi Dave, is that a 2008 MP 3,1 8 core 2.8 Ghz Machine?
I am running that machine with 10.7.5, a GTX 470 1.25 GB non flashed and find adding effects or exporting GH2 AVCHD footage slow in FCPX 10.0.6. Ca. 1 minute render for 1 min. of 1080 24P footage. FCPX does not give me a warning that the GPU does not support the program. I have a 2009 17″ laptop with a supported nvifdia mobile GPU and there the app “AtMonitor” shows me that the GPU is rarely being taxed by FCPX 10.0.6. I am even thinking 10.0.5 was faster, even though I know 10.0.6 is supposed to be faster.
I have Open CL enabled and get a Luxmark score of 978. Luxmark taxes the video card and I can monitor it with an app called Zeus: temp goes up and the gpu fan spins faster, much faster. I am noticing that FCPX renders & exporting do not tax the gpu, nothing makes the fans spin up.
I read somewhere on the net that the Open CL implementation in Nvidia cards may not be as good as in AMD cards (like most macs have).
I am wondering what your experience has been…?
I am wondering if Premiere might be faster. I know there have been comparisons, but, my gut says I am either expecting too much, or something is amiss in my (like yours) unsupported set up.
Thanks for your thoughts
Phillip Todd
Cinematographer -
Perhaps a quicktime on windows problem…? If there is anything to update, install the updates and try again.
I am just curious as the more complex these programs get, the more basic things sometimes get broken, like sync. Interesting.
Report back if you find a solution.
Phillip Todd
Cinematographer -
If the sync is slipping further and further out-of-sync, I wonder if the flags in the Quicktimes are correctly set (within the quicktime files themselves). There was a discussion about it here (in a FCP7 environment) and how to fix it so FCP7 would see it correctly via editing the XML data. https://library.creativecow.net/lyon_matt/fixing-fcp-assets/1
The relevant part about editing the XML data starts on page 2.I experienced this problem with Qucktime in MacOS 10.5 running FCP7, the problem was unknown to me, but my workaround was to change the audio speed of each sound clip to 109% (not ideal, or, recommended). I figured this was because my 23.976 footage was being interpreted as 24 fps in the audio track (all audio was 16 bit 48KHz). When I upgraded to OS 10.6 it was fixed in the same FCP7. So I believe it is a quicktime issue. I don’t know if there is a QT upgrade for you on the PC, or if Premiere relies on the QT sub-programming/sub-framework the way FCP7 did.
In any event, this may be a clue to help you solve the problem. The old QT 7 had it’s problems even on the mac, perhaps they didn’t get around to fixing it on the PC version, or, there is an update you need to apply. QT 10 is better but has provided me with some new mysteries.
Hope this helps
Phillip Todd
Cinematographer -
Thanks Gabriel
-
-
I am still on FCP 7 and am trying to decide on Premiere CS6 or FCPx (I do a lot of multicam). All this to say I do not know the problem but have read about the issue (if this is the right issue)
From:https://www.eoshd.com/content/8612/mac-avchd-gamma-issues-the-fix
topline:
“The fix
In Premiere Pro, the specific part of the Fast Color Corrector you need to apply the fix with is the Output Levels.
Keep the Input Levels at 0-255 but change the Output Levels to 15-235.”
Let us know if it works for you.
Phillip Todd
Cinematographer -
I agree with everything said above.
And here is a beta tester report of FCP 6.0.6 on ML:
https://forums.creativecow.net/thread/8/1162499I am still a skeptic.
Phillip Todd
Cinematographer -
Thank you for the tips David!
-
I did what David Eaks suggests for a client. I had 2 hours of 1080P footage. I added timecode since they would select the sound bites out of long speeches that they wanted. Generating the TC overlay using my 2009 17″ MBP (at the time my only editing platform) took a lot of render time, fans on full blast, then the compression for the web using QT7 (I was still using 10.5), a lot more time, fans on full blast.
Long story: I now have a MacPro as an edit platform and am wondering how well this will go if I have to do it again. The client liked the convenience of it, so chances are I’ll have to do it again.
I posted it on Vimeo and password protected it, lots of upload time, etc.I did learn that QTX was a lot faster than QT 7 to do the compression, and later that compressor would have been even better. I am currently on 10.6 and QT 7.
Phillip