Chant

Awesome, do you have a stream parser so you can compare the two bitrates?  zond 265 worked for me. They have trials as most are very costly. Do a sample with the before and after frame rate and then see what the analyzer says. This is a step for sure!

That is hard to say, might be able to load something like magic lantern, but the way the camera uses the .cpp files firmware wise make it limiting in what can be done. ML uses a modded firmware with a boot flag to enable what they use. But can be added to the list of things to look into. There will probley be a few variations of firmware, I found a log file of what they did to test and try to break the firmware so imitating it could be helpful.

 
With luck  that will be possible! The di-camera-app is interesting. I found the package info for it last night as well. 

 
Flat or log or cine gamma. All similar but not if you know what I mean. My want is for something to be similar to red.

It seems that way, or at least going down the bit stream things are implemented. There is so so so so many cpp files as you have probley seen. But thats part of the task haha! The hevc stream is interesting if you feed it into a parser. the compression is very dynamic. But pumping it up to the max of the sd bus speed could garner results. The gop of the file I tested was 15frames(500ms) So there is some possible quality improvements from there.

Some interesting tidbits found tonight. 

"setpath    0 - 2(0:OTF/1:IPCout/2:RawOut/3:Ldc Out/4:120FPS OTF/5:120FPS IPC out
        6:120FPS Raw Out/7:120FPS Ldc Out/8:panorama/9:MFZoom)"
"sensorframerate    12,15,20,24,25,30,40,50,60,100,120,240
        outputframerate    12,15,20,24,25,30,40,50,60,100,120,240
dataframerate      12,15,20,24,25,30,40,50,60,100,120,240"

Still looking for the encoder though. To confirm srp or other hardware. But the closer it gets. And then the real fun happens!
I can look into the nx500 firmware deeper after I do the nx1 and see what can be added or changed. I do have a want for a nx500 b cam, especially as a gopro stand in due to them being cheaper! Make everyone want this samsung gear now that they cant get them. Maybe it was samsungs plan all along.
Edit
"HEVC Encoder
%s:%s(%d)> Width(%d) or height(%d) is not multiple of 8
%s:%s(%d)> HEVC[%d] Cfg WH %dx%d %d, BR:%dkbps GOP:%d > size 0x%x > return %d"
the full sensor read out should be possible with this also notice gop setting and bit rate.
 
I will have to look at the encoder.cpp file which is where things get more complicated but this is very good news.

It seems that way, or at least going down the bit stream things are implemented. There is so so so so many cpp files as you have probley seen. But thats part of the task haha! The hevc stream is interesting if you feed it into a parser. the compression is very dynamic. But pumping it up to the max of the sd bus speed could garner results. The gop of the file I tested was 15frames(500ms) So there is some possible quality improvements from there.

I have a few githubs for other projects and its a good idea. it would be more of a blog, the amount of data I have examined would be too much to try to make sense of, as I said, I was working on this for my own personal goals a few months before I even found this thread.
Ill see if I can create something tangible in the next few days github wise and Ill post up. Alas text cant convey how excited I am as I go through all this info. I had a want for it to be a good system and it has surpassed my expectations. Great things can be done with it. 

Some interesting tidbits found tonight. 

"setpath    0 - 2(0:OTF/1:IPCout/2:RawOut/3:Ldc Out/4:120FPS OTF/5:120FPS IPC out
        6:120FPS Raw Out/7:120FPS Ldc Out/8:panorama/9:MFZoom)"
"sensorframerate    12,15,20,24,25,30,40,50,60,100,120,240
        outputframerate    12,15,20,24,25,30,40,50,60,100,120,240
dataframerate      12,15,20,24,25,30,40,50,60,100,120,240"

Still looking for the encoder though. To confirm srp or other hardware. But the closer it gets. And then the real fun happens!
I can look into the nx500 firmware deeper after I do the nx1 and see what can be added or changed. I do have a want for a nx500 b cam, especially as a gopro stand in due to them being cheaper! Make everyone want this samsung gear now that they cant get them. Maybe it was samsungs plan all along.
Edit
"HEVC Encoder
%s:%s(%d)> Width(%d) or height(%d) is not multiple of 8
%s:%s(%d)> HEVC[%d] Cfg WH %dx%d %d, BR:%dkbps GOP:%d > size 0x%x > return %d"
the full sensor read out should be possible with this also notice gop setting and bit rate.
 
I will have to look at the encoder.cpp file which is where things get more complicated but this is very good news.

I have a few githubs for other projects and its a good idea. it would be more of a blog, the amount of data I have examined would be too much to try to make sense of, as I said, I was working on this for my own personal goals a few months before I even found this thread.
Ill see if I can create something tangible in the next few days github wise and Ill post up. Alas text cant convey how excited I am as I go through all this info. I had a want for it to be a good system and it has surpassed my expectations. Great things can be done with it. 

Some interesting tidbits found tonight. 

"setpath    0 - 2(0:OTF/1:IPCout/2:RawOut/3:Ldc Out/4:120FPS OTF/5:120FPS IPC out
        6:120FPS Raw Out/7:120FPS Ldc Out/8:panorama/9:MFZoom)"
"sensorframerate    12,15,20,24,25,30,40,50,60,100,120,240
        outputframerate    12,15,20,24,25,30,40,50,60,100,120,240
dataframerate      12,15,20,24,25,30,40,50,60,100,120,240"

Still looking for the encoder though. To confirm srp or other hardware. But the closer it gets. And then the real fun happens!
I can look into the nx500 firmware deeper after I do the nx1 and see what can be added or changed. I do have a want for a nx500 b cam, especially as a gopro stand in due to them being cheaper! Make everyone want this samsung gear now that they cant get them. Maybe it was samsungs plan all along.
Edit
"HEVC Encoder
%s:%s(%d)> Width(%d) or height(%d) is not multiple of 8
%s:%s(%d)> HEVC[%d] Cfg WH %dx%d %d, BR:%dkbps GOP:%d > size 0x%x > return %d"
the full sensor read out should be possible with this also notice gop setting and bit rate.
 
I will have to look at the encoder.cpp file which is where things get more complicated but this is very good news.

It seems that way, or at least going down the bit stream things are implemented. There is so so so so many cpp files as you have probley seen. But thats part of the task haha! The hevc stream is interesting if you feed it into a parser. the compression is very dynamic. But pumping it up to the max of the sd bus speed could garner results. The gop of the file I tested was 15frames(500ms) So there is some possible quality improvements from there.

Some interesting tidbits found tonight. 

"setpath    0 - 2(0:OTF/1:IPCout/2:RawOut/3:Ldc Out/4:120FPS OTF/5:120FPS IPC out
        6:120FPS Raw Out/7:120FPS Ldc Out/8:panorama/9:MFZoom)"
"sensorframerate    12,15,20,24,25,30,40,50,60,100,120,240
        outputframerate    12,15,20,24,25,30,40,50,60,100,120,240
dataframerate      12,15,20,24,25,30,40,50,60,100,120,240"

Still looking for the encoder though. To confirm srp or other hardware. But the closer it gets. And then the real fun happens!
I can look into the nx500 firmware deeper after I do the nx1 and see what can be added or changed. I do have a want for a nx500 b cam, especially as a gopro stand in due to them being cheaper! Make everyone want this samsung gear now that they cant get them. Maybe it was samsungs plan all along.
Edit
"HEVC Encoder
%s:%s(%d)> Width(%d) or height(%d) is not multiple of 8
%s:%s(%d)> HEVC[%d] Cfg WH %dx%d %d, BR:%dkbps GOP:%d > size 0x%x > return %d"
the full sensor read out should be possible with this also notice gop setting and bit rate.
 
I will have to look at the encoder.cpp file which is where things get more complicated but this is very good news.

Some interesting tidbits found tonight. 

"setpath    0 - 2(0:OTF/1:IPCout/2:RawOut/3:Ldc Out/4:120FPS OTF/5:120FPS IPC out
        6:120FPS Raw Out/7:120FPS Ldc Out/8:panorama/9:MFZoom)"
"sensorframerate    12,15,20,24,25,30,40,50,60,100,120,240
        outputframerate    12,15,20,24,25,30,40,50,60,100,120,240
dataframerate      12,15,20,24,25,30,40,50,60,100,120,240"

Still looking for the encoder though. To confirm srp or other hardware. But the closer it gets. And then the real fun happens!
I can look into the nx500 firmware deeper after I do the nx1 and see what can be added or changed. I do have a want for a nx500 b cam, especially as a gopro stand in due to them being cheaper! Make everyone want this samsung gear now that they cant get them. Maybe it was samsungs plan all along.
Edit
"HEVC Encoder
%s:%s(%d)> Width(%d) or height(%d) is not multiple of 8
%s:%s(%d)> HEVC[%d] Cfg WH %dx%d %d, BR:%dkbps GOP:%d > size 0x%x > return %d"
the full sensor read out should be possible with this also notice gop setting and bit rate.
 
I will have to look at the encoder.cpp file which is where things get more complicated but this is very good news.

I have a few githubs for other projects and its a good idea. it would be more of a blog, the amount of data I have examined would be too much to try to make sense of, as I said, I was working on this for my own personal goals a few months before I even found this thread.
Ill see if I can create something tangible in the next few days github wise and Ill post up. Alas text cant convey how excited I am as I go through all this info. I had a want for it to be a good system and it has surpassed my expectations. Great things can be done with it. 

Some interesting tidbits found tonight. 

"setpath    0 - 2(0:OTF/1:IPCout/2:RawOut/3:Ldc Out/4:120FPS OTF/5:120FPS IPC out
        6:120FPS Raw Out/7:120FPS Ldc Out/8:panorama/9:MFZoom)"
"sensorframerate    12,15,20,24,25,30,40,50,60,100,120,240
        outputframerate    12,15,20,24,25,30,40,50,60,100,120,240
dataframerate      12,15,20,24,25,30,40,50,60,100,120,240"

Still looking for the encoder though. To confirm srp or other hardware. But the closer it gets. And then the real fun happens!
I can look into the nx500 firmware deeper after I do the nx1 and see what can be added or changed. I do have a want for a nx500 b cam, especially as a gopro stand in due to them being cheaper! Make everyone want this samsung gear now that they cant get them. Maybe it was samsungs plan all along.
Edit
"HEVC Encoder
%s:%s(%d)> Width(%d) or height(%d) is not multiple of 8
%s:%s(%d)> HEVC[%d] Cfg WH %dx%d %d, BR:%dkbps GOP:%d > size 0x%x > return %d"
the full sensor read out should be possible with this also notice gop setting and bit rate.
 
I will have to look at the encoder.cpp file which is where things get more complicated but this is very good news.

Some interesting tidbits found tonight. 

"setpath    0 - 2(0:OTF/1:IPCout/2:RawOut/3:Ldc Out/4:120FPS OTF/5:120FPS IPC out
        6:120FPS Raw Out/7:120FPS Ldc Out/8:panorama/9:MFZoom)"
"sensorframerate    12,15,20,24,25,30,40,50,60,100,120,240
        outputframerate    12,15,20,24,25,30,40,50,60,100,120,240
dataframerate      12,15,20,24,25,30,40,50,60,100,120,240"

Still looking for the encoder though. To confirm srp or other hardware. But the closer it gets. And then the real fun happens!
I can look into the nx500 firmware deeper after I do the nx1 and see what can be added or changed. I do have a want for a nx500 b cam, especially as a gopro stand in due to them being cheaper! Make everyone want this samsung gear now that they cant get them. Maybe it was samsungs plan all along.
Edit
"HEVC Encoder
%s:%s(%d)> Width(%d) or height(%d) is not multiple of 8
%s:%s(%d)> HEVC[%d] Cfg WH %dx%d %d, BR:%dkbps GOP:%d > size 0x%x > return %d"
the full sensor read out should be possible with this also notice gop setting and bit rate.
 
I will have to look at the encoder.cpp file which is where things get more complicated but this is very good news.

Some interesting tidbits found tonight. 

"setpath    0 - 2(0:OTF/1:IPCout/2:RawOut/3:Ldc Out/4:120FPS OTF/5:120FPS IPC out
        6:120FPS Raw Out/7:120FPS Ldc Out/8:panorama/9:MFZoom)"
"sensorframerate    12,15,20,24,25,30,40,50,60,100,120,240
        outputframerate    12,15,20,24,25,30,40,50,60,100,120,240
dataframerate      12,15,20,24,25,30,40,50,60,100,120,240"

Still looking for the encoder though. To confirm srp or other hardware. But the closer it gets. And then the real fun happens!
I can look into the nx500 firmware deeper after I do the nx1 and see what can be added or changed. I do have a want for a nx500 b cam, especially as a gopro stand in due to them being cheaper! Make everyone want this samsung gear now that they cant get them. Maybe it was samsungs plan all along.
Edit
"HEVC Encoder
%s:%s(%d)> Width(%d) or height(%d) is not multiple of 8
%s:%s(%d)> HEVC[%d] Cfg WH %dx%d %d, BR:%dkbps GOP:%d > size 0x%x > return %d"
the full sensor read out should be possible with this also notice gop setting and bit rate.
 
I will have to look at the encoder.cpp file which is where things get more complicated but this is very good news.

Some interesting tidbits found tonight. 

"setpath    0 - 2(0:OTF/1:IPCout/2:RawOut/3:Ldc Out/4:120FPS OTF/5:120FPS IPC out
        6:120FPS Raw Out/7:120FPS Ldc Out/8:panorama/9:MFZoom)"
"sensorframerate    12,15,20,24,25,30,40,50,60,100,120,240
        outputframerate    12,15,20,24,25,30,40,50,60,100,120,240
dataframerate      12,15,20,24,25,30,40,50,60,100,120,240"

Still looking for the encoder though. To confirm srp or other hardware. But the closer it gets. And then the real fun happens!
I can look into the nx500 firmware deeper after I do the nx1 and see what can be added or changed. I do have a want for a nx500 b cam, especially as a gopro stand in due to them being cheaper! Make everyone want this samsung gear now that they cant get them. Maybe it was samsungs plan all along.
Edit
"HEVC Encoder
%s:%s(%d)> Width(%d) or height(%d) is not multiple of 8
%s:%s(%d)> HEVC[%d] Cfg WH %dx%d %d, BR:%dkbps GOP:%d > size 0x%x > return %d"
the full sensor read out should be possible with this also notice gop setting and bit rate.
 
I will have to look at the encoder.cpp file which is where things get more complicated but this is very good news.

It might be better to split into two topics, nx500 and nx1. Or front end and back end. The things Otto is doing to the nx500 are amazing, but less similar to what I am doing with going into the firmware. It may be better to have things split up so updates dont get lost in the posts. My work has less shareability and its not something someone would want to play with unless they want a nice nx1 sized brick. I will be doing a comparison on the nx500-nx1 firmware to see if things can be added or removed by just copying the .cpp files.
But if you compare the fcc internal photos https://fccid.io/document.php?id=2507770 nx500 and https://fccid.io/document.php?id=2394073 nx1 you can see the change in size of the drime-v and drime-vs. There is also the unreleased nxmini2 which had the drime-vs in it also https://fccid.io/document.php?id=2594973 nxf2

From my end the later updates of the firmware do have a lot of changes, obviously due to file size less changes, but the specific documentation is there. But things are still progressing on my end.

Some interesting tidbits found tonight. 

"setpath    0 - 2(0:OTF/1:IPCout/2:RawOut/3:Ldc Out/4:120FPS OTF/5:120FPS IPC out
        6:120FPS Raw Out/7:120FPS Ldc Out/8:panorama/9:MFZoom)"
"sensorframerate    12,15,20,24,25,30,40,50,60,100,120,240
        outputframerate    12,15,20,24,25,30,40,50,60,100,120,240
dataframerate      12,15,20,24,25,30,40,50,60,100,120,240"

Still looking for the encoder though. To confirm srp or other hardware. But the closer it gets. And then the real fun happens!
I can look into the nx500 firmware deeper after I do the nx1 and see what can be added or changed. I do have a want for a nx500 b cam, especially as a gopro stand in due to them being cheaper! Make everyone want this samsung gear now that they cant get them. Maybe it was samsungs plan all along.
Edit
"HEVC Encoder
%s:%s(%d)> Width(%d) or height(%d) is not multiple of 8
%s:%s(%d)> HEVC[%d] Cfg WH %dx%d %d, BR:%dkbps GOP:%d > size 0x%x > return %d"
the full sensor read out should be possible with this also notice gop setting and bit rate.
 
I will have to look at the encoder.cpp file which is where things get more complicated but this is very good news.

I have a few githubs for other projects and its a good idea. it would be more of a blog, the amount of data I have examined would be too much to try to make sense of, as I said, I was working on this for my own personal goals a few months before I even found this thread.
Ill see if I can create something tangible in the next few days github wise and Ill post up. Alas text cant convey how excited I am as I go through all this info. I had a want for it to be a good system and it has surpassed my expectations. Great things can be done with it. 

It might be better to split into two topics, nx500 and nx1. Or front end and back end. The things Otto is doing to the nx500 are amazing, but less similar to what I am doing with going into the firmware. It may be better to have things split up so updates dont get lost in the posts. My work has less shareability and its not something someone would want to play with unless they want a nice nx1 sized brick. I will be doing a comparison on the nx500-nx1 firmware to see if things can be added or removed by just copying the .cpp files.
But if you compare the fcc internal photos https://fccid.io/document.php?id=2507770 nx500 and https://fccid.io/document.php?id=2394073 nx1 you can see the change in size of the drime-v and drime-vs. There is also the unreleased nxmini2 which had the drime-vs in it also https://fccid.io/document.php?id=2594973 nxf2

From my end the later updates of the firmware do have a lot of changes, obviously due to file size less changes, but the specific documentation is there. But things are still progressing on my end.

I have a few githubs for other projects and its a good idea. it would be more of a blog, the amount of data I have examined would be too much to try to make sense of, as I said, I was working on this for my own personal goals a few months before I even found this thread.
Ill see if I can create something tangible in the next few days github wise and Ill post up. Alas text cant convey how excited I am as I go through all this info. I had a want for it to be a good system and it has surpassed my expectations. Great things can be done with it. 

Unfortunately that's not how it works. The framerate is inversely proportional to the number of lines, not the number of pixels. Getting much more than 120fps in 1080p would require an entirely new image sensor. The reason is that all modern cameras (apart from some exotic high-end stuff) use "column parallel" sensors.
The best affordable high-speed camera at the moment is probably the crowd-funded fps1000, if it's actually shipping yet.
Please quit saying that without any evidence. The processor does not limit the readout speed of each individual frame. The RAM in the NX1 is fast enough to store the data to be processed in way under 1/30 of a second (you can see the clock speeds for the RAM in the kernel source). It can do that in its sleep. Literally. According to the source code, the RAM is running at 400Mhz in sleep mode. There is no way it is de-bayering, scaling, and encoding the video line by line without putting it in a framebuffer first. Yes I know a Samsung representative said the sensor was really fast in an interview, but the official Samsung website says otherwise. Furthermore every third-party test indicates otherwise. The proportionality between rolling shutter and lines of resolution in all real world tests agrees with my estimates. The information in the firmware release notes is consistent with those limitations. Every other camera ever made works like that.
The only way the processor could determine the rolling shutter is if they forced the LVDS receivers on the main SoC to run at a fraction of the rate they could be run at. That would be spectacularly stupid, since there are much easier ways to cripple a camera. Even if they knew about the details of the camera's operation, I doubt Samsung executives would choose to limit the camera in such a dumb, arbitrary way.
Unless you actually have evidence, stop spreading misinformation. It's a waste of time to keep explaining this over and over.

Im finding references of sensor read out in the fimware. But without full data Im not sure if things can be changed. If this sensor is similar to the S5KVB2 or a different roll out. Having the data sheet would shed some light. The cmosis cmv12000 and cmv20000 are both global and rolling and its implemented in code which readout it does. Unfortunately the S5KVB2 data sheet is not something that is attainable and if it was Im sure it would be under nda. But Its all things to test once I have it all sorted. My notes are filling up pages.

Sent you a message regarding this