NX1 users rejoice: H.265 support coming to AE CC 2015 update

So, I thought it'd be concurrent with the Windows 10 release and it's about a month later.
 
Premiere CC is getting it too later in the year according to Adobe. I wish Resolve 12 got it in the final release. It would be joyful for me! I absolutely love my NX1 for stills and video! Amazing little camera!
 
So what is currently the best workflow for h265? Is there a software that yields better image quality? I'm getting posterization very often.
 
It was a bold move by Samsung to put H.265 in their camera but was it a good move? Seems like a good H.264 implementation would have just as many benefits. Memory is very cheap and fast these days.
 
Until further notice H.265 just has to be regarded like RAW - meaning you just simply must transcode it prior to beginning work.

Yeah, it's a bummer, but it should only be for a few more months.

After all the NLE's update and add H.265 then all this will be forgotten.

Remember, the same thing just happened with AVCHD.
 
Bassman2003 said:
It was a bold move by Samsung to put H.265 in their camera but was it a good move? Seems like a good H.264 implementation would have just as many benefits. Memory is very cheap and fast these days.
Click to expand...
But then they'd have to tell you which cards work and which may not work quite as well as promised (do note how Convergent Design sets its criteria) and that can lead to some legal - or, worse, the internal company - arguments. Then they may have to redo the entire interface and that would have led to higher costs, et cetera.

IMO, 4K sets up well for the HEVC, even if NX1 had it nearly a year ahead of its time.
 
Yep, it is probably too much to add now. I was just referencing the initial design. I don't mind RAW transcoding as you get the chance to shape your image in the deal. "Converting" only is kind of a drag.
 
Any mention of support beyond 4K? I know h.265 standard can technically achieve 8K resolutions.​
Click to expand...

LOL! We can't handle H265 4K yet imagine 8K! I don't think computers as they are today won't be able to handle 8K at all.
 
egproductions said:
Any mention of support beyond 4K? I know h.265 standard can technically achieve 8K resolutions.
Click to expand...
The prototype 8K Canon camera that was shown at the Canon Expo last week had four (4!) Convergent Design Q7+ recorders hooked up to it, each responsible for its own 4K stream. To do 8K off one feed, all these recorder companies would have to scramble a little ... but one figures there's plenty of time for them to do that.
 
Red camera's go above 4K so I would think the need for an efficient codec above 4K is relevant. That aside, for my purposes, I'm looking to composite multiple 4K frames together.
 
Bassman2003 said:
It was a bold move by Samsung to put H.265 in their camera but was it a good move? Seems like a good H.264 implementation would have just as many benefits. Memory is very cheap and fast these days.
Click to expand...

I think it was more like when Apple dumped floppy drives, then optical drives, then FireWire, and expected the market to follow. Their opinion was "this is the best way and we're not doing it another way".

Samsung claims H265 can equal or better any similar bitrate of 264, at half the file size. And regardless of implementation, they decided it was the best, no-brainer codec for DSLRs, so they did it. (Don't forget the reviewer-shock when Samsung released a DSLR that was a serious contender in the Nikon-Canon market - they had to go all-out).

If they had given users the menu choice of 264 vs 265, everyone would have just shot 264 and there would be no strong demand for 265. Yeah, we'd read some reviews where someone got 265 transcoded and said "holy crap, this is where the camera really delivers" but there wouldn't be a burning need for widespread 265 adoption.

So is Samsung alone responsible for H265 coming to the Adobe suite - this year at least? I'd imagine so. If H265 becomes easier to use and more widely adopted (remember when people had to transcode H264?) by camera manufacturers, will Samsung get the credit for that (like Apple should get the credit for Visual Voicemail and, like, everything about smart phone UIs that everyone on earth has now copied)? Maybe so. It was a bold move by them. The whole damn camera was, as was their firmware strategy and their move into big-pro lens production. (Still haven't bought one though).
 
HEVC was developed by a committee and its arrival was inevitable, as the global data delivery - especially the internet video - kept ramping up. In the low-to-medium video market, HEVC helps with the media and the internal electronics that connect to the removable media. The downside is the increased processing power and the accumulation of heat. (and the early compatibility issues).

Me thinks, as this low-to-medium market moves to 10-bit 4:2:2 internal recording, an improvement over H264 based codecs is a must because faster cards (CFast2.0 and up) are more expensive than the encoding chips.*

A typical ARM based processor runs $20-$30. It includes both the operating and the graphics chip, comprising the so-called SoC.
 
DLD said:
The downside is the increased processing power and the accumulation of heat. (and the early compatibility issues).
Click to expand...
DLD, you forgot to mention the downside of patent-holders coming out of the woodwork demanding royalties. We're up to two patent pools now, and I hear that a third patent pool is expected. Each of them charging their own royalty fees. If I were a camera manufacturer, I would say screw that - I'm sticking with H.264.
 
Shenan said:
DLD, you forgot to mention the downside of patent-holders coming out of the woodwork demanding royalties. We're up to two patent pools now, and I hear that a third patent pool is expected. Each of them charging their own royalty fees. If I were a camera manufacturer, I would say screw that - I'm sticking with H.264.
Click to expand...
This is why the Blu-Ray player delivery has been pushed back. From an engineering standpoint, the player can go into production.

As to the various patent groups, they're certainly mocking up things. This is why there are alternate royalty-free codecs that are being developed (by Cisco and Daala) in addition to the already existing Google's VP9. The problem here is that big manufacturers are themselves represented on these coalitions and the royalties in question will generally levied against smaller entities, such as the internet streamers. The biggest losers, in the short term, are the content creators and the consumers. In the long term, these patent holders/pretenders/trolls will likely lose due to the companies bypassing their software altogether.

My take here is that the Blu-Ray makers have little choice, as the player was designed around HEVC, but, if I were a camera manufacturer, I'd go with VP9 right now and tell the legal beagles to go hump themselves. The reason for that is the transcoding ability of the advanced amateurs and pros. Sure, it might take a little longer but the benefits will usually outweigh it.

The other approach that is available to the manufacturers is to choose the established H.264 based codec and internal storage. A new Samsung 256 GB SSD that was announced yesterday retails for $200 and can hold about three hours of footage recorded at 200 Mbps. Transfer the files out via a USB 3.1 or T-bolt 3 port and voila.
 
A price drop on NX1 - now $1,200 (plus, B&H gives a 4% rebate, making it $1,150) for body only.

NX500 is now $599, with the lens included.

Are there new models on the horizon or is Samsung dropping out of the photo game, as some had rumored lately?

Or nothing at all?
 
DLD said:
A price drop on NX1 - now $1,200 (plus, B&H gives a 4% rebate, making it $1,150) for body only.

NX500 is now $599, with the lens included.

Are there new models on the horizon or is Samsung dropping out of the photo game, as some had rumored lately?

Or nothing at all?
Click to expand...

Sale ends tomorrow.
I suspect it was nothing more than that.
It was a pretty short sale too.
 
You must log in or register to reply here.
Back
Top