MeGUI: bug reports and feature requests

[Floatingshed]

Can any one help with this...
I've been creating .mp4 files with megui containing 1x264 stream and 1xaac stream using autoencode. For weeks all has been well.
Suddenly I find that when I play the mp4's all players report twice the actual duration. Demuxing and remuxing with YAMB fixes this fine.
I'm a bit baffled as megui and yamb both use mp4box to mux. Does anyone know what is going on? Thanks.

[Zathor]

2006 [MKV Muxer] added support for wav input files. Feature request #3253221
2005 [x264] added option for interlaced modes --tff and --bff. --interlaced has been removed. Bug #3204337
2004 [Audio Encoder] added option to choose the preferred decoder. Feature request #3053195
in case the preferred decoder cannot decode the input file the others will be tried, too
default order: NicAudio, FFAudioSource, DirectShow
2003 [One-Click] some profile adjustments

[Lighto]

There is a GUI bug with the NeroAAC config dialog.
The default constant bit rate value is always at 16 kbit/s until the user selects the constant bit rate radio button or the variable bit rate radio button.

http://i.imgur.com/hvG4R.png
http://i.imgur.com/XNKwp.png

[doc_dvxm]

Hi there...

I am using the latest development version of meGUI (2006). It crashes when I'm trying to load a .dgi file (properly indexed with activated & licensed DGAVCDecDI & DiAVC). Same script working fine when I am loading it on AvsP. The source is HD .h264.

There is no any problem with FFMS2 indexed and .dga files. Also it works fine with Directshowsource). Is it problem of newest meGUI? Unfortunately, I don't tried with previous version of meGUI. Can't compare. If no, I'll search at neuron2.net.

Thanx in advance...

doc

[Lyle_JP]

Hi there...

I am using the latest development version of meGUI (2006). It crashes when I'm trying to load a .dgi file (properly indexed with activated & licensed DGAVCDecDI & DiAVC). Same script working fine when I am loading it on AvsP. The source is HD .h264.

There is no any problem with FFMS2 indexed and .dga files. Also it works fine with Directshowsource). Is it problem of newest meGUI? Unfortunately, I don't tried with previous version of meGUI. Can't compare. If no, I'll search at neuron2.net.

Thanx in advance...

doc

Isn't .dgi strictly for use with DGDecodeNV and Nvidia Cuda cards?

[doc_dvxm]

DGDecodeNV requires NVIDIA Cuda cards. DGAVCDecDI is for all others...


Btw reinstalling of meGUI resolve the problem....

[rapscallion]

Megui, Misc tab, under V.U.I. there is a box checked for "Force pic_struct" for all the Blu-ray presets.

Is this the same effect as the command line --pic-struct ?

[Zathor]

Only two minor fixes:
2008 [Worker] fixed "shut down worker when finished local queue"
some cosmetics
2007 [Nero AAC Encoder] fixed cosmetic problem with wrong bitrate values in the configuration dialog. Bug #3286672

[Lighto]

Megui, Misc tab, under V.U.I. there is a box checked for "Force pic_struct" for all the Blu-ray presets.

Is this the same effect as the command line --pic-struct ?

I am pretty sure the command line --pic-struct is added when "Force pic_struct" is checked.

[rapscallion]

I am pretty sure the command line --pic-struct is added when "Force pic_struct" is checked.

No, it's not visible in the command line, that's what prompted me to ask.

[Lighto]

No, it's not visible in the command line, that's what prompted me to ask.

???
http://i.imgur.com/XqkaJ.png

[rapscallion]

As I stated , Blu-ray presets...not divx, not there :

[Lighto]

As I stated , Blu-ray presets...not divx, not there :

It would seems that -tff includes pic-struct in it.
pic-struct
Default: Not Set
Force sending pic_struct in Picture Timing SEI.
Implied when you use --pulldown or --tff/--bff.
Recommendation: Default

[rapscallion]

It would seems that -tff includes pic-struct in it.
Implied when you use --pulldown or --tff/--bff.

You know, it's funny Lighto, I read that in the MeWiki but didn't interpret that "implied" meant "turned on".

Thanks for the clarification!

[doc_dvxm]

My problem with DGAVCDecDI still persist.

Sometimes MeGUI opens properly (I don't know why ??? ), but usually going to crash...

I've switched to the stable server and it update to 1939 (svn), but the result was same. Just like the 2008 (svn) update...

Btw, When I am using same script from the x264 commandline, it working properly...

Now I'm sure that it is a MeGUI problem... Or it is MeGUI - DGDAVCDecodeDI incompatibility ???

What's wrong??

[rtjnyoface]

After a couple times (or maybe a certain time frame) of opening explorer to find files, for instance a d2v file in a folder, megui freezes and I have to delete the process and restart it to continue the work. It only recently started happening after I updated from 1998 if I remember correctly. I've seen that it may be due to ffms but that thread I read was like a year ago. Anyone know what might be the issue, had seen the issue, or know if its' one currently being rectified?

Win7 x86
Megui 2008

[Zathor]

2009 [MediaInfo] adjustment for recent mediainfo builds
and 2008 has been released as stable

[MenotBumba]

Could you please update x264 to 1937 ? :)

[Zathor]

No, not at the moment. I need to prepare the gui first for the --bluray-compat switch.

[Renzz]

There is a slight bug in audio encoding using Nero AAC and using FFAudioSource on the profile. I'm encoding .mpa files to .m4a, and when I try to delete the original .mpa afterwards, Windows tells me it's still in use by Megui. I have to completely close Megui to release it. Note: this only seems to affect the X64 version of Megui - as far as I can see the X32 version correctly closes the file (or at least lets me delete it).

[MenotBumba]

I noticed a bug which occurs from what I saw only when you are encoding a really long file. I tried to encode a 5 hours long file with MeGUI 2009, but when the audio encoding starts in the box where the file duration is, instead of five hours there says that the file is long only 2 hours. So I went back to 1989, and I did the same encode again, and the audio was correctly recognized as 5 hours long. I guess that this bug has something to do with this :

2004 [Audio Encoder] added option to choose the preferred decoder. Feature request #3053195
in case the preferred decoder cannot decode the input file the others will be tried, too
default order: NicAudio, FFAudioSource, DirectShow

[Lighto]

@MenotBumba
Change the decoder to to FFAudioSource or DirectShow in the audio presets config dialog.

[Zathor]

I noticed a bug which occurs from what I saw only when you are encoding a really long file. I tried to encode a 5 hours long file with MeGUI 2009, but when the audio encoding starts in the box where the file duration is, instead of five hours there says that the file is long only 2 hours. So I went back to 1989, and I did the same encode again, and the audio was correctly recognized as 5 hours long.
:logfile:

[tebasuna51]

@MenotBumba
Change the decoder to to FFAudioSource or DirectShow in the audio presets config dialog.
For what?
NicAudio don't have problems with long files.

[Lighto]

For what?
NicAudio don't have problems with long files.

Sorry, I am not familiar with NicAudio.
Thanks for letting me know.:)

IIRC, svn 1989 uses DirectShow for the audio decoding.
So I figured MenotBumba's audio problem will be solved by changing to the audio decoder svn 1989 was using.:p

[Zathor]

Without the log content the problem cannot be investigated and solved.

[tebasuna51]

Like Bluedan say here http://forum.doom9.org/showthread.php?p=1497623#post1497623 , with the actual version of oggenc2 the remap line:
6==Audiochannels(last)?GetChannel(last,1,3,2,5,6,4):last
is not more needed.

Please delete the line in next update.

[Zathor]

Thanks Tebasuna - the line has been removed.

[Jeremy Duncan]

I have a feature request.

I have made a avs file that makes a Trim list, see file it creates:



### scene change list ###
directshowsource("C:\Users\Rudolf\Desktop\121819956.vc1")
trim(0,93) +\
trim(94,153) +\
trim(154,197) +\
trim(198,249) +\
trim(250,287) +\
trim(288,331) +\
trim(332,398) +\
trim(399,420) +\
trim(421,467) +\
trim(468,485) +\
trim(486,512) +\
trim(513,526) +\
trim(527,540) +\
trim(541,592) +\
trim(593,653) +\
trim(654,688) +\
trim(689,714) +\
trim(715,787) +\
trim(788,848) +\
trim(849,925) +\
trim(926,942) +\
trim(943,995) +\
trim(996,1036) +\
trim(1037,1075) +\
trim(1076,1150)


However, when I load this as a avs file into megui I can only get one file outputted, according to Gavino, I have tried as well.

My feature request is that I load my trim file and get multiple output files, so each line of trim outputs a video clip.
Maybe this is a tool request?

[Lighto]

The ffms package on the development server isn't extracting in the right folder.
http://i.imgur.com/Mce8b.png

[Zathor]

Thanks & fixed

[Betsy25]

What about including a working DVD subtitle ripper (like VSRip) ?

I mainly use MeGUI now to convert media, but i need to start up the abandoned Staxrip in order to use VSRip to rip working subs (.idx) that I then can include in a MeGUI encoding.
:thanks:

[Lighto]

@Betsy25
Is VobSubber not working for you?
Personally, Both VobSubber and VSRip doesn't get my DVD subtitle color right for me, the subtitles turns out in some dark color for some reason.

[AMED]

Is anybody else having issues with aborting a single x264 encoding job when 2 workers are being used?

The whole MeGUI freezes up as well as the 2 job status windows. Looking under the processes tab in task manager, it shows that only 1 instance of x264_64.exe is running.

I have been waiting over 10mins for MeGUI to unfreeze, so it looks like i have to kill it manually in taskmanager.

By freeze i don't mean that MeGUI says it's not responding, you just can't click on anything in the windows or even move them.

[Lighto]

@AMED
The last time MeGUI was frozen with 2 workers for me was because I fed a video file as MeGUI's audio input.

[AMED]

Thanks for the reply Lighto,

naa thats not the problem, all the audio encodings are done with the HD stream extractor. So the only thing in the Queue is the x264 encode and then the mkv muxing.

So basically have 2 x264_64 jobs running at the same time and then on one of the encoding status windows press abort.

[Lighto]

Thanks for the reply Lighto,

naa thats not the problem, all the audio encodings are done with the HD stream extractor. So the only thing in the Queue is the x264 encode and then the mkv muxing.

So basically have 2 x264_64 jobs running at the same time and then on one of the encoding status windows press abort.

Just to add on, overwriting existing files in the second worker causes MeGUI to freeze up as well.

Edit:
It would seems that MeGUI works fine when handling smaller files.

[flebber]

What about including a working DVD subtitle ripper (like VSRip) ?

I mainly use MeGUI now to convert media, but i need to start up the abandoned Staxrip in order to use VSRip to rip working subs (.idx) that I then can include in a MeGUI encoding.
:thanks:

Abandoned? Stax has always taken periodical breaks between development.

[AMED]

i know this has been looked at before, but i have once again received an out of memory error when using MeGUI.


LINK (http://pastebin.com/PpgNqTwK) to the MeGUI log.

Currently MeGUI is using 987,300K in task manager when the error appeared

[Zathor]

http://forum.doom9.org/showthread.php?p=1494757#post1494757

When it's done it will be released :rolleyes:

EDIT: The problem is not --bluray-compat - the problem is that there is a bigger change partly implemented which interferes with this change. Should be ready soon but I will not give you any ETA or details about the the other change. So stay tuned.

[Poutnik]

Have you considered integrating of ProjectX among the tools set as preindexing step ?
It is useful for DVB-X origin sources, performing MPG PS/TS demuxing to M2V + MP2 or WAV, together with fixing DVB transmission errors and related A/V sync errors.

[Poutnik]

There is an interlace related source type analysis in AVS source creator.
It works well, but seems to me corrupting the processing work-flow.
It should be done after cutting e.g. by AVS cutter, not before.

If the source is DVB capture, present advertisements are often interlaced, but movie itself is progressive.
At AVS creation steps, analysis will mark the source as partly interlaced, but the interlaced parts are cut at the following cutting step.

So I think the analysis should be within MeGUI moved somewhere else.

Edit: OR - the cutting invokable within AVS creator, before running analysis.

[Zathor]

2019 [Lame] changed encoding modes to reflect valid values
Warning: review custom lame presets as there is no full update path
2018 [x264] enhanced help
[x264] small fixes/improvements
2017 [File Indexer] added MKV audio demuxer for FFMS
2016 [Update] enable 2010 only for debug builds
2015 [x264] added --bluray-compat option (requires x264 rev 1935+)
[x264] changed --open-gop handling (requires x264 rev 1935+)
[x264] added target playback device option
this option restricts or enforces x264 parameters if necessary
[x264] several adjustments
2014 [OggVorbis] removed channel remapping as it is not needed anymore
2013 [M2TS Muxer] fixed splitting option. Bug #3294210
fixed m2v input handling
2012 [File Indexer] disable Audio group box when FFMS is used because this indexer cannot extract audio streams
2011 [MediaInfo] introduce "Core" alias for DTSHD/DTSMA
2010 [Update] don't raise an update if the existing version number is higher than the latest version

Please test especially the x264 device option as a lot of code had to be changed.

[Lighto]

2019 [Lame] changed encoding modes to reflect valid values
Warning: review custom lame presets as there is no full update path
2018 [x264] enhanced help
[x264] small fixes/improvements
2017 [File Indexer] added MKV audio demuxer for FFMS
2016 [Update] enable 2010 only for debug builds
2015 [x264] added --bluray-compat option (requires x264 rev 1935+)
[x264] changed --open-gop handling (requires x264 rev 1935+)
[x264] added target playback device option
this option restricts or enforces x264 parameters if necessary
[x264] several adjustments
2014 [OggVorbis] removed channel remapping as it is not needed anymore
2013 [M2TS Muxer] fixed splitting option. Bug #3294210
fixed m2v input handling
2012 [File Indexer] disable Audio group box when FFMS is used because this indexer cannot extract audio streams
2011 [MediaInfo] introduce "Core" alias for DTSHD/DTSMA
2010 [Update] don't raise an update if the existing version number is higher than the latest version

Please test especially the x264 device option as a lot of code had to be changed.

Thanks for the updates!:)
:thanks:

Edit:
PSP profile not working. B-Pyramid needs to be disabled in order for the video to work.

Personally I can live without the target playback device option since it can't be modified by the user and new profiles cannot be added by the user also.
It's like a profile within a profile.:o

[Zathor]

PSP profile not working. B-Pyramid needs to be disabled in order for the video to work.
Will be added in the next build

Personally I can live without the target playback device option since it can't be modified by the user and new profiles cannot be added by the user also.
It's like a profile within a profile.:o
There will be no device preset anymore from the update server. The checks are much more comprehensive than the old device presets. It is still possible to create own presets of course.

[Lighto]

There will be no device preset anymore from the update server. The checks are much more comprehensive than the old device presets. It is still possible to create own presets of course.

So there won't be any more MeGUI presets updates from the server?
The device presets in the x264 dialog will be fixed by the dev and the user can only add custom MeGUI presets?

If so, I feel that only widely used device preset such as blu-ray, AVCHD, DXVA, DivX Plus HD, etc should be included in the x264 config dialog.
Including the preset for G1, N8, N900, etc feels like a waste of space.

[Cela]

deleted

[Sharktooth]

So there won't be any more MeGUI presets updates from the server?
The device presets in the x264 dialog will be fixed by the dev and the user can only add custom MeGUI presets?

If so, I feel that only widely used device preset such as blu-ray, AVCHD, DXVA, DivX Plus HD, etc should be included in the x264 config dialog.
Including the preset for G1, N8, N900, etc feels like a waste of space.
megui device presets are no longer necessary since x264 now includes devices presets. megui will support them as it is know to support the other x264 options (read as: it will support most or all of them). just configure the encoder from the config window and select the device you want to play the video on.
so, yes, they will be ADDED by the devs (im still confident i can be back working on the megui source... one day...) as long as they're an x264 option. on the other hand you can still create specific device presets setting the encoder advanced options accordingly to the device needs.

[Lighto]

@Sharktooth
So MeGUI devs are more or less preparing for x264 devices presets by including the devices drop down list in the x264 config dialog.
When the presets are ready, the devs can simply update with the device preset switch. Is that right?

[Zathor]

Yes, that is correct.

The new system even gives more flexibility in the limits of a specific device as the old system as the settings are not fixed anymore. e.g. the reference frames are not fixed anymore to 4 (for Blu-ray) - instead based upon the x264 preset, the video source / resolution, the user chosen value, ... the best value will be used and therefore may vary between 0 and 6.