kinoseed

wow... how.. disappointing
I wish they compared it with the 180Mbps HEVC of Nx500/Nx1 too

haha! I am sure they do!
Nuh..they are not that sensitive, cameras do not broke that easily, you see in various forums that only a few complain about broken NXes, and usually the top dial somehow do not work properly. They seem very well implemented, plus there are quite a lot new ones from Korea.
From various sources around the net (and your Fabebook as well) it seems like there are a lot more NX users than I though they were, just not enough obviously.
As it seems, my NX1/NX500/NX3000+all the lenses I need (except the 50-150 I do not have) will keep me good company for a few more years.
The things I mentioned above are the only concerns, but a breakthrough in any of these could keep the cameras relative for at least a couple more years (until 2020), do not even want to know what will happen if we can extract raw, somehow, out of these, people are buying 5DmarkII for their Magic Lantern capabilities!
We will see, it is an interesting journey nevertheless, and thanks for all your effort, much obliged!

wow... how.. disappointing
I wish they compared it with the 180Mbps HEVC of Nx500/Nx1 too

this will probably not eliminate macroblocks, as ti is not simply a sub-sampling artifact (I think).
if you try a filter which removes MPEG/JPEG compression, it should do the same, right?
You should easily (if you already have Avisynth) be able to test it, using the plugin, so just compare the results and check how it measures with the mpeg-denoiser of your choice.

Hello. Someone says he wrote a program to rebuild color sampling 4.2.0 in a real 4.4.4.
I'm not a programmer or hackers, or anyone good as @ottok or @kinoseed can see better what is it?
Thank you
https://forum.doom9.org/showthread.php?t=173005&page=6
https://github.com/Khanattila/KNLMeansCL/releases

One thing the Panasonics have going for them since the G7 is workable ISO up to 3200, and no I am not pulling this one out of my back. Have a look for yourself:
 

you probably had your camera set to AWB?

Wish someone who worked in Samsung camera department would accidentally leak the developer tools

You can use ecryptfs which produces "normal" files just with scrambled names and contents (used for example by Ubuntu if you select encryption of the home directory during the install) as well as block level encryption (see LUKS and Librecrypt for Windows use) that can work either on a complete card, a partition or use a file on the card as a block device. Both are vastly better than encryption after the image was saved. 
Also an option is to use network share to store photos so nothing is on the camera either way (but it's quite slow, around 3MB/s so ~4s per full resolution jpeg). 
The problem I have with nx500 is that it hangs if it cannot open the file it thinks exists (even the simple deletion from terminal can confuse playback). 

It's been a while since I looked at ML, but if memory serves, they were doing parallel readout of different ISOs, something which I think ALEXA is also doing.
So instead of blending two frames, they are reading the sensor at two different ISOs by having different amplification for different row-readouts. Something like - read the odd sensor rows at iso100 and read the even rows at iso1600.

Not that this changes the answer... which is No,
but they do have access to hardware control, which far supersedes the availability here.

There have been some updates after that version.

3x3 Grid (thick lines): with camera-ui not freezing (turn on/off from the menu)
note: overlay.png is still available as an option, just add your file and it will work (but the rest of the ui will freeze until you unload), if you want to use the non-freezing 3x3, simply remove the overlay.png from your sdcard.

2.35 filmgate: with camera-ui not freezing ( turn on/off with EV+OK)
note: if you are on NX1 you need to sacrifice another shortcut to use this one,
and simply rename EV_OK.sh to the one you like to use, before installing.
note2: it is possible to adjust the filmgate, just add the desired proportion as a parameter,
but you need to modify the bash command.
ex (for 16/9): /opt/usr/nx-ks/onscreen_235 1.77 

There have been some updates after that version.

3x3 Grid (thick lines): with camera-ui not freezing (turn on/off from the menu)
note: overlay.png is still available as an option, just add your file and it will work (but the rest of the ui will freeze until you unload), if you want to use the non-freezing 3x3, simply remove the overlay.png from your sdcard.

2.35 filmgate: with camera-ui not freezing ( turn on/off with EV+OK)
note: if you are on NX1 you need to sacrifice another shortcut to use this one,
and simply rename EV_OK.sh to the one you like to use, before installing.
note2: it is possible to adjust the filmgate, just add the desired proportion as a parameter,
but you need to modify the bash command.
ex (for 16/9): /opt/usr/nx-ks/onscreen_235 1.77 

There have been some updates after that version.

3x3 Grid (thick lines): with camera-ui not freezing (turn on/off from the menu)
note: overlay.png is still available as an option, just add your file and it will work (but the rest of the ui will freeze until you unload), if you want to use the non-freezing 3x3, simply remove the overlay.png from your sdcard.

2.35 filmgate: with camera-ui not freezing ( turn on/off with EV+OK)
note: if you are on NX1 you need to sacrifice another shortcut to use this one,
and simply rename EV_OK.sh to the one you like to use, before installing.
note2: it is possible to adjust the filmgate, just add the desired proportion as a parameter,
but you need to modify the bash command.
ex (for 16/9): /opt/usr/nx-ks/onscreen_235 1.77 

Amazing. Thank you so much. 

here you go:

v2.79
added: Custom overlay
- start from ( settings> overlay ). It loads your own custom overlay from the root directory of the sdcard ( sdcard/overlay.png ). Once activated the touchscreen will not work, and histogram will be "frozen" until you deactivate it ( reminder: Ev+Ev/Ok to start the menu for nx500/nx1)

note that the preview of the playback will not work, however press "ok" for the video playback to start, and the recorded video with the overlay on top will show.

you can make any overlay you like, as 720x480 transparent PNG  (replace the overlay.png with it)

I don't know if you noticed, but it seems there's "official" support of K-mount and one other "unknown"

[root@drime5 ~]# st cap capdtm getusr LENSMOUNT
UserData is LENSMOUNT_NX_MOUNT (0x590000)
UserData is LENSMOUNT_K_MOUNT (0x590001)
UserData is LENSMOUNT_UNKNOWN (0x590002)

 

here you go:

v2.79
added: Custom overlay
- start from ( settings> overlay ). It loads your own custom overlay from the root directory of the sdcard ( sdcard/overlay.png ). Once activated the touchscreen will not work, and histogram will be "frozen" until you deactivate it ( reminder: Ev+Ev/Ok to start the menu for nx500/nx1)

note that the preview of the playback will not work, however press "ok" for the video playback to start, and the recorded video with the overlay on top will show.

you can make any overlay you like, as 720x480 transparent PNG  (replace the overlay.png with it)

here you go:

v2.79
added: Custom overlay
- start from ( settings> overlay ). It loads your own custom overlay from the root directory of the sdcard ( sdcard/overlay.png ). Once activated the touchscreen will not work, and histogram will be "frozen" until you deactivate it ( reminder: Ev+Ev/Ok to start the menu for nx500/nx1)

note that the preview of the playback will not work, however press "ok" for the video playback to start, and the recorded video with the overlay on top will show.

you can make any overlay you like, as 720x480 transparent PNG  (replace the overlay.png with it)

here you go:

v2.79
added: Custom overlay
- start from ( settings> overlay ). It loads your own custom overlay from the root directory of the sdcard ( sdcard/overlay.png ). Once activated the touchscreen will not work, and histogram will be "frozen" until you deactivate it ( reminder: Ev+Ev/Ok to start the menu for nx500/nx1)

note that the preview of the playback will not work, however press "ok" for the video playback to start, and the recorded video with the overlay on top will show.

you can make any overlay you like, as 720x480 transparent PNG  (replace the overlay.png with it)

here you go:

v2.79
added: Custom overlay
- start from ( settings> overlay ). It loads your own custom overlay from the root directory of the sdcard ( sdcard/overlay.png ). Once activated the touchscreen will not work, and histogram will be "frozen" until you deactivate it ( reminder: Ev+Ev/Ok to start the menu for nx500/nx1)

note that the preview of the playback will not work, however press "ok" for the video playback to start, and the recorded video with the overlay on top will show.

you can make any overlay you like, as 720x480 transparent PNG  (replace the overlay.png with it)

here you go:

v2.79
added: Custom overlay
- start from ( settings> overlay ). It loads your own custom overlay from the root directory of the sdcard ( sdcard/overlay.png ). Once activated the touchscreen will not work, and histogram will be "frozen" until you deactivate it ( reminder: Ev+Ev/Ok to start the menu for nx500/nx1)

note that the preview of the playback will not work, however press "ok" for the video playback to start, and the recorded video with the overlay on top will show.

you can make any overlay you like, as 720x480 transparent PNG  (replace the overlay.png with it)

here you go:

v2.79
added: Custom overlay
- start from ( settings> overlay ). It loads your own custom overlay from the root directory of the sdcard ( sdcard/overlay.png ). Once activated the touchscreen will not work, and histogram will be "frozen" until you deactivate it ( reminder: Ev+Ev/Ok to start the menu for nx500/nx1)

note that the preview of the playback will not work, however press "ok" for the video playback to start, and the recorded video with the overlay on top will show.

you can make any overlay you like, as 720x480 transparent PNG  (replace the overlay.png with it)

Thank you for the explanation, however, I do not think it applies here.
There is no indication for difference in performance. NX1 and NX500 can handle up to the same amount of increased bitrate for the encoder. When I said same PPUs/OPUs etc (some of which handle image-resizing) - I am under the impression those are programmable hardware units. In particular resizing/re-sampling is set by a few registers which set the parameters for (I think it was PPU1 that handled resizing?), and the only block that is preventing NX500 of having non-crop 4K is control of those registers (which was not successful for now), but we can dump them quite easily.
So... if there were disabled processing cores, we would have noticed right away

Thank you for the explanation, however, I do not think it applies here.
There is no indication for difference in performance. NX1 and NX500 can handle up to the same amount of increased bitrate for the encoder. When I said same PPUs/OPUs etc (some of which handle image-resizing) - I am under the impression those are programmable hardware units. In particular resizing/re-sampling is set by a few registers which set the parameters for (I think it was PPU1 that handled resizing?), and the only block that is preventing NX500 of having non-crop 4K is control of those registers (which was not successful for now), but we can dump them quite easily.
So... if there were disabled processing cores, we would have noticed right away