derderimmermuedeist

Driptease ;-)

hey guys, please find below my first serious attempt of shooting with samsung nx1. It's just a travel film but i wanted to be more like a manifesto for the people in Nepal that stood straight before a cruel fate. Did my best to put the edit together and to grade the footage the way i saw it. Comments are much welcome :
 

I thought that we could make a Database here:
Samsung NX1:
 68.374 KB/s  Lexar SDXC 64 GB UHS-II U3 / Class 10  50.740 KB/s  ScanDisk SDHC 8 GB UHS-I / Class 10  44.328 KB/s  Samsung Pro SDXC 64GB UHS-I  37.873 KB/s  Transcend SDXC 64 GB UHS-I U3  37.347 KB/s  ScanDisk SDHC 8 GB UHS-I  36.186 KB/s  Samsung Pro microSDHC 16GB UHS-I  18.217 KB/s  Transcend SDHC 32 GB Class 10  16.616 KB/s  ADATA SDHC 32 GB Class 6  12.772 KB/s  ScanDisk Ultra microSDHC 16 GB Class 10    3.735 KB/s  Transcend SDHC 4 GB Class 4  xy  xy Only Write-speed, only Samsung-inCam testet (for NX500 i will make a second chart here)
Please write your results here and I will log it

Samsung NX1 80Mbit Pro Bitrate Adjustment
                              How To
This refers to version 1.0 of the nx1-pba.sh script and ancillary files
as provided in the original archive.
NB this script forces NX1 to use your choice of bitrate instead of the
80 Mbit Pro rate. It DOES NOT replace other (lower) Pro bitrates.
I might consider replacing other bitrates at a later time but this is
quite time consuming as it involves hand-coding multiple ARM instructions.
Usage:
  0. Make sure your NX1 is on firmware v1.40.
  1. Unzip the archive into the root of your sdcard.
  2. If you are a Windows user, make sure you have either Notepad++
     or another text editor capable of editing Linux-formatted files.
     Notepad++ can be found at https://notepad-plus-plus.org/.
  3. If you are a Linux user you can use vi or nano or your other 
     preferred equivalent tool.
  4. Open in the text editor (see point 2 above) the file nx1-pba.sh
     from the scripts folder of the sdcard.
  5. Uncomment (i.e. erase the # character at the beginning of the line
     underneath the bitrate you want to use as PRO bitrate with NX1.
     Make sure you do NOT otherwise touch the content of this file.
  6. Close and save the file.
  7. Pull the NX1 battery for a few seconds, and reinsert it.
  8. Insert the sdcard into your NX1 - the script won't work otherwise.
  9. Power on the camera - this is a mandatory step !!!!
 10. Wait until the dots on the left edge of the screen appear and
     disappear. This will take a few seconds.
NB. the above steps are one-time (or until you decide you want another bitrate),
and as long as you no longer touch the files you just put on the sdcard
and you keep the sdcard inside the camera, it will keep using the adjusted
bitrate.
Congratulations, as of now and until you power off the camera, your PRO
bitrate will have changed :-)
  A final word:
If you find this script useful, I would appreciate a donation that I will use
to acquire more photographic equipment which in turn will give me additional 
incentives towards spending my nights looking into the NX system :-)...
You can send donations to http://paypal.me/nxplay - thank you in advance.
 
 
(This is the readme.txt)

I mean that the panning shot is now also much smoother (with the 160 Mb/s).

Reported.

We don't even know if the nx1 benchmarks does random or sequential reads. Or if it's threaded. It's complicated.

Just testet (with the tool in Dev mode) in Camera:
Transcend SDXC 64GB UHD-I:
Read: 68.571 KB/s
Write: 37.873 KB/s
 
Lexar SDXC 64GB UHD-II:
Read: 88.619 KB/s 
Write: 68.374 KB/s

I thought that we could make a Database here:
Samsung NX1:
 68.374 KB/s  Lexar SDXC 64 GB UHS-II U3 / Class 10  50.740 KB/s  ScanDisk SDHC 8 GB UHS-I / Class 10  44.328 KB/s  Samsung Pro SDXC 64GB UHS-I  37.873 KB/s  Transcend SDXC 64 GB UHS-I U3  37.347 KB/s  ScanDisk SDHC 8 GB UHS-I  36.186 KB/s  Samsung Pro microSDHC 16GB UHS-I  18.217 KB/s  Transcend SDHC 32 GB Class 10  16.616 KB/s  ADATA SDHC 32 GB Class 6  12.772 KB/s  ScanDisk Ultra microSDHC 16 GB Class 10    3.735 KB/s  Transcend SDHC 4 GB Class 4  xy  xy Only Write-speed, only Samsung-inCam testet (for NX500 i will make a second chart here)
Please write your results here and I will log it

I thought that we could make a Database here:
Samsung NX1:
 68.374 KB/s  Lexar SDXC 64 GB UHS-II U3 / Class 10  50.740 KB/s  ScanDisk SDHC 8 GB UHS-I / Class 10  44.328 KB/s  Samsung Pro SDXC 64GB UHS-I  37.873 KB/s  Transcend SDXC 64 GB UHS-I U3  37.347 KB/s  ScanDisk SDHC 8 GB UHS-I  36.186 KB/s  Samsung Pro microSDHC 16GB UHS-I  18.217 KB/s  Transcend SDHC 32 GB Class 10  16.616 KB/s  ADATA SDHC 32 GB Class 6  12.772 KB/s  ScanDisk Ultra microSDHC 16 GB Class 10    3.735 KB/s  Transcend SDHC 4 GB Class 4  xy  xy Only Write-speed, only Samsung-inCam testet (for NX500 i will make a second chart here)
Please write your results here and I will log it

Just testet (with the tool in Dev mode) in Camera:
Transcend SDXC 64GB UHD-I:
Read: 68.571 KB/s
Write: 37.873 KB/s
 
Lexar SDXC 64GB UHD-II:
Read: 88.619 KB/s 
Write: 68.374 KB/s

Just testet (with the tool in Dev mode) in Camera:
Transcend SDXC 64GB UHD-I:
Read: 68.571 KB/s
Write: 37.873 KB/s
 
Lexar SDXC 64GB UHD-II:
Read: 88.619 KB/s 
Write: 68.374 KB/s

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.

https://www.slashcam.de/artikel/News/Samsung-NX1-NX500---erste-Hackerfolge.html

My plan is to see if I can replace Pro bitrate from 80 Mbps with something else, say 47 Mbps (my age  :)) for example, without otherwise touching the menu system or firmware internals. 

That would be great! But everyone here would probably appreciate if you would have more than 100 years :-D  (say 150Mbps would be nice).  But I understand, that was just an example.... 

If i see it right (in the Chart) then the maximum Bitrate for the H.265 HEVC is at Level 5.1 (found this Level in the File-Infos of my NX1-Videos) 160.000 kbit/s, approximately 156 Mbit/s.
And interessting too, the maximum Frame rates:
c4k @ 60p
UHD @ 64p
an FHD @ 256p

I  know by experience that the NX1 is not very sensitive to heat.
I had placed in a vacation my camera at the pool - right in the sun (it was 30 degrees Celsius in the shade!).
After about 25 minutes UHD / 30p recording was still running - despite that one could hardly touch the housing.
Heat test passed! I would say.

If i see it right (in the Chart) then the maximum Bitrate for the H.265 HEVC is at Level 5.1 (found this Level in the File-Infos of my NX1-Videos) 160.000 kbit/s, approximately 156 Mbit/s.
And interessting too, the maximum Frame rates:
c4k @ 60p
UHD @ 64p
an FHD @ 256p

If i see it right (in the Chart) then the maximum Bitrate for the H.265 HEVC is at Level 5.1 (found this Level in the File-Infos of my NX1-Videos) 160.000 kbit/s, approximately 156 Mbit/s.
And interessting too, the maximum Frame rates:
c4k @ 60p
UHD @ 64p
an FHD @ 256p

higher bit rate would be enough for me to throw 100$, also 240fps @ 1080p would be an awesome bonus

If i see it right (in the Chart) then the maximum Bitrate for the H.265 HEVC is at Level 5.1 (found this Level in the File-Infos of my NX1-Videos) 160.000 kbit/s, approximately 156 Mbit/s.
And interessting too, the maximum Frame rates:
c4k @ 60p
UHD @ 64p
an FHD @ 256p

I  know by experience that the NX1 is not very sensitive to heat.
I had placed in a vacation my camera at the pool - right in the sun (it was 30 degrees Celsius in the shade!).
After about 25 minutes UHD / 30p recording was still running - despite that one could hardly touch the housing.
Heat test passed! I would say.