Activity for Obi-Wan
-
Obi-Wan posted a comment on ticket #699
That FFMS is only in x64 there. Anywhere to find x86?
-
What is the difference between AviSynth+ and AviSynthPlus?
-
O_o. Is this some kind of fork? Or the dev moved to there?
-
Is there a manual how to build MeGUI on your own
-
Please, forgive me, that I dare to remind myself once again.
-
So Zathor is no longer? I thought he came back a year ago.
-
Thanks for your reply Zathor. There is no issue with the preview at all, but I personally just don't like it ;-) That's why I asked to have an option for that, That's all. I use "Tools" -> "AVS Script Creator" -> I put a file in "Video Input" -> I click "File Indexer" -> I click "Queue" (with selection of either FFMSIndex od L-SMASH) -> and the next window "AviSynth Script Creator" comes with opened Preview. That's the preview I am referring to. edit: The 2940 version does not show this preview,...
-
Don't show preview window on AVS Script Creator
-
A kindly reminder @zathor, can it be merged to mainline please? I know that I can manually change the AVS script before saving, but it is very unhandy if I want to use automated OneClickEncoder for whole directory.
-
A kindly reminder @zathor, can it be merged to mainline please?
-
x266 and VVenC are not the same. Both are implementations of H266 (VVT) encoding algorithm, but from different "manufacturers". VVenC/VVdeC is from Fraunhoffer Institute, and is available only as a source code for now. x266 is from MulticoreWare and its 1.0 release is planned to H2 2023.
-
Anyone? @zathor, can you please add this to mainline?
-
How is that related to my request?
-
I made a PATCH file to do this. @zathor - can you integrate this?
-
Add 'SincResize' to available resize filters
-
Because within MeGUI workflow x264 does not have to decode anything from the input. Instead it gets already uncompressed frames at input, which are decoded by ffms/lsmash via ffmpeg. Is that right?
-
Because within MeGUI workflow x264 does not have to decode anything. Instead it gets already uncompressed frames at input, which are decoded by ffms/lsmash via ffmpeg. Is that right?
-
The x264 0.164.3085 0bb85e8 is compiled without libavformat. Does this change anything? OLD x264 (from dev server): x264 0.164.3075 66a5bc1 (libswscale 5.9.100) (libavformat 58.76.100) (lsmash 2.16.1) built on Sep 29 2021, gcc: 8.2-win32 20190215 x264 configuration: --chroma-format=all libx264 configuration: --chroma-format=all x264 license: GPL version 2 or later libswscale/libavformat license: LGPL version 2.1 or later NEW x264 (from this post): x264 0.164.3085 0bb85e8 (lsmash 2.16.1) built on...
-
Oh, I see. Do I need to update first to the development version (2924)? Or the stable 2913 is ok?
-
Sorry for a newbie question, but do you guys just put the downloaded tools into appropriate folders (overwriting the old files), or these just gets slipstreamed into the megui-test branch, or AutoUpdate development update server?
-
Is Unicide support planned for MeGUI?
-
Is that implemented already in MeGUI stable?
-
Is something similar available in x265? I cannot see any muxer parameter only the output filename option.
-
Oh, thanks. You convinced me ;-)
-
Does it even matter? Does it influences playback or so?
-
Updated TODO
-
Updated TODO
-
updated TODO;
-
Added MIT License
-
release
-
added hints; fixed delete from queue selected files only; added application info strings
-
Initial commit
1
