ttbek

Hey IKSLIM, had I needed to buy a new one for this update I probably would have sold you one, but Luca's kind offer is keeping both with me for now.  Upon closer inspection the  Apurture design version doesn't have the contacts I need camera side, so unfortunately you're out of luck unless I end up acquiring a 3rd one. 

I have been working with a digital logic analyzer and an Arduino nano.  Via this setup I can set the aperture and move the focus to min and max so far.  So the setup is
For gathering data: Canon Camera + EF extension tube with AF contacts + lens, I have wired the extension tube to sample the data via a USB digital logic anlyzer. 
For testing my control: Arduino Nano + EF extension tube with AF contacts + lens (no body for now).  So the aperture and focus max and min are working as controlled by the nano. 
Next step: NX camera + NX extension tube with AF contacts + Arduino Nano  and use the digital logic analyzer to find the focus commands from the camera, also spoof the lens data.  Here is where ihkim's work will be a big help with the lens initialisation, to hopefully successfully spoof the lens in a way the camera accepts. 
Final case: NX camera signal to contacts on close end EF -> NX adapter, these wired to the nano, then from the nano to the contacts on the other side of the adapter, then to the lens.  Then replace the adapter with wired NX-L for focal reduction. 
Stabilization seems to work automatically for the lenses I've tried, but I think the EF-M mount lenses don't have physical switches, but these are not among the lenses we're adapting. 
My 10k offer still stands for anyone that can provide native-like camera driven AF.  The Apurture DEC does not do this, as I understand it doesn't listen to the camera half at all, in which case I'm only a few buttons away from doing the same with the nano (add button to repeat change focus command one way, another the other way, same for aperture).  Wifi would be a bunch of work though, but while nice it isn't on my own wish list.  The nano will allow more programmatic control, 2,3,4, etc... focus locations could be toggled, it's mostly a matter of adding physical inputs and writing logic into the nano code to handle them.  As I look back to your image of the upcoming system, the contacts are going to go just from the Apurture to the lens, I also need to get to the camera contacts somehow.  What I need is camera -> Apurture and Apurture -> lens (but with my nano instead of the Apurture).  With the current NX-L design I'm not sure how to get at the camera contacts, running wires even with a hole drilled through isn't great because of the rotating design, so they can be stressed or break if it rotates too far.  Solutions that come to mind would complicate the design quite a bit further (e.g. concentric rings for each contact on that part that rotates). 
That would be great, can you PM me the address, I didn't keep the packaging they arrived in so I lost the return address. 

I have been working with a digital logic analyzer and an Arduino nano.  Via this setup I can set the aperture and move the focus to min and max so far.  So the setup is
For gathering data: Canon Camera + EF extension tube with AF contacts + lens, I have wired the extension tube to sample the data via a USB digital logic anlyzer. 
For testing my control: Arduino Nano + EF extension tube with AF contacts + lens (no body for now).  So the aperture and focus max and min are working as controlled by the nano. 
Next step: NX camera + NX extension tube with AF contacts + Arduino Nano  and use the digital logic analyzer to find the focus commands from the camera, also spoof the lens data.  Here is where ihkim's work will be a big help with the lens initialisation, to hopefully successfully spoof the lens in a way the camera accepts. 
Final case: NX camera signal to contacts on close end EF -> NX adapter, these wired to the nano, then from the nano to the contacts on the other side of the adapter, then to the lens.  Then replace the adapter with wired NX-L for focal reduction. 
Stabilization seems to work automatically for the lenses I've tried, but I think the EF-M mount lenses don't have physical switches, but these are not among the lenses we're adapting. 
My 10k offer still stands for anyone that can provide native-like camera driven AF.  The Apurture DEC does not do this, as I understand it doesn't listen to the camera half at all, in which case I'm only a few buttons away from doing the same with the nano (add button to repeat change focus command one way, another the other way, same for aperture).  Wifi would be a bunch of work though, but while nice it isn't on my own wish list.  The nano will allow more programmatic control, 2,3,4, etc... focus locations could be toggled, it's mostly a matter of adding physical inputs and writing logic into the nano code to handle them.  As I look back to your image of the upcoming system, the contacts are going to go just from the Apurture to the lens, I also need to get to the camera contacts somehow.  What I need is camera -> Apurture and Apurture -> lens (but with my nano instead of the Apurture).  With the current NX-L design I'm not sure how to get at the camera contacts, running wires even with a hole drilled through isn't great because of the rotating design, so they can be stressed or break if it rotates too far.  Solutions that come to mind would complicate the design quite a bit further (e.g. concentric rings for each contact on that part that rotates). 
That would be great, can you PM me the address, I didn't keep the packaging they arrived in so I lost the return address. 

I have been working with a digital logic analyzer and an Arduino nano.  Via this setup I can set the aperture and move the focus to min and max so far.  So the setup is
For gathering data: Canon Camera + EF extension tube with AF contacts + lens, I have wired the extension tube to sample the data via a USB digital logic anlyzer. 
For testing my control: Arduino Nano + EF extension tube with AF contacts + lens (no body for now).  So the aperture and focus max and min are working as controlled by the nano. 
Next step: NX camera + NX extension tube with AF contacts + Arduino Nano  and use the digital logic analyzer to find the focus commands from the camera, also spoof the lens data.  Here is where ihkim's work will be a big help with the lens initialisation, to hopefully successfully spoof the lens in a way the camera accepts. 
Final case: NX camera signal to contacts on close end EF -> NX adapter, these wired to the nano, then from the nano to the contacts on the other side of the adapter, then to the lens.  Then replace the adapter with wired NX-L for focal reduction. 
Stabilization seems to work automatically for the lenses I've tried, but I think the EF-M mount lenses don't have physical switches, but these are not among the lenses we're adapting. 
My 10k offer still stands for anyone that can provide native-like camera driven AF.  The Apurture DEC does not do this, as I understand it doesn't listen to the camera half at all, in which case I'm only a few buttons away from doing the same with the nano (add button to repeat change focus command one way, another the other way, same for aperture).  Wifi would be a bunch of work though, but while nice it isn't on my own wish list.  The nano will allow more programmatic control, 2,3,4, etc... focus locations could be toggled, it's mostly a matter of adding physical inputs and writing logic into the nano code to handle them.  As I look back to your image of the upcoming system, the contacts are going to go just from the Apurture to the lens, I also need to get to the camera contacts somehow.  What I need is camera -> Apurture and Apurture -> lens (but with my nano instead of the Apurture).  With the current NX-L design I'm not sure how to get at the camera contacts, running wires even with a hole drilled through isn't great because of the rotating design, so they can be stressed or break if it rotates too far.  Solutions that come to mind would complicate the design quite a bit further (e.g. concentric rings for each contact on that part that rotates). 
That would be great, can you PM me the address, I didn't keep the packaging they arrived in so I lost the return address. 

I have been working with a digital logic analyzer and an Arduino nano.  Via this setup I can set the aperture and move the focus to min and max so far.  So the setup is
For gathering data: Canon Camera + EF extension tube with AF contacts + lens, I have wired the extension tube to sample the data via a USB digital logic anlyzer. 
For testing my control: Arduino Nano + EF extension tube with AF contacts + lens (no body for now).  So the aperture and focus max and min are working as controlled by the nano. 
Next step: NX camera + NX extension tube with AF contacts + Arduino Nano  and use the digital logic analyzer to find the focus commands from the camera, also spoof the lens data.  Here is where ihkim's work will be a big help with the lens initialisation, to hopefully successfully spoof the lens in a way the camera accepts. 
Final case: NX camera signal to contacts on close end EF -> NX adapter, these wired to the nano, then from the nano to the contacts on the other side of the adapter, then to the lens.  Then replace the adapter with wired NX-L for focal reduction. 
Stabilization seems to work automatically for the lenses I've tried, but I think the EF-M mount lenses don't have physical switches, but these are not among the lenses we're adapting. 
My 10k offer still stands for anyone that can provide native-like camera driven AF.  The Apurture DEC does not do this, as I understand it doesn't listen to the camera half at all, in which case I'm only a few buttons away from doing the same with the nano (add button to repeat change focus command one way, another the other way, same for aperture).  Wifi would be a bunch of work though, but while nice it isn't on my own wish list.  The nano will allow more programmatic control, 2,3,4, etc... focus locations could be toggled, it's mostly a matter of adding physical inputs and writing logic into the nano code to handle them.  As I look back to your image of the upcoming system, the contacts are going to go just from the Apurture to the lens, I also need to get to the camera contacts somehow.  What I need is camera -> Apurture and Apurture -> lens (but with my nano instead of the Apurture).  With the current NX-L design I'm not sure how to get at the camera contacts, running wires even with a hole drilled through isn't great because of the rotating design, so they can be stressed or break if it rotates too far.  Solutions that come to mind would complicate the design quite a bit further (e.g. concentric rings for each contact on that part that rotates). 
That would be great, can you PM me the address, I didn't keep the packaging they arrived in so I lost the return address. 

Hey IKSLIM, had I needed to buy a new one for this update I probably would have sold you one, but Luca's kind offer is keeping both with me for now.  Upon closer inspection the  Apurture design version doesn't have the contacts I need camera side, so unfortunately you're out of luck unless I end up acquiring a 3rd one. 

I have been working with a digital logic analyzer and an Arduino nano.  Via this setup I can set the aperture and move the focus to min and max so far.  So the setup is
For gathering data: Canon Camera + EF extension tube with AF contacts + lens, I have wired the extension tube to sample the data via a USB digital logic anlyzer. 
For testing my control: Arduino Nano + EF extension tube with AF contacts + lens (no body for now).  So the aperture and focus max and min are working as controlled by the nano. 
Next step: NX camera + NX extension tube with AF contacts + Arduino Nano  and use the digital logic analyzer to find the focus commands from the camera, also spoof the lens data.  Here is where ihkim's work will be a big help with the lens initialisation, to hopefully successfully spoof the lens in a way the camera accepts. 
Final case: NX camera signal to contacts on close end EF -> NX adapter, these wired to the nano, then from the nano to the contacts on the other side of the adapter, then to the lens.  Then replace the adapter with wired NX-L for focal reduction. 
Stabilization seems to work automatically for the lenses I've tried, but I think the EF-M mount lenses don't have physical switches, but these are not among the lenses we're adapting. 
My 10k offer still stands for anyone that can provide native-like camera driven AF.  The Apurture DEC does not do this, as I understand it doesn't listen to the camera half at all, in which case I'm only a few buttons away from doing the same with the nano (add button to repeat change focus command one way, another the other way, same for aperture).  Wifi would be a bunch of work though, but while nice it isn't on my own wish list.  The nano will allow more programmatic control, 2,3,4, etc... focus locations could be toggled, it's mostly a matter of adding physical inputs and writing logic into the nano code to handle them.  As I look back to your image of the upcoming system, the contacts are going to go just from the Apurture to the lens, I also need to get to the camera contacts somehow.  What I need is camera -> Apurture and Apurture -> lens (but with my nano instead of the Apurture).  With the current NX-L design I'm not sure how to get at the camera contacts, running wires even with a hole drilled through isn't great because of the rotating design, so they can be stressed or break if it rotates too far.  Solutions that come to mind would complicate the design quite a bit further (e.g. concentric rings for each contact on that part that rotates). 
That would be great, can you PM me the address, I didn't keep the packaging they arrived in so I lost the return address. 

I have been working with a digital logic analyzer and an Arduino nano.  Via this setup I can set the aperture and move the focus to min and max so far.  So the setup is
For gathering data: Canon Camera + EF extension tube with AF contacts + lens, I have wired the extension tube to sample the data via a USB digital logic anlyzer. 
For testing my control: Arduino Nano + EF extension tube with AF contacts + lens (no body for now).  So the aperture and focus max and min are working as controlled by the nano. 
Next step: NX camera + NX extension tube with AF contacts + Arduino Nano  and use the digital logic analyzer to find the focus commands from the camera, also spoof the lens data.  Here is where ihkim's work will be a big help with the lens initialisation, to hopefully successfully spoof the lens in a way the camera accepts. 
Final case: NX camera signal to contacts on close end EF -> NX adapter, these wired to the nano, then from the nano to the contacts on the other side of the adapter, then to the lens.  Then replace the adapter with wired NX-L for focal reduction. 
Stabilization seems to work automatically for the lenses I've tried, but I think the EF-M mount lenses don't have physical switches, but these are not among the lenses we're adapting. 
My 10k offer still stands for anyone that can provide native-like camera driven AF.  The Apurture DEC does not do this, as I understand it doesn't listen to the camera half at all, in which case I'm only a few buttons away from doing the same with the nano (add button to repeat change focus command one way, another the other way, same for aperture).  Wifi would be a bunch of work though, but while nice it isn't on my own wish list.  The nano will allow more programmatic control, 2,3,4, etc... focus locations could be toggled, it's mostly a matter of adding physical inputs and writing logic into the nano code to handle them.  As I look back to your image of the upcoming system, the contacts are going to go just from the Apurture to the lens, I also need to get to the camera contacts somehow.  What I need is camera -> Apurture and Apurture -> lens (but with my nano instead of the Apurture).  With the current NX-L design I'm not sure how to get at the camera contacts, running wires even with a hole drilled through isn't great because of the rotating design, so they can be stressed or break if it rotates too far.  Solutions that come to mind would complicate the design quite a bit further (e.g. concentric rings for each contact on that part that rotates). 
That would be great, can you PM me the address, I didn't keep the packaging they arrived in so I lost the return address. 

I have been working with a digital logic analyzer and an Arduino nano.  Via this setup I can set the aperture and move the focus to min and max so far.  So the setup is
For gathering data: Canon Camera + EF extension tube with AF contacts + lens, I have wired the extension tube to sample the data via a USB digital logic anlyzer. 
For testing my control: Arduino Nano + EF extension tube with AF contacts + lens (no body for now).  So the aperture and focus max and min are working as controlled by the nano. 
Next step: NX camera + NX extension tube with AF contacts + Arduino Nano  and use the digital logic analyzer to find the focus commands from the camera, also spoof the lens data.  Here is where ihkim's work will be a big help with the lens initialisation, to hopefully successfully spoof the lens in a way the camera accepts. 
Final case: NX camera signal to contacts on close end EF -> NX adapter, these wired to the nano, then from the nano to the contacts on the other side of the adapter, then to the lens.  Then replace the adapter with wired NX-L for focal reduction. 
Stabilization seems to work automatically for the lenses I've tried, but I think the EF-M mount lenses don't have physical switches, but these are not among the lenses we're adapting. 
My 10k offer still stands for anyone that can provide native-like camera driven AF.  The Apurture DEC does not do this, as I understand it doesn't listen to the camera half at all, in which case I'm only a few buttons away from doing the same with the nano (add button to repeat change focus command one way, another the other way, same for aperture).  Wifi would be a bunch of work though, but while nice it isn't on my own wish list.  The nano will allow more programmatic control, 2,3,4, etc... focus locations could be toggled, it's mostly a matter of adding physical inputs and writing logic into the nano code to handle them.  As I look back to your image of the upcoming system, the contacts are going to go just from the Apurture to the lens, I also need to get to the camera contacts somehow.  What I need is camera -> Apurture and Apurture -> lens (but with my nano instead of the Apurture).  With the current NX-L design I'm not sure how to get at the camera contacts, running wires even with a hole drilled through isn't great because of the rotating design, so they can be stressed or break if it rotates too far.  Solutions that come to mind would complicate the design quite a bit further (e.g. concentric rings for each contact on that part that rotates). 
That would be great, can you PM me the address, I didn't keep the packaging they arrived in so I lost the return address. 

Hey IKSLIM, had I needed to buy a new one for this update I probably would have sold you one, but Luca's kind offer is keeping both with me for now.  Upon closer inspection the  Apurture design version doesn't have the contacts I need camera side, so unfortunately you're out of luck unless I end up acquiring a 3rd one. 

Well, moving money to the smartphone department should be good for the cameras, since they've been in the same merged department since 2013 http://www.theverge.com/2013/12/13/5206560/samsung-merges-camera-and-mobile-divisions  But I assume that they have also been putting the money towards phones even within the department :P   

Giving -200 error when I try to upload my jpeg, trying to use a lower jpeg quality to see if the smaller file size lets it upload.  Hmm, no luck, says "There was a problem processing the uploaded file. -200"  I have no idea what the problem is.  Other files from the 5DSR also don't seem to be working.  Well, just uploaded a 400mm f/2.8 shot to DeviantArt, no appreciable vignetting: http://ttbek.deviantart.com/art/Tiny-Rocket-658531277?ga_submit_new=10%253A1484922555
Hmm, now two Samsung files are having the same problem with uploading, weird, at least the first two here worked though.  What I'm showing here is the slight play in the rotating section, it can be pulled slightly out or be slightly more in, first shot is out (5725) and the second is in (5726).  My Samyang 12mm's back element does something similar, not sure if it is supposed to be like that, maybe I'll open it up and see if I can tighten it.  It seems to be the same on both NX-L adapters.  I don't know if it is optically of concern or not, I think probably not, unless maybe if it shifts on you after you focus or something? 

Sorry for the delay, good to hear you have a solution, if you know anyone with a longer lens or a store that has one, maybe you could please test on a 600 or 800 lens.  Here are the images with the 1st version NX-L attached.  5707:Canon 400mm f/2.8 IS L version one,  5708:Sigma 150-600 Sport @150mm, 5709:Sigma 150-600 Sport @600mm, 5710:Tamron 75-300 Vi DC?...mumbo jumbo the latest one @75mm, 5712:Tamron 75-300@100mm, 5713:Tamron 75-300@135mm, 5714:Tamron 75-300@200mm, 5715:Tamron 75-300mm@300mm, 5716:Canon 400mm f/5.6 L.  
5722:Sigma 50mm f/1.4 Art glassless adapter, 5723:Sigma 50mm f/1.4 Art with NX-L  Focus is on front edge of the door, sharpness is retained quite well. Vignetting is much worse in the NX-L shot, but in this case it is in my opinion just from seeing more of the image circle here, though I should double check against a FF body just in case.  It's just vignette, not so much like the total corner blackout on the telephotos. 
Hmm, having trouble uploading my shot of the 400 f/5.6 on the 5DSR.  Maybe file/size limit per post, will retry in a separate post. 
 

+10000
And kudos to DXO for giving us this. At least we have a good understanding of performance sensor. I verified their measurement in real world with every camera I owned. 
Cross their results with the Dpreview image comparison tool for ISO and DR and it matches well. 
I don't understand your frustration Andrew.

Dxo marks always been like that. 
It's not THE reference ..it's only a reference for those who actually know how to read the graphs and analyse some of the results. Overall score means as much as saying that the sky is blue. 

I do agree that DXO's rankings are a bit questionable, but not too far off.  There are generally valid explanations of the issues you cited:
NX500 over 5DS and NX1:  I've personally handled 5DSR files, and can say that the IQ is terrible. Even Canon stated not to expect much more than their old APS-C cameras in the IQ department.  I've read a few times that the NX500 is considered to have higher IQ than the NX1.  By how much, I don't know.  But viewing test RAWs of the NX1, I'd say DR and high ISO are around 1/2 stop behind the Nikon D7200.
  DXO One:  Its Super RAW literally is super.  It takes 4 RAW files, stacks them, and averages out the noise.  The difference is dramatic.  While the detail level isn't the best at high ISO, the lack of noise is well beyond FF capability.  This is similar to Olympus' high res RAW mode, but instead of increasing resolution, it reduces noise and increases detail at the same output size.
  D3X over D5:  The D5 is a bomb below ISO 1600, nearly matching the 5D III.  Even crop sensors beat it.  The sensor is tuned for mid/high ISO performance, though current technology only goes so far.  The gains, while there (+1/2 stop vs 1DX II), really aren't worth the trade off for the flexibility in low ISO RAW.  Worthy of note is that the D3X has a Sony sensor, while the D5 is Nikon's own creation.
  D600 over 1DX II and P40+:  It's true.  The D600 kills the 1DX II in DR at base ISO, and at worst, ties it the rest of the way up.  the 1DX II literally has years-old crop sensor performance in that area, despite Canon's massive gain in their new generation of sensors.  High ISO is also neck and neck.

Vs the P40+, the sensor in the MF camera is quite old.  Despite having the resolution advantage, it loses out in DR and high ISO by quite a big margin.  By ISO 1600, colors turn to mush, which doesn't really happen on the D600 at any ISO.
  D3s and D700:  I've also worked with files from a D700 multiple times, and can say that yes, its sensor is outdated at this point.  It's competitive with today's crop sensor cameras (minus Canon's) at best.  The A7S/II sensor has been compared to current medium format in its DR and ability to reproduce color. 

Once again, the D3s/D700's sensor is Nikon's own.  Nikon isn't very competitive when it comes to sensors, and probably had its best attempt at competing with Sony in the D4/s/f.  All of the rest of their sensors just don't stand out, though aren't as bad as Canon's. I have a feeling that resolution plays a big part in DXO's rankings.  If you downscale the A7R II's files to A7S II size, they will certainly have an advantage in their "Sports" rating. It might also be why the A7R II beats the D810, when the D810 clearly has about 1/3 stop advantage at high ISO.  My friend tested 2x A7R IIs before returning them and keeping his D810.  #IQsnob.
For DR and high ISO, they test noise up to a certain amount.  How they get to that amount, who knows, but it's a cutoff point they chose that represents the transition from "OK" noise to offensive noise.  So while sensors may have DR response up to a certain amount of stops, after a point, it becomes wiser to turn things back a bit in software.  Where that happens is up to the user, as it's a more subjective choice.
And "Color" is more about correctly reproducing color in RAW than how the final JPG is rendered.  Color in the Canon sense is highly subjective.  Color against a known testing scene/chart isn't.

DXO has their explanations.
https://www.dxomark.com/About/Sensor-scores/Overall-Score
 
https://www.dxomark.com/About/Sensor-scores/Use-Case-Scores
Low light score in particular is an actual ISO and I think the easiest to explain.
"Sports & action photography: Low-Light ISO
Unlike the two previous scenarios in which light is either generous (studio) or stability is assured (landscape), photojournalists and action photographers often struggle with low available light and high motion. Achieving usable image quality is often difficult when pushing ISO.
When shooting a moving scene such as a sports event, action photographers’ primary objective is to freeze the motion, giving priority to short exposure time. To compensate for the lack of exposure, they have to increase the ISO setting, which means the SNR will decrease. How far can they go while keeping decent quality? Our low-light ISO metric will tell them.
The SNR indicates how much noise is present in an image compared to the actual information (signal). The higher the SNR value, the better the image looks, because details aren't drowned by noise. SNR strength is given in dB, which is a logarithmic scale: an increase of 6 dB corresponds to doubling the SNR, which equates to half the noise for the same signal.
An SNR value of 30dB means excellent image quality. Thus low-light ISO is the highest ISO setting for a camera that allows it to achieve an SNR of 30dB while keeping a good dynamic range of 9 EVs and a color depth of 18bits.
A difference in low-light ISO of 25% represents 1/3 EV and is only slightly noticeable.
As cameras improve, low-light ISO will continuously increase, making this scale open."
 
It has nothing to do with AF etc so I think the sports scores are pretty reasonable maybe more so if you just consider them as low light rather than sports and remember it is based on their criteria.       I am fine with using an A7s for night time sports.      I use an old manual focus 300 2.8 anyway so it just means I can use a higher shutter speed.     None of the shots would be printed huge so 12mp is fine.
A modern FF DSLR would be a better sports CAMERA most of the time but does it have a better sports SENSOR (given DXOmarks criteria)?
The overall scores are a bit based on voodoo as the bits that go into that are subjective without full explanation as to weighting.
I think some of the anomalies might be because of a low number of samples tested given many cameras get slightly different scores with the same sensors.      A slight difference might be just enough to take a camera a bit over or a bit under their marks.     I don't think the A7s is any noisier than the A7sii and It seems the colour depth might be why the A7sii gets a lower score for low light (the point they cross 18 bits for colour sensitivity).
For video it is all a bit silly though as they are only testing RAW stills and most video is Jpeg.
I would love to see a site test sensors for video.    RAW and otherwise.
 

Double checked again without the lens hoods, it doesn't start suddenly but starts becoming noticeable around 150mm on my Tamron 70-300. By 300 it is clear and obvious, on the 400 f/5.6 the corners become almost completely dark.  Different lens designs may make it show more or less, for example it definitely shows less on the 400 f/2.8 than on the 400 f/5.6.  I'll try to post sample pics sometime later today. 

Well... some bad news, the source I got 29mm from seems to be a typo, it seems the flange is only 20mm, which is still more than M mount, but that is very little space for the adapter.  It will definitely have vignetting, lots of it ^_^.  Maybe not too bad at some focal lengths though, not sure on that.  When I'm back home I'll check out the protocol as best I can, no need putting in any time until I do that.  Maybe the chip won't even be working, the camera shop I got it from had nothing to try it out on. 
The NX-Ls have arrived ^_^.  Unfortunately they came through Q-post on this end, but luckily my brother was still home and was able to pick them up for me, only made it by like two days as he is flying here tomorrow.  I asked him to bring one with him so I'll get to use it on this vacation ^_^. 

Well... some bad news, the source I got 29mm from seems to be a typo, it seems the flange is only 20mm, which is still more than M mount, but that is very little space for the adapter.  It will definitely have vignetting, lots of it ^_^.  Maybe not too bad at some focal lengths though, not sure on that.  When I'm back home I'll check out the protocol as best I can, no need putting in any time until I do that.  Maybe the chip won't even be working, the camera shop I got it from had nothing to try it out on. 
The NX-Ls have arrived ^_^.  Unfortunately they came through Q-post on this end, but luckily my brother was still home and was able to pick them up for me, only made it by like two days as he is flying here tomorrow.  I asked him to bring one with him so I'll get to use it on this vacation ^_^. 

Well... some bad news, the source I got 29mm from seems to be a typo, it seems the flange is only 20mm, which is still more than M mount, but that is very little space for the adapter.  It will definitely have vignetting, lots of it ^_^.  Maybe not too bad at some focal lengths though, not sure on that.  When I'm back home I'll check out the protocol as best I can, no need putting in any time until I do that.  Maybe the chip won't even be working, the camera shop I got it from had nothing to try it out on. 
The NX-Ls have arrived ^_^.  Unfortunately they came through Q-post on this end, but luckily my brother was still home and was able to pick them up for me, only made it by like two days as he is flying here tomorrow.  I asked him to bring one with him so I'll get to use it on this vacation ^_^. 

Good stuff, is it just me or is the bokeh actually a bit smoother with the NXL?  Video sharpness is definitely living up to at least 4k, and Luca's post a bit earlier shows it is just about at the limits of what that lens can do without the NXL, looking good.  Is mine in the mail?  :P

Hey Luca, finally received email due to end of fundraising directing me to profile page to enter address (https://www.produzionidalbasso.com/account/edit-profile) I entered my phone number in the same line as the street address.   I will be going for vacation on December 15th, so if it arrives between the Dec. 15th and January 20th or so then I will not be able to receive it and they will probably ship it back to you.  If it is without the phone number they will also ship it back to you as they will not be able to reach me so that I can collect the package.  ... I have been waiting until the start of the next year to get a PO box to receive with them because they charge for a whole calender year regardless of when you get it (e.g. so if I got it now it would be only for 2 months and I would pay for the entire year).  This is if your are sending via normal mail that arrives at the post office, some others through FedEx and DHL can deliver to the home depending on the class/type of mail service requested.  Sorry for the complicated shipping situation. 
Kisaha, I'm looking forward to it as well. 

Hey Luca, finally received email due to end of fundraising directing me to profile page to enter address (https://www.produzionidalbasso.com/account/edit-profile) I entered my phone number in the same line as the street address.   I will be going for vacation on December 15th, so if it arrives between the Dec. 15th and January 20th or so then I will not be able to receive it and they will probably ship it back to you.  If it is without the phone number they will also ship it back to you as they will not be able to reach me so that I can collect the package.  ... I have been waiting until the start of the next year to get a PO box to receive with them because they charge for a whole calender year regardless of when you get it (e.g. so if I got it now it would be only for 2 months and I would pay for the entire year).  This is if your are sending via normal mail that arrives at the post office, some others through FedEx and DHL can deliver to the home depending on the class/type of mail service requested.  Sorry for the complicated shipping situation. 
Kisaha, I'm looking forward to it as well. 

Eeeh?  Even for Metabones 10k is chump change.  10k won't get you a single good developer for 6 months.  I'm certain that at least a few people worked for quite some time on that.  That said, progress would be much faster if I had a 40 hour week to work on this instead of maybe a handful of hours every other weekend or so.