Peter Galbavy

For now I have added both CRW and THM to .ppignore and doing a full reinstall and fresh index. I hope that once there is time to address this issue...

I was going to dive in a little bit further myself after updating to the latest build (today). I built a test environment (on another server, obv) as per https://docs.photoprism.app/developer-guide/setup/...

There are no pre-converted "large" jpegs, that was just a specultive workaround/test: ```bash peter@ubuntu:/media/hdd1/Pictures/2002/2002-01-02 Dunstable Downs$ ls CRW_8876.CRW CRW_8878.CRW CRW_8880.CRW CRW_8882.CRW CRW_8884.CRW CRW_8886.CRW CRW_8888.CRW CRW_8890.CRW CRW_8892.CRW CRW_8894.CRW CRW_8896.CRW CRW_8876.THM CRW_8878.THM...

OK, before I do that I have found that it's for scanning files in originals, not for uploads. For uploads THM files are correctly ignored, but I mounted a local...

I would imagine it's because of some decision in the flow that says "if the file is already in originals, it cannot be ignored." In fact, now I look deeper...

It is accessing it fine and there were no sidecars files as I originally cleaned everything out and did a complete reinstall early on. For the above test it's a...

"prod" build is "Build 240420-ef5f14bc4" but I can reproduse the problem in "develop" branch from github with the docker env.

Could it be in here? https://github.com/photoprism/photoprism/blob/bb434f718b5eb4377eddc700838dfee57181d05f/internal/photoprism/index_mediafile.go#L288-L297

Will do now - lunchbreak from the day job :-)

OK, I will add code for that too in a moment. I would suggest changing the test in the first "hack" to ```go if !f.IsJpeg() { ... } ```