MeGUI: bug reports and feature requests

[Zathor]

Just a minor fix this time:
2396 [AutoEncode] fixed mp4 output (regression of 2381)

[hello_hello]

I think this was discussed previously, but I don't think it was ever resolved.

The default for --weightp appears to be --weightp 2.

Selecting Blu-ray as the target playback device appears to use --weightp 1

With no target device selected, checking Blu-ray compatibility also automatically adds --weightp 2 to the command line.

I'm just wondering if there's a reason for the inconstancy I'm missing. Should Blu-ray compatibility require a specific --weightp value and if so, should it be the same in both cases?

[sneaker_ger]

Blu-Ray does not require a specific --weightp value. Both 0 and 1 are allowed, 2 will automatically get reduced to 1 by --bluray-compat.

[hello_hello]

Yeah, if I recall correctly using --bluray-compat resulted in --weightp 1 even though checking --bluray-compat in MeGUI's encoder configuration automatically adds --weightp 2 to the command line. So while it does no harm, I guess technically it's wrong, or at least misleading. You can manually change it to --weightp 1 without the encoder configuration trying to stop you, and when you do --weightp disappears from the command line to indicate it's the (current) default.

If anything, checking --bluray-compat should cause --weightp 1 to be selected in the encoder configuration (same as selecting Blu-ray as the target playback device does), and while --bluray-compat is checked, ideally MeGUI should stop you from changing it to --weightp 2.

[ph4nt0m]

First of all, I want to thank everyone involved with the development of this fantastic tool. I recently discovered the "One Click" functionality, after having done many steps by hand up to this point.

The possibility to define a custom OneClick profile and especially a custom AviSynth template is amazing, but I lacks one feature imho: The only way to crop the input source is to either rely on AutoCrop or to hardcode the values into the AviSynth template manually each time. From my own experience, AutoCrop seems to be a little bit too "defensive" sometimes.

Feature request:
It would be great if you could add a crop tool to the One Click Encoder (just like the one in the AVS Script Creator), which shows a preview of the input video and lets the user choose the cropping values he likes. These values could then be inserted into the <crop> area of the AVS template.

[Zathor]

I am not sure if this can/should be implemented. It would introduce either a manuel action in the middle of the OneClick process (after indexing) or e.g. DirectShowSource must be used in the beginning which may cause problems.

AutoCrop seems to be a little bit too "defensive" sometimes
Please explain that in more detail. Maybe it is possible to adjust AutoCrop.

[ph4nt0m]

or e.g. DirectShowSource must be used
That's what I had in mind. Of course DirectShowSource is like a "last resort", but it usually works quite well. Remember that it would only be required to find the correct crop values. The actual encoding should be done as usual (with DGIndex, etc.), of course.

A manual input during the OneClick process would contradict the principle of batch processing, namely to add a bunch of jobs and then let MeGUI process the whole queue in one go without any further interruption.

Please explain that in more detail. Maybe it is possible to adjust AutoCrop.
As far as I understand, AutoCrop works by evaluating a certain amount of sample frames. Unfortunately in the past, some of my TV captures had varying black border sizes which seemed to cause an undercropped result sometimes. But looking at each single frame and taking the least common area is no option either, since very dark scenes would obviously distort the result.

I think that those sources should better be cropped manually, as no automated tool will ever cover each possible case and satisfy the preference of every user. :)

[Shevek]

It would be really nice to be able to right click on any completed entry in the Queue which has an output file (or folder) and have an option to open that location in Windows Explorer

[Kurtnoise]

It would be really nice to be able to right click on any completed entry in the Queue which has an output file (or folder) and have an option to open that location in Windows Explorer
It should be there in the next release...

[Shevek]

It should be there in the next release...

:thanks: :thanks: :cool: :cool:

[hello_hello]

I'd still love to be able to run a job immediately without the need to add it to the queue first. Maybe by holding down the shift key while clicking on any of the Queue buttons. Either that or maybe Shift+Queue could add a job to the queue and automatically run it in a temporary worker. Or something like that....

[Kurtnoise]

Never tried the AutoStart Queue option from the Settings ?

[bxyhxyh]

I think it is the time to release next "stable" release, since 10bit x264 feature added to meGUI.

[Kurtnoise]

it might be great to have more feedback on this using the dev release, first...

[hello_hello]

Never tried the AutoStart Queue option from the Settings ?

Yes, but it's not the same thing. For instance I often set up several encoding jobs, add them to the queue as I go, then run them once they're all added. With jobs already waiting in the queue, it'd be nice to be able (for example) to run a new indexing job without having to add it to the queue, switch to the queue tab, then right click to run it in a new temporary worker etc.

Having that happen automatically (via something like Shift+Queue in the File Indexer window) would be a nice convenience.

[Zathor]

it might be great to have more feedback on this using the dev release, first...
I agree. There is e.g. this ticket: http://sourceforge.net/p/megui/bugs/729/
Also there are no important bugs in the current stable build. Therefore there is no reason to rush it.

[Zathor]

I need a hint which way to go for this x264 problem:
http://forum.doom9.org/showpost.php?p=1640401&postcount=7207
You use 2-pass mode but 1st pass defaults to Main profile which has lower VBV than High profile used during 2nd pass. That is why you see this only during 1st pass.

Either I can remove the VBV restrictions for the 1st pass if they are above the main limit or I can lower them to the main limit. Which way is the better way?

[sneaker_ger]

Neither. Set the vbv values to the same values you are using on the second pass and simply ignore the x264 warning. (Probably what MeGUI is already doing right now?)

[detmek]

That is not a bug and everything works fine. Problem is that people see that warning and think that something is wrong.

@Zathor x264 devs are the only one who can give the right answer to that question. sneaker_ger is right, leave it as it is.

If you remove restrictions people will complain why restrictions are not set. If you lower values people will complain why MeGUI does not use values they set. In th current state, everything is on x264 to handle things correctly. If someone has a problem with that he can complain to x264 devs.

[Vincent Vega]

i need to transcode aac to ac3 but it errors out.
i tried aac in mka and without container.
logs are in attachment.

[detmek]

Something is wrong with your Avisynth script. You probably need to add another ) after last AudioRate() call.
SSRC((AudioRate()*1001+480)/960).AssumeSampleRate(AudioRate()).TimeStretch(pitch=Float((AudioRate()*1001+480)/960)*100.0/Float(AudioRate()))

[Vincent Vega]

its not my script, its script generated by megui for slow-down.
my input is audio file.

[detmek]

I didn't even notice that MeGUI has speedup/slowdown option for audio! Good news.
You are right. Its a bug.
Same thing with speedup option.

[Zathor]

Thanks, fixed.

[Zathor]

2402 [Queue] extended "Open" option to open input/output files/folders and in any job state if available
2401 [Audio Encoder] fixed TimeStretch support for 23.976 <--> 25 fps conversion (regression of 2383)
2400 [MediaInfo] added log output if fps cannot be determined
2399 [x264] if --bluray-compat is used without a BluRay device selected:
--open-gop is not forced anymore
--weightp is restricted to 0 or 1
2398 [Queue] allowed to open output folder when job is done. This is available via the right click on the Job Queue.
2397 [MediaInfo] use 23.976 instead of 99 as default value if fps cannot be determined

[Shevek]

2402 [Queue] extended "Open" option to open input/output files/folders and in any job state if available
2398 [Queue] allowed to open output folder when job is done. This is available via the right click on the Job Queue.


This is AWESOME - thanks! :thanks:

[Capsbackup]

Just updated MeGui to 2402, and now I am unable to open previous scripts using directshowsource.dll!
Even if I try AVS Script Creator and select "Directshowsource", I get an error that says it is not an AviSynth 2.5 Plugin.
Something changed? :confused:

EDIT:
Got directshowsource.dll working again by renaming the backup to directshowsource.dll, and removing the new one from this latest update.
Old one that works is 26KB. The one that does not work is 27KB.

[Zathor]

Thanks - as the megui.org server is currently offline I cannot change it.

[LigH]

Fortunately, there are more reliable alternatives. How many times was mentioned here that DirectShowSource is not the primary recommended one, because everyone may have a different set of installed DirectShow filters?

[luke83]

Megui doesn't mux subtitle file created with vobsubber (the index) even if i select it :/

[Kurtnoise]

:logfile:

[Capsbackup]

Fortunately, there are more reliable alternatives. How many times was mentioned here that DirectShowSource is not the primary recommended one, because everyone may have a different set of installed DirectShow filters?

Though I do not disagree, DirectShowSource has been quite reliable for me.
I was reporting what I consider or at least thought may be a bug, since DirectShowSource had been working fine with the previous version of DirectShowSource.dll, and only after the update did I experience a problem. After reverting back to this previous version it then worked as it use to.
There may be better alternatives, but DirectShowSource should still be an option I believe.

[Zathor]

Hello,

MeGUI auto updater wants to downgrade from:

core 2402 to core 2396

tsmuxer 1.12.6b to tsmuxer 1.11.6b

avs 2.6.0 a5 to avs 2.5.8

Why?

I can only guess as I do not have access to the server currently:
- avs caused problems with DirectShowSource (I have a fixed package, but cannot upload it)
- tsmuxer is not stable right now (I would recommend to downgrade to 1.10.x)
- core is likely a failure and has been reverted by accident during the two changes above

[Wilbert]

Just wanted to let you know that the domains megui.org and avisynth.org are transferred to me. I guess Richard gave ftp access to some of you know. So drop me a pm if you need ftp access again. (I left all the files on megui.org so there shouldn't be anything missing ...)

[Kurtnoise]

- avs caused problems with DirectShowSource
it works fine for me...So, don't do that please. The 2.6.0 alpha releases are highly recommended by the main Avisynth developer.
- tsmuxer is not stable right now (I would recommend to downgrade to 1.10.x)
It looks like the last beta published is fine...




PS: your PM box is full...I dropped a PM to Wilbert in order to have access to the megui.org once again.

[mini-moose]

it works fine for me...So, don't do that please. The 2.6.0 alpha releases are highly recommended by the main Avisynth developer.


DS works fine for me too.

[Zathor]

it works fine for me...So, don't do that please. The 2.6.0 alpha releases are highly recommended by the main Avisynth developer.
I agree to use 2.6 - but the included directshowsource.dll does not work when you have avs 2.5.x installed. Therefore either:
- the old directshowsource.dll from 2.5.x must be still used (does work with avs 2.6 also)
- or both DLLs have to be included and used depending on the avs version

I have a local package for the first option as it seems easier for me.
EDIT: uploaded

[hello_hello]

I agree to use 2.6 - but the included directshowsource.dll does not work when you have avs 2.5.x installed. Therefore either:
- the old directshowsource.dll from 2.5.x must be still used (does work with avs 2.6 also)
- or both DLLs have to be included and used depending on the avs version

I have a local package for the first option as it seems easier for me.
EDIT: uploaded

Isn't directshowsource.dll installed in the Avisynth plugins folder when Avisynth is installed? I'm not 100% sure, but if that's the case...

directshowsource.dll will be autoloaded whenever the "installed" version of Avisynth runs. Could it be conflicting with the new version if MeGUI loads it as well?

Another alternative might be for MeGUI not to load directshowsource.dll from it's own AVS folder if it detects Avisynth is installed, as directshowsource.dll should be autoloaded anyway and it'd prevent any possible conflicts.

[ph4nt0m]

Is it possible to extend the AutoEncode dialog to include additional muxing settings? When using mp4 as a target container for example, there is no way to define the audio language and track titles. Currently, this is only possible by using the mp4 muxer manually (Ctrl+5).

Maybe the default video track title could just be taken from the file name? :)

[Zathor]

2407 [Update] disabled megui.xvidvideo.ru mirror as it is out of sync
2406 [AviSynth] only load portable DirectShowSource.dll if portable mode is used
2405 [Log] improved avs log information
2404 [MediaInfo] ignore phantom audio tracks
2403 [M2TS Muxer] added A_LPCM as Audio Codec ID for WAV/PCM files. Bug #730

[hello_hello]

Minor feature request.....

Would it be possible for MeGUI to give each job in the log file a unique job number per session? Or for that matter, maybe per "forever".
Currently if you add a job and run it, it's job #1 in the log file. Adding another job to the queue after the first has finished assigns it job #1 also, etc. etc.
I know each job has a unique name.... well unless you run the same job twice then you can have two jobs with the same name and job number. ;)

Thanks.

[mini-moose]

just tried the new version. loaded an m2ts did crop etc saved the avs and it wouldn't load.
I looked at the avs file and it seems the DS bit is problematic:

#inputDirectShowSource("G:\MOVIES\RANDOM\BDMV\STREAM\00001.m2ts", fps=23.976, audio=false, convertfps=true).AssumeFPS(24000,1001)
#deinterlace
crop(0, 20, 0, -22)
Spline36Resize(1280,688) # Spline36 (Neutral)
#denoise

Maybe that has to do with "2406 [AviSynth] only load portable DirectShowSource.dll if portable mode is used" ? not sure what is portable mode but it still seems wrong.

[Kurtnoise]

Is it possible to extend the AutoEncode dialog to include additional muxing settings? When using mp4 as a target container for example, there is no way to define the audio language and track titles. Currently, this is only possible by using the mp4 muxer manually (Ctrl+5).

did you use the "Add additional content" checkbox ?

[Kurtnoise]

just tried the new version. loaded an m2ts did crop etc saved the avs and it wouldn't load.
I looked at the avs file and it seems the DS bit is problematic:

A carriage return seems to be missing between #input and DSS...try this build (http://www.mediafire.com/?98ukfs5u93akk40).

[Shevek]

I just updated and noticed a couple of errors in the updater's log:

Connecting to server: http://megui.xvidvideo.ru/auto/
There are 3 files which can be updated.
Updating core. File 1/3.
Error: Failed to download file core with error: CouldNotDownloadFile.
Updating ffmpeg. File 2/3.
Error: Failed to download file ffmpeg with error: CouldNotDownloadFile.
Updating avs. File 3/3.
Update completed
Files which have been sucessfully updated: 1
Error: Files which have been not sucessfully updated: 2

Last 2 lines - "sucessfully" should have 2 "c"s - "successfully"

Last line - "not" is in the wrong place, should be "Error: Files which have not been successfully updated"

[Zathor]

Thanks

2409 [Update] fixed grammar/spelling errors
2408 [AviSynth] fixed DirectShowSource in non-portable mode (regression of 2406)

[mini-moose]

A carriage return seems to be missing between #input and DSS...try this build (http://www.mediafire.com/?98ukfs5u93akk40).

#input
DirectShowSource("G:\MOVIES\RANDOM\BDMV\STREAM\00001.m2ts", fps=23.976, audio=false, convertfps=true).AssumeFPS(24000,1001)
#deinterlace
crop(0, 20, 0, -22)
Spline36Resize(1280,688) # Spline36 (Neutral)
#denoise

seems better now. ah and the #input part is gone with 2409 (I used Kurtnoise's linked build for the above), did seem unnecessary.

what is a portable mode? one that's runs on a pc without external separate installs of avisynth or other tools?

[Zathor]

what is a portable mode? one that's runs on a pc without external separate installs of avisynth or other tools?
Correct. If AviSynth is not installed the included build in MeGUI will be used - and therefore also the included DSS. Before the change in 2406 this portable/static MeGUI DSS file has always been used.

[Zathor]

Would it be possible for MeGUI to give each job in the log file a unique job number per session? Or for that matter, maybe per "forever".
Currently if you add a job and run it, it's job #1 in the log file. Adding another job to the queue after the first has finished assigns it job #1 also, etc. etc.
I know each job has a unique name.... well unless you run the same job twice then you can have two jobs with the same name and job number. ;)
New numbers will be assigned from 1 on of they are free. So if a job is completed and deleted from the queue this number will be reused. I do not understand the reson for this request as this should not cause any problems. Can you describe in more detail why you think this change is needed?

[ph4nt0m]

did you use the "Add additional content" checkbox ?
Thanks, I never would have guessed that this opens the adaptive muxing dialog. :) Now I can at least specify the audio track language, but the video title box is disabled. Is there any specific reason for this?

In addition, I have a few suggestions:


The audio track language in the muxing dialog could be set automatically according to the "Default languages" setting in Options -> Settings -> Main Configuration.

The video title in the muxing dialog could be <filename without extension> by default.

By default, "-muxed" is always appended to the output filename. I don't think anybody wants to leave it that way when archiving the final file. I suggest to add this string only in case there would be a name clash otherwise (could be the case with .mp4 if an audio file with the same extension already exists).


As you can see, I'm just trying to reduce the number of clicks and to make the AutoEncode a little bit more "Auto". ;) Alternatively, you could let the user define his own default muxing settings. However, this would require to introduce some new placeholders, like <filename without extension>.