sandro

vasile, thanks for your hard work! this is exciting stuff.
did some initial tests of 80 vs 180 (highest my card can write continuously) and I see little to no difference, so double checked the file and sure enough it is 180mbps. That was just a rough shadow/highlight/detail test. Later I'll sit down with some lights and a person and set up a scene to really test it out. My guess right now is that hevc is extremely efficient, so the difference between 80 and 180 are going to be negligible. 320 might be different, but I can't test that until I get a faster card. This does seem to make sense because even at 660+ mbps to an external recorder, the main improvement is only in shadow macro blocking... even with nearly 600 more mbps. It's also being written as prores, so that could even account for some of the improvement.

Tried to test that allocation unit size and if it does anything to improve the slow card problem.
Everything was tested at UHD 25p. Adapted lens. Samsung Pro 16gb SD, 50MB\s write speed, 200mbps hack enabled. Exfat.
Tried to set it with 1024 bytes (min value) - couldn't record more than 3 seconds even without DIS.
Tested it with max value (32768 kilobytes) - could record around 10 seconds without DIS.
512 kilobytes, 4096 kilobytes, 32 kilobytes - a bit better, but still with DIS on no more than 10 seconds, without DIS around 1 minute, sometimes more, sometimes less.
So couldn't get 200mbps working. Also the camera was really slow when turning shutter or iso dials.
160mbps seems to work with and without DIS, also the camera is much more responsive, though not in the level as without the hack. Did this with 32kbytes allocation unit size.
So my conclusion is that as long as you don't set this value to extremes, it doesn't have a huge impact.
Iso 6400 at 200mbps doesn't look much different than at 80mbps.

Anyone tried if there any improvement on 3200 ISO and beyond with higher bitrate?

I'm quite certain that it is actually 23.98p not 98p, but it's written as "3840_2160_23_98p". I hope I'm wrong.
 

With fewer lenses out there than NX1 bodies - I'm worried it's going to be the opposite.
If you happen to NEED the auto-focus or IS and want the "S" series lens...I could see them selling for twice retail because there are so few of them out there. Maybe 1 for every 10 bodies sold.

We don't even know if the nx1 benchmarks does random or sequential reads. Or if it's threaded. It's complicated.

We don't even know if the nx1 benchmarks does random or sequential reads. Or if it's threaded. It's complicated.

I thought that we could make a Database here:
Samsung NX1:
 68.374 KB/s  Lexar SDXC 64 GB UHS-II U3 / Class 10  50.740 KB/s  ScanDisk SDHC 8 GB UHS-I / Class 10  44.328 KB/s  Samsung Pro SDXC 64GB UHS-I  37.873 KB/s  Transcend SDXC 64 GB UHS-I U3  37.347 KB/s  ScanDisk SDHC 8 GB UHS-I  36.186 KB/s  Samsung Pro microSDHC 16GB UHS-I  18.217 KB/s  Transcend SDHC 32 GB Class 10  16.616 KB/s  ADATA SDHC 32 GB Class 6  12.772 KB/s  ScanDisk Ultra microSDHC 16 GB Class 10    3.735 KB/s  Transcend SDHC 4 GB Class 4  xy  xy Only Write-speed, only Samsung-inCam testet (for NX500 i will make a second chart here)
Please write your results here and I will log it

As promised, here are some Before-After + settings on how this was graded :






Settings :
Saturation : 53
Fade : 30,6
Sharpen: 11,1
Lut - Sunderland (DeLuts) @ 57,4 Intensity

Contrast/exposure are done individually, also forgot to turn off grain for some of the before shots, sorry ! Hope you guys like it =) 

That is basically what Motion JPEG codec is and Motion JPEG 2000 which allows for 422 - 444 and 10bit

ok thanks... anyway don't be offended but isn't time limit removal the last of our concerns right now? I can't find a reason to use such a powerful cinematic tool to record for such a long time
I wonder why internal storage is so slow...what if we try to enable swapping on the sd card? with fastest cards it shouldn't be a problem I guess

Yesterday filmed in 4K the korfball Play Off - Sports Event + 720p livestream to youtube with the "DEV" hacks to disable 30 mins limit and lens check.
Camera NX1 proofs to be stable, even in stress conditions of the sports event! 
Camera: NX1 Lens: Canon Broadcast J17ex7.7B4 Record: 2160  25p on Komputerbay SD card Video out: 1080P for Youtube livestream Great work and many thanks :-)

Effing gorgeous... The lenses look okay too...haha. I assume this is with the NX1?

My dreams come true :-D  Let's hope that will work on NX1 too (unlike silent shutter).

Well yes in terms of compression it is, but in terms of details in the image saved, its quite poor to be honest and quite atrocious at lower bitrates, 80mbps is way too low for HEVC it must be way higher to match lets say the 200mbps H264 out of the GH4, you notice fine details like NOISE grain are completely smashed to pieces and smeared in HEVC in the way it works, 8bit is hilariously better at retaining film grain than 10bit is, people tested this.
http://forum.doom9.org/showthread.php?t=170986
Here you can effectively see what HEVC does to finer details, I also noticed that X265 is far better at retaining details specially in low bitrate and against still images compared to the Adobe HEVC encoder which completely dismantles an image. I done tests on vintage BluRay Ghibli movies that have a lot of fine grains in them from the film transfer and I choose animation because they have a lot of flat surfaces that are prone to banding, I noticed the 8bit retains the grain better but still crushes it. 
The entire point of HEVC is to decrease file sizes but retain image quality however this comes at a cost, with loss of details and finer details and images appearing overly smooth. In my humble opinion Samsung picked HEVC was a good choice if it had been an entry level consumer camera or video camera for home usage. 
But for something like the NX1 its bloody terrible, HEVC destroys details the sensor outputs and I honestly believe the entire issue with ISO performance above 3200 is because of HEVC inability to deal with noise grain details at 80mbps bitrate even though that is quite a lot compared to what HEVC is designed to work with. 
Samsung should have stuck with either H264 or even the MJPEG which retains details far better than HEVC. The MJPEG codec is in fact present inside the NX1 which means it would be a walk in the park to switch that one for 4k rather than injecting an entire new codec to the camera. I think we should try enable the MJPEG for 1080p and 2160p to see the difference, from my experience working with HEVC and other codecs you know its terrible when FZ-1000's H264 retains finer details in the image than the NX1 does.
I actually have a comparison shot of the NX1 vs the FZ-1000 and the 1000 has better shadow details with far finer grain noise.

@SMGJohn
di-camera-app is leaking (not freeing after use properly) a small amount of RAM every frame it processes. Normally this is not an issue since it does not exhaust the available RAM in 30 minutes, but with time restriction lifted you hit it at ~75min. There are two options to fix this - find a memory leak and fix it in di-camera-app binary (hard) and this possible quick hack if you (or somebody else) is willing to try - create and enable swap file and use it (leaked memory is no actually used and can be safely moved to swap). For some reason swap file on SD card is not working (swap partition might, but it's too much work for an average person), but there is a writeable partition in camera already with ~2GB free, mounted on /opt/usr, so this might help:
First to see hwo things look before (all commands from telnet session):
[root@drime5 ~]£ free
             total       used       free     shared    buffers     cached
Mem:        511580     499896      11684          0       5260      70556
-/+ buffers/cache:     424080      87500
Swap:            0          0          0
[root@drime5 ~]£ df -h /opt/usr
Filesystem            Size  Used Avail Use% Mounted on
/dev/mmcblk0p14       2.3G  105M  2.1G   5% /opt/usr
OK, so we have no swap and have plenty of free disk space on /opt/usr, let's create some swap:
[root@drime5 ~]£ dd if=/dev/zero of=/opt/usr/swap bs=1M count=512
512+0 records in
512+0 records out
536870912 bytes (537 MB) copied, 42.882 s, 12.5 MB/s
[root@drime5 ~]£ mkswap /opt/usr/swap
Setting up swapspace version 1, size = 524284 KiB
no label, UUID=63995c82-cf71-43c6-ae32-34e520e7e280
Ouch, internal storage is not very fast... Let's turn it on:
[root@drime5 ~]£ swapon /opt/usr/swap
[root@drime5 ~]£ free
             total       used       free     shared    buffers     cached
Mem:        511580     506540       5040          0       4404      82108
-/+ buffers/cache:     420028      91552
Swap:       524284          0     524284
[root@drime5 ~]£ df -h /opt/usr
Filesystem            Size  Used Avail Use% Mounted on
/dev/mmcblk0p14       2.3G  617M  1.6G  29% /opt/usr
Yup, it works
You have to do everything before swapon only once, after that (and after every reboot) you only have to re-enable the swap with swapon /opt/usr/swap
I hope sombody with enough free time tests this, I have a good feeling.

http://***URL removed***/forums/thread/3980221#forum-post-57456639
:-)

I had a similar problem with blue splotches showing up at high ISOs and I had to send the camera in to Samsung. They replaced the sensor and a few other parts under the warranty and it's be perfect since.

How To - recording limit - NX500 and NX1

YOUR WARRANTY IS NOW VOID.

http://***URL removed***/forums/post/57446101

YOUR WARRANTY IS NOW VOID.
YOUR WARRANTY IS NOW VOID.
YOUR WARRANTY IS NOW VOID.
YOUR WARRANTY IS NOW VOID.
YOUR WARRANTY IS NOW VOID.

At least you can use use copyrighted music on there since the major monetizes on videos. I couldn't upload my last videos on vimeo since they got deleted immediately.

Another brick in the wall:
 
http://***URL removed***/forums/post/57435922

Some great work here
Thread is now a sticky topic.

There has been a few stating that they would like to tip/donate, which would of course be muchhelp,, as I seem to be doing this more than my 9-5 haha! But it is not at a quantifiable stage at the moment, What I have found out is pretty much just a key, and if the key can open the lock is not yet determined. Even with the sdk things of this nature are not 100% 
At any step of the way if they did something undocumented it can halt progress to a point the modification cant be done. Ive been lucky so far with things is all!

But if knowing that what Im doing may not bring a firmware mod to light people still wish to donate then I can put something together. But I started this not knowing there was anyone wanting this camera modded, and I would still do this if no one wanted to tip/donate.

That being said the next stages of what I am doing are copious research. There are white paper behind paywalls but my local university seems to have most of the books on file so I will be acquiring those to get a better idea of the way samsung chose to code.

Personally I am also interested in the lens mount for a working adapter to other lens systems. So the control files are something I am also looking into. As well as if hevc is the best choice for encoding or if something like the redcoderaw would be more suitable which is just their modded version of mjpeg2000. dct vs wavelet is something interesting to read about. 

Wow, nx1 Italian community! I feel less lonely now :-P 

Italian nx1 user number 3 is here! I'm ready to make a donation!