Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
|
|
Thread Tools | Search this Thread | Display Modes |
22nd September 2011, 19:12 | #41 | Link |
eccentric
Join Date: Jan 2011
Posts: 24
|
Code:
* Version 0.24.1: binary: - updated libass to current git HEAD - switched Harfbuzz to libass’ compatibility branch - compiled Harfbuzz without Uniscribe backend fixes lots of crashes and misbehavior Download |
20th April 2012, 08:51 | #42 | Link |
eccentric
Join Date: Jan 2011
Posts: 24
|
Code:
* Version 0.25: - code restructured - added support for the BT.709 color space and the “Video Colorspace” property that has been introduced with recent versions of Aegisub. binary: - updated everything, switched to MinGW-w64 (same toolchain as mplayer2 now) Download |
20th April 2012, 15:08 | #43 | Link |
Registered User
Join Date: Dec 2002
Posts: 5,565
|
Thx, but has a final agreement been reached on how to add "Video Colorspace"/color correction info to ASS scripts? I think ASS renderers should hold on implementing these until a final decision has been made. From the discussions on the xy-vsfilter google code site (issue 40), it seems that this may be subject to change until Aegisub 3.0.0 stable is released.
|
20th April 2012, 17:47 | #44 | Link |
eccentric
Join Date: Jan 2011
Posts: 24
|
Well, this is just used for convenience in an attempt to automatically choose the correct color space for the video, and it’s trivial to change too. AssRender will just follow whatever Aegisub is doing.
It’s is much more important for playback software, but there the right way to go is to stop rendering the subtitles onto the video surface and instead handle the subtitles separately, without requiring color space conversion or scaling (like what mplayer2 is doing in its EOSD code with renderers that support it, e.g. gl, gl3, direct3d and vdpau), which eliminates the issue entirely. |
20th April 2012, 17:59 | #45 | Link | ||
Registered User
Join Date: Dec 2002
Posts: 5,565
|
Quote:
Quote:
Anyways, assrender 0.25 does not work correctly at this point. To emulate vsfilter behavior (and the definition of the current "Video Colorspace" tag) one would have to set "Video Colorspace" to "BT.601", but this results in totally wrong colors at the moment. It would be better to revoke that feature for the time being. |
||
20th April 2012, 23:13 | #46 | Link | |
Registered User
Join Date: Mar 2012
Posts: 10
|
Quote:
|
|
21st April 2012, 21:05 | #47 | Link | |
eccentric
Join Date: Jan 2011
Posts: 24
|
…is not the point of this feature. The point is to use the *correct* color matrix (i.e. the one used by Aegisub) for overlaying the subtitles.
Quote:
The problem with those files is just that they always assume BT.601 colorspace, since Aegisub made the same mistake for a very long time. Playback software that gives a shit would just have to convert the colors for files which do not have the Video Colorspace property. Last edited by Guest; 7th June 2012 at 21:28. Reason: rule 4 |
|
22nd April 2012, 11:14 | #48 | Link | |
Registered User
Join Date: Dec 2002
Posts: 5,565
|
Quote:
The Aegisub devs don't want to do that. As it currently stands, Aegisub 3.0.0 will always emulate "legacy" behavior (though it will add info to tell you that, but probably not in the way the current trunk does, so reading "Video Colorspace" right now will produce wrong results with final Aegisub 3.0.0). Last edited by Guest; 7th June 2012 at 21:28. Reason: rule 4 |
|
13th October 2014, 16:15 | #51 | Link |
Registered User
Join Date: Jan 2012
Location: Mesopotamia
Posts: 2,587
|
thank you for this plugin
I wonder how can I compile lachs0r c-plugin one and what I need for that I didn't do any plugin compile before so I need your help I plan to play with libass and I think AssRender is a good choice for that and to releasing AssRender with last libass
__________________
See My Avisynth Stuff |
13th October 2014, 16:56 | #52 | Link |
Excessively jovial fellow
Join Date: Jun 2004
Location: rude
Posts: 1,100
|
If you've never compiled a plugin before, AssRender is probably the single worst example to start with. You can't actually build the plugin itself until you've compiled libass with MinGW, and that's a gigantic pain since it has a billion annoying dependencies, many of which are very tricky to get to compile on Windows. Start with something else.
|
13th October 2014, 19:43 | #53 | Link | |
Registered User
Join Date: Jan 2012
Location: Mesopotamia
Posts: 2,587
|
Quote:
I chose AssRender because it's just a plugin, as I can see the full program like vlc or mpv which using libass will be harder and AssRender easy to view the subtitle file with it every time in just avspmod
__________________
See My Avisynth Stuff |
|
27th April 2020, 21:02 | #54 | Link |
Registered User
Join Date: Mar 2012
Location: Texas
Posts: 1,666
|
Sorry to revive this thread, but has anyone come across binaries for the updated AssRender (v0.28): https://github.com/pingplug/assrender
I've searched and came up empty handed, most I found was a fork of the v0.28 version here: https://github.com/vadosnaprimer/assrender But still no binaries |
15th February 2021, 10:22 | #55 | Link | |
Registered User
Join Date: Jan 2012
Location: Mesopotamia
Posts: 2,587
|
Quote:
the x64 give me some errors in Visual Studio 2019, also the x86 I did seems only work in avs+! is the avs+ c header not work with avs 2.6 unlike the c++ one?
__________________
See My Avisynth Stuff |
|
15th February 2021, 13:54 | #56 | Link | |
Registered User
Join Date: Jan 2014
Posts: 2,314
|
Quote:
On the other hand, based on https://github.com/vadosnaprimer/assrender I have successfully built both x86 and x64 (after some path fixes). |
|
15th February 2021, 19:45 | #57 | Link | |
Registered User
Join Date: Jan 2012
Location: Mesopotamia
Posts: 2,587
|
Quote:
and can you share your edit of the code? with the x64 built anyway, at least in the built I did libass in not uptodate in the code, and maybe the others too, I didn't try to update it yet
__________________
See My Avisynth Stuff |
|
15th February 2021, 20:38 | #58 | Link |
Registered User
Join Date: Jan 2014
Posts: 2,314
|
It must be because of 32 bit 'decorated' names:
Avisynth 2.6 is looking for Code:
avisynth_c_plugin_init@4 or avisynth_c_plugin_init Code:
_avisynth_c_plugin_init@4 or avisynth_c_plugin_init@4 https://docs.microsoft.com/en-us/cpp...?view=msvc-160 So it won't be found by Avisynth 2.6 loader. I remember a similar case (I hope I find it soon; C plugins are rare on my git). I'll be back. As for the code edit: I've just cloned and not forked, it's only my local disk; but practically I didn't change the code. |
15th February 2021, 20:41 | #59 | Link |
Registered User
Join Date: Jan 2014
Posts: 2,314
|
It must be because of 32 bit 'decorated' names:
Avisynth 2.6 is looking for Code:
avisynth_c_plugin_init@4 or avisynth_c_plugin_init Code:
_avisynth_c_plugin_init@4 or avisynth_c_plugin_init@4 https://docs.microsoft.com/en-us/cpp...?view=msvc-160 So it won't be found by Avisynth 2.6 loader. I remember a similar case (I hope I find it soon; C plugins are rare on my git). I'll be back. EDIT: Yes, it was AvsInPaint. A definition file "assrender.def" must be created with the following content: Code:
LIBRARY assrender EXPORTS avisynth_c_plugin_init@4 = _avisynth_c_plugin_init@4 As for the code edit: I've just cloned and not forked, it's only my local disk; but practically I didn't change the code. |
|
|