Jump to content


  • Content Count

  • Joined

  • Last visited

About AccordingToMe

  • Rank

Profile Information

  • Gender
  1. ​It was present on h.264 export, a very common way to output files, I'd say. ​I had not seen the follow up post. It's good to know that Adobe reacted quickly and was able to solve that issue. It seems that any project output after Octobersih 2014 won't need to be re-exported.
  2. Also, be advised about: The quality difference between FCPX and Premiere Pro output
  3. OK. To me, laying out material, and working with the magnetic timeline, is exponentially faster than any other "classic" editor based around the 'source/record windows'. Also, I much prefer the organizational features in FCPX compared to DaVinci Resolve. And seeing that you answered "Yes. Yes": why on earth are you going via 3. party converters to get to ProRes?
  4. ​Before answering your question: are you on a Mac? Do you know FCPX well?
  5. Import into FCPX, start working while media is still being copied from CF card. Simultaneously auto convert to 4k ProRes 422 in background by FCPX, as well as 2k ProRes proxy. Optionally let your converted 4k ProRes files replace your originals to save space. Optionally flip a switch in FCPX to enter proxy mode. Transfer whole project to 2.5" USB3 drive and edit on MBP Retina, or MBP Air for that matter. Easy .xml round tripping to Resolve with presets for FCPX already in place. Support up to UHD resolution free with Resolve Lite. I am an active Creative Cloud subscriber. I wouldn't dream of u
  6. It does seem nice. Most of all, it seems to have a good price/performance ratio. I've done a super quick research and most seem happy with it. I'll check out Dell's UltraSharp next and see what differs. Daisy-chaning will drop the monitor to 30Hz, so that won't work. I have a R9 280X 3GB in my MacPro and it should be able to drive two of these. While super high end monitors are nice, I've always thought that it's a high price to pay since everyone else will be watching whatever you create on a consumer monitor/TV (in most cases). Like most review say: ticks the boxes 60Hz, SST with good gamut
  7. Well, two of these side by side—daisy chained—for $1400 sounds kind of nice. But historically, the good 24" 4k panels have been around $1300. It's always good to know where the money is being saved...
  8. ​An image can't be more flat with crushed shadows. When people say crushed shadows they mean "crushed down", as in turning dark gray areas completely black. Crushing the shadows makes an image more contrasty and punchy, often with the purpose of removing the dark, noisy part of the image by sending it to black.
  9. ​It's in the Canon Log white paper. I don't have the direct link, but it should be easy to find with google. Highly recommended reading if shooting Canon Log. Canon has released many white papers on the Cinema EOS system. Reading them will probaly increase one's understanding of Canon's philosophy towards sensors, cameras and lenses. Remember, Canon Log has been out for a long time. It's been thoroughly discussed and examined online. ​In their documentation of the Cinema EOS system, Canon describes the C300 as a quick-to-market product. They had to use Digic DVIII and went with a mpeg-2 codec
  10. ​OK, thanks. The fact that you can't go below ISO200 suggests to me that there is something similar going on. It dosen't really matter what it is, but my understanding is that Sony recommends quite high ISOs with the log profiles, correct? ISO3200 even? And then the community has landed somewhere below that at maybe ISO2500? I'm grasping here.... not really following Sony... As anecdotal as it may seem, I also can't help but noticing that for filmning, looking at the "money making" ISOs from ISO400-6400, the DR is for all intents and purposes identical between the A7s and the 1Dc (according to
  11. ​Yes, do the thinking up front. Applicable to many scenarios.
  12. ​My own analysis of Canon Log is that when put the 1Dc in Log mode (which is a special MODE in the camera, not just a picture profile) the raw data is pulled by 2 stops. The ISO400 then boosts the image back up again, according to the Log curve. If you put a 1Dc in Log mode and ISO below 400, you will never reach IRE 100, no matter how you expose. The data is pulled. It is equivalent to highlight protection mode. It makes sense for non raw recording. Take 10 clean base stops and add 2 "ISO stops" and you end up with 12 stops, even if DxO only measures around 11.8 for 1Dx raw. Sony does the sam
  13. Oblivion comes to mind. That is a movie I can watch just for the visuals and the soundtrack. Shot on F65: There are many beautiful shots in this movie. Naturally there are many computer generated images as well. But I remember sitting up straight in the theater during the scenes around the provisional lake cottage.
  14. ​Lot's of photographers can make it work and still plenty of people do complain about it. Or rather, they even complain about the DR of 1Dx raw. And there isn't such a thing as a "1Dx jpeg". If you compare a PP 'neutral' with contrast all the way down to a PP 'EOS standard' with default contrast, the difference might be even bigger than what you show here. What settings did you use for your jpeg? What people need to understand is that there is a tug-of-war between DR and tonal reproduction. Especially in 8 bit. I can somewhat understand the greed for DR when you shoot raw. But when we shoot to
  • Create New...