Jump to content

Last Leaves

Members
  • Content Count

    12
  • Joined

  • Last visited

About Last Leaves

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I'm really anxious to give it a try, but I just got a flood of work. If no one else does, I'll post some tests by the end of the week... wish it could be sooner. Thanks for all your hard work Vasile!
  2. My guess: A= 180Mb/s B= 80Mb/s and C(actually named "D")= Shogun My fast pass CC (could not get anything that I was happy with)- same order as yours: Stress test to show light bulb roll-off/banding (same order as yours):
  3. For me it hadn't been an issue because I transcode my footage to Prores for editing. I don't normally need to play h.265 files back, and when I have I've used VLC without issues up until now. Now, sorry for the distractions. Does anyone have any idea how we might go about trying to resolve this problem with the NX500 1080p120 "hack"?
  4. I made a mistake saying that all NX500 clips on my computer play fine in VLC. Upon closer inspection it appears that all 120p h.265s from the NX500 play back with this glitch in VLC. All non-120p clips play back without any problems. Sorry for the confusion, I should have checked that more closely. The real takeaway is that the 720p120 setting is actually recording 120p that is useable for slow motion work while the 1080p120 "hack" is not. Obviously, Otto pointed this out by saying that it wasn't real 120p, but I didn't find a description of the footage that stated that it was unusable for s
  5. Again, I am not saying that bitrates should never be variable. What I am saying is that: Every "non-hacked" video that I have shot on NX500 appears to have a completely constant bitrate, with absolutely no variations at all. The "hacked" 1080p @ 120fps using Otto's script provided on GitHub produces a file with an extremely variable bitrate. This "hack" appears to not work properly.
  6. I am skeptical that it is an apple issue. I'm pretty sure the file produced by the NX500 with the 1080p120 setting is messed up. I have never had any issue decoding any other NX500 clip (even on my brand-new-top-of-the-line-piece-of-shit apple machine that I shouldn't have bought because "really - it's a mac"). I know that variable bitrate can be good, but jumping from 2MB/s to 380Mb/s and back when the only thing changing in the shot are a few falling snowflakes does not seem like a good management of bitrate. Here are two test files straight off of the NX500's card: http://www.filedrop
  7. I just tested the NX500 1080p @120FPS via Otto K's github. By no means am I complaining, but the initial results were very disappointing. I saw that Otto said "not a real 120fps" but I wasn't sure what he meant. First of all, when I try to open the h.265 files in VLC (which usually plays h.265s straight off the NX500 without a problem) there are strange glitches in the footage. Every few frames displays completely full of strange artifacts (see pictures), like a corrupted or incomplete file. The strangest thing is that, similarly to Vasile's bitrate-boosted aquarium clip, the data rate is
  8. I'm quite certain that it is actually 23.98p not 98p, but it's written as "3840_2160_23_98p". I hope I'm wrong.
  9. A few feature hopes and dreams from someone willing to test, but not savvy enough to explore on my own. Thanks in advance for any work. The "SAS" (Samsung Auto Shot) functions on the NX500 have the potential of being very useful for various applications, but they are crippled by a few limitations that are most likely software-based. If you're struggling to see how the SAS functions would be useful skip to the Hypothetical Shoot Scenarios at the end. In order of priority, these are some changes that would make the SAS functions more useful: The ability to capture in RAW. Curre
  10. This was something that I noticed with Vasile's aquarium too. It is normal for bitrates to be somewhat variable, especially with the amount of color and light changing (i.e. less detail, less light, requires less data). But, assuming VLC's "Statistics" panel is accurate, this seems to be inverted with Vasile's clip; when the clip is completely black is when the bitrate is the highest. I have found frames (at around 21 seconds) that are less than 1/4 of the bitrate during the completely black seconds at the beginning. What is going on here? EDIT: I just checked a clip (DC24P [Cinema 4K] Mo
  11. Doh! I stupidly thought all of this time that the NX500 defaulted to exfat. I just formatted to expat with disk utility and it worked like a charm. Thanks.
  12. Long time lurker, first time poster, NX500 owner. First off, thanks to the folks that know what they are doing. Y'all are really doing all of us a huge service, and it is greatly appreciated. I just tried Vasile's record limit trick with some initially disappointing results. I'm hoping that these are due to my SD card. I don't want this to come across as complaining, just what I've observed with my attempt. NX500 w/ Transcend 32GB SDHC Class 10 UHS-1 600x card (this one) I followed Vasile's directions. No problems there. When I hit record on any of the settings it initially will
×
×
  • Create New...