Dean

They'll never be able to enter the camera business again. The NX1 was the only decent thing they ever made anyway. All their other stuff (tablets & phones etc) are crap. 

I personally preferred the situation where nx1 was abandonware, since...it's abandonware even today, but more closed. They'll never start nx again, unless someone buys the mount. They could release a fw with some of the 50+ requests we did in the last year and half, but they preferred not to listen and instead to lock the mods. Just like they did in the past, they go their own route, never listening to customers.
 
That's why they failed with nx and why most pros never took them seriously.
 
 

They are evil and selfish. Dark side. Vasile, otto, kino are our team of Jedi.

I'm travelling to Venice, Italy for work tomorrow. I hope I manage to get some shots with the GX80 while I'm there as well.

On a side note, would anybody be interested in working on a pdf with stills or an instruction video that we could embed in the post, so as to make this quite clear for new users. ie check firmware, reset camera to defaults, wipe card, place files in root etc, I can edit it in an afternoon, but would like someone to just check that the information is indeed correct. maybe some small points relating to what cards work best, and what speeds you will get out of them (maybe 5 most popular etc) I have 3 lens adapters arriving for EF, OM and M42 if there is any info that can come from those too...  

This video is comparing the P35-100/2.8 and P12-35/2.8 lenses with various camera stabilisations on the Panasonic  G7, GX80, LX100 and Olympus OMD E-M5II.  All was handheld, and I was using both hands with elbows braced against my body and eye to the EVF.
These were all shot in 1080p/25fps, with the E-M5II using the All-I codec.  I kept it in 1080p as it was easier to get more or less the same crop/frame without having to move around.  I didn't bother white balancing all the cameras (I should have sorry), and I probably should have tested the P12-35/2.8 on the E-M5II as well.
The E-M5II is rock solid, and the stabilisation is better than any of the others.  The 1080p codec (at shallow depth of field) also looks better on the E-M5II, in my opinion than the Panasonic 20Mbps 1080p.  I need to test the 4k with some wide/detailed shots, but I'm sure the Panasonics will blow away the E-M5II.
 

thanks, those settings got mentioned a couple time in this thread I believe.
I own the 20mm and the 50mm 1.8 (cheap plastic version). both small, lightweight and convenient. I am a nikon d800 shooter so those are the only 2 I used and cannot compare them with other brands. Happy with them though.
Gifs were too heavy and the quality was too bad so I had do opt for a looping youtube video instead.
I uploaded the cinemagraphs here:
https://www.behance.net/gallery/36514809/Cinemagraphs-Flavie-Lea
Would appreciate your support by clicking the blue like button if you like them!
here is a hd vs 4k screen grab (retouched)

 

Guys, 200 mbps confirmed!
SANDISK Extreme Pro SDXC 64GB Class 10 UHS-I U1 95/90 MB/s
I did the test for new version of Kino Seed's mod-pack for nx500 and NX1, and can confirm all this functionality:
Record limit on/off (resets after every reboot)
Setting up bitrate for current mode
Setting up bitrate for any video mode in menu
Hibernate and Sleep mode
Custom functions - focus and batch
Saving and loading profiles
Saving and loading full backup settings
Also - functional key-combinations, like EV+MOBILE for telnet, it's just perfect actually
All of this you can run and setup without rebooting the camera. We did debug for NX1 and all functions are OK and safe to go. While I've tested bitrate hack in this MOD, I find out that now my NX1 and Sandisk now can operate with 210 mbps with little lags, so I set up 200 mbps and it goes smooth and easy. Happy to announce that NX1 now can do 200 mbps video record. Now I'm ready to do some test shooting.
Here is the mod-pack
Thanks to Vasile, Otto K and Kino Seed

Yeah try DIS with OIS on, it's very smooth on the 16-50 S. Tripod like if you hold still. I personally wouldnt use DIS without ois turned on if the lens supports it.
 
But I'm a fan of DIS turned on with vintage adapted glass too.

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...

I think that most everything they did with this camera was for their TV's.
Sharpening the image would be to give more of a WOW factor when watching home movies on their Samsung TV's. Being Samsung, I'm amazed that the NX1 is actually as good as it is. Most of what they do is pretty shite or else a sneaky copy of what Apple or some other company has already come up with. They are a shit company and they way they handle their camera business being a total failure is yet more proof.
The image does look overly sharp to me but still ... I love the camera.

All entitled to our own opinion.

I think that most everything they did with this camera was for their TV's.
Sharpening the image would be to give more of a WOW factor when watching home movies on their Samsung TV's. Being Samsung, I'm amazed that the NX1 is actually as good as it is. Most of what they do is pretty shite or else a sneaky copy of what Apple or some other company has already come up with. They are a shit company and they way they handle their camera business being a total failure is yet more proof.
The image does look overly sharp to me but still ... I love the camera.

Learning a lot about the NX1 from this thread. Must be the best resource for this cam on the internet.
Tried to make my footage a bit more filmy today. Used the EOSHD Log Conversion LUT with a DELUT (Norwich) over the top. NX1 & 16-50/2-2.8.
 

I dislike 80% of everything that comes out of FilmConvert,
Their Canon LOG presets don't knock me out, no. But I find everything needs to be adjusted a lot with FilmConvert or it's just too heavy.
 

Have you had success with this?
I've tried the Canon LOG with the EOSHD LOG for NX1 footage and never had any luck making it look decent.
The Red Gamma profiles seem to work a lot better with the NX1 flat footage IMO.
Also, I reckon FC looks better on the NX1 using the Arri Rec 709 profile but not with the EOSHD LUT ... i.e. using just Gamma DR settings at default. 
Cheers.

Tried some different LUTs with the NX1 today.
Im stuck at home guarding my dog after surgery, so this is what I can do for now basically.
 

I just sold my A7rii today. After having it for a few months I had nothing but huge headaches. I did many test with a 4k video devices recorder. Besides the worst rolling shutter I've ever seen no one seems to be talking about the horrible judder when panning. At first I thought it was just I'm shooting in 24p and viewing on a computer monitor at 60hrz. But further test in every setting, shutter speed and frame rate seem to have far more than every other camera I've shot with. Another problem is in 60p and 24p 1080 the noise level is bad. I also kept getting bad moire and aliasing in full frame 4k and 1080p especially in the highlights.
Granted as a small compact photo camera it's frickin pretty awesome. But for video the image only looks good in crop mode 4k and as soon as it moves or things in it moves it falls apart. I barely took it on a shoot because of how much testing I had to figure out before I felt comfortable with all its down sides. And is not worth it.
I went back to my Nikon D750 with a external recorder for now until I decided what to get next, but even though the 1080p image is softer everything else is far better. Rolling shutter very little. Noise level very clean upto 6400. Slow motion just as good as the 24p and very smooth. Color science far better. Dynamic range little less. Post with it is super easy. It's a shame this camera has gotten no attention, but it such a reliable camera its what we wanted out of the 5D Mk iii but quickly forgot about with all the 4k cameras that just keep adding more new problems, headaches, time and money all for the sake to say its 4k.

Hey, I am currently on a shoot for a music video for 3 - 4 days but I have checked my mail, if nothing I will personally contact Samsung regarding the SDK for the NX1 in the weekend.
My guess is its sensitive SDK with very deep hardware binding codes because no one has leaked it anywhere, which means Samsung is having you write a deal with them to keep it to yourself. I literally spent days searching for it without a single trace of it. 
I personally have no clue what this SDK is, what it looks like and what it does exactly, all I know is what I have read and heard there is no images of it either, Samsung is really keeping it close to the chest and I only read about some people having it, I tried contacting them but no answers. I highly recommend people go around try contact these people whom possess the SDK for the NX1.
I will take a wild guess and assume it looks something similar to the Tizen SDK but with more hardware control, I will just post the image of the Tizen SDK here, however realistically it probably wont be as amazing as we think but it might be a good start to construct our own set of developer tools.

It was written in the .cpp files showing the hz of the sd bus, this would be an incremental increase test that would just be raising it until it crashes or to the limit stated by the sd association. And if it changes depending on what type of file is being written to it. As well as tracking the sensor and chip heat out put to see if it is underclocked for a reason. Lots of fun.
 
 
Not at the point yet, still tearing it down. The base tizen didnt seem to change much through the updates. It was the control files for the camera, written in c and a whole new ball game. I do about 15 hours of work into this a week, which isnt much considering but things are moving. If you wanted me to just make hello world appear it wouldnt really prove much, at least not in the way that this camera works.

 
 
Have not got to that point yet, still diving into the code and doing a control file comparison, as the updates for the camera happened they state what they changed, and that is what the major key point of what Im doing is. Its one of the nexts steps though. 
 
I can update as I progress and post summaries of what I find. Just to find the rgb888 and lut info I had to look though about 15000 lines of code. Its tedious. But worth while for me in the end, so I will continue to dig and deconstruct. And update!

I posted about the work Im doing on the firmware side of the nx1 a few pages back, but it was/still is hidden for some reason. 
**no longer hidden on page 11 at the bottom. Much more detail about what I have found on the camera.**
To sum it up, I have been working on this the better part of 6 months, didnt know anyone else was interested until I found this thread a bit over a week ago and posted my findings. Im at a point of comparing the changes in the firmware versions to see how the code is written. I have uncovered the bootloader, the file format and language used for their custom control files for tizen, info on lut, rgb 888, sd card bus speed(its quite low should be ush1 u3 but its not set close to the speed stated in the sd association docs) and a few more things. 
My goal is similar to what the guy said on the gh2 hack. I had a hacked 144mbs gh2 I used for 5 years until moisture killed it a few months ago. The tech inside the nx1 should be capeable of pushing the hevc and the sensor to the limit, even if it shortens the life by 4-5 years its still cheaper than a red by a magnitude.

Ideal goals for me are raw/compressed raw output, see if cdng or another compressed raw format would work. As red raw is just their version of jpeg2000 modded for cine work.
There is not a deadline I have set to finish this, as this is just one of many projects I have on the go but comparing it to other cameras its quite promising.

Just did a small video on some shots I had lying around, still testing rendering, but rendering in 4k def. makes it a lot better, still highly compressed though. Anyway hope you guys like it, not much love was put into grading on this one, unfortunately.
 

These cams do look pretty nice and I'll probably get the 24-85, but I'd still love to see an update to the LX100. That could be the ultimate compact if done right. 

I don't think I currently have the experience or time to successfully modify the NX1/NX500 firmware. I don't even have one of those cameras. However it would be a shame to let the interest in this die, so I guess I'll post some of my notes/thoughts about the firmware in hopes that it might help keep the ball rolling.
Note: if you aren't into technical minutiae, the only interesting part of this wall of text is the bulleted list at the end detailing what is and is not possible in my opinion.
Here are the files listed in the header of nx1.bin (version 1.4.0):
version.info:    offset=0x0          size=0x3F   (same as found in /etc/version.info)
linux image:    offset=0x0130       size=0x00624748
idk:                   offset=0x624878     size=0xD8E9
linux image:    offset=0x632161     size=0x3192E8
linux image:    offset=0x94B449     size=0x638518
idk:            offset=0xF83961     size=0x01FF10
idk:            offset=0xFA3871     size=0xB35140
rootfs:         offset=0x1AD89B1    size=0x117A89FF     (lzo compressed ext4 filesystem image)
opt:            offset=0x132813B0   size=0x58E91C   (lzo compressed ext4 filesystem image)
pcachelist:     offset=0x1380FCCC   size=0x7000 (PAGECACHELIST, preceded by a header, I think)
idk:            offset=0x13816CCC   size=0x35BCC44  (lzo compressed. header indicates swap image?)
Anyone with the skills to reverse engineer a camera could figure this out pretty easily, but it was fairly tedious so maybe this will save someone 20 minutes of poking around in a hex editor. If anyone knows what's up with the files I've labeled "idk," I would love to hear about it.
The checksum algorithm is fortunately unchanged from the NX300 as far as I can tell.
As documented at sites.google.com/site/nxcryptophotography/diy-firmware
"width=32 poly=0x04c11db7 init=0xffffffff refin=true refout=true xorout=0x00000000 check=0x340bc6d9 name="JAMCRC""
"jacksum -x -a crc:32,04c11db7,ffffffff,true,true,00000000 [file]"
The main camera app binary is (I'm pretty sure) located at /usr/apps/com.samsung.di-camera-app/bin/di-camera-app in the rootfs. It seems to access the hardware through a relatively high-level API with the /usr/lib/libmm* libraries. libmmf-camcorder.so is particularly interesting. The function I've focused my attention on is mmf_camcorder_set_attributes(), which comes from libffm-camcorder and is used repeatedly in di-camera-app. It conveniently (and strangely IMO) takes strings as identifiers for the attributes that are apparently being set (why not just an enum? I suppose I shouldn't look a gift horse in the mouth...). Some of those attributes include "target-time-limit," "audio-encoder-bitrate," and "video-encoder-bitrate." The guy who successfully removed the recording time limit on the NX300 did it by modifying the instructions that set the variable being passed along with "targe-time-limit." I found the control flow instructions he mentioned in that thread, so it should't be hard to get rid of the time limit on the NX1, provided the camera accepts the modified firmware. The NX500 is probably similar. The "video-encoder-bitrate" attribute also looks promising, though it would take some more advanced reverse engineering to figure out where the values are being set.
So from what I've seen and read, here is what I think is and is not possible to modify on the NX1 and NX500:
Remove time limit: Highly likely. Seems to be the same as the NX300. Pretty easy too, if there aren't any new security measures in place. Increased bitrate: Possible. Needs some real reverse engineering to find where the rates are set for each resolution and quality. Noise reduction and sharpening: Possible. Haven't seen anything that looks like it's controlling these, but if setting the bitrate works, this should be possible too. FWIW I think that increasing the bitrate would help with the noise reduction issues. H.265 tends to smooth things out a lot to achieve low bitrates. Re-enable 2.5k on NX500: Plausible but difficult. It depends on whether they just removed it from di-camera-app, or if they removed it from the underlying libraries as well. Either way it would likely require actually adding control flow to the binary, which opens a whole new can of worms. Beyond my current ability, for sure. Focus peaking for NX500 4k: Maybe? I have no idea, really. There might be a good reason they didn't include it, there might not. 4k crop on NX1: Plausible but even more difficult. We know the hardware can do it, but it was probably never implemented on the NX1, even in pre-production. Gamma profile on NX500: Plausible. Similar to porting the NX500's 4k crop to the NX1, I think. 6k 24fps H.265: Highly unlikely. The H.265 encoder would have to support frame sizes larger than DCI 4k and be able to handle twice the pixel rate (clock speed) of 4k. Furthermore it would require implementing a brand-new video mode at a very low level. I can't say for sure it's categorically impossible, but don't get your hopes up. 10bit H.265: Nope. The H.265 standard does indeed allow for 10bit encoding, but I highly doubt Samsung would include the significantly larger (wider busses, more complex encoding) hardware necessary to do it. It would be a miracle if Samsung had really decided to go to all that effort and not use it. 6k or full sensor 4k at more than 30fps or 1080p at (significantly) more than 120fps: Impossible. The image sensor simply isn't fast enough. If you hope for this you will just be disappointed! RAW Video: Not really. It might be theoretically possible to dump the live-view feed as in Magic Lantern. Who knows how fast the SD card interface is, though. Certainly no more than 1080p. I can imagine tricking the GPU into packing 12bit 4k RAW into 1080p 444 HDMI like Apertus, but consider that a pipe dream. Don't get your hopes up. Anyway, that was longer than I expected, but I enjoyed poking around in the firmware, so I don't regret it even if it comes to nothing. It's a shame Samsung appears to be dropping the NX line; they are cool little cameras.
p.s. If you know anything I've said is wrong, please correct me; I'm learning this as I go along.

I reckon the did it so the user can play the H265 directly into their Samsung TV's