Log in

View Full Version : MeGUI development


Pages : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 [84] 85 86 87 88 89 90 91 92

[ReX]
1st November 2008, 12:56
I don't know if it was a download error here, but on last x264 updated build (1016 - Skystrife's patched build) is missing the file pthreadGC2.dll.

If anyone have this problem, download this DLL here: ftp://sourceware.org/pub/pthreads-win32/prebuilt-dll-2-8-0-release/lib/

Kurtnoise
1st November 2008, 13:53
Will the autoupdater follow a HTTP 301/302 redirect without breaking in current versions of MeGUI?
I don't think so but can't you try by yourself ?

Fishman0919
1st November 2008, 14:28
Getting an error after updating to x264 1.016.

Vista error "x264 has stopped working"

skystrife
1st November 2008, 16:06
Getting an error after updating to x264 1.016.

Vista error "x264 has stopped working"

This is my fault, I had my msys environment set up incorrectly for the build (I had it set to my testing environment and stuff borked). I'll post a fixed build soon. Just download that and replace the x264 you have in your megui directory (Sharktooth will replace the build in the autoupdate but he's not online atm).

Fixed: http://skystrife.com/x264/x264.1016.modified.02.exe

Fishman0919
1st November 2008, 19:44
Thank You

Sharktooth
1st November 2008, 20:30
I don't think so but can't you try by yourself ?
it wont work.

saint-francis
2nd November 2008, 03:57
This is my fault, I had my msys environment set up incorrectly for the build (I had it set to my testing environment and stuff borked). I'll post a fixed build soon. Just download that and replace the x264 you have in your megui directory (Sharktooth will replace the build in the autoupdate but he's not online atm).

Fixed: http://skystrife.com/x264/x264.1016.modified.02.exe

Strange. I just encoded a movie with it and didn't have any problems at all. :confused:

Sharktooth
2nd November 2008, 06:04
probably you have (like me) the pthread lib in your windows\system32 folder (or in the path)

Kurtnoise
2nd November 2008, 08:31
it wont work.
why it won't work ? what's the problem ? ...just by curiosity coz I'm a simple newbie about http related stuff. :p

hydro
2nd November 2008, 10:25
I find switching between x264 profiles in the x264 configuration dialog tends to throw a lot of annoying errors in the event handlers.
I'm hoping the fix is as simple as disabling the event handlers during profile switch but has anyone tried this before?

This combination seems to work for my profiles and the few standard profiles I have installed (Insane + portable devices): http://pastebin.com/m528507a7

Kurtnoise
2nd November 2008, 14:43
the init type for "updating" is missing...

hydro
2nd November 2008, 15:24
It's a change to visibility of updating in VideoConfigurationPanel I forgot to include: http://pastebin.com/m610e8ec4

Kurtnoise
2nd November 2008, 17:33
ok...it seems to work fine for me too. :)

Sharktooth
2nd November 2008, 20:16
why it won't work ? what's the problem ? ...just by curiosity coz I'm a simple newbie about http related stuff. :p
coz megui is not a web browser... ;)
the http responses should be manually handled to make the redirect work...

check
4th November 2008, 03:34
can you tell me what functions are called? I'll have a read through the documentation. If it's possible to move the location of the autoupdate files I'd like to do so, but I don't want to break old clients.

Sharktooth
4th November 2008, 15:42
dont worry, that's why we have 2 auto-update servers by default and megui randomly chooses one of them at every startup for updating.
just tell us the new url and we'll change it.

Sharktooth
6th November 2008, 03:06
0.3.0.3008
- (sharktooth) [AviSynthWindow.cs] Default resize values now equal to the source file resolution values.
- (sharktooth) [x264Encoder.cs] --filter -> --deblock
- (ateeq) [x264Settings] Add MacroBlockOptions
- (ateeq) [x264ConfigurationPanel] set/get MacroBlockOptions to/from profiles

0.3.0.3007
- (ateeq) [x264ConfigurationPanel] set updating to avoid triggering spurious events during x264 profile switching
- (ateeq) [VideoConfigurationPanel] Change visibility of updating variable
- (ateeq) [AviSynthWindow] Remember current frame unless loading a new video
- (ateeq) [VideoPlayer] Add startFrame parameter to loadVideo to allow starting with specific frame
- (ateeq) [SettingsForm] Add missing clearDefaultOutputDir EventHandler link
- (ateeq) [AutoEncodeWindow] Change muxedOutput to FileBar
- (ateeq) [FileBar] Set File Dialog InitialDirectory to where current Filename is located
- (ateeq) [JobControl] Allow dependent jobs to run on JobStatus.SKIP
- (ateeq) [VideoPlayer] Help C# with memory management by disposing bitmap as soon as we're finished with it
- (ateeq) [JobControl] Remove job from parent/required job's EnabledJobs list (fixes #2124850)
- (ateeq) [AviSynthWindow] Delay OpenScript until ASW is closed to prevent ARChooser race condition with VideoPlayer
- (ateeq) [ARChooser] Fix to keep user selected ARs

Sharktooth
11th November 2008, 16:50
0.3.0.3009
- (sharktooth) [AVSCreator] Resize filter now disabled by default. AVS presets settings will not be overridden though.
- (ateeq) [x264ConfigurationPanel] Fix doMacroBlockAdjustments for P4x4 compliance at Level 3+ when All option is selected.
i uploaded into the auto-update server a default *scratchpad* AVS preset to disable the resize by default for older installations.
the installer is also available: https://sourceforge.net/project/showfiles.php?group_id=156112

Audionut
12th November 2008, 13:58
IMHO when setting Macroblock options to custom, I should be able to select P4x4 regardless if it breaks compliance.

I appreciate a warning, but hate being forced. :)

Thanks.

hydro
12th November 2008, 19:51
The previous behavior was to reset the level to unrestricted if you tried to set p4x4 so you can achieve the same by setting level to unrestricted (after the next update to fix a stupid bug) before trying to set p4x4?

Audionut
13th November 2008, 04:32
so you can achieve the same by setting level to unrestricted

No you can't. P4x4 is not selectable unless the AVC Level is 2.2 or lower.

P4x4 works fine with x264 and level 4.1 on PS3.

tomcat_
13th November 2008, 08:06
[code]0.3.0.3008
- (sharktooth) [AviSynthWindow.cs] Default resize values now equal to the source file resolution values.

I have noticed that now on the music dvds that i encode the resolution defaults to 720 while before it was at 680....

might sound a silly question as i'm not well up with the resolutions and such....but does this mean that before i was encoding or resizing at 680 where the source was 720?

thanks

Dark Shikari
13th November 2008, 08:07
Please stop trying to force false compliance... all levels allow p4x4.

Adub
13th November 2008, 09:00
@tomcat_
Yeah. The standard resolution for DVD's is 720.

tomcat_
13th November 2008, 10:21
so before the megui was defaulting at 680?

*edit* from what i understand aspect ratio is a hot subject...so reading a bit around...i'm very confused...so i guess i will have to read more...cause i have no clue what i have been encoding so far...as all the dvds were at 680 using the default settings of megui...

Adub
14th November 2008, 02:39
Yes, before MeGUI was defaulting to 640, or whatever it thought was best.

Edit: fixed to 640. oops.

Sharktooth
14th November 2008, 03:02
IIRC it was 640... and that was an arbitrary value, so i removed it.
a fix for the p4x4 thing has been committed. a new build is coming soon.

check
14th November 2008, 16:04
re: trac setup. I was hoping to set trac up on my main server (rather than a spare VM like it was) but it's proving complicated. More updates later this weekend.

Sharktooth
14th November 2008, 17:16
take your time, there is no hurry.

hydro
14th November 2008, 20:36
Please stop trying to force false compliance... all levels allow p4x4.

MeGUI used to reset Level to unrestricted if P4x4 was selected in levels > 3.1 or 3:

invalidLevelHelp = "P4x4 macroblocks are not allowed in level > 3 or in level 3 with B frames.";
I just took that for granted and changed it so you couldn't select P4x4 except <3.1 and unrestricted (ok I got the logic wrong in the current relase so you can't select p4x4 in unrestricted).

If it's related to MaxMvsPer2Mb http://forum.doom9.org/archive/index.php/t-125734.html, then I take it you are saying the check/restriction should be lifted for all levels as the likelihood of running into problems is negligible?

Sharktooth
15th November 2008, 16:06
0.3.0.3010
- (kurtnoise) removed CropDialog Form from projects files. This is not used anyway...
- (kurtnoise) revert rev805...shame on me (#2231667).
- (kurtnoise) [BeSplitter] one frame is missing for end value (#2283781)
- (kurtnoise) [BeSplitter] use dot instead of comma for start & end values (#2283781)
- (kurtnoise) updated MediaInfo library and its wrapper to the latest release (0.7.7.8)
- (ateeq) [x264ConfigurationPanel] Fix to correctly apply last P4x4 change to level 3.1 and unrestricted

hajj_3
17th November 2008, 17:56
please can you add ".mpa" to allowed extensions list in the open dialog box on bitrate calculator, there is .mp2 etc but no .mpa:

http://i33.tinypic.com/10nghgp.jpg

thanks.

Adub
17th November 2008, 19:37
That's a feature request. All feature requests need to go into the sourceforge page, or they will probably be ignored.

hajj_3
17th November 2008, 20:04
is it not a bugfix? as the audio encoding section of the main window can open .mpa files to encode to .mp4 etc so surely the bitrate calculator should be able to do this otherwise the bitrate wont be able to be calculated properly.

check
18th November 2008, 05:43
whatever it is, it's not what should go in this thread.

Dark Eiri
22nd November 2008, 02:15
Can I suggest something? I think it's well known that no MP4 splitters are able to fix negative audio delay.
I wonder if MeGUI could detect if the delay is negative, in the MP4 Muxer and delay the video instead. Wouldn't it fix the problem?

Kurtnoise
22nd November 2008, 08:44
nope...

If there is an audio delay, it should be "fixed" during your audio transcoding unless you use directly the muxer ?

Dark Eiri
23rd November 2008, 03:44
Oh, I didn't reencode the audio. I'm trying to encode some HDTV .ts, the audio already is AAC, so...

Kurtnoise
23rd November 2008, 11:03
this belongs to containers forum but...

did you try to mux directly your audio stream from the ts file ?

Dark Eiri
24th November 2008, 08:26
Demuxed it with DGindex and then added it to the MP4 Muxer inside MeGUI.
I mean, YAMB lets me delay the video, so the audio sync is fixed, I was thinking something like that for the internal MP4 Muxer.
I don't know if standalones can detect the video delay correctly, though...

Sharktooth
27th November 2008, 18:33
0.3.0.3011
- (ateeq) [VideoUtil] MediaInfo Track ID has changed to decimal for all tracks
- (ateeq) [ScriptServer] Add Spline64Resize option

~bT~
27th November 2008, 19:21
for those looking for the new resizer(s)

http://forum.doom9.org/showpost.php?p=958662&postcount=73

Kurtnoise
29th November 2008, 19:33
@Sharktooth: can you update the upgrade.xml file ? to have the yadif node in the avisynth deinterlacer subtree. Thanks...:)

like this one (http://kurtnoise.free.fr/index.php?dir=MeGUI/&file=upgrade.xml).

Sharktooth
1st December 2008, 03:02
why ?

Kurtnoise
1st December 2008, 09:33
as I said...in the updater, to have the yadif plugin in the avs deinterlacer subtree.

Currently, yadif is only in the root, not part of the avisynth filters.

Sharktooth
1st December 2008, 19:08
no, it's not possible. if you move yadif under avisynth section the file will be extracted in the avisynth plugin folder... and that's wrong coz it is a stdcall plugin and should not be placed in the avisynth plugin folder.

Kurtnoise
1st December 2008, 19:23
you can store yadif wherever you want...it's just LoadCplugin or Load_Stdcall_plugin the most important.

Sharktooth
1st December 2008, 19:36
if you move it under avisynth tree it will be stored in the avisynth plugin folder...

check
4th December 2008, 10:32
I believe yadif is no longer a weird plugin but is instead called normally. http://avisynth.org.ru/yadif/yadif.html

Adub
4th December 2008, 10:54
Nope, it's still "wierd". Read a little down on the page you linked to.

Implemented as Avisynth C-plugin (not regular Avisynth plugin).
Must be loaded with Load_Stdcall_plugin("yadif.dll") or LoadCplugin("yadif.dll") (not LoadPlugin !).