kidzrevil

Anything that gets read directly off the image sensor is "RAW." Magic lantern RAW comes from the image that is read out for live view, which is the same sensor mode that is used for video. Any camera with live view (essentially all modern cameras, including the NX1) could be hacked to do RAW video in theory, since they have to read out the sensor to memory at some point to get that preview image. It's just a matter of what resolutions (and bit depths) are available and how fast the camera can write that data to a card.

What format exactly did you use? DNxHR is supposed for resolutions above FullHD apparently and always has 4:2:2 color (which you probably don't need).
I think we should make some tests which bitrate is the best DNxHD for VIMEO upload. There's a huge table on wikipedia that shows which version is for which fps, bitrate and color depth. Makes probably no sense to use the high end one with 10bit color to deliver 8bit material. I think DNxHR might be overkill and one of these middle of the line DNxHD the best tradeoff.
I think it's a bit annoying that there's no ProRes on Windows and no DNxHD on Mac. I heard the non native (reverse engineered?) implementation of the Quicktime codecs is why you can get gamma shifts.

It's all about the codec parameters. They chose file size over detail. They could have made it so that the user could choose.

I'm quite sure that if nx1 could output in 4:4:4 10/12bit, it would sell so many units that samsung could even think about starting again the production :-P 

Another really promising snipet from NX1_packages\standard-arm7\usr\include\wideo\drime5\hdmi\d5_hdmi_video_type.h
 
/**
 * @enum ColorSpace
 * @brief Color space of video stream.
 */
enum ColorSpace {
    HDMI_CS_RGB,/**< RGB color space */
    HDMI_CS_YCBCR444,/**< YCbCr 4:4:4 color space */
    HDMI_CS_YCBCR422/**< YCbCr 4:2:2 color space */
};
/**
 * @enum ColorDepth
 * @brief Color depth per pixel of video stream
 */
enum ColorDepth {
    HDMI_CD_36,/**< 36 bit color depth per pixel */
    HDMI_CD_30,/**< 30 bit color depth per pixel */
    HDMI_CD_24/**< 24 bit color depth per pixel */
};
 
I don't have an external recorder but doesn't the NX1 currently only offer 4:2:2 8 bit out?

Looking at the information found about nx300 hack (the one which disables recording time limit), it seems that one way of doing some hacking would be with a firmware update.
Another way of doing it might be through wifi or connecting the camera to pc with a cable. If it would be possible to enter the camera as a developer/debug mode, maybe some code could be changed right in the camera.
As I understand, that nx1.zip file contains the updated firmware 1.4 which is running on the camera. Now when we have access to it, we can find the parameters, that describe the things we need to change, let's try the bitrate first. I just used search and was able to find many mentions of "bitrate" in the zip along with numbers like "min = 6000000" and "max = 8000000". Don't know what these numbers are for, but that is a start. So we need to find the right numbers and pack them in a new firmware update, like the nx300 hacker did.
Here is a description of that process: https://sites.google.com/site/nxcryptophotography/diy-firmware
And then someone needs to be brave enough to test it :D
 

I downloaded the source code a while ago and looked at it briefly but never found anything but after reading this tread I was inspired to take a second look and I found a whole folder of C++ files in the kernel package under driver\media\drime5\hevc. I even found this comment in one of them( d5_enc_host_ctrl.c).
 
  // Target cycle of 32x32 CU, P-slice
  // Mode1, LD_LC:  870         -- UHD30p @266MHz w/ 20% margin
  // Mode2, LD_HE: 1307         -- FHD60p @200MHz w/ 20% margin
  // Mode3, RA_LC: 1752         -- FHD60p @266MHz w/ 20% margin
  // Mode4, RA_HE: 2420         -- FHD30p @200MHz w/ 20% margin
  // Mode5, AI   :  870         -- UHD30p @266MHz w/ 20% margin
 
Does anyone here know anything about GNU licenses? My thinking is if they are using the drime5 CPU to code and decode HEVC it would need to be built into the Tizen kernel and would need to be open source. But I dont know for sure.
I think its all there folks we just need a Linux/Tizen master to take a look at it.

Finally got a few minutes to do a little "trailer" of the wedding I posted a few pics of a few weeks back, here it is...It was "rushed" because Im really in a very tight schedule lately, hope you guys like it :
Let me know what you guys think !
Ps. I still havent figured out how to render properly, quality is destroyed when I upload it somehow..

did you see the semi-recent thread by kidzrevil about using grain for the web? Rich101 had an interesting post in it, not a hundred percent it works wonders, but he seems to have thought it through
gorgeous btw, love your stuff

Guys, I am developer but being a developer is different than being a hacker. A developer works with tools that give them the functionality they need. A hacker may have to invent tools for platforms where such tools are not readily available. If we had a publically available SDK and a method to sign and upload the firmware onto the NX1 I am sure I could make changes to it.

Shit, that IS doable. Let's start contacting everyone we can and get the lay of the land, so if someone IS interested, we can get fundraising going ASAP.

From reading the NX1 thread on Personal View, it seems Vitali really likes the NX1 ... maybe he might be interested. He doesn't seem like the sort of person who would just do it for the money though. He would only do it if he wanted to do it ... if you get what I mean. Would be interesting to just hear his thoughts on the matter in any case.

Used my MF Nikkors for the first time and am really happy with them. Also used the Vizelex ND Throttle Adapter and happy with that too !! 
EOSHD LOG conversion LUT. OSIRIS Vision X LUT from VisionColor.
Nikon 24/2.8 Ai-S, Nikon 35/2 Ai-S, Nikon 50/1.4 Ai-S, Nikon 105/2.5 Ai-S. Default Gamma DR settings with sharpening set at -10. MBL = 0, 16-235.






 
 

This looks stunning ! Congrats !

Yea I fell in that aperture ring trap once when they only had classic line up. Bought an ZE for sony mirrorless, then jumped to NX1, doomed XD

Never thought I'd say this, but... That pile of dung looks great. 

Additionally, there was nikonhacker.com, pentax-hack.info, nex-hack .com (Sony cameras), and, evidently there is a GoPro hack from CHDK.
 
By the way, the main Magic Lantern developer (A1ex) was originally a contributor to the CHDK project prior to starting ML.  CHDK is still very active, primarily providing extra still photo features to Canon cameras.
 
Of course, there is also the Tragic Lantern fork of ML (which is still used to get All-I frames from the EOSM and the T3i/600D), and the is the existing Samsung NX hack.
 
 
LOL!  Now there's someone who I haven't thought of in several decades.  "Cuchi, cuchi!"

I think this sums up the situation pretty well.

I agree that contacting the Magic Lantern people might be the best bet.
Really there were only ever TWO hacked Camera OS's - Canon by Magic Lantern and GH2 by Vitaliy.
Casey's suggestion of enticing other hackers into it with a bounty might be the other viable option. 

I've never contacted the Magic Lantern people - but I know they ARE contactable. But it ain't gonna come cheap because those are pro's that have already done their time in hacking and have moved on in their lives.
Maybe we could pitch in our money and offer them a private concert by CHARO. That should hook anybody, right?

 

I use some pretty huge glass on the NX1 - Nikkor 28-70 (which people called "the beast" when it came out, but freaking amazing lens), 80-200 2.8, Canon FL 19mm… rails and a lens support are pretty mandatory. Especially if you use a follow focus, still lens mounts aren't made for smooth focus pulls and the frame can shift when you first start moving the focus; adding a little tension at the lens support is the only way I've found to totally lock focus down. You can see one edge of the support just under the AF/MF switch:
 

Stick with the Nikon, which can be adapted to pretty much anything. Get a better Nikon adapter for the NX1.

It will be the same weight, and moment. Unless they redesigned every lens for it's mount (which would make them different lenses) they all have the same distance from the optics to the sensor, so the weight of the adapter is inside the lens housing, and the distance from the front to the sensor is the same, as is the distance from the optics to the sensor, so in the end the moment is the same also. You can adapt nikon to canon, just in case you don't know. If you do so, get a good adapter, I have bad ones an they are terrible.

So the Nikon version is clickless but the canon version isn't? Weird. So, wait... You're gonna get the Ef version and use them on the 5d but not the NX? What will you use with the NX1? Speaking of 5D, have you seen Volker Schmidt's 5D Raw videos? They look great. I think he has one posted on your film grain thread. 

Yeah, they're sick. Can't believe they're jpegs. Good on you. And I thought the Contax Zeiss Planar I got the other week was sharp... Well it is but these new Zeiss are next level. Does the canon version have An aperture ring?

So the phone hacking guys at xda often have "bounties" for various things, like rooting or unlocking a boot loader. That method I think could be very successful for us. We find an arbiter that we trust, maybe kidzrevil since he started the thread, and pool our money into something like venmo, so that people are actually committed. The bounty would be for something specific like "installable firmware that can increase bitrate to 150 Mbps and increase frame rate to 60fps at highest stable bitrate at 4k". People that want that feature pool their money into that. Once real money can be seen, we might see bigger interest from developers. Of course if everyone wanted we could make the bounty for more or less features... My vote would be to keep it pretty realistic at first.

Dang! Those are some sharp ass pics. 
The fur on the leopard and the camel is nuts... Even zoomed in a couple hundred percent. But then I zoomed in on the pelican's feathers and... Whoa!!!
Is that the San Diego Zoo?