Jump to content

EditReady now supports the Samsung NX1 / H.265


Andrew Reid
 Share

Recommended Posts

  • Administrators

I'm having trouble transcoding 1080p H265 files from my NX1, is there something

I'm missing. I just bought the damn software. It wont even let me view the video

and when it transcodes it shoots out a green screen with audio only.

​No ProRes codecs installed? Do you have Final Cut Pro X?

Link to comment
Share on other sites

​What are your specs?

​MacBook Pro (Retina, 15-inch, Mid 2014)

2,5 Ghz Intel Core i/

16 Gb DDR3 RAM

Nvidia GeForce GT 750M 2048 MB

 

It also can't convert the ProRes back to H265. Maybe this is not important for all but after editing my videos in ProRes UHD, I convert them to H265 to play it back on my 4K LG TV that supports natively h265.

Link to comment
Share on other sites

I'm really liking my NX1, but i don't really feel like I'm maximizing its potential, especially in terms of DR and color. On just standard profiles, it looks great right out of the cam, but I haven't found a good flat setting yet. The colors seem to get messed up to my eyes in Gamma DR. Do these various converters deal with color differently?

Link to comment
Share on other sites

I'm really liking my NX1, but i don't really feel like I'm maximizing its potential, especially in terms of DR and color. On just standard profiles, it looks great right out of the cam, but I haven't found a good flat setting yet. The colors seem to get messed up to my eyes in Gamma DR. Do these various converters deal with color differently?

​For ffmpeg-based transcoders, there's a bug in ffmpeg and ProRes: it appears anything > 1080p gets marked as bt601 (instead of rec709) and the resulting incorrect transform(s) change the color and gamma. I tried various workarounds when developing Photon however non of them worked (ProRes mode 1 in Photon has the least color shift vs. mode 2). Thus, I included high-bitrate H.264 420 8-bit as well as H.264 10-bit 422 which preserve color much better and should be visually equivalent to ProRes, especially when coming from H.265 8-bit 420. 10-bit 422 ALL-I H.264 is pretty much the same as ProRes (a form of MJPEG in a sense: however H.264 ALL-I likely has more advanced macroblock handling (variable sizes, quality), which can provide higher quality but is more expensive to decode vs. ProRes, which is very fast (even faster than vanilla MJPEG)).

Link to comment
Share on other sites

 @ Caleb Genheimer Try the "calm" picture profile and adjust the colors so that they look right in camera and not so washed out. I tweaked the calm profiles's RGB settings and Hue to get the color back into balance. I wouldn't call it flat but out of the color profiles, I would try tweaking "calm" or "standard" to taste if you do not like Gamma DR, which has its place but is not the end all be all of picture profiles.

Link to comment
Share on other sites

Yeah, top image is iFFmpeg — lower image is EditReady. 

Your top image is named: EditReady.jpg.d7b9435857e491918307a0beea52aae8.jpg

and the bottom image is: iFFmpeg.jpg.d89ba4bd239a8061c664c55e0d1c76fb.jpg

Unless something got mixed up, the iFFMPEG version has a lot more shadow information (and the EditReady version has severely clipped the blacks). I use FFMPEG extensively, using both ProRes modes, and haven't seen black clipping like that (there are color shift issues with 4K material, however). You might try exporting to H.264 in both EditReady and iFFMPEG and see the difference from ProRes (H.264 runs really fast in FFMPEG). 175-225Mb/s H.264 should be OK for editing coming from 100Mb/s H.265 (nothing really lost as both are 420 8-bit).

Link to comment
Share on other sites

Hi,

 

I did other file test just to check my previous test.

 

Here is the result:

MacbookPro 15" Retina (mid 2014), 2,5Ghz,16 gbyte Ram, Nvidia 750GTM

Original file
length: 1m26 sec
Size: 859 885 665 bytes 

EditReady

Conversion time 3:08

Size: 6 063 430 470 bytes / 564,35 mbits

iFFmpeg
Conversion time: 4:18
Size: 7 415 829 539 bytes  / 690,22 mbits
 
WonderShare:
Conversion time: 4:57
Size: 5 914 414 404 bytes / 550 mbits

  Check the histogram of all the converted files

EditReady

EditReady.png

iFFmpeg

iFFmpeg.png

Wondershare

Wondershare.png

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...