You need further Support?
Join us @ the ABBYY OCR Linux Google Group
No, ABBYY CLI OCR V11 will not work with V9/V8 serial numbers, because it is based on a different FineReader Engine (more about ABBYY's OCR SDKs). If you wan to test V11, just request a Trial.
Well, it depends
The major difference is that V11 is now a native 64-Bit application. So if your OS is 64 bit it will probably should work when the minimum system requirements are fulfilled. If you run V9 on a 32-bit OS then V11 will not work.
ABBYY CLI OCR for Linux 11 or V9 can be reinstalled on one and the same computer an unlimited number of times without reactivation. However, if you make major system upgrades, e.g. format your hard drive, or reinstall the operating system, an additional activation may be required.
Situation: I have 2 machines. Local machine and Production machine. I had installed trial licence on my local machine. After obtaining a full licence, I replaced the trial licence with my full licence. I obtained a new production machine and installed my old trial licence on it. After testing everything, my intention was to move the full licence to the production machine.
To do so, I deactivated my full licence on my local machine and tried to activate the full licence on my production machine. The production machine displays 2 licences now → Trial licence and full licence. And the abbyyocr command reflects to the trial licence. I cannot deactivate the trial licence as the number of deactivations is crossed.
/var/lib/ABBYY/SDK/11/Licensesdirectory and remove all the files corresponding to your trial license. These files are prefixed with your trial license number.
Source: Google CLO OCR Group Discussion
The CLI application can only work with one active license file and it is not designed to switch between multiple licences out of the box). If you want to switch between to license files, you have to ensure that the CLI application only uses one active license file (with enough pages on the counter). Below further details that explain changes between V9 and V11:
*.frelfare located in the abbyyocr9 installation directory, by default
The process of exchanging the license file is in almost the same as for V9, but V11 works with a licensing service. So there is a slight difference. Here the instruction for CLI OCR V11 on how to switch between two license files:
*.ABBYY.Licenseare now always located in the
abbyy-fre11-licensing-servicelocated in the abbyyocr11 installation directory (default location
/opt/ABBYYOCR11) by calling the following command in terminal under 'root':
sudo ./abbyy-fre11-licensing-service stop
/var/lib/ABBYY/SDK/11/Licenses directoryand then move in your other license file.
sudo ./abbyy-fre11-licensing-service start
Theoretically yes, but in reality the internal protection scheme restricts that. So virtual machines are not allowed to run the CLI OCR. It has to be used on a real, physical machine.
Why? - ABBYY is concerned about piracy.
Note: Please be aware that a 12.000 pages per year license is not considered as “critical” for a server scenario, because it is less than 33 pages per day . Thus, these are not allowed to be used in virtual machines.
If you plan to use ABBYY CLI OCR in virtualized company server environments, then please contact ABBYY when the order value is bigger than 2.500€ and we will (try to) find a solution.
Technically the CLI OCR could also run in Cloud Data Centers, but…
So if you are planning a project where you need OCR licensing for Cloud, please contact your local ABBYY office.
Some more details on general ABBYY OCR Cloud licensing can be found here:
You would extend your Cloud Service also with OCR, then ABBYY's Cloud OCR Service might be an alternative. The service is simple to integrate, it comes with a REST API and you do not have to care about scalability. More about this topic @ the ABBYY Technology Portal:
Technically, yes. However, the default licensing mechanism of CLI11 does not support its usage in containers. A special licensing is required. If you are going to use CLI in containers, please contact ABBYY to find a suitable licencing solution for your scenario.
Important: If “normal” users can not use the CLI, please check the user rights and test
chmod 755 /var/lib/frengine9/.elf
Right after installation you were shown how to check you license settings:
Note: The serial in the screen shot is just a trial code – if you want to test just request your personal trial license
You can also call
abbyyocr11LM in the terminal – see details in the abbyy 11 - how many pages were executed?
rm –f –R
rm –f /usr/local/bin/abbyyocr
New CLI V11: V11 has a built in option to distribute the pages of a multi-page document over several CPU-Cores you can define how much CPU-resources you want/can 'invest'. Details can be found in the documentation: General: Miscellaneous Keys
The command pattern I used is:
abbyyocr9 -rl German English -if ./input.pdf -f Text -tet UTF8 -of ./ output.txt V11 has to be called with abbyyocr11
Please see below my results:
Result: Parallel processing of 214-page and 213-page PDFs takes ca 50% of the over all of the processing time
To start parallel processing, you should used the following command:
abbyyocr9 -rl German English -if ./Part1.pdf -f Text -tet UTF8 -of ./ Part1.txt & abbyyocr9 -rl German English -if ./Part2.pdf -f Text -tet UTF8 -of ./Part2.txt
As you can see, the results show that total processing time is almost two times smaller in comparison with sequential processing of the entire 427-page PDF if you process both halves of this document in parallel on two cores.
… more to come