View Full Version : Aegisub fork version
mojie126
16th June 2024, 16:09
I forked this version (https://github.com/arch1t3cht/Aegisub) and carried out secondary development on this basis, mainly supporting CUDA, D3D11 and DXVA2 hardware accelerated decoding support, and some functional updates and optimizations. I hope you can help test it.
github:https://github.com/mojie126/Aegisub
Emulgator
21st June 2024, 18:00
Win7U64: aegisub.exe: "GetDpiForSystem not found in USER32.dll".
Win10 only?
mojie126
22nd June 2024, 06:43
Yes, I used some functions that are only supported by Win10 and above
FranceBB
22nd June 2024, 19:03
I know that this is done with the best intention and everyone who is creating a fork is in some way trying to contribute, but the fact that there isn't a clear direction over where this is going means that after 2014 we ended up in a state in which different forks spread with different intentions and there doesn't seem to be any attempt to bring them back together under the same name / repository :( The fact that Aegisub is still kept alive by the various contributors who forked it is a good thing, but the fact that there are different forks means that we'll soon end up in a state in which different subtitling groups won't be able to collaborate as they're using different versions.
Although I wanna say 'thank you' for doing your part in keeping Aegisub alive, I can't deny that my first reaction to this post was:
https://media4.giphy.com/media/uFiaMyDjtxoE6Q1gCU/giphy.gif?cid=6c09b952pdpih4t6bz53ufswywcfotdau9j7j4jmm40fbpcs&ep=v1_gifs_search&rid=giphy.gif&ct=g
(for those not familiar with the meme, it's from the 2017 general election when the BBC was interviewing the UK public: https://youtu.be/H6-IQAdFU3w)
mojie126
27th June 2024, 07:44
I know that this is done with the best intention and everyone who is creating a fork is in some way trying to contribute, but the fact that there isn't a clear direction over where this is going means that after 2014 we ended up in a state in which different forks spread with different intentions and there doesn't seem to be any attempt to bring them back together under the same name / repository :( The fact that Aegisub is still kept alive by the various contributors who forked it is a good thing, but the fact that there are different forks means that we'll soon end up in a state in which different subtitling groups won't be able to collaborate as they're using different versions.
Although I wanna say 'thank you' for doing your part in keeping Aegisub alive, I can't deny that my first reaction to this post was:
https://media4.giphy.com/media/uFiaMyDjtxoE6Q1gCU/giphy.gif?cid=6c09b952pdpih4t6bz53ufswywcfotdau9j7j4jmm40fbpcs&ep=v1_gifs_search&rid=giphy.gif&ct=g
(for those not familiar with the meme, it's from the 2017 general election when the BBC was interviewing the UK public: https://youtu.be/H6-IQAdFU3w)
My English is not very good, so I may not fully understand what you mean.
My fork only enhances some capabilities, such as more high DPI adaptation, hardware acceleration when decoding, updates to some dependencies, and a simplified version of Aegisub-Motion
FranceBB
27th June 2024, 08:25
In a nutshell:
it's a very good thing that lots of people care about Aegisub and want to keep it alive, but the fact that we have several different forks and that each subtitling group is using whatever fork they deemed suited their interests best isn't exactly great.
Ideally, one day, we're gonna have one single repository with the forks being merged, thus bringing some clarity/sanity back. :)
Other than that, well done.
cubicibo
27th June 2024, 08:55
FranceBB is asking if these changes will be merged to the upstream repository (arch1t3cht's or TypesettingTools')? There are many Aegisub forks, any valuable inputs and updates should be merged to a common location to improve the Aegisub project. Not to spread isolated variants.
Anyway, good job. If it adds value to upstream, you should create a pull request!
mojie126
27th June 2024, 09:12
FranceBB is asking if these changes will be merged to the upstream repository (arch1t3cht's or TypesettingTools')? There are many Aegisub forks, any valuable inputs and updates should be merged to a common location to improve the Aegisub project. Not to spread isolated variants.
Anyway, good job. If it adds value to upstream, you should create a pull request!
I understand, but I don't dare. I am just a programming enthusiast, not a professional programmer. I only modified this fork based on my own preferences and needs. My changes are messy and may not adapt to the code style of the upstream library.
Last year, I also asked FranceBB about LUT and whether your SUPer can be transformed into a C++ static lib.
cubicibo
27th June 2024, 09:29
I just came here to help by reformulating FranceBB message and to cheer. Not to be blamed for something I cannot realistically achieve.
mojie126
27th June 2024, 09:38
I'm not blaming anyone, I'm just saying I knew both of your IDs before
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.