Jump to content

Pixel Shift

bergat

By bergat
in General Discussion

 Share

Recommended Posts

  • 4 months later...
SrMi Apprentice

SrMi

Posted
Posted

I have not heard about any plans. Fuji is apparently planning it for GFX100.

IMO, it is not a very useful feature. I have several cameras with pixel shift and have never used it but for testing it.

Link to post
Share on other sites
  • 1 month later...
matsonfamily Apprentice

matsonfamily

Posted
Posted (edited)

pixel shift results are AMAZING, but seems to be very processor intensive, as does the X-Trans sensor.  I know I've read articles that state this, but I'm taking a guess when I say that perhaps pixel shift with X-Trans together would require a processor newer than the X-Processor4?  Or perhaps some aggressive firmware that slows down the camera to keep heat down?  Even though it's the processor of the X-T3, it's still new enough that they use it in the X-T4.


EDIT: and I agree with @andrei89, that it would very likely require a wider shift to cover the pixel possibilities.  Looking at the Wiki entry, I would guess that the 1/2 pixel shift needed for a minimal pixel shift would require 3 pixels.  So could theoretically require 6x the light that Bayer requires.  Or 6x of some other resource... maybe 3x the light, but only 1/2 of the pixel increase of other cameras.


- just my 2cents

Edited by matsonfamily
Link to post
Share on other sites
matsonfamily Apprentice

matsonfamily

Posted
Posted

@jlmphotos, the xt1_manual in Specifications (pg126) states 4896x3264 (16MP) for single images, and 2160*9600 (21MP) for panorama.  That means the camera can improve it's resolution 31%, and you have the problem of varying perspective (do you raise and lower your tripod?  only works well for very close shots), as all panoramas have.  This is hardly a substitute for in-camera pixel shift (although pixel shift has the problem of increased exposure resulting in motion).  If you're referring to taking separate images and then using an editor to join them, that is quite a lot of extra work, especially for someone who isn't familiar with basic tools.  Image editors are far from intuitive.

On 7/11/2020 at 3:38 PM, jlmphotos said:

If you want higher res, shoot a vertical pano. Just a suggestion as I've done this with my X-T1 for sh*ts and giggles and the results are amazing.

J

 

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing

  • Similar Content

  • Posts

    • jerryy
      Fungus

      By jerryy · Posted

      A fungus in the forest.

      Welcome, dear visitor! As registered member you'd see an image here…

      Simply register for free here – We are always happy to welcome new members!

      (p.s. Open Topic.)  
    • Don Barar
      LUT doesn't works on resolve

      By Don Barar · Posted

      The backslashes you are referring are just symbols denoting path.  Once you import into these LUTS into Davinci Resolve those backslashes are removed by default and you only see is the true file name which has no backslashes.  Convince yourself of this by opening the LUT folder from the Davinci Resolve Project Settings.  Do you see any backslashes in those LUT names? Of course not.  The only name you see is the one that has the underscores and the periods. These LUTS work as designed without having to change any path names.  However, they need to be set up properly through CSTs and by what is supported in Davinci Resolve.  Hence, the FLog2C film simulation LUTS cannot be used because Davinci Resolve does not support Fuji Gamut color space and the FLog2C gamut. Alternatively, Davinci Resolve does support Flog2 film simulation LUTS because the color space for FLog2 is Rec 2020 and there is an FLog2 gamut. If all you are doing is changing the path names then you are not getting the correct results.
    • PoorAlchemist
      LUT doesn't works on resolve

      By PoorAlchemist · Posted

      I found the reddit topic i refere to :  https://www.reddit.com/r/davinciresolve/comments/1pc3f1e/cant_apply_new_fujifilm_gfx_55_lut/ "Update for y'all, It's just like what @ExpBalSat said, it's because of the backslashes in the names break them. I changed the file name and it works now. "   For me it was the solution. Realy annoying if it doesn’t work for you 😕  
    • Don Barar
      LUT doesn't works on resolve

      By Don Barar · Posted

      Here is the solution to using the Eterna 55 file simulation LUTs in Davinci Resolve.   In general, do not use the FLog2C to film simulation LUTs as they are not supported by Davinci Resolve for two reasons: 1) Davinci Resolve does not support Fuji Gamut Color Space and 2) Davinci Resolve does not support FLog2C gamma.  Instead, use Flog2 which is supported by Davinci Resolve.  Here is an example.  Let's say that you want to use Classic Chrome simulation.  Do the following: Complete your color grade and use a CST to get to Rec 709. Add a node.  Use a CST to convert from Rec 709 to FLog2.  Output Color space is Rec 2020 and Outout Gamut is FLog2. Add a node.  Apply the FLog2 to Classic Chrome LUT Create a combination node from node in steps 2 and 3. Apply a Key to the combination node and adjust the Key Output Gain to get the amount of the combination node that you want applied. So that you do not have to do this over and over again, generate a LUT for the combination node.  Remember to turn off all other nodes before generating the LUT. Hope this helps others. Don  
    • crazyfields
      Please save me from insanity 23mm f2 vs F1.4r

      By crazyfields · Posted

      Thanks for the insights. I think it's really hard to make a decision without having the two side by side! 
×
×
  • Create New...