Andrew Reid

EH? Neither have 4K UHD for a start. They only shoot DCI 4K.

Rather have MJPEG than a 3 minute time limit due to heat (cough cough Nikon)

This is superb. Thanks so much Ebrahim.

So just a recap on the crops... The 4K is APS-H crop, no full frame and the 1080p is pixel binned full frame. I heard some criticism that it shoots 4096 x 2160 instead of the more usual Ultra HD. Can only laugh at that. So trivial to place DCI 4K on a 3840 x 2160 timeline in any NLE.

It's not.

There was one that flashed off too quickly before I had finished reading it... Only one though, early on.

I think the message is pretty clear. A lot of democrats love Bernie and agree with him (especially younger voters) but they don't think he can beat Clinton for the nomination or get enough support. Thus if everyone thinks like that it is self defeating and the fate of the nation is decided in their heads before even a single vote has been cast.

Ah well FCPX is newer architecture and will be quicker than Premiere. My experiences are with 4K MJPEG at 24p in Premiere. Besides I don't think FCPX will deal as smoothly with 4K MJPEG at 60fps as it does with the 1D C's 24fps. 4K 60fps is more than double the number of frames to deal with and 800Mbit/s a big increase from 500Mbit/s. Hate to be negative but that's the way it is and I can't see it changing any time soon.

It's not hard on the disk... even 800Mbit/s is 80 megabytes per second off the drive and SSDs regularly do 500MB/s max, at least 350MB/s sustained. The problem is the CPU and lack of hardware acceleration for MJPEG. You can't apply much colour correction or effects in Premiere on 1D C footage and get smooth playback on the timeline without any rendering.

Speaking from my 1D C experience... MJPEG is 500Mbit/s so the data rate for the CPU to handle is insane. Editing off an SSD or RAID 0 like I do the drives aren't a bottle neck, it's the CPU. What compounds the problem is that MJPEG doesn't seem to be well supported with hardware acceleration. The Mercury Engine in Premiere for instance seems to revert to software rather than hardware accelerated by Open CL or CUDA when it comes to MJPEG. H.264 and H.265 may be more complex with the clever compression but it is hardware accelerated. You will effectivly be editing MJPEG 4K 60fps at 800Mbit/s in software mode, on the CPU only. The effects will take ages to render too. 1D C 4K 24p is 500Mbit/s (same on 1D X Mark II)... this is tough enough, you really need to transcode to ProRes. Again speaking from direct experience with the files, the H.264 4K from the GH4 and A7S II can be edited natively on my machine in Premiere with smooth playback especially at 1/2 res in the timeline monitor. MJPEG doesn't even play back smoothly when I reduce the playback res, which again points to the lack of proper support of such an old dated codec in a modern NLE. Canon have made a mistake.

File sizes are not too big for the NX1 at all. It doesn't need transcoding now, and it was always clear H.265 would get broad support in NLEs pretty quickly. The transcoding step I did put up with... it was a $1500 camera not a $6k one. I don't see why I should have to put up with MJPEG at $6k in 2016. On a used 1D C from 2012, that is understandable but it isn't now. Yes the FS7 is too big for me which is why I got the FS5 instead! My only use for 60p would be slow-mo. 60p offers mediocre slow-mo. I would rather sacrifice the resolution and unmanageable file sizes and shoot 240fps 1080p on the FS5... Oh did I mention the FS5 is also $400 cheaper than the 1D X Mark II, has a variable ND filter, LOG, small 4K file sizes, Speed Booster and proper video ergonomics & features?

I'd like to see her un-convince herself of voting for Bernie in a clever and impactful way that shows how stupid voters are

I prefer the Canon image as well but for sure as hell don't need 800Mbit/s 60fps file sizes. Think I will wait and see what else comes out this year. The 1D C's image is still the best 24p 4K for the money (and NX1 at the cheaper end).

This is lovely, nicely done Ed. There's a clear idea behind it which I like, in that the fate of a nation is decided in people's heads where principals get overridden by "what if" practical reasoning. But it's not executed to it's full potential. I think you should expand on it. I'd love to see an arc to the unfolding chatter, which takes it someplace else like a journey. She kind of starts and ends up in the same state

Sorry but 4K 60fps at 800Mbit/s is a total bullshit feature 10 minutes per 64GB card and impossible to edit without a transcoding step. At $6k, only $2k off the price of an FS7 which does 4K 60fps in a body designed for video to a codec designed for editing. Also there are so many cheap cameras that do 1080/60fps if slow-mo is your aim... Or even better many cameras half or even quarter the price of the 1D X Mark II that do 120fps! Small correction. The GH3 was not the first to get 1080/50p... Sony NEX 7 was. You see, we have had 60fps for mediocre slow-mo since 2011... why because it is now 4K is it suddenly a HUGE deal again?

How much for the 1D C cage Franz? I don't think the 1D C prices will drop - the 1D X Mark II only adds 60fps and AF. It takes away Canon LOG. It doesn't add a 4K HDMI output, peaking, articulated screen, XF codec or any Cinema EOS features worth mentioning apart from that Dual Pixel AF. Also at around 6000 euro its more expensive than a used 1D C. MJPEG was the weakest feature of the 1D C, it means a transcoding step and massive file sizes. Zero reason Canon could not have put an XF codec based on H.264 in the updated camera. 4K at 60fps will either be less quality at same bitrate as 1D C (500Mbit/s) or double the bitrate and double the file sizes. It's a lose-lose situation they have given us on the codec side. MJPEG 4:2:2 8bit is not better quality than H.264 4:2:2 10bit at half the bitrate of MJPEG so I don't really know if Canon can justify MJPEG with an image quality argument either.

Corrected link to the guide in OP - it is now: http://www.eoshd.com/samsung-nx1-video-settings-guide-tutorial/

Good luck editing 4K 60p in MJPEG on... anything

What for $6k? From Canon? I doubt it It probably doesn't even have peaking Honestly guys I would not expect a professional video codec on this camera... it will be small file sizes all the way. It isn't a Cinema EOS camera, it is designed for news crews, paparazzi and sports photographers to WeTransfer MOV clips to hacks.

My bet is it will be Super 35mm crop not 1.3x like the 1D C or full frame. There are also question marks over the codec. I doubt it is 500Mbit/s at 4K 60fps! The 1D C is 500Mbit/s in 24p - so a very nice image. It could be a worse image on the 1D X Mark II with more compression and less sensor area. Ultra HD crop from 20MP like we saw with D5 is 1.5x.

Looks like Alistair finally got the memo. http://www.xdcam-user.com/2016/01/sony-make-official-statement-regard-fs5-image-artefacts/ He eats words like I do cornflakes for breakfast.

Only if you're stupid. That's why you test a new camera before deploying it at work. Or read EOSHD before buying something. Or just avoid the settings where the bugs occur. Not rocket science is it. Not just fix it, but add new features like raw. Hard not to get excited about that Mr Cynical.

They could have saved themselves a lot of bad publicity and lost sales by having stronger critical judgement from their pre-production shooters Alister Chapman is looking very silly now. In the end the customer is always right... We are the ones that have to be convinced by the images, and at the moment there is unfortunately still too much XDCAM VIDEO DNA in the FS range.

Last week I had an insight into just how responsive Sony are becoming in rolling out support for their cameras. As users like myself and Paul Antico discovered soon after the FS5 was released the image had some issues. The very week I bought my camera Sony were in touch by email - I was then tasked to shoot some tests and send the XAVC footage to their engineers in Japan so they could work on analysing the problem. The detective work complete, Sony have now just released a statement saying they've identified the bugs and will squash these in upcoming firmware updates. Read the full article

I don't think there's quite the community around Fuji's cameras to make this possible like there is for Canon and Panasonic. Especially not for video.