MeGUI: bug reports and feature requests

[kalehrl]

MeGUI 2435 gets stuck at creating ffms index.
Log sent via pm.

[Zathor]

Please describe "got stuck".

How long did you wait? In your log file I cannot find any errors (beside one not available update server). Does it happen with all of your files? Can you upload a sample?

[Zathor]

2437 [OneClick] improved working directory generation
                improved handling if selected output container cannot be used
2436 [M2TS Muxer] added HEVC/x265 and MKV support (requires tsmuxer 2.5.5+)
     [OneClick] added HEVC/x265 support for MP4 and removed it for MKV

[kalehrl]

Originally Posted by Zathor

Please describe "got stuck".

How long did you wait? In your log file I cannot find any errors (beside one not available update server). Does it happen with all of your files? Can you upload a sample?

Problem file sent in a pm.
I waited a couple of minutes but the progress bar didn't move.
This is the first file this problem happened so maybe it's file related.

[Zathor]

Thanks - fixed with the FFMS update I just pushed out.
EDIT: Had to remove it because I have to modify MeGUI for it.

[LigH]

Originally Posted by Zathor

2431 [Update] optional packages will only be downloaded/enabled if needed
              therefore during first use of such packages an online connection may be required
	      if a package is not used in 60 days it will be disabled again

Oh heck. Another tool which tries to be smarter than its user. Like Microsoft Office. Why?!

[Zathor]

Originally Posted by LigH

Oh heck. Another tool which tries to be smarter than its user. Like Microsoft Office. Why?!

Traffic problems. If you have a fast server without any traffic limits which we can use I happily disable this change or at least add an option to download always everything.

Nevertheless why do you have problems with this change? It should! not have an impact to the user. Tuning of the options may be required of course so if you encounter any problems please drop a line here.
EDIT: To explain the behaviour in more detail:
Before every usage of the packages it will be checked if the local files are available. If not an online connection is required to download them immediately - otherwise the job will fail. But that can most likely never happen as the full MeGUI package on SF will always contain all files. Therefore likely only the files are outdated and they will be refreshed during the next update cycle. And a "disabled package" can of course still be used. But if it is not used it will not be updated automatically. If a user wants to do it all packages can be enabled in the update window (but that will last only for 60 days if those tools are not really needed).
As always - if you or anyone else has a better idea I will implement/change it if possible.

Btw there are some other changes regarding the update server coming - like update checks only once a week (dev server maybe every second day). Also here some points are mentioned but not all may be implemented because of the traffic problems: http://forum.doom9.org/showpost.php?...postcount=3721

[LigH]

Would the traffic problems be less urgent if I tried to find update server mirrors for you? If so, please tell me the expected traffic.

[Zathor]

2441 [OneClick] fixed PCM audio track handling in mkv files (regression of 2378)
2440 [XviD] hide FourCC box as it will not be used
2439 [FFMS Indexer] automatically switch to LoadCPlugin if required
                    add fpsnum and fpsden if required
2438 [x264] custom --fps values will be detected and used

Originally Posted by LigH

Would the traffic problems be less urgent if I tried to find update server mirrors for you? If so, please tell me the expected traffic.

New update servers are always welcome. The traffic cannot be predicted very well - also I do not have direct access to the servers.

But even with a new update server I will not revert all changes. E.g. also for users with slow/low network it makes sense that only needed packages are updated. Of course there will be an option to enable all packages without limitation.
Also it would be good to limit the major hit during a new stable release therefore a new update check on the stable every few days is also a good idea (which can be forced).

[Zathor]

Originally Posted by razvanultra55

here is my X265 preset

Thanks, I am able to reproduce the problem. The fix will be in the next build.

[Zathor]

The fix for your x265 problem is in build 2442. Currently online is 2441 so it cannot be fixed yet. As a workaround you can delete your x265 directory (while MeGUI is not running).

The other messages are ok. One server is not completly in sync (should be in a few minutes) and for one package the new build is required.

[Wam7]

I was wanting you to update QAAC from 2.27 to 2.32 but now you've done it and after using it for a while now I'm not too sure. I normally get 75x speed for encoding the audio using FFAudioSource or DirectShow as the preferred decoder but using either of those and the speed is sometimes now as low as 2x. I only get 75x using NicAudio. I've had occasions before where NicAudio has caused me problems so it was good to have the options...

[Zathor]

Originally Posted by Wam7

I was wanting you to update QAAC from 2.27 to 2.32 but now you've done it and after using it for a while now I'm not too sure. I normally get 75x speed for encoding the audio using FFAudioSource or DirectShow as the preferred decoder but using either of those and the speed is sometimes now as low as 2x. I only get 75x using NicAudio.

Can you please revert back to 2.27 and see if you get the old speed? I cannot reproduce your problem.

2444 [Settings] added option to always use the included/portable AviSynth build (disabled by default)
     [Update]   improved AviSynth portable support for external tools
     [Log]      added AviSynth+ detection
2443 [Settings] removed "Force Video File Extension for QT compatibility"
                removed "Samples between audio progress updates"
                removed "Use Advanced ToolTips"
                cosmetics
2442 [x265] fixed error during preset startup (regression of 2422)

In order to solve some of the confusions when the included AviSynth is used I have now added an option in the settings. When this option is enabled or no AviSynth is found the included AviSynth build is used - in all other cases the included build is not used and removed from the directories it has been copied to.

Also I have updated the included build to the recent AviSynth+. And btw the x265 builds have been switched to the VC12 legacy builds as the mingw builds caused on some of my machines crashes during the first 20-40 frames.

[Octo-puss]

I am not sure I understand. Are you saying MeGui switched to Avisynth+?

[SacredCultivator]

Thanks for the update and wanted to point out that in the settings "Always use inlcuded AviSynth", should be "included".

[Octo-puss]

Oh a small bug: if tools\avs folder is not present, MeGui produces an error and can't even update itself.

[LigH]

@ Octo-puss:

AviSynth+ may have a few quirks to be considered when a script is created; MeGUI probably wants to support both, or at least detect it correctly for a meaningful message if not.

[Zathor]

Originally Posted by SacredCultivator

Thanks for the update and wanted to point out that in the settings "Always use inlcuded AviSynth", should be "included".

Will be fixed. Thanks

Originally Posted by Octo-puss

Oh a small bug: if tools\avs folder is not present, MeGui produces an error and can't even update itself.

I cannot reproduce that. If the folder is not available it will be downloaded without problems.

Originally Posted by Octo-puss

I am not sure I understand. Are you saying MeGui switched to Avisynth+?

The included build has been switched to AviSynth+. Also a general detection for AviSynth+ has been added.

[Octo-puss]

Happens every time here. I have no idea what information could I provide to help you identify the problem.

[LigH]

"An error" is certainly not specific enough. I could even imagine that the UAC doesn't allow MeGUI to create a subdirectory when not run "as Administrator", who knows... Maybe you can quote that error before the attachments get approved.