I'll try some different versions of MeGUI later on, maybe starting with a fresh installation of MeGUI, and if I discover anything interesting I'll report back. Of course, that could simply be coincidence. I recall initially thinking it didn't seem right, but I didn't give it any further thought at the time as I normally use the installed Avisynth 2.6. If anything, I suspect the problem may have started when the Avisynth version information displayed in the log file was updated. I didn't update it though, and when I tested, it was correctly using the portable Avisynth . When I ran the updater it appeared to want to "upgrade" the portable version to Avisynth 2.6. I made a copy of my current MeGUI 2830 folder and replaced MeGUI.exe with version 2584. What happens if you use the old MeGUI version which does report proper results and update the AviSynth package to the one included on the update server? What happens when you only run a script with version() in it? In general both l-smash and ffms can still index AVI files.ĮDIT: If you however try to open the AVI directly in the AVS Creator this is blocked by default (and even if not advisable can be reenabled). Has this functionality been removed or do I need to download additional components/files?Īs written by hello_hello we would need more details. I have just upgraded to meGUI 2828 and there now seems to be no indexer to deal with avi (DivX5) files preparatory to conversion to AVC (mkv or mp4) files. Could you please post your log file (versions block) and which size your video has? That part of MeGUI is (even more than the others) a piece of. That is true, I did no changes for the video player. Pressing the buttons usually makes the preview so large that it's unusable and needs to be closed/reopened. From version's 2828 video player, W10 Pro, 125% custom DPI. ![]() Reading in the release notes that the DPI issues have been fixed but I'm seeing no changes. I'm short on time at the moment, but I can dig out some older MeGUI's tomorrow for testing if Zathor needs me to. I was just replacing MeGUI.exe in an old installation folder for testing and I'm not sure that's the best way to do it. Operating System: Windows XP Professional x86 SP3 (08.2600) The old version of the log file isn't as informative though. So it appears it is using the portable Avisynth . I thought maybe it was something peculiar to my PC as I tried a few older versions of MeGUI, telling it to use the included Avisynth and tested it's ability to open this script:Īnd they opened it successfully, which I assume they shouldn't be able to, but then I tried MeGUI 2584 and the portable Avisynth , it resulted in: The only reason I started to think about it was due to this thread (). MeGUI used to switch between the installed Avisynth and it's portable version, but doesn't seem to do so now. I'm still on XP, so it's in the C:\WINDOWS\system32 folder. HH, have you got an Avisynth.dll in system32/SysWOW64 ? When I renamed Avisynth.dll in the MeGUI folder to Avisynth.old, MeGUI could still open scripts even though it's configured to use the portable Avisynth So that seems okay, but no Avisynth specific functions seem to be working, so I suspect MeGUI is still using the installed Avisynth 2.6. Is it an XP thing?Ĭhecking Avisynth.dll in the MeGUI folder reveals the following: ![]() MeGUI seems to be saying it's using Avisynth and not using it at the same time. Does the following Avisynth info from MeGUI's log file make sense (MeGUI version 2830)?
0 Comments
Leave a Reply. |