sandro

+1
italy is here..im ready for give donation and agree for hacking nx1 

Are you sure the a6300 degrades from 6400? The sample from cinema 5d shows much more than that!

Yeah I payed $1600 for the NX1, 16-50 S, 30/2, 16/2.4, 45/1.8 and an extra battery. And Im sure I could have gotten it cheaper.
So image/dollar is definitely the NX1.
Between the a7sii and a6300 would probably go a7sii if money wasnt an issue.

I seriously don't get they the nx1 is do bad in lowlight while the a6300 can do this 
I mean there something wrong with the sensor design or we really need to remove that NR.

I'm afraid all the replies so far aren't right.
The NX1 uses a power saving live view mode when not in video standby mode.
In this mode for framing up a shot, there's hardly any rolling shutter skew because the sensor is doing a very fast sweep, missing out a lot of pixels and lines. We call that binning.
In video mode it does a 6K full pixel readout for the great quality 4K recording it has. That takes time... approx 30ms for the rolling shutter to expose the entire sensor, which is what creates the skew in video mode.
Switch to 1080/120fps and it reverts to pixel binning and there's less skew.

There's no rolling shutter because stills use the mechanical focal plane shutter while video uses the electronic shutter. It's quite obvious on cameras which can shoot both mechanical and electronic shutter (A7s, X-T1, ...), one has clear rolling shutter and the other not.

@sandro there are plenty of tutorials on https://github.com/ottokiksmaler/nx500 including the archive you should unpack to SD card for telnet, etc. 

Thanks to some ideas I had regarding hardware and if the nx1 was a true uhs2 camera or just backwards compatibility with uhs2 and thus only being a uhs1 camera I have found proof.

page 3 main pcb shows the full sd slot.
https://fccid.io/pdf.php?id=2394050

The sd slot http://www.alps.com/prod/info/E/HTML/Connector/SDMemoryCard/SCDA/SCDACA0200.html
 Made for uhs2. So the reality of the full speed uhs2 sd bus is possible.

are we talking about hevc support or gpu decoding? they're not the same

with what editing software? Adobe premiere afaik doesn't support hw decoding of hevc
i can help as well

The old (non ART version) Sigma 30mm f1.4 in Nikon mount is sweet. Doesnt cost much used.

If i see it right (in the Chart) then the maximum Bitrate for the H.265 HEVC is at Level 5.1 (found this Level in the File-Infos of my NX1-Videos) 160.000 kbit/s, approximately 156 Mbit/s.
And interessting too, the maximum Frame rates:
c4k @ 60p
UHD @ 64p
an FHD @ 256p

higher bit rate would be enough for me to throw 100$, also 240fps @ 1080p would be an awesome bonus

4) and 1) are definitely my top choices. It's a shame a camera like this is unusable at 3200.

When it comes to that point things can be figured out. As I stated, I started this project for my own ideal goals for this camera, I guess its just a plus that more people are interested in expanding what the nx1 can do. The next few weeks will dictate what is possible back end wise. What otto k has also done would be useful. As building a front end like ml would be more user friendly compared to what was built for the gh2 and ptool, and that sort of firmware update system. 
If we could get a list going of what people would like to see it could help focus the work better. Unlike other cameras the firmware is complicated but not near as obfuscated and vastly lacking encryption as other systems. Open source really makes it easy even if the sdk isnt public.

The list of additions are interesting, I have to admit the focus will be on video and all other aspects will be secondary.
Found a few things. DRIMe-V clock rate seems to be 200mhz. And that seems.. low. Im expecting an NX1 in the next few weeks, so that is one thing I will test. May have to do some heat dissipation help, but from other things I have found in the fw that should be able to be pushed. If things are on the level of the sony a7(s) line up with their over heating issues I think a tad below that will suffice. The upper limit should be 700mhz+ But erring on the safe side will always be more logical.

**Edit** In additon to that finding, I will have to track the changes to see if they upped the clock rate in the later fw. I am working in the first revision as that has the largest file size, so I assumed it would have the most debug changes from the 1.0 layout, with the other firmwares focusing more on updates and camera usability changes.**
I wasnt intending to work on this tonight as I have some graphic design work I need to do, but the more I look, the juicer things get!

samyang lenses in general are beautiful on the nx1

Absolutely agree with this one,
1. Most important - Higher bit rates is the thing we all need the most. Lets get rid of macroblocking and all sorts of problem.
2. Turn off the NoiseReduction - in my mind, the NR must slow eat a big chunk of processing power. If turned off, this power can be used elswhere.
3. 10 bit or 12RAW - I mean, honestly. You cant argue with this one.. 
4. Higher frame rates - is what makes the camera more appealing to us, but honestly, not more usable. Just makes it a better deal
5. Trying to disable crop 4K on NX500 and applieing 1 to 4 to NX500. That could make the camera more appealing to everybody. (not sure if we established already this is not possible?)

PS: Chant, as other stated, if you are dedicated to this task.. As other stated, dont be shy to ask for compensation or think of crowdfunding from us, if you plan to break in the camera and make it whole new better piece of tech.
 

Depending on what I find there could be an option for a 1:1.29 lossless or a higher compression visually lossless hevc. Creating a custom lut for a more red like log seems possible also.
 The firmware seems more of a proof of concept that they left it open to change so many things. And more so to show they can go head to head with the established makers and make something better. Since this thread has garnered more interest I have shifted to put more hours into this dive I am doing.

I can confirm 1,1x crop factor at 120p over s35 or 1,65x over full frame mode....  Someone tried today the camera

But RAW image has to be scale down because bitrate would be insane in this case (24x around 30MB = 720MB/s). Maximum write speed of NX1 is 60MB/s (see http://www.cameramemoryspeed.com/samsung-nx1/sd-card-comparison/ )

Played a little more to make two more "modern" and clean looks. 
(Didnt frame the letterbox properly)



 

Tried some different LUTs with the NX1 today.
Im stuck at home guarding my dog after surgery, so this is what I can do for now basically.
 

I started this research when the nx1 first came out, saved and tracked the firmware, and then started digging into when the rumors of the exit started happening. The tech inside this camera is just magic. Compared to what other companies are doing its a few years ahead. And due to samsung being able to roll their own chips it seems they didnt cripple anything because it was too costly. Im not going anywhere! 

New to the forum, but I have been working on the opening of the firmware for quite a few months. The second I heard about this camera coming from a modded gh2 I knew things were going to be fun.

I had plans to release what I found after having a stable custom build.

Good news after reading this thread as I seem to have quite a bit more discovered than most.

-bootloader
-3d lut info
-rgb888 info
And quite a few more things that make this an ideal camera to mod.

In the interview they basically implied they either had asics or fpgas built along side the arm cores.

"DE: When we were talking previously, you said that the architecture of DRIMe V is very different than DRIMe IV. What sorts of changes are made between them?
JK: The biggest change is the structure of the Image Signal Processor. The DRIMe V ISP is very different. Most ISPs have key parts of the processing hardwired to get the needed speed. What's really new with the DRIMe V is that the "hardwiring" can be reconfigured.
DE: That sounds very significant, although I have to admit I don't know how common it is that ISPs are actually hardwired.
JK: There's not much variability in them. Sometimes you'll get thresholding changes and small numeric variables, but the image path is usually very locked down...
DE: It's pretty much, a fixed pipeline.
JK: With a few tuning pieces, yeah.
DE: Whereas this is more configurable.
JK: Yes.
DE: And it's configurable not at the level of changing a firmware program, but you're actually changing the hardwiring. There are switches you can use to change the configuration of the functional units?
JK: Yeah, basically. And Samsung's software people are all over it; they're pretty sharp and I believe that we're really going to be able to tap fully into the DRIMe V's capabilities for the NX1.
DE: So even though it's hardwired, some of the connectivity is programmable through the firmware, so we can actually look for continued "firmware" development that would continue to improve performance, including the parts that are implemented in hardware.
JK: Yes.
DE: So there may be significant improvements in the near future. That's pretty interesting, because it sounds like it's already starting out pretty capable.
JK: And not just image quality, there's a lot going on in terms of programmability, like we talked about Samsung Auto-Shot mode before. Here's the UI for it."

TLDR: fpga or cpld or asic that can be reconfigd.

Now a few years ago samsung released info about adding fpgas into asics http://www.eetimes.com/document.asp?doc_id=1200317
 
And have teamed up with Lattice on a few projects http://www.oregonlive.com/silicon-forest/index.ssf/2014/04/which_oregon_company_has_a_chi.html
The back end camera control files seem to be written in .cpp so diving deep into the firmware to do a comparison of hex/string/hash changes and tracking the changes across the updates is what I am doing right now. And seeing which values can be modded. Recompiling is a different story but what it seems to be is that building a smiliar man in the middle to what magic lantern would be possible. Have a gui that would simialr to ptools in camera using the web browser capabilities.

Now this is not my full time work so Ive been progressing slowly as I have many projects on the go.
This is also coming from someone who doesnt yet have an nx1. Doing the proof of concept and running the fw in a vm to emulate the possible bricking before things are bought.
I am also tracking similarities to the nx500 to see what things are possible in that camera. Nice b camera which should be able to compete with a shortening of its life but at the cost 10x performance is worth the lifespan limit imo.