mirror of
https://github.com/CCExtractor/ccextractor.git
synced 2026-02-03 21:23:48 +00:00
Version 0.85 became much slower #246
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @maxkoryukov on GitHub (Jan 15, 2017).
As a result of latest few commits the current version (in master branch) works much slower ( x10 ):
this is a result of handling
BBC_NEWS_2016-06-21.tsfrom sample-videos. Previously it took about 0:57 (about one minute) for this file.PS: I have disabled my sbs feature for this speed test.
@maxkoryukov commented on GitHub (Jan 15, 2017):
I see, that CCE output now contains
<font>tags for most subtitles. This is the only one difference I see, being a consumer of CCE))))@cfsmp3 commented on GitHub (Jan 16, 2017):
What happens with -nodvbcolor ?
On Sun, Jan 15, 2017 at 3:40 PM, Maksim Koryukov notifications@github.com
wrote:
@maxkoryukov commented on GitHub (Jan 16, 2017):
@cfsmp3 ,
-nodvbcolorworks as expected (I think so), ccextractor with this option gives pure subs, without<font>(I use this for SBS // sentence-split feature), but even with-nodvbcolorccextrator 0.8.5 works at the same speed - 10 minutes for 10 minute movieI have tested only on my laptop, I didn't run/build ccextractor on other hosts.
@cfsmp3 commented on GitHub (Jan 16, 2017):
dvdcolor being the default is correct, but of course if sbs doesn't support
colors you can just turn colors off automatically with -sbs.
About speed, is this a windows or linux build?
In windows we now have tesseract 4 which seems a lot slower than 3...
On Sun, Jan 15, 2017 at 5:12 PM, Maksim Koryukov notifications@github.com
wrote:
@maxkoryukov commented on GitHub (Jan 16, 2017):
I am on linux.
I've downloaded the latest commits from master branch, and build it with
/linux/buildscript.@cfsmp3 commented on GitHub (Jan 17, 2017):
Seems like it's tesseract. @izaron is in charge of that - for now we'll
revert back to t3 as default.
On Mon, Jan 16, 2017 at 10:23 AM, Maksim Koryukov notifications@github.com
wrote:
@Izaron commented on GitHub (Jan 18, 2017):
Yes I saw that Tess 4.0 is slower because of new algorithm, and I'll solve it (change accuracy settings/downgrade to old .lib files and waiting for stable 4.0) But it's for Windows. @maxkoryukov can you check your tesseract version? As far I know, current
tesseract-ocr-devfrom Debian/Ubuntu have version3.0.4or3.0.5. Or you installed library from sources?@maxkoryukov commented on GitHub (Jan 18, 2017):
@Izaron
As I remember, installed with
apt-get, not from sources.