vaga

Sony should start making their cameras with optional heatsink+quiet fan attachments accessories.  Seriously, we would rather have that than an unpredictable camera.  And maybe the processing unit can be clocked faster for less rolling shutter.

Petty outstanding. Curious of seeing what it could be done with gammaDR and Andrew's lut.

Looks like pretty good highlight recovery too

YESSS! Incredible!  
I am also surprise that playback is realtime in full resolution in Premiere (it was choppy but I had to move the file to SSD, then it was fine). (i7 3,2Ghz, SSD, Nvidia GTX960 with h265 support). 
I think it is not against Vasile's rules - here are just 2 images - default and graded. The shadows noise is very usable - my opinion: it is not fine noise, but look at that - default was completely black in shadows!
 
 
 
 
 

Sweet Jesus and Lord in Heaven, I wonder what happens when you do GammaDR with that stuff, because I tried screw around with the clip in post and imao the range, the range! 
I hope there is a way to use the MJPEG codec for 2160p as well in high bitrates, that would be sweet.

GH5 Would be an awesome camera to me if 
 The sensor is bigger than M43 like the one JVC use.
10bit 4:2:2 internal processing and HDMI out with like the GH4.
Better internal codec and colour science with more info for post work.  
Manual  focus Zoom  in  option while recording.
Better slow-motion options.
Slightly bigger body than GH4 and Do not make it smaller than GH4.
One  or two extra stops of light sensitivity over GH4
 
Panasonic can also add dual base ISOs and IBIS  if they feel like giving us more
 
The only thing that is going to make the GH5 popular like GH4 is the sensor size. not 6K.

That would be great, but they should really give it a try and make a mirrorless version with EVF, it would suddenly make the A7X totally irrelevant for people with EF lenses only because of ergonomics. I guess they should have enough confidence in the double pixel AF.

Hello and thank you for your hard work. Do you think it would be possible to get a subsampling 4.2.2 in Nx1?

Jesus Christ I had a look at that file and the noise grain is way better looking than my NX1, and I went to see why.
And turns out its got almost 75% more bits per pixel now I know its got half the resolution of the NX1 video, but the more bits per pixel is generally a good thing because the pixel has more information, and the more information the better for everything specially for this kind of resolution, not bad at all.
It will be interesting to see what the higher bitrate will do to the NX1 video and hopefully it might solve the terrible noise streak on ISO 3200 and above.

I think vasile's idea of using the existing menu and then just overriding the bitrate values that Samsung has assigned to the options is probably the best option because it is the most integrated. Another potential option could be to add a menu option to pull up the keyboard and ask for a custom setting of resolution, frame rate, bitrate (and maybe anything else necessary like video profile).
We should try to avoid out of place, unintegrated UI if possible. It just adds clutter. 
 
@vasile can you explain what tbn and tbc are?
 
Also, can you check if there is a flag or something in the Dev menu that lets Samsung know if the video time limit has ever been disabled? (Assuming of course that you can uncheck the box in the menu).

Astral photography isn't the first thing I think of when I consider the type of photographer I am, but the experience of researching and going to this spot and tirelessly researching the techniques it took to get this shot I think really does sum me up. This is why I love this forum and what Andrew has done with EOSHD. I'm constantly reading what you all share and love the community aspect of being a creative person in this day and age. I very easily could've died getting this shot as I almost was bitten by a rattlesnake in the dark when helping another photographer with her camera settings. Makes it an even more memorable experience for me. 

It seems that way, or at least going down the bit stream things are implemented. There is so so so so many cpp files as you have probley seen. But thats part of the task haha! The hevc stream is interesting if you feed it into a parser. the compression is very dynamic. But pumping it up to the max of the sd bus speed could garner results. The gop of the file I tested was 15frames(500ms) So there is some possible quality improvements from there.

OttoK has a really good githud that he is updating regularly. Perhaps you could start a githud page for what you are working on (back end NX1 stuff). Even if its more of just sort of "blogish" updates at this point. I believe github is free but I honestly don't know. 
I am extremely excited reading the progress both of you have been making :). Keep up the good work, both of you.

So this sounds like lossy RAW on NX1 might be possible.
does anyone have an idea on how to easily toggle this lossy raw setting, if it's possible at all?

You'd normally go wide and deep depth of field, then keep your subject around the hyperfocal distance of your lens. That way, no AF required. It takes balls to rely on your camera's C-AF as most will hunt around a bit.

Admittedly, Andrew did try one of the first ones and concluded that, and I'm pharaphrasing, 'ok, this is a thing now and it's kinda decent'.
I went and got one of these glidecam mechanical things from China too to go with the GH2 and Tokina 11-16mm way back when. Quickly gave up and when these electronic pistol grip gimbal stabilizers started to pop-up, I perked my ears... opened my eyes. But I've been waiting forever to reach a certain point I'd felt comfortable getting one. Especially since the earlier ones really showed signs of like a delay on the correction and then correcting in a digital and excessive way, really robotic, not organic. That one video with the Pilotfly H1 then looked really nice and this H2 went up in processing and controlling and as well important: way of set-up. I looks like an OSMO-type device for mirrorless cameras and DSLRs now. Seems like a nicely polished product. Allows you full freedom and flexibility, you can use the tilty-screen of your camera, you can attach a monitor rather easily. It's looking good. I guess the pre-order special price runs until the 21th, so I got a little longer to make up my mind and indeed, hopefully more videos will come out!

Those are NOTHING! Man, you should have seen the complaints on the first year of the Nebula 4000!

Almost all the gimbals rack up complaints.

Mine was all hosed up when it arrived - thought it was defective. Turned out someone loaded in the wrong PID software profile in manufacturing.
Loaded up the correct one from the drop-down list. Then did the 20-second horizon auto-calibration and it's been right on the money ever since.

Here's a clip the include both the A6300 and the NX1. Not the greatest example because it looks like the saturation and contrast are not turned down on the NX1.
I did not shoot it.  Looking at crop fact, rolling shutter, ergonomics, battery life and over heating the NX1 wins.  Looking at the picture I see in the video above I like the A6300 better.

If you look at the github closely it isn't 98fps it is 23.98fps options.

Simple "hack" to enable silent shooting in single mode (not CH/CN):
[root@drime5 ~]£ st cap capdtm getusr 117
UserData is ADJUSTSHUTTERTYPE_MECHA (0x750000)
[root@drime5 ~]£ st cap capdtm setusr 117 0x00750001
UserData is set
[root@drime5 ~]£ st cap capdtm getusr 117
UserData is ADJUSTSHUTTERTYPE_ROLLING (0x750001)
ROLLING is full electronic shutter
Now, why Samsung did not enable this in the menu I have no idea... It's fully working in full resolution JPEGs and SRW files.
I have not time to test whether image quality suffers, but it looks OK to me
Could someone check if it works with NX1 as well?
Cheers and have fun,
Otto

Dude that's awesome! No way that it's that easy. So cool!
What else is in the dev options?

Actually never mind, RS is the parameter of the single frame, so there should be no correction for fps. So 25p RS should be identical to 24p, while 30p should be 1.225^2=1.5 times smaller(26ms). This makes sense, it should be kept under 1000ms/fps, otherwise the next frame starts before the current one finished processing. So for 30p RS should be under 33ms, while 24p under 42ms.

He's not a developer, he's a "Senior Marketing Manager."
If Samsung is like many other semiconductor and consumer electronics companies, I very well might.

What else is in this DEV menu?
Care to take some screen shots and upload? 
 
Also on behalf of everyone thank you your hard work is much appreciated.

ok, here are some quite interesting strings found in the NX500 firmware:

UseNoiseSuppressor
video-encoder-bitrate
VideoProfile
video-color-range
Sharpness

:-)

Still digging...