Pavel Mašek

Premiere doesn't like the default "data levels" of the H265 "fish tank" file. There is actually more dynamic range available in the shadows than what has been posted. In fact, DaVinci Resolve really brings the image to life if you input the file utilizing "data levels." Maybe I don't know Premiere well enough. Or, I'm just frustrated with Adobe?
Have never seen/graded NX1 footage before. Really excited to see this development take place and also frustrated to think how much tech is in the NX1 / NX500. Why is this tech being laid to rest by the manufacturer. Strange times, right!
From what I gather, this new bitrate is producing a natural response from the lens-sensor-processor-codec combination. It looks like it was shot at about 1600 ISO. Professionally speaking, this new bitrate may enable a new standard for accurately capturing an image without having to deal with random processing variations in the shadows/midtones/highlights. Hopefully, right.
Personally, I used to have quite a lot of issues with the GH4; specifically with regards to the lens-sensor-processing-codec algorithm. Eventually, I just went back to 1080 P DNG.
I'm impressed with render times with H265. First time for exporting an H265 image. Woohoo! DaVinci is exporting this 4k footage at nearly the same rate as the BMPCC 1080 DNG. It's possibly 1 - 2 frames faster with 1080 DNG pushed to the max 13 stops of DR and a light application of noise reduction. Then again, it's also only 1 - 2 frames behind 1080 DNG without the noise reduction. Kind of a nice balance, one with a serious bump in native image resolution. Does the footage need noise reduction? That's kind of what I'm thinking about here. It might actually need a fine layer of grain placed on top to reach a truly great image. But, who sees that stuff anyway?
Based on what others have written, over the past few pages, in regards to how h265 transcodes an image, I see the noise floor appear and also slightly disappear in this footage. It's nothing serious. IMO, I'm over analyzing the image. I feel that this was shot with contrasty glass set to a 5.6 in a room that reads somewhere closer to a T2.8 at ISO 800 on a LOG picture profile. Quite frankly, this combination is a challenge for any camera, especially when shooting with standard picture profiles, right?
Anyway, thanks for posting the "fish tank" video.
Also, it's not just the bit rate that's gone up, it's the heart rate too! I think the heart rate is closer to 100 BPM! LOL
Cheers,

YESSS! Incredible!  
I am also surprise that playback is realtime in full resolution in Premiere (it was choppy but I had to move the file to SSD, then it was fine). (i7 3,2Ghz, SSD, Nvidia GTX960 with h265 support). 
I think it is not against Vasile's rules - here are just 2 images - default and graded. The shadows noise is very usable - my opinion: it is not fine noise, but look at that - default was completely black in shadows!
 
 
 
 
 

Did a similar test. Ridiculously over and under exposed. I'm astounded. Given the lighting source I'm guessing we are looking at 800 iso or higher.

YESSS! Incredible!  
I am also surprise that playback is realtime in full resolution in Premiere (it was choppy but I had to move the file to SSD, then it was fine). (i7 3,2Ghz, SSD, Nvidia GTX960 with h265 support). 
I think it is not against Vasile's rules - here are just 2 images - default and graded. The shadows noise is very usable - my opinion: it is not fine noise, but look at that - default was completely black in shadows!
 
 
 
 
 

YESSS! Incredible!  
I am also surprise that playback is realtime in full resolution in Premiere (it was choppy but I had to move the file to SSD, then it was fine). (i7 3,2Ghz, SSD, Nvidia GTX960 with h265 support). 
I think it is not against Vasile's rules - here are just 2 images - default and graded. The shadows noise is very usable - my opinion: it is not fine noise, but look at that - default was completely black in shadows!
 
 
 
 
 

Looks like pretty good highlight recovery too

Petty outstanding. Curious of seeing what it could be done with gammaDR and Andrew's lut.

YESSS! Incredible!  
I am also surprise that playback is realtime in full resolution in Premiere (it was choppy but I had to move the file to SSD, then it was fine). (i7 3,2Ghz, SSD, Nvidia GTX960 with h265 support). 
I think it is not against Vasile's rules - here are just 2 images - default and graded. The shadows noise is very usable - my opinion: it is not fine noise, but look at that - default was completely black in shadows!
 
 
 
 
 

YESSS! Incredible!  
I am also surprise that playback is realtime in full resolution in Premiere (it was choppy but I had to move the file to SSD, then it was fine). (i7 3,2Ghz, SSD, Nvidia GTX960 with h265 support). 
I think it is not against Vasile's rules - here are just 2 images - default and graded. The shadows noise is very usable - my opinion: it is not fine noise, but look at that - default was completely black in shadows!
 
 
 
 
 

Can't wait to try this myself. I have the UHS-II card if I can give it a go for testing. 

Sweet Jesus and Lord in Heaven, I wonder what happens when you do GammaDR with that stuff, because I tried screw around with the clip in post and imao the range, the range! 
I hope there is a way to use the MJPEG codec for 2160p as well in high bitrates, that would be sweet.

Let's hope he doesn't vanish like the early nx hackers :-P 

My dreams come true :-D  Let's hope that will work on NX1 too (unlike silent shutter).

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

My dreams come true :-D  Let's hope that will work on NX1 too (unlike silent shutter).

My lexar 2000x can do about 250MB/sec write, so even 250Mb would be a joke for it!

Jesus Christ I had a look at that file and the noise grain is way better looking than my NX1, and I went to see why.
And turns out its got almost 75% more bits per pixel now I know its got half the resolution of the NX1 video, but the more bits per pixel is generally a good thing because the pixel has more information, and the more information the better for everything specially for this kind of resolution, not bad at all.
It will be interesting to see what the higher bitrate will do to the NX1 video and hopefully it might solve the terrible noise streak on ISO 3200 and above.

http://***URL removed***/forums/post/57456860
:-)

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.

https://www.slashcam.de/artikel/News/Samsung-NX1-NX500---erste-Hackerfolge.html

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.

What does these two settings do?
[113]| USERDATA_RAW_PACK             | RAW_PACK_PACK                 |0x00710000| 7405568|
[114]| USERDATA_RAWQUALITY           | RAWQUALITY_LOSSLESS           |0x00720000| 7471104|
Will it enable me to spit out lossless RAW photos? 
I always wanted to see what the NX1 would do with lossless raw images because I noticed blacks gets crushed on the extreme end and it looks more like compression artefacts than something the camera would not be able to capture.

Very nice! BTW - Is it Madeira?

Just finished my first Music Video, not exacly as I planned it would go, had some setbacks on filming and what not, but yet still pleased with how it turned out. Everything was shot on the NX1 and the aerials on the P3. Was a great challenge, doing something as "big" with such a tight budget, but loads of fun ! Let me know what you guys think =) 
 
 
Also, to anyone interested, heres the band iTunes page, they got some great songs =) https://itunes.apple.com/pt/album/new-dawn/id953049235?app=itunes&ign-mpt=uo%3D4

Mercer, I am both hobbyist and prosumer in the sense that I do short movies (+- 3 minutes) to place on vimeo to satisfy my "artistic" needs AND shoot shor clips with commercial value for Microstock for living. Because of that I'm of course always looking for best possible quality gear for value/money. So while profesionalism is the goal, minimalism in terms of quality for easy transportation for on location shoots is needed- for things like these, just gimme a year or two to get better in the edit part 

So when you mentioned the sensor is demanding, you actually pointed out the reason why I asked. If I may ask you for a bit of your time: what do you mean by that in connection to lenses and output quality? A few people already mentioned it, but I'm hoping for deeper explanation.