sandro

Yes the edit drive is when I'm working on a specific project, I'll import the footage into that drive and create a PP project.
Cache files, I set up a cache folder on my 4TB storage drive.
My programs drive is a whole different drive. It's a 500GB SSD.

I don't think hdds configuration makes that much of difference. Yes you can get less jumps between different clips if positioned distant on the HDD because it needs to seek on the platters. SSD removes that problem. BUT I don't think you will humanly notice any difference. For these applications where the CPU is always the limit hdd speed is negligible considerand that most reach 100MB/s at least.

Definitely. I get 160mb on an old Mustang class 10 sd card and 180 on the lexar 2000x, so the issue is the data rate in camera, not towards the sd.

As for now and with latest update of Kino Seed's mod-pack I use SANDISK Extreme Pro SDXC 64GB Class 10 UHS-I U1 (95/90 Mb/s) for 250 mbps but you need to understand that bitrate actually recourse consuming option, and NX1 resourses are limited and other functions rely on them as well. So, with 250 mbps you can do very soft and slow footage without any complex scenes like smoke or fountains close-ups, fast moving objects or fast panning, So, if you intended to shoot, say, field and sky or interior from tripod without any fast pan or tilt - you be able to record like 1-2 good minutes of 250 mbps. I can manage like up to 4 minutes. And this is without sound, because with sound there is a problem with any bitrate more then 190-200, for now. With fast moving picture there is a problem - for encode this type of frame codec needs more resourses that NX1 can manage for this, so record drops with sd-card slow speed message. Presumable there is a memory problem involved and if I understand right - guys tried to manage this, but not yet and there is a big "maybe"
I think with latest script modifications and optimizations there is no big problem with any sdcard, maybe a little differences like 10 mbps so no big deal. You can use any sdcard with UHS-I or UHS-II specification

I would take a bet that no one will notice. Nearly ever film gets projected at 2K resolution anyway.

I personally hope they manage to disable the NR because I did some downscaling and tests with the ones they already uploaded and even though the ISO is worse at lower resolution compared to 1440p and 2160p it still is superior to the old 1080p footage with the NR in place.

(1) and (2): Some explanations.
Scripts are stored on the SD card. SD cards are optimized for sustained writes and generally slower than internal emmc flash, especially for mixed read/writes. When you start to mix script reads and video writes you are confusing the sdcard (internal) flash memory controller and since the card is optimized for large writes it will behave badly for short reads like those of scripts. Especially when these are comparatively rare in between long sustained writes. The ARM core running Tizen and the user interface is single threaded and not very fast (the fast ones are running the non-Tizen T-Kernel operating the camera hardware). You WILL see slowness because the UI has to wait for the keyscan to finish which in turn waits for the scripts to finish which in turn get read from a (comparatively) slow card the SD before it (the UI) can continue with whatever it was doing. the scripts heavily use the Linux shell, launching it every single time a script is launched (and remember for us scripts are launching other scripts - nested scripts). Bottom line, there are several things someone will need to do before you will get better performance:
RUN, don't walk, from storing any script/mod/hack on SD card. This is the single greatest reason for slowness, and to make things worse, it is highly dependent on card model (and more expensive cards will not necessarily make things better because it may happen that high end cards will work less well for small reads than cheaper "non-optimized for writes" cards. Otto is doing something about this but AFAIK it is still experimental although not rocket science. But you will also have to overcome your fear of storing mods internally. After all, once you did the BT mod, you basically did 95% of what is required anyway and successfully passed the "dangerous" phase of changing camera rootfs. I do think that we need to improve that mod to enable mod bypass during boot just in case something goes wrong with any of the internal mods, and that we need to have a "mod witness" permanently on the screen to show that mods are enabled, but this is minor. Eliminate multiple scripts from "production" mods. Scripts are fantastic for getting functionality in your hands and to allow fast test turnaround and mod interface evolution but ultimately there needs to be a consolidated mod that sits in ONE binary. This is, by the way, I think, one of the reasons for the fat di-camera-app that runs the entire camera UI. Script support needs to stay (both card and internal) but over time, all mods should aspire to be part of a main mod binary. Ideally, a mod should go through multiple stages: SD card based while it is evaluated and goes through fast changes and updates and while we are NOT CERTAIN that it will not damage the camera internal when determined as safe for camera and changes are not so frequent once stable and generally accepted, optimize and integrate as binary (non-shell script) in a main executable mod for fastest speed. There you go.
Also, from what I can see in the firmware, it seems that the data flow in the camera goes: Sensor => DRIME (that is operated by T-Kernel) => Tizen kernel => write on card. The reason Tizen and not T-Kernel writes on card is that you cannot have multiple operating systems write on the card at the same time. This means that if we bloat memory use on Tizen, its capacity to maintain sustained writes is lowered compared to what it might achieve with more free RAM. In turn, this means: avoid shell scripts or heavy programs (like my gdb bitrate mod version).
This, IMO, is also the reason the "poker" method allows faster performance than the "gdb" method. It is also the reason I am working towards an even better method than "poker" which will consolidate the "memory change" mods in one binary without the need to stop the di-camera-app multiple times (which is very time consuming for the CPU).
Finally: Would anyone mind starting something like a gofundme campaign for a NX500. Mine needs a replacement power button (I kind of abused mine I guess) and I am reluctant to keep working on it after I get it repaired.
It is too bad because with time, based on what I see in the camera, and if there was a developer community built around it, the hardware could achieve wonders. And to be clear, Otto, Kino Seed, Chant, and me do not "community" make IMO, like for example Magic Lantern. If you guys want anything close to ML you will need to do a lot more about spreading the word and competing for developers time/recruiting new ones.
Regards
Vasile

Ok, here are my findings from dodays shoot.

It slows down the camera. A lot. Like a lot lot! But most of us already know that right?
a) When the SD is clean + you have a lot of light + temperature is ok (around 22 degrees *C on the sun), it works beautifully for me at 190mbps with pretty budget card.
b) When the SD is filling up (30% and more filled up) + you are loosing good light (golden hour is dimminishing and you are pushing Iso from 100 to 200, 400,800,1250,2000..) + temperature drops (7-8 *C), it stops frequently. What worked with conditions a) is not working with b) anymore. The camera is getting slower (my opinion, nothing scientific), the card is stopping- this one is for sure and I had to drop it down from 190 to 165.. I wonder what is causing it?

Also:
Loading of script is slow. Really slow. When you run and gun, everything needs to be smooth, fast. And its not. There was a moment when the camera frozed, so I took out the battery, placed it in and got like purple error screen (Looked like when you drop your phone on the ground and the screen breaks, looked really bad). So I rebooted again and the script. Just takes a long time and when you are shooting in high cadency motion situations, those moments to load the script just feels like forever. And you are loosing a lot of time. Didnt had the time to check the files, not sure if recording before the script is loaded causes to record with previously modified bitrate or just standard Pro 80mbps.

Other then that: cadency is fixed,CTUs are better, more einformation is there.
The question is
- what caused the card to be so unstable in my todays recordings?
- Is there a way to make the script not slow down the camera so much?

@Soul-Brother thanks! Can you provide 4kb tests also? For science
@sandro  here is the test footages, 15 sec each, just a roundtrip with camera and shaking 3 times with incresing intense. One is 50 mbps HQ 4K, other is 190 mbps

The big issue would be the card melting into a sticky liquid inside the camera and...
Kidding aside, I was at a bar one night and a client returned a SanDisk Extreme SD card (20mbs) I'd forgotten about. Stuck it in my jeans pocket (in the little plastic case - which isn't watertight or dustproof). Then we had drink after drink.
Anyway, a few days later, I noticed an SD card sitting in the laundry room. My wife said, "Oh, that thing was in your pocket". It had gone through wash, rinse, and spin, and then into the dryer for an hour. On "cotton" or whatever.
I took it to my desk, out of curiosity I wanted to test it before I threw it out. But… I got busy, and it got mixed into my other cards.
I still shoot with it to this day, a year or more later (not fast enough for my current 4K, but it goes in the big Panasonic and my Nikons). I have no idea which card it is. Works fine though.

I see, you could try with this tool https://www.attotech.com/disk-benchmark/ and check if you see a pattern. There must be a block size used while writing files that could explain the "slow" speeds.

As a long time lurker watching the progress happen and trying out some of the hacks my self here is a brief summary of main accomplishments.
Current hack achievements in no particular order
Increased bitrate on both NX1/NX500. So far there is no consensus on the optimal bitrate. Further testing is required by experience videographers who are good at analyzing footage. Added 2.5k full sensor readout with increased bitrate on NX500. I do not own an NX500 so I am not sure what is really happening with this hack. Perhaps someone else could fill in. Removed video record time limit on both NX1/NX500. This is something I haven’t personally tested as I do not need it but reports sound like it works perfectly fine and can be used to record videos that will fill up your card. Fully electronic (silent) shutter on the NX500. Not yet working on NX1 from what I understand. There are currently three main ways to apply hacks to the NX1/NX500. The original method by running in factory mode by running a script on the SD card root called info.tg that can run other apps such as Otto K’s keyscan The WiFi method. Similar to the blue tooth method below but more risky. The best method is the blue tooth method. This is done by modifying the file /usr/sbin/bluethd in camera to execute a scripts that can run whatever other program you want. Telnet (busy Box) can be run from the SD Card to remotely execute any command on camera.  Alot of the built in camera commands have been figured out and you can now write scripts to make the camera do pretty much anything you want. Even I was able to written a few scripts .  
Current progress
Lately (past few weeks) the majority of the activity has been around trying to remove the in camera NR for video. There has also been quite a bit of talk about creating a GUI for all the hacks. If you are a programmer and are interested in getting involved I think this is likely the area where you could really help out.
  If there is anything I got wrong or missed please don’t be shy and call me out on it

Request:
http://***URL removed***/forums/post/57640350
Thanks

It is a shame to have a camera in 2015 with usable ISO at only 1600.

I woudn't expect nothing comparable to the a6300 in terms of low light performance from the nx1. It's just not made to work in low light.
If i get acceptable 3200 iso, i'm already happy. But of course... without all the nasty macro blocking.
 

http://www.amazon.com/Samsung-Wireless-Smart-Camera-16-50mm/dp/B00V5UDU60/ref=sr_1_2?ie=UTF8&qid=1461082163&sr=8-2&keywords=nx1
But please do not buy it in the hope that more capabilities would be unlocked by anyone. Nothing is guaranteed. See here why: http://***URL removed***/forums/post/57624059.

It is it was on YT with millions of views and they removed it.

Calling all NX1 owners:
16-50s brand new back in stock for $800
http://www.bhphotovideo.com/bnh/controller/home?O&sku=1022903&gclid=CKD1zqy0lMwCFclkhgodSlkBEA&Q&ap=y&m=Y&c3api=1876%2C92051677442%2C&is=REG&A=details
Edit: Looks like tons of lenses are back in stock, majority with HUGE markdowns.
12-24,18-200,45 mm all marked down $200
50-150 is only a grand. Crazy deals.

This is depressing.  

I hope NR is not built in the HW...

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.

No idea but I doubt it w/o replacing the codec. Chant might eventually be able to do something about it but don't hold your breath. At the moment I see a slight chance to get:
more resolutions (i.e. 2.5K on NX1) the high rate 2.5K on NX500 (subject to dangerous manipulations on burner cam) maybe higher res and rate MJPEG out of NX1 (although TBH I do not think it would reach the quality of 150-160 Mbps hevc) with a lot of luck disable or reduce video NR (I might take a look at this at some point in the future but this will definitely involve weeks of work so not too keen to start). Basically Chant is looking into adding true new stuff.
I have been looking more on the side of tweaking what's already in there - easier than Chant's ambitions but I already picked the low and medium hanging fruits.

I agree that a very big thing for nx would be turning off the terrible nr. And when I say 'off' I mean really off, completely. Both in jpg pics and - much more important - video.

So from what I shot I noticed there is 'slightly' more details on the noise grain, but the NR is still terrible and it seem to kick in at any ISO. But the grain has definitely become more detailed and less blocky with 160mbps hack, this can even be witnessed in my pictures I posted. Its only slightly it still looks Godawful and post-NR is not helping all too well with it because it causes mosquito artefacts.
I also noticed that images can be pushed more in terms of colour grading, a lot more until they start breaking and this is very good news, you can have a lot more contrasty images, shadow details are also slightly better, there is definitely less macroblocking in dark areas but again the NR is the biggest culprit here I think when it comes to crushing details in the dark areas.
The bitrate increase definitely seem to have its effect, definitely for 1080p50/100 which seem to benefit the most of it and needed it badly, but again its not noticeable above ISO 1600 because the NR is destroying details hence why I did not notice much different when I first tried it other than that its fine and there is more details per pixels and again this helps in grading a lot, the banding issues seem to have been decreased but they are not gone at this point I am just going to blame it on both HEVC and the NR for the banding issue, GH4 has no issue with banding like this at 100mbps with H264, its clearly a codec issue at this point when JPEG's are doing fine even at normal compression.
I never touch saturation settings except for in the normal picture profiles when I need artistic images right out the camera, other than that I only touch contrast and sharpness including adjusting the RGB levels, the pedestal is useless all it does it makes shadow either greyer or more contrasty, I suppose its useful for artistic means but for flat images it does nothing but destroying finer details and make noise more apparent so anyone who want flat images should stay away from the pedestal tool its as useful as it is on the GH4.
So thanks again Vasile, I did notice the camera became a tad slower with the 160mbps setting I did not try anything below the bitrate, it takes a while after you start it to react to anything but just a few seconds at most. I read some did not have this issue, perhaps it depends on the SD card.

I have mentioned this previously on other forums, the H.265 codec profile used within the NX1 is limited to 160,000 kbps, it's MAIN - Level 5.1, to go higher you need to change the codec profile. To get to 10bit the NX1/NX500 needs the newer version of the codec without which it is impossible.
https://en.wikipedia.org/wiki/High_Efficiency_Video_Coding