Pavel Mašek

2 hours ago, vaga said:

Dude that's awesome! No way that it's that easy. So cool!

What else is in the dev options?

"Multiply bitrate" option could be very nice :-).

9 minutes ago, Pavel D Prichystal said:

So I have a contact with Apple coder (not helpful to us, I know). He raised the question, if Samsung actually said "No" to us on receiving SDK for camera?
Did they sent us remote control just to shut us up or because we didn't specifically ask for it? Can anybody confirm that they said NO to providing us with camera SDK under any circumstances ?

I sent them email that SDK they provided is not for camera itself but just for remote control. I have asked them about NX1 SDK again but I really do no believe that they have it or they will provide it... but better than nothing.

23 minutes ago, hirsti said:

Hi, this looks like the form I filled out for the SDK for the remote control of the NX1 and not a SDK for the actual camera itself.  I received the SDK which is documentation and sample programs in Visual Studio, this just contains commands for creating apps that you can connect to the NX1 remotely and control basic functions.  It doesn't contain anything different to what Samsung's remote studio offers.

Argh, damn. I will check it, but it seems that you are right. I thought we have found our holy grail :-(

UPDATE: Hirsti confirmed me that it is not SDK to camera itself (just SDK for remote control). I am sorry guys, I should verify it before I post it here.

18 minutes ago, Marco Tecno said:

I think that's the sdk to build pc apps to work with a connected nx1.

Maybe, we will see.  

Couple of others (including Chant) have asked this  ( http://nxcameraportal.cloudapp.net/SDK/SDKTerms ) and it seems that it is first answer from Samsung we have (it took them at least 4 weeks). There is quite detailed form to fill in... so I hope it is not "just" sdk to build pc app. 

WOW, I have just received email from SAMSUNG to download link to NX1 SDK!

(well I am quite scared to upload it somewhere, but I think I will do it). I will try to download it in the evening and let you know.

Chant, is it the one you have? Do you think it will be useful? I am not any IT expert, so I really do not know...

Dear Customer

Thank you for requesting an NX1 SDK.

Unauthorized distribution of the SDK may be unlawful.

You are not authorized to upload, copy, or redistribute the SDK in any way.

Click the link below. After input your E-mail address which you used for SDK request,

you can download SDK.

Contents:

• Sample Source: Sample source codes are provided for your reference.

                      (Tool : Visual Studio 2010 recommended.)

• SDK User Manual: This document contains general information of SDK API and user instructions for the SDK.

Thank you.

On 13. 3. 2016 at 2:41 PM, Chant said:

The code excerpts I posted are from the firmware. The statement about the camera being able to do 240fps is something they didnt remove. Also found a bunch of tizen watch stuff. Bad housekeeping is good news.

But I have yet to find a video output path that is concise. Tons of data on the hevc and everything else, but its what pointed me to the srp and needing to do more research. There way a camera would dump data to an onboard hevc is pretty well documented. Follow the mipi csi-2 bridge a few steps to get to the encoder. but the difference is, if it was indeed just a "hard" core hevc in the drime-v it would be more self contained. Taking what I know of chip construction and "hard" core asic  implementation. The more I do the more I find on how it works and what can be done.

Chant, could you please share the SDK? I think we could add it to github ( https://github.com/ottokiksmaler/nx500 ). One place to show actual progress and results of NX1 hacking would be nice (SD sripts hacks/ firmware hacking).

22 hours ago, Chant said:

I believe I have found the sdk for the srp. And quite a few examples of the c scripting style used before it is parsed into the machine state and binary. Working backwards it should be possible to figure out how it is compiled and explore what lies inside the system. It seems similar to an fpga so it shouldnt be very hard to dissect. Things that can be added over just changing the config files. Will update as I go. Keeping these updates short as I have a lot to do with making sure I fully understand the inner workings of this system.

Could you please share this SDK with others? Maybe someone else would like to help with it.

2 hours ago, Marco Tecno said:

The issue of nx1 at iso 3200 in video is, imo, nr. The raw pictures at iso 3200 are totally usable, especially when downscaled to 16mp or below. Hence at 8mp they should shine! Instead, video at 3200 is very poor. Hence, there is something 'wrong' going on in the process.

One more thing related to possible NR: Just take a look on photomode when you have set higher ISO - it looks same as 120fps above ISO 200 and 60fps above ISO 400 and 30fps 4K above ISO 1600.  I do not know, but I think that "noise reduction" is related to some hardware glitch (higher frequency of sensor - higher "NR"... ?).

But I really hope that it is real noise reduction that could be removed by hacking...

On 6. 3. 2016 at 1:18 PM, chauncy said:

with what editing software? Adobe premiere afaik doesn't support hw decoding of hevc

latest update of adobe cc2016 does. Davinci's latest does as well

I have downloaded sd.tar and follow instructions for customizing keys (https://github.com/ottokiksmaler/nx500/blob/master/Customizing%20keys.md) but it seems that NX1 do not want to load it. Boot takes same time and  I do not see any green dots and text "IP..." after pressing EV+MOBILE.

-------------

EDITED: I can see the green dots with IP ADRESS sign (after change content of nx_cs.adj file to "shell script /mnt/mmc/scripts/EV_MOBILE.sh" ) but EV scripts still does not work.

1 hour ago, kidzrevil said:

Email filmconvert with the statement I wrote so we can get true support for the camera instead of using these workarounds.

Yes, it seems that we are close and it is worth to try...

I have post request about that on Facebook NX1 page... maybe couple of others will join us :-)

2 minutes ago, MountneerMan said:

What about decoding?

I feel like decoding 400Mbits/s HEVC  would be ridiculous both in time and finale file size.

I also think that most computers wouldn't be able to edit 400 MBits/s HEVC natively using adobe cc (or any other program that can handle it natively like edit ready or wondershare).

I think "just" 160/200 Mbits H265 would improve image a lot. But question now is not "how much" but "how"...:-)

12 minutes ago, Marco Tecno said:

If raw video gets unleashed through hacking, then all these questions will become 'the past'. Consider this: nx1 does 1) full sensor readout up to 60fps, then 2) scales it to 4k or 2k, then 3) encodes it in h.265 in real time.

Now...think about jumping steps 2 and 3 and just saving the raw sampled 6.5k image to sd card. Even if that were 12bit instead of 14, even if 24/25fps instead of 30/60, even if only for few minutes, this would be the greatest achievement ever in a sub 1000$ camera.

 

I would buy a couple of spare bodies if this ever happens.

 

 

But RAW image has to be scale down because bitrate would be insane in this case (24x around 30MB = 720MB/s). Maximum write speed of NX1 is 60MB/s (see http://www.cameramemoryspeed.com/samsung-nx1/sd-card-comparison/ )

43 minutes ago, Pavel D Prichystal said:

Casey, if you did any scientific tests, could you share your results? Image examples for downloads and detailed overview of your findings. Details Details Details pleeease, because we are keen to find out also!

I think it depends on everyone's taste - someone prefers dynamic range (and more filmic?), someone likes richer and more accurate colours. I have almost same settings as Casey... I did not make any scientific tests but my opinion is that (with this limited bitrate and 8bit codec) it is best solution to get best picture straight out of camera. But please - let's focus on hacking of NX1 in this thread... :-)

Answer on my email:

The NX1 is certainly under consideration.

We almost did it last year, and then Samsung started pulling that camera from the shelves. 

It isn't sold in these parts anymore.

This is in discussion, but I can't promise anything at this stage.

We've had quite a few requests for this camera in the last week so hopefully we can push that through.

9 hours ago, SMGJohn said:

I will personally contact Samsung regarding the SDK for the NX1 in the weekend.

Thank you. I have requested SDK too ... do not belive I will have luck, but better then nothing :-) (strange they need to know name of company, type of business, position,...etc.)

On 20. 2. 2016 at 7:30 PM, SMGJohn said:

You can request the SDK here http://nxcameraportal.cloudapp.net/SDK/UserInfo or through the i-Launcher application, I requested a copy now I just have to wait, apparently the SDK gives you control over the camera completely for development of software.

I have tried finding external download links for it, but no imbecile has bothered sharing it apparently. Talk about being greedy, I seen loads of people with the SDK tool but no one gives download link and their posts are usually months old.

Have you received SDK? It can happen that shell scripts will be deadend (I hope not) in way to higher bitrate...

34 minutes ago, SMGJohn said:

We need to disable the noise reduction in video, its killing me inside literally. You know its sad when the Panasonic FZ-1000 has better noise grain in 4k video than the NX1 which is just muffled mosquito noise, I had a look but could not find anything. Does anyone have any idea? 

I know the HEVC codec deals with fine grain texture poorly specially in my personal tests from converting Blu-Ray films to HEVC. 

But the NX1 has a nasty noise reduction in video which you cannot turn off and quite frankly its destroying details very badly. 

I am not sure if it is really noise reduction what we see in 4K (I wish it would be and we could turn it OFF). Just take a look on the 1080p 60fps and especially 120fps - anything above ISO 400/200 looks bad with very high noise reduction applied... and these are really low ISOs without actually any noise. So maybe it is same for 4K just with higher ISO... Also maybe 80mbit/s H265 is not enough to render noise grain,... so (at least 2x) higher bitrate could help.

Otto K and Marco - you are so great! Thank you... I am starting to believe that higher bitrate is possible... if 120fps1080p mode works on NX500.

See this (take from DPreview forum) - https://github.com/ottokiksmaler/nx500

Thank you very much for you hard work.... I think this is definitely best summary related to possible hacking of NX1! 

Let's hope that someone else will be able to continue this way to higher bitrate in NX1. 

3 hours ago, Marco Tecno said:

Possibly cropped? Or full sensor readout and then downscaled? These are very different things.

5D has option for lower resolution "RAW" (it is not exactly the RAW becuase of resolution, but bit depth is same as original RAW). That is someting that NX1 does not have. Moreover - NX1 would need also electronic shutter to achieve "video RAW in photo mode". It would be complicated even for Samsung engineers...

Let's focus on bitrate first... (...crop mode, lower sharpness or noise reduction)

That is really wonderful, very nice. "Bus" picture is magnificent. It is Samyang 24 1.4?

+1

Just check this for example http://***URL removed***/reviews/image-comparison/fullscreen?attr18=daylight&attr13_0=samsung_nx1&attr13_1=canon_eos760d&attr15_0=raw&attr15_1=raw&attr16_0=3200&attr16_1=3200&normalization=compare&widget=13&x=-0.7114353680119314&y=-0.5467697883462821  

or

http://***URL removed***/reviews/image-comparison/fullscreen?attr144_0=canon_eos760d&attr144_1=samsung_nx1&attr144_2=canon_eos760d&attr144_3=samsung_nx1&attr146_0=100_0&attr146_1=100_0&attr146_2=100_6&attr146_3=100_6&normalization=compare&widget=288&x=-0.09205517399148358&y=0.35844805042993694

Right now is VIVID my best settings: 

Color: Red x0.95, Green x0.95. Blue x1.00, Saturation 0, Sharp. -10, Contrast -5, Hue -3°, MBL -8, 0-255 

Vivid is too much saturated and contrasty by default so I put contrast and MBL down to achieve better DR and keep colors correctly saturated without addional grading. 

Below is screen form video (just changed luminance from 0-255 to 0-235 in Premeire), no grading and RAW converted to jpg without any editing. I have to say I really like the result - by default is video much nicer that un-edited RAW. According my testing is DR similar to DynamicDR gamma but with better colors (BTW I think the pink on the face correspond with reality - it was really cold :-))

I will do more tests but I like so far... maybe I will play with hue and satuation a little and use color checker board.

 EDIT: I would now put hue to 0 as the result is probably too pinky

I am new in Premiere too :-). 

It can be done via Fast Color Collector. It is described in this video within few seconds starting 1:55 https://vimeo.com/92613144  (he changed it just in one direction from 255 to 235 but same works also to 0/16 indeed).