Otto K

Im considering getting an URSA mini (and I now have an NX1), because it has RAW, 10 bit color,12 stops DR, 4k 60fps and the amazing global shutter...thats enough to keep them both on a separate league IMO.

@vaga it depends on the setting, but this tool is, IMHO, better for data gathering as it has access to things some others don't. Oh, and for backup. 

@vaga it depends on the setting, but this tool is, IMHO, better for data gathering as it has access to things some others don't. Oh, and for backup. 

NX1 forum can be for all the Samsung cameras for now.

Interesting tool in firmware (at least on NX500): https://github.com/ottokiksmaler/nx500_nx1_modding/blob/master/Prefman_tool.md

Interesting tool in firmware (at least on NX500): https://github.com/ottokiksmaler/nx500_nx1_modding/blob/master/Prefman_tool.md

Things are moving fast guys.
I've created a sub-forum for any subjects which might require a separate thread.
Regarding compression on uploads or attachments, let me know if this is a problem and I will look into it.
http://www.eoshd.com/comments/forum/25-samsung-nx1-hack/

That is basically what Motion JPEG codec is and Motion JPEG 2000 which allows for 422 - 444 and 10bit

Interesting tool in firmware (at least on NX500): https://github.com/ottokiksmaler/nx500_nx1_modding/blob/master/Prefman_tool.md

Interesting tool in firmware (at least on NX500): https://github.com/ottokiksmaler/nx500_nx1_modding/blob/master/Prefman_tool.md

Interesting tool in firmware (at least on NX500): https://github.com/ottokiksmaler/nx500_nx1_modding/blob/master/Prefman_tool.md

Interesting tool in firmware (at least on NX500): https://github.com/ottokiksmaler/nx500_nx1_modding/blob/master/Prefman_tool.md

Interesting tool in firmware (at least on NX500): https://github.com/ottokiksmaler/nx500_nx1_modding/blob/master/Prefman_tool.md

Interesting tool in firmware (at least on NX500): https://github.com/ottokiksmaler/nx500_nx1_modding/blob/master/Prefman_tool.md

Interesting tool in firmware (at least on NX500): https://github.com/ottokiksmaler/nx500_nx1_modding/blob/master/Prefman_tool.md

The issue is not with speed of SD card, it's just that swapon command complains about the file structure if it's on SD card (don't know why, it's works fine on my laptop with Linux). Either way, speed of swap is not important as it has to write around 500MB in over an hour. 

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

@SMGJohn that's not how rolling shutter works and nx1/nx500 have a separate hevc cpu (block). 

@SMGJohn that's not how rolling shutter works and nx1/nx500 have a separate hevc cpu (block). 

Even before this hack, the shadows could be brought up quite a bit. Even in higher contrast situations than this. When you set the PP levels to 16-235 it actually shows, that the contrast here it no so harsh.
What I'm really interested in is testing these new things against the old things in the same conditions.

http://***URL removed***/forums/post/57461650
By the way, I'd like to ask you all to NOT name the bitrate and let everyone download the file if they want to know it.
It would be an interesting thing to see how long you can keep it under wraps and only discuss "around it" but without naming it explicitly.
I have no way to enforce this [oops, I just realized I do :-) and you know it too] but I do ask you to play by this rule, at least until I am back.
 

@SMGJohn
di-camera-app is leaking (not freeing after use properly) a small amount of RAM every frame it processes. Normally this is not an issue since it does not exhaust the available RAM in 30 minutes, but with time restriction lifted you hit it at ~75min. There are two options to fix this - find a memory leak and fix it in di-camera-app binary (hard) and this possible quick hack if you (or somebody else) is willing to try - create and enable swap file and use it (leaked memory is no actually used and can be safely moved to swap). For some reason swap file on SD card is not working (swap partition might, but it's too much work for an average person), but there is a writeable partition in camera already with ~2GB free, mounted on /opt/usr, so this might help:
First to see hwo things look before (all commands from telnet session):
[root@drime5 ~]£ free
             total       used       free     shared    buffers     cached
Mem:        511580     499896      11684          0       5260      70556
-/+ buffers/cache:     424080      87500
Swap:            0          0          0
[root@drime5 ~]£ df -h /opt/usr
Filesystem            Size  Used Avail Use% Mounted on
/dev/mmcblk0p14       2.3G  105M  2.1G   5% /opt/usr
OK, so we have no swap and have plenty of free disk space on /opt/usr, let's create some swap:
[root@drime5 ~]£ dd if=/dev/zero of=/opt/usr/swap bs=1M count=512
512+0 records in
512+0 records out
536870912 bytes (537 MB) copied, 42.882 s, 12.5 MB/s
[root@drime5 ~]£ mkswap /opt/usr/swap
Setting up swapspace version 1, size = 524284 KiB
no label, UUID=63995c82-cf71-43c6-ae32-34e520e7e280
Ouch, internal storage is not very fast... Let's turn it on:
[root@drime5 ~]£ swapon /opt/usr/swap
[root@drime5 ~]£ free
             total       used       free     shared    buffers     cached
Mem:        511580     506540       5040          0       4404      82108
-/+ buffers/cache:     420028      91552
Swap:       524284          0     524284
[root@drime5 ~]£ df -h /opt/usr
Filesystem            Size  Used Avail Use% Mounted on
/dev/mmcblk0p14       2.3G  617M  1.6G  29% /opt/usr
Yup, it works
You have to do everything before swapon only once, after that (and after every reboot) you only have to re-enable the swap with swapon /opt/usr/swap
I hope sombody with enough free time tests this, I have a good feeling.

@SMGJohn
di-camera-app is leaking (not freeing after use properly) a small amount of RAM every frame it processes. Normally this is not an issue since it does not exhaust the available RAM in 30 minutes, but with time restriction lifted you hit it at ~75min. There are two options to fix this - find a memory leak and fix it in di-camera-app binary (hard) and this possible quick hack if you (or somebody else) is willing to try - create and enable swap file and use it (leaked memory is no actually used and can be safely moved to swap). For some reason swap file on SD card is not working (swap partition might, but it's too much work for an average person), but there is a writeable partition in camera already with ~2GB free, mounted on /opt/usr, so this might help:
First to see hwo things look before (all commands from telnet session):
[root@drime5 ~]£ free
             total       used       free     shared    buffers     cached
Mem:        511580     499896      11684          0       5260      70556
-/+ buffers/cache:     424080      87500
Swap:            0          0          0
[root@drime5 ~]£ df -h /opt/usr
Filesystem            Size  Used Avail Use% Mounted on
/dev/mmcblk0p14       2.3G  105M  2.1G   5% /opt/usr
OK, so we have no swap and have plenty of free disk space on /opt/usr, let's create some swap:
[root@drime5 ~]£ dd if=/dev/zero of=/opt/usr/swap bs=1M count=512
512+0 records in
512+0 records out
536870912 bytes (537 MB) copied, 42.882 s, 12.5 MB/s
[root@drime5 ~]£ mkswap /opt/usr/swap
Setting up swapspace version 1, size = 524284 KiB
no label, UUID=63995c82-cf71-43c6-ae32-34e520e7e280
Ouch, internal storage is not very fast... Let's turn it on:
[root@drime5 ~]£ swapon /opt/usr/swap
[root@drime5 ~]£ free
             total       used       free     shared    buffers     cached
Mem:        511580     506540       5040          0       4404      82108
-/+ buffers/cache:     420028      91552
Swap:       524284          0     524284
[root@drime5 ~]£ df -h /opt/usr
Filesystem            Size  Used Avail Use% Mounted on
/dev/mmcblk0p14       2.3G  617M  1.6G  29% /opt/usr
Yup, it works
You have to do everything before swapon only once, after that (and after every reboot) you only have to re-enable the swap with swapon /opt/usr/swap
I hope sombody with enough free time tests this, I have a good feeling.

@SMGJohn
di-camera-app is leaking (not freeing after use properly) a small amount of RAM every frame it processes. Normally this is not an issue since it does not exhaust the available RAM in 30 minutes, but with time restriction lifted you hit it at ~75min. There are two options to fix this - find a memory leak and fix it in di-camera-app binary (hard) and this possible quick hack if you (or somebody else) is willing to try - create and enable swap file and use it (leaked memory is no actually used and can be safely moved to swap). For some reason swap file on SD card is not working (swap partition might, but it's too much work for an average person), but there is a writeable partition in camera already with ~2GB free, mounted on /opt/usr, so this might help:
First to see hwo things look before (all commands from telnet session):
[root@drime5 ~]£ free
             total       used       free     shared    buffers     cached
Mem:        511580     499896      11684          0       5260      70556
-/+ buffers/cache:     424080      87500
Swap:            0          0          0
[root@drime5 ~]£ df -h /opt/usr
Filesystem            Size  Used Avail Use% Mounted on
/dev/mmcblk0p14       2.3G  105M  2.1G   5% /opt/usr
OK, so we have no swap and have plenty of free disk space on /opt/usr, let's create some swap:
[root@drime5 ~]£ dd if=/dev/zero of=/opt/usr/swap bs=1M count=512
512+0 records in
512+0 records out
536870912 bytes (537 MB) copied, 42.882 s, 12.5 MB/s
[root@drime5 ~]£ mkswap /opt/usr/swap
Setting up swapspace version 1, size = 524284 KiB
no label, UUID=63995c82-cf71-43c6-ae32-34e520e7e280
Ouch, internal storage is not very fast... Let's turn it on:
[root@drime5 ~]£ swapon /opt/usr/swap
[root@drime5 ~]£ free
             total       used       free     shared    buffers     cached
Mem:        511580     506540       5040          0       4404      82108
-/+ buffers/cache:     420028      91552
Swap:       524284          0     524284
[root@drime5 ~]£ df -h /opt/usr
Filesystem            Size  Used Avail Use% Mounted on
/dev/mmcblk0p14       2.3G  617M  1.6G  29% /opt/usr
Yup, it works
You have to do everything before swapon only once, after that (and after every reboot) you only have to re-enable the swap with swapon /opt/usr/swap
I hope sombody with enough free time tests this, I have a good feeling.