RieGo

...and I can see that we have to wait until beginning of April (Vasile will come back on 6th April). 3 weeks... 

I think vasile's idea of using the existing menu and then just overriding the bitrate values that Samsung has assigned to the options is probably the best option because it is the most integrated. Another potential option could be to add a menu option to pull up the keyboard and ask for a custom setting of resolution, frame rate, bitrate (and maybe anything else necessary like video profile).
We should try to avoid out of place, unintegrated UI if possible. It just adds clutter. 
 
@vasile can you explain what tbn and tbc are?
 
Also, can you check if there is a flag or something in the Dev menu that lets Samsung know if the video time limit has ever been disabled? (Assuming of course that you can uncheck the box in the menu).

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.

So this sounds like lossy RAW on NX1 might be possible.
does anyone have an idea on how to easily toggle this lossy raw setting, if it's possible at all?

How To - recording limit - NX500 and NX1

YOUR WARRANTY IS NOW VOID.

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

YOUR WARRANTY IS NOW VOID.
YOUR WARRANTY IS NOW VOID.
YOUR WARRANTY IS NOW VOID.
YOUR WARRANTY IS NOW VOID.
YOUR WARRANTY IS NOW VOID.

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.

Here is a quick video showing the NX1 and NX500 SD Card Hack for Focus Buttons.
This program allows you to record up to 6 focal points, these are stored on the SD card and will work after a camera restart.
This works for photography, especially good for storing infinity focal point to re-use when it is dark for Astro Photography.
Works in video allows you to do focus pulling from one focal point to another.
Thanks again to Otto for all the hard work, All details can be found on https://github.com/ottokiksmaler/nx500
 

The code excerpts I posted are from the firmware. The statement about the camera being able to do 240fps is something they didnt remove. Also found a bunch of tizen watch stuff. Bad housekeeping is good news.

But I have yet to find a video output path that is concise. Tons of data on the hevc and everything else, but its what pointed me to the srp and needing to do more research. There way a camera would dump data to an onboard hevc is pretty well documented. Follow the mipi csi-2 bridge a few steps to get to the encoder. but the difference is, if it was indeed just a "hard" core hevc in the drime-v it would be more self contained. Taking what I know of chip construction and "hard" core asic  implementation. The more I do the more I find on how it works and what can be done.