File types changed and will not open and search not finding anything #36
Comments
|
Thank you for your issue. Can you confirm that you're using the newest version of obsidian-ocr, which is currently 2.0.0? |
|
Yes. Everything thing is up to date. Also my obsidian is Version 1.1.12 (Installer 1.1.9)
… On Feb 4, 2023, at 4:12 PM, Jonas Mohr ***@***.***> wrote:
Thank you for your issue. Can you confirm that you're using the newest version of obsidian-ocr, which is currently 2.0.0?
—
Reply to this email directly, view it on GitHub <#36 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEF5454SAKTL2RGINXIGJKTWV3O65ANCNFSM6AAAAAAURHPJ34>.
You are receiving this because you authored the thread.
|
|
Alright, thanks for checking. |
|
I sorted the files alphabetically and see that there is the base .png files and then another file, with the same name with the x.phg.hocr. I hadn’t noticed that before.
Jeff
… On Feb 5, 2023, at 11:17 AM, Jonas Mohr ***@***.***> wrote:
Alright, thanks for checking.
When you say the files have hocr added to the name, do you mean you have a file x.png and also a file x.png.hocr?
—
Reply to this email directly, view it on GitHub <#36 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEF5454MB673SK3LLGN2TQDWV7VFPANCNFSM6AAAAAAURHPJ34>.
You are receiving this because you authored the thread.
|
|
Alright, it's good to hear that the original file is still there, was a bit scared that I screwed something up, and it deleted the files 😌 Concerning the problem you described above: |
|
I opened the OCR search command and typed in a query and got this error in console after pressing return on the search.
<img width="586" alt="Screenshot of Obsidian (2-5-23, 1-50-49 PM)" src="https://user-images.githubusercontent.com/17555063/216848044-e069d05a-d55d-40c4-a1f7-01b678df976f.png">

… On Feb 5, 2023, at 1:49 PM, Jonas Mohr ***@***.***> wrote:
Alright, it's good to hear that the original file is still there, was a bit scared that I screwed something up, and it deleted the files 😌
The .hocr files are remnants of an older version of obsidian-ocr that stored the OCR information for x.png in x.png.hocr.
You can either leave them there and ignore them, or simply delete them.
Since version 2.0.0, the information is stored in a SQLite database, called .obsidian-ocr.sqlite, in the root of your vault.
Concerning the problem you described above:
Could you please open the developer console and see if any errors are reported?
—
Reply to this email directly, view it on GitHub <#36 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEF5455W4RIWOITP35BB74TWWAG4XANCNFSM6AAAAAAURHPJ34>.
You are receiving this because you authored the thread.
|
|
Unfortunately, I can't seem to see the attached image |
|
|
|
Sorry about that was replying by email and image didn't come through. I posted it above. |
|
Alright, thanks for the image. |
|
Sorry, but I a not sure were the the log file gets created and how to find it.
… On Feb 5, 2023, at 5:49 PM, Jonas Mohr ***@***.***> wrote:
Alright, thanks for the image.
Could you please enable Log to file in the settings of obsidian-ocr, restart obsidian and perform the same steps you did to produce the error above.
After that, could you please attach the log file.
—
Reply to this email directly, view it on GitHub <#36 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEF5456NV5LUK24YDZW5ICLWWBDAFANCNFSM6AAAAAAURHPJ34>.
You are receiving this because you authored the thread.
|
|
I found the file. |
|
Thank you for the log. I think I have somewhat of an idea what's going on here. |
|
I am currently running macOS Ventura 13.2 |
|
Okay, and could you tell me the output of |
|
tesseract 5.2.0 |
|
Alright, after looking at the logs I know why it doesn't work, but I don't know why it doesn't work. ...
const execReturn = exec(`tesseract ${this.settings.additionalArguments} "${source}" stdout -l ${this.settings.lang} hocr`);
...This would (as an example) translate into a command like that: The problem is (as can be seen in the log), that tesseract for some reason misinterprets the command, giving the following error message: As can be seen in the error message, tesseract tries to open stdout, -l and eng as files, even though they are just command line arguments, which is quite strange. I can only assume, that there is some sort of problem with the way the file path is handed to tesseract, because when I input the bogus command On the other hand, the file path is wrapped with |
|
I ran the path checks as listed below: |
A number of my png files in my attachment folders have .hocr added to name of file. They will not open now. Additionally, when I invoke the OCR search window, it doesn't find anything. I see when opening Obsidian that the indexing counter finishes.
The text was updated successfully, but these errors were encountered: