lucabutera

@RieGo, @tugela - I never said that NX1 can shoot UHD@120. What I sad is that camera can produce a file which is 3840x2160p and 120 fps

And I said that file is x4 speed timelapse with dublicated frames. Do you read?
And here you send me link on my own thread on DPR

Well, okay than. Do your thing.
It's already hacked like 4 month ago, just not implemented in hack with any key-combo. In telnet you can set up MF mode just like this:
st cap capdtm setusr AFMODE 0x70003
That's all, camera now in MF mode, but there is no indication of that, but if you know - you can use it. Tried this just now with NX1 and 16-50S in AF mode, works like a charm, MF ring is focusing, which doesn't happens with this lense in hardware-switch AF mode. MF assist also works okay.

If anyone need this in hack - you just can use keyscan and bind one of the camera buttons with EV+ combo for that.

I think the issue he was describing, or at least the one I'm thinking of is that everytime you enter video standby it defaults to continous autofocus :/ then you have to push the af back button everytime and/or choose saf. Just gets annoying.

Someone know if with hacks it possible to set manual focus in video mode, without setting it every times?

Someone know if with hacks it possible to set manual focus in video mode, without setting it every times?

We should make a first post summary cause I'm so confused... I lost track who is who and what are the difference between hacks.

As someone who has yet to install the hacks...it would be nice for Andrew to install them and spotlight these developments with a proper article.  You can find tons of information / reviews of the ML hacks for Cannon...all of this for the NX1 is found on two forums.  
Since I also purchased Andrew's NX1 guide, I think that should be updated with at least a summary of the possibilities that are now possible and how that can lead to a better image.

I guess some clarifications are in order.
NX-KS works with the new fw versions (1.12 / 1.41) for both cameras, and sets the bitrates as before, with one addition of 400Mbps for time-lapses.
@MountneerMan, vasile was never really part of NX-KS, from the very start I did uses his mod, but very soon after Otto made "poker" I started using that, which allowed for faster loading, and higher stable bitrates. Vasile, even tough apparently he obfuscated the bitrates and had to be "hacked" to be used with "poker" was given full credit.

Lets say that "falling out" is put mildly as there was never a "functioning team", often resulting him demanding of proof for this or that, like when I posted a very high-bit video, he demanded that I show him jump-table for a hack or give him credit for the video that I made, as "apparently I modified the bitrates using his spreadsheet" ... and so forth. Lets say the constant slander was almost a harassment.

When the new FW showed up, I gave him the new addresses, but the values were suspect, and after waiting a week for him to produce the new bitrates (as I suspected were different) he just said "they are the same" while apparently he's been working on his "mod". Well something didn't add up as the values from Samsung did not match Vasiles.
So I redid his hack, and found he had miscalculated the values 4 bits out of 8 bytes, (which was not critical in the end, but gave different values) maybe it was not from his calculations, but error from his obfuscation - no idea, didn't really care to check his work that much.

I can't speak of his new "mod", as I have not checked it, and don't intend to.
But since he didn't contribute anything for the latest NX-KS mod, and only made sure his work can't be really used as opensource, was enough to let him go and do his own thing, although teaming with Otto was great.

That about sums it up. : )

But of course I had to say Otto has my full respect!
He is the one that made it all possible.

Great - thanks kidzrevil! Will try it out!

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

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
 

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

Hi, please check second line of this. Kind regards.

(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

http://***URL removed***/forums/post/57685081

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!

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.

Congrats for all the effort guys (Chant, Vasile, Otto...).

I'm very excited to see all things you are implementing on this cameras.
Now with the new Blackmagic View Assist 4K i was wondering if (even on our more remote dreams) would be possible to get a RAW image via HDMI.
I have no knowledge in this area and i apologize if it's a stupid question. Take care and keep up the good work!


 

eoshd is the "other" board mentioned here :-)
http://***URL removed***/forums/post/57589144

120 fps works fine with 110Mbit as max bitrate. 100fps should be completely fine even with 160Mbits...

Since 120fps doesn't play nice with the bitrate hack has anyone tried PAL 100fps?  I feel like that should work without issue since the hack brings the 120fps recordings down to 106fps.

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.

Battery pull means no battery whatsoever, the camera should have no power source. Turning off is not enough. If you have two batteries you need to pull both.
Will add this clarification to the next mod version.

Honestly i make too the test but i didn't notice any update in my camera..for my side is always the same i never have problem macroblocking in my nx1 so i didn't notice difference
for flat profile here there is a test and explanation how i do