Replies: 4 comments 6 replies
-
|
I've encountered this too. I assume the issue is with the Google Lens binary itself (or possibly even just with Lens's OCR altogether), so there's probably not much to do - the only thing I could think of would be to do a second round of OCR through some other method and highlight every subtitle that has a different number of lines between the two. But that seems like overkill. |
Beta Was this translation helpful? Give feedback.
-
|
OK, try to detect of one-liner is wrongly broken: ce1fd4f |
Beta Was this translation helpful? Give feedback.
-
|
@niksedk https://github.com/timminator/Chrome-Lens-OCR/releases/tag/v3.4.0 Nothing about the output should have changed. I made a few performance improvements and added some retry logic if a request fails. Edit: I changed the executable name slightly from chrome-lens-cli.exe to just chrome-lens.exe |
Beta Was this translation helpful? Give feedback.
-
|
@fartle Do you have such an example sup file? I can look into it if the Server Response is just wrong - in which case nothing can be done - or if it is an actual processing issue inside the executable. |
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
-
I was stuck on 4.0.15 and never ventured into the betas still I learned they supported Google Lens. I've been using the beta's and they work great, but I'm having one issue I can't seem to solve. I'll have single lines in the sup that come out as double lines in the conversion. Even short lines like:
[Julia] Hello.
Will convert to:
[Julia]
Hello.
I've played with every setting I can find and can't get stuff like this to stay on a single line. What am I missing?
I'd like the conversion to keep the line assignment/placement identical to the original sup, if possible.
Beta Was this translation helpful? Give feedback.
All reactions