Thank’s I’ll try that when i get home from work.
Didn’t work, the camera name in the lens correction module changed to “generic crop sensor (2.00x)” but still no noise profile in the denoise module
Is that actually the path to your newly generated presets.json file?
This is peculiar! It works just fine on my machine.
Here are the steps I took:
- Download sample YI M1 file, like this one
- Fetch your presets.json from post above
- Change your maker to XIAOYI (as per above)
- Since the modified presets.json is in my current directory, I start darktable in this way
/opt/darktable/bin/darktable --noiseprofiles ./presets.json - I navigate to the sample file that I downloaded in step 1, open it in darkroom, select the correction group tab and expand module denoise (profiled). Success!
Now, there is another thing that bothers me… I suspect that my sample image and your images do not report maker in the same way! Your dump (above) reports maker YI TECHNOLOGY. My sample reports maker XIAOYI.
Isn’t life puzzling?
Have fun!
Claes in Lund, Sweden
@Claes interesting. I’ll try it with the sample wwhen I get home. Also, I suspect the difference in maker may be due to the DPReview samples being taken with early firmware, while I’m on the latest one.
This sounds strange. Why would the lens correction module change when editing the noise profile data? What exactly did you do to change the maker?
I’ve changed the maker field in pretests.json to YI TECHNOLOGY as that is what is reported in my DNG file.
Here is my presets.json:
{
"version": 0,
"noiseprofiles": [
{
"maker": "YI TECHNOLOGY",
"models": [
{
"comment": "m1 contributed by mica@silentumbrella.com",
"model": "M1",
"profiles": [
{"name": "M1 iso 100", "iso": 100, "a": [1.10711453293077e-05, 4.5553049100813e-06, 1.00316690340124e-05], "b": [-4.13243840571984e-10, 9.05781134283873e-09, 3.41324581919006e-08]},
{"name": "M1 iso 200", "iso": 200, "a": [1.10476862785712e-05, 4.55166027805942e-06, 9.61731856173001e-06], "b": [1.71033267821898e-08, 1.26022105005497e-08, 2.78265979780639e-08]},
{"name": "M1 iso 400", "iso": 400, "a": [2.1431686899096e-05, 8.68606734792238e-06, 1.833514118073e-05], "b": [2.13227367322229e-08, 2.61654826555548e-08, 6.34335556927895e-08]},
{"name": "M1 iso 800", "iso": 800, "a": [4.10928259840626e-05, 1.68942240848889e-05, 3.56925638897857e-05], "b": [6.83307060087334e-08, 5.88159491597772e-08, 1.27285727863453e-07]},
{"name": "M1 iso 1600", "iso": 1600, "a": [8.13184188347158e-05, 3.34187840992974e-05, 7.26354852980862e-05], "b": [1.93897140543902e-07, 1.5257620830091e-07, 2.42951564559548e-07]},
{"name": "M1 iso 3200", "iso": 3200, "a": [0.000167691097936184, 6.80753718157227e-05, 0.000148687911877462], "b": [4.34429630877549e-07, 4.15445996975158e-07, 4.43719759326219e-07]},
{"name": "M1 iso 6400", "iso": 6400, "a": [0.000356457116722712, 0.000147588142592895, 0.000311292370801957], "b": [8.55254329452434e-07, 9.74046195035361e-07, 7.16209612055463e-07]}
]
}
]
}
]
}
The profiled denoise should be added in 2.6 for the Yi M1.
sweet, thanks
My version above is missing the two highest isos, I will update it today.
Don’t be so pessimistic 
That’s what the bug report said last time I looked at it 
I’ve already added it to my json file locally. It is working well.
Hi, @paperdigits.
Sorry for the OT, but I would to know your thoughts after some time using this nice little camera.
I have a Canon EOS 1100d, not an high end model, do you think that changing to yi m1 would be a mistake, or quality is not so bad?
This while I’m trying to find a good offer for a 1st mark of Sony alpha7
Hi @Dario_M,
I like this little camera pretty well. I recently went to Mexico for 3 weeks and it was my only camera. Obviously the size is great for travel. I had heavily considered a Sony, but I hate Sony software and they always seems to be doing something strange (memory stick, star eating, bizarre file formats historically) so I passed on the Sony.
I aimed for this camera to replace my phone camera, which is horrible.
The down points of this camera, in my opinion are:
- no on-board flash (it has a standard hotshoe though)
- focusing misses some times
- kit zoom lens is soft (though sort of expected for a kit lens at this price)
- on long exposures, especially many long exposures, the sense noise and hot pixels are bad
- no view finder, it’s the touch screen on the back
- I can’t get the time lapse to change the exposure, but this could be user error
The good:
- wow, compact and tiny, especially with the tiny, prime lens I have on it
- 20MP is lots of megapixels, better than anything else at the price point
- great in daylight into the evening
- 4K video
- time lapse shoots to video or raw stills
- battery can be changed
- charges over micro USB, so I can use my phone charger
- Yi has put a a lot of firmware updates, so they are actively trying to improve this camera, which is nice
Ultimately, I had $100 in amazon points, which made this a super cheap purchase. It’s hard to argue with the price point.
1 Like
Perfect, thanks.
If you have any specific questions or want some specific (within reason) sample from the camera, please don’t hesitate to ask.
Thanks. I would like to understand if it could be an upgrade from eos 1100d in term of quality of raw.
1100d is not one of the best camera especially at iso above 400.
Even if equally performing, m1 could be a choice, for the weight.
I’m going to go out on a limb here and say that yes, quality of raw is probably better. Note that it’ll depend completely on what lens you’re using, because if the lens is soft, then the image is soft. But the 1100D came out in 2011, and I think sensor tech as made quite a few strides in the last ~6 years (the M1 is a year or two old at this point).
I can certainly provide you some high ISO samples, if that’d help. I think it is pretty usable at ISO 800.