outerbeat

Latest versions since 1.47 of KS-pack are not only faster with gui, it also seems to be faster with sd-cards due some optimizations in scripts. I can say that with first 1-2-3 versions of vasiles bitrate hack I can reach 140-180 mbps (depends on the card) and with latest versions of NX-KS I can use 190-260 mbps with pretty much the same cards.

But I really, really recommeng to read all info about this on dpr or github since guys mostly conversate there. it's not about that you can't use the hack without reading, of course not, you can, but there is known issues that not only mentioned but resolved in this threads, and there is unresolved ones, which good to be aware of. But in most cases all NX-KS works very good, bitrates, focus options, overall stability - is fine now
I can manage to use automatic focus pull with MF-switched lense during the video record with 120 mbps bitrate via Otto's script in NX-KS pack, which is VERY cool option. Same thing via telnet works faster for now, but with new optimisations I think there is a good chance to reach very-very good stability and speed in this. It looks just incredible, you know.

Yeah, I understand this it's cool, but I must say that latest versions of KS-pack are very, incredible fast compare even to early versions of KS-pack and of course to vasiles bitrate hack. It's because that now KS-pack use internal memory of camera to locate the scripts, now they are not on sd-card, so it works sooooo much faster than sd-card based scripts. Scripts are basically the same with some optimisations.
Thanks I think there lot of guys do the same, not only me of course, and even little help is help, so big thanks from me to all who seek any errors and inconveniences with this project, suggest new ways and produce other add-ons to the hack.
Oh, sorry about that, I know where I did mistake yesterday. Thanks for clearing it out, now I will use your name properly

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...

@lucabutera I've posted here screen grab from this footage and drop the link on original NX1 file few days earlier. Youtube version is far from ok for the any test unrelated to youtube itself ))
Here the link to original 250 mbps file from this session. Author send me this one since he doesn't registred at eoshd and dpr, and give me permission to share
Yeah, there is dropped frames all right. Also bit windy day so tripod is shaking and it's author's first shooting after he installed bitrate hack ever.

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

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.

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

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

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.

We tested NR all around and there is no evidence than NR on or off did any difference to footage in NX1
On nx500 with mod-pack there is the 2.5K enable option without NR whatsoever, well it's noisy allright ))
 
Also here is the LUT for my 200mbps test footage if anyone interested, I did it myself, so, use it freely

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).

It's here (this link contains all the versions and commit data) 
https://github.com/ottokiksmaler/nx500_nx1_modding/commits/master/NX-KS.zip

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

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

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

It's just about sd-cards mostly. This bitrate is perfectly utilize nowadays sd-cards speed and works without errors or lags. I've tested now like ten 64 GB sd-cards wide variety of prices and vendors, they pretty much the same when it comes to speed of NX1 sd-card driver (? idk how it calls) and top bitrate which I can use is no more 190 for now, but I'm going to test further  
Sandisk Extreme Pro UHS I 95MB/s 64GB is fastest one that I've tested. I can use it with 190 mbps easily, it works fine, but to be sure I just fly with 180 mbps.
Strange thing, when I did first testing of bitrate hack, all of my cards goes with "card is too slow" message when I tried to record video, and first bitrate, that any card allowed me is 140-160 mbps. But IDK how, when after some shooting with 140-160 mbps bitrate I've put the same sd-card but with 180-190 mbps option, run record, it goes with same error after 3-4 secons video... and after that allows you to go with 180-190. After that it goes smooth and pretty fine with 190. Can't say the reason, I don't know it, but I can recommend this way to any testers - just go first with 200 mbps, wait for "card is too slow" message, go second time, go third, if message still appears, turn off the camera, set 190 mbps, run 1-2 record with error message, and maybe now you can do 190. If not - go to settings and decrease bitrate one step more, repeat previous step "with 1-2 errors"..
Second sweet spot of bitrates - is size of sd-card. Actually, this one works with "record limit" hack. This hack allows you to record more than 30 min video. For UHD@30 it's 76 minutes with sound and not limited without audio (one user on dpreview said that but I didn't test this yet). So, now you have 76 minutes limit, ok. And now we can set 120 mbps bitrate for UHD@30 and this is a truly sweet spot for this two hacks - now you can record like 74-75 minutes 120 mbps UHD@30 video without any fear to get the error message or crash without message at all (NX1 did this with 4K video that exceed time limit 76 min). It is very cool!
One page before I've posted the test results of my bitrate hack test. There is 4K video file that I create from two 4K footages one 80 and other 150 mbps. They just heavily destructed (only luma curve + brightness + contrast) for more visual reference, left side - 150 mbps source, right side - 80. Both recorded in UHD@30 with identical setting and environment, only difference is the bitrate. Scale to 300% for better proof and to eliminate influence of export bitrate. Can you see the difference between them? For me it's obvious, and this test - is how I actually open my eyes to see all the power of High Efficiency Video Codec implemented in H265. Highly recommend to learn about it, worth knowing. 
If by "motion cadence" cinematorgaphers means some sort of undescribed mixture of shutter speed, framerate and limits of modern encoding process, but from "artistic point of view", then I can tell, bitrate hack definitely improve this, yep. I'd say HEVC theoretically wins in this field when it comes to any lossy codec, and it improves greatily from bitrate hack. Overall quality of picture is improved, each frame is far more stable in terms of color, light - all this parameters, that goes to codec and being encoded, and this goes more smoothly, this also applies to the serial set of frames.

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

The actual link, installation guide and core features of mod pack for NX1 and nx500
Download: link to package always updates, so you get last one for the time of downloading
Thanks to Vasile, Otto and Kino Seed
Key-combinations:
EV+...
AEL: immediate hibernation
UP: load UP profile
DOWN: load DOWN profile
Half-Press-Shutter: focus pull
mobile: telnet
EV: Main Menu  (NX500)
OK: Main Menu (NX1)
#############
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)|
- Kill switch (removes keyscan and gui from memory)
Profiles
save/load UP or DOWN profile
save/load FullBackup (all camera settings)
Settings
- Silent Shutter (nx500 only)
- VGA to 2.5K (nx500 only)
- No Rec Limit
- Uninstall Mod
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

So, if you using one of the Kino Seed's packs, here is the one, which didn't freezes the camera if mod boots with EVF, version 1.37 (and following I think)

I think it's never, but at some point there is price/quality question, like hmm I can get 100 minutes of pretty much FINE footage or 40 minutes of superb, and also it about keeping  footages after you acquired it and so on. Maybe the price is high for one and nothing to other, well it's just it
As for me, here the deal - I can easily say that I don't see any dfference in some scenes between 80 and 180, and in some scenes I can spot the difference between 160 and 180, and can predict that there is scenes, where 250 mbps isn't enough. It's really just question about how much is enough and how rare is not

If I may present to you: screengrab of 240 mbps test footage.

Yep. Did try this and seconded your result - camera need to battery pull off. I'm using 1.30 version and get this bug, Which version you use?

Stiils from 180 mbps video of that gig

I was onsite for NoFilmSchool and actually talked to the SoundDevices guy about this specifically!  I asked him whether he felt threatened by the development of a sub1k 4k monitor-recorder, since they have the Pix-E series, which I own.  He says no, because he was wondering about the feasability of Prores 4K being recorded to SD cards reliably.  Also, the PIX-E is fully kitted out with scopes et al and is super rugged.

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