Personal View site logo
Z-CAM E2 camera is coming with 4K at 120fps
  • 286 Replies sorted by
  • Just released New beta firmware suppose to have increased the DR to 15 stops ? When I questioned it on facebook group . They simply replied with "We are Z cam we can do it "

  • I have no way of knowing how much experience they have with that sort of thing. In the meantime, without LIDAR, they are working on having human detection for focus and the posted videos look decent if mildly laggy.

  • They are also talking about a lidar module for autofocus and combining that with built-in support for the API for some company's electronic focus puller.

    I am not sure if they know LIDARs really good. As making it work is around 100x harder than it seems.

  • Jason has lots of interesting side projects going. They are also talking about a lidar module for autofocus and combining that with built-in support for the API for some company's electronic focus puller.

  • Check

    https://www.facebook.com/Jasonzhangfan/videos/10217536213944168/?tn=C-R

    “Yes, this is the new virtual reality,” Zhang writes.

    “Built-in real-time facial beauty feature,” Z CAM writes. “Do you want it in [the] Z CAM E2?”

  • The ProRes bitrate on the E2 is a lot higher than h.265, as one would expect.

    ProRes 422 and ProRes HQ are only available at 4kp24 or 4kp30 right now. ProRes LT is available at up to 4kp60. 4kp120 is h.265 only.

    These limits are all based on how much data they can write to the card.

    Also, I don't think the engineers have committed to supporting 720p360 yet (and who cares, really?)

  • Z-CAM E2 / 3840x2160 / 4K 120p / 1768Mbps = 221MB/s ~H264/265 4:2:0

    Z-CAM E2 / 3840x2160 / 4K 60p / 884Mbps = 110MB/s ~ H264/265 4:2:0

    Z-CAM E2 / 3840x2160 / 4K 30p / 442Mbps = 55MB/s ~ H264/265 4:2:0

    pros : 4k 120fps 2k 240fps 720p 360fps(not yet?), small size, cheap and long life battery, 16stop DR Mode

    cons : monitor, low bitrate, not yet prores 422hq

    BMPCC 4K / 3840x2160 / 4K 120p / Not support

    BMPCC 4K / 3840x2160 / 4K 60p / 1760Mbps = 220MB/s / Prores 4:2:2 HQ

    BMPCC 4K / 3840x2160 / 4K 30p / 880MB/s = 110MB/s / Prores 4:2:2 HQ

    pros : 12bit RAW, huge bitrate, Blackmagic RAW(not yet), Intraframe compression codec(prores)

    cons : battery life, ugly size, crop 1080 120fps, RAW need external SSD.

    GH5s / 3840x2160 / 4K 120p / Not support

    GH5s / 3840x2160 / 4K 60p / 150Mbps = 18MB/s ~ H264/265 longGOP 4:2:2

    GH5s / 3840x2160 / 4K 30p / 400Mbps = 50MB/s ~ H264/265 ALL-Intra 4:2:2

    Is that correct?

    Is it possible that the bitrate increase on Z-cam e2 after prores 422 codec firmware updates?

  • ... and with a much easier hack (file on the memory card vs manually edit config files), my camera is now fully enabled for ProRes. It looks like the current firmware supports ProRes LT/422/HQ at up to 4kp30 and ProRes LT at 4kp60. Not bad! Too bad it'll be fairly dark by the time I'm done with my day job for today...

    prores enabled.jpg
    960 x 720 - 29K
  • After a little bit of hacking based on what I mentioned above, I can now confirm that ProRes code is done and in the camera, but waiting for some feature flag to be turned on.

    The "hack" persists between power cycles and a number of menu / settings changes, but will be instantly reset to h.264 if you make the mistake of going into the menu to choose h.264/h.265/etc. So far, in NTSC mode, the camera also only claims h.265 for 60p, but that might be different in PAL or CINEMA mode. I haven't taken a lot of time to play with it yet.

    Someone with more experience decompiling code might be able to figure out what flag needs to be present to enable the option in menus. I just made a guess at a config file setting based on the order of entries in the strings of the binary.

    prores menu.jpg
    960 x 720 - 40K
    prores_works.jpg
    1200 x 579 - 209K
  • 422 is useful for keying

  • They say that the code for ProRes is done, but they are awaiting license approval. I think that one of the Z-Cam people mentioned before that they will support ProRes 422 and ProRes HQ at up to 60 fps. For 4kp120, H.265 is the only promised option.

    Raw still hasn't been promised - and in fact, historically they've said they had no plans to support it. Jason Z said late last week that he was reconsidering that and that some form of raw may end up happening. I wouldn't bet on it happening any time soon, though.

    FWIW, the 10-bit 120 megabit/second h.265 that the camera already does is pretty darn good, even if it isn't the most efficient codec for editing on an older system.

    The improved monitor compatibility and lens support fix my two biggest gripes, really. Once they add ProRes and make CAF better (it currently doesn't do anything at all unless using the phone app, as far as I can tell), this will be a really impressive camera, especially given how small it is.

  • No progress on raw or 422 mode?

  • New firmware update with tons of fixes and user requests addressed. I'm delighted to say that my Olympus 40-150 now works (even with the teleconverter) and while I haven't tried it, I'm hopeful that the Olympus 7-14/2.8 will too.

    https://www.facebook.com/groups/zcame2/permalink/322731551791130/

    Fixed: HDMI compatibility with Small HD monitor
    Fixed: PCM track compatibility with QuickTime/FCP
    Fixed: ISO 800 as high native ISO
    Improved: Lens compatibility
    Improved: USB SSD writing stability and speed
    Improved: Luminance level default value is changed to limited
    Improved: TC run type default value is changed to free run
    Improved: Record audio in VFR mode
    Improved: 200/240 VFR for 1080P25/1080P50
    Improved: AF & continuous AF
    Improved: Firmware upgrade stability
    Improved: Menu layout
    New: Show menu on HDMI
    New: Desqueeze video display
    New: Option to select the playback FPS for VFR
    New: Option to enable/disable phantom power
    New: 3696x2772 resolution under WDR mode
    New: Show AF region in LCD monitor
    We will arrange the next release in the end of next month. It will:
    - Improve the CAF, it will base on human tracking.
    - Reduce the sharpness on zlog/rec709
    - AE metering: spot. It could work with the ROI of AF.
    - MF magnifier. Magnify the preview to help you to do the MF.
    - stability & other issues.

  • Some of the first footage from the global shutter version of the camera:

  • I haven't asked about sending mine back for a refund. I'm willing to keep working around the limitations for now.

    If you want a stable camera that will work with all of your micro 4/3 lenses, definitely work with your HDMI screen, and consistently connect to your phone without issues, etc, you should definitely wait before considering the E2.

  • @eatstoomuchjam Is the camera still too buggy to keep, or are you able to send it back for a refund/new one at a later date?

    I'm not a huge fan of "ship first, firmware fix later" cams, and sadly, our specific BMPCC4K has to go back as we saw a few too many operational "kinks/bugs" that have cropped up, ours was not reliable enough to use on paid shoots yet...

  • I started poking around at the latest beta firmware update package today. For someone who is better at decompiling/disassembling than I am, I think this camera is super-hackable.

    The firmware image is an unencrypted zip file. In it, there's a uImage (bootable Linux kernel image), a md5 checksum file, a version file, and some tgz's containing the root fs and preferences.

    I packed the rootfs and in poking around, it looks like a pretty darn standard Linux setup, but with a couple of added binaries - imvt_camera and imvt_camera_watchdog

    Running strings against imvt_camera turns up lots of useful stuff - e.g.

    $ strings imvt_camera | grep -i "\.cfg" /usr/local/share/script/pref.cfg /tmp/data/pref.cfg /usr/local/share/script/calibration.cfg /tmp/nv/calibration.cfg /tmp/mnt/sd/MISC/logo.cfg /tmp/nv/mipi_lvds_crop_position.cfg /tmp/nv/mipi_crop_position.cfg

  • @Vitaliy_Kisilev They have mentioned it on their facebook group repeatedly and are taking preorders for it. For $2500, it will be 4kp30 and there is an additional $500 upgrade to unlock 4kp60.

    In some other posts, they've dropped some hints like that the sensor is 8.9 megapixels and will be a 1" sensor with 12 stops of dynamic range (vs the 14-15 of the standard E2) - so the crop will be similar to the original BMPCC at around 2.7x.

    https://www.facebook.com/groups/zcame2/permalink/312279046169714/

    https://www.facebook.com/zcamera/photos/a.518814941837902/694754167577311/?type=3&theater

  • @IronFilm

    I mean, where they announced that they'll do it?

  • What you mean?

    Because they're a teeny company, any resources diverted elsewhere will lead to compromising their other current (and future) projects. Such as the E2 at the moment.

    but really, a $2500 global shutter camera is a pretty big deal.

    The Digital Bolex D16 struggled badly at US$2.5K (although the Kickstarter was very successful, but it failed to follow through in achieving much more great success beyond the Kickstarter campaign. Not helped by a small price increase post Kickstarter), this shipped way back in 2013. Shut down in 2016.

    I am very skeptical that in 2019 that Z Cam will have a better chance of pulling off a USS$2.5K S16 global shutter camera than Digital Bolex managed to do.

  • @eatstoomuchjam

    For now they can't pull E2, abandoned app, etc

    If they try to do global shutter it can be bad.

  • Agreed - I think that the global shutter is also only a 1" sensor which reduces the audience... but really, a $2500 global shutter camera is a pretty big deal. I can see why they jumped to the next shiny thing, but agreed that it would be nice if they got the E2 polished before jumping so hard on the E2G or whatever they end up calling the global shutter model.

    Apparently they need to implement support for each lens 1-by-1 so implementing new lenses is slow and requires them to have one. I've asked how Panasonic and Olympus are able to work so well with each others' lenses as well as lenses from Yi or DJI, etc. It seems like the majority of lenses from each manufacturer should "just work" if other lenses from that manufacturer work already.