Jump to content

DigitalOxygen.ca

Members
  • Content Count

    4
  • Joined

  • Last visited

About DigitalOxygen.ca

  • Rank
    New member
  1. Honestly so far I'm not sold on it. On paper it seems amazing and in lots of ways it is, but practically speaking for me it's not a game changer... yet. Being limited to odd crop sizes and limited frame rates (i.e. hard to get decent res at 60fps) is not great. Fully understand the hardware limitations all the ML contributors have to work with. The effort and ingenuity being put in to work around the limitations is amazing but I need more time with it to see if the downsides and extra workflow elements is worthwhile for me. So far it seems like if the scene is exposed properly there isn't a massive noticeable difference in the final footage with raw vs the default h.264. But again I need more time to fine tune the settings and figure out the best workflow.
  2. I played around a bit more and noticed that in a particular view of the resolutions it said something at the bottom about using left / right on the directional pad to fine tune the adjustments. I'm not near it at the moment so don't recall the wording or which screen it was on (it wasn't all of them that allowed resolution adjustments, just one I think). The directional buttons allow you to cycle through the "in between" resolutions.
  3. I have this same question. Most of the examples I see online show resolutions I don't seem to be able to get even with the experimental 10-bit builds. For example this article on this very site shows resolutions like 1792 x 762 on the 6d and even 70d. I finally discovered it's with experimental builds for 10-bit but even with that neither camera can do continuous above 1600 x 680 give or take. In most of the sources there doesn't seem to be mention of the sd_uhs hack so I feel like I'm missing something somewhere. Any help would be very greatly appreciated.
×
×
  • Create New...