luuca
Well-known
hahah, he continues to say that I didn't notice the issue in 10 years of using the camera :bang:
me... that like every enthusiast photographer I did every kind of stupid tests with the camera in my life...
it is very frustrating to live at the opposite of the world of him.
me... that like every enthusiast photographer I did every kind of stupid tests with the camera in my life...
it is very frustrating to live at the opposite of the world of him.
KismetSky
Established
I would not be surprised if one of Kolari's justifications for not working on M9P's and the like (since they use harder to remove coverglass) have to do with the potential for this type of 'damage'. Their strongly worded disclaimer certainly is telling:
"Lastly, some repairs are not possible (or very high risk) because of extremely strong bonding that can not be softened for a safe filter removal. If we find that we can not safely remove your ICF we will stop the repair process, reassemble your camera, notify you, and send it back. (This is the main reason we do not support the Leica M9M, M9-P, and M-E.) "
MaxMax sticks very strongly to his "I only did xxxx" but doesn't seem willing to connect the dots of cause and effect where his 'repair' may have caused damage/misalignment/sensitivity changes to at least one of the two halves.
"Lastly, some repairs are not possible (or very high risk) because of extremely strong bonding that can not be softened for a safe filter removal. If we find that we can not safely remove your ICF we will stop the repair process, reassemble your camera, notify you, and send it back. (This is the main reason we do not support the Leica M9M, M9-P, and M-E.) "
MaxMax sticks very strongly to his "I only did xxxx" but doesn't seem willing to connect the dots of cause and effect where his 'repair' may have caused damage/misalignment/sensitivity changes to at least one of the two halves.
luuca
Well-known
good catch.
you are giving to me many interesting hints that will help me in this dispute
luuca
Well-known
as you can see the defect is clear in normal shots too
luuca
Well-known
my bald head too is cut in half 
(I need to laugh about this... because it's gonna make me crazy...)
yeah, very difficult to notice...
(I need to laugh about this... because it's gonna make me crazy...)
yeah, very difficult to notice...
luuca
Well-known
look what I found:
this is the very last shot I took with the camera before stopping using it, due to glass corrosion
as you can see in the sky there's no central line
this is the very last shot I took with the camera before stopping using it, due to glass corrosion
as you can see in the sky there's no central line
GMOG
Well-known
How much time elapsed between taking that photo and sending the camera to LDP LLC - MaxMax?
Hopefully your credit card company's dispute resolution process gives you ample opportunity and means to present your evidence.
Hopefully your credit card company's dispute resolution process gives you ample opportunity and means to present your evidence.
luuca
Well-known
6 months between the shot with children on the wood and my wonderful selfie
Ko.Fe.
Lenses 35/21 Gears 46/20
So, they took 3000, but didn't told you what cameras are not gong to be usable after "service".
Wow... Dan dude is lucky not to do it with some kind of Russians, yet...
Some smarty on first page mentioned this to be not scam, but nomal.
Hey. Next time your car will need brakes service, they will install some junk, take your money and told you - go make it works with manufacturer.
Wow... Dan dude is lucky not to do it with some kind of Russians, yet...
Some smarty on first page mentioned this to be not scam, but nomal.
Hey. Next time your car will need brakes service, they will install some junk, take your money and told you - go make it works with manufacturer.
I wrote my own software to correct bad scan lines on the M Monochrom. Rather than "just" doing an average of adjacent neighbors, it computes the error introduced by the bad pixel and restores the line. I hate the idea of just throwing away an entire line of the sensor. I modified the code for a Forum members M Monochrom that had the same problem. and also a "HOT" pixel that came in at low ISO. When everyone shot film, serious photographers developed their own. You'd think more digital photographers would write their own software.
Shoot some grey scale cards, look to see if this is a DC offset, or has an intensity component to it. The problem could be corrected in post. Complexity of the algorithm depends on if the difference is a DC offset, linear function with intensity, or has a higher level component to it. Also depends if a difference is required for RGB elements. In Photoshop you could select the dark side of the image and use "Curves" to correct. That will give an idea of error. If the M9 applies the non-uniformity correction on the analog signal, it is probably just a gain and offset.
Nothing 100 lines of Fortran cannot solve. The M Monochrom has the same DNG structure as the M9- meaning the array size is identical. I can take a look. I also have a custom demosaic routine for the M9, so already process RGB pixels. Runs under Windows as a command line batch process, runs through all DNG files on the SD card once it is placed in the computer. Super-busy with work, but if this is something that can be fixed with Fortran- I'd just give the program to Dan for anyone else- if it can correct your images. The forum member sent me some DNG files from his camera to look at. Fixed the problem, needed an extra 8 lines of code.
The alternative is a useless camera.
Shoot some grey scale cards, look to see if this is a DC offset, or has an intensity component to it. The problem could be corrected in post. Complexity of the algorithm depends on if the difference is a DC offset, linear function with intensity, or has a higher level component to it. Also depends if a difference is required for RGB elements. In Photoshop you could select the dark side of the image and use "Curves" to correct. That will give an idea of error. If the M9 applies the non-uniformity correction on the analog signal, it is probably just a gain and offset.
Nothing 100 lines of Fortran cannot solve. The M Monochrom has the same DNG structure as the M9- meaning the array size is identical. I can take a look. I also have a custom demosaic routine for the M9, so already process RGB pixels. Runs under Windows as a command line batch process, runs through all DNG files on the SD card once it is placed in the computer. Super-busy with work, but if this is something that can be fixed with Fortran- I'd just give the program to Dan for anyone else- if it can correct your images. The forum member sent me some DNG files from his camera to look at. Fixed the problem, needed an extra 8 lines of code.
The alternative is a useless camera.
luuca
Well-known
wow.
thanks Sonnar Brian.
I'm not into software to do it by myself.
I don't know what it is a DC offset or a intensity component...
I usually shot film...
can you help me?
what does it means that it can be corrected via software in practice? I donwload the dngs on the pc and run this software before importing them in lightroom?
thanks Sonnar Brian.
I'm not into software to do it by myself.
I don't know what it is a DC offset or a intensity component...
I usually shot film...
can you help me?
what does it means that it can be corrected via software in practice? I donwload the dngs on the pc and run this software before importing them in lightroom?
luuca
Well-known
Some news from MaxMax!!!
he told me he spoke with the programmer of Rawdigger,
he asked to me to send him grey card dng shot from both cameras, to find a software solution.
same thing you say, Sonnar Brian
he told me he spoke with the programmer of Rawdigger,
he asked to me to send him grey card dng shot from both cameras, to find a software solution.
same thing you say, Sonnar Brian
Freakscene
Obscure member
The M9 uses Blackfin 547 and 561 processors and the firmware is XOR encrypted; a decent programmer should be able to fairly easily dig into the firmware and remap the sensor. I did it and I am a neophyte in comparison to Sonnar Brian (should we call him seven-in-three?) in terms of programming.
Marty
A "DC Offset"- means you just add a value to every pixel on right hand side.
A "Gain"- means you also need to multiply the pixel by a value. "Linear" means it is just a simple multiply, one value that does not change. Usually that works. You need a two-point calibration, one grey scale that is closer to black, one grey scale that is closer to white.
I wrote my code to ask for the directory name, read all the files in it, and process all of them. I create a copy of the file- give it a "c" for the first letter in the name- for "corrected". The files open in Lightroom, or any other DNG processor. The files that it processes must be straight out of the camera, not those from Photoshop or anything else.
Most of the code is written already. I used the Watcom Fortran-77 compiler, so it runs from XP to Win10. Most of the complicated code is to read in and parse the DNG file to get to the actual pixels. Adding code to do a non-uniformity correction means swapping out code in one subroutine. I would also offer the code as is to Dan, or if a new version does the trick- he can have that.
I use the same program to compute vignetting, reads in and process the DNG files. SO- Stop down to F8 or so when taking pictures of the grey cards.
I can probably use the same code to compute the corrections.
I've not dug into the firmware on the cameras- that can take some time. What I like about my own code: Much of it was written in the 1980s, when digital imagers were mostly in the R&D phase. Spent the 1980s doing that.
A "Gain"- means you also need to multiply the pixel by a value. "Linear" means it is just a simple multiply, one value that does not change. Usually that works. You need a two-point calibration, one grey scale that is closer to black, one grey scale that is closer to white.
I wrote my code to ask for the directory name, read all the files in it, and process all of them. I create a copy of the file- give it a "c" for the first letter in the name- for "corrected". The files open in Lightroom, or any other DNG processor. The files that it processes must be straight out of the camera, not those from Photoshop or anything else.
Most of the code is written already. I used the Watcom Fortran-77 compiler, so it runs from XP to Win10. Most of the complicated code is to read in and parse the DNG file to get to the actual pixels. Adding code to do a non-uniformity correction means swapping out code in one subroutine. I would also offer the code as is to Dan, or if a new version does the trick- he can have that.
I use the same program to compute vignetting, reads in and process the DNG files. SO- Stop down to F8 or so when taking pictures of the grey cards.
I can probably use the same code to compute the corrections.
I've not dug into the firmware on the cameras- that can take some time. What I like about my own code: Much of it was written in the 1980s, when digital imagers were mostly in the R&D phase. Spent the 1980s doing that.
luuca
Well-known
thanks Brian, I look for a grey card and I send to you the dng of the cameras.
take your time, I'm not pressed anymore...
take your time, I'm not pressed anymore...
Dan
Let's Sway
Now, this ^^ from Brian is worth $3K. MaxMax should take note of how to properly do business!
GMOG
Well-known
I wonder if MaxMax heard from their merchant account about the dispute you filed.
A camera software fix would be ideal! I hope it works out!
I’m in 100% agreement. I’d be livid. Even if true and Leica or someone else can fix it, this key step needs to be told by Dan dude.
oldwino
Well-known
Seems like Dan needs to change his company’s name to MINMIN to more accurately describe the level of customer service.