Jump to content

SMGJohn

Members
  • Posts

    365
  • Joined

  • Last visited

Reputation Activity

  1. Like
    SMGJohn reacted to Pavel MaÅ¡ek in Petition for Samsung NX1 hack   
    I have just ordered this 2000x Lexar card (64GB) - I hope  there will be some benefit over Extereme PRO 95MB/s ( maybe in even higher bitrates thanks to Vasile's hack). BTW I think quite good deal for EU based users
  2. Like
    SMGJohn reacted to Chant in Petition for Samsung NX1 hack   
    The camera is limited by the bus speed of UHS-2 which is 312MB/s 2496Mb/s Fastest card is currently the sandisk extreme pro at 250MB/s 2000Mb/s So there is much more to go until we reach that. Should be enough for what I am looking into. And remember, higher bit rate, lower compression, less math the processor needs to do, so less work and less heat. Theoretically the limit is high, and if you look at the dp review of the canon 80d and the nx1 their new low noise tech is still miles away.
  3. Like
    SMGJohn got a reaction from vaga in Petition for Samsung NX1 hack   
    JPEG's will have superior grading capability than HEVC, to match a Super Fine JPEG to HEVC the bitrate has to be so insane that grading that HEVC video is going to be a nightmare if you do not own a 50k dollar workstation, not to mention the HEVC codec in Premiere CC2015 is causing me more trouble and performance issue than I want to deal with, I rather spare a few GB of space and continue converting them to ProResLT.
    I rarely noticed banding issue with JPEG's in the NX1 either, some rare cases but that would just be the terrible JPEG compression algorithm that Samsung uses.
    If you want I can shoot a 15fps 6k in 16 by 9, 1 - 2 second video and you can have fun in whichever video editing software you use, from personal experience the JPEG's out of the camera have pretty damn good data in it, allowing me to pull some pretty amazing details out of dark areas and compress highlights, its no raw but its WAAAAY better than HEVC could probably ever do if you ask me.
  4. Like
    SMGJohn reacted to lucabutera in Petition for Samsung NX1 hack   
    25fps in jpeg, 4608x2592, aspect ratio 16:9, picture quality "super fine", has a bit rate of about 100MB/s.
    25fps in jpeg, 6480x3640, aspect ratio 16:9, picture quality "super fine", has a bit rate of about 170MB/s.
    The Vasile hack has demonstrated that the Samsung nx1 is able to shoot video over 150MB / s so we are not very far from a new Magic Lantern for Samsung Nx1.

  5. Like
    SMGJohn got a reaction from Hanriverprod in Petition for Samsung NX1 hack   
    I have found a massive issue regarding record limit on the HEVC, it appears to be more the fault of HEVC screwing around with us rather than the camera or file structure issues.
    I tested the MJPEG codec this time around with a 64GB card and the camera plugged into the wall with no battery power to do a record session. Lets just say, just not did it pass the 75 - 78 minute limit the HEVC exhibits.
    It clocked around ~620 minutes before running out of space on the 64GB card and froze, I am pretty sure it would last even longer if I had used the 128GB one.

     
     
     
     
     
     
     
     
     
     
     
    Now again this is a low bitrate, low resolution video mode that works the sensor less, so I did the test again but this time with 480p HEVC at 25fps, and once more it crashes at 75 - 78 minute mark, its hard to tell the exact mark because its random most of the time. 
    I tried both HQ and Normal bitrate but it still crashes above 75~min. files for HQ are no more than over 2GB and the Normal one is half that. Its strange and mystifies me, which concludes that it could be a codec limitation, if the MJPEG can do it, why can the HEVC not do it? Sounds really strange, I am testing the 720p mode as we speak, if it wields the same results I wont bother posting about it, someone else tested 1080p mode which seemed to suffer from the same issues. MJPEG is the only one that not just broke the 78 minute mark but it completely blew me away how long it recorded, it was still going until next morning until it ran out of space and froze the camera.
    I will also do a third record session with the MJPEG with the 128GB card to see how long he can sustain record time, I am going to assume its going to be over 1200 minutes which will be quite long time indeed. I decided to share this details simply because it struck me as weird, why would the MJPEG reach 58GB while the same resolution HEVC did not even reach 3GB before stopping, its just puzzling.
  6. Like
    SMGJohn got a reaction from TheRenaissanceMan in Petition for Samsung NX1 hack   
    I have found a massive issue regarding record limit on the HEVC, it appears to be more the fault of HEVC screwing around with us rather than the camera or file structure issues.
    I tested the MJPEG codec this time around with a 64GB card and the camera plugged into the wall with no battery power to do a record session. Lets just say, just not did it pass the 75 - 78 minute limit the HEVC exhibits.
    It clocked around ~620 minutes before running out of space on the 64GB card and froze, I am pretty sure it would last even longer if I had used the 128GB one.

     
     
     
     
     
     
     
     
     
     
     
    Now again this is a low bitrate, low resolution video mode that works the sensor less, so I did the test again but this time with 480p HEVC at 25fps, and once more it crashes at 75 - 78 minute mark, its hard to tell the exact mark because its random most of the time. 
    I tried both HQ and Normal bitrate but it still crashes above 75~min. files for HQ are no more than over 2GB and the Normal one is half that. Its strange and mystifies me, which concludes that it could be a codec limitation, if the MJPEG can do it, why can the HEVC not do it? Sounds really strange, I am testing the 720p mode as we speak, if it wields the same results I wont bother posting about it, someone else tested 1080p mode which seemed to suffer from the same issues. MJPEG is the only one that not just broke the 78 minute mark but it completely blew me away how long it recorded, it was still going until next morning until it ran out of space and froze the camera.
    I will also do a third record session with the MJPEG with the 128GB card to see how long he can sustain record time, I am going to assume its going to be over 1200 minutes which will be quite long time indeed. I decided to share this details simply because it struck me as weird, why would the MJPEG reach 58GB while the same resolution HEVC did not even reach 3GB before stopping, its just puzzling.
  7. Like
    SMGJohn got a reaction from Marco Tecno in Petition for Samsung NX1 hack   
    I have found a massive issue regarding record limit on the HEVC, it appears to be more the fault of HEVC screwing around with us rather than the camera or file structure issues.
    I tested the MJPEG codec this time around with a 64GB card and the camera plugged into the wall with no battery power to do a record session. Lets just say, just not did it pass the 75 - 78 minute limit the HEVC exhibits.
    It clocked around ~620 minutes before running out of space on the 64GB card and froze, I am pretty sure it would last even longer if I had used the 128GB one.

     
     
     
     
     
     
     
     
     
     
     
    Now again this is a low bitrate, low resolution video mode that works the sensor less, so I did the test again but this time with 480p HEVC at 25fps, and once more it crashes at 75 - 78 minute mark, its hard to tell the exact mark because its random most of the time. 
    I tried both HQ and Normal bitrate but it still crashes above 75~min. files for HQ are no more than over 2GB and the Normal one is half that. Its strange and mystifies me, which concludes that it could be a codec limitation, if the MJPEG can do it, why can the HEVC not do it? Sounds really strange, I am testing the 720p mode as we speak, if it wields the same results I wont bother posting about it, someone else tested 1080p mode which seemed to suffer from the same issues. MJPEG is the only one that not just broke the 78 minute mark but it completely blew me away how long it recorded, it was still going until next morning until it ran out of space and froze the camera.
    I will also do a third record session with the MJPEG with the 128GB card to see how long he can sustain record time, I am going to assume its going to be over 1200 minutes which will be quite long time indeed. I decided to share this details simply because it struck me as weird, why would the MJPEG reach 58GB while the same resolution HEVC did not even reach 3GB before stopping, its just puzzling.
  8. Like
    SMGJohn got a reaction from Pavel MaÅ¡ek in Petition for Samsung NX1 hack   
    I have found a massive issue regarding record limit on the HEVC, it appears to be more the fault of HEVC screwing around with us rather than the camera or file structure issues.
    I tested the MJPEG codec this time around with a 64GB card and the camera plugged into the wall with no battery power to do a record session. Lets just say, just not did it pass the 75 - 78 minute limit the HEVC exhibits.
    It clocked around ~620 minutes before running out of space on the 64GB card and froze, I am pretty sure it would last even longer if I had used the 128GB one.

     
     
     
     
     
     
     
     
     
     
     
    Now again this is a low bitrate, low resolution video mode that works the sensor less, so I did the test again but this time with 480p HEVC at 25fps, and once more it crashes at 75 - 78 minute mark, its hard to tell the exact mark because its random most of the time. 
    I tried both HQ and Normal bitrate but it still crashes above 75~min. files for HQ are no more than over 2GB and the Normal one is half that. Its strange and mystifies me, which concludes that it could be a codec limitation, if the MJPEG can do it, why can the HEVC not do it? Sounds really strange, I am testing the 720p mode as we speak, if it wields the same results I wont bother posting about it, someone else tested 1080p mode which seemed to suffer from the same issues. MJPEG is the only one that not just broke the 78 minute mark but it completely blew me away how long it recorded, it was still going until next morning until it ran out of space and froze the camera.
    I will also do a third record session with the MJPEG with the 128GB card to see how long he can sustain record time, I am going to assume its going to be over 1200 minutes which will be quite long time indeed. I decided to share this details simply because it struck me as weird, why would the MJPEG reach 58GB while the same resolution HEVC did not even reach 3GB before stopping, its just puzzling.
  9. Like
    SMGJohn got a reaction from Kisaha in 4K / 2K MJPEG?   
    Chant said he might look into increasing resolution and maybe bitrate for the MJPEG, honestly I think the focus should be more on the MJPEG rather than the HEVC which is just painful to work with already and any higher bitrate will make it even more painful to work with than it already is, so instead of having a thorn in our bums, MJPEG would be the better pick here for easy editing.
  10. Like
    SMGJohn reacted to Otto K in Petition for Samsung NX1 hack   
    @vaga it depends on the setting, but this tool is, IMHO, better for data gathering as it has access to things some others don't. Oh, and for backup. 
  11. Like
    SMGJohn got a reaction from kidzrevil in 4K / 2K MJPEG?   
    Chant said he might look into increasing resolution and maybe bitrate for the MJPEG, honestly I think the focus should be more on the MJPEG rather than the HEVC which is just painful to work with already and any higher bitrate will make it even more painful to work with than it already is, so instead of having a thorn in our bums, MJPEG would be the better pick here for easy editing.
  12. Like
    SMGJohn reacted to Andrew Reid in NX500 hopes and dreams   
    Yes huge thanks to Otto, amazing work.
    I wonder if the Magic Lantern guys might want to collaborate with him on it?
  13. Like
    SMGJohn got a reaction from /Chop N Shoot Films/ in 4K / 2K MJPEG?   
    Chant said he might look into increasing resolution and maybe bitrate for the MJPEG, honestly I think the focus should be more on the MJPEG rather than the HEVC which is just painful to work with already and any higher bitrate will make it even more painful to work with than it already is, so instead of having a thorn in our bums, MJPEG would be the better pick here for easy editing.
  14. Like
    SMGJohn got a reaction from Pavel MaÅ¡ek in 4K / 2K MJPEG?   
    Chant said he might look into increasing resolution and maybe bitrate for the MJPEG, honestly I think the focus should be more on the MJPEG rather than the HEVC which is just painful to work with already and any higher bitrate will make it even more painful to work with than it already is, so instead of having a thorn in our bums, MJPEG would be the better pick here for easy editing.
  15. Like
    SMGJohn got a reaction from samuel.cabral in 4K / 2K MJPEG?   
    Chant said he might look into increasing resolution and maybe bitrate for the MJPEG, honestly I think the focus should be more on the MJPEG rather than the HEVC which is just painful to work with already and any higher bitrate will make it even more painful to work with than it already is, so instead of having a thorn in our bums, MJPEG would be the better pick here for easy editing.
  16. Like
    SMGJohn got a reaction from Beritar in 4K / 2K MJPEG?   
    Chant said he might look into increasing resolution and maybe bitrate for the MJPEG, honestly I think the focus should be more on the MJPEG rather than the HEVC which is just painful to work with already and any higher bitrate will make it even more painful to work with than it already is, so instead of having a thorn in our bums, MJPEG would be the better pick here for easy editing.
  17. Like
    SMGJohn got a reaction from Alborat in 4K / 2K MJPEG?   
    Chant said he might look into increasing resolution and maybe bitrate for the MJPEG, honestly I think the focus should be more on the MJPEG rather than the HEVC which is just painful to work with already and any higher bitrate will make it even more painful to work with than it already is, so instead of having a thorn in our bums, MJPEG would be the better pick here for easy editing.
  18. Like
    SMGJohn got a reaction from Marco Tecno in 4K / 2K MJPEG?   
    Chant said he might look into increasing resolution and maybe bitrate for the MJPEG, honestly I think the focus should be more on the MJPEG rather than the HEVC which is just painful to work with already and any higher bitrate will make it even more painful to work with than it already is, so instead of having a thorn in our bums, MJPEG would be the better pick here for easy editing.
  19. Like
    SMGJohn reacted to Andrew Reid in 4K / 2K MJPEG?   
    I see the NX1 and NX500 have an MJPEG codec, but it's only used for the 640x480 recording mode.
    But the codec is there, right? Maybe we could persuade it to record at a higher resolution and bitrate in 4:2:2 like the Canon 1D C. (Ok, wild leap there, but any improvement would be an interesting discovery).
    Also the silent shutter, in this mode it does raw from a rolling shutter scan of the sensor, just like a video mode... the raw data must be lurking in the buffer somewhere whilst it runs in video mode... now what we need is a genius to dive in a grab it
  20. Like
    SMGJohn reacted to Chant in Petition for Samsung NX1 hack   
    When Im off work Ill post up what Ive been doing and the things that have happened with the route Im doing. I suggest that otto k and vasile when he is back start a new thread containing the work they have done, as they are pertaining to different things and their updates come more quickly than mine! I will also post up the info in a github of the progress but I think it would help the organize the information better
  21. Like
    SMGJohn got a reaction from Geoff CB in Petition for Samsung NX1 hack   
    480p25 MJPEG vs HEVC - NX1
    So I decided to test in internal MJPEG versus HEVC at the same resolution and framerate, obviously the HEVC will have lower bitrate than the MJPEG one, regardless I found some interesting results, hopefully the forum wont compress the PNG's to death, but the MJPEG has noticeable more grain details compared to HEVC whether this is the codec or simply lower bitrate for the HEVC is hard to tell. Still the HEVC shows the same noise characteristics it does in 80mbps, it simply smooths them out.
    I filmed them in GammaC and GammaDR with HQ video setting in camera, 1/50 shutter, F/2.8 and ISO1000, exposed to 0, all images were given the same simple curve adjustment in photoshop to raise shadows.
     
    GammaC settings:
    Red X1.00 - Green X0.95 - Blue X1.00
    Sharpness -7
    Contrast -3
    GammaDR settings:
    Red X1.00 - Green X0.95 - Blue X1.00
    Sharpness -10
    Contrast -10
     
    MJPEG - GammaC

    HEVC - GammaC

    MJPEG - GammaDR

    HEVC - GammaDR


    LEFT = MJPEG | RIGHT = HEVC
  22. Like
    SMGJohn reacted to Andrew Reid in Petition for Samsung NX1 hack   
    NX1 forum can be for all the Samsung cameras for now.
  23. Like
    SMGJohn reacted to Andrew Reid in Petition for Samsung NX1 hack   
    Things are moving fast guys.
    I've created a sub-forum for any subjects which might require a separate thread.
    Regarding compression on uploads or attachments, let me know if this is a problem and I will look into it.
    http://www.eoshd.com/comments/forum/25-samsung-nx1-hack/
  24. Like
    SMGJohn got a reaction from sandro in Petition for Samsung NX1 hack   
    That is basically what Motion JPEG codec is and Motion JPEG 2000 which allows for 422 - 444 and 10bit
  25. Like
    SMGJohn got a reaction from Otto K in Petition for Samsung NX1 hack   
    That is basically what Motion JPEG codec is and Motion JPEG 2000 which allows for 422 - 444 and 10bit
×
×
  • Create New...