summaryrefslogtreecommitdiffstats
path: root/libass
Commit message (Collapse)AuthorAgeFilesLines
* Add support for font width propertyGrigori Goronzy2015-07-103-7/+19
| | | | | | Add a width field to metadata. This is used for sorting fonts as well. Fixes wrong matches with different width variants in the same font family.
* Use streamed access for memory fontsGrigori Goronzy2015-07-105-30/+70
| | | | | This is faster in many cases, and more suitable for Windows' GetFontData function.
* Pass family name as path for memory fontsGrigori Goronzy2015-07-102-5/+5
| | | | | This is a bit nicer because we can actually see which physical font has been selected for a certain logical font.
* Export font provider interfaceGrigori Goronzy2015-07-105-37/+83
| | | | | | | Add wrapper to the ASS_Renderer to create a font provider from its internal font selector and shuffle some code around to export everything that's needed for font providers to the public. Document font provider functions.
* Memory font supportGrigori Goronzy2015-07-104-51/+98
| | | | | Allow memory fonts with the get_face_data callback. This feature is used for embedded fonts, but can be used by any font provider.
* Make sure font path is validGrigori Goronzy2015-07-101-1/+3
| | | | We do not support memory-based fonts yet, so a path is mandatory.
* Fix weight validity checkGrigori Goronzy2015-07-101-1/+1
|
* Free a provider's fonts when it is freedGrigori Goronzy2015-07-101-25/+65
| | | | | When a provider is freed, iterate the font database, free all fonts that belong to that provider and compact the database afterwards.
* Add convenience defines for slant valuesGrigori Goronzy2015-07-101-0/+3
| | | | | | | | There is no standard scale for slant. This is almost a boolean attribute. However, a font can have a real italic variant, and/or a simple oblique variant. fontconfig's notation supports both of these, so it makes sense to reuse that notation for the sake of flexibility; we might need to differentiate between them.
* oops: remove debug outputGrigori Goronzy2015-07-101-2/+0
|
* Check weight and slant validity in font providerGrigori Goronzy2015-07-101-3/+13
| | | | | When adding a new font, check that weight and slant are valid. If they're not, use reasonable defaults.
* Use TrueType font weight scaleGrigori Goronzy2015-07-105-7/+23
| | | | | | | | | | fontconfig uses an unusual scale from 0-215 for the font weight. It looks like it is somewhat derived from the typographic scale some font families use, but is still rather nonstandard. Nowadays the TrueType scale from 100-900 seems to be standard. CSS uses it, for example. However, most importantly, VSFilter also uses the TrueType scale. So let's use it in libass, too.
* Fix similarity calculationsGrigori Goronzy2015-07-101-2/+2
|
* Add a fixed set of fallback fontsGrigori Goronzy2015-07-101-11/+22
| | | | | Add a small set of fixed fallback fonts, some of them with very wide glyph coverage.
* Don't match any font if there's no glyph coverageGrigori Goronzy2015-07-101-1/+3
| | | | | Do not return a font face at all instead of using the last one. Fixes fallback to the default font path.
* Restore fontconfig runtime configurationGrigori Goronzy2015-07-103-9/+8
| | | | | | | | | | | Pass the fontconfig configuration file option and enable switch through into the font selector. This restores some of the old functionality related to fontconfig. However, the functionality to delay the fontconfig database update will not come back. This is not a big problem. Later it will be possible to manually add the fontconfig provider, which will delay the update in a comparable way.
* Fix compilation without fontconfigGrigori Goronzy2015-07-101-0/+4
| | | | | | Conditionally add the fontconfig provider. We can actually run without fontconfig now! That is, if embedded fonts or fallbacks are good enough.
* Fix off-by-one bug in font matchingGrigori Goronzy2015-07-101-1/+1
|
* Add reference to font provider in font databaseGrigori Goronzy2015-07-101-13/+20
| | | | | | This provides more flexibility than just referencing the callbacks: we can identify the font provider (useful for removing fonts when a provider is freed) and possibly access the font provider private data.
* Improve font selector/provider documentationGrigori Goronzy2015-07-101-5/+41
|
* Convert embedded font handling to a real font providerGrigori Goronzy2015-07-101-33/+55
|
* Add glyph coverage map for embedded fontsGrigori Goronzy2015-07-103-5/+83
| | | | | | Introduce a simple glyph coverage map (created when the font is added) and use it for checking glyph coverage in font selection. This uses a simple linear search at the moment.
* Never add a face twice to an ASS_FontGrigori Goronzy2015-07-104-27/+52
| | | | | | Introduce a unique ID per font face and check it in add_face to make sure we never add a font face twice. This is useful in case the glyph coverage report is unreliable.
* Fix trimming functionGrigori Goronzy2015-07-101-1/+1
| | | | Did not correctly handle empty strings (only whitespace). Whoops.
* Trim spaces of font family stringsGrigori Goronzy2015-07-103-3/+23
| | | | | This adds a trimming utility function that is used for trimming strings of font requests in the font sorter.
* Custom font matching and font sourcesGrigori Goronzy2015-07-1013-563/+733
| | | | | | | Implement a simple font sorter (FontSelector) and an interface to deal with multiple font sources (FontProvider). Unfinished business, but works for the most part. Currently the only implemented FontProvider uses fontconfig.
* Implement cascade gaussian blurDr.Smile2015-07-0410-351/+2525
| | | | | | | | | | That's complete version with SSE2/AVX2 assembly. Should be much faster than old algorithm even in pure C. Algorithm description can be found in this article (PDF): https://github.com/MrSmile/CascadeBlur/releases Close #9
* Fix code path of rasterization through FreeTypeDr.Smile2015-07-011-2/+2
|
* Release 0.12.30.12.3wm42015-06-302-2/+2
|
* Makefile.am: add missing ass_func_template.h to list of sourceswm42015-06-301-1/+1
|
* Switch to virtual function tableDr.Smile2015-06-2611-392/+297
| | | | | | | | | | Use one pointer to table of functions instead of scattered bunch of function pointers. Different versions of these tables can be constructed in compile time. Also, bitmap memory alignment now depends only on SSE2/AVX2 support and is constant for every width. That simplifies code without noticeable performance penalty.
* Improve rasterizer commentsDr.Smile2015-06-263-26/+48
|
* Merge pull request #160 from astiob/beGrigori Goronzy2015-06-233-57/+133
|\ | | | | \be fixes including clipping and value range
| * Make sure the synth tmp buffer is large enough for be_blurOleg Oshmyan2015-02-101-1/+2
| |
| * Use correct types in be_blur_cOleg Oshmyan2015-02-101-6/+5
| | | | | | | | | | | | | | | | Also fix a related sort-of-bug: a multiple of sizeof(uint16_t) was being added to a pointer that already pointed to uint16_t. This was not causing any harm given enough space in the buffer. Fixing the above also lets us combine the two memsets.
| * Add enough padding for \be to avoid clippingOleg Oshmyan2015-02-103-1/+31
| | | | | | | | | | To avoid making bitmaps unnecessarily large, use just the necessary amount of padding for the given \be value.
| * Calculate \be using [0..64] value range (like VSFilter)Oleg Oshmyan2015-02-102-9/+58
| | | | | | | | | | | | | | | | | | | | | | | | | | To avoid banding in the output, the full [0..255] value range is restored before the last \be pass, which then uses the full range and hides the bands by virtue of being a blur. With this, our \be finally closely matches VSFilter's. The only visible difference (other than the lack of banding) is in clipping: we add proper padding and output the whole blurred image, while VSFilter does not add any padding and hence clips the blurred image too early.
| * Apply \be after \blur (like VSFilter)Oleg Oshmyan2015-02-101-14/+14
| |
| * Don't forget to apply \be to the first/last row/column (again)Oleg Oshmyan2015-02-101-29/+26
| | | | | | | | | | The implementation of \be was changed to xy-VSFilter's, which (like VSFilter's) reads but does not write out the first/last row/column.
* | Fix crash when stroked outline overflows SHRT_MAXDr.Smile2015-06-141-1/+1
| |
* | Do not apply ass_set_line_position() to positioned eventswm42015-06-111-3/+4
| | | | | | | | | | Even if we wanted this, the result would be inconsistent if e.g. \clip is used.
* | string2timecode: don't truncate to intOleg Oshmyan2015-06-091-1/+1
| | | | | | | | | | | | | | | | | | The timecode is a long long, but it is computed as a product whose all multiplicands are (unsigned) ints and so effectively has the value of an (unsigned) int. Fix this, and use the full long long range, by explicitly making one of the first two multiplicands a long long. Found by Coverity Scan.
* | Remove several dead storesGrigori Goronzy2015-06-072-7/+4
| | | | | | | | Reported by clang scan-build static analysis.
* | Check possible NULL dereferenceGrigori Goronzy2015-06-071-1/+1
| | | | | | | | | | | | Reported by clang scan-build static analysis. This cannot happen with the current code, but the check might make this more robust in case anything changes.
* | Fix minor memory leak in ass_read_stylesGrigori Goronzy2015-06-071-1/+2
| | | | | | | | | | Reported by clang scan-build static analysis. Also fix incorrect return value in case of error.
* | Strictly clip non-dialog events against the video rectanglewm42015-05-251-0/+13
| | | | | | | | | | | | Only normal dialog lines are allowed to appear outside. Fixes #177.
* | Simplify change_alpha and change_colorOleg Oshmyan2015-05-251-6/+4
| |
* | Apply fade only when the fade alpha is positive (like VSFilter)Oleg Oshmyan2015-05-253-6/+8
| |
* | parse_tag: split \[1-4][ac]Oleg Oshmyan2015-05-251-47/+49
| |
* | Parse and animate all colors and alpha values like VSFilterOleg Oshmyan2015-05-255-61/+135
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Allow exactly one of these prefixes in header values: 0x, 0X, &h, &H. Note that "0x0xFFFFFF" is a correct value, as the first 0x is consumed by the parser and the second by the string-to-number conversion following strtol semantics. * Allow arbitrary numbers of leading & and H (and not h) in any order in override tag values. * Reduce header values modulo 2**32 instead of saturating them to LLONG_MIN/MAX. * Saturate override tag values to INT32_MIN/MAX rather than to LLONG_MIN/MAX. * Don't fiddle with bytes in alpha override tag values. (They can be outside of the 0..255 range.) Also change the byte swapping code to be more sensible. Fixes #80. Fixes #145. Fixes #178. Also fixes our behavior in the case described in https://code.google.com/p/xy-vsfilter/issues/detail?id=80.
* | shaper: purge outdated commentGrigori Goronzy2015-05-241-2/+2
| | | | | | | | | | HarfBuzz has been able to disable fallback kerning since commit 038c98f6. Add some more useful docstrings instead.
* | Fix a wrong commentOleg Oshmyan2015-05-231-1/+1
| |
* | Fix memory leak with drawingswm42015-05-101-1/+6
| | | | | | | | | | | | What. Closes #175.
* | Remove RenderContext.drawingwm42015-05-102-20/+19
| | | | | | | | | | This really didn't make a lot of sense. This is a simplification, and should not affect actual program behavior.
* | Release 0.12.20.12.2wm42015-05-072-2/+2
| |
* | Don't use margins for events that should not be overriddenwm42015-03-162-0/+14
| | | | | | | | | | | | | | libass already does not use the margins for events using \pos. This is not quite complete: there are other tags that we consider as "not dialogue", and which should not be overridden. These tags do not use EVENT_POSITIONED, and thus use the margins, which can mess up rendering.
* | Reorder functionswm42015-03-161-12/+12
| | | | | | | | Just move the *_pos ones about the variants without this postfix.
* | Fix range in rot_keyRodger Combs2015-03-121-1/+1
| | | | | | | | Oops, trig is hard. We output from -pi to +pi now.
* | Fix degrees/radians cache confusion; avoid a fixed-point overflowRodger Combs2015-03-122-5/+5
| | | | | | | | Also fix an incorrect comment
* | Ignore extra coordinates in drawingswm42015-03-091-0/+7
| | | | | | | | | | | | | | | | | | | | | | If there's an odd number of values, ignore the extra value, instead of shifting all values after the next command. While such drawings are boken strictly speaking, VSFilter handles them gracefully, and what libass did before this commit made no sense anyway. Test case: {\an7\pos(0.01,0.7)\c&H5A493D&\p1\iclip(11,m 857379 -744112 l 517759 -744112 517759 -942768 857379 -942768 m 851235 -422238 l 689105 -422238 689105 -620546 851235 -620546 m 679889 -421552 l 517411 -421552 517411 -620894 679889 -620894 -55984 m 860113 425634 l 519459 425634 519459 226640 860113 226640 m 868305 992080 l 465361 992080 465361 793936 868305 793936 m 841343 1317200 l 520145 1317200 520145 1118206 841343 1118206 m 411662 -245762 b 411662 -242373 408918 -239618 405518 -239618 l 342931 -239618 b 339532 -239618 336787 -242373 336787 -245762 l 336787 -308226 b 336787 -311626 339532 -314370 342931 -314370 l 405518 -314370 b 408918 -314370 411662 -311626 411662 -308226 m 414929 -907440 b 414929 -904051 412174 -901296 408785 -901296 l 346198 -901296 b 342798 -901296 340054 -904051 340054 -907440 l 340054 -969904 b 340054 -973294 342798 -976048 346198 -976048 l 408785 -976048 b 412174 -976048 414929 -973294 414929 -969904 m 414417 -585904 b 414417 -582515 411652 -579760 408252 -579760 l 345450 -579760 b 342041 -579760 339286 -582515 339286 -585904 l 339286 -648368 b 339286 -651758 342041 -654512 345450 -654512 l 408252 -654512 b 411652 -654512 414417 -651758 414417 -648368 m 414929 -44997 b 414929 -41597 412174 -38832 408785 -38832 l 346198 -38832 b 342798 -38832 340054 -41597 340054 -44997 l 340054 -107676 b 340054 -111075 342798 -113840 346198 -113840 l 408785 -113840 b 412174 -113840 414929 -111075 414929 -107676 m 415932 261456 b 415932 264845 413178 267600 409788 267600 l 347191 267600 b 343802 267600 341047 264845 341047 261456 l 341047 198992 b 341047 195602 343802 192848 347191 192848 l 409788 192848 b 413178 192848 415932 195602 415932 198992 m 414929 564048 b 414929 567437 412174 570192 408785 570192 l 346198 570192 b 342798 570192 340054 567437 340054 564048 l 340054 501584 b 340054 498194 342798 495440 346198 495440 l 408785 495440 b 412174 495440 414929 498194 414929 501584 m 414929 781136 b 414929 784525 412174 787280 408785 787280 l 346198 787280 b 342798 787280 340054 784525 340054 781136 l 340054 718672 b 340054 715282 342798 712528 346198 712528 l 408785 712528 b 412174 712528 414929 715282 414929 718672 m 414929 1133525 b 414929 1136914 412174 1139669 408785 1139669 l 346198 1139669 b 342798 1139669 340054 1136914 340054 1133525 l 340054 1071061 b 340054 1067661 342798 1064917 346198 1064917 l 408785 1064917 b 412174 1064917 414929 1067661 414929 1071061)}m 0 0 l 1280 0 1280 720 0 720 0 0{\p0}
* | Fix BorderStyle=3 with zero Outline and ShadowDr.Smile2015-03-061-1/+5
| |
* | Make timestamp parsing more lenientwm42015-03-061-1/+1
| | | | | | | | | | | | | | Fixes "[ARR] Musashi no Ken - 01 [AVC][5697986B].ssa", which has timestamps like "00:02:30.85". It starts with 2 zeros instead of one, which probably means it's an invalid file, but it's accepted by various other parsers (VSFilter, MPlayer, vlc, ffmpeg).
* | Prevent selective style overrides with scrollingwm42015-03-061-2/+3
| | | | | | | | Similar to xy-VSFilter.
* | Refine list of tags that prevent selective style overrideswm42015-03-063-6/+9
| | | | | | | | | | | | | | Somewhat stolen from: https://github.com/Cyberbeing/xy-VSFilter/blob/xy_sub_filter_rc3/src/subtitles/RTS.cpp#L2004 (xy-VSFilter started work on this in commit 014da6d9766417d7886eb867c9f2c14038f2a226)
* | Allow more fine grained control over style overrideswm42015-02-264-46/+143
| | | | | | | | | | | | | | | | Add tons of ASS_OVERRIDE_ flags, which control whether certain ASS_Style fields are copied when doing selective style overrides with ass_set_selective_style_override_enabled(). This comes with some cleanup. It should be fully backwards-compatible.
* | Change what fields are overridden with style overridewm42015-02-261-1/+1
| | | | | | | | | | | | | | | | "Bold" should obviously be taken from the script's style, like it's done with StrikeOut and Underline. treat_fontname_as_pattern is specific to the font, and thus should be taken from the same style as the font (the override style).
* | Always use the new style with \r and style overrideswm42015-02-261-6/+6
| | | | | | | | | | | | I don't know why it was done this way, but some fields were always taken from the event's style, instead of the (possibly different) \r style. Undo this, as it seems like an unnecessary complication.
* |