Pavel Mašek

Sometimes one just have to question what insanity Samsung went through to make it so damn hard to just disable that NR, even if HEVC is a lets just say not the best codec out there for a camera but even with NR off the differences are night and day imao, it still wont be glorious but Samsung should have stopped being so childish and just given us the option to turn this off I remember quite early a lot of NX users asked for this, we been ignored ever since about it. 
Despite them pushing out the updates they never included an option for disabling NR in video mode.
 

Well, there are no samples yet - guys there just test it and they have not yet uploaded any screen grab from the video to proof there us is no NR
BTW - I saw noise grain in very early stages of 2.5K video so I believe it is possible (see above)

I think MJPEG is without noise reduction - could it help to find where it is set?

http://www.amazon.com/Samsung-Wireless-Smart-Camera-16-50mm/dp/B00V5UDU60/ref=sr_1_2?ie=UTF8&qid=1461082163&sr=8-2&keywords=nx1
But please do not buy it in the hope that more capabilities would be unlocked by anyone. Nothing is guaranteed. See here why: http://***URL removed***/forums/post/57624059.

I forgot mentioned it - NX1. Moreover - it is screen grab from in-camera timelapse so it is not so static scene but quite complex with fast moving trees, waves and clouds.
There was some small macroblocking in blue parts but they disappeared after conversion to 16-235.

demanded != being useful/used.

DR of 180Mbps footage. Great thing is there is no macroblocking in lifted shadows, just litle lack of details... but still very good result I think. 
BTW - First image is unedited 0-255, Standard, MBL +8. Second is converted to 16-235 with some grading (also added saturation becuase there was lack of colours in shadows and just a little bit sharpness to left side of image)
 

 
 
 

I was playing around with this last night and it looks like you can get the Saturation, Sharpness and contract to values that are not shown in the menu including negative numbers. 
ex:  if you set sharpness to -10 in the menu and do "prefman get 0 0x87c l" comes back showing the value is set to 0 and like wise if you set sharpness to +10 in the menu and prefman get again reads the value as 20 therfore -10=0 and +10=20. now if you do "prefman set 0 0x87c l -10" witch would be an equivalent to -20 sharpness in the menu then do a "prefman get 0 0x87c l" it read the value is still being set to -10.
I will do some more testing to see if the value is actually sticking during or after recording and if it makes a difference to the quality then report back.
 
I also wrote a script last night that uses nested while commands to consecutively record 5 sec clips testing all the gammaDR setting in a given range. this could in theory test every possible combination for saturation, sharpness, contrast setting automatically(1000 tests total). Let me know if any one is interested in this script for themselves.
This script could also very easily be altered to do or include MBL, RGB setting or HUE settings if that is your kinds of thing.

Samples 
http://***URL removed***/forums/post/57621998

I'm really anxious to give it a try, but I just got a flood of work. If no one else does, I'll post some tests by the end of the week... wish it could be sooner.
Thanks for all your hard work Vasile!

I am wondering that there is no report about quality of highbitrate 2.5K mode by some of NX500 users (Vasile's latest high bitrate hack for NX500). It was so demanded...

I am wondering that there is no report about quality of highbitrate 2.5K mode by some of NX500 users (Vasile's latest high bitrate hack for NX500). It was so demanded...

I think MJPEG is without noise reduction - could it help to find where it is set?

Mod update for NX500 users here: http://***URL removed***/forums/post/57619677
NX1 users can stay on v2.0, no change - yet ;-) - for them.
Enjoy...

OK, some advancements - namely a way to speed up applying mods as soon as the camera wakes up from sleep. See more here https://github.com/ottokiksmaler/nx500_nx1_modding/blob/master/doc/Boot_Process_and_Speeding_up_Mods.md
Also, a small poll and explanation:
If you don't want to do it from telnet, wait a few days, there will be a nicer, more automated way to do it.
If you are starting other things (bitrate hacks, whatever) - please do check if they are running already. You can use keyscan as test as it will return 0 only if it's not already running, like this /opt/usr/devel/bin/keyscan /dev/event0 /dev/event1 /opt/usr/devel/bin/ && my_program
Just to make things clear - it's not modifying the firmware.I have no intention to mess with firmware as I have no easy way to repair my camera.
We slightly tweak the "read only" rootfs (like we already do for BT hack - we just change a single line in script) and move our scripts from SD card to internal filesystem - the one mounted under /opt as "read write" by default. It's not going to brick a camera, I have even put a swap file to extend RAM on that filesystem and everything worked.
NB, I have been using and testing this for two days now - no side effects.
The main difference is that right now, when you pop out the SD card with mods and put in a clean one - your camera acts as if it was neved modded. With this it would be modded even without a SD card (ie, it would be modded with every SD card).
All modifications are fully reversible and would be reversible from aforementioned utility.
So, a small poll - do you want me to make an installer that will install mods to the camera internally in order to work faster?

Yes but not necessarily the best. I like more the nrmenable st cap live parameter from here: https://github.com/ottokiksmaler/nx500_nx1_modding/blob/master/ST%20Commands.md
If I could find where it is set in di-camera-app I'd be in business.

I think max. bitrate (according my tests) is 110Mbps to have full 120fps. 
Thanks to latest hack version by Vasile I could set this value to HQ mode and 180Mbps to PRO mode - if need 120fps I just change PRO to HQ.
Yes, more significant improvement than for 4K: 
I can use full available bitrate (180Mbps with Lexar 2000x), image is very nice (I will start it much more than 120fps now), only (yes, heavy) line skipping, no macroblocking.

Well, it is still there quite a lot - I think just compression is better.

Here are two comparison videos with side-by-side evaluations on a number of areas, like low light, slow motion, audio, rolling shutter, and how they key.
Part 1:
Part 2:
 
In short:
Ursa Mini: better overall picture (flatter shooting profile, better color gamut) global shutter, better for green screening
Nx1: sharper, less noise in low light, better audio, better slow motion

Yeah I was wondering about that myself.
I am also curious about the following commands as well
startfisheye stopfisheye setpath 0 - 2(0:OTF/1:IPCout/2:RawOut/3:Ldc Out/4:120FPS OTF/5:120FPS IPC out stremmode [0 – 14] sensorframerate 240 outputframerate 240 dataframerate 240 Hopefully I will have some time to play around with it this sunday.

Any idea what can be "nrmenable 0 - 1 (0:off/1:on)"? Noise reduction in movie mode? :-) 

Any idea what can be "nrmenable 0 - 1 (0:off/1:on)"? Noise reduction in movie mode? :-) 

Better color tonalities & less banding are expected theoretically with more bits as mentioned earlier in this thread. Your tests confirm that. The differences are subtle but still there. 
Some of Sony's gammas are also not correctly recognized in Premiere and it is indeed annoying. Even more annoying is that I don't know who to blame for this. 

Below is comparsion of 16-235 and 0-255 (converted in Premiere to 16-235 according video above) + same images with lifted shadows in Lumetri.
Both same exposure, WB, Standard profile, 180Mbit bitrate, ISO 320
I think that converted 0-255 looks better, it has at least more accurate colours (wall is more orange in reality) in shadows, otherwise it looks same in to me (even in video)