Last Leaves

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!

Let me just thank you so much Vasile for all your hard work so far, I am grateful.
So when I first saw your bitrate hack the first thing I did was testing it, sadly my SD cards are only capable of 160Mbps on the NX1 despite having average 40MB/s writing speed on my computer which should have allowed me to use the ~300Mbps bitrate according to a couple of calculators I used, I could be wrong again, my terrible maths sometime.
While I tested it I honestly could not notice much difference between the shots at 1600ISO, now this is just a quick test nothing in depth really, hopefully someone will do more scientific tests, I suppose you all should take this test with a pinch of salt because it was done in a hurry, I have not tested whether the banding issue is gone either, and I did extensive tests with JPEG's a few days back and the banding barely occurs at normal JPEG compression and completely gone with super and fine, so clearly the issue lays not with 8bit if its fed enough data. My biggest suspicion here because GH4 does not suffer from banding if you know what you are doing, it could be the noise reduction internally which lets face it, destroys details notoriously even at lower ISO's and higher bitrate does not seem to slow it down in its path of destruction.
As always video mode feature my usual settings GammaDR (R1.00 G0.95 B1.00 | -10 Sharpness | -10 Contrast)
80Mbps (Standard Pro Setting) 2160p UHD [1/50 - F/2.0 - 1600ISO]

160Mbps (Vasile's High Bitrate Hack) 2160p UHD [1/50 - F/2.0 - 1600ISO]

320Mbps (Vasile's High Bitrate Hack) 2160p UHD [1/50 - F/2.0 - 1600ISO]

JPEG NORMAL (-10 Sharpness -10 Contrast) 2048x1152 [1/50 - F/2.0 - 1600ISO]

Left 160Mbps - Right 320Mbps

Again, thank you so much Vasile for all your hard work, I really appreciate it even though my results might not prove much but still the bitrate increase is REALLY there, whether the changes are not there could be more the faults of the God damn atrocious HEVC codec which was the biggest mistake to be put in a camera since H264. 
If I have time I will try to record some blue sky if they appear again this week with the 160Mbps setting to see if the banding issue has been negated a bit.
 
 

http://***URL removed***/forums/thread/3988168

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.
 

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.
 

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.
 

Thank you very much for your good work. My hope is:
When remote shooting NX500 via iOS Samsung Camera Manager i can not shoot RAW. Only JPG is possible. Is that software or hardware related? Strange. All my other cameras can shoot RAW via wifi. I would be extremely happy if RAW (.SRW) remote shooting could be made possible.
Thank you

A few feature hopes and dreams from someone willing to test, but not savvy enough to explore on my own. Thanks in advance for any work.
The "SAS" (Samsung Auto Shot) functions on the  NX500 have the potential of being very useful for various applications, but they are crippled by a few limitations that are most likely software-based. If you're struggling to see how the SAS functions would be useful skip to the Hypothetical Shoot Scenarios at the end. 
In order of priority, these are some changes that would make the SAS functions more useful:
The ability to capture in RAW. Currently, as far as I know, all Auto settings are limited to JPG on the NX500. Manual settings. Just because it is called "Samsung Auto Shot" doesn't mean that you shouldn't be able to manually set aperture, shutter speed, and ISO. Continuous AF. Currently it is limited to Single AF, which means it sets AF at the beginning of the capture and doesn't change depending on the subject. Ideally the AF would be smart enough to detect movement, focus on the moving subject, and then trigger the shutter (I know this is a lot to ask for, but it could be bloody useful, and doesn't seem outside of the realm of possibility).  The ability to set "Trap Shot" to be triggered by movement in any direction. Currently you can only set it to be triggered by movement from one direction at a time. The ability to have video recording triggered by movement. Currently the SAS modes are only available for stills. Hypothetical Shoot Scenario: You're trying to catch birds in flight and you've found their nest. With the camera on a tripod you frame up a shot to capture the bird as it is just taking off or just coming in for a landing. Ideally, you would be able to set your shutter speed to one fast enough to stop the bird in mid-air without motion blur, set your AF to continuous, and leave the camera to do its thing.
Less likely Shoot Scenario: You're trying to capture footage of polar bears leaving their den in the spring. You set up your camera a few hundred meters from the den opening and run your camera off of a large external battery. With a long lens you frame up a shot of the den opening, you lock your shutter at 1/50th and set your aperture to f/5.6, you set ISO to Auto, and you turn AF off. Ideally, the camera is able to be left alone for hours, and when movement is detected in the frame a video is captured for a set period of time.
These scenarios are just meant to spark people's imagination with the potential utility of this already powerful, but crippled, capture tool.
 

We will be expecting eagerly your hacking/moding advances, until then just keep it humble, so to keep this thread useful and without any grey noise.

This was something that I noticed with Vasile's aquarium too. It is normal for bitrates to be somewhat variable, especially with the amount of color and light changing (i.e. less detail, less light, requires less data). But, assuming VLC's "Statistics" panel is accurate, this seems to be inverted with Vasile's clip; when the clip is completely black is when the bitrate is the highest. I have found frames (at around 21 seconds) that are less than 1/4 of the bitrate during the completely black seconds at the beginning. What is going on here?
EDIT: I just checked a clip (DC24P [Cinema 4K] Movie Quality 'Pro') that I shot on NX500 to see if there was variation in bitrate throughout the shot. The shot lasts 8m09s. The subject is moving water at sunset... a huge amount of variation in color and light. The data rate is locked at 71826kb/s (this is for my shot, not Vasile's!). After looking at this shot I looked through a few more and they also have this exact same bitrate.