Jump to content


  • Posts

  • Joined

  • Last visited

Posts posted by RieGo

  1. 7 hours ago, vasile said:


    NB. This is a very very short explanation of my thought process how I went from zero ARM assembly knowledge to encoding these instructions, by using the ARM reference manual.

    I hope this post will clear any lingering doubts about the correctness of my calculations.

    thanks a lot for the detailed explanation. i really enjoyed reading through it!


    3 hours ago, outerbeat said:

    Well, as I said on dpr, codec can do even 4K @ 120 fps, here it summary of files that I record, camera was able to create a file with this properties:

    Width : 3 840 pixels
    Height : 2 160 pixels
    Frame rate mode : Constant
    Frame rate : 119.880 fps

    So, UHD @ 120 file is exists and it's smooth. With dublicates though (every 11th = every 10th frame). And it's x4 speed timelapse. But in principle it is possible.

    I guess you have to rethink this. the camera doesn't actually encode 120 frames per second. it encodes 30 frames (my tests showed it's probably 25 frames) in one second of realtime. once it finished (or more probably also while) recording it tells the container that this, say 1000 frames, should be played back at 120f/s. which makes it basically really fast -> timelapse. camera didn't have to do any more work than in 30p.

    btw take a look at http://***URL removed***/forums/post/57866447 for framerate/resolution/slot tests and sample files

  2. 15 minutes ago, tugela said:

    The trouble is that many equate resolution with oversharpened, because they are looking for soft footage.

    true. also many people are watching it on 1080p monitors, which obviously downsamples as well....

  3. regarding the sharpness: i'm starting to believe -10 = no post sharpening, like someone else suggested. i did some tests with many details and sharpening -10. i couldn't find any interpolated edge sharpening, which is usually visible by ringing artifacts. my consumption: the oversharpening some are seeing is a result of a downsampler, probably bicubic ... is there a way to change this? i don't know.

  4. so there is a little misconception: the higher the bitrate/quality the encoder has to output the more work he has to do. so it's usual (at least in my experience) for encoders to get slower while bitrate increases. you can try a simple x264 crf 18 vs x264 crf 30 to see what i'm talking about.

    also don't forget: a major quality decrease at 120p compared to 30p/60p comes from no full sensor readout, which also makes it harder to compress because of more noise.

  5. i manually worked through all values by inputting them and looking at the camera icon. don't know if there's an easier way...

    btw: ignore the "seems like 9 sets it to fhd24" was a misconception :grin: 9 is just undefined like any other value >14

  6. 16 minutes ago, SMGJohn said:

    Also NX1 HEVC codec is Level 5.1 which only allows for max 160mbps so any higher would be pointless as its not presented in the camera


    On 6.4.2016 at 7:09 PM, tugela said:

    It is just a specification. There is no reason why the software can't go higher, just if it does it will generate an out of spec file.

    This is still true. the final file HAS 180MBit/s so they ARE used. This is no fill up data or anything like this.... well i can't proof that, but i'm pretty sure there is no such thing as filling data in mp4 containers... only television packets use filling data because they have to use a defined constant data rate.

    sorry, that was a lot of "filling data" but "filling data" is the only way i know to make bits disappear :grin: 

  7. 27 minutes ago, vasile said:

    resolution [show, name] means you can use resolution show or resolution name.

    Presumably resolution show would list available names to be used as "name" parameter for resolution "name"

    alright, my bad. anyways "resolution show" doesn't give any output on terminal. maybe it's just in log or something...

    i'm just running the video tests. just looks like a bunch of small videos in different resolutions...

    btw: at "basic" and "full" test my battery turned from 50% to 0% in like 5 minutes until camera turned off... maybe that's part of the test or my battery is broken :grin:

  8. just tried "st app nx record start" and "st app nx record stop". works just as expected, starts and stops video recording. but i have no clue how to use the resolution parameter... i tried but couldn't get to change anything.
    is this even what you are thinking about? i have no clue :grin:

    resolution [show,name] -> this arguments seem like only predefined resolutions can be used

  9. 2 hours ago, ricardo_sousa11 said:

    But is there any risk just disabeling that ? I just want that, not the recording limit, because I currently have a piece of paper on the lens button, so I can use my nikon glass..

    it SHOULD not make any problems. it's disabled on mine since that hack came up. but please make sure to follow the manual closely. you don't need to disable recording limit for this.

  10. averaging two frames should be completely equal to doubling the shutter time. i think we can agree on that :grin:

    if you're into avisynth: qtgmc contains a part where it can simulate motion blur, i.e. when you discard one field on interlaced source, making it half shutter angle. OR when you set your shutter speed too high, cause this is something that's not as easy. but that's a very exceptional case...

  11. 20 minutes ago, 瞿盛龙 said:

    Video, I hope the shutter speed can be set, perhaps a hacker can break this limit?

    that's how video recording works. you cannot open the shutter longer than the duration of a frame. only very expensive cams can do this afaik. also you would get a lot of blur.
    i highly doubt this will be possible on this camera with a hack.

    well, if someone manages to make fps freely adjustable you could set it to 10fps and you'd get your 1/10 :-)

  12. omg i never realised you get so much ugly sharpening, even though you did sharpness -10. seems like video postprocessing messes things really up.
    so let's assume we get mjpeg codec - wouldn't it go through the same video processing? i think so. we definitely need a way to go around this horrible sharpening... :confused:

    OR it really is a sideeffect of hevc... i'm not sure.

    well, ungraded looks way better (still too much) in terms of sharpness. did you do any post sharpening?

  13. 15 minutes ago, ricardo_sousa11 said:

    Is there any tutorial and download link for the hack ? I want to stop getting the lens detached error, to use my cheap Nikon adapters, but cant find the DL link and how to install it..

    just follow this instructions: https://github.com/ottokiksmaler/nx500_nx1_modding/blob/master/DEV%20and%20CS%20modes.md

    But instead of disabling recording limit just use this setting:



    please be careful, the dev menu is dangerous!

  14. 4 hours ago, SMGJohn said:

    Are you on a Mac or Windows?

    Adobe for Windows is bloody atrocious as much as I dislike Mac it simply just works better with the Adobe programs because of the Unix code. If Adobe stopped being fools and just made their programs for Linux then I would switch in a heart beat imao, sadly I do not have HEVC hardware encoding, refuse to switch to nVidia just for that though I will place my bet on Polaris from AMD.

    There where some issues with it stopping rendering completely so I had to spit out JPEG's and even then he corrupted a lot of frames which I had to painstakingly replace manually. But like you said it could be lack of hardware support but then again I do not have any issues with any other codec its only HEVC.

    i'm on windows.
    i see your point. new tech definitely needs some time to get widely adopted... let's just hope in a few years it will be as compatible as h264. in the meantime the only option is to convert the files before working with them, or hopefully someone can get some different encoding working on this firmware.
    only time will tell :)

  15. I'm using an up-to-date Premiere Pro and nowadays it's no problem at all to work with hevc. the only thing premiere has difficulties with is reading the color range 0-255 from the NX1.
    if you got performance problems you probably just need hevc hardware decoding (intel skylake or nvidia 960 or 970 i think)

  16. 2 minutes ago, Otto K said:

     Actually, the user interface itself is stored in .edj files (like nx_style.edj) and can be extracted with edje_decc tool (but nx_style contains config.h file that lies outside of the allowed root directory so the decompiler exits). UI is a mix of images (icons, backgrounds, etc) and .edc files that are textual and describe the actual layout of the UI as well as the logic contained within (can contain even lua programs). Di-camera-app services signals from edje ui. 

    that's interesting! i didn't take a look at the edj files yet. i was just about to decompile the binary.

    i see there is still a lot to explore...

  • Create New...