Intel announces 7th Gen Kaby Lake CPUs with 10 Bit Hardware Decode and Encode

[LimitBreak]

10 Bit HEVC 4K Encode and Decode provides 4K editing and watching capabilities to the masses. Also will support VP9 10 bit hardware decode and 8 bit VP9 hardware Encode for Youtube consumption. 

If you have the Samsung NX1 or NX500 and want to edit on the go, this might be useful for you. 

Source:  http://www.anandtech.com/show/10610/intel-announces-7th-gen-kaby-lake-14nm-plus-six-notebook-skus-desktop-coming-in-january/3

"There's also HDR and wide color gamut support, but Intel says it's up to manufacturers to implement the two competing HDR standards, Dolby Vision and HDR10. On top of just letting you watch more 4K video, the new chips' encoding performance could be a huge deal for anyone editing media, with speeds between 1X and 3X real-time for 30FPS 4K. Source: https://www.engadget.com/2016/08/30/intel-7th-generation-core-cpus/"

 

 

[DBounce]

1 hour ago, LimitBreak said:

10 Bit HEVC 4K Encode and Decode provides 4K editing and watching capabilities to the masses. Also will support VP9 10 bit hardware decode and 8 bit VP9 hardware Encode for Youtube consumption. 

If you have the Samsung NX1 or NX500 and want to edit on the go, this might be useful for you. 

Source:  http://www.anandtech.com/show/10610/intel-announces-7th-gen-kaby-lake-14nm-plus-six-notebook-skus-desktop-coming-in-january/3

"There's also HDR and wide color gamut support, but Intel says it's up to manufacturers to implement the two competing HDR standards, Dolby Vision and HDR10. On top of just letting you watch more 4K video, the new chips' encoding performance could be a huge deal for anyone editing media, with speeds between 1X and 3X real-time for 30FPS 4K. Source: https://www.engadget.com/2016/08/30/intel-7th-generation-core-cpus/"

 

 

Samsung was ahead of it's time with the NX1... Too bad they got out of the DSLR business. They showed real promise. 

[MountneerMan]

"HEVC decode designed to meet 4kp60 real-time (RT) at up to 120 Mbps"

Is it just me or does this seam way too low bit rate for 60p?

[ntblowz]

15 minutes ago, MountneerMan said:

"HEVC decode designed to meet 4kp60 real-time (RT) at up to 120 Mbps"

Is it just me or does this seam way too low bit rate for 60p?

HEVC is like double the current compression in terms of the efficiency, so 120Mbps will be equal to 240Mbps in H.264

[IronFilm]

RIP Samsung,  you were way ahead of your time. Too smart for your own good! 

[Luke Mason]

HEVC/H.265 was not suitable for and was not designed as an acquisition format, it's too computationally intensive for both encoding and decoding.

[Andrew Reid]

5 minutes ago, Luke Mason said:

HEVC/H.265 was not suitable for and was not designed as an acquisition format, it's too computationally intensive for both encoding and decoding.

I see where you're coming from but...

That is the same as saying H.264 wasn't designed as an acquisition format, yet now it's the basis for Sony XAVC and Canon XF codecs.

As long as H.265 has the hardware encoder / decoder chips to support it there's no reason why it can't be an acquisition format and an edit-ready codec.

[Marco Tecno]

120mb is definitely too low for nx1 with the hack, which easily reaches 160-180mb.

[Luke Mason]

42 minutes ago, Andrew Reid said:

I see where you're coming from but...

That is the same as saying H.264 wasn't designed as an acquisition format, yet now it's the basis for Sony XAVC and Canon XF codecs.

As long as H.265 has the hardware encoder / decoder chips to support it there's no reason why it can't be an acquisition format and an edit-ready codec.

You said it yourself, H264 is the basis of XAVC and XF-AVC, there were a lot of changes made to them and they are distinctively different from consumer H.264 designed for exhibition.

 

[MountneerMan]

Personally I don't have any issue with using H.265 or H.264. I have an NX1 and love the image it gives.

The thing that has always bothered me is the fact that I film with HEVC and usually deliver in H.264 witch is theoretically less compression and it "should" be the other way around.