Still have one problem. HDMI out is always 25p, 50p, 30p or 60p. But what if I want 24p??
@Vitaliy_Kiselev, is it possible to view files on E1?
You can try to put some video files (used to check 444) on card and connect camera to monitor to check.
@samuelcabral, I'm not sure about it. Data is packed as 4:4:4 but it can be 4:2:2 from DSP. We need somebody to test it because my recorder can only write 4:2:2 to SSD
Great! This means that i can get 444 with an external recorder?
GUYS!!! GREEN SCREEN IS TOTALLY FIXED! Blackmagic Shuttle 2 wants YUV 4:4:4 signal out from camera's HDMI, but in E1 it's forced to RGB. I've made it to use YUV 4:4:4 through HDMI - result you can see in pictures below. Some little things left, like make sure it's real 10-bit color. I'll upload fix to my repository: http://github.com/storyboardcreativity/Z-Camera-E1-Reverse-Engineering
Today got Blackmagic HyperDesk Shuttle 2 and... it's a fail. Green screen. Any ideas?
I need some help from E1 users. Do you have any problems with HDMI out? On my 0.31 version I have frozen picture on LCD when HDMI is connected and after some idle time HDMI out signal is frozen too. Is it ok? :D
Camera does not compress HDMI signal (except may be for color sampling) :-)
@rjhinde, I wrote a letter to Z Cam with some questions about slow motion on E1. It will be better if it's possible to read only top sensor part (still 1536x288, but without subsampling). It can make quality much better.
Hey, guys! New info about E1 firmware internals: when you choose "720P 240 FPS" mode, actual readout from sensor is 1536x288! Than frame is interpolated to 1280x720 and encoded. So, it looks like a foul play from Z Cam :)
@Vitaliy_Kiselev, what about DSP assertion codes?
I actually looked around the older firmware before encryption and couldn't find anything resembling a key (which is not to say it doesn't exist). It may actually be in a part of the camera not changed by firmware (which would mean breaking it would be pretty much permanent).
If it's just spelunking for features, though, I am already able to do that without breaking the firmware. There's another backdoor in. Is there one in particular that you're interested in?
The newer ones use zip encryption - so it's not entirely unbreakable, but much more time-consuming if you care to do it.
Well, due to incremental nature of firmware it is easy breakable :-) As you can just use older, latest firmware before encryption to find proper keys.
I haven't seen any reason to mess with it, though, since the current quality/features are already fine.
Usually such things have few small surprises :-) May be some stuff stuff can be just disabled.
If you can find an older E2 firmware package, they didn't bother with any sort of encryption. You can just unzip it and look around. The newer ones use zip encryption - so it's not entirely unbreakable, but much more time-consuming if you care to do it.
The E2 firmware is mostly just a ucLinux OS. The camera-specific stuff (mostly) is in a single executable file. I haven't seen any reason to mess with it, though, since the current quality/features are already fine.
@Vitaliy_Kiselev, I still don't have a E2. I started reverse-engineering E1 firmware because I wanted this camera and I saw that 4K24P 60 Mb/s is too low for this camera. It was just interesting for me. But I don't have E2 because it's too expensive for me - maybe later, when I can buy it with ~$400-$600...
And what do you need to edit in E2 firmware? Is not it good?
It looks like you're new here. If you want to get involved, click one of these buttons!