Jump to content

androidlad

Members
  • Posts

    1,213
  • Joined

  • Last visited

Everything posted by androidlad

  1. Report this issue to Nikon and see if their engineer can replicate this https://www.nikonusa.com/en/about-nikon/contact-us.page
  2. It's Nikon proprietary, non-standard DC connector
  3. Your vintage lens is too soft to trigger edge detection algorithm. Try setting "sharpness" to +4, stopping down and shoot something with fine texture.
  4. GH5s outputs maximum 60fps in FHD and 4K.
  5. It's unlikely to go beyond 12 stops in V-log, this is a stills-oriented camera that operate using 12bit ADC in video mode. Heavy NR also tricks the image analysis software for cleaner shadows (more absolute DR in shadow but not very usable).
  6. To get beyond 12 stops DR the sensor ADC has to be at least 14bit or dual ADC readout. The power consumption and heat management are simply not feasible in a mirrorless stills camera form factor.
  7. Portkeys/IKAN has one, brighter at 1500nit, similar feature set and quite a bit cheaper at $279 https://suikui.myshopify.com/products/lh5-hdr-5-1500nit-4k-signal-support-touch-screen-1920-x-1080-hdmi-on-camera-monitor-with-hdr
  8. It's a hardware limitation, simultaneous HDR has only started to appear in small sensors for automobile use: This one does 20 stops tone-mapped.
  9. XC10 and other Cinema EOS products use DIGIC DV processor, while EOS DSLR/R/RP use regular DIGIC with stills JPEG engine, MJPEG would be the natural choice.
  10. Removing the 29:59 limit via firmware upgrade would require new serial numbers for every camera sold per EU law. Technically it's doable but logistically nah.
  11. 12bit sounds sensational eh? In reality 12bit linear RAW wastes too much bits in highlight causing shadow area to exhibit artifacts. In many case 10bit log actually delivers better results than 12bit linear.
  12. Rolling shutter is 20ms in 4K which is ok but definitely not little. 1080 120p is not oversampled in either cameras but a combination of vertical lineskipping and horizontal pixel binning.
  13. Or use higher ISO for the noise to dither some of the banding. F-log offers between 11-12 stops based on your tolerance for noise.
  14. Internal 8bit F-log won't be useful for serious work. X-T3 has banding problem even in 10bit.
  15. Official X-T3 V3.0 firmware announcement: http://www.fujifilm.com/news/n190214_06.html Camera Remote V4.0 app announcement: http://www.fujifilm.com/news/n190214_06.html To submit feature requests/bug reports about Fujifilm cameras, please contact Fujifilm directly at: http://www.fujifilm.com/contact/
  16. Canon calls it DS, Sony calls it STF, Fuji calls it APD. Basically makes bokeh outlines smoother than regular lenses.
  17. DPAF is the AF technology at hardware level, it's a variant of Phase Detection AF (PDAF) that Sony implements as masked pixels. What Sony did was a significant algorithm overhaul, it's a software feature hence can be realised with a firmware update. Theoretically Canon can do the same.
  18. You can go directly to 2.10, Fuji firmware updates are cumulative.
  19. FYI in that test, X-T3 was set to factory default setting and the measurements were done with an in-camera JPEG (Provia).
  20. It's nothing to do with Ninja. It's the way Fuji cameras encode video files with confusing metadata that causes the discrepancy. Ninja recordings show the correct colour, the video level just need to be changed to full instead of limited.
  21. 4k60p crop is 1.18x, with v2.0 firmware the crop factor is displayed on the top left corner.
  22. Exactly. The confusing colour metadata tags cause the Fuji internal files to be decoded incorrectly, it doesn't matter if it's video player or video editor. Open a file with MediaInfo and you'll see.
  23. Apply "Rec709toRec601.cube" LUT to Fuji internal files from this pack: http://www.pantarheon.org/601vs709luts.zip Root cause of this problem:
  24. There was a lengthy discussion/investigation regarding this issue. The conclusion was Ninja files show the correct colour. Fuji internal files are handled incorrectly by certain applications including Premiere and Resolve (version dependent) due to confusing colour metadata tags. Reds turn orange and greens become darkened. In high end finishing tools such as Baselight and Scratch, the files are completely identical.
×
×
  • Create New...