Pavel Mašek

I really appreciate your hard work as tester - it is really great contribution.
Honestly - I have tried one of very very early version of Kino Seed's version and then rather stick to original Vasile's BT hack becuase it basically fixed most important issue to me of NX1 (macroblocking) and I am fine with it (except longer booting). I know that last versions are probably big leap from earlier versions (also because of you)- I will definitely try it but updates comes so fast (which is great!) and I was 2 weeks without internet connection so I am little bit lost now :))   
BTW  :-) - my name is Pavel (first name) Masek (surname). MaÅ¡ek corrupted because of unsupported diacritics from FB login...

I really appreciate your hard work as tester - it is really great contribution.
Honestly - I have tried one of very very early version of Kino Seed's version and then rather stick to original Vasile's BT hack becuase it basically fixed most important issue to me of NX1 (macroblocking) and I am fine with it (except longer booting). I know that last versions are probably big leap from earlier versions (also because of you)- I will definitely try it but updates comes so fast (which is great!) and I was 2 weeks without internet connection so I am little bit lost now :))   
BTW  :-) - my name is Pavel (first name) Masek (surname). MaÅ¡ek corrupted because of unsupported diacritics from FB login...

Well now is the time
It's stable and pretty much fast. You don't need to follow exact last version, any from 1.47 are OK, but I recommend to use latest one at the moment. I'd say you find it more practical than sd-card scripts. Also there is a little "readme related" problem, since guys work fast and do so much things, there is no way one of them can be proper technical writer for the project and here is the problem (not so much problem but somewhat inconvenience) - early adopters might be in far more vantage point since they follow the progress with developers and there is no need to explain everything between them, and any last adopters need to ask more and more with each version of hack, because proper technical writer is very hard work and obviously not so beneficial in terms of progress.
It is what it is, yes. Early adopters are testers, so I can understand you if have no time for this, but here my 2 cents

not yet, keyscan is killed in the process of updating the hibernation image. Please be patient, I received the burner so i am working on it.

I have realized that it also proves also somehow limited computing capability on NX1 with high bitrates (what we see in 120fps and max 100Mbit is seen also in 4K with bitrate above 200Mbps)... I have made lot clips with 180Mbps and there were no dropped frames what I have seen so far (I have check it via PotPlayer). I think that 24p200Mbps should be without issues if 30p180Mbps is fine (lower framerate -> higher bitrate)... I think even 220Mbit should be fine.
I have not use Kino Seed's version yet but it should be same or better (according experience of Outerbeat and others), I will wait a little while to test it (morerover it seems that Otto K just found the way how to make it built-in which is great http://***URL removed***/forums/thread/4000563?page=5 )

You can catch some dropped frames with any bitrate, but this number increases with increased bitrates, yes. It's not about sdcard I presume, it's mostly of the camera settings which can affect codec itself and it goes wild. I can tell that even with standart 80 mbps bitrate, before the hack FHD@120 have dropped frames. It's heavily affected by camera settings and enviroment of the record.
Me too with sandisk 95MB\s
But you need to test your footages, it easy to do in any video editor or player, you just need to find file properties and see is there variable or constant frame rate. It will tell you about dropped frames during the record of this file.

I think you have slow card.
I have pushed bitrate from 180Mbps (no issues) to 250Mbit and get only 25 fps (it should be 30p) - recording time is more than 2 minutes without any slow card message (no sound)
320Mbit - works too but record. time around 20 seconds with only 22fps (no sound)
320Mbit - x5 timelapse works fine, full 29.97fps, no issues (thank you Kino Seed for suggestion! :-))
Lexar 64GB 2000x UHS-II, original Vasile's bitrate hack
So my opinion is that if you have dropped frames it means that card is not fast enough
 

Nope. This will require T-Kernel break-in and neither me nor any sane person would attempt this on anything BUT a burner cam.
If burner cam available and significant effort/time then chance > 0.
 
Nope. Kino Seed saw it in the kernel sources but from there to modding anything is like going from being me (hint: I am not a string theorist) to being a string theorist (like, for example, Sheldon Cooper). Comparison intentional because the fact that an interface (API) has been published does not mean it has also been implemented (just like Sheldon who has not yet discovered anything AFAIK).

just in case anyone missed it and wants to help: vasile started a gofundme for a sacrificial hack camera. all details here: https://www.gofundme.com/22d7kj8

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

Hi cisco150,
Well, the effort is/was spread between various contributors (in temporal order of first contribution):
Otto - initial break in the camera (through information gleaned from the NX500 service manual, which allowed access to a root shell); also various utilities that are enhancing the photo side of the camera as well as providing the user interface you can see used by various mod packs, and the bluetooth hook; low bitrate 2.5K mod for NX500. Myself: all my work to date was basically about video: access to DEV menu to (among others) disable video recording limits, high bitrates for all video modes for NX1 and NX500 and high bitrate for NX500 / 2.5K. I am also looking into other more difficult aspects of the camera operation but I won't comment about it because nothing came out yet. Kino Seed (and maybe others) - packaging and fine tuning the results of 1. and 2. above. If you would like to recognize the above work there's no one place for everything: Otto suggests you contribute to a charity as a recognition of his efforts. I am looking to get some more NX lenses (so far I am about 1/3 :-( of the way to my first wish (take a look here), and Kino Seed did not mention anything.
In addition, you might pledge here to help make a camera available to me to (a) stop using my own camera for my investigations - two months of intensive research use resulted in a loose power button that needs replacement and (b) to enable some dangerous experiments for which I do not dare risk my own camera but which might benefit the user base - an example would be a permanent hook that does not depend on bluetooth and would be instantly available upon power on.
Hope this helps
regards

DR of 180Mbps footage. Great thing is there is no macroblocking in lifted shadows, just litle lack of details... but still very good result I think. 
BTW - First image is unedited 0-255, Standard, MBL +8. Second is converted to 16-235 with some grading (also added saturation becuase there was lack of colours in shadows and just a little bit sharpness to left side of image)
 

 
 
 

(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

Just caught up with this thread, are most people formatting with the windows/other os format program?

Ive been using https://www.sdcard.org/downloads/formatter_4/
For the longest time it has worked way better than anything windows does, as my first test with a sandisk extreme pro 32GBs uhs-1 gave me 200mbs right off the bat. Try this and reformat the cards and see if you gain speed. Might work for the uhs-2 card that seem slower than they should.

Still sorting through firmware and dumping data from the camera. My day job has gotten busy so I have not had the time to post here but I have not slowed down my work. But whats happened is amazing, seems like more people are finding these mods, maybe samsung will notice.

I can confirm Outerbeats findings. I was lurking in the shadows until something bigger happens, but my video assignment for today made me to step forward and try to install the hack.
To my findings it was super easy and the hack works perfectly with my budget card Transcend Ultimate 600x 64GB SDXC 90MB/s Class 10 (which offeres best price/performance for the lowest price). The card heats up, but as others said already, until its hot to melting point (which won't happen), no problem at all. With that NX1 can do
- 200mbit for 6 sec
- 195mbit for aprox. 6,5 minut
- 190mbit no stopping after 12 minutes.. 

Not sure what changed, but great job guys, very much so!

@kidzrevil 
You just need to follow instructions on the dpr page, but I can put them here:
How to install:
1) start with a clean memory card (no files)
2) unzip the contents of the zip into the root of the sdcard
3) put card in camera, and restart
x) to uninstall mod - from custom menu> settings> Uninstall Mod
To change bitrate start the camera wait for [loading complete] message push EV button see menu and take "bitrate" option. There you can insert all numbers for each quality option, also you can push "current" and change current bitrate which camera operates right now, e.g. your last settings

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

Nice footage there, what was the grade / LUT?
High bitrates looking great.

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.

Most decent cards should be fine when operating in temperatures from -13F to 185F (-25C to 85C) SanDisk Extreme PRO® SDHC™, SDXC™ UHS-II cards Specifications

Depends on how it is, if the card is so hot you get burns you probably should just stop with whatever you are doing imao.
SD cards are generally designed to take take some serious punishment, they can survive up to 85 degrees Celsius which is pretty standard across any reputable card manufacturer.
http://kb.sandisk.com/app/answers/detail/a_id/4687/~/sandisk-cards-environmental-tolerance-(waterproof,-temperature,-magnetic-and

Thank to Kino Seed on dpr, here is great mod pack for nx500 with MENU for all options, so no more need for editing files to change settings!
There are some key-combination changes:
EV+...
AEL: immediate hibernation
UP: load UP profile
DOWN: load DOWN profile
Half-Press-Shutter: focus pull
mobile: telnet
EV: Main Menu
#############
Main Menu
- video birtates
- custom functions
- profiles
- settings
- hibernate
- sleep
Video Bitrates
lists all set bitrates, and allows for changing them persistently
(that means settings are kept even after camera restart)
Custom Functions
- focus stacking
- focus buttons
- batch recording (continuous recording)
Profiles
save/load UP or DOWN profile
save/load FullBackup (all camera settings)
Settings
- Silent Shutter (nx500 only)
- VGA to 2.5K (nx500 only)
- Uninstall Mod
NOTES:
- for the moment this mod utilizes only the BT-patch (loading from Sdcard)
- "checkbuttons" used for nx500 are not "holding" the preset values at the moment
- options / buttons starting with a "-" are not yet implemented
How to install:
1) start with a clean memory card (no files)
2) unzip the contents of the zip into the root of the sdcard
3) put card in camera, and restart
x) to uninstall mod - from custom menu> settings> Uninstall Mod
Download link
_____________________
I've tried this one on NX1, it installs OK but does not apply any settings yet, need some bug-fixing. I think in nx500 it must work great. though. Please try it and share experience

At first I'm actually was going to disagree with you, but then I'm remembered that I did exactly the same at one moment - disable record limit, and only after this I did try new bitrate parameters, increasing from 160 to 190 on my Sandisk. So... right now I run DEV mode and enable record limit back. Testing video... Records two files without errorrs, three files more than 1 minute lenght, - it is all ok with 190 mbps bitrate hack.
So, it might worth trying to disable record limit in DEV menu
 
Hi Soul-Brother. Well, first of all, I am talking only about usage some of sd-cards while running bitrate hack for NX1 cameras. It increases bitrate up to enormous 320 mbps, which can't be operate at any of sd-cards, no matter UHS-II or not. And according to that table in Blackmagics "sd card speed" document, which I've posted earlier, the brand new Lexar one is not good for record with such a high bitrates. Still, it can be useful for usual "PRO" bitrate in NX1, but I have zero experience on this, sorry.

One more thing (I really do not know if it can make any difference) - I have played with this hidden menu in past and checked "disable movie record limit".  But I doubt it would affect anything, but who knows... http://***URL removed***/forums/thread/3979382

Maybe it's not about exact 160, maybe it's, say, 158 - OK, and 159 - is not OK, so it's not codec issue, but more speed limits
Thanks, man, I will try this, but brand new Kingston that failed me is already moneyback'ed
It is very true, I've tested enough to say all of my cards been formatted in NX1 and in PC, and in PC they all been formatted in all of the block sizes. It's actually a huge test yep. I can say that you can easily format sd-card in PC, just use "standart block size" option, I think NX1 do the same, but slill, better do format in NX1