SMGJohn

not 120, but here is 60fps 1080p internal vs high bit rate
http://www.eoshd.com/comments/topic/18661-your-ideal-nx1-settings/?do=findComment&comment=129594

 
I'm not entirely sure the camera is outputting 422. 8bit 422 on other dslrs produce much less banding which leads me to believe the nx1 is outputting 8bit 420 over hdmi. 
macroblocking is precisely what increased bitrate will help us with, however.
80mbps:

600 mbps:

clearly here is some jpeg compression from the upload and its a major crop of the origional, but the difference i think is clear.
higher bit rates = less macroblocking and more fine detail.
it will not significantly reduce banding, we need 422 and ideally 10bit+ for that.

Just wait at least until 6th April :-) But I think the improvement will be significant. I just made few 120fps shots yesterday - those with shallow depth of field are very nice without any macroblocking... but others are where is everything is in focus are quite awful (especially in shadows). 80mbits are clearly not enough and it is most visible in 120 fps mode. 

Time limit hack works for NX30, NX300 and NX1100 for all video recording formats including 60fps 1080p. NX30 and NX300 shows 3579139 for total duration for all videos, if last two digits are decimal points, it will roughly equate to 34.67 GB corruption mark. 34.67 gb converts to 35502.08 and 35791.39 mb converts to 34.95 Gb.
NX1100 had a time duration showing instead of a constant, different times for different formats. NX1100 does not have an AE button, but substituting the Trash button worked to gain access to Dev Menu.

That is strange, I had macroblockin with the Atomos when I used it could be older firmware or something, whatever it was its just not worth to pay 1500 - 2000 dollars for an external recorder when there is already someone who managed to hack higher bitrate on the NX1, all the benefits you get with the Atomos will surely soon be available inside the camera, the HEVC in the camera if its following the standard set for HEVC, it should come with 10bit, 12bit and 422 + 444. There is also a MJPEG codec in the camera, my prayer to the heaven is someone manages to replace it with the MJPEG2000 codec and enables RGBA4444

That is strange, I had macroblockin with the Atomos when I used it could be older firmware or something, whatever it was its just not worth to pay 1500 - 2000 dollars for an external recorder when there is already someone who managed to hack higher bitrate on the NX1, all the benefits you get with the Atomos will surely soon be available inside the camera, the HEVC in the camera if its following the standard set for HEVC, it should come with 10bit, 12bit and 422 + 444. There is also a MJPEG codec in the camera, my prayer to the heaven is someone manages to replace it with the MJPEG2000 codec and enables RGBA4444

I have used the Shogun myself with the NX1 once on a short film, I did not notice much differences or gains so I just shot without it on difficult shots.
I think the NX1 only spits out the same bitrate its set in the menu out on HDMI, I might be terribly wrong but its what I think based on personal experience with the shogun and the NX1

They say the same thing for using Shogun with Gh4 and a7s. Huge unwieldy files and no discernible improvement in the image. Besides the monitoring benefits it doesn't seem like they really make the image thicker for grading. Seems like a huge price to pay to discover this.
 

Unfortunately it'll look like this:

colored and punched into problem area:

600+ mbps prores hq recorded on shogun from the nx1
of course that is gamma dr -10 contrast... so about as extreme as you can get, and maybe its usable in cases where you wont have gradients, but as i demonstrated a lot in the "your ideal nx1 settings" thread, increased bitrate will help us with shadows and highlights (we can improve usable DR by 2 stops is my guess), but we need 422 to get us away from banding.

Having a truncated MP4 file recovery utility running on the camera would be really cool.  To avoid complicated menus, the utility when executed could automatically scan the SD card for truncated files and automatically recover them.

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 :-)

No one seemed to have graded the video footage from Vasile so I decided to have a go and oh boy its glorious, the image has a very analogue feel to it at least in my opinion, I have tried to push the colours very far, much further than I normally would with the regular NX1 footage to see what happens, the NX1 suffers from colour bleeding at times specially when there is strong colour light on a scene like concerts etc. In this footage I did not notice any so that in itself is pretty glorious.
Everyones favourite, the Vasile Frame

EOSHD GammaDR2LOG LUT Applied

Quick Grade with VisionColor's Impulz LUT - Tetrachrome 400 and high colour saturation

A more colourful frame

No one seemed to have graded the video footage from Vasile so I decided to have a go and oh boy its glorious, the image has a very analogue feel to it at least in my opinion, I have tried to push the colours very far, much further than I normally would with the regular NX1 footage to see what happens, the NX1 suffers from colour bleeding at times specially when there is strong colour light on a scene like concerts etc. In this footage I did not notice any so that in itself is pretty glorious.
Everyones favourite, the Vasile Frame

EOSHD GammaDR2LOG LUT Applied

Quick Grade with VisionColor's Impulz LUT - Tetrachrome 400 and high colour saturation

A more colourful frame

No one seemed to have graded the video footage from Vasile so I decided to have a go and oh boy its glorious, the image has a very analogue feel to it at least in my opinion, I have tried to push the colours very far, much further than I normally would with the regular NX1 footage to see what happens, the NX1 suffers from colour bleeding at times specially when there is strong colour light on a scene like concerts etc. In this footage I did not notice any so that in itself is pretty glorious.
Everyones favourite, the Vasile Frame

EOSHD GammaDR2LOG LUT Applied

Quick Grade with VisionColor's Impulz LUT - Tetrachrome 400 and high colour saturation

A more colourful frame

@SMGJohn I've seen your video before . I like the look a lot. What's with the blockiness on the shot of the helicopter alone in the sky?
Even back when NoamKroll reviewed the NX1, it was pretty obvious that the camera could have some good information if you protected the highlights and underexposed slightly. That's a camera characteristic that should be independent of the codec. 
While you could raise shadows before and see some detail, you'd see a lot of smearing because of the coding trees. Now that the bitrate is higher, from what I understand, HEVC will dynamically end up making smaller coding trees to produce more data without the smearing. (I hate that it's now inaccurate to say macroblocking!). Thus the information is now less blocky and more deliverable.

We gotta remember here, H264 suffers at low bitrates whereas the HEVC biggest strengths are just that, at low bitrates! 
But the higher you go with the bitrate, the HEVC starts to suffer and loose against the ageing H264 and this simply comes down to the way HEVC is designed for, streaming and low bitrate use. Its not meant to be used in video cameras and for high bitrate use they specifically states it.
http://forum.doom9.org/showthread.php?t=170986
Here they do a huge comparison of the x265 versus the x264 and it shows, low bitrate it shows strengths but at high bitrates it does funky stuff.
Again here we see it once more, it destroys fine details in images even with the specific setting grain on http://forum.doom9.org/showthread.php?t=172458
Now the x265 is constantly under development the x264 was not perfect at its beginning either, but the NX1 uses early HEVC version unless there is evidence of it being updated in the firmware. HEVC is basically made to look good, not keep info which is why we have camera specific codecs to do just that.

The second image is incredible.
P.s. now think about what could be recovered if the bits were 10 instead of 8, with that high bit rate!

Hope these images sit within reason... May need to convert the H265 4k to something like a CineForm / ProRes / DNxHR 2K. These codecs might actually edit / process quicker than H265 and/or H264; particularly ProRes.
The grade is a single node:
Shadows at 50. (Kinda pushing it far... But, not too much to create halos.) Highlights down to -25. Midtone Detail is set to 40. (Kind of far here, too.) Saturation at 70. (Need the extra with raised shadows IMO) I threw in a simple curves adjustment, particularly aimed at the midtones. 1. Data Levels.

2. DaVinci Grade.

3. Video Levels.

Premiere doesn't like the default "data levels" of the H265 "fish tank" file. There is actually more dynamic range available in the shadows than what has been posted. In fact, DaVinci Resolve really brings the image to life if you input the file utilizing "data levels." Maybe I don't know Premiere well enough. Or, I'm just frustrated with Adobe?
Have never seen/graded NX1 footage before. Really excited to see this development take place and also frustrated to think how much tech is in the NX1 / NX500. Why is this tech being laid to rest by the manufacturer. Strange times, right!
From what I gather, this new bitrate is producing a natural response from the lens-sensor-processor-codec combination. It looks like it was shot at about 1600 ISO. Professionally speaking, this new bitrate may enable a new standard for accurately capturing an image without having to deal with random processing variations in the shadows/midtones/highlights. Hopefully, right.
Personally, I used to have quite a lot of issues with the GH4; specifically with regards to the lens-sensor-processing-codec algorithm. Eventually, I just went back to 1080 P DNG.
I'm impressed with render times with H265. First time for exporting an H265 image. Woohoo! DaVinci is exporting this 4k footage at nearly the same rate as the BMPCC 1080 DNG. It's possibly 1 - 2 frames faster with 1080 DNG pushed to the max 13 stops of DR and a light application of noise reduction. Then again, it's also only 1 - 2 frames behind 1080 DNG without the noise reduction. Kind of a nice balance, one with a serious bump in native image resolution. Does the footage need noise reduction? That's kind of what I'm thinking about here. It might actually need a fine layer of grain placed on top to reach a truly great image. But, who sees that stuff anyway?
Based on what others have written, over the past few pages, in regards to how h265 transcodes an image, I see the noise floor appear and also slightly disappear in this footage. It's nothing serious. IMO, I'm over analyzing the image. I feel that this was shot with contrasty glass set to a 5.6 in a room that reads somewhere closer to a T2.8 at ISO 800 on a LOG picture profile. Quite frankly, this combination is a challenge for any camera, especially when shooting with standard picture profiles, right?
Anyway, thanks for posting the "fish tank" video.
Also, it's not just the bit rate that's gone up, it's the heart rate too! I think the heart rate is closer to 100 BPM! LOL
Cheers,

Oh my god, the news on this thread is so exciting - I can't express it in ASCII/UNICODE.  How awesome, you guys made my week!  'm a lurker who finally signed up here, just to post a reply:
So, I'm a 'prosumer' camera user who purchased my NX500 around christmas (the 'big gift from family') based on the specs & price.  My idea was to shoot unattended from an unattended tripod, then crop (& potentially stabilize handheld footage) from 4K to FHD in post.  Sadly, once I started using the camera I was pretty disappointed.  The 15-minute/4GB limit (still an issue @ 4K if I understand correctly?), and for me especially the lack of manual video white balance control in the NX500 made my results horrible, even worse than my cheap old Panasonic TM-90 (which I know well and still love).
This 'forced auto' white balance on the NX500 is killing me!  It's tolerable outdoors but absolutely horrible indoors, resulting in unusable orange-on-yellow garbage that's pretty much uncorrectable since the auto-white-balancer is constantly shifting the white balance around...  (It seems like such a deal-killer, could I be missing something here?)
Having spent the evening reading this thread (I should have taken notes!), I was wondering if anyone has tried running the NX1's .BIN apps on the NX500 camera yet?  'IF' the NX1 video capture app could be made to run on the NX500 that would give us it's manual white balance control (among other things) and to me that would be HUGE.
I didn't return the NX500 because it's supposedly a quasi-open-source device and I was hoping something exactly like this would break open.  (Plus the fact that raising kids I can't justify spending more... anyway...)  Then when Samsung discontinued the product and left us in the lurch, just looking at it sitting on my shelf was kind of depressing.  It looked like a device with great potential, intentionally hamstrung for marketing purposes that was going to be a dead-end and a big wasted investment.  I was left monitoring developments by searching for 'NX500 firmware' every few weeks...
And now these developments...  I am super excited and want to contribute however I can.  Actually I'm a career software developer with over 30 years of experience.  Haven't done much low level hacking lately but know (some) Linux / (a lot of) C++ down to binary optimization (mostly windows) / etc and could probably do some heavy lifting, time-permitting...  Not much image processing background, but I think I understand at least the basics.
So, from my N00B perspective, and not wanting to brick my (now increasingly valuable!) NX500, I'd like to help (in descending order priority) 1) figure out how to get the camera to boot from the SD card, 2) get the camera to run NX1 firmware (more on this in a moment), and 3) remove the 15-minute 4K video recording time.
On the NX1 firm(ish)ware on the NX500 proposed project, the core question seems to be whether the camera is running the same FPGA or if Samsung fabbed different ASIC's for the different cameras.  Information seems conflicting on this, with FCC screenshots indicating they're different chips but FFMPEG reporting the same compression engine metadata.  So which is it?  It seems there's a good argument for both approaches (transistors are cheap vs. FPGA implementation battery run-time might be bad) If anyone can clarify this it seems this would determine whether this NX1 firmware on NX500 project is viable...  OR am I missing something here?  Admit I've had a few beers tonight...
On the 15-minute 4K time limit, it seems like the idea posted earlier of pre-allocating the MP4 files on the SD card is a viable pathway, since probably closing / flushing / opening a new file while straming is problematic and why the limit exists.  (Samsung - you could have just supported NTFS, duh!)  Or we could somehow just hook the '15-minute-limit-reached' event and re-initiate recording, it wouldn't kill me to lose a few frames (hundreds of frames is more likely :-p).  Or at least if the camera could beep a few times to let me know it's stopped recording, that would be a big improvement.  Or we could implement NTFS as a supported filesystem, that would be awesome!)
One last thing, SAMSUNG - IF YOU ARE READING THIS:  Look, you kinda screwed your customers by discontinuing your product line.  Sure there are business realities, but I think your sales could have been 50X if you had just completely open-sourced the firmware...  Seriously, this hardware has awesome specs and enthusiasts could have made this the cult camera of all time if you had just forked over the crown jewels...  (Probably IP licensing issues aside)  You could still do that and help compensate your shafted customers.  Or at least get your devs to push one more release out, removing all these silly caps.  If you're exiting the market, you're not cannibalizing higher-end or newer products!
All this being said, I want to end by thanking the guys who have contributed to unlocking the potential this camera holds.  Set up a paypal, I'll contribute as well as code!  I'm looking forward to seeing how this develops and to contributing as I can.
...  Interesting, it looks like the price of this discontinued camera is going UP!  If this pans out, folks might want to stock up on Samy cameras before they're gone...  ;-)
 

Thanks I would appreciate if you could look into the MJPEG codec, its quite an interesting thing they added for low fi video.

The higher bitrate has definitely seemed to help quite a lot, I also noticed less banding in blue sky with -10 contrast in GammeDR with 1.40 after they increased bitrate, which means banding issue can indeed be fixed with higher bitrate, now imagine what it would look like with 200mbps+ bitrate, the higher bitrate usually has quite a lot to say but I am still in favour of using the MJPEG codec in the camera over the HEVC one, the MJPEG is far less CPU intensive compared to the HEVC which is extremely CPU intensive, and the NOISE grain in the pathetic 480p MJPEG mode seems to have more details than the 2160p HEVC with 3200ISO does.
Now you might be asking why the hell would anyone want to use MJPEG over HEVC and the answer simply is that MJPEG is better at retaining finer details in images than the HEVC is and this is JPEG stills we are talking about, well somewhat. HEVC will still try to destroy details in images even at insanely high bitrates, its just how the codec works sadly whereas MJPEG will have better details at higher bitrates and this still is true with Canon old ancient cine line which shoots with MJPEG codecs and 4k, there is just more info in the images and they can be pushed around more. 
Sadly the Motion JPEG 2000 is not available in the camera as far as I can tell, if there was a way to implement that it would be king of king cameras, there probably would be no need for raw video, with high enough bitrate the MJPEG2000 is quite a beastly codec supporting RGB444 and even RGBA4444

One can just hope they see what the community has done knowing that the nx was at end of life I probley just bought one of the last ones that were at adorama has 1.32 firmware on it. Make them rethink the choice and maybe come back with the rumored lx version. I think it was called. But now that I have one the discovery and research time into firmware is going to go up. And as much as things moved the last week I think things will happen much quicker than with the other cameras that have been modded. Good bye sleep haha

The higher bitrate has definitely seemed to help quite a lot, I also noticed less banding in blue sky with -10 contrast in GammeDR with 1.40 after they increased bitrate, which means banding issue can indeed be fixed with higher bitrate, now imagine what it would look like with 200mbps+ bitrate, the higher bitrate usually has quite a lot to say but I am still in favour of using the MJPEG codec in the camera over the HEVC one, the MJPEG is far less CPU intensive compared to the HEVC which is extremely CPU intensive, and the NOISE grain in the pathetic 480p MJPEG mode seems to have more details than the 2160p HEVC with 3200ISO does.
Now you might be asking why the hell would anyone want to use MJPEG over HEVC and the answer simply is that MJPEG is better at retaining finer details in images than the HEVC is and this is JPEG stills we are talking about, well somewhat. HEVC will still try to destroy details in images even at insanely high bitrates, its just how the codec works sadly whereas MJPEG will have better details at higher bitrates and this still is true with Canon old ancient cine line which shoots with MJPEG codecs and 4k, there is just more info in the images and they can be pushed around more. 
Sadly the Motion JPEG 2000 is not available in the camera as far as I can tell, if there was a way to implement that it would be king of king cameras, there probably would be no need for raw video, with high enough bitrate the MJPEG2000 is quite a beastly codec supporting RGB444 and even RGBA4444

This is more along the lines of what I am working on. The bitrate mod that they did should be good for most. But I am diving deep into the fw, Still a good time away until my end shows any gains. But like I said a few posts ago the more I find the more excited I get. I can look at the mjpeg encoder cpp and see if things can me modded to allow a higher frame size. But again thats just adding to the list of things. But at least things have moved up! Maybe samsung will have an official word the more news of these mods get better known
 

Did a similar test. Ridiculously over and under exposed. I'm astounded. Given the lighting source I'm guessing we are looking at 800 iso or higher.