Pavel D Prichystal

(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?

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?

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?

That is handheld + stabilized lens + DIS or no DIS?
I have to say, before my biggest concern with NX1 was CTUs(bigger chunks of macroblocks) and motion cadency, which was choppy and somewhat.. Disturbing. Couldnt quite find out the cause in order to solve it. The 200mbps increase seems to solved both of these major issues. And quite well I have to say!! I have a 6 hour commercial shooting today so will post my findings with functionality of latest hack

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!

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!

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!

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!

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

You got my attention now!! :D
Could you (or anyone) upload a short example of this onto vimeo/youtube?

Yes, I have noticed that too (especially in 4k), but I thought it is just my opinion. Anyone complained "motion cadence problem" in NX1? I think it is gone now!

Reported.

Dude, Tommix. Could you maybe not?
How about no to you acting like bully to all of us? Just stop. Either start contributing and stop being a dick to us, or just watch what is happening or lets ask Andrew to get you banned? 


PS: This is not an invitation for you to flame spam this topic so be that kind to us, fellow cinematographers, and get better, friendlier.

Reported.

Reported.

Dude, Tommix. Could you maybe not?
How about no to you acting like bully to all of us? Just stop. Either start contributing and stop being a dick to us, or just watch what is happening or lets ask Andrew to get you banned? 


PS: This is not an invitation for you to flame spam this topic so be that kind to us, fellow cinematographers, and get better, friendlier.

Reported.

Dude, Tommix. Could you maybe not?
How about no to you acting like bully to all of us? Just stop. Either start contributing and stop being a dick to us, or just watch what is happening or lets ask Andrew to get you banned? 


PS: This is not an invitation for you to flame spam this topic so be that kind to us, fellow cinematographers, and get better, friendlier.

Reported.

Reported.

Dude, Tommix. Could you maybe not?
How about no to you acting like bully to all of us? Just stop. Either start contributing and stop being a dick to us, or just watch what is happening or lets ask Andrew to get you banned? 


PS: This is not an invitation for you to flame spam this topic so be that kind to us, fellow cinematographers, and get better, friendlier.

Reported.

Reported.

Reported.