SMGJohn

Who actually has any coding experience here? Specially with Tizan Linux. I tried applying a modified firmware to the NX1 removing the record limit but the shit wont accept it, maybe there is some in-camera security system to check if firmware is legit or not?

There seems to be a lot of small forum posts about hacking the NX1, the camera definitely supports 10bit, 240fps in 1080p or even 1440p, it should also spit out 2160p in RAW and it should record 6k in 30 max fps in h265 codec with bitrate probably around 40 to 100 mbps. The 10bit colours or even 14bit should not cause much more strain on the CPU then there already is, its just requires a faster card. I would personally be willing to sacrifice my NX1 just to get all these features or at least 2160p raw output. It is a real bummer that Samsung decided not to enable these feature I know they are in the damn camera they are just disabled. God knows why the fuck they decided to do something as stupid like that, they could have sold the damn fucker for 6000+ dollars and enabled everything, it would be adopted by damn Hollywood for its image quality at such a price range.

Best lenses for Samsung camera regarding video is obviously the Samyang/Rokinon/Bower lenses which are cheap ultra-fast cine lenses with great value for what you get. Check this out for best deals on them: https://***URL not allowed***/the-best-samyang-rokinon-bower-cine-lens-deals-updated-sep-18th/ Remember that not all of them are APS-C size so you gotta apply crop factor on some of them since they are full-frame (Crop factor for NX1 is x1.53) If you just want an all around cheap and good Samsung lens for video I recommend the Samsung Compact 18-55mm f/3.5-5.6 OIS Zoom Lens its good value for money and it covers most of the zoom ranges you would need in video. If you need extra wide I recommend the Samsung Compact 12-24mm f/4-5.6 ED and of course if you got cash to burn get the Samsung 16-50mm f/2-2.8 OIS S lens. I do not really recommend neither the 45mm nor the 35mm because no one will notice the picture difference from them to the 12-24mm or the 18-55mm when it comes to video, these lenses are designed for high megapixel usage with Samsung cameras and the max you will use these for videos are generally 1080p and 2160p so the distortion is minimal.

That is RockyMountains Converter, ClipToolz v2 is usually a lot slower for God knows why, Adobe Media Encoder CC 2015 is also quite fast taking in the ProRes files and converting them to DNxHD444 in fact its almost faster than RockyMountains when I do 100 or 120fps LUT converting because I work with some people that uses FCPX and it does not like DNxHD and because ClipToolz does not like 100fps nor 120fps files I gotta convert it to ProResHQ (RockeyMountains) --> DNxHD444 with LOG (Media Encoder) --> ProResLT (RockeyMountains)

I found a different way of converting footage with LUT, basically you use RockyMountains Movie Converter, convert the h265 to ProRes 422HQ, and then use Adobe Media Encoder CC/2014/2015 to convert the footage to either ProRes 422LT or DNxHD185 with 10bit. Is a bit tedious but its the only way I found for Windows to reliable convert these 100FPS footage with the LUT, its great if I want to give off the footage to someone else without having to share the LUT as well because the footage is already converted with it. There is also Hybrid by selur.de that comes with Apple ProRes and DNxHD natively also supports x265 if someone wants more advanced controls than the simple interface of RockyMountains Movie Converter. I hope ClipToolz implements support for 100fps in their ProRes.

What settings did you have in ClipToolz? Also did you run it in compatibility mode + administration rights checked?

The encoding I tested was HEVC -> ProRes 422HQ In the program I had to select ProRes 4k in order to be able to apply the LUT, I tested it both with 1080p100 and 2160p25 and it applied the LUT fine, some of my older 1080p25 overcranked footage before the increasing bitrate firmware came I see extreme banding in the sky but that might also just be me tweaking the settings to give me a flat profile with this ¤/!%#@( 8bit codec. The 1080p100 footage wont convert in ProRes 4k mode, I assumed its because ProRes does not support 100 fps or the program is simply incapable of it, though it will slow the footage down for you. DNxHD does not have the LUT option available its greyed out for some reasons, MXF is useless it gets wrapper problems, the MPEG Intra are 8bit only also useless, the TIFF 48bit mode worked fine for me as well with the LUT so did H264 export. As for 25fps render for a 25p project file which was for ProRes, my computer is quite beefy so it tends to spit out 10 minute HEVC files in RockyMountains Converter in 2 minutes to ProRes

I gave ClipToolz Convert V2 a try, I got Windows 8.1 x64 at first it would not work properly but under Windows 7 compatibility mode and administration right it ran fine, the LUT wont work on all codecs but I tried the ProRes 4k with 422 colour space and 10bit the only available option for it, and it takes 1080p and 2160p just fine with the LUT and it looks pretty good. The interface is a bit lack-cluster but its better than nothing I suppose. Its also VERY slow, at most its 25fps for a 25p footage, I suppose it has to render the LUT data into the footage.

What do we Windows users have to do because EditReady does not work on Windows, do we just place the LUT at the bottom and stack other LUT's above it in Premiere after we converted the footage to ProRes422?

I have a few questions before buying, what I noticed when I personally transcode the HEVC files to ProRes or DNxHD with ffmpeg and applying a flat curve to it with AviSynth script is that the banding gets even worse than it already is. Now the banding is far better than it used to be in the past with the latest update of course, but will the banding be more visible with this workflow and do I get more infomation out of the shadows with this method? RE: I also noticed that you included EditReady in the article, I am an avid Windows user is there included an alternative for Windows or do you recommend any converters with LOG support, I know Vanguard is developing h.265 for Adobe After Effects, Premiere and Media Encoder and Media Encoder have LOG support to encode files with but its not out yet and probably wont be for a long time.