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 |
1st March 2021, 12:35 | #101 | Link |
Registered User
Join Date: Jan 2012
Location: Mesopotamia
Posts: 2,587
|
yes, and still there are some use 601 or no info at all (They still use old versions of aegisub or something)
__________________
See My Avisynth Stuff |
1st March 2021, 14:51 | #102 | Link | |
Registered User
Join Date: Jan 2014
Posts: 2,309
|
Quote:
https://github.com/ShiftMediaProject...s_types.h#L106 |
|
1st March 2021, 19:28 | #103 | Link |
Registered User
Join Date: Jan 2014
Posts: 2,309
|
vsFilter TextSub is exactly doing nothing
Code:
BlankClip(ColorbarsHD(), color = $123456) TextSub("ctest2.ass") No wonder it perfectly fit the rectangles into colorbars samples because it left the Colorbars image untouched. Or what did I do wrong? |
1st March 2021, 21:01 | #104 | Link | |
Registered User
Join Date: Jan 2012
Location: Mesopotamia
Posts: 2,587
|
Quote:
putting converttoyv12 before TextSub will make it work edit: ok, seems AssRender and TextSub now are similar with ctest2 here are ctest3 https://www.solidfiles.com/v/Gv3mRXMyre3e5 done by corrects colors manually, it seems work fine in both, the ctest2 was done using old ctest (which also give similar output in TextSub) with aegisub resample resolution The lesson: no one should use BT.601 with HD in last aegisub, and never trust or wait error report of what color formats filter can work with (vsfilter case with yv24)
__________________
See My Avisynth Stuff Last edited by real.finder; 1st March 2021 at 21:25. |
|
4th March 2021, 11:15 | #105 | Link |
Registered User
Join Date: Jan 2014
Posts: 2,309
|
New release: ASSRender 0.35
This version seemed for me significantly quicker than the previous one. Code:
### 0.35 (20210304) * Windows MSVC: Update to libass v0.15 (git submodule update --init --recursive --remote) For changes since v0.14 see https://github.com/libass/libass/blob/master/Changelog * don't guess base on video resolution (realfinder) if .ass file has no Matrix info then it should be treated as it "Rec601" to maintain compatibility * Parameter 'colorspace' default value is no longer "guess" * Add more color options: PC.709, PC.601, TV.fcc, PC.fcc, TV.240m, PC.240m, none. "none" and "guess" implies "guess-by-resolution". * Fix: possible crash on initializing phase (buffer overread, linux crashed, Windows was just lucky) |
4th March 2021, 21:35 | #106 | Link |
Registered User
Join Date: Jan 2012
Location: Mesopotamia
Posts: 2,587
|
thanks, I did update the wiki http://avisynth.nl/index.php/AssRender
__________________
See My Avisynth Stuff |
28th May 2021, 17:12 | #107 | Link | |
Registered User
Join Date: Jan 2012
Location: Mesopotamia
Posts: 2,587
|
I did post this
Quote:
then after I did not get an answer I asked in irc.libera.chat/#libass in IRC and I get this answer "libass simply doesn't. it's given a time, and subtitles are time-based" so I think the peoples who work on AssRender have the answer edit: I get an answer, ceil(start timestamp in seconds * frames per second)
__________________
See My Avisynth Stuff Last edited by real.finder; 28th May 2021 at 17:40. |
|
12th October 2022, 16:11 | #109 | Link | |
Registered User
Join Date: Jan 2018
Posts: 2,153
|
Quote:
https://github.com/subelf/Spp2Pgs/releases Btw, it's already support avs?? |
|
12th October 2022, 16:14 | #110 | Link |
Registered User
Join Date: Feb 2022
Posts: 104
|
PunkGraphicStream and easySUP will do direct .ass to .sup.
avs2bdnxml will as well if you're fine using an avisynth script that renders your ASS file. SubtitleEdit has an option to export to SUP, should work from ASS. Anything else will need to be converted to BDNXML or other formats first then to SUP. |
12th October 2022, 21:46 | #111 | Link |
Registered User
Join Date: Jul 2003
Location: Italy
Posts: 1,135
|
How these projects are really "BD compliant"? For example, the 4 MB decoding buffer limitation... is it even checked?
Normally, "official" SUP subtitles (created by Scenarist BD), cannot require more than 4 MB of buffer to be decoded but I think these "SUP" could be out of standard. Avs2bdnxml have the advantage to export PNG+XML subtitles, and these are imported into Scenarist who check that everything is compliant and then encode to SUP. Exporting directly to SUP in this case could be a bit risky. |
12th October 2022, 23:16 | #112 | Link |
Registered User
Join Date: Feb 2022
Posts: 104
|
The 4 MB buffer only applies to displayed objects or the ones that will be displayed next frames. In fact it is not the bottleneck of the hardware SUP decoders. What I find to be the limits are the coded bandwidth (16 Mbps) and decoded bandwith (128 Mbps).
For example, your FSN release has fading staff credits aside of subtitles lines. When the fades happen, all objects are redrawn every frame. The instantaneous PGS bitrate is then 10~11 Mbps (~70% of capacity) at most. During the heaviest epoch you write 7.23 MiB of decoded object data to the buffer in ~13s. Decoded bandwidth is used between 10%~50%. Buffer is never full because on every acquisition, it is flushed. The 4 MiB buffer is not the issue at all unless you attempt to draw 1920x1080 objects via PGS very often (128 Mbps -> can theoretically draw 1920x1080 images every 120 ms -> ~3 frames, or >6 frames on epoch start as the screen has to be "cleared"). What blows up is the coded buffer bandwidth. /Salesman person: SUPer has a more advanced bandwidth and buffer checker function than avs2bdnxml. You can easily call it Code:
from SUPer.render import is_compliant from SUPer import SupStream FILE = ... FPS = ... sup = SupStream(FILE) epochs = [epoch for epoch in sup.epochs()] print(is_compliant(epochs, FPS)) Last edited by cubicibo; 12th October 2022 at 23:38. |
14th January 2023, 00:49 | #113 | Link |
Registered User
Join Date: Jan 2014
Posts: 6
|
a slightly naive question but, since this plugin uses libass and not VSfilter. If all I need is to hard-code subtitles (and not using other filters), what would be the advantage of writing a script to hard-code subtitles with AssRender, instead of hard-coding the subs with ffmpeg directly with something like
ffmpeg -i video.mp4 -vf "ass=subtitle.ass" out.mp4 ? |
14th January 2023, 18:19 | #114 | Link | |
Registered User
Join Date: Mar 2012
Location: Texas
Posts: 1,664
|
Quote:
|
|
Thread Tools | Search this Thread |
Display Modes | |
|
|