View Full Version : MeGUI: bug reports and feature requests
Pages :
[
1]
2
3
4
5
6
7
8
Zathor
5th December 2009, 12:42
The correct place for bug reports and feature request is the Project page, but if you want to discuss them first you can do it here. However remember: without opening a bug report or feature request at the project page it is likely that we forgot about it.
Project page
http://sourceforge.net/projects/megui/
Bug reports (http://sourceforge.net/tracker/?group_id=156112&atid=798476)
Feature requests (http://sourceforge.net/tracker/?group_id=156112&atid=798479)
Support (http://forum.doom9.org/showthread.php?t=105920)
Recommended installation instructions:
1. Download the recent MeGUI build: Download (http://sourceforge.net/projects/megui/files/latest/download)
2. Extract the file (recommended to not extract it in the program files directory - use e.g. C:\Tools\MeGUI)
3. Run the program megui.exe and let it update all necessary files
This build does not require write access outside of the program directory. Therefore it is easy to use in a more restrictive environment. It is even possible to have several versions installed independently.
[Moderator edit]The last included Avisynth+ version is 3.5 r3106, if you have installed a more updated versión (now 3.7...) you need check Options -> Main -> Always use the included AviSynth or replace the AvisynthWrapper.dll (https://forum.doom9.org/showthread.php?p=1913117#post1913117)[/Moderator edit]
Development Updates
If you want to have always the newest build please switch to the development update server in MeGUI. You can find this setting in
"Options\Settings\Extra Configuration\Auto Update" and switch to "Use development update server". Afterwards do an update check or restart MeGUI.
Zathor
5th December 2009, 16:08
- [ProgressWindow] added Windows 7 taskbar progress
Link removed. Please download above.
Please try this version on a OS before Windows 7 and without .NET 3.5 and post the result. The progress window "should" work without problems and of course without the taskbar progress but I can not test it myself.
prOnorama
5th December 2009, 16:30
@ Zathor: thanks a lot I will try it out. :)
PS: please do not use RapidShare alone for hosting, a lot of the time I get "There are no more download slots available for free users right now. " even if I want to download a small file. So I can't try it out now.
MediaFire is a good alternative.
Zathor
5th December 2009, 17:08
@ Zathor: thanks a lot I will try it out. :)
PS: please do not use RapidShare alone for hosting, a lot of the time I get "There are no more download slots available for free users right now. " even if I want to download a small file. So I can't try it out now.
MediaFire is a good alternative.
Thank your for the feedback. I have uploaded the file to mediafire.
j8ee
5th December 2009, 20:42
It crashes when I try to start it...
edit:
http://thumbnails23.imagebam.com/5877/c2278158764204.gif (http://www.imagebam.com/image/c2278158764204)
I think you get the idea without an error message translation.
box is XP SP3 32 bit, .net 1.1, 2.0 SP1, 3 SP2 and 3.5 SP1
Puncakes
5th December 2009, 21:10
You, my good sir, have my most heartfelt, and deepest thanks.
j8ee: It would be best if you provided some details as to the machine you're attempting to use it on(e.g OS, 32/64bit, .NET installed). Also, host your error image somewhere like http://imageshack.us/ and post the link to it, rather than waiting for a mod to approve it. I'm on Win7 32bit, with .NET 3.5 as well, so I can't provide much in the way of testing, but it certainly works great for me.
Once again, thank you very much, Zathor.
ncatt
5th December 2009, 22:13
Zathor Hi, thanks for this fixed version. Just a suggestion: do not put the files on rapidshare. In recent days I always see this message: "There are no more download slots available for free users right now. If you don't want to become a premium member, you might want to try again later." And if i try again later the same message pops up. It's annoying. Mediafire is much better. :thanks:
Zathor
6th December 2009, 01:41
It crashes when I try to start it...
I think you get the idea without an error message translation.
box is XP SP3 32 bit, .net 1.1, 2.0 SP1, 3 SP2 and 3.5 SP1
Thanks, it seems to be not working on non Windows 7 OS. Please use the build from the first post until I have a newer build. The version does not have any modifications in the progress window.
j8ee
6th December 2009, 02:02
Oh, now I saw that you wanted a test without .net 3.5. Anyway, 3.5 is an auto-update as far as I know, so most XP users have it.
Zathor
6th December 2009, 02:15
Oh, now I saw that you wanted a test without .net 3.5. Anyway, 3.5 is an auto-update as far as I know, so most XP users have it.
I added a few checks if the OS is Windows 7 (or above). Please try the new build again (it is in the first post).
Additionally I changed a small thing in profile handling
- [x264Config] the advanced settings will be applied to the command line independent of the advanced settings checkbox
quantum5uicid3
6th December 2009, 02:19
I didn't notice it at first, but it's still not saving the following settings after you create a new preset and close the x264 configuration dialog.
--ref
--bframes
--deblock
--no-cabac
--no-deblock
--ipratio
--pbratio
--deadzone-inter
--deadzone-intra
--qcomp
--aq-mode
--aq-strength
--psy-rd
--no-dct-decimate
and the --no-mbtree checkbox is not working properly
xp sp3 3.5 .net, someone confirm please.
Zathor
6th December 2009, 02:27
I didn't notice it at first, but it's still not saving the following settings after you create a new preset and close the x264 configuration dialog.
--ref
....
and the --no-mbtree checkbox is not working properly
xp sp3 3.5 .net, someone confirm please.
Did only a quick check with --ref. And yes, I can confirm the problem. On the other hand the --no-mbtree checkbox is working properly for me. In the fastest 3 presets --no-mbtree is always active and therefore it can not be activated (note to myself: disable the button if using these presets)
quantum5uicid3
6th December 2009, 02:44
yeah that was it with --no-mbtree, i just left the preset on fast and was going through all the settings one by one to see which saved and which didn't
Zathor
6th December 2009, 03:28
yeah that was it with --no-mbtree, i just left the preset on fast and was going through all the settings one by one to see which saved and which didn't
It should be fixed now and the build is in the first post. Please check if all settings can be loaded now.
quantum5uicid3
6th December 2009, 03:49
thanks, good work! the only thing left before testing more extensively, does "Credits Quantizer" still correspond to any x264 option (I don't see it doing anything and can find no reference in the command line options)? and the --rclookahead field still doesn't seem to change the commandline.
stax76
6th December 2009, 04:31
x264 GUIs involve complexity, some settings depend on other settings which again depend on other settings and sometimes it's very difficult to disable all controls accordingly. With such issues the first thing you would do is check the x264 docs on what other settings the setting depend taking also the settings of the preset and tuning into account. --rc-lookahead don't has dependencies and interactions documented so it's a simple bug.
quantum5uicid3
6th December 2009, 04:42
yeah i checked if it corresponded with mbtree or vbv settings, but it doesn't. "Credits Quantizer" apparently is only used if you "set the credit starting point in the preview window." overlooked it before, thanks.
j8ee
6th December 2009, 10:57
Using the build in the first post, I have the same crash as before. On my laptop I don't have the .net Swedish language packs installed, so the error message is in English this time.
XP SP3, .net 2.0 SP2, 3.0 SP2 and 3.5 SP1
http://thumbnails20.imagebam.com/5882/410d9158818147.gif (http://www.imagebam.com/image/410d9158818147)
Zathor
6th December 2009, 11:50
Using the build in the first post, I have the same crash as before. On my laptop I don't have the .net Swedish language packs installed, so the error message is in English this time.
XP SP3, .net 2.0 SP2, 3.0 SP2 and 3.5 SP1
(hopefully) finally fixed. Please try the new build. If not, please provide a few more details (which kind of job crashed, ...)
...and the --rclookahead field still doesn't seem to change the commandline.
I have changed the input handling in the new build. It did already changed the command line for me before, but maybe this change solves your problems.
j8ee
6th December 2009, 12:03
Seems to work now, I haven't been using it yet, but at least it starts! Nice work, many thanks!
edit: Hmm, disabling mb-tree isn't saved in a profile. It's checked when I load the profile again, and looking at the xml it says <NoMBTree>false</NoMBTree>.
edit 2: Correction - as far as I can see, none of my settings are saved at all. The changed settings are for ipod compliance: --profile baseline --level 3 --crf 20.0 --thread-input --ref 2 --vbv-bufsize 10000 --vbv-maxrate 10000 --no-mbtree --me umh --partitions p8x8,b8x8,i4x4 (which I think is the default, but I'm not quite sure)
edit 3: OK... it seems like loading the profile manually in the drop down menu in the config dialog brings up the correct commandline. I haven't made any test encodes to see if it's actually used yet, but I'll do that soon. Still, that the cabac checkbox does nothing makes me a little suspicious.
Zathor
6th December 2009, 14:08
edit: Hmm, disabling mb-tree isn't saved in a profile. It's checked when I load the profile again, and looking at the xml it says <NoMBTree>false</NoMBTree>.
edit 2: Correction - as far as I can see, none of my settings are saved at all. The changed settings are for ipod compliance: --profile baseline --level 3 --crf 20.0 --thread-input --ref 2 --vbv-bufsize 10000 --vbv-maxrate 10000 --no-mbtree --me umh --partitions p8x8,b8x8,i4x4 (which I think is the default, but I'm not quite sure)
edit 3: OK... it seems like loading the profile manually in the drop down menu in the config dialog brings up the correct commandline. I haven't made any test encodes to see if it's actually used yet, but I'll do that soon. Still, that the cabac checkbox does nothing makes me a little suspicious.
Both problems have been fixed (at least partially). Please try the new build and post again if any problem arise.
Cabac does nothing because in baseline profile it is already disabled. Please have a look at http://mewiki.project357.com/wiki/X264_Settings. If you find other settings which does not match with the GUI feel free to address them here.
bluebebe
6th December 2009, 17:32
thanks for the patch. everything is working fine now.
showergel
6th December 2009, 17:55
So as of today, it has been 42 days without a single code commit on MeGUI's Sourceforge.net portal. This sudden stop by all members of the team seemingly has the symptom of some argument/disagreement.
This morning I looked at x264.nl and MeGUI has been removed from their home page. Hmmmm...
Anyway, if this is really going to be the next evolution of MeGUI, then perhaps you can check the code out of MeGUI's SVN and start a new project page. You'll also get hosted there and won't have to worry about posting to rapidshare, etc.
There is precedent for this; ffdshow became ffdshow-tryouts on sourceforge.
Cisco7
6th December 2009, 20:56
I hope Kurtnoise and his co-workers will continue their incredible work on MeGUI or maybe qualified people could take care of the project and his evolution. Others GUIs are so annoying, smartless. MeGUI has been made by the users for the users. Please keep up your bloody good work, please keep us informed of your intention.
Zathor
7th December 2009, 01:25
MeGUI has so much potential to be the universal GUI for many aspects of multimedia encoding. The only purpose of my builds is to keep the project up and running (more or less) until the hard time is over and Kurtnoise or another one of the staff will continue their work. Maybe a few of my modifications are helpful for them.
I have no intention to take over this project. Beside a lack of time the most important thing is that I know that my programing skills are good enough for easy things in a supporting role - but way too weak for such a project in general.
I do not know why the project is on hold and I do not want to know it. There are surely reasons why this happened and why it has not been spread widely. My only hope is that the project has been suspended and not terminated.
Best wishes!
mozzle
7th December 2009, 04:30
You've done a good thing here, Zathor.
Thank you.
Triccotracco
7th December 2009, 10:19
Good work Zathor! Thank you very much!
:thanks:
Zathor
7th December 2009, 14:04
- [HDBDStreamExtractor] fixed a crash bug
- [HDBDStreamExtractor] input and output path will be preselected if the window stays open
- [BitrateCalculator] added experimental M2TS support
The M2TS support for the calculator is experimental and is based upon the "6 percent rule" (http://forum.doom9.org/showthread.php?p=1223719). Because this is only an educated guess I appreciate your feedback.
Additionally I have added a x264 BluRay profile as an example. The profile is based upon http://forum.doom9.org/showthread.php?t=149711 and http://mewiki.project357.com/wiki/X264_Settings. The profile has the goal to fulfill the bluray specs and be playable on most standalone players. A few remarks:
--nal-hrd requires a patched x264
--b-pyramid strict can not be aplied while mbtree is enabled but it should work sometime in the future. Please ignore the warning in the log.
The profile has been created as I understand the profile management should work. Feel free to start a discussion if you think that it should work the other way around. The custom command line "locks" the settings you want to force while you can change the quality/speed with the preset slider. The "advanced settings" tabs have been disabled in order to not confuse the more inexperienced users.
JoeH
7th December 2009, 17:40
I hope Kurtnoise and his co-workers will continue their incredible work on MeGUI or maybe qualified people could take care of the project and his evolution. Others GUIs are so annoying, smartless. MeGUI has been made by the users for the users. Please keep up your bloody good work, please keep us informed of your intention.
+1. Thanks to Kurtnoise, Sharktooth and team for the single most useful X264 tool around. We all look forward to seeing it continue to thrive!
Warbucks81
7th December 2009, 19:47
- [HDBDStreamExtractor] fixed a crash bug
- [HDBDStreamExtractor] input and output path will be preselected if the window stays open
- [BitrateCalculator] added experimental M2TS support
The M2TS support for the calculator is experimental and is based upon the "6 percent rule" (http://forum.doom9.org/showthread.php?p=1223719). Because this is only an educated guess I appreciate your feedback.
Additionally I have added a x264 BluRay profile as an example. The profile is based upon http://forum.doom9.org/showthread.php?t=149711 and http://mewiki.project357.com/wiki/X264_Settings. The profile has the goal to fulfill the bluray specs and be playable on most standalone players. A few remarks:
--nal-hrd requires a patched x264
--b-pyramid strict can not be aplied while mbtree is enabled but it should work sometime in the future. Please ignore the warning in the log.
The profile has been created as I understand the profile management should work. Feel free to start a discussion if you think that it should work the other way around. The custom command line "locks" the settings you want to force while you can change the quality/speed with the preset slider. The "advanced settings" tabs have been disabled in order to not confuse the more inexperienced users.
Thanks for the patched build. I assume this same profile would be good for creating MKV's for media player type devices.
Zathor
7th December 2009, 20:36
Thanks for the patched build. I assume this same profile would be good for creating MKV's for media player type devices.
Yes, every device that’s able to play BluRay compliant streams should be able to play back these files. At least it did work for me in the past for PS3, some standalone players and my streaming capable TV. Nevertheless there may be devices where you have to use a more restrictive profile (e.g. limit vbv bitrate). And you should not crop the files because some devices have problems if its is not 1920x1080 or 1280x720.
j8ee
7th December 2009, 20:51
Profiles are not deleted, and --ref 2 is not saved for me in a profile, it goes back to default 3 (it says 2 in the xml though). edit: After the fourth restart and manual deletion of some profiles --ref 2 is loaded in the profile.
Zathor
7th December 2009, 21:00
Profiles are not deleted, and --ref 2 is not saved for me in a profile, it goes back to default 3 (it says 2 in the xml though). edit: After the fourth restart and manual deletion of some profiles --ref 2 is loaded in the profile.
I can reproduce both problems. The deletion is fixed but I will upload a new build only after I have found the second problem.
Zathor
7th December 2009, 21:45
Profiles are not deleted, and --ref 2 is not saved for me in a profile, it goes back to default 3 (it says 2 in the xml though). edit: After the fourth restart and manual deletion of some profiles --ref 2 is loaded in the profile.
Both problems have been addressed in the build below.
Because of the greater changes regarding the file handling I do not want to change the link in the first post at the moment.
Link removed. Please have a look at the first posting.
- [MeGUISettings] change the default auto update server list to development
- [MeGUISettings] the update_cache location has been changed to a sub dir of the program dir
- [MeGUISettings] the avisynth plugin location has been changed to a sub dir of the program\tools dir
- [AviSynthWindow] + [AvisynthWrapper] LoadPlugin will be called for every DLL in the megui avisynth plugin dir
- [x264Config] changed the order the settings will be applied initially
This build does not require anymore write access outside of the program directory. Therefore it should be now much easier to use it in a more restrictive environment. It is even possible to have several versions installed independently.
Because I do not know if this is the way to go I would like to have feedback. The next step would be to disable the manual selection of the update_cache, avisynth plugin dir and maybe all other tools which will be installed automatically.
By the way: it is now possible - and I recommend it - to extract the zip file in an empty directory. It will be updated automatically through the development update server. Afterwards you have to update a few files manually (e.g. x264, mkvtools, eac3to, ...).
SacredCultivator
8th December 2009, 00:38
Thanks for this patched build, my question is in regard to the update server... Even under Development, which server would you be using?
kool
8th December 2009, 06:01
Thank you Zathor for this great work,
A question, I'm on Win 7 32 Bit OS and don't have meGUI and Avisynth install yet, now when I want to install meGUI, which version you recommend Win 7?
Thanks in advance.
Zathor
8th December 2009, 06:33
Thanks for this patched build, my question is in regard to the update server... Even under Development, which server would you be using?
I have not changed the servers in any way and I use at the moment the first one. But both servers seems to have identical files. Nevertheless you have to update a few files yourself (most important x264.exe and so on).
A question, I'm on Win 7 32 Bit OS and don't have meGUI and Avisynth install yet, now when I want to install meGUI, which version you recommend Win 7?
Avisynth 2.5.8 and the MeGUI build posted above (http://forum.doom9.org/showthread.php?p=1350501#post1350501)
JoeH
8th December 2009, 08:53
Avisynth 2.5.8 and the MeGUI build posted above (http://forum.doom9.org/showthread.php?p=1350501#post1350501)
I just installed this - it works GREAT! Thanks!
Here are the installation instructions I followed. As I had a few difficulties getting it installed, and finally found a safe and sure method, I thought I'd post it here:
1. Install the standard version 1056 from SourceForge
2. Update all parts using the "Stable" servers except the 1056 core
3. Change update server to development. Update all parts again except the 1056 core (if you do this without doing step 2 first you will get an error).
4. Copy the files that Zathor has prepared and select replace all.
When you open up MeGUI you will have a fully functional 1057 install, with full support for the new X264 features! Fantastic!
Zathor - thanks for your hard work. Here is a small feature request. I always ouput MKV files, but MeGUI always defaults to MP4 on the main screen. It would be great if MeGUI would save the last selected format, or had an option to set the default.
szabi
8th December 2009, 09:00
Also many :thanks: for it.
nakTT
8th December 2009, 09:15
Zathor - thanks for your hard work. Here is a small feature request. I always ouput MKV files, but MeGUI always defaults to MP4 on the main screen. It would be great if MeGUI would save the last selected format, or had an option to set the default.
You can set MKV as default by going to:
Options>Settings>Extra Config>Configure Auto Encode Default>
And choose the container that you like.
Zathor
8th December 2009, 09:30
Here are the installation instructions I followed. As I had a few difficulties getting it installed, and finally found a safe and sure method, I thought I'd post it here:
1. Install the standard version 1056 from SourceForge
2. Update all parts using the "Stable" servers except the 1056 core
3. Change update server to development. Update all parts again except the 1056 core (if you do this without doing step 2 first you will get an error).
4. Copy the files that Zathor has prepared and select replace all.
When you open up MeGUI you will have a fully functional 1057 install, with full support for the new X264 features! Fantastic!
Thanks for your reply.
With the newest build it is even easier to install:
1. Install Avisynth 2.5.8 (if not already installed)
2. Extract my build to a new/empty directory
3. Run the program and let it update all necessary files from the development server.
4. Update some files manually (x264.exe, ...)
nakTT
8th December 2009, 11:20
Thanks for your reply.
With the newest build it is even easier to install:
1. Install Avisynth 2.5.8 (if not already installed)
2. Extract my build to a new/empty directory
3. Run the program and let it update all necessary files from the development server.
4. Update some files manually (x264.exe, ...)
May I know which one U mean by "newest build"? Is it the one at the 1st post or the one at the 2nd page?
:thanks:
forum king
8th December 2009, 11:23
thanks mate
i have used the latest development build of urs ..
but tell me when i usesd to use 1051 with unrestricted 2 pass profile the settings were that of SLOWER
in mean like this :
program --profile high --pass 2 --bitrate 1000 --stats ".stats" --ref 5 --b-adapt 2 --b-pyramid --direct auto --deblock -1:-1 --trellis 2 --partitions all --me umh --thread-input --output "output" "input"
but in this one ( the new patched 1057 build the settings in that same profile are FAST..
program --profile high --preset fast --pass 2 --bitrate 1000 --stats ".stats" --thread-input --deblock -1:-1 --no-dct-decimate --output "output" "input"
what should be done ( does it mean that in the new megui build and x264 build SLOWER stuff is more faster or i need to drag the slider to slower to get the same settings.. and quality as that of unrestricted 2 pass
Triccotracco
8th December 2009, 11:49
May I know which one U mean by "newest build"? Is it the one at the 1st post or the one at the 2nd page?
:thanks:
The one in the first page, is true that at 2nd page there is a newer version but with a lot of changes, if I understand well.
Also for me patched 1057 version works fine & faster (used with x264 rev.1360 Jeeb's build)
Thank you again!
forum king
8th December 2009, 11:52
The one in the first page, is true that at 2nd page there is a newer version but with a lot of changes, if I understand well.
its very clearly mentioned on page 1
Stable build
http://www.mediafire.com/download.php?hj23mmmlmux
Development build with the additional changes below
http://www.mediafire.com/download.php?mfwnemetzt4
i have used the developmemnt build and its working great...
nakTT
8th December 2009, 12:32
The one in the first page, is true that at 2nd page there is a newer version but with a lot of changes, if I understand well.
Also for me patched 1057 version works fine & faster (used with x264 rev.1360 Jeeb's build)
Thank you again!
I see. I have just downloaded the unpatched one.
I'm interested to know about the "faster" bit for the patched 1057. Hope you can share your experience in a little bit detail.
:thanks:
quantum5uicid3
8th December 2009, 12:46
better solution...
forum king
8th December 2009, 12:58
well guys :( i am giving up
looks like i cant use the latest megui builds and the benefits of x264.
i have done everything as was said here and at the troubleshooting thread..
but it just wont work out..
i used the latest build by Zathor ( the 2nd one ) and installed it in a separate folder..
used unrestricted 2 pass HQ with SLower settings
it will do the first pass and give a STANDARD ERROR STREAM error upon second always..
sometimes the same error on first pass as well..
can someone please please please guide me how should i go about it all.. i have been trying to do this from last 3 days in TOTALO vain.
it looks i ll have to go back to 1051 :(
quantum5uicid3
8th December 2009, 13:02
stop trying to use the old presets. theyre no longer applicable
forum king
8th December 2009, 13:04
stop trying to use the old presets. theyre no longer applicable
o damn !!!
then which one is equivalent to unrestricted 2 pass now ..
i need something equivalent to that with no blurred edges and no pixelations at all.
thanks
quantum5uicid3
8th December 2009, 13:08
your gonna have to create your own presets, because nobody has taken time to do so yet. putting the preset slider on "slower", change the mode to automated twopass, uncheck the turbo, and entering the bitrate will be pretty damn close to what you were doing before
do what i said in my post above, so you can get all the old junk out of the way. you'll have a fresh new megui with no presets, then use this information to create your own presets based on your needs.
http://mewiki.project357.com/wiki/X264_Settings
you don't need to understand all of it, the default values and the presets built into x264 is all you need to be aware of
here's the settings you need if you want compatibility with a certain device
http://forum.doom9.org/showthread.php?t=149711
forum king
8th December 2009, 13:13
your gonna have to create your own presets, because nobody has taken time to do so yet. putting the preset slider on "slower", change the mode to automated twopass, uncheck the turbo, and entering the bitrate will be pretty damn close to what you were doing before
do what i said in my post above, so you can get all the old junk out of the way. you'll have a fresh new megui with no presets, then use this information to create your own presets based on your needs.
http://mewiki.project357.com/wiki/X264_Settings
ok as you say dear Sir !!! :)
but if i am right turbo used to be on in the past ,
BTW i am kinna noob in all this , setting it up would be so damn diff for me..
cant i just set it up as it was earlier in the unresticted 2 pass .. i have screenshotts of the 1051 version presets settings,
EDIT also , u said first to install 1056 then ur build ..
do we have to update 1056 first and then install ur build or how ?
also the 1309 x264 is there in ur update should i also replace this with 1360 from x264.nl
please forgive me noobiness , but my head is now aching with all this :P
regards
Glenn
quantum5uicid3
8th December 2009, 13:19
turbo turns the options way down for the first pass. what i'm telling you is that the defaults in conjunction with presets built into x264 really replace the need for sharktooth's presets. setting up x264 is nowhere near as complicated as it was before.
do you even need to hit a specific file size?
kool
8th December 2009, 13:22
a very 1th error I get under Win 7, I have installed as Zathor says
With the newest build it is even easier to install:
1. Install Avisynth 2.5.8 (if not already installed)
2. Extract my build to a new/empty directory
3. Run the program and let it update all necessary files from the development server.
4. Update some files manually (x264.exe, ...)
Error 1: happen when I select all profile and hit on import.
http://i49.tinypic.com/3160nev.png
Error 2: same as error 1
http://i46.tinypic.com/vsm683.png
Error 3 & 4 at the same time when I want to close meGUI.
http://i46.tinypic.com/nlyjcy.png
http://i49.tinypic.com/20az5g8.png
forum king
8th December 2009, 13:24
turbo turns the options way down for the first pass. what i'm telling you is that the defaults in conjunction with presets built into x264 really replace the need for sharktooth's presets. setting up x264 is nowhere near as complicated as it was before.
do you even need to hit a specific file size?yes
actually i am trying to make some dvds and and some HD content to a lower size like around bitrate of 600 to 700..
quantum5uicid3
8th December 2009, 13:27
ok as you say dear Sir !!! :)
but if i am right turbo used to be on in the past ,
BTW i am kinna noob in all this , setting it up would be so damn diff for me..
cant i just set it up as it was earlier in the unresticted 2 pass .. i have screenshotts of the 1051 version presets settings,
EDIT also , u said first to install 1056 then ur build ..
do we have to update 1056 first and then install ur build or how ?
also the 1309 x264 is there in ur update should i also replace this with 1360 from x264.nl
please forgive me noobiness , but my head is now aching with all this :P
regards
Glenn
no
1. uninstall and remove any traces of megui
2. install 1056, but dont even run it (this is just to provide the uninstaller and shortcuts, im lazy)
3. download and install the package of 1057 i put together ( it is fully up to date so no need to copy x264)
forum king
8th December 2009, 13:34
no
1. uninstall and remove any traces of megui
2. install 1056, but dont even run it (this is just to provide the uninstaller and shortcuts, im lazy)
3. download and install the package of 1057 i put together ( it is fully up to date so no need to copy x264)
yupp i have done it like that..
now the issue is how to make a profile which can rip on the same grounds as the unrestrcited 2pass was doing earlier in earlier builds.
quantum5uicid3
8th December 2009, 13:37
like i said before, putting the preset slider on "slower", change the mode to automated twopass, uncheck the turbo, and entering the bitrate will be pretty damn close to what you were doing before. leave turbo checked if you'd like but if your encoding down below 1000kbps, your gonna need to squeeze as much as you can out of it
quantum5uicid3
8th December 2009, 13:43
kool, i had problems with the audio presets as well. thats why i made that package. ru using 32 or 64bit windows 7?
forum king
8th December 2009, 13:53
Thanks Q :)
i donno anything about the options and yes i generally encode below 700 bits almost always :P so if u say it shouls be unticked then it ll be unticked dear Sir :)
what about deblocking strength coz i found thats thew only thing that has changed in this..
in earlier presets it used to be -1:-1 but tyhe default in that lone preset now is 0:0 should i change that..
if u can suggest anything which will be beneficial for ripping on low bit rate and getting good quality then please :)
regards
Glenn
quantum5uicid3
8th December 2009, 14:05
the defaults are all very well rounded at this point. i don't think i would worry about changing anything if i were you. if you would like to tweak, this really explains everything you need to know.
http://mewiki.project357.com/wiki/X264_Settings
I would consider playing with crf, if you don't need to hit an exact file size. it sounds more like you just wanna keep the bitrates pretty low. The problem with using the exact same bitrate for every source is that some are going to be more complex than others. I would consider experimenting with crf values between 25-30(im just guessing,higher crf=lower bitrate), so just keep raising your crf until the video doesn't look good enough to you anymore and then stick with the highest acceptable value.
forum king
8th December 2009, 14:13
the defaults are all very well rounded at this point. i don't think i would worry about changing anything if i were you. if you would like to tweak, this really explains everything you need to know.
http://mewiki.project357.com/wiki/X264_Settings
I would consider playing with crf, if you don't need to hit an exact file size. it sounds more like you just wanna keep the bitrates pretty low. The problem with using the exact same bitrate for every source is that some are going to be more complex than others. I would consider experimenting with crf values between 25-30(im just guessing,higher crf=lower bitrate), so just keep raising your crf until the video doesn't look good enough to you anymore and then stick with the highest acceptable value.
yes you are right ,
now i am getting why same bitrate doesnt give better quality with diff sources.
about deblocking well i guess -1:-1 gives ok results as it has been like that on all SLOWER profiles till date..
abiut the size well i try to make em small with bit rates in the range of 500 on an av for a dvd and for HD i try like 600 to 700.
but yeah my friends always ask me for a smaller size possible LOL
also Turbo is by default on in automated 2pass , you cant unchk it i have just noticed.
nakTT
8th December 2009, 14:18
In order to keep the MeGUI project running I have fixed a few of the problems with the latest version. Most of them are related to the recent changes in the x264 command line syntax and the not updated config gui in MeGUI.
Hopefully Kurtnoise/Sharktooth/... will continue their work on this great program. Kudos to them!
0.3.1.1057 patched build
- [x264Config] add support for weighted P prediction. Requires x264 revision 1327 or higher.
- [x264Config] fix issues with weighted B prediction
- [x264Config] fix an issue where custom profile settings may be lost
- [x264Config] very minor cosmetic changes
- removed the default UAC elevation prompt. Instead it will only be elevated if the app dir or avisynth plugin dir is not writeable
- [Util] + [FileUtil] incompatible xml files (e.g. profiles) will be moved to a backup dir
- fixed the problem of the incompatible x264 profiles. As a result the old B-Pyramid setting will be disabled
- [OSInfo] fixed a problem with the .NET detection
- [MuxStreamControl] preselect language if the filename contains the language name
- [x264Config] fixed a few input validate problems
- [x264Config] the advanced settings will be applied to the command line independent of the advanced settings checkbox
- [x264Config] a few profile settings could not be loaded
- [x264Config] extended input handling
- updatecopier.exe will be called elevated
- [x264Config] disable cabac and mbtree checkbox if setting disabled in profile or preset
- [x264Config] custom command line settings will replace settings in generated command line
- [HDBDStreamExtractor] fixed a crash bug
- [HDBDStreamExtractor] input and output path will be preselected if the window stays open
- [BitrateCalculator] added experimental M2TS support
Patch code is included, full source code can be requested if necessary. I do not know the GPL in every detail. If this is not sufficient please drop me a line and I will upload the full source files.
I did not change the version number for obvious reasons.
Feel free to address other/new problems, but I can not promise that I am able to solve them.
Stable build
http://www.mediafire.com/download.php?hj23mmmlmux
Hi Zathor,
First of all I want to thank you for continuing the MeGUI development.
I'm now using Stable Build version of your MeGUI. The first problem that I instantly notice is that when I select "Automated 2pass" in the x264 setting, the checkbox for "Turbo" seems to be checked by default and can't be unchecked. Please advice.
:thanks:
quantum5uicid3
8th December 2009, 14:28
as a workaround, just create the 1st and 2nd pass separately
nakTT
8th December 2009, 14:37
Thanks for the suggestion but I guess I would rather wait for the fix.
:thanks:
rack04
8th December 2009, 14:50
In the Blu-ray profile the default for partitions shouldn't be --partitions all. Also, --profile high is default. In the rate control tab the values for vbv buffer and vbv max bitrate are not passed to command line.
quantum5uicid3
8th December 2009, 15:13
In the Blu-ray profile the default for partitions shouldn't be --partitions all. Also, --profile high is default. In the rate control tab the values for vbv buffer and vbv max bitrate are not passed to command line.
are you sure --partitions all isn't supported by the bluray profile?
the other two problems u mentioned are fixed in the development build
stax76
8th December 2009, 15:19
--partitions all must be supported since RipBot264 uses it for it's Bluray profile.
quantum5uicid3
8th December 2009, 15:23
the reason why it looks like you can't change the vbv options is he set it up to where anything you specify in custom commandline options overides any attempted change in the gui. so the bluray compliancy settings are essentially locked on the profile he created.
rack04
8th December 2009, 15:27
are you sure --partitions all isn't supported by the bluray profile?
the other two problems u mentioned are fixed in the development build
I never said it wasn't supported. I just said that when you select default it retains --partitions all. I would rather the preset dictate when --partitions all is used.
EDIT: Actually I read my post again and can see how you made that assumption.
quantum5uicid3
8th December 2009, 15:31
same thing as vbv, --partitions all is forced in the custom command line.
and --profile high for that matter
Frosty5689
8th December 2009, 18:13
I noticed how megui passes a parameter to neroencaac.exe that creates a fake chapters in the mp4/m4a container. If this could be fixed so it doesn't create fake chapters,it'd help muxing mp4 and uploading to youtube without using mp4box as a cli.
szabi
8th December 2009, 18:19
I use this collection to keep compatibility with different devices. click (http://spreadsheets.google.com/pub?key=tYGTjNd0dG6P_A9z-YkFzFg&output=html).
Zathor
8th December 2009, 18:35
Waaah, so much postings :cool:
May I know which one U mean by "newest build"? Is it the one at the 1st post or the one at the 2nd page?
I recommend the "development build" but because of the rather big changes compared to the "stable" build there may arise problems. Up to now I do not know about problems.
thanks mate
i have used the latest development build of urs ..
but tell me when i usesd to use 1051 with unrestricted 2 pass profile the settings were that of SLOWER
in mean like this :
program --profile high --pass 2 --bitrate 1000 --stats ".stats" --ref 5 --b-adapt 2 --b-pyramid --direct auto --deblock -1:-1 --trellis 2 --partitions all --me umh --thread-input --output "output" "input"
but in this one ( the new patched 1057 build the settings in that same profile are FAST..
program --profile high --preset fast --pass 2 --bitrate 1000 --stats ".stats" --thread-input --deblock -1:-1 --no-dct-decimate --output "output" "input"
what should be done ( does it mean that in the new megui build and x264 build SLOWER stuff is more faster or i need to drag the slider to slower to get the same settings.. and quality as that of unrestricted 2 pass
Sorry, I did not use 1051 for a very long time. But as i read the changelog correctly the presets have been introduced in 1053 and are in x264 since 1206 (or so). Therefore you will get a different command line with the both MeGUI versions. The default preset setting is medium and therefore the command line created by 1051 will be slower compared to the one from 1057 patched. Additionally "--trellis 2 --partitions all --me umh" affect also speed/quality. If you want to have a high quality profile just use 1057 patched and move the slider to the right (placebo has the best quality / worst speed)
I made a simple installer to hopefully make things easier for people.
Thank you very much. May I request to add the newer eac3to? :)
i used the latest build by Zathor ( the 2nd one ) and installed it in a separate folder..
used unrestricted 2 pass HQ with SLower settings
it will do the first pass and give a STANDARD ERROR STREAM error upon second always..
sometimes the same error on first pass as well..
Please send me the error stream text (per PM for example). I can only fix it if I can reproduce it or I am able to make a educated guess.
a very 1th error I get under Win 7, I have installed as Zathor says
Error 1: happen when I select all profile and hit on import.
Error 2: same as error 1
Error 3 & 4 at the same time when I want to close meGUI.
Thanks for the report. Will try to reproduce (and fix) it later.
I'm now using Stable Build version of your MeGUI. The first problem that I instantly notice is that when I select "Automated 2pass" in the x264 setting, the checkbox for "Turbo" seems to be checked by default and can't be unchecked. Please advice.
I have to check this later, too. At the moment I do not know at which event/setting it should be activated or disabled.
I never said it wasn't supported. I just said that when you select default it retains --partitions all. I would rather the preset dictate when --partitions all is used.
I followed this thread and link in the first post. It looks like --partitions all is required or at least recommended for the BluRay profile. http://forum.doom9.org/showthread.php?t=149711
Additionally I have added a x264 BluRay profile as an example. The profile is based upon http://forum.doom9.org/showthread.php?t=149711 and http://mewiki.project357.com/wiki/X264_Settings. The profile has the goal to fulfill the bluray specs and be playable on most standalone players. A few remarks:
--nal-hrd requires a patched x264
--b-pyramid strict can not be aplied while mbtree is enabled but it should work sometime in the future. Please ignore the warning in the log.
The profile has been created as I understand the profile management should work. Feel free to start a discussion if you think that it should work the other way around. The custom command line "locks" the settings you want to force while you can change the quality/speed with the preset slider. The "advanced settings" tabs have been disabled in order to not confuse the more inexperienced users.
JoeH
8th December 2009, 18:45
You can set MKV as default by going to:
Options>Settings>Extra Config>Configure Auto Encode Default>
And choose the container that you like.
Thanks - I wasn't aware of that and I'll keep it in mind. However, that works for autoencode and is helpful, but it still doesn't change the default on the main screen, which is useful when you are putting multiple items into the Queue. It would still be helpful to be able to set the default (or just have it remember last selected, either way) on the main screen.
forum king
8th December 2009, 18:54
Dear Zathor and Quantum i have a suggestion :
you guys are so good at it and now as the thread is getting so many replies , why dont you guys gradually take over and develop megui builds which are compatible as the big guys are busy, i mean something like a full fledged patch over the latest build which takes care of the major issues.
I can tell you for sure that more than 50% of megui users are suffering since the updates have stopped and since the messups have started..
it took me whole 3 days to figure it out and i am a member since 1 year ..
guys please consider this , i am asking on behalf of all the affected folks.
regards
Glenn :)
i am still testing the second patch of urs dear zathor which quantum has made into a consolidated exe. will revert ....
bluebebe
8th December 2009, 20:41
why are the main developers of megui gone?
Triccotracco
8th December 2009, 21:08
a very 1th error I get under Win 7, I have installed as Zathor says
Error 1: happen when I select all profile and hit on import.
Error 2: same as error 1
following Zathor's instructions:
1. Install Avisynth 2.5.8 (if not already installed)
2. Extract the build to a new/empty directory
3. Run the program and let it update all necessary files from the development server.
4. Update some files manually if needed (x264.exe, ...)
also for me during first execution of Megui's update
I solve this issue restart Megui again forcing the update of "STAudio" restart again Megui and finally update Tx264 & TXviD :confused::confused: .... yes I know a little bit confused procedure but works!
kool
8th December 2009, 21:15
kool, i had problems with the audio presets as well. thats why i made that package. ru using 32 or 64bit windows 7?
32 Bit, and other thing when I checked avisynth plugin directory it was empty, expect 3 avisynth plugin.
Zathor
8th December 2009, 21:56
also for me during first execution of Megui's update
I solve this issue restart Megui again forcing the update of "STAudio" restart again Megui and finally update Tx264 & TXviD :confused::confused: .... yes I know a little bit confused procedure but works!
Problem found and fixed (in the next upload). These two files are simply not at the http://megui.org/auto/ location. I have removed this mirror until the update server is updated. Is someone able to provide a new update server with the latest packages?
Zathor
8th December 2009, 22:08
32 Bit, and other thing when I checked avisynth plugin directory it was empty, expect 3 avisynth plugin.
Which one? The one from avisynth or megui\tools\avisynth_plugins?
a very 1th error I get under Win 7, I have installed as Zathor says
Error 1: happen when I select all profile and hit on import.
Error 2: same as error 1
Error 3 & 4 at the same time when I want to close meGUI.
1 + 2) fixed (forgot to put the MessageBoxExLib.dll in the zip file...)
3 + 4) because of 1+2 the file handle could not be closed and therefore it can not be deleted/written during MeGUI closing ==> fixed
I will upload the new build soon.
stax76
8th December 2009, 22:27
why are the main developers of megui gone?
They didn't made a statement and only few things are known like sharktooth's health condition. Kurtnoise made a statement a while back saying something like like pausing computing generally but never made it true, maybe he made it now true but in this case he would have made another statement probably, I guess he isn't sure atm., he is still reading the forum.
Kurtnoise stopped after the last release which caused a lot problems for many users. I don't know exactly of what nature these problems were but it seemed the way some users reacted might have played a role, users with little support and understanding. If that's true it would be sad for supportive users like Inspector.Gadget. A way to deal with it could be to ignore unhelpful feedback and only support helpful feedback instead.
Zathor
8th December 2009, 23:21
Here is a small feature request. I always ouput MKV files, but MeGUI always defaults to MP4 on the main screen. It would be great if MeGUI would save the last selected format, or had an option to set the default.
It will now save the last used format.
The first problem that I instantly notice is that when I select "Automated 2pass" in the x264 setting, the checkbox for "Turbo" seems to be checked by default and can't be unchecked. :
Fixed.
New build has been uploaded:
- [MeGUISettings] removed the http://megui.org/auto/ update server
- [VideoEncodingComponent] + [MeGUISettings] added file format saving
- [x264ConfigurationPanel] Turbo mode can be changed in automated 2 or 3 pass
Because I did not receive any negative feedback regarding the development build I have deleted the "stable" build.
Zathor
8th December 2009, 23:28
I noticed how megui passes a parameter to neroencaac.exe that creates a fake chapters in the mp4/m4a container. If this could be fixed so it doesn't create fake chapters,it'd help muxing mp4 and uploading to youtube without using mp4box as a cli.
Can you please describe the problem in more detail? I do not use neroencaac.exe and a more detailed explanation (like the wrong parameter) should make it easier for me to fix the problem.
prOnorama
9th December 2009, 00:11
- [VideoEncodingComponent] + [MeGUISettings] added file format saving
Great, this works now it remembers your last setting for file format :)
Every setting I tried works from the main x264 configuration GUI except I'm still having a problem setting a value for rc-lookahead (doesn't show up in command line at all)
rack04
9th December 2009, 03:48
Can you update meGUI to support the new combined DGIndexNV? The way it is set up now you have to specify a path to DGAVCIndex, DGVC1Index, and DGMPGIndex. Now there is only DGIndexNV.
nakTT
9th December 2009, 06:04
New build has been uploaded
Because I did not receive any negative feedback regarding the development build I have deleted the "stable" build.
Anyone know what is the safest way to put the new build on top of my current build ("stable" build)?
:thanks:
nakTT
9th December 2009, 06:18
They didn't made a statement and only few things are known like sharktooth's health condition. Kurtnoise made a statement a while back saying something like like pausing computing generally but never made it true, maybe he made it now true but in this case he would have made another statement probably, I guess he isn't sure atm., he is still reading the forum.
Kurtnoise stopped after the last release which caused a lot problems for many users. I don't know exactly of what nature these problems were but it seemed the way some users reacted might have played a role, users with little support and understanding. If that's true it would be sad for supportive users like Inspector.Gadget. A way to deal with it could be to ignore unhelpful feedback and only support helpful feedback instead.
Oh! Sad to hear that. What about him? Anyway, I hope he will get better soon.
:thanks:
Zathor
9th December 2009, 06:29
Every setting I tried works from the main x264 configuration GUI except I'm still having a problem setting a value for rc-lookahead (doesn't show up in command line at all)
As soon as I change the value for "Nb. of Frames for Lockahead" the change is shown in the command line. Therefore I can not reproduce your problem. Can you explain the problem in more detail?
Can you update meGUI to support the new combined DGIndexNV? The way it is set up now you have to specify a path to DGAVCIndex, DGVC1Index, and DGMPGIndex. Now there is only DGIndexNV.
The main problem is that I do not have a license for the DGDecNV tool. If the commands have not changed between the old 3 tools version and now it should be possible. I cannot promise that I am able to change it.
Anyone know what is the safest way to put the new build on top of my current build ("stable" build)?
Create a backup of your MeGUI folder (in case something goes wrong) and copy the new files into the original directory.
Triccotracco
9th December 2009, 06:36
Can you please describe the problem in more detail? I do not use neroencaac.exe and a more detailed explanation (like the wrong parameter) should make it easier for me to fix the problem.
The same for me, not a big problem in my workflow. BTW when for example I load the .mp4 audio file in a gui like mkvmerge i see two, let me say, parts: the correct aac audio track & also this fake chapter. Not a big problem because with mkvmerge yuo can disable the fake chapter & then muxing mormally. For sure some mounths ago this strange stuff doesn't heppend.
Thankyou guys for all!
quantum5uicid3
9th December 2009, 09:41
i also confirm the --rc-lookahead issue still exists here on xp sp3 .net 3.5. what information do you need?
...reworking....
Zathor
9th December 2009, 11:14
i also confirm the --rc-lookahead issue still exists here on xp sp3 .net 3.5. what information do you need?
Which value do you would like to set and so on. At the moment I can confirm that a value of 40 will never be displayed regardless of the preset level. This is wrong and will be fixed. All other values should be shown in the command line (if it is not the default value of the preset). Please enter for example 41 and it should be visible.
quantum5uicid3
9th December 2009, 12:14
no it doesn't matter what it's set to, ive tried a wide variety of values
Zathor
9th December 2009, 14:54
no it doesn't matter what it's set to, ive tried a wide variety of values
Strange, can you send me please the profile with the problem?
nakTT
9th December 2009, 15:05
- [MeGUISettings] removed the http://megui.org/auto/ update server
- [VideoEncodingComponent] + [MeGUISettings] added file format saving
- [x264ConfigurationPanel] Turbo mode can be changed in automated 2 or 3 pass
Because I did not receive any negative feedback regarding the development build I have deleted the "stable" build.
Can you do this for audio file format as well?
:thanks:
Zathor
9th December 2009, 15:44
Can you do this for audio file format as well?
:thanks:
Give somebody an inch, and he will take a mile :p
JoeH
9th December 2009, 15:54
It will now save the last used format.
Thanks so much! :thanks::thanks::thanks:
JoeH
9th December 2009, 16:15
i made a couple more packages. to maybe make things easier. (full installer. creates shortcuts and uninstaller)
Lite (just megui, no tools) (http://www.constructd.com/megui/megui1057_zathorpatched_lite.exe)
Full (all tools updated beyond current update server) (http://www.constructd.com/megui/megui1057_zathorpatched.exe)
Thanks. It works great - I love the idea of having all the updated tools included.
When I installed it, the tools "oggenc2", "STX264", and "TXviD" all still asked to update. I updated oggenc2, but as I imagine the profiles you included are probably more updated than the ones included in STX264 and TXvid I downloaded them (to get rid of the "update" question) but did not install any of the profiles. I don't know if it is possible to avoid those tools not appeariing as updated, but I thought I'd mention it in case.
kool
9th December 2009, 16:24
Which one? The one from avisynth or megui\tools\avisynth_plugins?
Avisynth.
I will upload the new build soon.
Did you updated yet?
nakTT
9th December 2009, 16:37
Give somebody an inch, and he will take a mile :p
:D silly me.
Zathor
9th December 2009, 16:43
Avisynth.
With the newer builds the plugins will not be copied to the avisynth plugin dir. Instead they will be copied to tools\avisynth_plugins in order to use different versions without problems.
Did you updated yet?
Yes, it has been updated yesterday.
hajj_3
9th December 2009, 16:53
great work, hope you can add x264 v1369 soon, current version available in the updates list in megui is v1309.
Anyone know what happened to the megui developers? hope they didn't have a car crash or anything.
prOnorama
9th December 2009, 18:16
i also confirm the --rc-lookahead issue still exists here on xp sp3 .net 3.5. what information do you need?
i made a couple more packages. to maybe make things easier. (full installer. creates shortcuts and uninstaller)
Full (all tools updated beyond current update server) (http://www.constructd.com/megui/megui1057_zathorpatched.exe)
-it does not check if previous version is installed yet, so please uninstall any old version first.
-new uninstaller completely wipes megui directory, i think this was previous behavior.
- Uninstaller does not remove Start Menu and Quick start links.
- When installed no x264 *scratchpad* profile is loaded
- (I think this is a general flaw) the x264 Bluray_example profile "cheats" by having values in the Custom Command Line which should be set by the main patched GUI, just --nal-hrd --aud should be needed.
http://thumbnails23.imagebam.com/5925/1cc6f859241981.gif (http://www.imagebam.com/image/1cc6f859241981)
quantum5uicid3
9th December 2009, 18:24
- Uninstaller does not remove Start Menu and Quick start links.
what OS? I'm not great with NSIS, but I'll have more time to learn when finals are over. :)
anybody wanna help?
http://www.constructd.com/megui/megui_nsis.zip
nakTT
9th December 2009, 19:13
Hi Zathor,
I would be great if you could update MeGUI to accommodate this change of x264. Link below:
http://repo.or.cz/w/x264.git/commit/de5beaec2078967d08da8ae2483c9f982b0ab07e
:thanks:
prOnorama
9th December 2009, 19:50
what OS? I'm not great with NSIS, but I'll have more time to learn when finals are over. :)
anybody wanna help?
http://www.constructd.com/megui/megui_nsis.zip
WinXP SP3
kool
9th December 2009, 20:41
With the newer builds the plugins will not be copied to the avisynth plugin dir. Instead they will be copied to tools\avisynth_plugins in order to use different versions without problems.
Yes, it has been updated yesterday.
Thanks, it works now.
* If you upload a newer version in post 1, should we also replace our meGUI folder or we get every change by auto update?
* Do we need to change anything in existing x264 presets, or just leave it to default and encode? "I mean best quality"
Triccotracco
9th December 2009, 21:58
I see. I have just downloaded the unpatched one.
I'm interested to know about the "faster" bit for the patched 1057. Hope you can share your experience in a little bit detail.
:thanks:
Fine is for this megui patched build & faster is for these latest x264 releases compared old one. My experience is limited because i'm using now the presets with very very little adjustments such as crf value, my target is to watch movies on mediaplayer like for example WDTV and presets now, but also Sharktooth profiles in the past works 100% for me.:)
quantum5uicid3
9th December 2009, 22:17
Hi Zathor,
I would be great if you could update MeGUI to accommodate this change of x264. Link below:
http://repo.or.cz/w/x264.git/commit/de5beaec2078967d08da8ae2483c9f982b0ab07e
:thanks:
he didn't set it up to where they disable each other within the gui since x264 did it automatically. so its already supported, just copy new x264 in and change b-pyramid to normal.
Zathor
9th December 2009, 23:13
Uploaded a new build. Today there are only two very small changes - more to come in the next days.
- [MeGUISettings] changed the development server to http://www.constructd.com/megui
- [x264Encoder] changed the --rc-lookahead command line creation
The mirror is provided by quantum5uicid3. Thank you very much!
Zathor
9th December 2009, 23:21
Thanks, it works now.
* If you upload a newer version in post 1, should we also replace our meGUI folder or we get every change by auto update?
With the new mirror provided by quantum5uicid3 it will be possible to use once again auto update. Please change your development path to http://www.constructd.com/megui. Starting with the next build it will be uploaded there.
* Do we need to change anything in existing x264 presets, or just leave it to default and encode? "I mean best quality"
It depends on how old your profiles are, which settings you changed and on your target device. I can not answer this question in general.
(I think this is a general flaw) the x264 Bluray_example profile "cheats" by having values in the Custom Command Line which should be set by the main patched GUI, just --nal-hrd --aud should be needed.
As said earlier before. With this profile I want to start a discussion about how the profile management system should work. At the moment the only way to lock or force settings is to write it in the custom command line. With the preset slider you are then able to change the speed/quality without loosing your important parameters.
kool
9th December 2009, 23:39
It depends on how old your profiles are, which settings you changed and on your target device. I can not answer this question in general.
I don't have any profile, I just downloaded your build, do I need to make any profile?
Zathor
9th December 2009, 23:47
You need to know the limitations of your target device(s) and have to change the settings accordingly. If you have only one "rule set" you will need only one profile.
kool
10th December 2009, 00:20
The error still exists after trying both new versions and + new problem I don't get Xvid profiles and x264 by update.
http://i50.tinypic.com/2dazyb4.png
http://i48.tinypic.com/2mnopc6.png
For the screen shots 2, I think it happen with each profile in encoder settings.
I don't know why it happen :confused: , Or it is problem with Win 7.
Can't get megui to work :(
Forteen88
10th December 2009, 00:23
I don't know why it happen :confused: , Or it is problem with Win 7.
Can't get megui to work :(Try running MeGUI as administrator, by right-clicking on the icon and select "Run as administrator".
kool
10th December 2009, 00:29
Run as administrator solve the problem, but do I need to do this all the time? because after I select run as administrator things work fine, but when I load megui normally I get the error back.
* The simpleresize which come with megui update, why it doesn't work under avisynth 2.5.8? when I tried, got error simpleresize is not avisynth 2.5 plugin.
wlee15
10th December 2009, 00:36
Run as administrator solve the problem, but do I need to do this all the time? because after I select run as administrator things work fine, but when I load megui normally I get the error back.
* The simpleresize which come with megui update, why it doesn't work under avisynth 2.5.8? when I tried, got error simpleresize is not avisynth 2.5 plugin.
Right-click the megui shortcut, select properties, select the compatibility tab, check the box beside "Run this program as administrator".
kool
10th December 2009, 00:38
OK, the error issue as been solved by right click on "meGUI > Properties > Compatibility > Tick on Run meGUI as administrator" Hope this is the right solution.
But
* I don't get x264 profiles and Xvid by update
* simpleresize doesn't work under avisynth 2.5.8
* meGUI icon doesn't show up in Win 7 taskbar.
http://i48.tinypic.com/302yy5s.png
Adub
10th December 2009, 02:01
I have mirrored the current version on the first post here:
www.mirror.adubvideo.net/megui.zip
In addition, I can provide you with an ftp account on my server (unlimited bandwidth) if you would like. Just let me know if you are interested. It takes me two seconds to setup.
quantum5uicid3
10th December 2009, 02:01
you should be able to get xvid profiles now
there are no x264 profiles, someone needs to make them.
simpleresize was out of date, did a clean installation and updated. issue appears resolved
you're on your own with the taskbar
nakTT
10th December 2009, 03:05
he didn't set it up to where they disable each other within the gui since x264 did it automatically. so its already supported, just copy new x264 in and change b-pyramid to normal.
Thank you for the info. Glad to know that. Will give it a try ASAP.
:thanks:
Fine is for this megui patched build & faster is for these latest x264 releases compared old one. My experience is limited because i'm using now the presets with very very little adjustments such as crf value, my target is to watch movies on mediaplayer like for example WDTV and presets now, but also Sharktooth profiles in the past works 100% for me.:)
Thanks for sharing info.
:thanks:
Aoshi101
10th December 2009, 05:45
Problem: It keeps erroring out when I try to encode. It doesn't give any error message at all. In the worker it starts the encode but not even a second later, encode stops and worker status changes to say "error". Any way to find out the error or any solution on why this problem would occur?
How to duplicate this problem: Well there's no sure way to duplicate it unless if you're running default settings on everything. I just used the basic blu ray profile that came with this developmental build provided at the beginning of this thread. I changed nothing, tried encoding in mp4 x264.
Now I'm not encode savvy but I'm willing to learn. Could it be that blu-ray type settings cannot be encoded in an mp4 container? Any other info you guys need, just ask ill post as quickly as possible. I tried several things including changing the profile, trying a different container, tried changing resolution from 1080p down to 720p, etc etc. Can't figure it out for the life of me. Ideas?
System Specs:
Windows 7 64 bit
Quad Core 2 Q6600
4 gig 1066 ram
P.S. I lurk doom9 alot for encode information, first time i had any real errors with MeGUI that wasn't already solved. I appreciate your efforts Zathor!
Zathor
10th December 2009, 06:21
Do you have an entry in the log (in the file after closing megui or located at the log tab in MeGUI)? There should/could be a more specific error message.
Zathor
10th December 2009, 06:31
Run as administrator solve the problem, but do I need to do this all the time? because after I select run as administrator things work fine, but when I load megui normally I get the error back.
During startup of MeGUI it will be detected if you have write access in the MeGUI dir. If not the program will be restarted as administartor automatically. In your case it seems to be that you have write access to the MeGUI dir and no access to the allprofiles\x264 dir. Can you please check this (create a file in both directories without UAC and post the results)
* meGUI icon doesn't show up in Win 7 taskbar.
Sorry, I can see the icon in Win7. Do you get the megui.exe icon in the explorer?
Aoshi101
10th December 2009, 08:09
Do you have an entry in the log (in the file after closing megui or located at the log tab in MeGUI)? There should/could be a more specific error message.
--[NoImage] Standard error stream: C:\Program Files (x86)\megui\tools\x264\x264.exe: unrecognised option `--nal-hrd'
Thats the error then. Pulled it from the log, didn't even notice the log tab before (fyi me = not very observant ahaha).
Zathor
10th December 2009, 08:34
Thats the error then. Pulled it from the log, didn't even notice the log tab before (fyi me = not very observant ahaha).
You need to use a patched x264.exe which supports this feature.
Aoshi101
10th December 2009, 08:36
I thought the build you supplied was already patched for it? Everything I use currently is from the zip provided at the beginning of this thread, unless if I have to manually patch x264 exe?
Zathor
10th December 2009, 09:09
I thought the build you supplied was already patched for it? Everything I use currently is from the zip provided at the beginning of this thread, unless if I have to manually patch x264 exe?
The update server has recently changed. The new mirror is provided by quantum5uicid3 and I do not know at the moment if the x264 (build 1360 I think) is a patched one. I can check this not earlier than in ~12 hours. Which version of x264 and which mirror do you use?
Aoshi101
10th December 2009, 09:27
I use the constructd.com/megui/ address for patches and its currently set up to the 1369 techouse's vanilla build. I've seen the words "Jeebs patched" back in older versions of x264, so my guess is you can tell if its patched if it has the word "patched" in the name, or is that just for naming convention sakes.
Should I fall back to 1360?
nakTT
10th December 2009, 09:48
Uploaded a new build. Today there are only two very small changes - more to come in the next days.
- [MeGUISettings] changed the development server to http://www.constructd.com/megui
- [x264Encoder] changed the --rc-lookahead command line creation
The mirror is provided by quantum5uicid3. Thank you very much!
Glad to hear that we already have a new update server. Thanks to you and quantum5uicid3.
:thanks:
Lugia25000
10th December 2009, 10:29
http://www.constructd.com/megui
The new xvid encraw from alexins has many bugs. Can anyone change the encraw with the old encraw from -> http://megui.org/auto/stable/xvid_encraw-2009-05-30.zip ?
Old encraw needed aviwriter.dll.
Old xvidcore.dll and new xvidcore.dll work very fine with the old encraw.
@Zathor, big thx for the development.
My english is not so good, i hope everyone understand me.
Zathor
10th December 2009, 10:50
I use the constructd.com/megui/ address for patches and its currently set up to the 1369 techouse's vanilla build. I've seen the words "Jeebs patched" back in older versions of MeGUI, so my guess is you can tell if its patched if it has the word "patched" in the name, or is that just for naming convention sakes.
I have no access to the file at the moment but "vanilla" is most likely an unpatched version. And if you used this version and got the error it is clearly unpatched.
JEEBs builds can be found here: http://x264.fushizen.eu/
Direct link to Jeebs build with hrd:
http://x264.fushizen.eu/files/1369_hrd/x264.exe
More patches here: http://forum.doom9.org/showthread.php?t=130364
Aoshi101
10th December 2009, 12:29
Thanks so much for explaining it and helping me Zathor. I look foward to more possible updates to this build and hopefully if Sharktooth or Kurtnoise or any of the other MeGUI coders come back, they apply your fixes to their official build. Kudos to you bro.
quantum5uicid3
10th December 2009, 14:01
reverted back to old encraw as requested
updated to techhouse 1369 patched v2 for nal-hrd
EDIT: reverted back to unpatched 1369, im getting application errors with patched versions...
kool
10th December 2009, 14:26
You should be able to get Xvid profiles now
simpleresize was out of date, did a clean installation and updated. issue appears resolved
It works now thanks.
There are no x264 profiles, someone needs to make them.
Hope some one make them soon, because I don't know how to make them :p
During startup of MeGUI it will be detected if you have write access in the MeGUI dir. If not the program will be restarted as administartor automatically. In your case it seems to be that you have write access to the MeGUI dir and no access to the allprofiles\x264 dir. Can you please check this (create a file in both directories without UAC and post the results)
Hope I get you right by "with out UAC" I untick the option run meGUI as administrator in meGUI properties and tried to open meGUI and the result is as follow
http://i46.tinypic.com/35jxi8h.png
http://i48.tinypic.com/34t5qut.png
Sorry, I can see the icon in Win7. Do you get the megui.exe icon in the explorer?
Yes I do get the icon in explorer.
in 1th time when i install meGUI i do get both icon in explorer & taskbar, but after I restart megui I don't get meGUI icon in taskbar but in explorer it remain as normal.
JoeH
10th December 2009, 14:33
As said earlier before. With this profile I want to start a discussion about how the profile management system should work. At the moment the only way to lock or force settings is to write it in the custom command line. With the preset slider you are then able to change the speed/quality without loosing your important parameters.
After running loads (i.e. about 50) of tests quality / speed tests with the new X264, I wholly agree with you, Zathor. I think that the new profiles should NOT set the options which are set by the new "Speed" and "Tune" options in X264, and should only set options which are ignored by those but somehow necessary / helpful for a certain type of encode.
That way users can easily modify the settings based on how much time /quality they want / need, but also be assured of compatibility with the different devices or uses MeGUI offers.
Zathor
10th December 2009, 15:13
I have mirrored the current version on the first post here:
www.mirror.adubvideo.net/megui.zip
In addition, I can provide you with an ftp account on my server (unlimited bandwidth) if you would like. Just let me know if you are interested. It takes me two seconds to setup.
Thank you very much for your offer. Because quantum5uicid3 already provided a mirror we do not need an additional mirror at the moment. I will keep your offer in mind and would like to come back to you later if necessary.
livetolove92
10th December 2009, 16:09
No more x264 default setting =((
Hix, I may try to be adapt in using command line.
JoeH
10th December 2009, 17:35
After running loads (i.e. about 50) of tests quality / speed tests with the new X264, I wholly agree with you, Zathor. I think that the new profiles should NOT set the options which are set by the new "Speed" and "Tune" options in X264, and should only set options which are ignored by those but somehow necessary / helpful for a certain type of encode.
That way users can easily modify the settings based on how much time /quality they want / need, but also be assured of compatibility with the different devices or uses MeGUI offers.
I have thought this through a little more, and here is how I would propose the MeGUI "presets" work from here on out:
1. On the main screen, add a drop down menu for the "Speed" and the "Tune" options in X264. So, instead of just selecting the "preset", you would select the "preset", the "speed" and the "tune". In the case of "speed" and "tune", the first option in the dropdown would be to default to whatever is set in the "preset" you choose.
2. But, if you select, for example, "Animation" in the "Tune" dropdown, that would override whatever option is set in the preset for "Tune". The same for "Speed".
3. The included presets, then, would serve mainly to provide different "types" of encodings, such as for Blu-ray standalone, for IPod, DXVA compatible, etc.
4. There would NOT, however be duplicates for whether you want it to go fast or slow, high quality or low quality. All that can be decided at the time of encode using the two drop downs on the main menu.
5. The end result would be far fewer presets, easier to maintain, with much greater flexibility for the end user regarding speed/quality and tuning.
What do you think?
Triccotracco
10th December 2009, 20:55
Little vsfilter problem with autoupdate from:
http://www.constructd.com/megui
http://img709.imageshack.us/img709/8669/meguiupdateerror.jpg (http://img709.imageshack.us/i/meguiupdateerror.jpg/)
Kagain
10th December 2009, 23:10
A few profiles for those in need
Medium:
SD (DXVA-AVCHD)
HD (DXVA-AVCHD)
HD (DXVA-PS3)
HD (DXVA-Blu-ray)
Slower:
SD (DXVA-AVCHD)
HD (DXVA-AVCHD)
HD (DXVA-PS3)
HD (DXVA-Blu-ray)
Needs a x264 build patched with nal-hrd
http://www.mediafire.com/?znoqzwm2kdf
Zathor
10th December 2009, 23:19
No more x264 default setting =((
Hix, I may try to be adapt in using command line.
Sorry, I do not understand your posting. Maybe it's too late for me... Can you please explain?
Hope I get you right by "with out UAC" I untick the option run meGUI as administrator in meGUI properties and tried to open meGUI and the result is as follow
Sorry, I did not have made myself clear enough. Please copy a file with the windows explorer in the directory c:\program files\megui\allprofiles\x264 and a file in c:\program files\megui. I assume that the last one will work without prompt and the first one only if you confirm the administrative prompt. Is this correct?
I have thought this through a little more, and here is how I would propose the MeGUI "presets" work from here on out:
1. On the main screen, add a drop down menu for the "Speed" and the "Tune" options in X264. So, instead of just selecting the "preset", you would select the "preset", the "speed" and the "tune". In the case of "speed" and "tune", the first option in the dropdown would be to default to whatever is set in the "preset" you choose.
2. But, if you select, for example, "Animation" in the "Tune" dropdown, that would override whatever option is set in the preset for "Tune". The same for "Speed".
3. The included presets, then, would serve mainly to provide different "types" of encodings, such as for Blu-ray standalone, for IPod, DXVA compatible, etc.
4. There would NOT, however be duplicates for whether you want it to go fast or slow, high quality or low quality. All that can be decided at the time of encode using the two drop downs on the main menu.
5. The end result would be far fewer presets, easier to maintain, with much greater flexibility for the end user regarding speed/quality and tuning.
What do you think?
It seems to be not my day :) So I need to ask a few questions:
1) main screen = main configuration screen of the profile or the main screen?
speed = x264 preset and preset = profile?
3) so we have basic rulesets for the devices? great!
More or less this is the way I would want it to be, but everybody keep the feedback flowing!
Aoshi101
10th December 2009, 23:44
reverted back to old encraw as requested
updated to techhouse 1369 patched v2 for nal-hrd
EDIT: reverted back to unpatched 1369, im getting application errors with patched versions...
Well Zathor supplied me with Jeebs' 1369 patched and it works just fine so far. Test out Jeebs' version?
Adub
11th December 2009, 00:47
Thank you very much for your offer. Because quantum5uicid3 already provided a mirror we do not need an additional mirror at the moment. I will keep your offer in mind and would like to come back to you later if necessary.
You are certainly welcome. Just let me know if you need me.
livetolove92
11th December 2009, 02:22
Sorry, I do not understand your posting. Maybe it's too late for me... Can you please explain?
Sorry, I did not have made myself clear enough. Please copy a file with the windows explorer in the directory c:\program files\megui\allprofiles\x264 and a file in c:\program files\megui. I assume that the last one will work without prompt and the first one only if you confirm the administrative prompt. Is this correct?
It seems to be not my day :) So I need to ask a few questions:
1) main screen = main configuration screen of the profile or the main screen?
speed = x264 preset and preset = profile?
3) so we have basic rulesets for the devices? great!
More or less this is the way I would want it to be, but everybody keep the feedback flowing!
I mean the x264 profiles such as "1pass Extra Quality, 2pass Insane,...". Now it's only x264 Bluray :p.
And actually it get a problem when updating vsfilter like this http://img709.imageshack.us/img709/8669/meguiupdateerror.jpg
quantum5uicid3
11th December 2009, 02:27
i put kagain's profiles on the update server as long as there are no objections and updated to jeeb's r1369 patched for nal-hrd support. it seems stable
thank you Kagain
I made an installer, it includes the latest version of megui and the contents of the update server. the uninstaller removes everything except the allprofiles directory and there's no taskbar shortcut. there's no check for previous version, it should safely overwrite any previous version, but if you do have problems, uninstall old and then install new
Installer (http://www.mediafire.com/?q2hw1zza5jn)
vsfilter prob resolved
livetolove92
11th December 2009, 03:10
Well done, mate :D. Tks so much.
kool
11th December 2009, 05:31
Thank you Zathor & quantum5uicid3 you guys did a great work :logfile:
and Zathor my problem as been fixed with quantum5uicid3 new installer, hope things go smoothly after now on :p
Triccotracco
11th December 2009, 06:45
A few profiles for those in need
Medium:
SD (DXVA-AVCHD)
HD (DXVA-AVCHD)
HD (DXVA-PS3)
HD (DXVA-Blu-ray)
.....
.....
Needs a x264 build patched with nal-hrd
testing SD (DXVA-AVCHD) profile but:
[Information] Log
--[Information] [11/12/2009 06:39:07] Started handling job
--[Information] [11/12/2009 06:39:07] Preprocessing
--[NoImage] Job commandline: "C:\Program Files\megui patched\tools\x264\x264.exe" --profile high --level 3.1 --preset slower --crf 20.0 --thread-input --keyint 48 --min-keyint 1 --b-pyramid strict --ref 6 --slices 4 --vbv-bufsize 15000 --vbv-maxrate 15000 --aud --nal-hrd --sar 64:45 --output "movie.264" "movie.avs"
--[Information] [11/12/2009 06:39:07] Encoding started
--[NoImage] Standard output stream
--[NoImage] Standard error stream: C:\Program Files\megui patched\tools\x264\x264.exe: unrecognised option `--nal-hrd'
--[Information] [11/12/2009 06:39:07] Job completed
seems jeeb's 1369 patched not work properly. Without --nal-hrd works.
Tricco:)
nakTT
11th December 2009, 06:54
seems jeeb's 1369 patched not work properly. Without --nal-hrd works.
Tricco:)
Sorry for this noob question. What is --nal-hrd ?
:thanks:
JoeH
11th December 2009, 08:06
It seems to be not my day :) So I need to ask a few questions:
1) main screen = main configuration screen of the profile or the main screen?
speed = x264 preset and preset = profile?
3) so we have basic rulesets for the devices? great!
More or less this is the way I would want it to be, but everybody keep the feedback flowing!
Sorry for the term confusion. Yes, I was referring to
"Main screen" of MeGUI, NOT of the profile
speed = X264 preset
Preset = MeGUI profile
So, I think we are in agreement.
Adub
11th December 2009, 08:58
Seems to be a small bug when entering in values by hand into the x264 settings dialog window. It basically goes haywire and is very difficult to compensate for.
Also, when scrolling down from 1000 kbps, it jumps to 9999 and then starts to decrease.
Zathor
11th December 2009, 11:02
Seems to be a small bug when entering in values by hand into the x264 settings dialog window. It basically goes haywire and is very difficult to compensate for.
Also, when scrolling down from 1000 kbps, it jumps to 9999 and then starts to decrease.
Thanks for the problem report. I will have a look at it. Do you have the problem with all sliders?
Sorry for this noob question. What is --nal-hrd ?
http://mewiki.project357.com/wiki/X264_Settings#nal-hrd
Add NAL HRD parameters to the output stream; used for HD-DVD and Blu-ray compliancy. Depends on vbv-bufsize and vbv-maxrate to be set to be active.
quantum5uicid3
11th December 2009, 15:52
not sure if auto update wasn't working because version didn't change or what, but jeeb's 1373 patched is up now.
nakTT
11th December 2009, 15:54
not sure if auto update wasn't working because version didn't change or what, but jeeb's 1373 patched is up now.
Thank god. I have been waiting for it.
:thanks:
Edited: I get this error.
Finished parsing update file...
There is 1 file that can be updated.
Updating x264. File 1/1.
Update completed.
0 file was completed successfully
1 file had problem.
nakTT
11th December 2009, 15:56
http://mewiki.project357.com/wiki/X264_Settings#nal-hrd
Thanks for the info. No wonder I never encounter issue with 1369, because I did not use that particular feature.
:thanks:
rack04
11th December 2009, 15:58
In the new x264 profiles I is possible to break Blu-ray compliance using the tunes. For example, --tune animation increases bframes to 5 while blu-ray specifications say the limit is 3. If you know what settings you need for compliance I would add those to the custom command line so you're not relying on the defaults.
Kagain
11th December 2009, 17:05
In the new x264 profiles I is possible to break Blu-ray compliance
You're right about that.
Deleted the animation profiles.
Added reference frames and b frames to the command line so now the tune animation can be used instead.
http://www.mediafire.com/?znoqzwm2kdf
Thanks
quantum5uicid3
11th December 2009, 17:13
if i understand the presets and tuning correctly. specifying individual options in the command line does overwrite the tunings, but does not overwrite the presets. i didn't think about this before, so i think we're gonna need more gui changes. someone correct me if i'm wrong.
the update server should be good now, i think it was having trouble parsing the name of the patch for some reason. the hyphen maybe?
nakTT
11th December 2009, 17:16
the update server should be good now, i think it was having trouble parsing the name of the patch for some reason. the hyphen maybe?
After I keep on trying, it just succeeded in the end. I don't know what is the problem but it is okay now. Many thanks for providing us the update server.
:thanks:
quantum5uicid3
11th December 2009, 17:20
ive been messing with it for a while now, i verified it wasn't working here either. i was confused why, i'm pretty sure it was the hyphen in the patch name though :)
quantum5uicid3
11th December 2009, 17:25
so no confusion
nakTT
11th December 2009, 17:28
ive been messing with it for a while now, i verified it wasn't working here either. i was confused why, i'm pretty sure it was the hyphen in the patch name though :)
I don't know why and I can't really help as I'm not a programmer. But I'm very glad it is working now. Thanks again.
:thanks:
quantum5uicid3
11th December 2009, 17:46
Presets will be used as follows:
--preset name
and apply before all other options. In other words, they override the x264 defaults, which, with the default changes (http://forum.doom9.org/showthread.php?t=148148), will be:
--subme 7 --bframes 3 --weightb --8x8dct --ref 3 --mixed-refs --trellis 1 --crf 23 --threads auto
As such, all options that you set will act on top of the preset you choose, regardless of the option order.
ultrafast:
--ref 1 --scenecut 0 --nf --no-cabac --bframes 0 --partitions none --no-8x8dct --me dia --subme 0 --aq-mode 0
veryfast:
--partitions i8x8,i4x4 --subme 1 --me dia --ref 1 --trellis 0
fast:
--mixed-refs 0 --ref 2 --subme 5
medium:
<defaults>
slow:
--me umh --subme 8 --ref 5 --b-adapt 2 --direct auto
slower:
--me umh --subme 9 --ref 8 --b-adapt 2 --direct auto --partitions all --trellis 2
placebo:
--me tesa --subme 9 --merange 24 --ref 16 --b-adapt 2 --direct auto --partitions all --no-fast-pskip --trellis 2 --bframes 16
For all encodes, regardless of preset or not, using --pass 1 will automatically trigger "turbo" settings, which are as follows and override all commandline options:
--trellis 0 --no-8x8dct --partitions none --me dia --ref 1 --subme MIN(2, previous subme)
This can be disabled using --slow-firstpass.
For all encodes, if you don't set your own --ref option and instead use the default or a preset, x264 will automatically lower --ref if the --level you set conflicts with it. If you set --ref explicitly, it will not override what you set.
Profiles will be used as follows:
--profile name
The options will be baseline, main, and high, which do what you think they do. Note that these override all other options no matter what, with two exceptions.. Because interlaced and lossless coding are options with very explicit meanings, the encoder will terminate with an error if you attempt to use them with an incompatible profile.
Tunings will be used as follows:
--tune name
The options will be "film" and "animation", and will tweak AQ strength, psy-rd/trellis strength, deblock, refs, and so forth:
film:
--deblock -1:-1 --psy-rd 1.0:0.15
animation:
--ref (previousref==1?1:MIN(previousref*2,16)) --deblock 1:1 --psy-rd 0.4:0 --aq-strength 0.6 --bframes 5
All of this is subject to change before final release, and suggestions are welcome.
If you don't use any of the new presets, the only changes for you will be the new defaults, and the automatic fast first pass.
maybe someone can understnad this better, i just kept setting all my options manually, so never bothered to understand this. does "explicitly" setting options override the --tune and --preset or not?
rack04
11th December 2009, 18:18
maybe someone can understnad this better, i just kept setting all my options manually, so never bothered to understand this. does "explicitly" setting options override the --tune and --preset or not?
yes it will override both.
quantum5uicid3
11th December 2009, 18:25
ok cool thanks. im doing new ones now, it's so tedious :)
foxace
11th December 2009, 18:58
Hello and thank you for your excellent work.
Is it possible to make megui compatible with
the new version of "DG NV tools 2.0.0 "
The server "CUVIDServer .exe" does not launch properly, the function resize nvidia not working well.
:thanks:
quantum5uicid3
11th December 2009, 19:03
does anyone know? DXVA can now play anything as long as it's h264 compliant, right?
and AVCHD compliant is the same as bluray compliant?
i made some device presets with quality settings ranging from crf 18.5 to 23 in increments of 1.5 and a 2pass. you still need to set the tune option depending on the source and adjust the preset slider for speed adjustments.
quantum5uicid3
11th December 2009, 19:32
Hello and thank you for your excellent work.
Is it possible to make megui compatible with
the new version of "DG NV tools 2.0.0 "
The server "CUVIDServer .exe" does not launch properly, the function resize nvidia not working well.
:thanks:
someone buy zathor a gtx 295 and dgnv and i'm sure he'd be inclined :)
foxace
11th December 2009, 20:03
someone buy zathor a gtx 295 and dgnv and i'm sure he'd be inclined :)
ok. I send a letter to Father Christmas we'll see if he answers.:p
Kagain
11th December 2009, 23:29
you still need to set the tune option depending on the source and adjust the preset slider for speed adjustments.
The problem with making device profiles and still use the preset slider for speed adjustments is that the reference frames will not be adjuster accordingly.
i.e if --ref 4 is set in the commandline and you want a faster profile, the # of reference frames will not be decreased if you use the slider. But that might not matter too much.
quantum5uicid3
11th December 2009, 23:47
i know it's not absolutely perfect, but playing with it, ultra fast still goes pretty damn fast.
quantum5uicid3
12th December 2009, 00:20
zathor,
the following fields throw an error when trying to delete them to type in a new value, functionally everything is good, it's purely aesthetic.
Maximum GOP Size
Minimum GOP Size
Number of Reference Frames
VBV Buffer Size
VBV Maximum Bitrate
there's also problems deleting the crf and typing in a new value. if i delete it and want 23 for instance, i have to type 3-2.
Zathor
12th December 2009, 01:51
the following fields throw an error when trying to delete them to type in a new value, functionally everything is good, it's purely aesthetic. [...] there's also problems deleting the crf and typing in a new value. if i delete it and want 23 for instance, i have to type 3-2.
Thanks and fixed (as soon as I upload the next build)
I noticed how megui passes a parameter to neroencaac.exe that creates a fake chapters in the mp4/m4a container. If this could be fixed so it doesn't create fake chapters,it'd help muxing mp4 and uploading to youtube without using mp4box as a cli.
From the nero aac encoder help:
Note that multiple input files can be specified, they will be encoded together into a single output file with chapter marks indicating source file divisions.
So the problem seems to be a feature which works as designed. I assume a chapter will be created every time a stream is passed to neroaacencoder from stdin.
nakTT
12th December 2009, 02:07
zathor,
the following fields throw an error when trying to delete them to type in a new value, functionally everything is good, it's purely aesthetic.
Maximum GOP Size
Minimum GOP Size
Number of Reference Frames
VBV Buffer Size
VBV Maximum Bitrate
there's also problems deleting the crf and typing in a new value. if i delete it and want 23 for instance, i have to type 3-2.
The same issue happen when you want to type bitrate for "automated 2pass".
Zathor
12th December 2009, 02:38
The same issue happen when you want to type bitrate for "automated 2pass".
I have checked all input handler in the configuration window. All of them should be ok now.
Can you do this for audio file format as well?
This has been added, too. But the new build is still not available and because of other changes it may take one or two days before this build is available.
nakTT
12th December 2009, 02:50
Glad to hear that. Thanks man.
:thanks:
Evil Ash
12th December 2009, 15:36
Hi, this is my 1st post and I'm sorry its to report a bug. MeGUI is adding "--sar 1:1" at the end of the command line overriding any custom I add, its a PAL DVD so I'm adding "--sar 64:45" to the custom command line, everything looks fine in the profile, eg."program --crf 21.5 --thread-input --sar 64:45 --output "output" "input" ", I hit encode and heres an edited log so you can see what I mean.
--[NoImage] Job commandline: "x264.exe" --crf 21.5 --thread-input --sar 64:45 --sar 1:1 --output "E:\MKVs\vinny.mkv" "E:\MKVs\vinny.avs"
---[NoImage] avs [info]: 708x548 @ 25.00 fps (171658 frames)
---[NoImage] x264 [info]: using SAR=1/1I'm using the newest installer(thanks quantum5uicid3) fully updated and WinXp-SP3.
Zathor
12th December 2009, 15:44
Hi, this is my 1st post and I'm sorry its to report a bug. MeGUI is adding "--sar 1:1" at the end of the command line overriding any custom I add, its a PAL DVD so I'm adding "--sar 64:45" to the custom command line, everything looks fine in the profile, eg."program --crf 21.5 --thread-input --sar 64:45 --output "output" "input" ", I hit encode and heres an edited log so you can see what I mean.
Welcome to the forum!
And thanks for the problem report. I have fixed the error and a custom sar will overwrite the automatically generated one. But I can still not upload the build because of ongoing other changes.
Zathor
12th December 2009, 18:45
- [x264ConfigurationPanel] updated the input handling
- [AudioEncodingComponent] + [MeGUISettings] added audio format saving
- [MainForm] changed the unexptected error handler. The details will be only written to the log
- [ProfileConfigurationWindow] icon added
- [ProfileConfigurationWindow] every closing of the form will check if there has been something changed
- [x264ConfigurationPanel] added nal-hrd and aud checkbox (required for bluray; patched x264 is required for nal-hrd)
- [ContextHelp.xml] added and changed a few entries
- removed DGM and DGVC1 Indexer, removed CUVIDServer start
- added DGIndexNV and DGMultiSource support
This is an unstable build only for testing purposes because of the DGIndexer changes. I cannot test it myself (no license) so someone else needs to test it. As soon as the feedback is positive I will merge all three DGIndexer. At the moment all three indexer may not function properly. So do not use it in a productive environment!
If you want to test it, download the build, install as usual, edit the DGIndexNV path in the settings and copy the DGMultiDecodeNV.dll to the megui\tools\avisynth_plugin folder.
Unstable development build!
Link removed
Guest
12th December 2009, 21:02
It crashes MEGUI when I enqueue a script using DGMultiDecodeNV.dll. It opens the preview fine but then crashes when I enqueue a job. This is the problem I have always had.
If you have an Nvidia card I'd be happy to give you a license so you can figure out why Megui crashes.
foxace
12th December 2009, 23:48
It crashes MEGUI when I enqueue a script using DGMultiDecodeNV.dll. It opens the preview fine but then crashes when I enqueue a job. This is the problem I have always had.
If you have an Nvidia card I'd be happy to give you a license so you can figure out why Megui crashes.
same for me when I click on queue megui crash and the nvidia resizer don't work the resolution becomes very small
Zathor
12th December 2009, 23:52
If you have an Nvidia card I'd be happy to give you a license so you can figure out why Megui crashes.
That would be so great! Thank you very much. Sent you a PM.
Hopefully I can reproduce the crashes, it's easy to solve and the CUVIDServer is not necessary anymore.
I have removed the link in my previous posting because of the existing problems.
olex99
13th December 2009, 00:41
I had a look at this a while ago when i was having the same problem. Worked out it was a timing issue between the different threads. When you click Enqueue it opens the script at least 3 times and i guess that on some occasions it wasn't able to dispose of the old one before opening it again.
I ended up putting a Thread.Sleep(50) inside the AVSReader class just after it opens the script and that fixed my problem. Bit of a hack i know, but since it was only for me i didn't care. You might be able to come up with a better solution.
stax76
13th December 2009, 01:08
There might as well be a bug on the native side since I have a report DGMultiSource with resize arguments crashing StaxRip which doesn't do anything special other than a few simple VFW calls. Such a bug might not cause issues in a native application but only in managed applications. Some people notice a script running in a native application and don't in a managed application and conclude there is a bug in the managed application but it might as well be a bug in the native component. Often the CLR detects when a native component tries to corrupt managed memory, sometimes the complete managed exception handling fails.
I ended up putting a Thread.Sleep(50) inside the AVSReader class just after it opens the script and that fixed my problem. Bit of a hack i know, but since it was only for me i didn't care. You might be able to come up with a better solution.
Maybe some simple thread synchronization.
Zathor
13th December 2009, 01:31
Thanks to neuron2 I have now a license and I am able to reproduce the problem.
I had a look at this a while ago when i was having the same problem. Worked out it was a timing issue between the different threads. When you click Enqueue it opens the script at least 3 times and i guess that on some occasions it wasn't able to dispose of the old one before opening it again.
You really do not want to know how many times the avs file is opened...
I ended up putting a Thread.Sleep(50) inside the AVSReader class just after it opens the script and that fixed my problem. Bit of a hack i know, but since it was only for me i didn't care. You might be able to come up with a better solution.
Tried this "hack", too, but I had no luck. Even with very high values and explicit dispose of the opened avs the program crashed without error handling in places where a error handling should catch it. Also I was not able to attach the CLR to the process. DGMultiSource errors out with cuCtxCreate() failed
It's too late now to check this further. Will have a look at it tomorrow.
BuckMaster
13th December 2009, 08:06
I want to thank you Zathor for all you do and time spend for Megui.I read this tread from the start, Megui is an app who worth more and you are one of the people who can prove that.
Cheers bro!:D
medp7060
13th December 2009, 09:59
Agreed. It seems that MeGUI is one of the best x264 GUI out there, but its develpment is not as avtive as before. Hope it is not another GKnot.
JoeH
13th December 2009, 13:09
Thanks to Kagain and Quantum for their work on v1 and v2 of the profiles. I have done some more work on the Bluray profiles, and am attaching the results.
NOTE: These profiles will ONLY work with the new version of MeGUI that Zathor has not yet released which has the checkboxes for the --aud and --nal-hrd options.
Here is a list of the changes I made and why:
1. Increased Bitrate on 2 pass to 8000 - Typical usage for a DVD9. The setting of 700 is not realistic for Bluray compatible devices.
2. Turned on Turbo on 2 pass - Default option, should always be used except in cases of extreme need.
3. --keyint 24 --min-keyint 2 - Required by Bluray specifications according the x264 Wiki
4. Moved everything I could off the "Custom command line" - It is not necessary to put everything that shouldn't change on the "Custom command line". It is enough that it appear in the command line. Anything that simply appears in the command line will take preference over the X264 "preset" and "tune" option. Because of this, the only thing I included was --bframe 3, as this is the default and thus does not naturally appear.
5. Selected the --nal-hrd and --aud checkboxes which Zathor added (Thanks Zathor!)
6. Slightly modified the CRF values - I changed "Very High Quality" to 15.0, which is what is recommended in the x264 official documentation as giving extremely high quality. I adjusted the values of Balanced and High Quality to step gradually up to the value of 23.0 in Standard.
7. Removed the difference between 1080p and 720p - X264 does nothing to resize the video. So, there is no need to have different profiles for 1080p and 720p. Therefore, I eliminated the redundancy and kept only 1 set of Bluray profiles, which should be used both for 1080p and 720p.
I think that's about it. If those changes seem good to you, please delete the v2 Bluray profiles and include these ones. Thanks!
Here is a link to download them: Bluray_profiles_v3.zip (http://www.mediafire.com/?zejiwmyeu0e)
P.S. - If you want to install these manually, just unzip them into the profiles directory. Just keep in mind you will need the update which Zathor posted but then took off.
quantum5uicid3
13th December 2009, 14:12
1. i assumed people would use the bitrate calculator
2. yeah, i agree, should probably be left on
3. oops :)
4. the slider and tune will change the commandline beyond just specifying the --tune and --preset is the problem. i think forcing the options in custom commandline is the better idea, because this makes maintaining compatibility for anyone completely dependent on the presets dummy proof(for lack of a better way to put it)
5. ok
6. i would imagine crf 15 would exceed the size of the original source in some cases. in other words, i think it's excessive. since this is a very subjective, i'd like to hear more opinions. maybe a "transparent" preset?
7. the difference is the maximum number of reference frames supported.
Zathor
13th December 2009, 14:20
Thank you very much, JoeH!
3. --keyint 24 --min-keyint 2 - Required by Bluray specifications according the x264 Wiki
I have read somewhere that --min-keyint 1 is recommended if targeting bluray. But I can't find the source now.
I'm in the process of bringing a new build online (without the DGindexer changes at the moment). I have changed the version to 1058 so that it can be updated with the new update server.
nakTT
13th December 2009, 14:31
Can't wait to give 1058 a try. Thanks Zathor.
:thanks:
shon3i
13th December 2009, 14:33
I have read somewhere that --min-keyint 1 is recommended if targeting bluray. But I can't find the source now.Both --min-keyint 1 and --min-keyint 2 are ok, --min-keyint 2 is preffered if stream after encoding goes to authoring application such as sonic scenarist. max --keyint depend of maximum bitrate and fps.
Removed the difference between 1080p and 720p - X264 does nothing to resize the video. So, there is no need to have different profiles for 1080p and 720p. Therefore, I eliminated the redundancy and kept only 1 set of Bluray profiles, which should be used both for 1080p and 720p.
7. the difference is the maximum number of reference frames supported. 6 vs 4 for 720p anyway will not incrase quality that much. I recomend to not use more than 4 ref's in any case.
Guest
13th December 2009, 15:06
You really do not want to know how many times the avs file is opened...
DGMultiSource errors out with cuCtxCreate() failed It's crucial to know that, because the GPU card's memory limits the number of simultaneous script instantiations. So, please tell us exactly how many times the script is opened, when and if they are closed, how they are closed (are they "really" closed, i.e., DGMultiDecode's destructor is called, or some funniness is used such that they are not really closed until Megui exits), etc.
quantum5uicid3
13th December 2009, 15:10
Thanks to Kagain and Quantum for their work on v1 and v2 of the profiles. I have done some more work on the Bluray profiles, and am attaching the results.
NOTE: These profiles will ONLY work with the new version of MeGUI that Zathor has not yet released which has the checkboxes for the --aud and --nal-hrd options.
Here is a list of the changes I made and why:
1. Increased Bitrate on 2 pass to 8000 - Typical usage for a DVD9. The setting of 700 is not realistic for Bluray compatible devices.
2. Turned on Turbo on 2 pass - Default option, should always be used except in cases of extreme need.
3. --keyint 24 --min-keyint 2 - Required by Bluray specifications according the x264 Wiki
4. Moved everything I could off the "Custom command line" - It is not necessary to put everything that shouldn't change on the "Custom command line". It is enough that it appear in the command line. Anything that simply appears in the command line will take preference over the X264 "preset" and "tune" option. Because of this, the only thing I included was --bframe 3, as this is the default and thus does not naturally appear.
5. Selected the --nal-hrd and --aud checkboxes which Zathor added (Thanks Zathor!)
6. Slightly modified the CRF values - I changed "Very High Quality" to 15.0, which is what is recommended in the x264 official documentation as giving extremely high quality. I adjusted the values of Balanced and High Quality to step gradually up to the value of 23.0 in Standard.
7. Removed the difference between 1080p and 720p - X264 does nothing to resize the video. So, there is no need to have different profiles for 1080p and 720p. Therefore, I eliminated the redundancy and kept only 1 set of Bluray profiles, which should be used both for 1080p and 720p.
I think that's about it. If those changes seem good to you, please delete the v2 Bluray profiles and include these ones. Thanks!
Here is a link to download them: Bluray_profiles_v3.zip (http://www.mediafire.com/?zejiwmyeu0e)
P.S. - If you want to install these manually, just unzip them into the profiles directory. Just keep in mind you will need the update which Zathor posted but then took off.
ok thanks to JoeH, ive made the changes to presets according to suggested points 1,2,3,7.
zathor we need your thoughts on point 4
Guest
13th December 2009, 15:38
OK, more data on the DG tools problem...
I found a missing close of the CUDA context in DGMultiDecode.dll. So please get the fixed one by redownloading 2.0.0 beta 6. It doesn't fix the Megui crashing but it may cure the cuCtxCreate() failure.
I traced my code and I see Megui doing this:
[open avs]
create DGMultiDecode instance (for preview)
[I close the preview]
destroy instance
[I enqueue the job]
create
destroy
create
destroy
create
destroy
CRASH!
So it should be working with my fix above but it is still crashing.
Also, it doesn't crash with the CUVID server, although I thought I saw that previously.
Zathor
13th December 2009, 15:39
- [x264ConfigurationPanel] updated the input handling
- [AudioEncodingComponent] + [MeGUISettings] added audio format saving
- [MainForm] changed the unexptected error handler. The details will be only written to the log
- [ProfileConfigurationWindow] icon added
- [ProfileConfigurationWindow] every closing of the form will check if there has been something changed
- [x264ConfigurationPanel] added nal-hrd and aud checkbox (required for bluray; patched x264 is required for nal-hrd)
- [ContextHelp.xml] added and changed a few entries
- update MediaInfo library and its wrapper to the latest release (0.7.25)
In order to have a stable release the build 1058 is now online. Point the update server to http://www.constructd.com/megui/ and the new version will be applied.
It's crucial to know that, because the GPU card's memory limits the number of simultaneous script instantiations. So, please tell us exactly how many times the script is opened, when and if they are closed, how they are closed (are they "really" closed, i.e., DGMultiDecode's destructor is called, or some funniness is used such that they are not really closed until Megui exits), etc.
After 1058 is out I will continue the work at this front. Sadly it's not easy to answer your question because of the structure the avs are opened/called. Give me a little bit time :rolleyes:
4. Moved everything I could off the "Custom command line" - It is not necessary to put everything that shouldn't change on the "Custom command line". It is enough that it appear in the command line. Anything that simply appears in the command line will take preference over the X264 "preset" and "tune" option. Because of this, the only thing I included was --bframe 3, as this is the default and thus does not naturally appear.
Changing the preset or tune slider will change things a user selected in other areas. That's the way it works now. So if a user wants to have higher speed/quality and moves the slider, some values which are required for device compatibility may be overwritten. For example the reference frames will increase up to 16 and many devices support only 3. I'm still unsure how to change the behavior. At the moment I recommend to put all device values into the custom command line. Device values = values which are required for device compatibility and which may change due to preset/tune changes.
JoeH
13th December 2009, 16:13
Changing the preset or tune slider will change things a user selected in other areas. That's the way it works now. So if a user wants to have higher speed/quality and moves the slider, some values which are required for device compatibility may be overwritten. For example the reference frames will increase up to 16 and many devices support only 3. I'm still unsure how to change the behavior. At the moment I recommend to put all device values into the custom command line. Device values = values which are required for device compatibility and which may change due to preset/tune changes.
Quantum and Zathor,
Thanks for clearing that up. I don't understand why it works that way - do you know if it is a bug in X264 or is this specific to MeGUI?
I just ran the updater to v1058, but the presets did not import. The window came up asking if I wanted to import the presets, but it was totally empty.
JoeH
13th December 2009, 16:27
6. i would imagine crf 15 would exceed the size of the original source in some cases. in other words, i think it's excessive. since this is a very subjective, i'd like to hear more opinions. maybe a "transparent" preset?
At least for Bluray movies it still tends to be smaller than the original, at least in tests I've run. Obviously this wouldn't be for someone who wants to burn to a DVD9, but for those times you want to quickly export a video to actually burn on a Bluray-25 disk, it tends to give about the right size.
Of course, it's not big deal for me to just customize it - so either way is fine with me.
I think Sharktooth used the term "insane" in his profiles to refer to extremely high quality...:p
Zathor
13th December 2009, 16:27
Thanks for clearing that up. I don't understand why it works that way - do you know if it is a bug in X264 or is this specific to MeGUI?
It's a MeGUI related "problem". If you change an option it is not locked and it will be changed if the preset/tune changes.
That's the way x264 applies the parameters:
--preset
--tune
user settings (will override preset and tune settings)
--profile overrides all settings
Thats the way MeGUI applies the settings if you change a value:
megui profile setting
changed user setting
if changed --preset overrides all settings
if changed --tune overrides all settings
if changed --profile overrides all settings
custom command line overrides all settings
That's not good at all, but if you understand how it works it is possible to create stable profiles.
OK, more data on the DG tools problem...
I found a missing close of the CUDA context in DGMultiDecode.dll. So please get the fixed one by redownloading 2.0.0 beta 6. It doesn't fix the Megui crashing but it may cure the cuCtxCreate() failure.
I traced my code and I see Megui doing this:
[open avs]
create DGMultiDecode instance (for preview)
[I close the preview]
destroy instance
[I enqueue the job]
create
destroy
create
destroy
create
destroy
CRASH!
So it should be working with my fix above but it is still crashing.
Also, it doesn't crash with the CUVID server, although I thought I saw that previously.
Yes, the cuCtxCreate() is gone but it is still crashing... The good news is as soon as the job is in the queue it can be started without problems. But it's very hard to get it in the queue without crash.
quantum5uicid3
13th December 2009, 16:56
I just ran the updater to v1058, but the presets did not import. The window came up asking if I wanted to import the presets, but it was totally empty.
made a mistake with the zip file. fixed
JoeH
13th December 2009, 18:37
That's the way x264 applies the parameters:
--preset
--tune
user settings (will override preset and tune settings)
--profile overrides all settings
Thats the way MeGUI applies the settings if you change a value:
megui profile setting
changed user setting
if changed --preset overrides all settings
if changed --tune overrides all settings
if changed --profile overrides all settings
custom command line overrides all settings
That's not good at all, but if you understand how it works it is possible to create stable profiles.
OK. I suppose the best order, followin along with how X264 by default works, would be something like this, each overriding the previous when it applies:
x264 preset
x264 tune
megui profile setting - whenever it is not the "default" (that is, whenever it appears in the "command line" which appears inside the megui profile - that way the user can expect that the command line which appears in MeGUI will act just as it would if he were to type that command line in MSDOS)
custom command line
JoeH
13th December 2009, 18:41
made a mistake with the zip file. fixed
Confirmed. Works great. I deleted all other profiles and imported only these. Do we still need STx264? It might be helpful to clean up the profiles to just drop it now that we have the new ones.
Triccotracco
13th December 2009, 21:42
Update all to the last revisions, seems work good. A question about presets slide: why when i move from very slow to slower a --bframe 8 appear?
slide in "very slow" position:
program --preset veryslow --thread-input --output "output" "input"
now slide in "slower" position:
program --preset slower --thread-input --bframes 8 --output "output" "input"
:thanks:
Zathor
13th December 2009, 22:12
Update all to the last revisions, seems work good. A question about presets slide: why when i move from very slow to slower a --bframe 8 appear?
slide in "very slow" position:
program --preset veryslow --thread-input --output "output" "input"
now slide in "slower" position:
program --preset slower --thread-input --bframes 8 --output "output" "input"
Thanks, there is an error in applying the bframes in the preset slower. Will be fixed in the next update.
TDC.net
14th December 2009, 04:07
Hi Zathor,
thanks for reviving megui development! Really an impressive number of improvements in build 1058!
Just a small error:
When you move the megui folder to another path, all folders that are subfolders of megui are updated in the options automatically except:
-update path
-avisynth plugins path
Can't wait to test more improvements in megui thanks to your skills!
Regards,
Raist
ircopdd
14th December 2009, 04:08
DGSource("C:\CH010_0920_2033.dga", deinterlace=2, resize_w=1280, resize_h=720)
why use deinterlace=2
fps change to 59.94fps???
---[NoImage] avs [warning]: converting input clip to YV12
---[NoImage] avs [info]: 1280x720 @ 59.94 fps (3066 frames)
use deinterlace=1
fps Normal
fps=29.970
Inspector.Gadget
14th December 2009, 04:40
Because BOBBING ALWAYS DOUBLES THE FRAMERATE. That's not a MeGUI topic anyway, take it up in the existing DGNV tools thread.
Triccotracco
14th December 2009, 06:31
Another question about "preset setting" switch in "misc" tab of x264 configuration window: how does it work? Or better, what is the difference from "preset setting" switch and "Presets" slide on "main" tab.?
amgeex
14th December 2009, 07:14
Just wanted to say thanks for keeping this GUI alive, its my favorite so far and there isn't a replacement right now, so yeah, thanks a lot!!
ACrowley
14th December 2009, 11:01
Hello
I cant update :
Trying server: http://www.constructd.com/megui
Retrieving update file from server...
Error: Couldn't connect to server.
Error: Could not download XML file
EDIT:
Now it works...The Problem was my old megui folder from the old builds
Im glad to see megui workinf fine again :) it was my favourite gui.
Have you planned x264_x64 Support ?
Zathor
14th December 2009, 13:10
Have you planned x264_x64 Support ?
I already have a few features planed for the next milestone release. But of course there may be problems implementing them and therefore I will only comment on or publish an feature if it is proofed to be working (at least for me) or if I need additional input from the community (like below).
Just a small error:
When you move the megui folder to another path, all folders that are subfolders of megui are updated in the options automatically except:
-update path
-avisynth plugins path
Thanks for the feedback. I will change that behavior.
I would like to change it so that all of the file and path settings will be tied up so that the files have to be in the tools directory at the specified location. That's the way most of the other GUIs work and I think it's the best solution in order to keep it simple and with less problems (like the UAC problem when the files have to be copied in a special directory). What do you and all others think?
Another question about "preset setting" switch in "misc" tab of x264 configuration window: how does it work? Or better, what is the difference from "preset setting" switch and "Presets" slide on "main" tab.?
Both do more or less the same. If you move the slider the settings will be applied all over the tabs. The "preset setting" will write them back to the tabs in case you have changed a preset setting like the number of reference frames and do not want to move the slider.
XhmikosR
14th December 2009, 14:00
Zathor: Although I don't use MeGUI for the last one year or so, I'd like to thank you for trying to fix a great tool for a lot of users out there. One question: Can't you get SVN access? Maybe ask Kurtnoise or Doom9? It would be nice to have all of your changes in the trunk.
I patched the source with your patch, updated the AssemblyInfo for MediaInfoWrapper and meGUI and updated MediaInfo.dll to 0.7.25 and compiled a new installer for those who used the old one.
You can find it here (http://www.mediafire.com/?ty1mjgmgmum). (no changes have been made to the installer except just the version bump which means it still needs administrator privileges like the old one)
ACrowley
14th December 2009, 14:09
@Zathor
x264 cmd encoding Status window displays the current Bitrate (%,Frame,FPS,kbp/s,eta Time)
Megui doesnt show it. Its very important when you ask me .
Please, can you add this Info in the Megui Proccess/Status Window ?
Zathor
14th December 2009, 16:49
x264 cmd encoding Status window displays the current Bitrate (%,Frame,FPS,kbp/s,eta Time)
Megui doesnt show it. Its very important when you ask me .
Please, can you add this Info in the Megui Proccess/Status Window ?
Ok, I ask you: Why is it important to know? :-)
Sorry, but I cannot see an improvement if you know the current bitrate. What benefit do you have if you know it during the encoding process?
Can't you get SVN access? Maybe ask Kurtnoise or Doom9? It would be nice to have all of your changes in the trunk.
It took some days but :
kurtnoise13 added zathor to the meGUI project.
2009-12-14 13:31:53 CET by kurtnoise13
Thanks to Kurtnoise I am now able to commit my source code and have access to the official MeGUI update server. I need to change a few things before I am able to commit the source code and update the files on the server.
In the meantime I invite you all to test the current build and give me feedback about problems/bugs. Especially the upgrade path 1051 --> 1058 and 1057 (official) --> 1058 is important. I would like to commit a version which is as bug free as possible.
detmek
14th December 2009, 17:03
Hi. Just to say, thank you, Zathor, for fixing and continuing development of my (our) favourite GUI. I didn't test much 1058 but, so far, works good.
And, thanks to Kurtnoise and Sharktooth for previous development.
TDC.net
14th December 2009, 17:27
Thanks for the feedback. I will change that behavior.
I would like to change it so that all of the file and path settings will be tied up so that the files have to be in the tools directory at the specified location. That's the way most of the other GUIs work and I think it's the best solution in order to keep it simple and with less problems (like the UAC problem when the files have to be copied in a special directory). What do you and all others think?
Perfect idea! I vote for that! If you really want to customize something as a user, just copy the custom files there ;)
Ok, I ask you: Why is it important to know? :-)
Sorry, but I cannot see an improvement if you know the current bitrate. What benefit do you have if you know it during the encoding process?
I totally agree! current info such as estimated total size, remaining time and fps is enough.
R
ACrowley
14th December 2009, 17:35
[QUOTE=Zathor;1352803]Ok, I ask you: Why is it important to know? :-)
Sorry, but I cannot see an improvement if you know the current bitrate. What benefit do you have if you know it during the encoding process?
[/CODE]
Ofcourse i can use a Bitrateviewer after encoding
Usefull or not..i think megui could view all x264 Status informations, why not
Kurtnoise
14th December 2009, 17:40
Usefull or not..i think megui could view all x264 Status informations, why not
it's already in the log...
nakTT
14th December 2009, 17:44
it's already in the log...
Hi Kurt, glad to see you here.
Zathor
14th December 2009, 18:06
0.3.1.1058 dev
- [MeGUISettings] update_cache location and avisynth plugin location can not be changed anymore
- [x264Settings] changed the default *scratchpad* settings to x264 default (preset and some other settings have been wrong)
- [x264ConfigurationPanel] changed b-frames value in preset slower
Uploaded a new build to the first posting. It's a small step on the way to the stable release. Do not expect new features until the stable commit. Beside bug fixes I will only remove the possibility to change the program path of the auto downloaded tools.
nakTT
14th December 2009, 18:26
0.3.1.1058 dev
- [MeGUISettings] update_cache location and avisynth plugin location can not be changed anymore
- [x264Settings] changed the default *scratchpad* settings to x264 default (preset and some other settings have been wrong)
- [x264ConfigurationPanel] changed b-frames value in preset slower
Uploaded a new build to the first posting. It's a small step on the way to the stable release. Do not expect new features until the stable commit. Beside bug fixes I will only remove the possibility to change the program path of the auto downloaded tools.
Is the b-frames for preset slower has been changed from 8 to 3 (the way it was)? Thanks.
Zathor
14th December 2009, 18:29
Is the b-frames for preset slower has been changed from 8 to 3 (the way it was)? Thanks.
There has been an logical error preventing to update the value if the value has been different from 0. Do not ask... it has been fixed.
nakTT
14th December 2009, 18:40
There has been an logical error preventing to update the value if the value has been different from 0. Do not ask... it has been fixed.
Sorry. Thanks.
:thanks:
MatLz
14th December 2009, 18:54
Hi!
It seems AQ can't be disabled, even with the usage of the custom command line --aq-mode 0, mode 1 is used. Mode 2 seems to work.
Zathor
14th December 2009, 19:33
Hi!
It seems AQ can't be disabled, even with the usage of the custom command line --aq-mode 0, mode 1 is used. Mode 2 seems to work.
- [x264ConfigurationPanel] subme 10 instead of 9 will force trellis 2 and aq-mode > 0
- [x264ConfigurationPanel] removed dependency between mb-tree and aq-mode
- [x264Encoder] fixed aq-mode command line generation (aq-mode 0 has never been appended)
Update in the first post. There have been a few wrong settings regarding aq-mode...
Sorry. Thanks.
Why do you say "sorry"? I am very grateful for your problem reports. :thanks:
MatLz
14th December 2009, 19:43
Sorry I missed that...
:stupid:
Zathor
14th December 2009, 19:48
Sorry I missed that...
:stupid:
No, I have fixed it after your problem report! Thank you very much! :-)
Theliel
14th December 2009, 20:23
thank you Zathor for your work.
many ppl forget much times the work behind a proyect like MeGui. Of course, thank anyway (and always) to Kurtnoise and Sharktooth and many others.
shon3i
14th December 2009, 20:30
I am wery happy to see MeGUI alive ;) Zathor, thank you for hard work and of course all greetings to main developers (berrinam, Sharktooth, dimzon51, Kurtnoise13) for great application for years :)
@Zathor, i must you note that Blu-Ray profiles which came with MeGUI is out of spec.
Can i suggest you instead fixing those profiles, make one completly new option insade x264 settings which will correct settings if are out of spec from bd standard.
Zathor
14th December 2009, 20:41
@Zathor, i must you note that Blu-Ray profiles which came with MeGUI is out of spec.
In which way it is out of spec? At least the bluray 2-pass looks good. Btw you have to look in the command line below - the GUI values may change when using the preset slider but they will be overridden by the custom command line.
Can i suggest you instead fixing those profiles, make one completly new option insade x264 settings which will correct settings if are out of spec from bd standard.
Some kind of device preset is indeed required. At the moment you have to put the device settings in the custom command line.
Carpo
14th December 2009, 20:45
Zathor any chance you could look at getting CUVIDServer.exe to be found by megui, every time it comes up with the error it cant find it, even if you tell it where DGIndexNV.exe is, i am assuming (probably incorrectly) that megui assumes it to be in the same place.
Thanks :0)
Zathor
14th December 2009, 20:53
Zathor any chance you could look at getting CUVIDServer.exe to be found by megui, every time it comes up with the error it cant find it, even if you tell it where DGIndexNV.exe is, i am assuming (probably incorrectly) that megui assumes it to be in the same place.
As stated last weekend I will add support for the new DGIndexNV. As soon as I start to implement this all CUVIDServer.exe calls have to be renewed. Because of the big changes needed it will not be included in the next official and stable release.
Do you have a workaround like starting the CUVIDServer.exe yourself before MeGUI starts?
shon3i
14th December 2009, 20:55
Btw you have to look in the command line belowHah, i didn't look ;) sorry, it's fine. I thinked about some option which will prevent user from changing. For example if user set vbv-maxrate higher than 15000, automaticly to disable Max Keyint should be larger than blu-ray specs specified.
Triccotracco
14th December 2009, 21:49
Another note about presets slide cursor(this is my matter :D): when i move from ultrafast until slower "--aq-mode 0" (that is correct for ultrafast) remain.
cursor in ultrafast position:
program --preset ultrafast --thread-input --aq-mode 0 --output "output" "input"
cursor in slower position:
program --preset slower --thread-input --aq-mode 0 --output "output" "input"
Carpo
14th December 2009, 22:01
As stated last weekend I will add support for the new DGIndexNV. As soon as I start to implement this all CUVIDServer.exe calls have to be renewed. Because of the big changes needed it will not be included in the next official and stable release.
Do you have a workaround like starting the CUVIDServer.exe yourself before MeGUI starts?
thats what i have been doing, with 1051 its hit and miss - 1056 and above its pure miss, i can wait :)
Zathor
14th December 2009, 23:03
- [x264Encoder] fixed aq-mode in all presets
- [DialogManager] minor change to the CUVIDServer call
- [MeGUISettings] + [SettingsForm] all automatically installed tool paths cannot be changed anymore
thats what i have been doing, with 1051 its hit and miss - 1056 and above its pure miss, i can wait :)
Please try the new build. Link is in the first post. I have made only a very minor change but maybe together with the new path system it will work. Please try it with a clean installation - but expect the real fix later. Oh, by the way: Please specify in the settings the path to either the VC1 or MPG dgindex NV tool.
Another note about presets slide cursor(this is my matter :D): when i move from ultrafast until slower "--aq-mode 0" (that is correct for ultrafast) remain.
Thanks, it has also been fixed.
Carpo
14th December 2009, 23:51
Oh, by the way: Please specify in the settings the path to either the VC1 or MPG dgindex NV tool.
Thanks, it has also been fixed.
Thought DGIndexNV.exe did them all as its the new merged version of his tools?
Edit: went and got beta 11 still not working, i will do the 2 backups i have to do manually and sit and wait till you have time to sort out megui - its no biggy :)
rack04
14th December 2009, 23:54
- [MeGUISettings] + [SettingsForm] all automatically installed tool paths cannot be changed anymore
Would you consider changing this back to the way it was? I don't like having multiple copies of the same programs floating around. I would like to be able to specify paths to x264, dgindex, dgavcindex, mp4box, tsmuxer, mkvmerge, eac3to, dgdecode, and dgavcdecode. Thanks.
Zathor
15th December 2009, 00:25
Thought DGIndexNV.exe did them all as its the new merged version of his tools?
Edit: went and got beta 11 still not working, i will do the 2 backups i have to do manually and sit and wait till you have time to sort out megui - its no biggy :)
Yes, DGIndexNV is the "one for all" tool but it is not supported by MeGUI at the moment.
Would you consider changing this back to the way it was? I don't like having multiple copies of the same programs floating around. I would like to be able to specify paths to x264, dgindex, dgavcindex, mp4box, tsmuxer, mkvmerge, eac3to, dgdecode, and dgavcdecode. Thanks.
Today it is no problem at all to waste this little space - especially if you are encoding HD videos.
The more experienced user lost the ability to change the path. On the other hand the more inexperienced user lost the possibility to have problems due to the configurable path settings.
Every one of the other GUIs (at least all I know) has the tools in the program folders and the path is not changeable at all. But I would never do things only because all other do them. I have to be sure that this is the right thing. Therefore I would like to have additional feedback. To revert the changes is no problem at all and only a matter of minutes (thanks to source control)
Aoshi101
15th December 2009, 01:07
After installing one of the older builds of MeGUI like 1051 or 1056, you can take everything that was supplied in this new build by Zathor and copy it over into the MeGUI directory on your C drive. Say yes when it asks to copy over files currently there. Now when you try to use your taskbar shortcut or your start menu shortcut, it will work fine and you don't have to worry about reconfiguring paths and such. Very simple copy paste.
Im sure alot of you figured it out, this is for those who didn't realize it or haven't tried.
stax76
15th December 2009, 03:01
Yes, DGIndexNV is the "one for all" tool but it is not supported by MeGUI at the moment.
Is there any managed GUI where it works?
Would you consider changing this back to the way it was? I don't like having multiple copies of the same programs floating around. I would like to be able to specify paths to x264, dgindex, dgavcindex, mp4box, tsmuxer, mkvmerge, eac3to, dgdecode, and dgavcdecode. Thanks.
From developers view very very bad idea, using AviSynth plugin auto loading also very bad idea, download feature, very doubtful. I've been there and have done this and will never go back.
nakTT
15th December 2009, 03:33
Why do you say "sorry"? I am very grateful for your problem reports. :thanks:
I just thought I don't want you to get mad at me over my noob question. Glad to know that you are not easily mad. Not like some other guy.
:thanks:
P/S: I can't seems to get the latest update. Just now I tried to update and there is nothing new other than my current 1058. Please help.
Guest
15th December 2009, 03:51
Is there any managed GUI where it works? I've been asking myself that question also. Nvidia has no clue about the failures and neither do I. :(
ACrowley
15th December 2009, 07:52
it's already in the log...
ofcourse ....but i often take a look to the current Bitrate/Frames when i encode in CRF Mode.
And sometimes i can decide if i should take a lower/higher CRF Value. For example when the Bitrate is to high/low and the Output File becomes to big/small for my needs.
Thats why i think the x264 Status Information about the Bitrate usefull.
BuckMaster
15th December 2009, 11:23
Today NV update driver to GeForce/ION Driver Release 195.81 BETA...maybe have some bug fixes :D
JoeH
15th December 2009, 15:40
Every one of the other GUIs (at least all I know) has the tools in the program folders and the path is not changeable at all. But I would never do things only because all other do them. I have to be sure that this is the right thing. Therefore I would like to have additional feedback. To revert the changes is no problem at all and only a matter of minutes (thanks to source control)
My personal preference would be both to:
1. Do not allow the paths to be changed
2. Continue to offer the option to download a version which is complete, and has all the tools included.
Adub
15th December 2009, 19:08
Zathor
That small input bug still exists in 1058. It appears with any profile and slider position. Simply try and edit the crf value or psy-rd values by punching in the numbers on your keyboard and you will see what I am talking about. It's pretty annoying.
Triccotracco
15th December 2009, 21:43
another 4 "cosmetic" bugs: start from x264 defaults (verified with x264 --fullhelp) I move the preset slide and verified the parameter changes according x264 --fullhelp.
Preset Ultrafast:
cabac toggle should be disable (command line ok)
Preset Veryfast:
I8x8 should be enable with adaptive DCT that come with profile high (command line ok)
now the last two notes:
with "Defaul Settings" button on "Misc" tab --subme 6 appear, should be 7.
the right title of context help for "Weighted Prediction for P-Fr." is "P-frame Weighted Prediction"
hoping that my observations are ok, thank you again Zathor!
Zathor
15th December 2009, 22:55
Simply try and edit the crf value or psy-rd values by punching in the numbers on your keyboard
I reverted the event handler back to the old one. The problem with the old handler is that the value will be only processed if the control lost the focus or the up/down slider is used. Btw I changed ALL NumericUpDown events so that the user experience is the same for all controls.
hoping that my observations are ok, thank you again Zathor!
:thanks: It should be fixed now.
- [AvsReader] workaround for DGMultiSource added. The program will crash less frequently. Patch by neuron2
- [ProfileManager] save the profiles during closing of MeGUI even if the profile folder could not be deleted
- [UpdateWindow] update check is able to find missing files
- [x264ConfigurationPanel] changed a few preset/tuning settings, changed NumericUpDown event
- [AvsReader] workaround for DGMultiSource added. The program will crash less frequently. Patch by neuron2
With this fix the program did not crash for neuron2 (1024MB GPU). On my system (256 GPU) the crash appeared later... I am now able to enqueue the job, close MeGUI and start the job. Far away from perfect and therefore the CUVIDServer is recommended (no crash at all).
Carpo
16th December 2009, 00:37
sounding good :)
[ReX]
16th December 2009, 04:17
This (http://doom10.org/index.php?topic=55.msg397#msg397) tool may come in handy for x64+x264.
I can't test it (no x64 OS atm).
forum king
16th December 2009, 09:42
ok guys i need some info'''
i have been doing whatever dear Zathor has asked us to..
today i have installed megui in separate folder as he said..
now my biggest concern is how to work with the presets.. see what i do is i try to re encode my DVDs and the other HD content to a smaller size i mean to a video bit rate of b/w 500 and 600.. previously i used to use HQ insane or slower then started using Unrestricted 2 pass HQ.. but now as the interface is totally changed i dont have a clue what to use ...
i tried to tweak one x264 by adding high profile , automated 2 pass , turbo , deblocking -1 : -1 , adaptive Bframes - 2 optimal , mv pridiction - auto , trellis 2 always , and MV algorithm - Multihex and sunpixel refinement to 9 ... i mean tried to make it look like unrestricted 2 pass..
the quality came out good but the video was jerky :(...
so please suggest me which profile to use and if i need to tweak something what should they be , so that i can workaround to a bit rate b/w 500 to 600.
thanks
Glenn
SacredCultivator
16th December 2009, 11:08
For some reason, with the latest update... It always says there are updates... Only for the avisynth plugins... I see them in my update cache folder but even after I install/force install, and restart the client... it says there are updates again... Not too sure if anyone else is experiencing this.
nakTT
16th December 2009, 11:29
For some reason, with the latest update... It always says there are updates... Only for the avisynth plugins... I see them in my update cache folder but even after I install/force install, and restart the client... it says there are updates again... Not too sure if anyone else is experiencing this.
So far no issue for me.
Anyone else please share your experience.
Zathor
16th December 2009, 11:44
i tried to tweak one x264 by adding high profile , automated 2 pass , turbo , deblocking -1 : -1 , adaptive Bframes - 2 optimal , mv pridiction - auto , trellis 2 always , and MV algorithm - Multihex and sunpixel refinement to 9 ... i mean tried to make it look like unrestricted 2 pass..
the quality came out good but the video was jerky :(...
so please suggest me which profile to use and if i need to tweak something what should they be , so that i can workaround to a bit rate b/w 500 to 600.
Sadly I am no profile / x264 settings expert. Maybe you can solve it yourself if you compare a new file with an old working file (for example use mediainfo and compare the x264 settings).
For some reason, with the latest update... It always says there are updates... Only for the avisynth plugins... I see them in my update cache folder but even after I install/force install, and restart the client... it says there are updates again... Not too sure if anyone else is experiencing this.
EDIT: Thanks, problem found.
EDIT2: fix in first posting
forum king
16th December 2009, 15:02
Sadly I am no profile / x264 settings expert. Maybe you can solve it yourself if you compare a new file with an old working file (for example use mediainfo and compare the x264 settings).
No issues buddy :)
Thanks for the awesome effort :)
i ll try as you said... also if you come across something or someone then please suggest...
god bless
Glenn
simonb1975uk
16th December 2009, 16:48
Hi,
I'm a newbie but have been lurking for a long time now so please be gentle with me. Am using the new MeGui but when I try and convert my audio tracks via NeroAAC to .mp4, MeGui produces an error. The log says 'Attempted to read or write protected memory. This is often an indication that other memory is corrupt', then MeGui will crash. I am using the 'Nero *scratchpad*' Encoder Setting and the only thing I have changed there is 'Downmix to stereo'. Video encoding works fine, just audio encoding has stopped working. I am using Windows 7 Pro 64-bit.
kool
16th December 2009, 17:08
Download Nero Digital Audio (http://www.nero.com/eng/downloads-nerodigital-nero-aac-codec.php), creat folder neroaacen in C:\Program Files\megui\tools\.
Extract the contents of the zip file to your desktop and move the contant of win32 folder to "C:\Program Files\megui\tools\neroaacenc\".
in MeGUI, go to Options -> Settings -> Program Paths. Look for the entry with NeroAacEnc and click the browse icon to the right. Find neroaacenc.exe which should be in the "megui\tools\neroaacenc\" folder if you followed the instructions above.
simonb1975uk
16th December 2009, 17:13
kool,
I did as you suggested but received the same error.
rack04
16th December 2009, 17:16
Hi,
I'm a newbie but have been lurking for a long time now so please be gentle with me. Am using the new MeGui but when I try and convert my audio tracks via NeroAAC to .mp4, MeGui produces an error. The log says 'Attempted to read or write protected memory. This is often an indication that other memory is corrupt', then MeGui will crash. I am using the 'Nero *scratchpad*' Encoder Setting and the only thing I have changed there is 'Downmix to stereo'. Video encoding works fine, just audio encoding has stopped working. I am using Windows 7 Pro 64-bit.
What are you trying to convert? You say "my audio tracks" but give no indication of the format. Try enabling/disabling "Force decoding via DirectShow".
simonb1975uk
16th December 2009, 17:17
Sorry the format is the .ac3 file created after I have run DGIndex.
rack04
16th December 2009, 17:19
Sorry the format is the .ac3 file created after I have run DGIndex.
What is the exact file name? I have had problems in the past with special charaters used in file names.
simonb1975uk
16th December 2009, 17:21
Enabling 'Force Decoding via DirectShow' did it. Many thanks.
kool
16th December 2009, 17:22
great to hear that you fix it.
forum king
16th December 2009, 18:16
This one gave me good results ( in previous 1057 build by zathor in which we had to download 1056 and then apply the patch )
cabac=1 / ref=8 / deblock=1:0:0 / analyse=0x3:0x133 / me=umh / subme=9 / psy=1 / psy_rd=1.0:0.0 / mixed_ref=1 / me_range=16 / chroma_me=1 / trellis=2 / 8x8dct=1 / cqm=0 / deadzone=21,11 / chroma_qp_offset=-2 / threads=6 / nr=0 / decimate=1 / mbaff=0 / constrained_intra=0 / bframes=3 / b_pyramid=0 / b_adapt=2 / b_bias=0 / direct=3 / wpredb=1 / wpredp=2 / keyint=250 / keyint_min=25 / scenecut=40 / rc_lookahead=60 / rc=2pass / mbtree=1 / bitrate=597 / ratetol=1.0 / qcomp=0.60 / qpmin=10 / qpmax=51 / qpstep=4 / cplxblur=20.0 / qblur=0.5 / ip_ratio=1.40 / aq=1:1.00
this is the one i have been able to make.now ( in the latest build standalone by zathor )
cabac=1 / ref=8 / deblock=1:-1:-1 / analyse=0x3:0x133 / me=umh / subme=9 / psy=1 / psy_rd=1.0:0.0 / mixed_ref=1 / me_range=16 / chroma_me=1 / trellis=2 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=-2 / threads=6 / sliced_threads=0 / nr=0 / decimate=1 / mbaff=0 / constrained_intra=0 / bframes=3 / b_pyramid=0 / b_adapt=2 / b_bias=0 / direct=3 / wpredb=1 / wpredp=2 / keyint=250 / keyint_min=25 / scenecut=40 / rc_lookahead=60 / rc=2pass / mbtree=1 / bitrate=539 / ratetol=1.0 / qcomp=0.60 / qpmin=10 / qpmax=51 / qpstep=4 / cplxblur=20.0 / qblur=0.5 / ip_ratio=1.40 / aq=1:1.00
now the diff in these two are obviously deblocking ( that i can correct :P )
but the lower one has these two settings extra which i am not able to find out how to remove or :P
fast_pskip=1
sliced_threads=0
can someone suggest me via screen which option are these :P and how can i totally disable them so that the lower profile looks exactly like the upper one .. or if its ok to have them :P
Zathor
16th December 2009, 18:29
fast_pskip=1
sliced_threads=0
can someone suggest me via screen which option are these :P and how can i totally disable them so that the lower profile looks exactly like the upper one .. or if its ok to have them :P
Great that you figured it out!
fast_pskip=1 ==> Misc, "No fast P-Skip"
sliced_threads is a new feature since r1364 and is disabled by default. So I assume that sliced_threads=0 is no problem at all compared to your old encoding.
forum king
16th December 2009, 18:33
Great that you figured it out!
fast_pskip=1 ==> Misc, "No fast P-Skip"
sliced_threads is a new feature since r1364 and is disabled by default. So I assume that sliced_threads=0 is no problem at all compared to your old encoding.
thanks mate :) love ya :)
also i would like to ask if you can link us all to the latest profiles made by someone trusted which are totally compatible with your build and latest x264 ...
coz despite numerous searches i was not able to get hold of compatible ones ( for sure )...
coz you know once everything is fixed guys like me who dont have too much of an experience try and rip acc to presets...
regards
Glenn
Adub
16th December 2009, 18:37
I reverted the event handler back to the old one. The problem with the old handler is that the value will be only processed if the control lost the focus or the up/down slider is used. Btw I changed ALL NumericUpDown events so that the user experience is the same for all controls.
Great! Thanks for fixing this Zathor. Works like a charm now.
SacredCultivator
16th December 2009, 18:46
@Zathor: Tried the new version and those avisnyth plugins work like a charm now, thanks!
Zathor
16th December 2009, 19:20
;1353401']This (http://doom10.org/index.php?topic=55.msg397#msg397) tool may come in handy for x64+x264.
I only did a few tests and it seems to be not faster than pipebuf + avs2yuv. Can anyone confirm?
forum king
17th December 2009, 14:51
hi Zathor :)
mate i donno whats gone wrong i have reinstalled windows coz megui was not working in user interface ( something got messed earlier )
i have done everything right :(
but my re encodes are all coming out jerky
any ideas
please help.
EDIT : man i have tried everything but the re encodes are jerky
what do i do :(
EDIT 2 : ok looks like its not the fault of megui o4 x264 there is something wrong in the windows then coz i used 1051 version that i had backedup and it also produced similar famy rip
any ideas please..
JoeH
17th December 2009, 17:52
I was thinking that when you add the new version of MeGUI to the "stable" servers and thousands begin downloading the updates, what will probably most confuse users will be the new + old profiles confusion - they'll have their old profiles, plus new profiles, with no easy way to distinguish them.
Here is what I would suggest:
1. Move all old profiles to a backup folder
2. Install only new profiles
3. Remove STx264 from the update servers
4. Display a message stating that the old profiles have been moved to the backup folder (maybe with a link) and that they are available there if needed.
Zathor
17th December 2009, 18:13
EDIT 2 : ok looks like its not the fault of megui o4 x264 there is something wrong in the windows then coz i used 1051 version that i had backedup and it also produced similar famy rip
any ideas please..
Sorry, no idea. If you have reinstaled your PC which kind of video filters / codec do you have installed afterwards? Maybe one of them - or your source file - is causing the trouble.
I was thinking that when you add the new version of MeGUI to the "stable" servers and thousands begin downloading the updates, what will probably most confuse users will be the new + old profiles confusion - they'll have their old profiles, plus new profiles, with no easy way to distinguish them.
Because of the lack of negative feedback I have already added the version 1059 (more or less the lastest 1058 renamed to 1059) to the official development server. I did it an hour ago...
Here is what I would suggest:
1. Move all old profiles to a backup folder
2. Install only new profiles
3. Remove STx264 from the update servers
4. Display a message stating that the old profiles have been moved to the backup folder (maybe with a link) and that they are available there if needed.
1./4. I do not know what is more confusing - to lost the old profiles or have the old and the new ones. The old ones are working more or less. The new settings will revert to default values (mostly bad at all).
2./3. STx264 can only be found on the stable server. The development server do not have these profiles.
forum king
17th December 2009, 18:17
@ Zathor .. no mate i havent done anything fancy..
after setting windows up
i installed CCCP
avisynth
1056 and updated with ur server.. ( also did a standalone installation nas is there on page one ) ( also used a 1051 backup.. but all producing video which are like jerky as when you see a video in an old mobo with low memory )
the system is quad core amd with 8GB ddr2 ram no graphics card..
was ripping well on it before this.. but 2 days back megui suddently lost its User interface though it could be seen running in task manager.. thats whay did a reinstall.
Guest
17th December 2009, 20:15
Start a new thread, forum_king. Analyzing why your rips are jerky is off topic in here.
forum king
17th December 2009, 20:20
Start a new thread, forum_king. Analyzing why your rips are jerky is off topic in here.
Ok thanks dear..
duely noted.
love ya zathor
Triccotracco
17th December 2009, 21:20
Gentlemen,
please test as much as possible, if there are some issues don't exitate to post. Thank you Zathor for the big work, from my site I continue to test as my knowledge permits.
:thanks::thanks::thanks:
AiDz0r
18th December 2009, 02:09
well guys :( i am giving up
looks like i cant use the latest megui builds and the benefits of x264.
i have done everything as was said here and at the troubleshooting thread..
but it just wont work out..
i used the latest build by Zathor ( the 2nd one ) and installed it in a separate folder..
used unrestricted 2 pass HQ with SLower settings
it will do the first pass and give a STANDARD ERROR STREAM error upon second always..
sometimes the same error on first pass as well..
can someone please please please guide me how should i go about it all.. i have been trying to do this from last 3 days in TOTALO vain.
it looks i ll have to go back to 1051 :(
Just as forum king said, I'm having the same problem. but i searched up and i guess its because of the presets? Is there any ready-working presets available? for normal video encoding.
http://img26.imageshack.us/img26/6562/15796918.jpg
stax76
18th December 2009, 04:21
@newbie
The root of the most problems reported about MeGUI is newbies trying to use a application designed for experts. There are applications that take much better care about newbies.
Generally if a software don't work you start with the most simplest scenario and then modify it until it breaks to understand where and why it breaks. In a video encoding scenario this would be using a simple AviSynth script that don't contain any filter other than AVISource with a simple XviD source file and encode it with the command shell with a x264 command line that don't contain any switches switches other then IO, this would like like this:
x264.exe --output "<target>" "<source>"
If this works then you would use the script and command line in MeGUI, then you add settings until it breaks. Verify if it might be a encoder or decoder problem, try different x264 versions, try players with different playback engines like VLC and SMPayer, if all fails investigate the OS and the hardware. Don't reinstall your OS, be a man and fix it, use system recovery if necessary.
Recently I told a user I don't have much time to assist him with a particular issue I've not given a high priority, I told him to investigate it himself and tell me if he finds out something. Apparently he was strong and didn't give up, a few days later he came back and told me exactly where and why it breaks, he uploaded sample files and told me how to reproduce the problem. It took me 2 minutes to find the problem and 2 more to fix the code.
Maybe a good idea to tell more often users to trying to find out what the problem is themselves, many just come and tell that it crashes but don't provide enough details that it would allow for anything more then guesswork.
nakTT
18th December 2009, 04:37
Hi,
Any chance for us to get x264 rev1376 from our update server?
:thanks:
poisondeathray
18th December 2009, 04:52
@AiDz0r - I've seen several very similar crashes reported by some people (good luck trying to find the exact post with this search system :) ), and the fix was to replace the x264.exe version with another build. Apparently there was some incompatiblity isssue with jeeb's build and that specific system/cpu/os or whatever.
Try a build from the url below, backup the old x264.exe (make a copy just in case), and replace it with a renamed one that you downloaded from the below (ie. rename it to x264.exe and put in the same directory)
http://komisar.gin.by/
poisondeathray
18th December 2009, 04:55
@nakTT , you can download and manually replace the x264.exe if you want from the x264 build thread. You can backup (make a copy) of the original in a folder
Just be aware the various builds can have different patches applied
AiDz0r
18th December 2009, 04:59
@newbie
The root of the most problems reported about MeGUI is newbies trying to use a application designed for experts. There are applications that take much better care about newbies.
Generally if a software don't work you start with the most simplest scenario and then modify it until it breaks to understand where and why it breaks. In a video encoding scenario this would be using a simple AviSynth script that don't contain any filter other than AVISource with a simple XviD source file and encode it with the command shell with a x264 command line that don't contain any switches switches other then IO, this would like like this:
x264.exe --output "<target>" "<source>"
If this works then you would use the script and command line in MeGUI, then you add settings until it breaks. Verify if it might be a encoder or decoder problem, try different x264 versions, try players with different playback engines like VLC and SMPayer, if all fails investigate the OS and the hardware. Don't reinstall your OS, be a man and fix it, use system recovery if necessary.
Recently I told a user I don't have much time to assist him with a particular issue I've not given a high priority, I told him to investigate it himself and tell me if he finds out something. Apparently he was strong and didn't give up, a few days later he came back and told me exactly where and why it breaks, he uploaded sample files and told me how to reproduce the problem. It took me 2 minutes to find the problem and 2 more to fix the code.
Maybe a good idea to tell more often users to trying to find out what the problem is themselves, many just come and tell that it crashes but don't provide enough details that it would allow for anything more then guesswork.
Well fist of all, i did search it and couldn't find anything related. Yet I'm here to get help not advise and again this is a forum to help other people get feedback and so on. It's more like you don't even understand why its giving an error so you're just getting away with it and tired to find out what's making the error. I tried everything, and as always i do a research on the forum and other forum to find solution then i post my comment for help. if i did find the solution why would i bother... and you have totally misunderstood me, I can playback my videos I tried re-installing re-updating my MEGUI and not using the old system by using "Zathor's patched build" and none of them work well in encoding, I could use normal basic commands, but their not useful, when I could make my video better why wouldn't I?
Inspector.Gadget
18th December 2009, 06:48
Note that "playback works fine" isn't the same as "DirectShowSource (and AVISource, which uses VFW) is able to access the correct filters and they work without incident".
medp7060
18th December 2009, 07:09
Well fist of all, i did search it and couldn't find anything related. Yet I'm here to get help not advise and again this is a forum to help other people get feedback and so on. It's more like you don't even understand why its giving an error so you're just getting away with it and tired to find out what's making the error. I tried everything, and as always i do a research on the forum and other forum to find solution then i post my comment for help. if i did find the solution why would i bother... and you have totally misunderstood me, I can playback my videos I tried re-installing re-updating my MEGUI and not using the old system by using "Zathor's patched build" and none of them work well in encoding, I could use normal basic commands, but their not useful, when I could make my video better why wouldn't I?
Do not get disappointed. I am also starting to learn x264 encoding recently, although I have been doing Xvid encoding for a number of years. There was time when I was called "Nut" or "Monkey" by some experts, but I still keep reading and try to learn the basics. It will take time to get familiar with a well-designed GUI such as MeGUI and many others. I do not know what is your problem, but based on Xvid experience, before you load it into MeGui, first try to player it (the script) using Windows Media Player, by doing that, it will tell you what is the basic problem. Then start to solve it from there.
nakTT
18th December 2009, 08:03
@nakTT , you can download and manually replace the x264.exe if you want from the x264 build thread. You can backup (make a copy) of the original in a folder
Just be aware the various builds can have different patches applied
Thanks for the reply bro.
The builds with patches will not going to have any effect on normal user right?
:thanks:
Zathor
18th December 2009, 09:43
Any chance for us to get x264 rev1376 from our update server?
Did not notice that there has been a new one. Thanks for the information - new file online.
...the fix was to replace the x264.exe version with another build. Apparently there was some incompatiblity isssue with jeeb's build and that specific system/cpu/os or whatever.
If jeeb's build really is the source of the problem I will switch to another one. Can anyone confirm that jeeb's build is crashing and another build not?
The builds with patches will not going to have any effect on normal user right?
The patched builds are needed if you want to use the --nal-hrd switch and this switch is needed if you want to follow the BluRay specs. So if your target device is not BluRay you can disable this switch in the profile and can use an unpatched build.
nakTT
18th December 2009, 11:06
Did not notice that there has been a new one. Thanks for the information - new file online.
No problem. Will be happy to let you know when the next update available.
The patched builds are needed if you want to use the --nal-hrd switch and this switch is needed if you want to follow the BluRay specs. So if your target device is not BluRay you can disable this switch in the profile and can use an unpatched build.
Is that mean there will be some kind of negative effect if I use patched version (e.g Jeeb) if my target is not BluRay (just normal mkv file to be played on my PC)?
:thanks:
prOnorama
18th December 2009, 11:58
@ nakTT: you can just go to x264.nl, grab the vanilla x264 1376 build and replace the patched build in the Megui\Tools\x264 folder
(I've never used JEEB's builds with MeGUI, always vanilla since I don't need the nal-hrd patch for Blu-ray compatibility)
nakTT
18th December 2009, 12:03
@ nakTT: you can just go to x264.nl, grab the vanilla x264 1376 build and replace the patched build in the Megui\Tools\x264 folder
(I've never used JEEB's builds with MeGUI, always vanilla since I don't need the nal-hrd patch for Blu-ray compatibility)
Thanks for the reply.
BTW, vanilla = Original (no patch whatsoever) right? Sorry for my english.;)
:thanks:
Triccotracco
18th December 2009, 14:09
BTW, vanilla = Original (no patch whatsoever) right?
Yes vanilla = Unpatched, BTW also jeeb's builds are good IMO.
nakTT
18th December 2009, 14:20
Yes vanilla = Unpatched, BTW also jeeb's builds are good IMO.
Thanks for the reply bro.
:thanks:
JoeH
18th December 2009, 14:49
1./4. I do not know what is more confusing - to lost the old profiles or have the old and the new ones. The old ones are working more or less. The new settings will revert to default values (mostly bad at all).
2./3. STx264 can only be found on the stable server. The development server do not have these profiles.
OK. I was referring to when you move over the new builds to the "Stable" servers.
Alf Bundy
18th December 2009, 15:44
First, thank you for your work Zathor.
By fixing that : - (zathor) [x264Config] fix an issue where custom profile settings may be lost,
you earned the Nobel Prize of ABF (Annoying Bug Fixing).
http://img290.echo.cx/img290/9768/yahoo6lp.gif
Second : Since the 1059 update, I got an error when closing MeGUI :
http://img20.imageshack.us/img20/8459/meguiclosingerror.png
The part in french says "object's reference is not defined to an object's instance" (translation might not be accurate, but even in french it makes no sense to me, so ...)
I'm on WinXP SP3 and this closing error does not happen all the time.
- When I start MeGUI and close it without doing anything -> no error.
- When I start MeGUI and use it to encode a single WAV to AAC -> no error when closing.
- But when I encode multiples WAV's or video scripts, I have to kill MeGUI from the task manager.
I didn't find any other problem with 1059.
Thanks again !
Zathor
18th December 2009, 16:54
Since the 1059 update, I got an error when closing MeGUI[...]The part in french says "object's reference is not defined to an object's instance" (translation might not be accurate, but even in french it makes no sense to me, so ...)
There should be more details in the log file. Can you send it to me, please (PM)?
[ReX]
18th December 2009, 18:59
In Subpixel Refinement/subme, the tooltip says that x264's default is 7, it actually is, but in x264 configuration dialog "6" is actually the default but the result is 7. So you won't get 6.
Zathor
18th December 2009, 19:14
;1354397']In Subpixel Refinement/subme, the tooltip says that x264's default is 7, it actually is, but in x264 configuration dialog "6" is actually the default but the result is 7. So you won't get 6.
Thanks, I found a line in the source code where subme defaults incorrectly to 6. I'm unsure if this is the problem you have described but nevertheless this has been fixed. You have to wait a little bit (maybe up to a few days) before I can upload a new build because of ongoing other changes.
[ReX]
18th December 2009, 19:16
Thanks, I found a line in the source code where subme defaults incorrectly to 6. I'm unsure if this is the problem you have described but nevertheless this has been fixed. You have to wait a little bit (maybe up to a few days) before I can upload a new build because of ongoing other changes.
That's it. Don't worry, I'll just add "--subme 6" in Custom Command Line. :p
Alf Bundy
18th December 2009, 22:34
about a fatal error when closing MeGUI
There should be more details in the log file. Can you send it to me, please (PM)?
Well, there's nothing in the logs about this error. Only encoding related stuffs.
... And I can't reproduce it anymore !
I tried a dozen of multiple video & audio encodes, and MeGUI closed normally with no error.
So don't worry about that. If it happen again, I will check the log tab and send you the log file.
But I noticed something else in the logfile :
[Information] Log
-[Information] Versions
--[NoImage] MeGUI Version : 0.3.1.1059
--[NoImage] OS : Windows XP Professional x64 SP3 (5.1.196608.2600)
--[NoImage] Latest .Net Framework installed : 3.5 (3.5.30729.01)
--[NoImage] Avisynth Version : 2.5.7.0
My XP is 32bit, not 64bit. So I thought it would write x86 (I may be wrong).
There's absolutely no issue with that. MeGUI works great.
It's only (probably useless) for your information. :o
Zathor
18th December 2009, 22:47
My XP is 32bit, not 64bit. So I thought it would write x86 (I may be wrong).
There's absolutely no issue with that. MeGUI works great.
It's only (probably useless) for your information. :o
I fixed that already yesterday and committed it a few hours ago to sourceforge. [OSInfo] changed x64 detection, fixed a few typos But thanks for your report! Oh, and it is NOT useless. Without this fix another function does not work properly.
TDC.net
18th December 2009, 23:03
Another question:
If I run several audio encodes in temporary workers, it asks me to close each of this workers at the end.
Why does it ask for this? What is the idea for that? I don't really understand it, so it seems useless to me.
Do we need this or could it be removed (or optionally disabled)?
Thanks
Raist
Adub
18th December 2009, 23:19
Another question:
If I run several audio encodes in temporary workers, it asks me to close each of this workers at the end.
Why does it ask for this? What is the idea for that? I don't really understand it, so it seems useless to me.
Do we need this or could it be removed (or optionally disabled)?
Thanks
Raist
You answered your own question. You are using temporary workers in this situation. If you don't want to shutdown your workers, then create permanent ones.
And just because you don't understand something doesn't mean that it is useless.
Zathor
18th December 2009, 23:27
If you don't want to shutdown your workers, then create permanent ones.
Exactly that is the point. Is the question "do you want to shutdown the worker" really necessary? Or should a temporary worker be closed automatically after the assigned job has been completed? And as I understand TDC.net that is his question, too.
Adub
18th December 2009, 23:34
Ah! I understand the question now. Okay, I see your point. Since I don't edit the code myself, you can do it one of two ways. Have a checkbox in the settings menu to disable this, or simply turn it off all together. It really doesn't make a whole lot of sense.
TDC.net
19th December 2009, 00:02
Sorry if my question was confusing.
Zathor, you're right, the question is "why do I have to confirm the closure of this temporary workers".
I do not want to have permanent workers because I want only one video to encode at the same time, cause it's using almost 100% CPU, but several audio encodes at the same time to speed up audio encoding (nero uses only one of my eight threads for each transcode).
So what'S the idea for this question "Close temp worker"?
BEst would be an option to have several workers for audio, but (as option) only one worker for video. But I guess this is really a little bit special, so I don't know if this would be useful for others as well...
[ReX]
19th December 2009, 01:48
I fixed that already yesterday and committed it a few hours ago to sourceforge. [OSInfo] changed x64 detection, fixed a few typos But thanks for your report! Oh, and it is NOT useless. Without this fix another function does not work properly.
Is your patched build merged with the SF.net one or aren't all the changes and fixes implemented on it?
i.e. your build = SF.net MeGUI SVN?
Edit: Looks like I have to delete a profile two times to actually delete it. (edited again, happened one or two times, I can't reproduce. maybe bad profiles?)
Edit 2: The profile (http://www.mediafire.com/?rzqezmjz1qj) I use for anime, if anyone is interested (not a bad profile).
quantum5uicid3
19th December 2009, 03:33
the profiles are saved when you close megui, so if you delete it in explorer when megui is open, it will recreate it when you close megui. yes-no?
ircopdd
19th December 2009, 04:22
why megui 1059 use dgavcindex??
http://txd9gg.bay.livefilestore.com/y1pvrXyrTiZZg0pzNo9BvSTHGcuMrZ37Kdi4tjhbvh9Lm2somvZntX05zGISaXwPIjJ-A844h3dNVTg_x2t9hIkLt8-PImznYMh/avc.jpg
I can not choose dgavcindexNV
Adub
19th December 2009, 08:19
TDC,simply create one worker for your video files then assign your audio files to a different worker or workers. An encode will only queue on a worker basis, so as long as you use separate workers you should be fine.
TDC.net
19th December 2009, 09:01
Thanks Adub for the hint!
Zathor
19th December 2009, 09:47
Regarding the temporary workers. I would like to change it that way that a temporary worker is closed automatically without question. Any objections arising?
the profiles are saved when you close megui, so if you delete it in explorer when megui is open, it will recreate it when you close megui. yes-no?
Correct. Settings, log file and profiles are saved during closing of MeGUI.
;1354533']Is your patched build merged with the SF.net one or aren't all the changes and fixes implemented on it?
i.e. your build = SF.net MeGUI SVN?
No, the build I am using is different from the one at SF. Otherwise I had to commit every few minutes and the commit may be not stable at all. I commit only the changes as soon as I am sure that they are working.
EDIT: Sorry, I have been half asleep. Yes, the build you can download in this thread is already merged completly with SF. But some new things have not been committed yet.
why megui 1059 use dgavcindex?? I can not choose dgavcindexNV I had to change it because of the a few changes to the tool paths. Nevertheless the next build will have hopefully support for DGIndexNV and therefore you won't need dgavcindexnv anymore.
arestarh
19th December 2009, 13:35
Zathor
Thanks for your work under MeGUI!
My question about content of x264_r1376.zip at http://www.constructd.com/megui/:
why it include project files and some .exe files
x264_64_wrap.c
x264_64_wrapper.c
avs4x264.exe
vfw4x264.exe
avisynth_c.h
Zathor
19th December 2009, 13:56
Zathor
Thanks for your work under MeGUI!
My question about content of x264_r1376.zip at http://www.constructd.com/megui/:
why it include project files and some .exe files
The next build includes support for x64 versions of x264.exe. The wrapper is needed to feed 64bit x264 with 32bit avisynth. The source code is included because that's the way the author has been distributed the files.
nakTT
19th December 2009, 13:57
Zathor
Thanks for your work under MeGUI!
My question about content of x264_r1376.zip at http://www.constructd.com/megui/:
why it include project files and some .exe files
Thanks for the question. I was about to ask the same question.
:thanks:
nakTT
19th December 2009, 14:00
The next build includes support for x64 versions of x264.exe. The wrapper is needed to feed 64bit x264 with 32bit avisynth. The source code is included because that's the way the author has been distributed the files.
Is that means if my OS is 64bit (which it is), MeGUI will automatically execute x264 64bit version instead of 32bit version? Any idea on speed benefit?
:thanks:
Zathor
19th December 2009, 14:09
Is that means if my OS is 64bit (which it is), MeGUI will automatically execute x264 64bit version instead of 32bit version? Any idea on speed benefit?
I did several benchmarks and the process has been in average 6% faster (mostly between 4 and 8%) than the 32bit x264. My conclusion is also that the avs4x264.exe is slightly faster than the "old" method with pipebuf.exe and avs2yuv.exe. But this may vary from system to system and setting to setting.
nakTT
19th December 2009, 15:03
I did several benchmarks and the process has been in average 6% faster (mostly between 4 and 8%) than the 32bit x264. My conclusion is also that the avs4x264.exe is slightly faster than the "old" method with pipebuf.exe and avs2yuv.exe. But this may vary from system to system and setting to setting.
Thanks for the input and great to know about the 6% improvement. To me 6% improvement is A LOT in encoding world, which I'm very happy to hear. But I guess you missed my first question. :p
:thanks:
Zathor
19th December 2009, 15:05
Is that means if my OS is 64bit (which it is), MeGUI will automatically execute x264 64bit version instead of 32bit version?
Yes :)
nakTT
19th December 2009, 15:14
Yes :)
Glad to know that too.
Is there any way for the to tell which version (not revision) of x264 (either 32/64 bit) used by looking at the output video? I mean, does MeGUI have any tools to determine it? Thanks for your excellent work for MeGUI.
:thanks:
Zathor
19th December 2009, 15:16
Is there any way for the to tell which version (not revision) of x264 (either 32/64 bit) used by looking at the output video? I mean, does MeGUI have any tools to determine it?
The output video is the same for both encoders. In the log file you can see which command is executed - avs2x264.exe for 64bit and x264.exe for 32bit.
nakTT
19th December 2009, 15:36
The output video is the same for both encoders. In the log file you can see which command is executed - avs2x264.exe for 64bit and x264.exe for 32bit.
Glad to know that.
:thanks:
Zathor
19th December 2009, 15:50
0.3.1.1060
- [OSInfo] changed x64 detection, fixed a few typos
- [x264Encoder] + [UpdateWindows] added support for x64 x264
- [CommandlineJobProcessor] wait for aborted process to be closed before trying to delete the output file
- [x264ConfigurationPanel] changed subme default value according to the x264 specs
- merged the DG Indexer, added DGIndexNV support and removed the 3 old NV indexer
- [SettingsForm] added the ability to deselect the usage of the CUVIDServer
- [DialogManager] CUVIDServer will be started if necessary and only closed if started by MeGUI
- [UpdateWindow] if a file is not longer available it will not be selected for download
- added DGIndexNV download package, moved the location of the DGAVCDecode.dl to the DGAVCIndex package
- [DG Creator] if DGIndexNV is licensed it will be preselected - otherwise it will be disabled
- [ScriptServer] LoadPlugin will be called automatically for the different indexer types
nakTT
19th December 2009, 16:21
The output video is the same for both encoders. In the log file you can see which command is executed - avs2x264.exe for 64bit and x264.exe for 32bit.
My OS is Vista Business 64bit, here what I got from MeGUI log.
Job commandline: "C:\MeGUI\tools\x264\x264.exe"
Is that means the 32bit version of x264 has been choosen by MeGUI instead of the 64bit?
:thanks:
Zathor
19th December 2009, 16:32
Is that means the 32bit version of x264 has been choosen by MeGUI instead of the 64bit?
Yes...
In the log file is a line about your OS. There should be an x64 in the string.
EDIT: MediaFire is sloww as hell for me at the moment. So I cannot check if the file has been correctly uploaded. Does the MEGUI.exe has a timestamp from today?
nakTT
19th December 2009, 16:41
Yes...
In the log file is a line about your OS. There should be an x64 in the string.
EDIT: MediaFire is sloww as hell for me at the moment. So I cannot check if the file has been correctly uploaded. Does the MEGUI.exe has a timestamp from today?
I'm not quite sure what you means, sorry for my english.:)
By the way, my OS is 64bit and detected as 64bit. Sorry, I forgot to post this info in my previous post. Here you go:
-[Information] Versions
--[NoImage] MeGUI Version : 0.3.1.1059
--[NoImage] OS : Windows Vista Business Edition x64 SP2 (6.0.131072.6002)
--[NoImage] Latest .Net Framework installed : 3.5 (3.5.30729.01)
--[NoImage] Avisynth Version : 2.5.8.5
:thanks:
Zathor
19th December 2009, 16:48
I'm not quite sure what you means, sorry for my english.:)
I want to know if the file you are using is the new one. I have not changed the build number yet, so 0.3.1.1059 is the number for the old and the new version. Can you please have a look at the changelog at "Help\Changelog". Are there any lines regarding the new changes?
By the way, my OS is 64bit and detected as 64bit. Sorry, I forgot to post this info in my previous post. Here you go:
-[Information] Versions
--[NoImage] MeGUI Version : 0.3.1.1059
--[NoImage] OS : Windows Vista Business Edition x64 SP2 (6.0.131072.6002)
--[NoImage] Latest .Net Framework installed : 3.5 (3.5.30729.01)
--[NoImage] Avisynth Version : 2.5.8.5
That's ok, so the x64 detection is working for your system.
MuLTiTaSK
19th December 2009, 16:51
Yes...
In the log file is a line about your OS. There should be an x64 in the string.
EDIT: MediaFire is sloww as hell for me at the moment. So I cannot check if the file has been correctly uploaded. Does the MEGUI.exe has a timestamp from today?
maybe uploading it to multiple hosting sites will help MultiUpload (http://www.multiupload.com/)
gino25
19th December 2009, 17:29
hello, i've a simple question on MEGUI.
I've downloaded it from sourceforce (i have version 1056 installed).
If i use internel update megui download for example x264 build 1183. But i check on x264 website that is out version 1376.
Maybe internal update is... out-of date?
Or did i dowload a wrong version? Thank you very much
nakTT
19th December 2009, 17:36
I want to know if the file you are using is the new one. I have not changed the build number yet, so 0.3.1.1059 is the number for the old and the new version. Can you please have a look at the changelog at "Help\Changelog". Are there any lines regarding the new changes?
Thanks for the reply. As for the changelog, here you go:
0.3.1.1059
- (zathor) [MeGUISettings] update_cache location and avisynth plugin location cannot be changed anymore
- (zathor) [x264Settings] changed the default *scratchpad* settings to x264 default (preset and some other settings have been wrong)
- (zathor) [x264ConfigurationPanel] changed b-frames value in preset slower
- (zathor) [x264ConfigurationPanel] subme 10 instead of 9 will force trellis 2 and aq-mode > 0
- (zathor) [x264ConfigurationPanel] removed dependency between mb-tree and aq-mode
- (zathor) [x264Encoder] fixed aq-mode command line generation (aq-mode 0 has never been appended)
- (zathor) [x264Encoder] fixed aq-mode in all presets
- (zathor) [DialogManager] minor change to the CUVIDServer call
- (zathor) [MeGUISettings] + [SettingsForm] all automatically installed tool paths cannot be changed anymore
- (zathor) [AvsReader] workaround for DGMultiSource added. The program will crash less frequently. Patch by neuron2
- (zathor) [ProfileManager] save the profiles during closing of MeGUI even if the profile folder could not be deleted
- (zathor) [UpdateWindow] update check is able to find missing files
- (zathor) [x264ConfigurationPanel] changed a few preset/tuning settings, changed NumericUpDown event
- (zathor) [UpdateWindow] fixed wrong savepath after moving MeGUI directory
:thanks:
Zathor
19th December 2009, 17:36
hello, i've a simple question on MEGUI.
I've downloaded it from sourceforce (i have version 1056 installed).
If i use internel update megui download for example x264 build 1183. But i check on x264 website that is out version 1376.
Maybe internal update is... out-of date?
Or did i dowload a wrong version? Thank you very much
The new changes have not been published to the stable server. If you want to test them you can switch to the development server (Options\Settings\Extra config\Configure Servers\Development)
Zathor
19th December 2009, 17:38
Thanks for the reply. As for the changelog, here you go
This is the old build. Redownload the file from the first post and extract them to your MeGUI directory. The MeGUI.exe should be newer that your file.
nakTT
19th December 2009, 17:39
hello, i've a simple question on MEGUI.
I've downloaded it from sourceforce (i have version 1056 installed).
If i use internel update megui download for example x264 build 1183. But i check on x264 website that is out version 1376.
Maybe internal update is... out-of date?
Or did i dowload a wrong version? Thank you very much
Perhaps you want to download "MeGUI Patched Build" by Zathor. It has all the latest updates.
gino25
19th December 2009, 17:44
thank you very much nakTT and zathor
nakTT
19th December 2009, 17:59
This is the old build. Redownload this file http://www.mediafire.com/download.php?t0ztwzozm42 and extract them to your MeGUI directory. The MeGUI.exe should be newer that your file.
Will do that. Thanks
Just curious, is that means the one on the update server is not the current one? Because mine is the latest update as far as the update server is concern.
:thanks:
Zathor
19th December 2009, 18:08
Just curious, is that means the one on the update server is not the current one? Because mine is the latest update as far as the update server is concern./QUOTE]
[QUOTE=Zathor;1354724]Because of the more or less heavy changes there may be bugs! Therefore I will not update the link in the first posting at the moment or upload this file to the update servers.
:) But I may add it to the first post as an option.
nakTT
19th December 2009, 18:19
Because of the more or less heavy changes there may be bugs! Therefore I will not update the link in the first posting at the moment or upload this file to the update servers.
:) But I may add it to the first post as an option.
I see. Now I understand that I need MeGUI 1060 to get x264 64bit work.
x264_64_wrap.c
x264_64_wrapper.c
avs4x264.exe
vfw4x264.exe
avisynth_c.h
Before this I thought that as long as I have all of the above (updated by the update server), the x264 64bit will just work.
Thanks for clear things up.
:thanks:
Kagain
19th December 2009, 19:22
A request
It would be nice to have a droplist with --sar values somewhere.
10:11, 1:1, 12:11, 40:33, 4:3, 15:11, 16:11, 3:2, 160:99, 18:11, 20:11, 64:33, 2:1, 24:11, 80:33, 32:11
I'm too lazy to write it in the command line everytime I need one of them.
I haven't had any problems with the GUI so far.
Thanks
SacredCultivator
19th December 2009, 19:24
Just tested the new Dev. Build and got to say, loving that it auto detects my OS as 64-bit and uses the 64-bit of x264. Thanks.
Triccotracco
19th December 2009, 19:26
Because of the more or less heavy changes there may be bugs! Therefore I will not update the link in the first posting at the moment or upload this file to the update servers.
testing, new DG Creator works for me, I don't know for DGIndexNV due my ATI graphics card :angry::angry::angry:
[ReX]
19th December 2009, 19:44
the profiles are saved when you close megui, so if you delete it in explorer when megui is open, it will recreate it when you close megui. yes-no?
Yes, but I deleted using MeGUI.
But they were old profiles, they weren't supposed to be there anyway, so no problem. :)
Alf Bundy
19th December 2009, 21:00
With the new dev. build, my XP SP3 32bits is now detected correctly.
[Information] Log
-[Information] Versions
--[NoImage] MeGUI Version : 0.3.1.1059
--[NoImage] OS : Windows XP Professional x86 SP3 (5.1.196608.2600)
--[NoImage] Latest .Net Framework installed : 3.5 (3.5.30729.01)
--[NoImage] Avisynth Version : 2.5.7.0
(it was x64 with the previous one.)
:)
ircopdd
20th December 2009, 04:37
1060 DGIndexNV
You can join all the files in support?
I can not open the TS file
----------------------------------------------
DGindexNV
I open the DVD VOB files appear mosaic
http://txd9gg.bay.livefilestore.com/y1pF40zNC-FMW9HB2K9A50BN7gdUq7MVd7mpLvILGMTLuNgrnOjfh1oFmLkjR8HUrf2z-Xv9pevjh_4TNIrb-hIJPDN4KB3RgwN/MASK.JPG
-----------------------------------------------
DGAVCindex
Open the AVC TS appear mosaic
http://txd9gg.bay.livefilestore.com/y1p2az0z1unoYhYO_2yOJf4zxDqFcN-5yXWD3b6uBhV0n8U1GZJqus8THkuVT2QoPI-OLpltf9d5zjrVDPT8kb8Ar2rD-iijKJH/Snap2.jpg
But DGAVCindexNV normal
forum king
20th December 2009, 08:33
wow thats a great news Zathor on the Team now :)
congratulations mate..
all the best :)
JoeH
20th December 2009, 08:56
Zathor,
Thanks! I just ran some tests, and am seeing a TWENTY PERCENT :cool: speed improvement with the 64-bit build (on a Core i7 overclocked to 3.8GHz). Amazing!
:thanks::thanks::thanks::thanks:
ACrowley
20th December 2009, 09:54
My Version info is still 1059 ? But the exe is 0.3.1.1060 right ?
x264_x64 works fine so far :)
Perfomance with x264 is great! I run it on a Intel i5 750 ~3,36Ghz...
As i say..i would like to see the current kbps info in the Process View :) Please add it ...
Zathor
20th December 2009, 10:36
1060 DGIndexNV
You can join all the files in support?
I can not open the TS file
Sorry, I do not understand your problem/question.
DGindexNV
I open the DVD VOB files appear mosaic
DGAVCindex
Open the AVC TS appear mosaic
But DGAVCindexNV normal
Please try the old/stable release of MeGUI or the DGAVCIndex and DGIndex tool directly. I have no problems with VOB or (MPGE2) TS files, but I have no AVC TS file to verify it.
My Version info is still 1059 ? But the exe is 0.3.1.1060 right ?
Yes, I will change the version number as soon as I publish it on the update server.
As i say..i would like to see the current kbps info in the Process View :) Please add it ...
It's on the list but I'm still unsure how to implement it.
ircopdd
20th December 2009, 13:21
Sorry, I do not understand your problem/question.
Please try the old/stable release of MeGUI or the DGAVCIndex and DGIndex tool directly. I have no problems with VOB or (MPGE2) TS files, but I have no AVC TS file to verify it.
http://txd9gg.bay.livefilestore.com/y1pWv7qIGXnLcIJM1nAaInFBBXI3WrHY-inHdHuHD5D1_u7_Lf4NA8AMyosbXuuL9YQXSBCIQotJVG4wq6ur8ztUgJegRbf77-A/Snap3.jpg
Can not be opened ".TS" files
old megui
http://txd9gg.bay.livefilestore.com/y1puU1g000uX_D4bQ1ghV5lsVGLUB5wEAGo7W8zzQBcMRgCqTMH83e2Zd7YKhkroUaFy3JDBv6aY7NueAKkByvOqHq0EdLwS-f5/Snap5.jpg
AVC TS file
http://www.multiupload.com/0QPKTZPTBC
Zathor
20th December 2009, 16:14
Can not be opened ".TS" files
Fixed, download in the first posting.
Regarding your DGAVCIndex problems. I have the same problem with your file even with a basic avs script outside of MeGUI. Therefore I assume it is a problem with the file or DGAVCIndex. Please have a look at the DGIndex forum: http://forum.doom9.org/forumdisplay.php?f=5
ircopdd
20th December 2009, 16:36
Thanks you:thanks:
Cyber-Mav
20th December 2009, 17:19
whoa is this correct, i can see in taskmanager that megui has now launched x264_64.exe and encoding the same test clip i did with the 32bit version i averaged 10fps, now im getting average of 11.5-12.2 fps, 64bit version seems to have provided around 15%+ speed increase on my q9650 cpu.
what sort of difference are you guys seeing going from 32bit to 64bit version.
JoeH
20th December 2009, 17:34
Hi guys,
One feature I think that would be very interesting now that we are using the new X264 versions would be to allow files other than AVS scripts as input files. As X264 can now read many files directly without an AVS script, that would simplify at least certain encodes.
Cyber-Mav
20th December 2009, 17:54
ok my encode has finished with the 64bit x264 and looks like something has gone wrong here is the screenshots:
input source is vob file segment from starwars dvd short 3 mins 32sec long.
firsly here is what it shoudl look like encoded with the 32bit version of x264:
http://img297.imageshack.us/img297/8981/x26432bit.jpg
now here is the screenshot of the encode done with the 64bit version of x264:
http://img502.imageshack.us/img502/1458/x26464bit.jpg
as you can see its mashed up big time. decoder used was coreavc 1.9.5 in software and in cuda mode and still the 64bit version is mangled up output.
my test clip is 40mb big, if someone would like i can upload both the 32bit encode and the 64bit encode, both at 40mb big, and post links to them here. let me know if its required. im off to test again and see if i happens on other video.
actually after watching the scrambled video im wondering could this be a decoding issue as in when megui is feeding the video to x264? i used the 1059 build version thats 32bit only when i did the 32bit encode, then i downloaded from the first link the updated 1059 aka 1060 which enables 64bit x264 support. im going to try encoding again but forcing it to use the 32bit encoder. (probably rename x264 32bit version into x264_64.exe) and see what happens.
lnatan25
20th December 2009, 18:11
Cyber-Mav, did you have proper 64bit codecs and AviSynth for decoding the source? I also know that there is no 64-bit ColorMatrix for the 64-bit version of AviSynth, so maybe you used some filter that messed up? Perhaps you can post the AviSynth script?
Also, try opening the script in Media Player Classic Homecinema once in the 32-bit version and then in the 64-bit version to see if both decode fine.
Could also be due to some odd resolution, but such errors usually don't look like this.
Cyber-Mav
20th December 2009, 18:17
i use minimal noise filter.
pc is currently doing the 2nd pass of the encode using the 32bit encoder, avs4x264.exe is flagged as a 32bit app during the encoding in task manager.
i will retest again in few mins with no noise filter and then see the results.
as requested here is the avs script:
#Import required DLLs
LoadPlugin("C:\Program Files (x86)\megui\tools\avisynth_plugin\ColorMatrix.dll")
LoadPlugin("C:\Program Files (x86)\megui\tools\avisynth_plugin\Convolution3DYV12.dll")
LoadPlugin("C:\Program Files (x86)\megui\tools\avisynth_plugin\Decomb.dll")
LoadPlugin("C:\Program Files (x86)\megui\tools\avisynth_plugin\DGAVCDecode.dll")
LoadPlugin("C:\Program Files (x86)\megui\tools\avisynth_plugin\DGDecode.dll")
LoadPlugin("C:\Program Files (x86)\megui\tools\avisynth_plugin\EEDI2.dll")
LoadPlugin("C:\Program Files (x86)\megui\tools\avisynth_plugin\FluxSmooth.dll")
LoadPlugin("C:\Program Files (x86)\megui\tools\avisynth_plugin\LeakKernelDeint.dll")
LoadPlugin("C:\Program Files (x86)\megui\tools\avisynth_plugin\NicAudio.dll")
LoadPlugin("C:\Program Files (x86)\megui\tools\avisynth_plugin\TDeint.dll")
LoadPlugin("C:\Program Files (x86)\megui\tools\avisynth_plugin\TIVTC.dll")
LoadPlugin("C:\Program Files (x86)\megui\tools\avisynth_plugin\TomsMoComp.dll")
LoadPlugin("C:\Program Files (x86)\megui\tools\avisynth_plugin\UnDot.dll")
LoadPlugin("C:\Program Files (x86)\megui\tools\avisynth_plugin\VSFilter.dll")
DGDecode_mpeg2source("C:\Video Processing\video\video.d2v", info=3)
ColorMatrix(hints=true, threads=0)
#deinterlace
crop( 0, 72, 0, -70)
LanczosResize(720,304) # Lanczos (Sharp)
Undot() # Minimal Noise
lnatan25
20th December 2009, 18:20
Do you see the ColorMatrix function call? Perhaps that is the problem. As far as I know, there is no ColorMatrix with the 64-bit version of AviSynth (could be wrong though).
Zathor
20th December 2009, 18:22
Cyber-Mav, did you have proper 64bit codecs and AviSynth for decoding the source? I also know that there is no 64-bit ColorMatrix for the 64-bit version of AviSynth, so maybe you used some filter that messed up? Perhaps you can post the AviSynth script?
Avisynth 64-bit is not necessary. The avs4x264 is a wrapper between the 64bit x264 and the 32bit avisynth.
i use minimal noise filter.
pc is currently doing the 2nd pass of the encode using the 32bit encoder, avs4x264.exe is flagged as a 32bit app during the encoding in task manager.
i will retest again in few mins with no noise filter and then see the results.
New Build in the first posting. I have finally removed the unnecessary LoadPlugin calls if the filter is not needed.
Can you please try to encode it with the same config with both x264 versions? You can do the trick the following way:
Enqueue your x264 64bit job, run it and then delete the tools\x264\avs4x264.exe and enque the new job and run it again. This time the x264.exe (32bit) will be used. Compare both files.
EDIT: I assume at the moment that your 32bit encoding is rather old and has been encoded without weighted P prediction. Weighted P prediction has some issues in older codecs.
Cyber-Mav
20th December 2009, 18:22
ok the encode just finished with the 32bit version of x264 renamed to x264_64.exe and.... the video is still garbled up. so somethings not right here. i will do few more tests now. first with the noise filter removed, and then with the colourmatrix turned off.
ok scratch the above, let me download the new build and give it a go.
lnatan25
20th December 2009, 18:23
Thanks for clearing this up, Zathor. :)
Zathor
20th December 2009, 18:27
ok the encode just finished with the 32bit version of x264 renamed to x264_64.exe and.... the video is still garbled up. so somethings not right here. i will do few more tests now. first with the noise filter removed, and then with the colourmatrix turned off.
ok scratch the above, let me download the new build and give it a go.
My edit in the post above has been too late..
So here again:
I assume at the moment that your 32bit encoding is rather old and has been encoded without weighted P prediction. Weighted P prediction has some issues in older codecs and will be not properly displayed. You have to disable weighted P in the encoder (not recommended) or have to use a new codec (recommended).
Cyber-Mav
20th December 2009, 18:35
nah my encoding on 32bit is proper hardcore man, here, i dropped the working 32bit video i encoded before i downloaded the 64bit enabled build of megui onto avinaptic. i use everything man, 3 b-frames, weighted p and b etc:
http://img687.imageshack.us/img687/617/x264settingsused.jpg
currently the video is encoding again using new build you linked me to.
the avs script looks lot shorter now:
LoadPlugin("C:\Program Files (x86)\megui\tools\dgindex\DGDecode.dll")
DGDecode_mpeg2source("C:\Video Processing\video\video.d2v", info=3)
LoadPlugin("C:\Program Files (x86)\megui\tools\avisynth_plugin\ColorMatrix.dll")
ColorMatrix(hints=true, threads=0)
#deinterlace
crop( 0, 72, 0, -70)
LanczosResize(720,304) # Lanczos (Sharp)
LoadPlugin("C:\Program Files (x86)\megui\tools\avisynth_plugin\UnDot.dll")
Undot() # Minimal Noise
///argh i just noticed i forgot to remove the noise filter this time damn it, its on the 2nd pass now anyways so i will try again without noise filter next, unless this new build you put up has sorted it out.
lnatan25
20th December 2009, 18:36
Two questions,
I extracted the developmental build, but it still says 1059. Is that normal?
Where is the setting to select the 64-bit encoder?
Thanks!
Zathor
20th December 2009, 18:44
Two questions,
I extracted the developmental build, but it still says 1059. Is that normal?
Yes, as soon as I publish it to the update server it will be changed so that everyone get the correct and new version.
Where is the setting to select the 64-bit encoder?
Nowhere. It will be selected automatically if a 64bit OS is detected (and avs4x264.exe is found)
lnatan25
20th December 2009, 18:49
OK, thanks, now a follow up with two more. :P
First, I have .Net Framework 4.0 (in addition to the others), and in the logger, it says ".x (..)" (this is what was causing an exception in the last build before your builds). Is this normal? I assume you do not use the framework version to determine wither the OS is 64-bit or 32-bit.
Second, how efficient is avs4x264 versus a native 64-bit AviSynth w/ codecs? Perhaps an option to select the encoding "path" (32-bit, avs4x264, native 64-bit) would be best, even if only for experimental and benchmarking purposes.
nurbs
20th December 2009, 18:52
The problem with using native 64bit avisynth is that most of the avisynth filters aren't available in 64bit and therefore won't work.
lnatan25
20th December 2009, 18:54
Yes, I understand that, this is why offering a selectable option is best, in my opinion. Filters are not always needed, thus whenever possible, it would be best to use the native. :)
Cyber-Mav
20th December 2009, 18:55
Can you please try to encode it with the same config with both x264 versions? You can do the trick the following way:
Enqueue your x264 64bit job, run it and then delete the tools\x264\avs4x264.exe and enque the new job and run it again. This time the x264.exe (32bit) will be used. Compare both files.
ok im running it now, the video i encoded that used x264_64 and avs4x264 turned out corrupted as in the previous screenshot.
i deleted the avs4x264.exe file and started the job that was queued up. task manager now shows that only x264.exe*32 is now doing the encoding. as soon as it is finished i will post on here letting you know how its gone.
the encode is finished and it plays back perfectly fine. so the issue is most likely avs4x264.exe
im going to run another encode now i restarted megui and the updates downloaded new avs4x264 which i deleted previously. i will now remove the noise filter and see how it encodes in 64bit.
Carpo
20th December 2009, 19:20
i can confirm Cyber-Mavs issue as i am getting it here too using x264_x64, looks like the image is all squashed and going diagonally across the screen, will also try with x264 32bit and see if same happens
Edit: with 32bit x264 picture is fine
Zathor
20th December 2009, 19:24
Strange. I did also several encodings with the 64bit version and my files are ok.
Zathor
20th December 2009, 19:30
OK, thanks, now a follow up with two more. :P
First, I have .Net Framework 4.0 (in addition to the others), and in the logger, it says ".x (..)" (this is what was causing an exception in the last build before your builds). Is this normal? I assume you do not use the framework version to determine wither the OS is 64-bit or 32-bit.
Yes, I have fixed the .NET detection so that there will be no error anymore when an unknown version is found.
Second, how efficient is avs4x264 versus a native 64-bit AviSynth w/ codecs? Perhaps an option to select the encoding "path" (32-bit, avs4x264, native 64-bit) would be best, even if only for experimental and benchmarking purposes.
Native 64bit should be faster, but I cannot test it because nearly all of my plugins are 32bit only. Therefore MeGUI will not support it at the moment. If you want to test it you can write a small batch file.
Carpo
20th December 2009, 19:45
Strange. I did also several encodings with the 64bit version and my files are ok.
is avs4x264 a wrapper to make x264_x64 work? I only seem to have this with interlaced material, will try and find some progressive and test with that
Cyber-Mav
20th December 2009, 19:48
ok i tried again now using 64bit and this avs script:
LoadPlugin("C:\Program Files (x86)\megui\tools\dgindex\DGDecode.dll")
DGDecode_mpeg2source("C:\Video Processing\video\video.d2v", info=3)
LoadPlugin("C:\Program Files (x86)\megui\tools\avisynth_plugin\ColorMatrix.dll")
ColorMatrix(hints=true, threads=0)
#deinterlace
crop( 0, 72, 0, -70)
LanczosResize(720,304) # Lanczos (Sharp)
#denoise
i removed the denoise filter and still the image is garbled up. its deffo something to do with avs4x264 since i tried using avs4x264.exe along with the 32bit version of x264 and it still results in a grabled up image.
Cyber-Mav
20th December 2009, 19:50
ok im trying another encode now using this script:
LoadPlugin("C:\Program Files (x86)\megui\tools\dgindex\DGDecode.dll")
DGDecode_mpeg2source("C:\Video Processing\video\video.d2v")
#deinterlace
crop( 0, 72, 0, -70)
LanczosResize(720,304) # Lanczos (Sharp)
#denoise
iv removed the colourmatrix as well now so will see how this effects the output.
and its failed again, image is all garbled up. 64bit is just not ready for prime time i guess.
horvathd
20th December 2009, 19:55
I found the following annoyance/bug in the 0.3.1.1059 version:
When I select the animation tuning then in the command line appears the --ref and --bframes commands with the correct number according to the preset and tuning. As far as I know it's not necessary the x264 will calculate these numbers.
Also when a tuning is selected and I change to preset then a --ref command appears with the number related to the preset without the tuning.
Zathor
20th December 2009, 19:55
Please try the vfw4x264.exe (rename it to avs4x264.exe).
Cyber-Mav
20th December 2009, 20:08
Please try the vfw4x264.exe (rename it to avs4x264.exe).
ok i will try this method now.
ok an update this method works, when vfw4x264.exe is renamed to avs4x264.exe the 64bit x264 encode plays back with no issues.
biggest problem with this is that im unsure if any of the filters will work, also the speed, renaming as the above dropped encoding speed down to 8.5fps.
regular 32bit encoding using the noise filter and colormatrix did around 10fps, and the 64bit version using the original avs4x264.exe did around 12fps (although the video playback was corrupted).
so all in all 64bit version is useless to me. how do i revert megui back to pure 32bit mode?
Cyber-Mav
20th December 2009, 20:42
actually never mind i worked it out i downloaded the stable build posted on the first page and thats sorted it now, its using 32bit mode again with no issues.
Carpo
20th December 2009, 20:54
i just renamed all the files and left 32bit x264.exe alone, nice and 32bit only now :)
Zathor
20th December 2009, 21:07
Thanks for the tests. I will do some tests on my own now and will then decide which 64bit mode will be implemented.
EDIT: AVCSource works with avs4x264, DGDecode_mpeg2source not. Anyone knows why?
EDIT2: New ev build in the first post. It will use vfw4x264.exe until the problem with avs4x264 has been resolved. In my tests it has the same speed as avs4x264 and the encoding is ok.
Cyber-Mav
20th December 2009, 23:03
i will keep my dvd vob file sample on my hard drive. when you have new version of avs4x264 i wll try again for you and see if 64bit encoding is fixed.
i didnt try encoding any hd source material but since you can replicate the problem with mpeg2 then i guess we know its an issue with mpeg2 decoding/frame serving.
since your method uses a wrapper to frameserve to x264 64bit does that mean that the filters can be used since they will be processed before the wrapper frameserves to the encoder?
Zathor
20th December 2009, 23:13
i will keep my dvd vob file sample on my hard drive. when you have new version of avs4x264 i wll try again for you and see if 64bit encoding is fixed.
Can you please try the new build and compare the speed to the 32bit one? For me vfw4x264 is faster than the 32bit one but I would like to have results from other systems.
since your method uses a wrapper to frameserve to x264 64bit does that mean that the filters can be used since they will be processed before the wrapper frameserves to the encoder?
Yes, you can use all filters.
Cyber-Mav
20th December 2009, 23:20
yes i can test this for you, also i just remebered that you have fixed megui so that it doesnt need to use any files outside of its own directory so i can make a new folder called megui64 and use it to do all your testing without effecting my current stable 32bit megui.
im installing now and will provide you with the test results.
Cyber-Mav
21st December 2009, 00:01
ok 64bit version you just updated has been tested the encoded video plays back fine this time with no issues.
64bit speed was between 8.6-9.0 fps during both passes.
yes i is browsing internet in small window and have megui encoding window on the side which im constantly monitoring. wish there was an automated way to do the speed checking. im going to run the 32bit version now and measure speed.
ok the 32bit encoder is finished now, and the 64bit one is faster.
32bit one encoded at 7.6-8fps during both passes. so a small advantage for the 64bit one.
although when the 64bit version was using avs4x264 it was running even faster than vfv4x264, although the final output was all corrupted.
simonb1975uk
21st December 2009, 00:08
Zathor I am getting the same thing happening. Where can I obtain this new build?
Thanks,
Simon
Zathor
21st December 2009, 00:16
Zathor I am getting the same thing happening. Where can I obtain this new build?
In the first posting is a link to the development build.
nakTT
21st December 2009, 01:56
Can you please try the new build and compare the speed to the 32bit one? For me vfw4x264 is faster than the 32bit one but I would like to have results from other systems.
Hi Zathor,
Is there any way for me to turn off the 64bit and only use 32bit? The reason is I want to compare the speed between both of them. As for 64bit, it works like a charm.
Carpo
21st December 2009, 01:58
rename the x64 x264 exe ;)
nakTT
21st December 2009, 02:02
Yes, I understand that, this is why offering a selectable option is best, in my opinion. Filters are not always needed, thus whenever possible, it would be best to use the native. :)
100% agree with you. At least we could have some kind of checkbox to enable it.
Strange. I did also several encodings with the 64bit version and my files are ok.
Me too. No issue whatsoever.
Thanks for the tests. I will do some tests on my own now and will then decide which 64bit mode will be implemented.
EDIT: AVCSource works with avs4x264, DGDecode_mpeg2source not. Anyone knows why?
EDIT2: New ev build in the first post. It will use vfw4x264.exe until the problem with avs4x264 has been resolved. In my tests it has the same speed as avs4x264 and the encoding is ok.
I have no problem at all with avs4x264. Works like a charm.
:thanks:
Mtz
21st December 2009, 03:32
In settings, the button for neroaacenc.exe is not working. For besplit is OK.
enjoy,
Mtz
magic144
21st December 2009, 03:35
great job Zathor - thanks for keeping this project alive :-)
[ReX]
21st December 2009, 04:58
About the AVI Muxer.
If you use input files with some characters such as "ã" or "ó" in the file name you get "No video source chosen!", that's because MeGUI is saving the AVI-Mux GUI job files as UTF-8, but if I save the same job file as UTF-8 signature (that's how AVI-Mux GUI saves it) or ANSI it works.
Edit:
I'm not a programmer, but looks like that changing from
using (StreamWriter output = new StreamWriter(File.OpenWrite(filename)))
to:
using (StreamWriter output = new StreamWriter(File.OpenWrite(filename), System.Text.Encoding.UTF8))
in megui/trunk/packages/muxer/avimuxgui/AMGMuxer.cs did the job (saves as UTF-8 signature).
Zathor
21st December 2009, 06:15
rename the x64 x264 exe ;)
The best way is to delete/rename the vfw4x264.exe. If you do it this way the wrapper will no be used at all and will not interfere with the test results. Btw the update check will notice that the file is missing.
In settings, the button for neroaacenc.exe is not working. For besplit is OK.
;1355335']About the AVI Muxer.
If you use input files with some characters such as "ã" or "ó" in the file name you get "No video source chosen!", that's because MeGUI is saving the AVI-Mux GUI job files as UTF-8, but if I save the same job file as UTF-8 signature (that's how AVI-Mux GUI saves it) or ANSI it works.
Thanks, will change/fix both things later.
nakTT
21st December 2009, 06:27
Strange. I did also several encodings with the 64bit version and my files are ok.
The problem arise when my input file is avi but no problem when the input is mkv (encoded using x264). Any idea why?
How can I easily turn off the x264 64bit option when I'm encoding using avi input?
:thanks:
Zathor
21st December 2009, 06:37
In settings, the button for neroaacenc.exe is not working. For besplit is OK.
;1355335']About the AVI Muxer.
If you use input files with some characters such as "ã" or "ó" in the file name you get "No video source chosen!", that's because MeGUI is saving the AVI-Mux GUI job files as UTF-8, but if I save the same job file as UTF-8 signature (that's how AVI-Mux GUI saves it) or ANSI it works.
New dev build in the first posting, but I had no time yet to test both changes.
Zathor
21st December 2009, 06:40
The problem arise when my input file is avi but no problem when the input is mkv (encoded using x264). Any idea why?
How can I easily turn off the x264 64bit option when I'm encoding using avi input?
Do you have the dev build which uses vfw4x264.exe or the old one which uses avs4x264.exe (if unsure, please redownload the dev build in the first posting and test again)? I'm asking because there seems to be no problems with vfw4x264.exe but I did not test it with AVI input yet.
nakTT
21st December 2009, 06:54
Do you have the dev build which uses vfw4x264.exe or the old one which uses avs4x264.exe (if unsure, please redownload the dev build in the first posting and test again)? I'm asking because there seems to be no problems with vfw4x264.exe but I did not test it with AVI input yet.
I think its avs4x264.exe because it is the first time you implement the 64bit x264 before complains arise.
Any rough idea on speed comparison between:
avs4x264.exe with 64bit x264
vs
vfw4x264.exe with 64bit x264
:thanks:
Zathor
21st December 2009, 11:09
Any rough idea on speed comparison between:
avs4x264.exe with 64bit x264
vs
vfw4x264.exe with 64bit x264
In my benchmarks there has been no real difference between both wrappers.
murtuza
21st December 2009, 13:22
Problem: It keeps erroring out when I try to encode. It doesn't give any error message at all. In the worker it starts the encode but not even a second later, encode stops and worker status changes to say "error". Any way to find out the error or any solution on why this problem would occur?
How to duplicate this problem: Well there's no sure way to duplicate it unless if you're running default settings on everything. I just used the basic blu ray profile that came with this developmental build provided at the beginning of this thread. I changed nothing, tried encoding in mp4 x264.
Now I'm not encode savvy but I'm willing to learn. Could it be that blu-ray type settings cannot be encoded in an mp4 container? Any other info you guys need, just ask ill post as quickly as possible. I tried several things including changing the profile, trying a different container, tried changing resolution from 1080p down to 720p, etc etc. Can't figure it out for the life of me. Ideas?
System Specs:
Windows 7 64 bit
Quad Core 2 Q6600
4 gig 1066 ram
P.S. I lurk doom9 alot for encode information, first time i had any real errors with MeGUI that wasn't already solved. I appreciate your efforts Zathor!
guys i am having the same problem he mentioned , i am trying to rip a DVD not a bluray , i tried Xvid , x264 both , but it is not working , it starts for a second and stops showing error
Well i am on windows XP SP3
[Information] Log
-[Information] Versions
--[NoImage] MeGUI Version : 0.3.1.1051
--[NoImage] OS : Windows XP Professional x86 SP3 (5.1.196608.2600)
--[NoImage] Framework used : 2.0 SP1 (2.0.50727.3053)
-[Information] Hardware
--[NoImage] CPU : Intel(R) Pentium(R) Dual CPU E2180 @ 2.00GHz
-[Information] Log for job1 (video, 2.avs -> )
--[Information] [12/21/2009 7:13:46 PM] Started handling job
--[Information] [12/21/2009 7:13:46 PM] Preprocessing
--[NoImage] Job commandline: "C:\Program Files\megui\tools\xvid_encraw\xvid_encraw.exe" -i "E:\Radio (Live in air) Untouched NTSC DVD9 UDR Exclusive\rip\2.avs" -pass1 "E:\Radio (Live in air) Untouched NTSC DVD9 UDR Exclusive\rip\2.stats" -bitrate 600 -kboost 100 -chigh 30 -clow 15 -overhead 0 -turbo -max_key_interval 250 -nopacked -vhqmode 4 -qpel -closed_gop -lumimasking -imin 1 -pmin 1 -bvhq -bquant_ratio 162 -bquant_offset 0 -bmin 1 -par 1:1 -threads 1
--[Information] [12/21/2009 7:13:46 PM] Encoding started
--[NoImage] Standard output stream
--[NoImage] Standard error stream
--[Information] [12/21/2009 7:13:47 PM] Job completed
here is the log
plz somebody help , struggling from 2 days on this :(
plz help
thanks
waiting
simonb1975uk
21st December 2009, 13:26
Zathor,
I can confirm that the new dev build works great for me. Excellent work! :thanks:
Simon
JoeH
21st December 2009, 15:29
Zathor,
I just tried the latest development build with vfw4x264.
It works great, and for me runs even slightly faster (between .5% and 2%) than the avs4x264!
amgeex
21st December 2009, 18:22
Do we use the same update server (http://megui.org/auto/) with the development version?
Thanks for the great work Zathor!
quantum5uicid3
21st December 2009, 22:14
murtuza, it sounds like a problem with your source. check if you can play the avs in mpc or similar. if so, post the script.
Zathor
21st December 2009, 22:28
--[NoImage] MeGUI Version : 0.3.1.1051
Please update to build 1059. I can only support the latest version. You should switch to the development server mentioned in the first posting. Please report back if the problem has been solved.
Do we use the same update server (http://megui.org/auto/) with the development version?
Yes
nakTT
21st December 2009, 22:46
Yes
How about this server:
http://www.constructd.com/megui/
I have used it ever-since and its seems to works.
Zathor
21st December 2009, 22:51
How about this server:
http://www.constructd.com/megui/
I have used it ever-since and its seems to works.
It has the same files as the official development server. You can use that one, too.
nakTT
21st December 2009, 22:58
In my benchmarks there has been no real difference between both wrappers.
It has the same files as the official development server. You can use that one, too.
I see. Thanks for the reply.
:thanks:
horvathd
21st December 2009, 23:51
Is anybody else noticed this problem with MeGUI?
I found the following annoyance/bug in the 0.3.1.1059 version:
When I select the animation tuning then in the command line appears the --ref and --bframes commands with the correct number according to the preset and tuning. As far as I know it's not necessary the x264 will calculate these numbers.
Also when a tuning is selected and I change the preset then a --ref command appears with the number related to the preset without the tuning.
murtuza
22nd December 2009, 04:10
murtuza, it sounds like a problem with your source. check if you can play the avs in mpc or similar. if so, post the script.
Well i tried everything , i tried using nothing in the script , no filters , still doesnt work
DGDecode_mpeg2source("E:\Radio (Live in air) \rip\2.d2v", info=3)
ColorMatrix(hints=true, threads=0)
#deinterlace
crop( 0, 44, 0, -42)
LanczosResize(720,480) # Lanczos (Sharp)
#denoise
here is the script
I dont think the problem is with script :(
plz help
Please update to build 1059. I can only support the latest version. You should switch to the development server mentioned in the first posting. Please report back if the problem has been solved.
It still doesnt work with the new version :(
Wat shall i do now :(
plz help
Inspector.Gadget
22nd December 2009, 05:27
We are not allowed to help people with downloaded content per the forum rules. See if you can replicate the issue with a DVD you OWN and you RIP.
Alf Bundy
22nd December 2009, 07:33
Hi Zathor,
In the last non patched 1057 build, Winamp AAC didn't work anymore.
So I used NeroAAC and forgot about it.
Now with the latest dev build, I tried again.
First, Megui detects the missing enc_aacplus.exe and download it.
But after an encode ending with an error, the logfile says "can't find enc_aacplus.dll".
So I took it from a backup folder.
Unfortunately, it still doesn't work.
Here are logfiles from failing attempts to encode a WAV file (44.1Khz stereo) to Winamp AAC (with and without decoding via DirectShow),
-[Error] Log for job1 (audio, The Allman Brothers Band - Jessica.wav -> The Allman Brothers Band - Jessica.m4a)
--[Information] [22/12/2009 7:10:14] Started handling job
--[Information] [22/12/2009 7:10:14] Preprocessing
--[NoImage] Avisynth script
---[NoImage] LoadPlugin("C:\Program Files\megui\tools\avisynth_plugin\NicAudio.dll")
---[NoImage] RaWavSource("D:\DVD burn\The Allman Brothers Band - Jessica.wav")
---[NoImage] Normalize()
---[NoImage] 32==Audiobits(last)?ConvertAudioTo16bit(last):last
---[NoImage] return last
--[NoImage] Commandline used: - "{0}" --rawpcm {1} {3} {2} --br 128000 --mpeg4aac --lc
--[Information] [22/12/2009 7:10:14] Encoding started
--[Information] [22/12/2009 7:10:14] Encode thread started
--[Information] [22/12/2009 7:10:14] Avisynth script environment opened
--[Information] [22/12/2009 7:10:15] Script loaded
--[Information] Output Decoder
---[NoImage] Channels: 2
---[NoImage] Bits per sample: 16
---[NoImage] Sample rate: 44100
--[NoImage] Commandline: C:\Program Files\megui\tools\enc_aacplus\enc_aacPlus.exe - "D:\DVD burn\The Allman Brothers Band - Jessica.m4a" --rawpcm 44100 2 16 --br 128000 --mpeg4aac --lc
--[Information] [22/12/2009 7:10:15] Encoder process started
--[Error] An error occurred
---[NoImage] Exception message: Le canal de communication a été fermé. (-> The communication channel has been closed.)
---[NoImage] Stacktrace
----[NoImage] à System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
----[NoImage] à System.IO.FileStream.WriteCore(Byte[] buffer, Int32 offset, Int32 count)
----[NoImage] à System.IO.FileStream.Write(Byte[] array, Int32 offset, Int32 count)
----[NoImage] à MeGUI.AviSynthAudioEncoder.encode()
---[NoImage] Inner exception: null
--[Information] [22/12/2009 7:10:15] Job completed
-[Error] Log for job1 (audio, The Allman Brothers Band - Jessica.wav -> The Allman Brothers Band - Jessica.m4a)
--[Information] [22/12/2009 6:49:55] Started handling job
--[Information] [22/12/2009 6:49:55] Preprocessing
--[NoImage] Avisynth script
---[NoImage] DirectShowSource("D:\DVD burn\The Allman Brothers Band - Jessica.wav")
---[NoImage] EnsureVBRMP3Sync()
---[NoImage] Normalize()
---[NoImage] 32==Audiobits(last)?ConvertAudioTo16bit(last):last
---[NoImage] return last
--[NoImage] Commandline used: - "{0}" --rawpcm {1} {3} {2} --br 128000 --mpeg4aac --lc
--[Information] [22/12/2009 6:49:55] Encoding started
--[Information] [22/12/2009 6:49:55] Encode thread started
--[Information] [22/12/2009 6:49:55] Avisynth script environment opened
--[Information] [22/12/2009 6:50:01] Script loaded
--[Information] Output Decoder
---[NoImage] Channels: 2
---[NoImage] Bits per sample: 16
---[NoImage] Sample rate: 44100
--[NoImage] Commandline: C:\Program Files\megui\tools\enc_aacplus\enc_aacPlus.exe - "D:\DVD burn\The Allman Brothers Band - Jessica.m4a" --rawpcm 44100 2 16 --br 128000 --mpeg4aac --lc
--[Information] [22/12/2009 6:50:01] Encoder process started
--[Error] An error occurred
---[NoImage] Exception message: Abnormal encoder termination -1066598274
---[NoImage] Stacktrace: à MeGUI.AviSynthAudioEncoder.encode()
---[NoImage] Inner exception: null
--[Information] [22/12/2009 6:50:02] Job completed
And Finally, sometimes I get a different error message :
-[Error] Log for job1 (audio, The Allman Brothers Band - Jessica.wav -> The Allman Brothers Band - Jessica.m4a)
--[Information] [22/12/2009 7:20:30] Started handling job
--[Information] [22/12/2009 7:20:30] Preprocessing
--[NoImage] Avisynth script
---[NoImage] LoadPlugin("C:\Program Files\megui\tools\avisynth_plugin\NicAudio.dll")
---[NoImage] RaWavSource("D:\DVD burn\The Allman Brothers Band - Jessica.wav")
---[NoImage] Normalize()
---[NoImage] 32==Audiobits(last)?ConvertAudioTo16bit(last):last
---[NoImage] return last
--[NoImage] Commandline used: - "{0}" --rawpcm {1} {3} {2} --br 128000 --mpeg4aac --lc
--[Information] [22/12/2009 7:20:30] Encoding started
--[Information] [22/12/2009 7:20:30] Encode thread started
--[Information] [22/12/2009 7:20:30] Avisynth script environment opened
--[Error] An error occurred
---[NoImage] Exception message: m2RaWavSource: unsupported number of channels defined
---[NoImage] Stacktrace
----[NoImage] à MeGUI.AviSynthClip..ctor(String func, String arg, AviSynthColorspace forceColorspace, AviSynthScriptEnvironment env)
----[NoImage] à MeGUI.AviSynthAudioEncoder.encode()
---[NoImage] Inner exception: null
--[Information] [22/12/2009 7:20:30] Job completed
I can encode the same WAV file with NeroAAC, AftenAC3 and Vorbis (didn't try with other encoders).
Winamp AAC fails with every WAV, AC3 and MP3 I tried.
But I still can encode these files with Winamp AAC in Megui 1056 and older ...
Could anyone give a try to Winamp AAC and see if I'm the only one with this issue ?
Guest
22nd December 2009, 15:14
The link to the development build in first post is dead.
EDIT: OK now, I guess mediafire was down.
lnatan25
23rd December 2009, 02:20
Hi Zathor, some reporting. I've been testing the devel build for a few hours, and there seem to be a lot of bugs related to aborting x264 encoding. A lot of times, MeGUI and encoding status would just freeze (long after avs4x264.exe and x264_64.exe have exited). Other times, while encoding, MeGUI freezes up (x264 and co. keep working though) and suddenly after a long period it unfreezes and updates the status window; could be related to the next problem. Whenever I encode, no matter what priority both the EXE files are set (MeGUI launches them with "Below Normal" priority), they just make my system unstable. Net keeps disconnecting, applications freeze, etc. I know encoding is very CPU consuming, but I have encoded a lot of files with previous versions of MeGUI (and 32-bit x264.exe), and had never had these problems. Perhaps something in the communication between avs4x264.exe and x264_64.exe is causing it, I'm not sure, but it is very annoying. I think this is what caused MeGUI to freeze.
I still hope to see at least an option to allow us to switch back to the 32-bit encoder. Thanks in advance!
quantum5uicid3
23rd December 2009, 09:08
Hi Zathor,
In the last non patched 1057 build, Winamp AAC didn't work anymore.
So I used NeroAAC and forgot about it.
Now with the latest dev build, I tried again.
First, Megui detects the missing enc_aacplus.exe and download it.
But after an encode ending with an error, the logfile says "can't find enc_aacplus.dll".
So I took it from a backup folder.
Unfortunately, it still doesn't work.
Here are logfiles from failing attempts to encode a WAV file (44.1Khz stereo) to Winamp AAC (with and without decoding via DirectShow),
And Finally, sometimes I get a different error message :
I can encode the same WAV file with NeroAAC, AftenAC3 and Vorbis (didn't try with other encoders).
Winamp AAC fails with every WAV, AC3 and MP3 I tried.
But I still can encode these files with Winamp AAC in Megui 1056 and older ...
Could anyone give a try to Winamp AAC and see if I'm the only one with this issue ?
i can not reproduce the error. are you using the latest dlls from winamp?
quantum5uicid3
23rd December 2009, 09:12
Appears to be something wrong with the version of xvid_encraw (20090530) used in MeGUI 1059.
Threads used is always one less than the number of threads requested (where number of threads requested is greater than one):
xvid_encraw.exe -i in.avs -threads 4 -o out.avi
...
xvid [info]: Detected cpus = 2, threads requested = 3, threads in use = 3
i think it's intended, xvid's smp support is kind of hacked. just +1 the threads fields, if it helps you get better performance.
though, i did a very unscientific quick test and -threads 4 was slightly faster then -threads 5 on my quad core.
quantum5uicid3
23rd December 2009, 09:30
Is anybody else noticed this problem with MeGUI?
the problem i noticed with the tune animation is if you keep slecting it repeatedly, it increases the ref(2x) and bframes(+2) until fatal error when ref tries to go to 24
Elbart_
23rd December 2009, 09:53
Appears to be something wrong with the version of xvid_encraw (20090530) used in MeGUI 1059.
Threads used is always one less than the number of threads requested (where number of threads requested is greater than one):
xvid_encraw.exe -i in.avs -threads 4 -o out.avi
...
xvid [info]: Detected cpus = 2, threads requested = 3, threads in use = 3
Computers count from 0 onwards, so 4 threads for you are 3 (0,1,2,3) for computers.
Alf Bundy
23rd December 2009, 20:02
i can not reproduce the error. are you using the latest dlls from winamp?
Yes, dll is from the latest Winamp rev5.57 (build 2009-12-21).
This dll works with the old enc_aacplus.exe (2006-05-15) from Megui 1056, but exports only raw aac.
With the latest enc_aacplus.exe (2009-10-10) from Megui 1059, it gives the aforementioned error.
And if I put the old enc_aacplus in the latest Megui folder, there's no error and the file is exported in .m4a.
But I always end up with a 32Khz 48kbps file, no matter what setting I choose. :confused:
That's no big deal, I can use the old Megui when I want Winamp AAC (for ultra low bitrates).
Still, I wonder why the needed dll is not downloaded with enc_aacplus since it won't work without it ?
gahz
25th December 2009, 10:30
since switching to this patch build i have noticed my encodes have dropped in size by almost half. has anyone else noticed this?
i thought it was due to some incompatibility with my older profiles so i made a new profile starting with the slide bar then changing advanced settings so it matched up with my old profile settings.
even with the new profile i am still getting half the file size as i do from the older version of megui. anyone able to help me out with an answer as to why this is happening?
nurbs
25th December 2009, 11:51
What was the x264 revision before the update and what settings do you use?
MOS-Marauder
25th December 2009, 12:57
Whoo hi all... I have also a Problem with the Patched MeGui 0.3.1.1059.
In special its converting an Ac3 to Ac3 in Megui...
The Log seems ok.
But the crated file only has a "Small distorted scratch" in it and then .. only emptyness...
I enclosed the Log file. Maybe someone can help ....
Chris
----
[Information] Log for job1 (audio, boheme PID b6b 2_0ch 48KHz 448Kbps DELAY 60ms.ac3 -> boheme PID b6b 2_0ch 48KHz 448Kbps DELAY 0ms.ac3)
-[Information] [25.12.2009 12:50:33] Started handling job
-[Information] [25.12.2009 12:50:33] Preprocessing
-[NoImage] Avisynth script
--[NoImage] NicAc3Source("F:\000-CAPTURE-BACKUP\____BluRay-BRENN\life\boheme PID b6b 2_0ch 48KHz 448Kbps DELAY 60ms.ac3", DRC=1)
--[NoImage] DelayAudio(60.0/1000.0)
--[NoImage] Normalize()
--[NoImage] return last
-[NoImage] Commandline used: -readtoeof 1 -b 384 - "{0}"
-[Information] [25.12.2009 12:50:33] Encoding started
-[Information] [25.12.2009 12:50:33] Encode thread started
-[Information] [25.12.2009 12:50:33] Avisynth script environment opened
-[Information] [25.12.2009 12:50:33] Script loaded
-[Information] Output Decoder
--[NoImage] Channels: 2
--[NoImage] Bits per sample: 32
--[NoImage] Sample rate: 48000
-[NoImage] Commandline: C:\Program Files (x86)\megui\tools\aften\aften.exe -readtoeof 1 -b 384 - "F:\000-CAPTURE-BACKUP\____BluRay-BRENN\life\boheme PID b6b 2_0ch 48KHz 448Kbps DELAY 0ms.ac3"
-[Information] [25.12.2009 12:50:33] Encoder process started
-[NoImage] Output from encoder via stderr
--[NoImage] Aften: A/52 audio encoder
--[NoImage] Version SVN
--[NoImage] (c) 2006-2007 Justin Ruggles, Prakash Punnoor, et al.
--[NoImage] input format: Microsoft WAVE Floating-point 32-bit little-endian 48000 Hz stereo
--[NoImage] output format: 48000 Hz stereo (2/0)
--[NoImage] SIMD usage: MMX SSE SSE2 SSE3
--[NoImage] Threads: 4
--[NoImage] progress: 100% | q: 616.0 | bw: 60.0 | bitrate: 384.0 kbps
-[Information] [25.12.2009 12:51:19] Postprocessing
-[Information] [25.12.2009 12:51:19] Job completed
-----
Triccotracco
25th December 2009, 19:13
since switching to this patch build i have noticed my encodes have dropped in size by almost half. has anyone else noticed this?
i thought it was due to some incompatibility with my older profiles so i made a new profile starting with the slide bar then changing advanced settings so it matched up with my old profile settings.
even with the new profile i am still getting half the file size as i do from the older version of megui. anyone able to help me out with an answer as to why this is happening?
with x264?
BTW I think this happend due new x264 features, also my experiences with crf mode i note a dropper size of encodes (i'm not sure an half size). But I remark that this dropper size depend from x264 not from megui.
Merry Xmas:)
gahz
25th December 2009, 19:29
this is my old settings:
program --profile high --crf 18.0 --thread-input --bframes 4 --b-adapt 2 --ref 5 --merange 32 --me umh --subme 8 --partitions all --trellis 2 --no-dct-decimate --no-fast-pskip --output "output" "input"
and my new settings are:
program --profile high --preset slower --tune film --crf 18.0 --thread-input --bframes 4 --ref 5 --merange 32 --no-dct-decimate --no-fast-pskip --output "output" "input"
yes with x264
-- i encoded a video with the patched megui and i'm seeing bitrates that are at half the value of the older version megui. don't get me wrong, the vids are just as good as the bigger, higher bitrate versions. i just don't know what's going on and if it's something i configured wrongly that is causing this.
quantum5uicid3
26th December 2009, 03:34
this is my old settings:
program --profile high --crf 18.0 --thread-input --bframes 4 --b-adapt 2 --ref 5 --merange 32 --me umh --subme 8 --partitions all --trellis 2 --no-dct-decimate --no-fast-pskip --output "output" "input"
and my new settings are:
program --profile high --preset slower --tune film --crf 18.0 --thread-input --bframes 4 --ref 5 --merange 32 --no-dct-decimate --no-fast-pskip --output "output" "input"
yes with x264
-- i encoded a video with the patched megui and i'm seeing bitrates that are at half the value of the older version megui. don't get me wrong, the vids are just as good as the bigger, higher bitrate versions. i just don't know what's going on and if it's something i configured wrongly that is causing this.
the introduction of mbtree and now even more so with its compatibility with bpyramid have increased compression quite a bit, so no you're not doing anything wrong. you will however probably need to play with the settings a bit to find a new personal balance of speed/quality.
on a different note. i installed vista64 to try out the new 64bit piping feature.
EDIT nvm, yay, works great. good job zathor. now if only ffmpegsource2 would be incorporated ;)
quantum5uicid3
26th December 2009, 07:30
Whoo hi all... I have also a Problem with the Patched MeGui 0.3.1.1059.
In special its converting an Ac3 to Ac3 in Megui...
The Log seems ok.
But the crated file only has a "Small distorted scratch" in it and then .. only emptyness...
I enclosed the Log file. Maybe someone can help ....
Chris
----
[Information] Log for job1 (audio, boheme PID b6b 2_0ch 48KHz 448Kbps DELAY 60ms.ac3 -> boheme PID b6b 2_0ch 48KHz 448Kbps DELAY 0ms.ac3)
-[Information] [25.12.2009 12:50:33] Started handling job
-[Information] [25.12.2009 12:50:33] Preprocessing
-[NoImage] Avisynth script
--[NoImage] NicAc3Source("F:\000-CAPTURE-BACKUP\____BluRay-BRENN\life\boheme PID b6b 2_0ch 48KHz 448Kbps DELAY 60ms.ac3", DRC=1)
--[NoImage] DelayAudio(60.0/1000.0)
--[NoImage] Normalize()
--[NoImage] return last
-[NoImage] Commandline used: -readtoeof 1 -b 384 - "{0}"
-[Information] [25.12.2009 12:50:33] Encoding started
-[Information] [25.12.2009 12:50:33] Encode thread started
-[Information] [25.12.2009 12:50:33] Avisynth script environment opened
-[Information] [25.12.2009 12:50:33] Script loaded
-[Information] Output Decoder
--[NoImage] Channels: 2
--[NoImage] Bits per sample: 32
--[NoImage] Sample rate: 48000
-[NoImage] Commandline: C:\Program Files (x86)\megui\tools\aften\aften.exe -readtoeof 1 -b 384 - "F:\000-CAPTURE-BACKUP\____BluRay-BRENN\life\boheme PID b6b 2_0ch 48KHz 448Kbps DELAY 0ms.ac3"
-[Information] [25.12.2009 12:50:33] Encoder process started
-[NoImage] Output from encoder via stderr
--[NoImage] Aften: A/52 audio encoder
--[NoImage] Version SVN
--[NoImage] (c) 2006-2007 Justin Ruggles, Prakash Punnoor, et al.
--[NoImage] input format: Microsoft WAVE Floating-point 32-bit little-endian 48000 Hz stereo
--[NoImage] output format: 48000 Hz stereo (2/0)
--[NoImage] SIMD usage: MMX SSE SSE2 SSE3
--[NoImage] Threads: 4
--[NoImage] progress: 100% | q: 616.0 | bw: 60.0 | bitrate: 384.0 kbps
-[Information] [25.12.2009 12:51:19] Postprocessing
-[Information] [25.12.2009 12:51:19] Job completed
-----
it looks like you're using a SVn build of aften, this is likely the culprit.
MOS-Marauder
26th December 2009, 10:38
Hm its the Version of Alften that is in MeGui "Original" and now in the Patched MeGUI. (I downloaded MeGui patched and let it install all tools)
WHat Version would be better ?
Chris
pdexdee
26th December 2009, 11:30
whewre to download version: 3.1.1057 ?
gahz
26th December 2009, 11:54
on a different note. i installed vista64 to try out the new 64bit piping feature.
does the mbtree stuff really make that much of a diff? is this also why on the same vid source i get lower average bitrate with the newer x264?
what 65bit piping feature? it's built into megui?
quantum5uicid3
26th December 2009, 14:04
WHat Version would be better ?
yeah the one that comes with it is good. do all ac3 encodes turn out like that or just that one in particular?
does the mbtree stuff really make that much of a diff?
yes, the extent varies. like i siad, you are going to need to change your crf and settings to find a new balance.
is this also why on the same vid source i get lower average bitrate with the newer x264?
yes
what 65bit piping feature? it's built into megui?
64bit windows will automatically use 64bit x264, yes
Zathor
26th December 2009, 14:18
Hi Zathor, some reporting. I've been testing the devel build for a few hours, and there seem to be a lot of bugs related to aborting x264 encoding. A lot of times, MeGUI and encoding status would just freeze (long after avs4x264.exe and x264_64.exe have exited). Other times, while encoding, MeGUI freezes up (x264 and co. keep working though) and suddenly after a long period it unfreezes and updates the status window; could be related to the next problem. Whenever I encode, no matter what priority both the EXE files are set (MeGUI launches them with "Below Normal" priority), they just make my system unstable. Net keeps disconnecting, applications freeze, etc. I know encoding is very CPU consuming, but I have encoded a lot of files with previous versions of MeGUI (and 32-bit x264.exe), and had never had these problems. Perhaps something in the communication between avs4x264.exe and x264_64.exe is causing it, I'm not sure, but it is very annoying. I think this is what caused MeGUI to freeze.
Are you using the latest dev build? I'm asking because the latest build is using vfw4x264 and not avs4x264 because of some problems (e.g. with mpeg2 input). Also please give us more details about how to reproduce this (avs script, media information, and so on).
I still hope to see at least an option to allow us to switch back to the 32-bit encoder. Thanks in advance!
And I hope that this is not necessary.
When I select the animation tuning then in the command line appears the --ref and --bframes commands with the correct number according to the preset and tuning. As far as I know it's not necessary the x264 will calculate these numbers.
Also when a tuning is selected and I change to preset then a --ref command appears with the number related to the preset without the tuning.
the problem i noticed with the tune animation is if you keep slecting it repeatedly, it increases the ref(2x) and bframes(+2) until fatal error when ref tries to go to 24
I cannot reproduce it - at least in my first tests.
whewre to download version: 3.1.1057?
http://megui.xvidvideo.ru/auto/core_0_3_1_1057.zip
Yes, dll is from the latest Winamp rev5.57 (build 2009-12-21).
This dll works with the old enc_aacplus.exe (2006-05-15) from Megui 1056, but exports only raw aac.
With the latest enc_aacplus.exe (2009-10-10) from Megui 1059, it gives the aforementioned error.
And if I put the old enc_aacplus in the latest Megui folder, there's no error and the file is exported in .m4a.
But I always end up with a 32Khz 48kbps file, no matter what setting I choose. :confused:
That's no big deal, I can use the old Megui when I want Winamp AAC (for ultra low bitrates).
Still, I wonder why the needed dll is not downloaded with enc_aacplus since it won't work without it ?
I do not use WinAMP at all. Therefore it would be nice if someone can provide a few more details on how to fix this and what kind of dll is missing.
quantum5uicid3
26th December 2009, 14:27
heres a 12/24 git build of aften pulled from http://code.google.com/p/wavtoac3encoder/downloads/list
i repackaged it to where u just extract it into the megui directory.
http://www.mediafire.com/?ylmmllxgwmj
IT IS NOT TESTED
I do not use WinAMP at all. Therefore it would be nice if someone can provide a few more details on how to fix this and what kind of dll is missing.
dll has to come from winamp for licensing reasons and it's working fine for me
I cannot reproduce it - at least in my first tests.
its a xp sp3 issue apprently because i can't reproduce on vista64
horvathd
26th December 2009, 16:47
the problem i noticed with the tune animation is if you keep slecting it repeatedly, it increases the ref(2x) and bframes(+2) until fatal error when ref tries to go to 24
I can confirm it it's happening to me as well on XP SP3.
lnatan25
26th December 2009, 18:07
Are you using the latest dev build? I'm asking because the latest build is using vfw4x264 and not avs4x264 because of some problems (e.g. with mpeg2 input). Also please give us more details about how to reproduce this (avs script, media information, and so on).
I am now not completely sure where the problem lies. Whilst encoding from MeGUI (I have tried Xvid and x264), various application windows freeze with AppHangXProcB1 (including MeGUI itself), and will only start responding again once a long time has passed and/or the encoding process has finished. It is very important to stress that only happens from encoding initiated by MeGUI, and not CPU stressful operations in general. In fact I have had never heard of this AppHangXProcB1 before, let alone get it on my computer. It has also never happened before on the old MeGUI builds.
Please look into this, this is very problematic, as I cannot use the computer for anything while encoding.
Zathor
26th December 2009, 18:19
Whilst encoding from MeGUI (I have tried Xvid and x264), various application windows freeze with AppHangXProcB1[...]It has also never happened before on the old MeGUI builds.
I have changed nothing regarding Xvid encoding. Can you please try replacing the new megui.exe with an old one which has been working before? I assume at the moment that not MeGUI (at least not alone) is the problem because no one else has this kind of problem.
Please look into this, this is very problematic, as I cannot use the computer for anything while encoding.
Please answer my questions I posted already. If I'm not able to reproduce it I cannot find the source of the problem.
Zathor
26th December 2009, 18:19
dll has to come from winamp for licensing reasons and it's working fine for me
Thanks, so I will not change anything regarding winamp.
lnatan25
26th December 2009, 19:35
I will download an old release tomorrow together with an old x264.exe (just like it was before you stepped in ;)) and do some tests.
pdexdee
26th December 2009, 20:07
this 2 links are dead,please reupload:
http://www.mediafire.com/download.php?mfwnemetzt4
http://www.mediafire.com/download.php?hj23mmmlmux
pdexdee
26th December 2009, 22:56
when will be release:
megui-0.3.1.1060 ?
where is here tutorial how to encode dvd movie in mkv format?
thanks
help_me!
27th December 2009, 11:00
Here's an old guide: http://mewiki.project357.com/wiki/Guides/Basic_Guide
Zathor, HUGE thanks for continuing the development of MeGUI!!
MOS-Marauder
27th December 2009, 12:52
I tried MeGUI from Sourceforge now on a Clean WinXP Install and got the same Problem: One Small Audio Distortion at the beginnign and then an empty Ac3.
I got it at all my latest Captures i wanted to encode.
Chris
quantum5uicid3
27th December 2009, 23:39
I tried MeGUI from Sourceforge now on a Clean WinXP Install and got the same Problem: One Small Audio Distortion at the beginnign and then an empty Ac3.
I got it at all my latest Captures i wanted to encode.
Chris
What format is the source?
MOS-Marauder
28th December 2009, 00:43
SOurce format was Ac3. (ArteHD)
I guess that Distortion could be Switch between Ac2 2.0 and 5.1.. is that possible?
And after that switch was...nothing... Emptyness.
If i encode the same Src wit BeLight 0.22 i have that Distorted scratch, too but the rest Audio is there.
quantum5uicid3
28th December 2009, 01:11
tried both with/without to force decoding via directshow? does the original file playback properly?
uplload a very short sample of source.
MOS-Marauder
28th December 2009, 11:20
tried both with/without to force decoding via directshow? does the original file playback properly?
uplload a very short sample of source.
I tried both.
The Original File plays fine.. but now also with the small Scratch at the beginning. Meanwhile i muxed the Original File to my Video W/o encoding.
But i got some more Files here with that Problem so on the Next one i Upload a small Sample.
Chris
Zathor
28th December 2009, 17:45
The dev build in the first posting will be released as 1060 to the development servers tomorrow and at the beginning of the new year to the stable servers. The time frame may change if problems arise. Please continue testing.
TDC.net
28th December 2009, 23:45
Just a small issue with the 1060 dev build:
Default update server is the stable one, which downloads outdated components for this build.
eg. x264 is too old, weightp is missing in this build.
degindex and dgindexavc are also still shown as updates after update again and again...
stable build from first post is 1058 dev?! should this not be 1059?
Thanks
TDC.net
28th December 2009, 23:48
just another idea:
would it be possible to change mkv muxer settings for a job after having added it to the queue?
eg sometimes the audio delays are wrong, so the user needs to try to find the correct setting.
in the current setting, the user has to enter all data again, so i use mmg in that case where i can only change the delay setting and try again ;)
thanks again
mcwups1
28th December 2009, 23:51
I skimmed through the first 5 pages and saw nothing about a Trojan Horse.
When I downloaded this and unzipped it, I got a message from Norton's 360 similar to this....
mkvtoolnix-unicode-2.4.1-build20081207-44-setup.exe Removed....Trojan Horse
XhmikosR
28th December 2009, 23:55
And you trust Norton?:p And by the way, mkvtoolnix setup has nothing to do with MeGUI. MeGUI uses an unzipped version of mkvtoolnix. Both are open source programs; feel free to take a look at their source code to see for yourself if there really is a trojan ;)
quantum5uicid3
29th December 2009, 00:32
zathor, once you release a stable version with installer included, it would probably be a good idea to completely remove all the old "stable" tools from the update.xml and start off by bringing both the stable and development branches to the current toolset. so all these old versions can get out of rotation and also so the stable and devlopment branches would be more uniform going forward.
quantum5uicid3
29th December 2009, 01:13
I skimmed through the first 5 pages and saw nothing about a Trojan Horse.
When I downloaded this and unzipped it, I got a message from Norton's 360 similar to this....
yes, it's a false positive, but why are you downloading a year old version of matroska tools?
quantum5uicid3
29th December 2009, 03:38
Yes, dll is from the latest Winamp rev5.57 (build 2009-12-21).
This dll works with the old enc_aacplus.exe (2006-05-15) from Megui 1056, but exports only raw aac.
With the latest enc_aacplus.exe (2009-10-10) from Megui 1059, it gives the aforementioned error.
And if I put the old enc_aacplus in the latest Megui folder, there's no error and the file is exported in .m4a.
But I always end up with a 32Khz 48kbps file, no matter what setting I choose. :confused:
That's no big deal, I can use the old Megui when I want Winamp AAC (for ultra low bitrates).
Still, I wonder why the needed dll is not downloaded with enc_aacplus since it won't work without it ?
finally ran across a similar prob. latest enc_aacplus.exe doesn't work with winamp 5.57. u need these files from 5.56
enc_aacplus.dll
nscrt.dll
libmp4v2.dll
gahz
29th December 2009, 04:22
yes, the extent varies. like i siad, you are going to need to change your crf and settings to find a new balance.
i'm trying to wrap my head around this. which would be true then in my way of thought to this quote:
1. keep my current crf value of 18 and just realize that my new encodes are lower in bitrate because the new x264 stuff is just more efficient.
or
2. my old crf value of 18 is now a value of 16(just guessing a number here) with the newer version and i should adjust my crf value.
as far as i can tell i havent seen any reduction in quality so i'm thinking arguement 1 is more sound than #2.
buzzqw
29th December 2009, 08:02
will be possibile to have a new full package ? (with all required softwares/profiles updates)
thanks
BHH
Kurtnoise
29th December 2009, 08:54
finally ran across a similar prob. latest enc_aacplus.exe doesn't work with winamp 5.57. u need these files from 5.56
enc_aacplus.dll
nscrt.dll
libmp4v2.dll
It's because winamp developpers have turned on some new options during their libraries compilation processes. In other words, we also needs to recompile enc_aacplus. It's already done in my local tree. I'll probably upload a new build tomorrow...
gahz
29th December 2009, 11:29
quick update. i enabled b-pyramid and now i'm getting the bitrates and filesizes i used to get. i didn't know b-pyramid would increase things that much.
TDC.net
29th December 2009, 15:22
feedback for x64 encoding,
Running x64_x264 on my Core i7 920 at 2.67 GHz I get a speed increase of 22% compared to x264 (x86).
Thanks for adding x64 support in MeGUI :)
alwa
29th December 2009, 19:32
Since they are actually used i've decided to update the wrapper.
Click (http://www.mediafire.com/file/xmomu3nzmob/x264_wrapper.zip)
Changes:
avs4x264: applied MT fix from x264 & better error handling
vfw4x264: better error handling
Have Fun...
nakTT
29th December 2009, 20:21
Since they are actually used i've decided to update the wrapper.
Click (http://www.mediafire.com/file/xmomu3nzmob/x264_wrapper.zip)
Changes:
avs4x264: applied MT fix from x264 & better error handling
vfw4x264: better error handling
Have Fun...
So you are the developer of the two softwares that makes 64bit x264 with avisynth 32bit possible? I thank you for that.
:thanks:
P/S: Do you have any website or something that we can browse through for change log and other info, just for the fun of it?
Zathor
29th December 2009, 23:27
Uploaded latest build (0.3.1.1060) to the development update servers. Please adress all problems with this build as usual. Thanks.
Zathor
29th December 2009, 23:30
zathor, once you release a stable version with installer included, it would probably be a good idea to completely remove all the old "stable" tools from the update.xml and start off by bringing both the stable and development branches to the current toolset. so all these old versions can get out of rotation and also so the stable and devlopment branches would be more uniform going forward.
Yes, that's the plan. If no serious problems arise I will release 1060 soon (start of the next week to have some time for testing) as a stable build to the update servers.
horvathd
30th December 2009, 00:41
Also when a tuning is selected and I change the preset then a --ref command appears with the number related to the preset without the tuning.
After checking the source code I think the problem is that when you have a tuning selected and then you change the preset the default values are set only according to the new preset and the modifications of the tuning is left out until you select it again.
I think the solution is that when you change the preset or tuning, first the values have to update according to the preset and then the tuning.
2019 private void btPresetSettings_Click(object sender, EventArgs e)
2020 {
2021 doPresetsAdjustments();
doTuningsAdjustments();
genericUpdate();
2023 }
2024
2025 private void x264Tunes_SelectedIndexChanged(object sender, EventArgs e)
2026 {
doPresetsAdjustments();
2027 doTuningsAdjustments();
2028 genericUpdate();
2029 }
Modifications are in italic. Also the if() should be left out from btPresetSettings_Click() since it is possible to move back the preset to Medium.
Kurtnoise
30th December 2009, 09:13
It's because winamp developpers have turned on some new options during their libraries compilation processes. In other words, we also needs to recompile enc_aacplus. It's already done in my local tree. I'll probably upload a new build tomorrow...
http://aacpluscli.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=37963
alwa
30th December 2009, 15:11
So you are the developer of the two softwares that makes 64bit x264 with avisynth 32bit possible? I thank you for that.
No problemo :). I'm happy MeGUI works again and supports x264 64Bit. Thanks to Zathor for that.
P/S: Do you have any website or something that we can browse through for change log and other info, just for the fun of it?
No, sorry. But it's practically copied from the input of x264 + the piping part. And there will be any updates for the Wrapper in future, except for fixing bugs(if there are any). Because i think there is not much more that can be done for the Wrappers.
nakTT
31st December 2009, 04:00
Uploaded latest build (0.3.1.1060) to the development update servers. Please adress all problems with this build as usual. Thanks.
Many thanks for the latest release. Testing it as we speak.
:thanks:
Likeatree
1st January 2010, 10:17
The latest update broke something in the wrapper for me:
cmd looks find though:
Edit: Nevemind it was something else
Remicade
1st January 2010, 19:26
Dumb question: i made update to 1060 and DXVA-HD-Balanced, Extra Quality, HQ is gone. Where ? :(
I have x264 Unrestricted (DXVA) but is something wrong when I hit AutoEncode I don't have any option for File Size is grey.
rapscallion
1st January 2010, 20:51
Zathor, thank you for all your work in keeping Megui alive .These new builds look very promising.
My one request would be if you could please create a profile for: "x264:Standalone AVC-HD"
Vs x264:Blu-ray, I know VBV buffer ,VBV max br and Q Comp are different, but I'm sure there are other settings as well.
lnatan25
2nd January 2010, 08:19
Dumb question: i made update to 1060 and DXVA-HD-Balanced, Extra Quality, HQ is gone. Where ? :(
I have x264 Unrestricted (DXVA) but is something wrong when I hit AutoEncode I don't have any option for File Size is grey.
That's because most of the profiles are CRF based, as opposed to bitrate based. Select the "Unrestricted (DXVA) - 2-Pass" profile. You might also want to hit "Config" on it and move the slider from "Medium" to "Slower" or "Very Slow". :)
MOS-Marauder
2nd January 2010, 11:22
HM since 0.3.1.1060 i cannot use MeGui anymore. It Simply Crashes in Pass 1 after some Seconds on 720p Encodes.
Dunno why.... If i use Neurons DG NV Tools it "would" work but they crash my Nvidia Driver all the Time so i cannot use.
I enclosed the Complete Log. Maybe someone see something that may help.
Chris
Edit:
I found out that its Definitive done by DGAVCIndex/DLL v 1.0.9 ! I can play that AVS sone Seconds and then MplayerClassic also crashes with the same message as u see in the MeGui Log ( This application has requested the Runtime to terminate it in an unusual way. - and so on)
But all this ONLY happens on 720 p Streams. With an 1080i i got no problem.
My AVS:
LoadPlugin("C:\Program Files (x86)\megui\tools\dgavcindex\DGAVCDecode.dll")
AVCSource("F:\000-CAPTURE-BACKUP\____BluRay-BRENN\Catchmeifyoucan\01-01_20-10-00_Das Erste HD_Catch me if you can - Mein Leben auf der Flucht Demux\catch.dga")
#deinterlace
crop( 6, 0, 0, 0)
LanczosResize(1280,720) # Lanczos (Sharp)
So nothing Special inside... But: the Title of the Crash Windows shows Microsoft Visual C Runtime Library.... Maybe because the Mplayer Classic is Progged with that.
[Information] Log
-[Information] Versions
--[NoImage] MeGUI Version : 0.3.1.1060
--[NoImage] OS : Windows Seven Ultimate Edition x64 (6.1.0.7600)
--[NoImage] Latest .Net Framework installed : 3.5 SP1 (3.5.30729.4926)
--[NoImage] Avisynth Version : 2.6.0.1
-[Information] AutoEncode job generation log
--[NoImage] Desired Size : 4,38 GB
--[NoImage] Split Size : null
--[Information] Eliminating duplicate filenames
---[NoImage] Video output file: F:\000-CAPTURE-BACKUP\____BluRay-BRENN\Catchmeifyoucan\01-01_20-10-00_Das Erste HD_Catch me if you can - Mein Leben auf der Flucht Demux\catch.264
---[NoImage] Muxed output file: F:\000-CAPTURE-BACKUP\____BluRay-BRENN\Catchmeifyoucan\01-01_20-10-00_Das Erste HD_Catch me if you can - Mein Leben auf der Flucht Demux\catch-muxed.mkv
---[NoImage] Encodable audio stream 0: F:\000-CAPTURE-BACKUP\____BluRay-BRENN\Catchmeifyoucan\01-01_20-10-00_Das Erste HD_Catch me if you can - Mein Leben auf der Flucht Demux\audio_.ac3
-[Information] Log for job1 (audio, 01-01_20-10-00_Das Erste HD_Catch me if you can - Mein Leben auf der Flucht.6022_.ac3 -> audio_.ac3)
--[Information] [02.01.2010 11:16:16] Started handling job
--[Information] [02.01.2010 11:16:16] Preprocessing
--[NoImage] Avisynth script
---[NoImage] LoadPlugin("C:\Program Files (x86)\megui\tools\avisynth_plugin\NicAudio.dll")
---[NoImage] NicAc3Source("F:\000-CAPTURE-BACKUP\____BluRay-BRENN\Catchmeifyoucan\01-01_20-10-00_Das Erste HD_Catch me if you can - Mein Leben auf der Flucht Demux\01-01_20-10-00_Das Erste HD_Catch me if you can - Mein Leben auf der Flucht.6022_.ac3", DRC=1)
---[NoImage] Normalize()
---[NoImage] return last
--[NoImage] Commandline used: -readtoeof 1 -b 224 - "{0}"
--[Information] [02.01.2010 11:16:16] Encoding started
--[Information] [02.01.2010 11:16:16] Encode thread started
--[Information] [02.01.2010 11:16:16] Avisynth script environment opened
--[Information] [02.01.2010 11:16:16] Script loaded
--[Information] Output Decoder
---[NoImage] Channels: 2
---[NoImage] Bits per sample: 32
---[NoImage] Sample rate: 48000
--[NoImage] Commandline: C:\Program Files (x86)\megui\tools\aften\aften.exe -readtoeof 1 -b 224 - "F:\000-CAPTURE-BACKUP\____BluRay-BRENN\Catchmeifyoucan\01-01_20-10-00_Das Erste HD_Catch me if you can - Mein Leben auf der Flucht Demux\audio_.ac3"
--[Information] [02.01.2010 11:16:16] Encoder process started
--[NoImage] Output from encoder via stderr
---[NoImage] Aften: A/52 audio encoder
---[NoImage] Version 0.0.8
---[NoImage] (c) 2006-2007 Justin Ruggles, Prakash Punnoor, et al.
---[NoImage] input format: WAVE Floating-point 32-bit little-endian 48000 Hz stereo
---[NoImage] output format: 48000 Hz stereo (2/0)
---[NoImage] SIMD usage: MMX SSE SSE2 SSE3
---[NoImage] Threads: 4
---[NoImage] progress: 0% | q: 243.7 | bw: 48.0 | bitrate: 224.0 kbps
--[Information] [02.01.2010 11:17:31] Postprocessing
--[Information] [02.01.2010 11:17:31] Job completed
-[Information] Log for job2 (video, catch.avs -> )
--[Information] [02.01.2010 11:17:31] Started handling job
--[Information] [02.01.2010 11:17:31] Preprocessing
---[Information] Bitrate calculation for video
----[NoImage] Desired size after subtracting audio: 4366303KBs
----[NoImage] Calculated desired bitrate: 4518kbit/s
--[NoImage] Job commandline: "C:\Program Files (x86)\megui\tools\x264\vfw4x264.exe" --profile high --level 4.1 --pass 1 --bitrate 4518 --stats "F:\000-CAPTURE-BACKUP\____BluRay-BRENN\Catchmeifyoucan\01-01_20-10-00_Das Erste HD_Catch me if you can - Mein Leben auf der Flucht Demux\catch.stats" --thread-input --b-adapt 2 --no-weightb --ref 4 --weightp 0 --vbv-bufsize 50000 --vbv-maxrate 50000 --me umh --direct auto --partitions p8x8,b8x8,i4x4,i8x8 --no-fast-pskip --sar 1:1 --output NUL "F:\000-CAPTURE-BACKUP\____BluRay-BRENN\Catchmeifyoucan\01-01_20-10-00_Das Erste HD_Catch me if you can - Mein Leben auf der Flucht Demux\catch.avs"
--[Information] [02.01.2010 11:17:33] Encoding started
--[NoImage] Standard output stream
--[NoImage] Standard error stream
---[NoImage] x264 [info]: 1280x720 @ 50.00 fps
---[NoImage] x264 [info]: using SAR=1/1
---[NoImage] x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 FastShuffle SSE4.1 Cache64
---[NoImage] x264 [info]: profile Main, level 4.1
---[NoImage] This application has requested the Runtime to terminate it in an unusual way.
---[NoImage] Please contact the application's support team for more information.
---[NoImage]
---[NoImage] x264 [info]: frame I:2 Avg QP:17.99 size: 47304
---[NoImage] x264 [info]: frame P:170 Avg QP:18.13 size: 25809
---[NoImage] x264 [info]: frame B:157 Avg QP:18.11 size: 2641
---[NoImage] x264 [info]: consecutive B-frames: 9.5% 74.0% 16.5% 0.0%
---[NoImage] x264 [info]: mb I I16..4: 71.7% 0.0% 28.3%
---[NoImage] x264 [info]: mb P I16..4: 57.1% 0.0% 0.0% P16..4: 36.7% 0.0% 0.0% 0.0% 0.0% skip: 6.2%
---[NoImage] x264 [info]: mb B I16..4: 1.4% 0.0% 0.0% B16..8: 10.7% 0.0% 0.0% direct:12.3% skip:75.6% L0:18.0% L1:78.9% BI: 3.1%
---[NoImage] x264 [info]: final ratefactor: 19.69
---[NoImage] x264 [info]: direct mvs spatial:97.5% temporal:2.5%
---[NoImage] x264 [info]: coded y,uvDC,uvAC intra: 40.8% 49.2% 10.2% inter: 11.6% 18.4% 0.5%
---[NoImage] x264 [info]: i16 v,h,dc,p: 35% 21% 21% 22%
---[NoImage] x264 [info]: i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 14% 14% 31% 8% 7% 7% 6% 6% 6%
---[NoImage] x264 [info]: kb/s:5953.50
---[NoImage] encoded 329 frames, 18.83 fps, 5953.50 kb/s
--[Information] [02.01.2010 11:17:51] Job completed
quantum5uicid3
2nd January 2010, 14:32
Zathor, thank you for all your work in keeping Megui alive .These new builds look very promising.
My one request would be if you could please create a profile for: "x264:Standalone AVC-HD"
Vs x264:Blu-ray, I know VBV buffer ,VBV max br and Q Comp are different, but I'm sure there are other settings as well.
AVCHD preset is Level 4.1. Anything beyond that is implementation specific.
oops and max bitrate of 24Mbps
whats the point of encoding to an AVCHD compliant stream using x264 anyways? my interpretation of it is a marketing term for h264 encoding digital video camcorders. since your playback device will probably be either a DVD player, Bluray Player, or a computer, why not just worry about those constraints?
rapscallion
2nd January 2010, 15:21
AVCHD preset is Level 4.1. Anything beyond that is implementation specific.
oops and max bitrate of 24Mbps
whats the point of encoding to an AVCHD compliant stream using x264 anyways? my interpretation of it is a marketing term for h264 encoding digital video recorders. since your playback device will probably be either a DVD player, Bluray Player, or a computer, why not just worry about those constraints?
Thanks for your response.
Both Blu-ray and AVCHD are level 4.1
I'm encoding to a avchd compliant stream because I'm making movie backups to DVD-R DL, not BD-R. My playback device is a SA BD player. Even though the player is a constraint, so is the media.
If you recall, before Sharktooth left the project, one of the profiles was, in fact, SA AVCHD. If I use the Blu-ray profile the settings will be incorrect, thus my original request to Zathor.
Capsbackup
2nd January 2010, 15:54
Is there something wrong with the existing SA AVCHD profile that I have in my MeGUI 0.3.1.1060 ? I have not used it for quite some time, since BD-RB made things simpler, but it would be nice to know if it is know longer a valid profile. Perhaps, if it is not valid, what changes could be made to that profile to make it current/valid ? :confused:
rapscallion
2nd January 2010, 15:57
Is there something wrong with the existing SA AVCHD profile that I have in my MeGUI 0.3.1.1060 ? I have not used it for quite some time, since BD-RB made things simpler, but it would be nice to know if it is know longer a valid profile. Perhaps, if it is not valid, what changes could be made to that profile to make it current/valid ? :confused:No, it's no longer valid and those changes are exactly what I'm asking.
Capsbackup
2nd January 2010, 16:51
No, it's no longer valid and those changes are exactly what I'm asking.
OK thanks, good to know. Hopefully we will get a reply as to what changes to implement or a new SA AVCHD profile.
quantum5uicid3
2nd January 2010, 16:53
ok, the only difference between the bluray preset and an avchd preset would be the vbv. maxbitrate for dvd is 18Mbps
so...
the safe setting would be
--vbv-maxrate 14000 --vbv-bufsize 14500
if sharktooth's preset always worked, use
--vbv-maxrate 16500 --vbv-bufsize 16500
Triccotracco
2nd January 2010, 18:41
When I select the animation tuning then in the command line appears the --ref and --bframes commands with the correct number according to the preset and tuning. As far as I know it's not necessary the x264 will calculate these numbers.
Also when a tuning is selected and I change to preset then a --ref command appears with the number related to the preset without the tuning.
Hey guys, first of all happy new year! ;););)
Also for me the problem exist + the aud option appear (not set in x264 config window):
Job commandline: "C:\Program Files\megui patched\tools\x264\x264.exe" --preset slow --tune animation --thread-input --bframes 5 --ref 10 --aud
--bframes 5 --ref 10 are not necessary the x264 will calculate these numbers so the following is equivalent:
Job commandline: "C:\Program Files\megui patched\tools\x264\x264.exe" --preset slow --tune animation --thread-input
also --aud appear (not set in x264 config window).
:thanks:
Zathor
3rd January 2010, 10:37
HM since 0.3.1.1060 i cannot use MeGui anymore. It Simply Crashes in Pass 1 after some Seconds on 720p Encodes.
Dunno why.... If i use Neurons DG NV Tools it "would" work but they crash my Nvidia Driver all the Time so i cannot use.
Edit:
I found out that its Definitive done by DGAVCIndex/DLL v 1.0.9 ! I can play that AVS sone Seconds and then MplayerClassic also crashes with the same message as u see in the MeGui Log ( This application has requested the Runtime to terminate it in an unusual way. - and so on)
But all this ONLY happens on 720 p Streams. With an 1080i i got no problem.
Please try to encode it without MeGUI in order to find the source of the problem. Simply execute this command line:
"C:\Program Files (x86)\megui\tools\x264\vfw4x264.exe" --profile high --level 4.1 --pass 1 --bitrate 4518 --stats "F:\000-CAPTURE-BACKUP\____BluRay-BRENN\Catchmeifyoucan\01-01_20-10-00_Das Erste HD_Catch me if you can - Mein Leben auf der Flucht Demux\catch.stats" --thread-input --b-adapt 2 --no-weightb --ref 4 --weightp 0 --vbv-bufsize 50000 --vbv-maxrate 50000 --me umh --direct auto --partitions p8x8,b8x8,i4x4,i8x8 --no-fast-pskip --sar 1:1 --output NUL "F:\000-CAPTURE-BACKUP\____BluRay-BRENN\Catchmeifyoucan\01-01_20-10-00_Das Erste HD_Catch me if you can - Mein Leben auf der Flucht Demux\catch.avs"
If this crashs, too, please replace the vfw4x264.exe with x264.exe and try it again. If it still crashes please post a short sample of the source here or in the DGIndex subforum. Maybe the source stream with 50fps is the problem.
EDIT: I have read your text again. If you have the problem also with the avs file + media player classic I assume that the source and not MeGUI is the problem. Please post a sample of the source to the DGIndex subforum.
Zathor
3rd January 2010, 10:44
--bframes 5 --ref 10 are not necessary the x264 will calculate these numbers so the following is equivalent:
Yes, this is still not changed but not very important. Nevertheless I will change it.
also --aud appear (not set in x264 config window).
I do not have this problem. Do you have specified it in the custom command line?
MOS-Marauder
3rd January 2010, 11:22
If this crashs, too, please replace the vfw4x264.exe with x264.exe and try it again. If it still crashes please post a short sample of the source here or in the DGIndex subforum. Maybe the source stream with 50fps is the problem.
EDIT: I have read your text again. If you have the problem also with the avs file + media player classic I assume that the source and not MeGUI is the problem. Please post a sample of the source to the DGIndex subforum.
Thx Zathor i will do it.
The Strange thing is: i already used it before exact the same way. 720p/50 FPS Streams from ArteHD (Germany). I have Old from ArteHD that still work. Only the new ones wont.. And (of course now) Das Erste HD...So i go and ask Donald maybe he knows this Problem already.
Chris
Zathor
3rd January 2010, 11:46
Thx Zathor i will do it.
The Strange thing is: i already used it before exact the same way. 720p/50 FPS Streams from ArteHD (Germany). I have Old from ArteHD that still work. Only the new ones wont.. And (of course now) Das Erste HD...So i go and ask Donald maybe he knows this Problem already.
"Das Erste HD" is still in some kind of showcase. Maybe they have changed a thing in comparison to ArteHD. With the sample we can see if this is a general problem with the source or "only" a problem on your side.
Zathor
3rd January 2010, 14:22
After checking the source code I think the problem is that when you have a tuning selected and then you change the preset the default values are set only according to the new preset and the modifications of the tuning is left out until you select it again.
I think the solution is that when you change the preset or tuning, first the values have to update according to the preset and then the tuning.
2019 private void btPresetSettings_Click(object sender, EventArgs e)
2020 {
2021 doPresetsAdjustments();
doTuningsAdjustments();
genericUpdate();
2023 }
2024
2025 private void x264Tunes_SelectedIndexChanged(object sender, EventArgs e)
2026 {
doPresetsAdjustments();
2027 doTuningsAdjustments();
2028 genericUpdate();
2029 }
Modifications are in italic. Also the if() should be left out from btPresetSettings_Click() since it is possible to move back the preset to Medium.
Thanks, I have removed the "if" so that you can revert back to the medium presets. I have not added your other changes. If you change the tune setting this would also revert all preset settings to their default settings and this may not the expected behavior for the user.
horvathd
3rd January 2010, 14:46
Thats ok. But when you change the preset after it the tunings have to be applied again. Right? So I guess in the btPresetSettings_Click() function the doTuningsAdjustments() is still necessary.
Zathor
3rd January 2010, 15:15
The btPresetSettings_Click() will only be fired if the "Preset settings" button is clicked so that the default settings of the preset will be loaded. I'm a little bit unsure if I would like to have the tuning settings applied, too. Both actions (apply or not) have some drawbacks.
rapscallion
3rd January 2010, 15:30
ok, the only difference between the bluray preset and an avchd preset would be the vbv. maxbitrate for dvd is 18Mbps
so...
the safe setting would be
--vbv-maxrate 14000 --vbv-bufsize 14500
if sharktooth's preset always worked, use
--vbv-maxrate 16500 --vbv-bufsize 16500
Thanks "q".....yes ST's 16500 always worked without a problem so I'll stay with it for now.
Edit : I see some other minor differences and one big, between avchd and blu-ray presets.
And that is GOP size. Blu-ray 2-pass defaults to max 250, min 25. While AVCHD defaults to max 24, min 2. That's a significant difference and I'm curious why ?
horvathd
3rd January 2010, 15:35
In that case your right, I thought it runs when the preset is changed. But I think the tunings should be reseted also when this button is pressed.
Now, it works like:
1.) Default settings:
program --output "output" "input"
2.) I select the Slow preset:
program --preset slow --output "output" "input"
3.) Select animation tuning:
program --preset slow --tune animation --bframes 5 --ref 10 --output "output" "input"
4.) Click preset settings button:
program --preset slow --tune animation --ref 5 --output "output" "input"
It changes back the --ref to 5 but the animation tuning is still applied except the --ref.
I check the source again and I found the tbx264Presets_Scroll() which is runs when the preset slider is moved. So if I'm right, also should contain a doTuningsAdjustments() function or it needs to reset the tunings.
Zathor
3rd January 2010, 20:14
In that case your right, I thought it runs when the preset is changed. But I think the tunings should be reseted also when this button is pressed.
0.3.1.1061
- [x264Encoder] updated the command line generation
- [x264ConfigurationPanel] button "preset settings" also reloads the tuning settings
Download in the first posting. If checked the command line generation in oder to be in sync with the x264 documentation. Because of many changes there may be new wrong command lines but hopefully I have fixed more problems than creating new ones.
I'm still on the way towards a real stable build in the next week.
Regarding the x264 profile request in this thread I can only say that I am surely no expert in these things and will not create profiles myself for the public.
rapscallion
3rd January 2010, 20:37
[CODE]
Regarding the x264 profile request in this thread I can only say that I am surely no expert in these things and will not create profiles myself for the public.
Zathor, then you did not create the "blu-ray-2pass" profile that 1060 updates to ?
Because I was going to ask why the max 250 GOP size, where the wiki recommends 1X the framerate for blu-ray ?
Zathor
3rd January 2010, 20:45
Zathor, then you did not create the "blu-ray-2pass" profile that 1060 updates to ?
Yes. quantum5uicid3 created the package and I think he did a great job.
Because I was going to ask why the max 250 GOP size, where the wiki recommends 1X the framerate for blu-ray ?
Because of "--keyint 24" in the custom command line a GOP size of 24 will be applied. It is a little bit confusing, but the custom command line will overwrite every setting you can see/edit in the other GUI elements. The custom command line is some kind of "device preset".
horvathd
3rd January 2010, 20:55
Download in the first posting. If checked the command line generation in oder to be in sync with the x264 documentation. Because of many changes there may be new wrong command lines but hopefully I have fixed more problems than creating new ones.
The command line generation still has some flaws.
1.) Preset settings button don't reset some of the variables, for example the --qpmin.
2.) Grain tunings add --deadzone-inter 21 --deadzone-intra 11 to the command line, but according to the x264's fullhelp the default is --deadzone-inter 6 --deadzone-intra 6.
3.) If you select the Animation tunings multiple time one after the other you get this command line:
Default: program --output "output" "input"
Selected once: program --tune animation --output "output" "input"
Selected twice: program --tune animation --bframes 7 --ref 12 --output "output" "input"
Selected three times: program --tune animation --bframes 9 --ref 12 --output "output" "input"
4.) When you have Medium preset and Animation tunings selected and then you change the preset to Fast you get this:
program --preset fast --tune animation --bframes 3 --ref 2 --output "output" "input"
where the numbers at --bframes and --ref are wrong they didn't count in the modification of the tunings.
M4ST3R
3rd January 2010, 20:56
I'm a noob but I think that the "adaptive quantization" checkbox in the xvid settings is useless/does nothing
Triccotracco
3rd January 2010, 20:58
Yes, this is still not changed but not very important. Nevertheless I will change it.
I do not have this problem. Do you have specified it in the custom command line?
No, the custom command line is empty but --aud option appear in the log, not a real problem i think only cosmetic.
:thanks:
Zathor
3rd January 2010, 21:05
No, the custom command line is empty but --aud option appear in the log, not a real problem i think only cosmetic.
:thanks:
Ok, found this in the code:
// recommended by the specs
if (output.EndsWith(".264"))
sb.Append("--aud ");
So if your output type is .264 it wil allways encode with --aud. I do not know if this is really necessary and I can not find documentation about this behavior.
horvathd
3rd January 2010, 21:11
There is a topic regarding --aud: http://forum.doom9.org/showthread.php?t=144241
stax76
3rd January 2010, 21:21
I do not know if this is really necessary and I can not find documentation about this behavior.
Maybe for certain devices, I don't think it should be hardcoded but rather be enabled in device presets.
rapscallion
3rd January 2010, 22:24
Yes. quantum5uicid3 created the package and I think he did a great job.
I agree !
Because of "--keyint 24" in the custom command line a GOP size of 24 will be applied. It is a little bit confusing, but the custom command line will overwrite every setting you can see/edit in the other GUI elements. The custom command line is some kind of "device preset".
Ah ha, that one got by me. Thank you and look forward to the stable ver, if it happens next week.
If not, you know that we'll all be patient because we are so grateful that you've continued development of Megui.
Rat Killer
4th January 2010, 11:47
I have what I hope is a minor fix request in the GUI.
HD Streamsextractor, select file as input, click browse button, a file select box opens with a filter applied to the list of files 'All Files supported (*.*)' Unfortunatly the filter does not include mkv files which the tool supports requireing manual entry of the file name or *.mkv as a search. Can you fix the filter such that *.mkv files are included in the 'All Files supported' default filter? Small thing but I use this tool a LOT.
Thanks!
quantum5uicid3
4th January 2010, 17:09
credit really goes to Kurtnoise for compiling the device settings spreadsheet. i updated the profiles to include AVCHD (DVD5/9) and an "Insane" quality preset with crf 17.
rack04
4th January 2010, 17:09
I have a dumb question. I have recently installed Windows 7 Ultimate 64bit. If I want to run the 64bit capable tools included with MeGUI in 64bit do I need to install the programs to "Program Files" or "Program Files (86)"?
help_me!
4th January 2010, 18:52
Doesn't matter at all.
Zathor
4th January 2010, 22:53
HD Streamsextractor, select file as input, click browse button, a file select box opens with a filter applied to the list of files 'All Files supported (*.*)' Unfortunatly the filter does not include mkv files which the tool supports requireing manual entry of the file name or *.mkv as a search. Can you fix the filter such that *.mkv files are included in the 'All Files supported' default filter?
- [DGIndexer] added percentage output to the progress window
- [DGNVIndexer] + [DGAVCIndexer] prepared for reading the stdout so that the percentage can be read as soon as it is supported by the tools
- [HDBDStreamExtractor] added mkv as file input source
- [HDBDStreamExtractor] for audio stream types the first stream output type will be preselected
- [MeGUISettings] + [SettingsForm] + [MP4BoxMuxer] added temporary folder selection for mp4 muxer
- [SettingsForm] cosmetics
Link in the first posting.
rapscallion
4th January 2010, 23:40
credit really goes to Kurtnoise for compiling the device settings spreadsheet. i updated the profiles to include AVCHD (DVD5/9)
Will that be included as an update in the next stable build ?
ircopdd
5th January 2010, 02:48
Hi Zathor
i use DGindexNV
mpeg2 encode
Audio not synchronized
can you Check?
Thanks!
Zathor
5th January 2010, 06:22
Will that be included as an update in the next stable build ?
Yes
i use DGindexNV
mpeg2 encode
Audio not synchronized
can you Check?
Can you please upload a source sample and provide more details?
ircopdd
5th January 2010, 08:56
Can you please upload a source sample and provide more details?
source sample
215mb
http://www.multiupload.com/HHUQ2LEPIU
part1
http://www.multiupload.com/DO6V17PHX2
part2
http://www.multiupload.com/U8TKNCQFKP
part3
DGindexNV -201 ms Not synchronized
DGindex -201ms synchronized
I do not know why
http://txd9gg.bay.livefilestore.com/y1pbQ_-NUlB-Hhog5hclBIe1B7mdMkeZDbkUENCsyuwOkk0IZCMCiTkXSHNTzP0f_3sxrFzFqBW2pZ2VyG-M8kND1fQCjnOJFMM/APC%20-%202010.01.05%2015.50%20-%20001.3d.jpg
Knuffi
5th January 2010, 13:02
The Update-routine of the new presets is a little buggy: Neither "Import" nor "Cancel" close the window.
Kurtnoise
5th January 2010, 13:16
- [HDBDStreamExtractor] added mkv as file input source
be aware that eac3to doesn't handle all streams which can be found in mkv nowadays. That's why I hadn't added this extension.
Zathor
5th January 2010, 14:03
be aware that eac3to doesn't handle all streams which can be found in mkv nowadays. That's why I hadn't added this extension.
Thank you very much for your warning! Do you know which streams can not be handled? I would like to make a few tests with these streams.
The Update-routine of the new presets is a little buggy: Neither "Import" nor "Cancel" close the window.
I will check this later.
buzzqw
5th January 2010, 14:11
also.. proxy seems to not work
BHH
saint-francis
5th January 2010, 18:08
Long standing issue with the HD stream extractor. When selecting an output format you need to click on the box 3 times to get a drop down.
Also i want to second this:
The Update-routine of the new presets is a little buggy: Neither "Import" nor "Cancel" close the window.
BTW.
Everyone involved in MeGUI development.... You rock. Thank you all for making the most versatile GUI available.
Kurtnoise
5th January 2010, 18:18
Do you know which streams can not be handled?
iirc, mainly AAC & subtitles streams (SRT,SSA,VobSub)...
Long standing issue with the HD stream extractor. When selecting an output format you need to click on the box 3 times to get a drop down.
this comes from the designed component...
saint-francis
5th January 2010, 19:04
this comes from the designed component...
You mean this (http://forum.doom9.org/showthread.php?t=141829)tool? As I recall the issue was there and it eventually disappeared. I think that in it's last iterations the issue was not present but it was when merged with MeGUI. Correct me if I'm wrong.
Rat Killer
5th January 2010, 20:42
- [DGIndexer] added percentage output to the progress window
- [DGNVIndexer] + [DGAVCIndexer] prepared for reading the stdout so that the percentage can be read as soon as it is supported by the tools
- [HDBDStreamExtractor] added mkv as file input source
- [HDBDStreamExtractor] for audio stream types the first stream output type will be preselected
- [MeGUISettings] + [SettingsForm] + [MP4BoxMuxer] added temporary folder selection for mp4 muxer
- [SettingsForm] cosmetics
Link in the first posting.
:thanks:
Zathor
5th January 2010, 23:17
The Update-routine of the new presets is a little buggy: Neither "Import" nor "Cancel" close the window.
Fixed (new build in first post)
also.. proxy seems to not work
Can someone confirm that the proxy is working (or not)? I have no proxy to test but if I use a wrong proxy the connection will fail (as expected). So the proxy value is used.
DGindexNV -201 ms Not synchronized
DGindex -201ms synchronized
I do not know why
DGIndexNV, 99,99% film, 29,970 fps
DGIndex, 94,85% film, 23,976 fps
Seems to be a problem with film detection. I have to confess that I have no experience with film because I live in PAL land... need to read a few things about it.
EDIT: Solution found. Edit your dgi file and replace "FO 2" with "FO 1" and "FPS 30000 / 1001" with "FPS 24000 / 1001". This will be added automatically like in the dgv with the next build.
rtjnyoface
6th January 2010, 00:08
I'm getting a directshow error when opening .ts (or m2ts) files in the avisynth creator. I know this has been addressed before but I couldn't find the answer. I've reintstalled ffdshow. Anyone care to reiterate?
gwaitsi
6th January 2010, 00:18
when i open DG Creator, DGIndexNV is greyed out. this happens on both my machines, one which has a 8600GTS - supported card according to the author.
If i try to run DGIndexNV directly, it says license.txt is missing. is this required for MeGUI?
I am trying to converty a vc1 source and i did it with AVS Creator using direct show, but the converted video plays back choppy.
Knuffi
6th January 2010, 00:18
MKV as input file is really a great feature! THANKS!
BTW: 1061 from the first post calls itself 1060 ... ;)
Zathor
6th January 2010, 00:26
BTW: 1061 from the first post calls itself 1060 ... ;)
Yes, the version number changes as soon as 1061 is officially released. Therefore it is possible to update all dev 1061 builds with the final build.
when i open DG Creator, DGIndexNV is greyed out. this happens on both my machines, one which has a 8600GTS - supported card according to the author.
If i try to run DGIndexNV directly, it says license.txt is missing. is this required for MeGUI?
You need the license.txt to use DGIndexNV:
http://neuron2.net/dgdecnv/dgdecnv.html
rtjnyoface
6th January 2010, 00:38
I've begun to get confused now that (1) I've updated to the latest development of megui and (2) started the blu ray process since I've recently bought a blu ray drive. I don't have a CUDA graphics card, so am I not able to decode blu ray movies? Sorry but the blu ray transcoding process related to Megui is quite unclear to me.
edit: can we encode DTS HD to aac in Megui?
Rat Killer
6th January 2010, 01:26
I use the HD streams extractor to extract an h264 and an ac3 track from an mkv. Then use the mp4 muxer to put them in an IMSA standard mp4 container. The original mkv plays fine, the mp4 the audio is very out of sync and seems to get worse throughout the video.
Ideas what I am doing wrong or how I can accomplish the mkv -> mp4 conversion and maintain the audio sync?
Zathor
6th January 2010, 06:30
I've begun to get confused now that (1) I've updated to the latest development of megui and (2) started the blu ray process since I've recently bought a blu ray drive. I don't have a CUDA graphics card, so am I not able to decode blu ray movies? Sorry but the blu ray transcoding process related to Megui is quite unclear to me.
Of course you are able to decode bluray movies without dgindexnv. You can use dg(avc)index for mpeg2/avc movies and open the vc-1 source file directly with directshowsource or dss2 if the proper filters are installed.
MeGUI is not the simplest GUI when it comes to default tasks like converting a bluray to a mkv/avchd image. For example you can have a look at staxrip or ripbot.
gwaitsi
6th January 2010, 07:07
Of course you are able to decode bluray movies without dgindexnv. You can use dg(avc)index for mpeg2/avc movies and open the vc-1 source file directly with directshowsource or dss2 if the proper filters are installed.
So i am trying to convert a vc1 in mkv with directshow. picture opens up in avs creator save it and picture opens up with avs is loaded into megui. start the queue and log file shows
"encoding started
standard output stream
stander error stream"
and marks the job complete.
Zathor
6th January 2010, 09:13
So i am trying to convert a vc1 in mkv with directshow. picture opens up in avs creator save it and picture opens up with avs is loaded into megui. start the queue and log file shows
"encoding started
standard output stream
stander error stream"
and marks the job complete.
If using Windows 7 (do not know if in this case the picture could be shown at all during preview):
http://forum.doom9.org/showthread.php?t=146910
If not please give us more details like the avs script or the complete log file. For me it is working with W7 x64 and DSS.
Maxim Maximov
6th January 2010, 13:25
AutoEncode "problem".
Encoded tracks can't be modifed (set up language etc) in adaptive muxer, i.e.:
http://img109.imageshack.us/img109/204/meguiam.th.gif (http://img109.imageshack.us/img109/204/meguiam.gif)
Of cource I can mux it after encoding, but it's not so comfy :)
p.s. megui 0.3.1.1060, win7 x86
lnatan25
6th January 2010, 14:20
Zathor, is the source code in SourceForge in sync with the latest version?
Zathor
6th January 2010, 14:48
Zathor, is the source code in SourceForge in sync with the latest version?
It is always in sync with the main build numbers (eg. the stable 1060 build) but there may be differences between this build and my development build.
Lambpete
6th January 2010, 14:56
I just updated to 1060 and noticed in the log: - (zathor) [SettingsForm] removed the unnecessary program paths
and: (zathor) [MeGUISettings] + [SettingsForm] all automatically installed tool paths cannot be changed anymore
:(
Is there any way you could add the x264 one back... I frequently change my build outside of the update server and this will be very annoying :(
thanks for all the work you have been doing :)
quantum5uicid3
6th January 2010, 16:35
I just updated to 1060 and noticed in the log: - (zathor) [SettingsForm] removed the unnecessary program paths
and: (zathor) [MeGUISettings] + [SettingsForm] all automatically installed tool paths cannot be changed anymore
:(
Is there any way you could add the x264 one back... I frequently change my build outside of the update server and this will be very annoying :(
thanks for all the work you have been doing :)
in case it makes life a pain the ass for zathor, an easy workaround would be to set x264 to not autoupdate and create a symlink to your desired directory. that's what i did.
MKLINK [[/D] | [/H] | [/J]] Link Target
/D Creates a directory symbolic link. Default is a file
symbolic link.
/H Creates a hard link instead of a symbolic link.
/J Creates a Directory Junction.
Link specifies the new symbolic link name.
Target specifies the path (relative or absolute) that the new link
refers to.
rtjnyoface
6th January 2010, 18:12
Of course you are able to decode bluray movies without dgindexnv. You can use dg(avc)index for mpeg2/avc movies and open the vc-1 source file directly with directshowsource or dss2 if the proper filters are installed.
I wasn't aware of Dgavc until yesterday. And I tried opening the files via directshow but I kept getting a directshow error. I asked here in the forum but didn't receive an answer.
MeGUI is not the simplest GUI when it comes to default tasks like converting a bluray to a mkv/avchd image. For example you can have a look at staxrip or ripbot.
I definitely wasn't looking for the most simple. I just hadn't done a blu ray encode until yesterday. I had just got a blu ray drive and started buying blu rays so I was entirely unaware of the process of encoding a blu ray. Unfortunately it took me the whole day (work may not be all THAT important ;)) just to figure it out when a few simple answers were all I needed. Could have saved an enormous amount of time (and gave me more time to pretend as though I was working ;)).
Zathor
6th January 2010, 23:02
Seems to be a problem with film detection. I have to confess that I have no experience with film because I live in PAL land... need to read a few things about it.
EDIT: Solution found. Edit your dgi file and replace "FO 2" with "FO 1" and "FPS 30000 / 1001" with "FPS 24000 / 1001". This will be added automatically like in the dgv with the next build.
- [AviSynthWindow] "source is anime" button will also be recognized if selected before analisys
- [ProfileImporter] added force film detection for DGIndexNV
fixed
gwaitsi
6th January 2010, 23:58
If using Windows 7 (do not know if in this case the picture could be shown at all during preview):
http://forum.doom9.org/showthread.php?t=146910
If not please give us more details like the avs script or the complete log file. For me it is working with W7 x64 and DSS.
yep, i have win7 x64. i tried playback using wmv9 and it was fine. i switched to libavcodec and the playback was choppy. i updated my k-lite to the latest version which resolved that.
i can play back through mkv or m2ts but not as raw vc1.
the m2ts causes AVS Script Creator to crash i.e. hangs trying to load.
the mkv has the same problem originally posted in Megui. Log says nothing really.
-[Information] Log for job5 (video, 00014.track_4113.avs -> 00014.track_4113.mkv)
--[Information] [6/01/2010 5:58:37 PM] Started handling job
--[Information] [6/01/2010 5:58:37 PM] Preprocessing
--[NoImage] Job commandline: "C:\Program Files (x86)\megui\tools\x264\vfw4x264.exe" --profile high --level 4.1 --preset fast --tune film --crf 21.0 --thread-input --b-adapt 2 --ref 4 --vbv-bufsize 50000 --vbv-maxrate 50000 --rc-lookahead 40 --me umh --direct auto --partitions p8x8,b8x8,i4x4,i8x8 --trellis 2 --sar 1591:1600 --output "C:\00014.track_4113.mkv" "C:\00014.track_4113.avs"
--[Information] [6/01/2010 5:58:38 PM] Encoding started
--[NoImage] Standard output stream
--[NoImage] Standard error stream
--[Information] [6/01/2010 5:58:38 PM] Job completed
rapscallion
7th January 2010, 00:01
FPS 24000 / 1001
Funny, but whenever I've used that in a AVS script, the Megui log shows 23.000 fps. The only way I get 23.976 is to use the floating point # in the script.
--[NoImage] Standard error stream
---[NoImage] avs [info]: 1280x720 @ 23.00 fps (20698 frames)
---[NoImage] x264 [info]: using SAR=1/1
---[NoImage] x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 Cache64
---[NoImage] x264 [info]: profile Main, level 4.1
--[Warning] Deleting aborted output
Barough
7th January 2010, 02:09
@ Zathor
Any chance that u could update the MediaInfo libraries to the latest version also, ie v0.7.27
ircopdd
7th January 2010, 02:30
Zathor Thanks! fixed
:thanks::thanks::D
HeadlessCow
7th January 2010, 07:23
Funny, but whenever I've used that in a AVS script, the Megui log shows 23.000 fps. The only way I get 23.976 is to use the floating point # in the script.
You should be able to use AssumeFPS(24000, 1001) or ChangeFPS/ConvertFPS in your avisynth script if you want to specify 23.976 fps using the fractional representation.
Zathor
7th January 2010, 10:19
@ Zathor
Any chance that u could update the MediaInfo libraries to the latest version also, ie v0.7.27
It will be updated with the next official build. Just for my information: why would you like to have it updated? The changelog seems to be more or less irrelevant for MeGUI.
Kurtnoise
7th January 2010, 12:44
You mean this (http://forum.doom9.org/showthread.php?t=141829)tool? As I recall the issue was there and it eventually disappeared. I think that in it's last iterations the issue was not present but it was when merged with MeGUI. Correct me if I'm wrong.
I meant the listview component. HDBDStreamExtractor and the form built in MeGUI use the same component (i.e the same code to create the interface). And the issue you described appears in both since the beginning. You have to ask to Greif about this...
@Zathor : what do you think about the Audio Interface that I made in my own branch (http://megui.svn.sourceforge.net/viewvc/megui/megui/branches/kurtnoise/) ? It's much clearer than the current one imo. Could be great to have it in the trunk or not ?
rapscallion
7th January 2010, 18:59
You should be able to use AssumeFPS(24000, 1001) or ChangeFPS/ConvertFPS in your avisynth script if you want to specify 23.976 fps using the fractional representation.
All 3 of those cause a script error.
Barough
7th January 2010, 19:41
It will be updated with the next official build. Just for my information: why would you like to have it updated? The changelog seems to be more or less irrelevant for MeGUI.
I noticed that a new version of it was released and u have been fixing/tweaking stuff in meGUI so i thought i would just ask
dstln
7th January 2010, 19:45
Not sure if you're accepting feature requests or not, but if so, would it be possible to add flac encoding support? I personally use flac a decent amount for archiving stuff from capture and would get good use out of batch converting from video files.
Also what is the link for the development servers?
SacredCultivator
7th January 2010, 20:45
@dstln: For update server, if anything it is the one listed on first post, "http://megui.org/auto/"
Although there isn't much to update at the moment, unless I am mistaken myself.
kool
7th January 2010, 22:47
Link for stable version is not working.
rapscallion
7th January 2010, 23:09
Site is down temporarily for maintenance.
Edit : Site back up, links are working
Cyber-Mav
8th January 2010, 01:57
is it possible to encode an xvid avi file directly into x264 using megui yet?
quantum5uicid3
8th January 2010, 02:49
without an avs u mean? no. after ffmpegsource2 is integrated in the git, hopefully. i already manually use ffmpegsource2 instead of directshow for all my video sources through avisynth and it works great.
nurbs
8th January 2010, 14:19
Zathor, there is a small bug in the DG Creator (0.3.1.1060). It displays a warning that no audio tracks are found even if the file you select is a .vc1 or .h264 file.
TDC.net
8th January 2010, 15:21
Zathor, there is a small bug in the DG Creator (0.3.1.1060). It displays a warning that no audio tracks are found even if the file you select is a .vc1 or .h264 file.
Is this warning really needed anyway?
I mean you see the audio disabled radio button anyway below.
I always demux the content of my blu-rays with hd stream extractor prior to transcoding to x264.
I use mkv format in stream extractor for video as h264 cannot be used for directshowsource.
I always get this warning although I know that there cannot be any audio file in this mkv.
Perhaps, it would be possible to add a checkbox to the warning "Never show again", so people can disable it that don't want to see it, others can leave it active.
Thanks
Raist
TDC.net
8th January 2010, 16:21
I meant the listview component. HDBDStreamExtractor and the form built in MeGUI use the same component (i.e the same code to create the interface). And the issue you described appears in both since the beginning. You have to ask to Greif about this...
I just tested Greif's version 0.6, there it is fixed.
So the fix was not ported to MeGUI.
Thanks
Raist
TDC.net
8th January 2010, 16:23
Regarding the temporary workers. I would like to change it that way that a temporary worker is closed automatically without question. Any objections arising?
It's still asking for closing the temporary workers here in build 0.3.1.1060.
Just to bring this back ontopic :helpful:
:thanks:
mcwups1
8th January 2010, 20:08
Just got this downloaded. I've always like MeGui, but last night I tried to convert a half of a basketball game from an HD-PVR recording, and it stopped with a few hundred frames left to transcode. (99.89%)
It happened twice actually since the download. Set it @7pm last night, then got up @ 3am and re-did the encode. Still, same results.
Any ideas?
XhmikosR
8th January 2010, 20:37
That's a x264 problem and not MeGUI's fault. You can try a build from x264.nl to see if the problem exists with that build too.
Blue_MiSfit
9th January 2010, 12:47
Nice job, gentlemen! MeGUI is quite usable now - and with a lot of spit 'n' polish compared to the old versions!
I've been using Lord_Mulder's simple launcher up until now, but this is quite useful when I need a queue ;)
~MiSfit
Zathor
9th January 2010, 12:54
With the stable build knocking on the door I will not add or change things at the moment beside main bugs. The only other thing is to add support for the new DGIndexNV build 2001 which has a new cli syntax. This seems to be a bigger change because the film handling is moved from the dgi project file to the Avisynth DGSource call but I think it is necessary to add this to the stable build. Therefore I will release (hopefully only one) last dev build before going public.
Additionally I would like to change the version number schema used. With every release to the stable branch I will increase the build number (0.3.1.1060) and set the revision to 0 (0.3.2.0). With every development build I will increase the revision while not changing the build number. With this schema I am able to push out updates to the development server for every small fix. The changelog will include updates for every revision but as soon as a new build number is released I will merge these revision entries. The major and minor version numbers (0.3.1.1060) will not increase at all. Any other suggestions/ideas?
And now to some postings of the last days:
iirc, mainly AAC & subtitles streams (SRT,SSA,VobSub)...
Thanks, the test is still outstanding.
AutoEncode "problem".
Encoded tracks can't be modifed (set up language etc) in adaptive muxer[...]Of cource I can mux it after encoding, but it's not so comfy :)
Please add this as a feature request:
http://sourceforge.net/tracker/?atid=798479&group_id=156112
It is not on my list for the next few days and if not added there it may be lost.
It's still asking for closing the temporary workers here in build 0.3.1.1060.
Just to bring this back ontopic :helpful:
I agree that a temporary worker should be closed automatically without question because it is a temporary worker. Nevertheless I will not add/change it before the stable build and therefore please open a feature request or you have to keep up reminding me.
I noticed that a new version of it [mediainfo] was released and u have been fixing/tweaking stuff in meGUI so i thought i would just ask
Thanks, I have thought that there may be an important fix because of your posting. @all: Please carry on posting new versions of mediainfo or any other tool we are using in MeGUI.
Zathor, there is a small bug in the DG Creator (0.3.1.1060). It displays a warning that no audio tracks are found even if the file you select is a .vc1 or .h264 file.
I would like to remove it completely and independently of the source file. Nevertheless this will not be changed in the next days so please open a feature request (I think it is no bug because there isn't any audio information in these files and therefore the message is correct).
Not sure if you're accepting feature requests or not, but if so, would it be possible to add flac encoding support? I personally use flac a decent amount for archiving stuff from capture and would get good use out of batch converting from video files.
Thanks, new suggestions are welcome. Please open a feature request at sourceforge.
You mean this (http://forum.doom9.org/showthread.php?t=141829)tool? As I recall the issue was there and it eventually disappeared. I think that in it's last iterations the issue was not present but it was when merged with MeGUI. Correct me if I'm wrong.
Thanks, I will have a look at this problem - but very likely not in the next days.
@Zathor : what do you think about the Audio Interface that I made in my own branch (http://megui.svn.sourceforge.net/viewvc/megui/megui/branches/kurtnoise/) ? It's much clearer than the current one imo. Could be great to have it in the trunk or not ?
Thank you very much for your hint. I didn't know that you have some secrets there :) Sadly I had no time to have a look at it but I will add it after the stable build has been released.
saint-francis
9th January 2010, 15:13
Thanks, I will have a look at this problem - but very likely not in the next days.
Thanks for any effort at all. It's certainly not a show stopper so please take your time. I also posted about it to Greif in the original thread for the tool.
Thank you for all of your hard work.
Lambpete
9th January 2010, 15:56
That's a x264 problem and not MeGUI's fault. You can try a build from x264.nl to see if the problem exists with that build too.
except you can't set the filepath for x264 anymore :(
Any chance on getting this added back in Zathor ?
( I know there are workarounds.. but if it isn't too much trouble to bring that back it would be very useful )
XhmikosR
9th January 2010, 16:09
There are pros and cons. In my opinion, it's better the way it is now. Just replace x264.exe.
TDC.net
9th January 2010, 16:48
There are pros and cons. In my opinion, it's better the way it is now. Just replace x264.exe.
I second that, leave it fixed.
TDC.net
9th January 2010, 16:49
Thanks Zathor for all your improvements, I will create these feature requests.
Thanks again
Raist
lnatan25
9th January 2010, 17:58
There are pros and cons. In my opinion, it's better the way it is now.
Any option that takes control from the user cannot be considered a pro in any way.:rolleyes:
Zathor
9th January 2010, 18:12
except you can't set the filepath for x264 anymore :(
Any chance on getting this added back in Zathor ?
( I know there are workarounds.. but if it isn't too much trouble to bring that back it would be very useful )
As long as x264 is one of the automatic downloaded tools I will not readd this feature. It has not been an easy decision but I made this decision. Please understand that I will not respond anymore to this request until someone comes up with really good arguments.
Of course you can and should discuss this further! I love to read your opinions.
nakTT
9th January 2010, 18:45
There are pros and cons. In my opinion, it's better the way it is now. Just replace x264.exe.
I second that. IMHO the way it is now is better.
quantum5uicid3
9th January 2010, 19:02
i think mklink (http://technet.microsoft.com/en-us/library/cc753194%28WS.10%29.aspx)on vista/7 or junction (http://technet.microsoft.com/en-us/sysinternals/bb896768.aspx) on 2000/xp is a simple enough solution.
TDC.net
9th January 2010, 19:12
Any option that takes control from the user cannot be considered a pro in any way.:rolleyes:
Yes, it can!
Newbies will have less problems that way!
:p
quantum5uicid3
9th January 2010, 19:31
i have a feature request. can u add a constant quality mode that also creates the --pass 1/--slowfirstpass stats file for those instances that crf produces an undesirable result. i tried to do it in the custom command line, but can't figure out how to take advantage of the variable filename ".stats" file megui creates in the same directory as source.
Lambpete
9th January 2010, 23:23
As long as x264 is one of the automatic downloaded tools I will not readd this feature. It has not been an easy decision but I made this decision. Please understand that I will not respond anymore to this request until someone comes up with really good arguments.
Of course you can and should discuss this further! I love to read your opinions.
Maybe i missed something along the way, but what was the reason for its removal? was it just that it is automatically updated?
I personally have not used any of the automatically updated x264 builds for over a year.
I can respect that some people like it the way it is now.. but can someone explain the advantage of having to manually overwrite your x264.exe file instead of just updating the path?
Any option that takes control from the user cannot be considered a pro in any way.
I agree completely.
Yes, it can!
Newbies will have less problems that way!
I don't see how having the option to set your x264 path poses a problem to newbies learning to encode. I have overseen many the newbie through the process and that is certainly not one of the issues which has ever popped up.
And why should megui be catering to n00bs anyway?
I thought that's what handbrake was for? :P
( which coincidentally does force its users to use their custom x264 build which cannot be overwritten or updated )
quantum5uicid3
9th January 2010, 23:39
complications arise from UAC, a process starting processes outside of the program directory needs escalation i think. so not really so much a noob issue, but the unneccsary need to run megui escalated. don't be afraid of symlinks, they are your friend.
aegisofrime
10th January 2010, 13:42
I have an extremely puzzling problem that started recently, after I upgraded my Windows 7 RC to the final retail.
I can open .avs scripts, the preview window comes up just fine. After I enqueue and start the job, the job instantly ends with an error. I check the log and the only thing is says is "Standard error stream"
The same .avs script encodes fine with Lord Mulder's simple x64 launcher, so I don't think the problem lies with Avisynth.
I have tried uninstalling MeGUI, installing and updating to build 1060 but that doesn't solve it. :(
Zathor
10th January 2010, 13:49
I have an extremely puzzling problem that started recently, after I upgraded my Windows 7 RC to the final retail.
I can open .avs scripts, the preview window comes up just fine. After I enqueue and start the job, the job instantly ends with an error. I check the log and the only thing is says is "Standard error stream"
The same .avs script encodes fine with Lord Mulder's simple x64 launcher, so I don't think the problem lies with Avisynth.
I have tried uninstalling MeGUI, installing and updating to build 1060 but that doesn't solve it. :(
Please post your log, avs file and the source information.
MOS-Marauder
10th January 2010, 15:34
@Zathor... I found out why MeGui & DGNVTools crashed here.... The Nvidia Driver dont like it that i have all Memory Slots Occupied. Removing one solved it. (RAM is still OK..also the Removed one)
Chris
stax76
10th January 2010, 19:56
@Zathor... I found out why MeGui & DGNVTools crashed here.... The Nvidia Driver dont like it that i have all Memory Slots Occupied. Removing one solved it.
Interesting, was it the same or different memory, how many slots do you have?
MOS-Marauder
10th January 2010, 20:09
Interesting, was it the same or different memory, how many slots do you have?
4 Slots and all with the Same Riggs. 4x 2 GB Chaintech Apogee DDR2 Ram.
Chris
Zathor
10th January 2010, 21:37
Interesting, I have also the crashes and all my slots are occupied (2x2GB + 2x1GB DDR2)
Btw I have just released build 0.3.1.1061 to the dev update server.
- added force film and DAR detection for DGIndexNV
- added support for new DGIndexNV (requires build 2001 or higher)
- update MediaInfo library and its wrapper to the latest release (0.7.27)
MuLTiTaSK
10th January 2010, 21:52
@Zathor
regarding the DGIndexNV crashes does MeGUI use DGSource("") with CUVIDServer or DGMulitSource("")?
rapscallion
10th January 2010, 22:06
Btw I have just released build 0.3.1.1061 to the dev update server.
Looks like you're getting close to a new stable build ?
I notice that the AVCHD presets have been added, thanks.
nurbs
10th January 2010, 22:33
regarding the DGIndexNV crashes does MeGUI use DGSource("") with CUVIDServer or DGMulitSource("")?
It still uses DGSource and autostarts the CUVID Server.
Zathor
10th January 2010, 22:42
@Zathor
regarding the DGIndexNV crashes does MeGUI use DGSource("") with CUVIDServer or DGMulitSource("")?
By default it uses DGSource (more stable) but you can switch to DGMultiSource in the settings.
hajj_3
10th January 2010, 23:46
please can you add 1.778 to the DAR list as that is what tv shows air in, i have to manually add this each time i upgrade a build of megui:(
also is it possible to let it upscale for example, tv shows that air in 544x576, can you we not make them 720x400 when we encode them as the highest resolution i can choose is 544x320 which is poor, xvid will let you choose 720x400.
thanks zathor, you're doing a great job!
MOS-Marauder
11th January 2010, 00:07
By default it uses DGSource (more stable) but you can switch to DGMultiSource in the settings.
Where ? (Switch to DGMultiSource...)
Chris
nurbs
11th January 2010, 00:19
options->settings->external programs settings-> uncheck "use cuvid server"
MOS-Marauder
11th January 2010, 00:53
Ah Unchecking the Server uses Multi? .. Go and checking it...
Chris
Triccotracco
11th January 2010, 08:17
please can you add 1.778 to the DAR list as that is what tv shows air in, i have to manually add this each time i upgrade a build of megui:(
!
quoted!
also DAR 1.333 is also useful
:)
lucassp
11th January 2010, 11:47
Why are the new DXVA profiles unrestricted? Thanks!
quantum5uicid3
11th January 2010, 16:40
because your video card will play unrestricted with 16ref and 16bframes np
i'll be more specific,
1. i found no restriction info in the microsoft api doumentation here, although most of it is beyond my level.
http://www.microsoft.com/downloads/details.aspx?FamilyID=3d1c290b-310b-4ea2-bf76-714063a6d7a6&DisplayLang=en
2. nvidia has certainly solved the limitations that existed previously in all their cards supporting h264 decodinng (8400GS+, pretty much i think) by driver fixes
3. ive found no credible info that limitations still exist that aren't device specific.
MuLTiTaSK
11th January 2010, 18:40
@Zathor
:eek: great job you've done with MeGUI already seems like a different program awesome coding
script creator worked pretty flawless with DGIndexNV for me with no problems i have all memory slots on mobo filled so it might be a different source for the crashes reported
only way i could get MeGUI to crash was to use AviSynth cropping aside Nvidia Resizer only then preview window would get mental and crashes would occur note that MeGUI does'nt always crash doing this:)
System
MeGUI Version : 0.3.1.1061
OS : Windows Seven Ultimate Edition x64 (6.1.0.7600)
Latest .Net Framework installed : 3.5 SP1 (3.5.30729.4926)
Avisynth Version : 2.5.8.5
Source
Format : VC-1
Format profile : AP@L3
Codec ID : WVC1
Codec ID/Hint : Microsoft
Duration : 3h 6mn
Bit rate : 18.1 Mbps
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate : 23.976 fps
Resolution : 8 bits
Colorimetry : 4:2:0
Scan type : Progressive
Bits/(Pixel*Frame) : 0.364
Stream size : 23.6 GiB (98%)
AviSynth resizing still frame (works)
http://img51.imageshack.us/img51/5154/ss20100111110557.th.jpg (http://img51.imageshack.us/i/ss20100111110557.jpg/)
AviSynth resizing playing (works)
http://img15.imageshack.us/img15/9808/ss20100111111103.th.jpg (http://img15.imageshack.us/i/ss20100111111103.jpg/)
Script
LoadPlugin("I:\MeGUI\tools\dgindexnv\DGMultiDecodeNV.dll")
DGMultiSource("J:\MeGUI\Watchmen.dgi",fieldop=0)
#deinterlace
crop( 0, 140, 0, -140)
Spline64Resize(1280,528) # Spline64 (Sharp)
LoadPlugin("I:\MeGUI\tools\avisynth_plugin\UnDot.dll")
Undot() # Minimal Noise
__film = last
__t0 = __film.trim(134126, 140362)
__t0
job
[Information] Log for job19 (video, test.avs -> test.264)
-[Information] [1/11/2010 11:25:15 AM] Started handling job
-[Information] [1/11/2010 11:25:15 AM] Preprocessing
-[NoImage] Job commandline: "I:\MeGUI\tools\x264\vfw4x264.exe" --profile high --level 4.1 --preset slower --tune film --crf 18.5 --thread-input --vbv-maxrate 31250 --sar 1:1 --aud --output "J:\megui\test.264" "J:\MeGUI\test.avs"
-[Information] [1/11/2010 11:25:17 AM] Encoding started
-[NoImage] Standard output stream
-[NoImage] Standard error stream
--[NoImage] x264 [info]: 1280x528 @ 23.98 fps
--[NoImage] x264 [info]: using SAR=1/1
--[NoImage] x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 FastShuffle SSE4.2
--[NoImage] x264 [warning]: VBV maxrate specified, but no bufsize.
--[NoImage] x264 [info]: profile High, level 4.1
--[NoImage]
--[NoImage] x264 [info]: frame I:97 Avg QP:14.85 size: 52150
--[NoImage] x264 [info]: frame P:2226 Avg QP:18.02 size: 19160
--[NoImage] x264 [info]: frame B:3914 Avg QP:20.20 size: 6300
--[NoImage] x264 [info]: consecutive B-frames: 4.1% 17.6% 45.2% 33.0%
--[NoImage] x264 [info]: mb I I16..4: 14.6% 73.0% 12.4%
--[NoImage] x264 [info]: mb P I16..4: 4.7% 9.4% 0.9% P16..4: 45.3% 13.4% 10.3% 0.2% 0.2% skip:15.8%
--[NoImage] x264 [info]: mb B I16..4: 0.2% 1.0% 0.2% B16..8: 40.9% 1.1% 1.3% direct: 5.6% skip:49.7% L0:43.8% L1:49.8% BI: 6.3%
--[NoImage] x264 [info]: 8x8 transform intra:65.7% inter:67.9%
--[NoImage] x264 [info]: direct mvs spatial:98.5% temporal:1.5%
--[NoImage] x264 [info]: coded y,uvDC,uvAC intra: 63.2% 72.5% 43.8% inter: 19.4% 19.3% 1.6%
--[NoImage] x264 [info]: i16 v,h,dc,p: 67% 10% 7% 17%
--[NoImage] x264 [info]: i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 9% 8% 8% 10% 14% 12% 14% 11% 14%
--[NoImage] x264 [info]: i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 8% 8% 6% 10% 16% 13% 14% 11% 14%
--[NoImage] x264 [info]: Weighted P-Frames: Y:3.9%
--[NoImage] x264 [info]: ref P L0: 51.6% 14.0% 13.9% 6.1% 4.8% 3.6% 2.8% 1.6% 1.5% 0.1%
--[NoImage] x264 [info]: ref B L0: 75.5% 10.9% 5.8% 2.8% 2.2% 1.6% 1.2%
--[NoImage] x264 [info]: kb/s:2225.50
--[NoImage] encoded 6237 frames, 12.54 fps, 2225.50 kb/s
-[Information] Final statistics
--[NoImage] Constant Quality Mode: Quality 18 computed...
--[NoImage] Video Bitrate Obtained (approximate): 2225 kbit/s
-[Information] [1/11/2010 11:33:40 AM] Postprocessing
-[Information] [1/11/2010 11:33:40 AM] Job completed
btw could you share info with stax76 on how you got them working together or any findings you made along the way that could help him accomplish the same feat with StaxRip thanks again
keep up the great coding ;)
MuLTiTaSK
11th January 2010, 18:49
@Zathor
Nvidia Resizer no cropping still frame (works)
http://img687.imageshack.us/img687/5481/ss20100111124241.th.jpg (http://img687.imageshack.us/i/ss20100111124241.jpg/)
Nvidia Resizer no cropping playing (works)
http://img687.imageshack.us/img687/12/ss20100111124324.th.jpg (http://img687.imageshack.us/i/ss20100111124324.jpg/)
Nvidia Resizer cropping still frame (crash)
http://img519.imageshack.us/img519/1567/ss20100111124434.th.jpg (http://img519.imageshack.us/i/ss20100111124434.jpg/)
Kurtnoise
11th January 2010, 19:33
Please, resize your pictures or post only the link...
MuLTiTaSK
11th January 2010, 19:55
@Kurtnoise
done sorry about that:cool:
Zathor
11th January 2010, 21:56
btw could you share info with stax76 on how you got them working together or any findings you made along the way that could help him accomplish the same feat with StaxRip thanks again
We talked already about the findings. The problem seems to be that MeGUI (and StaxRip as I understand) are opening a lot of avisynth scripts internal - one after another but in a quick row. The only change from my side inspired by neuron2 was to add a small delay after one avs script is closed and before a new one is opened. This reduced the likelihood of crashes but they are still there. The CUVIDServer is more or less stable (I only get it to crash sometimes during the source analyze) and DGMultiSource is crashing for me during adding a already created avs file as a new job. But not always - it is not predictable. A solution could be to change the way MeGUI handles avs files in order to get information out of them (frames, size, ....) so that it is only needed to open the file once. That’s the reason I believe why some tools have no problems in opening and encoding these files. But to change this in MeGUI would be a huge task.
@all: Thanks for the large amount of bug reports and feature request at the sourceforge project page during the last two days. Ok, bugs are not good at all but it is great that you share your findings.
EDIT:
@Zathor
:eek: great job you've done with MeGUI already seems like a different program awesome coding
Thanks but that is not fair at all. The other developers like Kurtnoise had the hard job to develop the program and functions from scratch. I am only doing small changes here and there. So a big thanks to all of them!
Capsbackup
12th January 2010, 05:08
Hopefully I didn't miss this, or if it hasn't been discussed, how do you import the latest presets?
When I start MeGui, it asks if I want to update, and I say yes. It then updates several files, including the option to select the latest presets, but the pop up window that says MeGui needs to restart is selected before I can check all the presets to import.
I seem to remember from older versions of MeGui that you had to either cancel or select the presets before the pop up box to restart MeGui was displayed, thereby avoiding the present problem of restarting MeGui before selecting the presets.
This may just be a cosmetic issue, or maybe its just me, but I have now missed the last update option to import the latest presets on both of my computers.:o
rapscallion
12th January 2010, 05:52
Click on Options/update/...select preset collections.
check box "Tx264" and then click "update. Alternately, right click on Tx264 and select "force reinstall". Then just check the presets that you want to update. Then click "update". Done.
Capsbackup
12th January 2010, 06:14
Click on Options/update/...select preset collections.
check box "Tx264" and then click "update. Alternately, right click on Tx264 and select "force reinstall". Then just check the presets that you want to update. Then click "update". Done.
Thank you rapscallion, much appreciated. :)
AnarkiNet
12th January 2010, 17:16
Just updated to 0.3.1.1061 and DGDecNV reports "invalid license file" when I try and run it from megui but when i just double click the DGIndexNV exe it works fine.
rack04
12th January 2010, 19:00
Just updated to 0.3.1.1061 and DGDecNV reports "invalid license file" when I try and run it from megui but when i just double click the DGIndexNV exe it works fine.
Have you copied your license file to the directory MeGUI saved DGIndexNV?
Richardw322
15th January 2010, 15:50
Just a dumb question here. I have been using Ver 1051 (updated till 11-19) with Vista to now and it has been working fine. Problem is I want to clean install Win 7 on this machine. Can I just download the file from msg one and let it update or do I have to install an older (ver 1056) one first? I read the whole thread, but my head is spinning here. I keep seeing references to updating from a previous version.
Lyle_JP
15th January 2010, 17:59
Just got this downloaded. I've always like MeGui, but last night I tried to convert a half of a basketball game from an HD-PVR recording, and it stopped with a few hundred frames left to transcode. (99.89%)
It happened twice actually since the download. Set it @7pm last night, then got up @ 3am and re-did the encode. Still, same results.
Any ideas?
Sounds like a Jeeb's build problem (x264). No offense to Jeeb, but roughly 75% of his builds crash on me (usually at 99.99%, but sometimes just because I switch user and switch back). The ones from x264.nl are always rock solid. I've had good luck with Techouse's gcc builds as well (if you need the interlaced patch).
rack04
15th January 2010, 19:35
Does the MeGUI avisynth script creator default to fieldop=1 or does it analyze the output and determine the pulldown?
rapscallion
15th January 2010, 20:07
Sounds like a Jeeb's build problem (x264). No offense to Jeeb, but roughly 75% of his builds crash on me (usually at 99.99%, but sometimes just because I switch user and switch back). The ones from x264.nl are always rock solid. I've had good luck with Techouse's gcc builds as well (if you need the interlaced patch).
Your post is timely because last night I tried a test encode of a 1080i source (1061/jeebs 1376 /x264 AVCHD-2 pass preset) and got this warning in the error stream :
[NoImage] Standard error stream
---[NoImage] avs [info]: 1920x1080 @ 29.97 fps (17981 frames)
---[NoImage] x264 [warning]: interlace + weightp is not implemented
I've read on the Wiki that Megui is inefficient for interlace encodes so, in the past, I've unchecled the interlace box and encoded progressive.(ie 1920x1080i to 1280x720p)
What does the TH Interlace patch do and am I better off encoding with his build and do interlace or encode progressive ?
zamwow
15th January 2010, 21:06
Could you guys take the misc tab in x264 configuration out of the advanced settings? (and merge it with the main tab or something)
Lyle_JP
15th January 2010, 22:15
I think all the patch does is (blah blah blah... deleted)
Nevermind. The patch just "converts" 23.976 progressive HD material to 29.970 interlaced by flagging the progressive frames with pulldown info. This makes the stream compliant with the HD-DVD spec, among others (I guess Scenarist needs this too).
I haven't had any problems using weightp with interlaced encoding (but the only encoding I did was 480i and I only use it in blind mode).
rapscallion
15th January 2010, 22:20
From my post : "1061/jeebs 1376 /x264 AVCHD-2 pass preset"
Also, I'm encoding to rawavc, if that makea any difference.
Btw the encode completed successfully and the vid looks fine, but I'm still curious why I got that warning/error ?
Edit: wow! 16 posts in 6 years Lyle, you really are a post whore :)
rapscallion
15th January 2010, 23:11
I think all the patch does is (blah blah blah... deleted)
Nevermind. The patch just "converts" 23.976 progressive HD material to 29.970 interlaced by flagging the progressive frames with pulldown info. This makes the stream compliant with the HD-DVD spec, among others (I guess Scenarist needs this too).
I haven't had any problems using weightp with interlaced encoding (but the only encoding I did was 480i and I only use it in blind mode).
OK, Lyle thanks for the update. In the interim, I found this post in answer to interlace discussion:
Jeeb (http://x264.fushizen.eu/) or techouse (http://x264mirror.tk/) builds.
I'd suggest using 1352 since there is some bug reports from 1353/1354. Also if you use 1320+ you'll want to use x264 --weightp 0 to avoid video corruption in some standalones and coreavc, and you also won't lose 10-15% speed.
So, for the time being, I'm going to disable weightp as my encodes are for Standalone AVCHD.
However, per the warning , x264 disabled it anyway.
deets
15th January 2010, 23:14
im having major issues on DXVA playback using unrestricted and then "very slow" preset.
playback has issues with some DXVA decoders, so i set the level to 4.1 and all is ok.
Lyle_JP
16th January 2010, 00:53
OK, Lyle thanks for the update. In the interim, I found this post in answer to interlace discussion:
So, for the time being, I'm going to disable weightp as my encodes are for Standalone AVCHD.
However, per the warning , x264 disabled it anyway.
That issue has to do with the extra reference frames that --weightp creates; it puts the encoding over the maximum reference frames that some standalones can handle. But this can be easily worked around by lowering the --ref value. For example, if your playback device limits you to 5 reference frames, use --ref 3 with --weightp 2 or --ref 4 with --weightp 1 (which is my preference since it seems to behave better with the PS3).
quantum5uicid3
16th January 2010, 01:32
im having major issues on DXVA playback using unrestricted and then "very slow" preset.
playback has issues with some DXVA decoders, so i set the level to 4.1 and all is ok.
what video card?
Nikolausr
16th January 2010, 11:08
I just downloaded this patched build and ran the updates off of the development server. The first thing I tried to encode didn't work.
[Information] Log
-[Information] Versions
--[NoImage] MeGUI Version : 0.3.1.1061
--[NoImage] OS : Windows Seven x64 (6.1.0.7600)
--[NoImage] Latest .Net Framework installed : 3.5 SP1 (3.5.30729.4926)
--[NoImage] Avisynth Version : 2.5.8.5
-[Information] Log for job1 (video, VTS_05_1.avs -> )
--[Information] [1/16/2010 2:01:21 AM] Started handling job
--[Information] [1/16/2010 2:01:21 AM] Preprocessing
--[NoImage] Job commandline: "C:\Users\Nick\Downloads\Unsorted\megui\tools\x264\vfw4x264.exe" --level 4.1 --preset veryslow --tune film --pass 1 --bitrate 500 --stats "H:\Misc\Ripped Movies\IDIOCRACY_SIDEA\VIDEO_TS\VTS_05_1.stats" --thread-input --bframes 3 --ref 1 --me hex --subme 1 --partitions none --no-8x8dct --trellis 0 --sar 1:1 --output NUL "H:\Misc\Ripped Movies\IDIOCRACY_SIDEA\VIDEO_TS\VTS_05_1.avs"
--[Information] [1/16/2010 2:01:21 AM] Encoding started
--[NoImage] Standard output stream
--[NoImage] Standard error stream
--[Information] [1/16/2010 2:01:21 AM] Job completed
Zathor
16th January 2010, 12:40
I just downloaded this patched build and ran the updates off of the development server. The first thing I tried to encode didn't work.
Please try another x264 build like this one:
http://komisar.gin.by/old/1376/x264.1376.generic.x86_64.exe
Copy it to "C:\Users\Nick\Downloads\Unsorted\megui\tools\x264" and rename it to x264_64.exe.
deets
16th January 2010, 13:38
what video card?
GTX 260
on some decoders it either stops after a second, on others it just pixelates to the moon.
this is only with the "very slow" profile, the other profiles work fine on unrestricted....
Zathor
16th January 2010, 13:49
Does the MeGUI avisynth script creator default to fieldop=1 or does it analyze the output and determine the pulldown?
If the FILM value in DGIndexNV is above the threshold in the MeGUI settings fieldop will be 1 (force film) - in all other cases it will default to 0 (honour pulldown).
EDIT: Sorry, wrong values...
Boo
16th January 2010, 15:22
It would be nice to have a droplist with --sar values somewhere.
10:11, 1:1, 12:11, 40:33, 4:3, 15:11, 16:11, 3:2, 160:99, 18:11, 20:11, 64:33, 2:1, 24:11, 80:33, 32:11
In the x264 settings main tab would be nice
Zathor
16th January 2010, 16:42
I have uploaded build 0.3.2.0 to the stable + development server. There are no changes compared to 0.3.1.1061.
Triccotracco
16th January 2010, 18:14
I have uploaded build 0.3.2.0 to the stable + development server. There are no changes compared to 0.3.1.1061.
Good luck Zathor! Thank you very much for all!
quantum5uicid3
16th January 2010, 20:42
GTX 260
on some decoders it either stops after a second, on others it just pixelates to the moon.
this is only with the "very slow" profile, the other profiles work fine on unrestricted....
OS? DirectX up to date? Nvidia Drivers latest stable? what decoders?
I just downloaded this patched build and ran the updates off of the development server. The first thing I tried to encode didn't work.
can u open and play the avs in mpc?
carlo_0000
17th January 2010, 01:13
hello
i update megui today from 0.3.1.1051 to 0.3.2.0
[Warning] Log
-[Information] Versions
--[NoImage] MeGUI Version : 0.3.2.0
--[NoImage] OS : Windows XP Professional x86 SP3 (5.1.196608.2600)
--[NoImage] Latest .Net Framework installed : 3.5 (3.5.30729.01)
--[NoImage] Avisynth Version : 2.5.8.5
-[Information] Hardware
--[NoImage] CPU : AMD Processor model unknown
-[Warning] Log for job1 (video, Terminator.Salvation.1080p.avs -> )
--[Information] [17/01/2010 1:02:22] Started handling job
--[Information] [17/01/2010 1:02:22] Preprocessing
--[NoImage] Job commandline: "C:\Program Files\megui\tools\x264\x264.exe" --profile high --level 4.1 --preset placebo --pass 1 --bitrate 9000 --stats "K:\Terminator.Salvation.1080p.stats" --slow-firstpass --thread-input --deblock -1:-1 --keyint 200 --min-keyint 22 --vbv-bufsize 50000 --vbv-maxrate 50000 --no-dct-decimate --sar 1:1 --output NUL "K:\Terminator.Salvation.1080p.avs"
--[Information] [17/01/2010 1:02:23] Encoding started
--[NoImage] Standard output stream
--[Warning] Deleting aborted output
---[NoImage] Delete aborted ouptut set: True
---[NoImage] File to delete
---[Warning] Error deleting file
----[NoImage] Exception message: Le chemin d'accès n'a pas une forme conforme.
----[NoImage] Stacktrace
-----[NoImage] à System.IO.Path.NormalizePathFast(String path, Boolean fullCheck)
-----[NoImage] à System.IO.Path.NormalizePath(String path, Boolean fullCheck)
-----[NoImage] à System.IO.Path.GetFullPathInternal(String path)
-----[NoImage] à System.IO.File.Delete(String path)
-----[NoImage] à MeGUI.core.gui.JobWorker.markJobAborted()
----[NoImage] Inner exception: null
--[NoImage] Standard error stream
--[Information] [17/01/2010 1:03:39] Job completed
--[Information] [17/01/2010 1:03:40] Current job was aborted
-[Warning] Log for job1 (video, Terminator.Salvation.1080p.avs -> )
--[Information] [17/01/2010 1:04:08] Started handling job
--[Information] [17/01/2010 1:04:08] Preprocessing
--[NoImage] Job commandline: "C:\Program Files\megui\tools\x264\x264.exe" --profile high --level 4.1 --preset placebo --pass 1 --bitrate 9000 --stats "K:\Terminator.Salvation.1080p.stats" --slow-firstpass --thread-input --threads 4 --deblock -1:-1 --keyint 200 --min-keyint 22 --vbv-bufsize 50000 --vbv-maxrate 50000 --no-dct-decimate --sar 1:1 --output NUL "K:\Terminator.Salvation.1080p.avs"
--[Information] [17/01/2010 1:04:10] Encoding started
--[NoImage] Standard output stream
--[Warning] Deleting aborted output
---[NoImage] Delete aborted ouptut set: True
---[NoImage] File to delete
---[Warning] Error deleting file
----[NoImage] Exception message: Le chemin d'accès n'a pas une forme conforme.
----[NoImage] Stacktrace
-----[NoImage] à System.IO.Path.NormalizePathFast(String path, Boolean fullCheck)
-----[NoImage] à System.IO.Path.NormalizePath(String path, Boolean fullCheck)
-----[NoImage] à System.IO.Path.GetFullPathInternal(String path)
-----[NoImage] à System.IO.File.Delete(String path)
-----[NoImage] à MeGUI.core.gui.JobWorker.markJobAborted()
----[NoImage] Inner exception: null
--[NoImage] Standard error stream
--[Information] [17/01/2010 1:09:42] Job completed
--[Information] [17/01/2010 1:09:44] Current job was aborted
but there is some sort of problem
the computer is very slow that it s like if i m on a p2 200mhz under xp :)
if i start my queud job
when it start with the 1st pass, there must be something wrong
only the hard drive is working (led is completly red)
cpu is far from full speed
and it completly slowdown the computer that i can do nothing else
i try small videos 3-4 minute not hd
and that it s work like before (but 1st pass same to be slower that old 1)
thank for help
http://perso.latribu.com/tribu/jpg/meguibug.JPG
ok i encoded a small one
but it s look corrupt mpchc (with coreavc)
i tested with vlc it s look ok but it s olso corrupt a few seconds when seeking in the video
i tested with mpchc and powerdvd8 it s ok too (but not with dxva)
something wrong with coreavc
http://perso.latribu.com/tribu/DjShog-Live4Music(aac2.0)V.jpg
--[Information] [17/01/2010 1:27:47] Job completed
-[Information] Log for job6 (video, Dj Shog - Live 4 Music.avs -> )
--[Information] [17/01/2010 1:28:51] Started handling job
--[Information] [17/01/2010 1:28:51] Preprocessing
--[NoImage] Job commandline: "C:\Program Files\megui\tools\x264\x264.exe" --profile high --level 3.1 --preset placebo --pass 1 --bitrate 1440 --stats "K:\Dj Shog - Live 4 Music.stats" --thread-input --deblock -1:-1 --vbv-bufsize 14000 --vbv-maxrate 17500 --no-dct-decimate --sar 1:1 --output NUL "K:\Dj Shog - Live 4 Music.avs"
--[Information] [17/01/2010 1:28:51] Encoding started
--[NoImage] Standard output stream
--[NoImage] Standard error stream
---[NoImage] avs [info]: 720x320 @ 29.97 fps (6755 frames)
---[NoImage] x264 [info]: using SAR=1/1
---[NoImage] x264 [info]: using cpu capabilities: MMX2 SSE2Fast FastShuffle SSEMisalign LZCNT
---[NoImage] x264 [info]: profile High, level 3.1
---[NoImage]
---[NoImage] x264 [info]: frame I:34 Avg QP:18.32 size: 15066
---[NoImage] x264 [info]: frame P:2565 Avg QP:21.80 size: 9341
---[NoImage] x264 [info]: frame B:4156 Avg QP:23.19 size: 4247
---[NoImage] x264 [info]: consecutive B-frames: 9.3% 23.6% 28.8% 13.7% 3.6% 12.9% 8.1% 0.0% 0.0% 0.0% 0.0% 0.0% 0.0% 0.0% 0.0% 0.0% 0.0%
---[NoImage] x264 [info]: mb I I16..4: 4.5% 90.2% 5.4%
---[NoImage] x264 [info]: mb P I16..4: 4.0% 33.9% 1.8% P16..4: 39.2% 15.3% 4.9% 0.1% 0.0% skip: 0.8%
---[NoImage] x264 [info]: mb B I16..4: 0.3% 2.2% 0.1% B16..8: 42.7% 1.2% 1.6% direct:20.3% skip:31.6% L0:47.3% L1:47.3% BI: 5.4%
---[NoImage] x264 [info]: final ratefactor: 19.90
---[NoImage] x264 [info]: 8x8 transform intra:85.7% inter:92.9%
---[NoImage] x264 [info]: direct mvs spatial:99.9% temporal:0.1%
---[NoImage] x264 [info]: coded y,uvDC,uvAC intra: 82.0% 86.2% 36.2% inter: 50.5% 62.3% 9.7%
---[NoImage] x264 [info]: i16 v,h,dc,p: 42% 30% 7% 21%
---[NoImage] x264 [info]: i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 7% 7% 4% 11% 15% 15% 14% 13% 14%
---[NoImage] x264 [info]: i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 8% 9% 2% 10% 15% 15% 16% 11% 13%
---[NoImage] x264 [info]: Weighted P-Frames: Y:25.6%
---[NoImage] x264 [info]: ref P L0: 37.4% 13.5% 17.8% 6.9% 6.2% 3.7% 2.9% 2.1% 1.5% 1.4% 1.2% 1.2% 1.1% 1.0% 1.1% 0.9%
---[NoImage] x264 [info]: ref B L0: 67.6% 10.8% 6.2% 3.4% 2.4% 1.9% 1.5% 1.1% 0.9% 0.9% 0.8% 0.7% 0.7% 0.6% 0.7%
---[NoImage] x264 [info]: kb/s:1495.01
---[NoImage] encoded 6755 frames, 2.46 fps, 1495.01 kb/s
--[Information] [17/01/2010 2:14:44] Postprocessing
---[Information] Deleting intermediate files
--[Information] [17/01/2010 2:14:45] Job completed
-[Information] Log for job7 (video, Dj Shog - Live 4 Music.avs -> Dj Shog - Live 4 Music.mp4)
--[Information] [17/01/2010 2:14:45] Started handling job
--[Information] [17/01/2010 2:14:45] Preprocessing
--[NoImage] Job commandline: "C:\Program Files\megui\tools\x264\x264.exe" --profile high --level 3.1 --preset placebo --pass 2 --bitrate 1440 --stats "K:\Dj Shog - Live 4 Music.stats" --thread-input --deblock -1:-1 --vbv-bufsize 14000 --vbv-maxrate 17500 --no-dct-decimate --sar 1:1 --output "K:\Dj Shog - Live 4 Music.mp4" "K:\Dj Shog - Live 4 Music.avs"
--[Information] [17/01/2010 2:14:50] Encoding started
--[NoImage] Standard output stream:
--[NoImage] Standard error stream
---[NoImage] avs [info]: 720x320 @ 29.97 fps (6755 frames)
---[NoImage] x264 [info]: using SAR=1/1
---[NoImage] x264 [info]: using cpu capabilities: MMX2 SSE2Fast FastShuffle SSEMisalign LZCNT
---[NoImage] x264 [info]: profile High, level 3.1
---[NoImage] mp4 [info]: initial delay 1001 (scale 30000)
---[NoImage]
---[NoImage] x264 [info]: frame I:34 Avg QP:19.14 size: 13513
---[NoImage] x264 [info]: frame P:2565 Avg QP:21.98 size: 9092
---[NoImage] x264 [info]: frame B:4156 Avg QP:23.43 size: 4059
---[NoImage] x264 [info]: consecutive B-frames: 9.3% 23.6% 28.8% 13.7% 3.6% 12.9% 8.1% 0.0% 0.0% 0.0% 0.0% 0.0% 0.0% 0.0% 0.0% 0.0% 0.0%
---[NoImage] x264 [info]: mb I I16..4: 5.4% 88.7% 5.9%
---[NoImage] x264 [info]: mb P I16..4: 4.0% 32.7% 1.7% P16..4: 40.2% 15.4% 5.1% 0.0% 0.0% skip: 0.8%
---[NoImage] x264 [info]: mb B I16..4: 0.3% 2.1% 0.1% B16..8: 43.1% 1.1% 1.5% direct:19.0% skip:32.7% L0:47.6% L1:47.2% BI: 5.1%
---[NoImage] x264 [info]: 8x8 transform intra:85.2% inter:93.3%
---[NoImage] x264 [info]: direct mvs spatial:83.1% temporal:16.9%
---[NoImage] x264 [info]: coded y,uvDC,uvAC intra: 81.4% 85.8% 34.8% inter: 49.0% 61.3% 9.1%
---[NoImage] x264 [info]: i16 v,h,dc,p: 41% 30% 7% 21%
---[NoImage] x264 [info]: i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 7% 7% 4% 11% 15% 15% 14% 13% 14%
---[NoImage] x264 [info]: i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 8% 9% 2% 10% 15% 15% 16% 11% 14%
---[NoImage] x264 [info]: Weighted P-Frames: Y:25.7%
---[NoImage] x264 [info]: ref P L0: 36.9% 19.5% 21.9% 6.2% 5.3% 3.0% 2.2% 1.3% 1.0% 0.7% 0.6% 0.5% 0.4% 0.3% 0.2% 0.1%
---[NoImage] x264 [info]: ref B L0: 66.5% 13.8% 6.9% 3.5% 2.4% 1.8% 1.4% 0.8% 0.7% 0.5% 0.4% 0.4% 0.3% 0.2% 0.2%
---[NoImage] x264 [info]: kb/s:1442.87
---[NoImage] encoded 6755 frames, 2.66 fps, 1442.87 kb/s
--[Information] Final statistics
---[NoImage] Video Bitrate Desired: 1440 kbit/s
---[NoImage] Video Bitrate Obtained (approximate): 1445 kbit/s
--[Information] [17/01/2010 2:57:10] Postprocessing
---[Information] Deleting intermediate files
----[Information] [17/01/2010 2:57:10] Successfully deleted K:\Dj Shog - Live 4 Music.stats
----[Information] [17/01/2010 2:57:10] Successfully deleted K:\Dj Shog - Live 4 Music.stats.mbtree
--[Information] [17/01/2010 2:57:10] Job completed
nurbs
17th January 2010, 09:06
If you are using CoreAVC 1.9.5 then it's a know bug and your options are upgrading to CoreAVC 2.0, using another decoder or encoding with --weightp 1. The corruption for a short time in VLC is because of the way it handles seeking. First pass is that slow because you use --preset placebo which runs first pass with exactly the same settings as second pass.
Booji Boy
17th January 2010, 16:45
Is multi-threading broken after the latest update to 0.3.2.0?
vfw4x264.exe uses only one thread, FPS and EST are gone from the statistics window during encoding, too.
EDIT: Oh, it seems that the fast decode tuning does some single-threaded pre-processing... so I deactivated it.
MOS-Marauder
17th January 2010, 17:52
Hi ;)
If i disable the Cuvid Server @Preferences (use DGMultiDecodeNV) and start and encode it performs Pass 1 perfectly but on start of Pass 2 it simply stops.
(Cant decode Picures, like the Cuvid Server would somehow ended)
So i guess it has something to to with DGMultiDecodeNV.
If i use the Cuvid Server Option Pass 1 and 2 complete flawless. (DGDecodeNV)
Chris
BLKMGK
17th January 2010, 18:38
Much happiness to see this program updated and being worked on! I had refused to move forward on x.264 versions because of my wanting to use this, so many of the other 1 button push programs didn't do what I wanted! I am also very happy to see X64 and CUDA integration ongoing - awesome!
I'd like to setup my system to be as efficient as possible. I've dropped the profile I'd put together myself previously in favor of using some of the ones in this new release - I am specifically reprocessing BD movies. I'm testing with Bluray - Insane, 2-pass, and Very High Quality. I'm seeing slowdowns or equal speed to what I'd rigged together before. In one case, with 2-pass, I saw a 2Gig reduction in size for equal speed - excellent! Picture quality remains very high which is what I'm after.
I have a CUDA capable video card, an i7 clocked to the moon, Win7 64, and have registered CoreAVC 2.0. I'm now trying to figure out how best to string it all together. When I put together a graph using Haali I cannot select CoreAVC for decoding, instead I'm using ffdshow - boo! Is it worth sorting that?
I have also registered but not yet received the license for dgindexnv - do I simply need to copy the license file into the correct tool directory to activate this for meGUI? Will I see a speedup in processing with this alongside my 8 cores when this is properly setup? My previous attempts at using CUDA encoders resulted in less flexibility and slower encoding speeds so if this code can just assist my processor I'll be quite thrilled! Well worth the fee to support good code too.
I've been working with this stuff awhile but I will admit to not being 100% clear as to how it all works together (obviously) and now with new code am trying to get a better handle on it to best setup my workflow. I would imagine I'm not alone in this! So any tips to help out would be nice or perhaps a link somewhere to explanations for the new code features would be helpful! I just want to get most efficient use of my hardware I can and the best\smallest video possible without having to become a PHD in the guts of it all. I have CPU to burn but would prefer not to do so needlessly.
Lastly, my sincere thanks to Zanthor for picking this up and continuing to develop it! I realize there are simpler programs but I really appreciate this one for it's flexibility even if I do manage to dig myself into a hole occasionally. :)
carlo_0000
17th January 2010, 22:47
If you are using CoreAVC 1.9.5 then it's a know bug and your options are upgrading to CoreAVC 2.0, using another decoder or encoding with --weightp 1. The corruption for a short time in VLC is because of the way it handles seeking. First pass is that slow because you use --preset placebo which runs first pass with exactly the same settings as second pass.
ok thank coreavc problem
but for my movie in 1080p there is still a strange problem
why does x264 using so much the harddrive that it completly kill my computer
and longer i let try to encode the 1st pass and more bigger the swap memory is used
and it does not use a lot of cpu only 10-15%
with the old megui it didin't do that (it olso used a lot of swap memory) but it didn't kill my hard disk like that and cpu was use more than 90% in 1st pass
and why is dxva sd profile only level 3.1 , have i better quality if i select 4.1 and using placebo
and the turbo option is for 1st pass right ?
i tryed with an other profil (dxva hd extra quality) and that 1 work, it don't kill my hard disk
so there is someting wrong with my selected profil (profil dxva hd insane moved the preset on placebo)
did i set the profil to high ? can't we use placebo on 1080p ?
conclusion; profil dxva hd with preset on placebo don't work)
i move to preset very slow cpu is used @ 100% (athlon 620 4x3.1ghz) i have +- 4fps
Lyle_JP
18th January 2010, 04:28
What build of x264 were you using previously? It sounds to me like you've been completely unaware of the last year's worth of updates to x264, like Mb Tree (which explains the greater use of your hard-drive), presets (your lack of understanding regarding placebo and 2-pass) and weightp (your CORE AVC issues). It doesn't sound like you should be blaming MeGUI for your "things have changed" woes. x264 has undergone massive changes in the last year (MeGUI is only now catching up), and they're pretty much all good, but you do need to introduce yourself to the new concepts, and accept that using open source programs still in their development means having to keep your eye on things occasionally.
I strongly recommend spending some time in the "MPEG-4 AVC/H.264" board here on doom9, and I also recommend perusing x264's changelog. It may be technical and dry, but there's a lot of good stuff in there to help you understand all the new features, and why there is always a perpetual learning curve for all of us as updates are made.
AMED
18th January 2010, 06:12
I have seen a bug in MeGUI that stops you from being able to close MeGUI after a long encoding run (1-2 weeks). if you try and close with the X, the error below appears. the only way to kill MeGUI it through the task manager.
http://img29.imageshack.us/img29/4511/megui.th.png (http://img29.imageshack.us/i/megui.png/)
I've also noticed MeGUI using quite a lot of memory when this bug happens.
http://img188.imageshack.us/img188/8969/megui01.th.png (http://img188.imageshack.us/i/megui01.png/)
nurbs
18th January 2010, 08:33
and why is dxva sd profile only level 3.1 , have i better quality if i select 4.1 and using placebo The only difference for SD between level 3.1 and level 4.1 is that you can use 16 reference frames instead of 13 and your vbv-maxrate goes to 62.5 Mb/s from 17.5 Mb/s. The former will give you marginally better quality, but probably nothing that will be visible and the latter should have no impact at all at the bitrates SD normally is encoded at.
conclusion; profil dxva hd with preset on placebo don't work
Wrong. You are using preset placebo, which is more or less the slowest settings x264 supports, and you complain that it's slow. :rolleyes:
It doesn't use turbo in first pass, 16 b-frames with --b-adapt 2 is slow and the frametype decision is not multithreaded so it is to be expected that your cpu isn't anywhere near 100%.
LegendSeeker
18th January 2010, 15:01
Hi zathor, x264 settings; no fast pskip clicked but after encode, file settings mediainfo text:
"fast-pskip=0" normally?
"-no-fast-pskip" code not x264 command line.
nurbs
18th January 2010, 15:05
fast-pskip=0 means that it's turned off, so --no-fast-pskip is used.
deets
18th January 2010, 19:57
OS? DirectX up to date? Nvidia Drivers latest stable? what decoders?
vista 64. latest DX. 195.81 BETA drivers. arcsoft and powerDVD decoders.
set level to 4.1 and all works fine on very slow
Zathor
18th January 2010, 23:36
I have also registered but not yet received the license for dgindexnv - do I simply need to copy the license file into the correct tool directory to activate this for meGUI?
Yes, you have to copy the file to the tools\dgindexnv directory.
quantum5uicid3
19th January 2010, 00:58
vista 64. latest DX. 195.81 BETA drivers. arcsoft and powerDVD decoders.
set level to 4.1 and all works fine on very slow
ive been doing more testing, apparently my 8400gs does fail to playback unrestricted 1080p with both dxva(mpc-hc) and cuda(coreavc). however they definitely work flawlessly on my 9600gt, so it should work fine on a 260 gtx. Can you try again with the mpc-hc built in decoder? We need another dxva preset either way.
MOS-Marauder
19th January 2010, 01:29
Zathor: Update from 0.3.2.0 to 0.3.2.1 is broken.
It says updating..downloads to Cache..and after update Copier ist still old Version. Manual Extracting does same. So maybe u packed the wrong File in the Zip ? (megui-core_0_3_2_1.zip)
Chris
ludeboy12
19th January 2010, 01:36
Odd...Mine updated to 0.3.2.1 just fine here.
MOS-Marauder
19th January 2010, 02:07
How ? the File inside the Zip is the same exact same filesize like the old 0.3.2.0. Can u upload your MeGui.exe somewhere ?
Chris
Edit: I checked the Files @ Update Servers. All the same Build. NO 0.3.2.1.
ludeboy12
19th January 2010, 02:32
Oh wait. I thought you meant within auto update. Mine updated the core to 0.3.2.1 that way. Sorry I misunderstood you.
MOS-Marauder
19th January 2010, 02:53
Oh wait. I thought you meant within auto update. Mine updated the core to 0.3.2.1 that way. Sorry I misunderstood you.
Can u upload Your MeGui.exe file ?
Auto Update is nice but i checked all files @ Update servers..-.
ludeboy12
19th January 2010, 03:26
Ok here ya go: http://www.mediafire.com/?jijk5ywmymn
If I'm breaking any rules please delete.
Zathor
19th January 2010, 07:06
Zathor: Update from 0.3.2.0 to 0.3.2.1 is broken.
It says updating..downloads to Cache..and after update Copier ist still old Version. Manual Extracting does same. So maybe u packed the wrong File in the Zip ? (megui-core_0_3_2_1.zip)
Thanks! One mirror had a wrong file. Has been fixed.
MOS-Marauder
19th January 2010, 11:44
Thanks! One mirror had a wrong file. Has been fixed.
Thx Zathor ;) Works like a charm now. Also thx Ludeboy.
Is that right..also AviMuxGui got a step back ?
Chris
Zathor
19th January 2010, 12:44
Is that right..also AviMuxGui got a step back ?
Yes, because the latest version has problems with Win7 / Vista. You have to set the compatibility mode to XP SP3 with the latest version.
MOS-Marauder
19th January 2010, 13:56
Yes, because the latest version has problems with Win7 / Vista. You have to set the compatibility mode to XP SP3 with the latest version.
I know.. with the Older one u also had to do this.
But as long as it works ;))))
Good work on MeGui Zathor!!!!!!!!!!
Chris
deets
19th January 2010, 14:33
ive been doing more testing, apparently my 8400gs does fail to playback unrestricted 1080p with both dxva(mpc-hc) and cuda(coreavc). however they definitely work flawlessly on my 9600gt, so it should work fine on a 260 gtx. Can you try again with the mpc-hc built in decoder? We need another dxva preset either way.
yep mpc works fine, cant test coreavc as its not on the main PC.
if mpc could handle live streams i would just use that, but it doesnt so i need a few decoders on my system :(
hajj_3
19th January 2010, 16:19
please can you add support for .MTS files in the DG Creator, it isn't in the list of formats that can be opened, i have to use dgavcindex 1.0.9 and do this manually and load the .h264 file into megui:(
http://i50.tinypic.com/qp585v.jpg
Zathor
19th January 2010, 22:39
It is more or less painful to publish a new stable build with only one change, but it is necessary...
0.3.3.0
- (zathor) [OSInfo] Fix crash if OS is Windows 2000
Hopefully all big bugs are fixed and I can tweak MeGUI now with a few dev builds :)
Zathor
19th January 2010, 22:55
please can you add support for .MTS files in the DG Creator, it isn't in the list of formats that can be opened, i have to use dgavcindex 1.0.9 and do this manually and load the .h264 file into megui:(
Will be added in the next dev build.
don_h
19th January 2010, 23:28
please can you add support for .MTS files in the DG Creator, it isn't in the list of formats that can be opened, i have to use dgavcindex 1.0.9 and do this manually and load the .h264 file into megui:(
Try to enter *.* as the file name?
[ReX]
20th January 2010, 12:52
It's using vfw4x264.exe now instead of avs4x264.exe?
Why the change?
avs4x264.exe is faster here.
TheProfosist
20th January 2010, 14:10
im having problems using the DGcreator and DGindexNV it creates a file incompatible with DGsource and fails going into AVS script creator is this because it hasnt been update for latest version and any plan to fix it?
rack04
20th January 2010, 14:16
im having problems using the DGcreator and DGindexNV it creates a file incompatible with DGsource and fails going into AVS script creator is this because it hasnt been update for latest version and any plan to fix it?
It works perfectly for me. Have you tried creating your own script to verify that "DGcreator" and DGIndexNV is creating an invalid file?
TheProfosist
20th January 2010, 14:25
It works perfectly for me. Have you tried creating your own script to verify that "DGcreator" and DGIndexNV is creating an invalid file?
i have updated it to the latest build 2003
i did create one using DGindexNV and it puts out a dgm file. when using MeGUI it puts out a dgi file then when trying to load AVS script creator throws an error message saying some comand for DGSource is invalid
at the moment i create index file using DGindexNV crop inside it the create AVS scrip by hand having DGSource deinterlace and resize then tack on setting for FFT3dGPU
also i know with regular DGindex ColorMatrix is in AVS script is this needed with DGSource if so what script would be there?
Guest
20th January 2010, 14:48
i have updated it to the latest build 2003
i did create one using DGindexNV and it puts out a dgm file. Build 2003 cannot create DGM files.
TheProfosist
20th January 2010, 17:47
Build 2003 cannot create DGM files.
oops sorry!
im totally doing everything outside MeGUI at this point then just inputing the avsscript i manually made
i have build 2.0.0 beta 3
i input to DGindexNV a mpg file index file comes out is dgm
then i use this AVS script:
loadplugin("C:\Program Files (x86)\megui\tools\dgindexnv\DGDecodeNV.dll")
DGSource("C:\TEMP\Lain\07 - Cvt Vid\01.track_224-002_Track1.dgm", deinterlace=1, use_top_field=true, use_pf=true, resize_w=616, resize_h=480)
FFT3dGPU(sigma=4,sharpen=1.0,plane=4,precision=2,degrid=1.0)
hit enqueue takes a bit then hit start and its encoding at 6.7fps using the below x264 code:
program --profile high --level 5.1 --preset placebo --pass 3 --bitrate 1500 --stats ".stats" --thread-input --deblock 2:2 --bframes 5 --b-pyramid normal --rc-lookahead 40 --aq-mode 2 --aq-strength 1.5 --merange 16 --me umh --subme 7 --psy-rd 1.0:0.20 --no-mixed-refs --non-deterministic --vbv-maxrate 9800 --output "output" "input"
and it works but i cant for the life of me get DG NV to work through MeGUI like its supposed to.
rack04
20th January 2010, 17:51
i have build 2.0.0 beta 3
i input to DGindexNV a mpg file index file comes out is dgm
then i use this AVS script:
loadplugin("C:\Program Files (x86)\megui\tools\dgindexnv\DGDecodeNV.dll")
DGSource("C:\TEMP\Lain\07 - Cvt Vid\01.track_224-002_Track1.dgm", deinterlace=1, use_top_field=true, use_pf=true, resize_w=616, resize_h=480
As neuron2 stated, "Build 2003 cannot create DGM files." The output extension is DGI.
TheProfosist
20th January 2010, 17:56
As neuron2 stated, "Build 2003 cannot create DGM files." The output extension is DGI.
then how did i just make one using the program and use it in a script then encode useing it?
also dgi is listed as imcompatible when i tried to use it
Zathor
20th January 2010, 18:27
;1365704']It's using vfw4x264.exe now instead of avs4x264.exe?
Why the change?
avs4x264.exe is faster here.
Because avs4x264 produces garbage if the source is mpeg2 with DGDecode_mpeg2source serving this file (I do not know if dgmpg is the source of the problem or mpeg2 in general or avs4x264). vfw4x264 has no known problems.
rack04
20th January 2010, 18:27
then how did i just make one using the program and use it in a script then encode useing it?
also dgi is listed as imcompatible when i tried to use it
No clue. Maybe MeGUI update server has older version of DGIndexNV. Where is it listed as incompatible?
Guest
20th January 2010, 18:30
i have build 2.0.0 beta 3 Use the latest build: DGDecNV build 2003!
TheProfosist
21st January 2010, 01:21
Use the latest build: DGDecNV build 2003!
hmm i though that was what i had because i just went to this site yesterday to get it http://neuron2.net/dgdecnv/dgdecnv.html
homefully 2003 will fix some of the huge pixelation that i just got when encoding also
TheProfosist
21st January 2010, 01:47
ok dled 2003 got dgi file. still using dgindexnv outside megui because i need to crop but i can now put a dgi files right into the script editor which is good. but im having problems with the fieldop option because i dot know how to tell the difference between something being 3:2 pulldown or interlaced
Guest
21st January 2010, 01:55
"Build 2003" and "2.0.0 beta 3" are not the same thing!
I recently went to the 4 digit build number.
I answered your 3:2 versus interlaced question in the DGNV thread.
TheProfosist
21st January 2010, 02:09
"Build 2003" and "2.0.0 beta 3" are not the same thing!
I recently went to the 4 digit build number.
I answered your 3:2 versus interlaced question in the DGNV thread.
yep got it! thanks for all the help! i must have just started useing the day u switched
CIHx264
21st January 2010, 07:37
Hi Zathor, thanks for taking over megui and putting in, what must be a lot of work.
I may have found a bug in the x264 configuration.
In the Frame-Type tab if I set the B-Pyramid to disabled, and then move the Presets slider to any position the B-Pyramid stays disabled.
But if I set it to normal and then move the slider, it stays on normal on every position except Ultra Fast where it is set to disabled. Moving it back to a slower setting B-Pyramid stays disabled.
Is this how it’s supposed to work?
Puncakes
21st January 2010, 09:35
BeSplit doesn't appear to be included, but is required for the audio cutter. It's also called from the main megui directory rather than a folder in the tools directory. Are these intended? If not, the latest BeSplit can be found here (http://ffdshow.faireal.net/mirror/tmp/besplitv0.9b7.zip).
MOS-Marauder
21st January 2010, 12:26
Use the latest build: DGDecNV build 2003!
MeGui still uses 2002 ;)
Chris
I found something out... If i want to Crop a Source i cannot use NV Resize due Dimensions are not ok then. (error Message bust be Multiple by.... and so on.)
Is there a way to do the cropping also in the DGI Source Line?
Edit: found a bad but working solution.... I Cropped with DGIndexNV and after creating the AVS in MeGUI (Enabling NV Resizer) i entered manually in the AVS the final Resolution. Quick n Dirty but worked due in MeGui i cannot go over the input resolution ..eg if its 1244x720 i cannot enter 1280x720.
Maybe it is possible to make it that way that the Cropping Paramters are entered in the .dgi file by MeGui on enabling HW Resize? (CLIP 16 20 0 0 - top/bottom/left/right)
Im not sure if i have to enter left/right as positive or neg (2 or -2 for example like @ avisynth)
Chris
jmrenrav
21st January 2010, 19:56
I have a small request if possible.
Can you add an option for 2 pass encoding via Nero AAC Encoder? I have ran into some problems with the encoder giving me an error message, especially 5.1 HE audio. I manually created a 5.1 Wav using Besweet and replicated the same errors. Once I enabled the 2 pass option, everything worked great.
Errors were generated using directshow and avi input with MeGUI.
jmrenrav
21st January 2010, 20:02
MeGui still uses 2002 ;)
Chris
I found something out... If i want to Crop a Source i cannot use NV Resize due Dimensions are not ok then. (error Message bust be Multiple by.... and so on.)
Is there a way to do the cropping also in the DGI Source Line?
Edit: found a bad but working solution.... I Cropped with DGIndexNV and after creating the AVS in MeGUI (Enabling NV Resizer) i entered manually in the AVS the final Resolution. Quick n Dirty but worked due in MeGui i cannot go over the input resolution ..eg if its 1244x720 i cannot enter 1280x720.
Maybe it is possible to make it that way that the Cropping Paramters are entered in the .dgi file by MeGui on enabling HW Resize? (CLIP 16 20 0 0 - top/bottom/left/right)
Im not sure if i have to enter left/right as positive or neg (2 or -2 for example like @ avisynth)
Chris
Are you talking about when you crop it comes up with numbers divisible by 2 and you change it to a uneven number it gives you that error message?
I found a workaround by converting it to RGB32 before the crop and then back to YV12 after resize. I don't even like the idea of having one line of movie cropped if it's not needed ;)
Inspector.Gadget
21st January 2010, 20:07
If you need to crop by uneven numbers to reach an ultimately even width or height, you can pad the picture with AddBorders() and then crop it evenly (including cropping the borders) in the YV12 colorspace to end up with the same result as if you were able to crop by an odd number.
jmrenrav
21st January 2010, 20:29
If you need to crop by uneven numbers to reach an ultimately even width or height, you can pad the picture with AddBorders() and then crop it evenly (including cropping the borders) in the YV12 colorspace to end up with the same result as if you were able to crop by an odd number.
Oh wow that might help me alot, so here is an example of my current
# Set DAR in encoder to 47 : 20. The following line is for automatic signalling
global MeGUI_darx = 47
global MeGUI_dary = 20
LoadPlugin("C:\Program Files (x86)\MeGUI\tools\dgindex\DGDecode.dll")
DGDecode_mpeg2source("E:\Widescreen\A KNIGHTS TALE WS\VIDEO_TS\VTS_01_1.d2v", info=3)
LoadPlugin("C:\Program Files (x86)\MeGUI\tools\avisynth_plugin\ColorMatrix.dll")
ColorMatrix(hints=true, threads=0)
#deinterlace
ConvertToRGB32()
crop( 5, 54, 0, -59)
Spline36Resize(720,368) # Spline36 (Neutral)
ConvertToYV12()
LoadPlugin("C:\Program Files (x86)\MeGUI\tools\avisynth_plugin\UnDot.dll")
Undot() # Minimal Noise
and I could clean it up to look something like this...
# Set DAR in encoder to 47 : 20. The following line is for automatic signalling
global MeGUI_darx = 47
global MeGUI_dary = 20
LoadPlugin("C:\Program Files (x86)\MeGUI\tools\dgindex\DGDecode.dll")
DGDecode_mpeg2source("E:\Widescreen\A KNIGHTS TALE WS\VIDEO_TS\VTS_01_1.d2v", info=3)
#deinterlace
addborders(1, 0, 0, 1)
crop( 5, 54, 0, -59)
Spline36Resize(720,368) # Spline36 (Neutral)
LoadPlugin("C:\Program Files (x86)\MeGUI\tools\avisynth_plugin\UnDot.dll")
Undot() # Minimal Noise
Wouldnt need any color space conversions this way, nice!
salatoimikud
21st January 2010, 22:22
When i use Megui version 0.3.1.1056 then i have
x264 DXVA-SD-Insane profile 2 pass encoding FPS ~22
But when i use 0.3.3.0 then same profile 2 pass encoding FPS is only ~3.
What the hell? :devil:
Zathor
21st January 2010, 23:34
I may have found a bug in the x264 configuration.
In the Frame-Type tab if I set the B-Pyramid to disabled, and then move the Presets slider to any position the B-Pyramid stays disabled.
But if I set it to normal and then move the slider, it stays on normal on every position except Ultra Fast where it is set to disabled. Moving it back to a slower setting B-Pyramid stays disabled.
Is this how it’s supposed to work?
Simply: yes :rolleyes:Of course it is not perfect but as long as you cannot lock a value this behaviour is more or less necessary. Otherwise every slider move will revert the value back to a default value. Ideas are welcome!
BeSplit doesn't appear to be included, but is required for the audio cutter. It's also called from the main megui directory rather than a folder in the tools directory. Are these intended? If not, the latest BeSplit can be found here (http://ffdshow.faireal.net/mirror/tmp/besplitv0.9b7.zip).
BeSplit has not been included in the past as I know and I do not know why. You can specify the path to BeSplit in the MeGUI settings.
MeGui still uses 2002 ;)
It should be updated at the weekend.
Maybe it is possible to make it that way that the Cropping Paramters are entered in the .dgi file by MeGui on enabling HW Resize? (CLIP 16 20 0 0 - top/bottom/left/right)
Can you create a feature request at the sourceforge project page, please? Otherwise it may get lost.
Should NV resize be the default option if DGIndexNV is used?
Can you add an option for 2 pass encoding via Nero AAC Encoder? I have ran into some problems with the encoder giving me an error message, especially 5.1 HE audio. I manually created a 5.1 Wav using Besweet and replicated the same errors. Once I enabled the 2 pass option, everything worked great. Errors were generated using directshow and avi input with MeGUI.
Please create a feature request. Thanks!
When i use Megui version 0.3.1.1056 then i have
x264 DXVA-SD-Insane profile 2 pass encoding FPS ~22
But when i use 0.3.3.0 then same profile 2 pass encoding FPS is only ~3.
What the hell? :devil:
http://forum.doom9.org/showthread.php?p=1366376#post1366376
quantum5uicid3
22nd January 2010, 00:10
since jeeb appears to be afk, here's the komisar 1400kGIT generic builds for testing.
http://www.mediafire.com/?uynmhizymyt
NAL HRD 1.0 is included
MOS-Marauder
22nd January 2010, 00:50
Na u get me wrong.
Normally i do Crop and Resize in Megui.
When i enable NV Resize avisynth does the following...
Inputs the already resized Video and THEN appys the (now wrong) crop values from MeGui.
So i ask for a way IF enabling NV Resize that MeGui alters the DGI files with the Values and disables the crop in the avs File.
Chris
MOS-Marauder
22nd January 2010, 00:52
It should be updated at the weekend.
...
Can you create a feature request at the sourceforge project page, please? Otherwise it may get lost.
Should NV resize be the default option if DGIndexNV is used?
No need to hurry done it already manualy (even if Megui still shows 2002)...
Ok i do. I can say this only for me, but if i use NV i always use the Deinterlace (if nessesary) and always the NV Resizer.
Chris
tebasuna51
22nd January 2010, 01:49
Can you add an option for 2 pass encoding via Nero AAC Encoder?
Is not possible.
For the 2 pass encode NeroAacEnc need a physical wav file like input. And AviSynth send the audio data to NeroAacEnc STDIN.
Xvid or x264 can do 2 pass because in first pass write the 'stats' file and the second pass read this file. This method isn't supported by NearoAacEnc.
BTW, I think Nero developers are working in the problem (the crash with HE encode).
Zathor
22nd January 2010, 20:45
I have updated a few tools (x264, mkvtoolnix, dgindexnv). I'm only writing this because I have moved to the x264 build from Komisar and replaced the avs4x264 file with a new one from alwa. This should fix the problem with DGDecode_mpeg2source but I did not test it and therefore vfw4x264.exe is still used for x64.
Can you please try out the avs4x64 file and compare it in terms of speed to vfwx264? (Simply rename avs2x264 to vfw2x264)
Poutnik
22nd January 2010, 21:24
Note that I am not very familiar with 32 to 64 process piping, or with piping at all.
Proces explorer I/O monitoring shows VFW4x264 and X264_64 are exchanging about 40 MB of data per second.
Is it real writing /reading to/from disk of temporary passover files ?
CIHx264
22nd January 2010, 22:59
Simply: yes :rolleyes:Of course it is not perfect but as long as you cannot lock a value this behaviour is more or less necessary. Otherwise every slider move will revert the value back to a default value. Ideas are welcome!
Zathor, I’m now very confused.
Slider in position -Very Fast-
P-frame Weighted Prediction = Disabled
Adaptive B-Frames = 1-Fast
B-Pyramid = Disabled
M.E. Algorithm = Diamond
Subpixel Prediction = 01-QPel SAD
MV Prediction Mode = Spatial
Trellis = 0-None
Slider in position -Medium-
P-frame Weighted Prediction = Smart
Adaptive B-Frames = 1-Fast
B-Pyramid = Disabled
M.E. Algorithm = Hexagon
Subpixel Prediction = 07-RD on all frames
MV Prediction Mode = Spatial
Trellis = 1-Final MB
Slider in position -Very Slow-
P-frame Weighted Prediction = Smart
Adaptive B-Frames = 2-Optimal
B-Pyramid = Disabled
M.E. Algorithm = Multi hex
Subpixel Prediction = 10-QP-RD
MV Prediction Mode = Auto
Trellis = 2-Always
All the settings change with the slider position, as would be expected.
All except B-Pyramid, it stays the same in all positions including Placebo. Does this indicate that we should never use B-Pyramid settings or should it be treated as the items on the Main tab that are not affected by the slider.
I would have expected B-Pyramid to change from Disabled in Very Fast to Normal in the Medium position of the slider. With Strict added somewhere along the way.
Thank you for your patience.
nurbs
22nd January 2010, 22:59
Note that I am not very familiar with 32 to 64 process piping, or with piping at all.
Proces explorer I/O monitoring shows VFW4x264 and X264_64 are exchanging about 40 MB of data per second.
Is it real writing /reading to/from disk of temporary passover files ?
The data passed from vfw4x264 to x264_64 is the uncompressed video after avisynth processing (width x height x 12 bits per frame). That's much more then the harddisk IO because only the compressed streams are read and written.
All the settings change with the slider position, as would be expected.
All except B-Pyramid, it stays the same in all positions including Placebo. Does this indicate that we should never use B-Pyramid settings or should it be treated as the items on the Main tab that are not affected by the slider.
I would have expected B-Pyramid to change from Disabled in Very Fast to Normal in the Medium position of the slider. With Strict added somewhere along the way.
b-pyramid isn't used by any of the presets, because it didn't work with mb-tree until a month or so ago. The presets haven't changed since then. Dark Shikari mentioned that he is thinking about making --b-pyramid normal default, because it should give better quality and speeds things up a little. The speedup is more noticeable when you use many b-frames with --b-adapt 2. --b-pyramid strict is only there for blu-ray compatibility. It helps fast forwarding but hurts compression in comparison to normal.
Alf Bundy
22nd January 2010, 23:05
Can you please try out the avs4x64 file and compare it in terms of speed to vfwx264? (Simply rename avs2x264 to vfw2x264)
Just updated to x264 1400 and made 2 quick tests :
- Test 1 : Source MPEG-2 decoded with DGmultiSource()
640x480 25fps (44min 35")
avs4x264.exe - Fast 1st pass : avg FPS = 72,92fps - 15min 16"
vfw4x264.exe - Fast 1st pass : avg FPS = 80,73fps - 13min 49"
- Test 2 : Source VC-1 ES decoded with DGmultiSource()
1280x544 23.976fps (1000 frames)
avs4x264.exe
- Fast 1st pass : avg FPS = 27,04fps - 36 sec
- 2nd pass : avg FPS = 3,5fps - 4min 46"
vfw4x264.exe
- Fast 1st pass : avg FPS = 27,69fps - 36sec
- 2nd pass : avg FPS = 3,51fps - 4min 45"
Win7 x64, C2D E7400 @ 3Ghz, GPU = NV 9800GTX+
MeGUI 0.3.3.0, DG tools build 2005
PS : about MeGUI's version , in update (dev. server) I see Existing version 0.3.3.0 / latest version 0.3.2.3
Is that normal ?
CIHx264
22nd January 2010, 23:23
b-pyramid isn't used by any of the presets, because it didn't work with mb-tree until a month or so ago. The presets haven't changed since then. Dark Shikari mentioned that he is thinking about making --b-pyramid normal default, because it should give better quality and speeds things up a little. The speedup is more noticeable when you use many b-frames with --b-adapt 2. --b-pyramid strict is only there for blu-ray compatibility. It helps fast forwarding but hurts compression in comparison to normal.
Thank you, that answers my question. So is it OK to use B-Pyramid with the slider in the Slow position (all items up to date, stable server) or should I wait until it is officially added?
nurbs
22nd January 2010, 23:39
Whatever you prefer. There is no technical (except for blu-ray), quality or speed related reason not to use it as far as I know. Personally I use it.
MOS-Marauder
23rd January 2010, 11:17
I have updated a few tools (x264, mkvtoolnix, dgindexnv).)
I love You ;)
Btw i wrote the Feature Request @Sourceforge.
Chris
Zathor
23rd January 2010, 12:25
Just updated to x264 1400 and made 2 quick tests
Thank you very much. So at least based on your and my tests there is no need to switch back to avs2x264.
PS : about MeGUI's version , in update (dev. server) I see Existing version 0.3.3.0 / latest version 0.3.2.3
Is that normal ?
Thanks - fixed.
Zathor, I’m now very confused.
All the settings change with the slider position, as would be expected.
All except B-Pyramid, it stays the same in all positions including Placebo.
The whole preset handling in MeGUI is in parts confusing. Beside my rather small changes the complete interface has to be reworked. But I would like to wait so that the new things like the device, resize, ... handling in x264 will be revealed.
Btw i wrote the Feature Request @Sourceforge.
Thanks!
TheSane
23rd January 2010, 13:18
I Have a question. I installed my pc wiht Windows 7, before it runs with Windows Vista.
When i now want to recode a Movie (BR) and select 2pass (vbr) the first Job don't comes to an end and shows no progress. It makes no difference if i use predefined or self configured profile. When i use a 1pass (ex. BR Standard), it will start and show progress.
So i think i have a problem with the first pass job. How can i fix it?
Triccotracco
23rd January 2010, 14:07
The whole preset handling in MeGUI is in parts confusing. Beside my rather small changes the complete interface has to be reworked. But I would like to wait so that the new things like the device, resize, ... handling in x264 will be revealed.
:goodpost::thanks:
7ekno
23rd January 2010, 22:03
Well done Zathor!!!
I have only just come back to GUI's since MeGUI broke (which forced me to CLI/CMD files) ...
This is an awesome job, you rock for reviving the MeGUI project!!
Just a big thanks from an old user that appreciates the effort ;)
7ek
Zathor
23rd January 2010, 22:54
0.3.3.1
- [VobinputWindow] added mts as supported file extensions
- [MainForm] added information to the main window title if auto update is activated and the development server is used
- [VobinputWindow] Removed warning if no audio can be found. Feature request #2847468
- [JobWorkerWindow] Temporary worker will be closed automatically. Feature request #2928875
- [DAR] + [ARChooser] added 4:3 and 16:9 DAR
AMED
24th January 2010, 02:28
Is there any chance of changing the default supported file mask in the HD-DVD\Blu-ray Stream Extractor(in file mode) from mkv to all supported files?
Zathor
24th January 2010, 06:43
Is there any chance of changing the default supported file mask in the HD-DVD\Blu-ray Stream Extractor(in file mode) from mkv to all supported files?
Which file extensions are missing?
AMED
24th January 2010, 06:58
nothing is missing, it just defaults to look for only .mkv's and not to all supported files. so you have to keep manually changing it if you are not dealing with .mkv's.
http://img204.imageshack.us/img204/6634/mkv.th.png (http://img204.imageshack.us/i/mkv.png/)
nesta
24th January 2010, 10:38
I have a problem with x264 encoding in latest development build. It wont use my set reference frames in config or custom command line. No matter what I set, it always uses 3. Also noticed most changes made in profile config dont seem to update the command line often.
Elbart_
24th January 2010, 13:38
Because next to everything is done via custom commandline instead of the dialog, i.e. BluRay 2-pass: Picture (http://i49.tinypic.com/2008pjl.png)
nesta
24th January 2010, 21:10
Yes but even when i edit the custom command line, ill check final encode after in mediainfo, avinaptic, etc.. and it still didnt use the settings i set. I check megui log to see the settings used and there will be no mention of reference frames and other options that i set in profile and custom command line. It seems to have a mind of its own :p
Zathor
24th January 2010, 21:15
Please post your log and profile so that we can reproduce it.
Zathor
24th January 2010, 23:46
0.3.3.2
- [HDBDStreamExtractor] changed default file input type
- [InputBox] set initial focus to text box. Feature request #2938589
- [InputBox] if text box has focus pressing "enter" will call the ok event and "escape" the cancel event
- [tsMuxeR] fix final m2ts file creating in OneClick. Bug #2936118
Poutnik
25th January 2010, 07:58
The data passed from vfw4x264 to x264_64 is the uncompressed video after avisynth processing (width x height x 12 bits per frame). That's much more then the harddisk IO because only the compressed streams are read and written.
Dealing with uncompresed video is obvious to me.
I was just curious why Process Explorer marks tis data flow by same way as reading source by vfw4x264 and writing encoded h264 by x264_64..... ( i.e I/O read bytes/s, I/O write bytes/s)
aMvEL
25th January 2010, 10:33
Indexing a dvd-folder with multiple vob-files with dgindexnv only indexes the first (selected) vob, in contrary to dgindex which indexes all vobs when you select the first.
Is this intended, or a bug? Because as of now I have to manually open dgindexnv and select all vobs and index them.
Zathor
25th January 2010, 13:24
Indexing a dvd-folder with multiple vob-files with dgindexnv only indexes the first (selected) vob, in contrary to dgindex which indexes all vobs when you select the first.
Is this intended, or a bug? Because as of now I have to manually open dgindexnv and select all vobs and index them.
Bug or not - it should be investigated (and changed). It may be a problem in the behavior of DGIndex/DGIndexNV or MeGUI.
buzzqw
25th January 2010, 14:55
any hope for fixing the proxy support (for live update)?
BHH
Alf Bundy
25th January 2010, 15:20
Bug or not - it should be investigated (and changed). It may be a problem in the behavior of DGIndex/DGIndexNV or MeGUI.
It's the behavior of DGindexNV.
If you open only the file _0 of a such a sequence :
VOB_0
VOB_1
VOB_2
DGindexNV doesn't autoload _1 and _2.
Zathor
25th January 2010, 15:59
any hope for fixing the proxy support (for live update)?
BHH
I do not have/need a proxy and therefore I cannot reproduce and fix it.
Zathor
25th January 2010, 16:00
It's the behavior of DGindexNV.
If you open only the file _0 of a such a sequence :
VOB_0
VOB_1
VOB_2
DGindexNV doesn't autoload _1 and _2.
Ok, in this case the best way is to post this to the DGIndexNV thread (if not done already) as a feature request.
stax76
25th January 2010, 16:30
@Zathor
Use:
-i file1, file2
Unfortunately there is a comma as separator needed, this isn't common practice but for a GUI usually no problem, in some situations it is a problem (operating system or application not having a appropriate macro)
aMvEL
25th January 2010, 17:18
Ok, in this case the best way is to post this to the DGIndexNV thread (if not done already) as a feature request.
Well, DGIndexNV acts just like DGIndex-regular ... none of them open all vobs automatically ... so you need to select and open all files at once.
I'm guessing MeGUI opens all vobs with DGIndex/DGAVCIndex, because it indexes the whole movie with those tools.
So the same thing needs to be implemented when using DGIndexNV, since you can't select multiple files for indexing with MeGUI, only one single file.
Zathor
25th January 2010, 17:24
any hope for fixing the proxy support (for live update)?
BHH
Ok, I did a quick test with a proxy without authentication and I could download files without problems.
stax76
25th January 2010, 17:25
none of them open all vobs automatically
DGIndex should still have such auto load feature and neuron2 didn't want to implement it for other index applications.
All index applications have CLI documentation!
hajj_3
25th January 2010, 18:38
can you add 1.778 and 1.333 to the list of default A.R's, i have to add this manually every time i update to a new megui build:( Please add 559mb (1/8 dvdr), 746mb (1/6 dvdr) and 2239mb (1/2 dvdr) to the list of default sizes in bitrate calculator window too please.
Zathor
25th January 2010, 20:40
can you add 1.778 and 1.333 to the list of default A.R's, i have to add this manually every time i update to a new megui build:(
It's already added:
0.3.3.1
- [DAR] + [ARChooser] added 4:3 and 16:9 DAR
Mtouset
25th January 2010, 21:05
I hope this is the right place for my post. I'm currently running W7 with i7 processor. The Megui version I'm running is 0.3.3.0 as well as having run 0.3.1.106. The version does not appear to matter. Since I've been running W7 with the i7 processor I have not been able to encode an entire movie. I get through the 1st pass just fine, but the 2nd pass goes on forever, 12 hours+, and subsequently, esomewhere, after several hours, Megui errors out while trying to process the 2nd pass. I hope someone has some good guidance for me
hajj_3
25th January 2010, 21:08
It's already added:
0.3.3.1
- [DAR] + [ARChooser] added 4:3 and 16:9 DAR
ahh yeah, thanks:) Just dvdr files to add now then i'll be a happy bunny :)
Zathor
25th January 2010, 21:21
I hope this is the right place for my post. I'm currently running W7 with i7 processor. The Megui version I'm running is 0.3.3.0 as well as having run 0.3.1.106. The version does not appear to matter. Since I've been running W7 with the i7 processor I have not been able to encode an entire movie. I get through the 1st pass just fine, but the 2nd pass goes on forever, 12 hours+, and subsequently, esomewhere, after several hours, Megui errors out while trying to process the 2nd pass. I hope someone has some good guidance for me
Some ideas:
- switch to the development server. A new x264 build has been added there.
- install megui to a new directory (clean install)
- post your log
Zathor
25th January 2010, 21:42
I would like to add the new audio/video config panel which kurtnoise has developed. As a result ffac3, ffmp2, aud-x and faac encoders will be removed. Is anyone using these audio encoders?
HeadlessCow
25th January 2010, 22:59
If you're tweaking the video/audio page, could you add a button to the audio section that tells it to use the Avisynth script from the video section as the audio input as well? About 90% of the time I'm using the same source for both and that'd make it a little easier :-D
bkman
26th January 2010, 02:02
Hi,
I can't seem to initiate any x264 encoding at all with newer versions of MeGui. I've tried latest stable and latest dev.
All I get is this:
[Information] Log
-[Information] Versions
--[NoImage] MeGUI Version : 0.3.3.2
--[NoImage] OS : Windows Seven Ultimate Edition x64 (6.1.0.7600)
--[NoImage] Latest .Net Framework installed : 3.5 SP1 (3.5.30729.4926)
--[NoImage] Avisynth Version : 2.5.8.5
-[Information] Log for job7 (video, 01_ep02.avs -> )
--[Information] [1/26/2010 11:54:13 AM] Started handling job
--[Information] [1/26/2010 11:54:13 AM] Preprocessing
--[NoImage] Job commandline: "C:\Program Files (x86)\megui\tools\x264\vfw4x264.exe" --pass 1 --bitrate 3707 --stats "S:\Media\Movies\HD-DVD\STAR_TREK_EUR_D1\HVDVD_TS\converted\01_ep02_final.stats" --thread-input --deblock -1:-1 --keyint 240 --min-keyint 24 --b-adapt 2 --aq-mode 2 --me umh --trellis 2 --no-fast-pskip --sar 1:1 --output NUL "S:\Media\Movies\HD-DVD\STAR_TREK_EUR_D1\HVDVD_TS\converted\01_ep02.avs"
--[NoImage] Standard output stream
--[NoImage] Standard error stream
--[Information] [1/26/2010 11:54:14 AM] Job completed
-[NoImage] Error starting job
--[NoImage] Exception message: starting encoder failed with error 'Process has exited'
--[NoImage] Stacktrace: at MeGUI.core.gui.JobWorker.startEncoding(TaggedJob job)
--[NoImage] Inner exception: null
-[Information] Log for job7 (video, 01_ep02.avs -> )
--[Information] [1/26/2010 11:54:26 AM] Started handling job
--[Information] [1/26/2010 11:54:26 AM] Preprocessing
--[NoImage] Job commandline: "C:\Program Files (x86)\megui\tools\x264\vfw4x264.exe" --pass 1 --bitrate 3707 --stats "S:\Media\Movies\HD-DVD\STAR_TREK_EUR_D1\HVDVD_TS\converted\01_ep02_final.stats" --thread-input --deblock -1:-1 --keyint 240 --min-keyint 24 --b-adapt 2 --aq-mode 2 --me umh --trellis 2 --no-fast-pskip --sar 1:1 --output NUL "S:\Media\Movies\HD-DVD\STAR_TREK_EUR_D1\HVDVD_TS\converted\01_ep02.avs"
--[Information] [1/26/2010 11:54:27 AM] Encoding started
--[NoImage] Standard output stream
--[NoImage] Standard error stream
--[Information] [1/26/2010 11:54:27 AM] Job completed
It exits right away.
I'm running Win7 64-bit.
AMED
26th January 2010, 05:10
as along as the .AVS is still there try running this from a cmd prompt
"C:\Program Files (x86)\megui\tools\x264\vfw4x264.exe" --pass 1 --bitrate 3707 --stats "S:\Media\Movies\HD-DVD\STAR_TREK_EUR_D1\HVDVD_TS\converted\01_ep02_final.stats" --thread-input --deblock -1:-1 --keyint 240 --min-keyint 24 --b-adapt 2 --aq-mode 2 --me umh --trellis 2 --no-fast-pskip --sar 1:1 --output NUL "S:\Media\Movies\HD-DVD\STAR_TREK_EUR_D1\HVDVD_TS\converted\01_ep02.avs" and let us know what error you get.
7ekno
26th January 2010, 07:24
Well done Zathor :)
Just a quick question, any reason "Ref" and "bframes" are forced when selecting the "Levels" paramter?!?
Basically, I would like to be able to run something like "--crf 18 --preset slow --tune animation --level 3.1" and have x264 chose appropriate refs / bframes for the selected level (the CLI behaves that way) ... by adding the --ref and --bframe explicitly to the end of the CLI, it takes precedent over the "--level" setting ...
Also, may I suggest 3 modes 1) basic (to function as is) 2) Advanced (to function as is with the addition UI tabs) and 3) Custom (where the paramters can be typed over in the text box down the bottom of the profile - so the above issue can be bypassed, or typed explicitly)?!?
Thanks,
7ek
JoeH
26th January 2010, 08:28
I would like to add the new audio/video config panel which kurtnoise has developed. As a result ffac3, ffmp2, aud-x and faac encoders will be removed. Is anyone using these audio encoders?
No. I would like to see some lossless options, however - WAV 16/24 and FLAC output, for example.
Triccotracco
26th January 2010, 08:35
I would like to add the new audio/video config panel which kurtnoise has developed. As a result ffac3, ffmp2, aud-x and faac encoders will be removed. Is anyone using these audio encoders?
No, from my side. Flac could be usefull.
SacredCultivator
26th January 2010, 08:36
I used to use faac, until someone suggested to use nero-aac, and never looked back
help_me!
26th January 2010, 08:47
I'd like to see FLAC support too!
Taddeusz
26th January 2010, 18:29
x264 seems to no longer be tagging the resulting files with the settings used to encode.
Barough
26th January 2010, 19:04
I would like to add the new audio/video config panel which kurtnoise has developed. As a result ffac3, ffmp2, aud-x and faac encoders will be removed. Is anyone using these audio encoders?
I say, go ahead and add the the new A/V Config Panel. :)
Never used any of the encoders u mentioned.
Zathor
26th January 2010, 21:17
x264 seems to no longer be tagging the resulting files with the settings used to encode.
Please explain the problem in more detail (e.g. with log, mediainfo, ...)
Lyle_JP
27th January 2010, 08:02
Is there anything out there for AC3 audio in Avisynth other that NicAudio? It doesn't really handle less-common channel configurations (3.0, 4.1, etc) properly at all. Yes, I'm aware that Nero AAC won't encode anything but 1.0, 2.0, and 5.1 anyway, but at least if it decoded properly, I could manipulate the channels in a script to allow me to feed pseudo 5.1 to Nero. As it stands now, I must use eac3to using libav/ffmpeg (since Nero 7 and BeSweet are mostly useless for this task) to decode separate wav files for the channels, and then write a script to manipulate those.
I know, mostly this seems like an off-topic discussion for this thread, but what I would really like is to have Megui automatically handle these exotic ac-3 tracks, such as always expanding a mono surround channel in two, or the automatic creation of dummy "silent" surround tracks for 3.0 material, or a dummy silent center track for 4.0 material encoded as 2/2, etc. I guess the first paragraph was just to ask if there's even a plugin out there besides NicAudio for handling ac-3 audio in avisynth, because if there isn't, then this feature request would be moot.
Since Zathor wants to make the audio portion of MeGui the focus of his next most immediate work, I thought this might be a good time to ask this.
BuckMaster
27th January 2010, 10:46
Hi,
I have a problem with the new Megui,after update :
-[Information] Versions
--[NoImage] MeGUI Version : 0.3.3.2
--[NoImage] OS : Windows Seven Ultimate Edition x86 (6.1.0.7600)
--[NoImage] Latest .Net Framework installed : 3.5 SP1 (3.5.30729.4926)
--[NoImage] Avisynth Version : 2.5.8.5
-[Error] Log for job1 (video, 2012.avs -> )
--[Information] [27-Jan-10 11:40:43] Started handling job
--[Information] [27-Jan-10 11:40:43] Preprocessing
--[NoImage] Job commandline: "C:\Program Files\megui\tools\x264\x264.exe" --profile high --level 4.1 --preset fast --pass 1 --bitrate 1760 --stats "F:\2012.stats" --thread-input --deblock -1:-1 --bframes 4 --b-adapt 2 --ref 8 --slices 4 --vbv-bufsize 30000 --vbv-maxrate 40000 --rc-lookahead 60 --me umh --subme 9 --trellis 2 --psy-rd 1.0:1.00 --nal-hrd --keyint 24 --min-keyint 2 --sar 1:1 --output NUL "F:\2012.avs"
--[Information] [27-Jan-10 11:40:45] Encoding started
--[Error] An error occurred: avs [error]: Can't open F:\2012.mkv: 800401f0
--[Error] An error occurred: x264 [error]: could not open input file `F:\2012.avs'
--[NoImage] Standard output stream
--[NoImage] Standard error stream: (F:\2012.avs, line 6)
--[Information] [27-Jan-10 11:40:46] Job completed
if anyone have an idea please help me.
Thanks
tebasuna51
27th January 2010, 12:03
Is there anything out there for AC3 audio in Avisynth other that NicAudio? It doesn't really handle less-common channel configurations (3.0, 4.1, etc) properly at all. Yes, I'm aware that Nero AAC won't encode anything but 1.0, 2.0, and 5.1 anyway, but at least if it decoded properly, I could manipulate the channels in a script to allow me to feed pseudo 5.1 to Nero. As it stands now, I must use eac3to using libav/ffmpeg (since Nero 7 and BeSweet are mostly useless for this task) to decode separate wav files for the channels, and then write a script to manipulate those.
I know, mostly this seems like an off-topic discussion for this thread, but what I would really like is to have Megui automatically handle these exotic ac-3 tracks, such as always expanding a mono surround channel in two, or the automatic creation of dummy "silent" surround tracks for 3.0 material, or a dummy silent center track for 4.0 material encoded as 2/2, etc. I guess the first paragraph was just to ask if there's even a plugin out there besides NicAudio for handling ac-3 audio in avisynth, because if there isn't, then this feature request would be moot.
Since Zathor wants to make the audio portion of MeGui the focus of his next most immediate work, I thought this might be a good time to ask this.
The problem isn't the NicAudio decoder but how manage the channels to obtain the desired 5.1 output.
There are a generic AviSynth problem:
NicAudio know the channel mapping (3/0.0, 2/2.0, ...) but can't inform about that to AviSynth (don't exist a channelmask audio property), to make automatic management.
Then, if you know the channel map of the input ac3 file, you need write a specific .avs file to do the encode.
Avs example for 3.0 to 5.1 with empty channels:
a = NicAc3Source("file_3/0.0.ac3")
flr = GetChannel(a, 1, 2) # Front channels
fcc = GetChannel(a, 3) # Center channel
lfe = Amplify(fcc, 0) # empty LFE channel
slr = Amplify(flr, 0) # empty Surround channels
MergeChannels(flr, fcc, lfe, slr)
Avs example for 2/2.0 to 5.1 with empty channels:
a = NicAc3Source("file_2/2.0.ac3")
flr = GetChannel(a, 1, 2) # Front channels
slr = GetChannel(a, 3, 4) # Surround channels
clf = Amplify(slr, 0) # empty Center and LFE channels
MergeChannels(flr, clf, slr)
MeGUI (or BeHappy) can load these .avs like input audio.
bkman
28th January 2010, 10:18
as along as the .AVS is still there try running this from a cmd prompt
"C:\Program Files (x86)\megui\tools\x264\vfw4x264.exe" --pass 1 --bitrate 3707 --stats "S:\Media\Movies\HD-DVD\STAR_TREK_EUR_D1\HVDVD_TS\converted\01_ep02_final.stats" --thread-input --deblock -1:-1 --keyint 240 --min-keyint 24 --b-adapt 2 --aq-mode 2 --me umh --trellis 2 --no-fast-pskip --sar 1:1 --output NUL "S:\Media\Movies\HD-DVD\STAR_TREK_EUR_D1\HVDVD_TS\converted\01_ep02.avs" and let us know what error you get.
I don't get any error or any output at all. The command just executes and finishes without doing anything.
Interestingly, if I run the exact same command with avs4x264 instead it works perfectly.
quantum5uicid3
28th January 2010, 12:48
.....................
Elbart_
28th January 2010, 17:08
Just for future reference, in case there will be a premade preset for the iPad, its limitation is main profile level 3.1 up to 720p.
AMED
28th January 2010, 20:28
I don't get any error or any output at all. The command just executes and finishes without doing anything.
Interestingly, if I run the exact same command with avs4x264 instead it works perfectly.I wonder if this has anything to do with the long path names?
quantum5uicid3
29th January 2010, 04:58
.....................
MOS-Marauder
29th January 2010, 14:25
Hi,
I have a problem with the new Megui,after update :
--[Error] An error occurred: avs [error]: Can't open F:\2012.mkv: 800401f0
--[Error] An error occurred: x264 [error]: could not open input file `F:\2012.avs'
--[NoImage] Standard output stream
--[NoImage] Standard error stream: (F:\2012.avs, line 6)
--[Information] [27-Jan-10 11:40:46] Job completed[/code]
if anyone have an idea please help me.
Thanks
Looks like the AVIsynth script cannot find your .mkv File or You have no matching Decoder instralled.
If u used DirectShowSource make sure your system has a Decoder installed.
U can try it by Playing the AVS File in MediaPlayer Classic HC.
The better solution is to use Donald Grafts DGAVCIndex before to create the Frameserver File. That one u can load into the AVS Script Generator.
Chris
Dayvon
29th January 2010, 15:43
Hey all!!
I've been using MeGUI for quite a long time, I helped with some general information stuff in these forums near the start of it. Anyways, I did a update and I'm getting some weird results. This is the first time I've ever had an issue like this.
Went to encode, and I used the preset i made for Quicktime encoding. Never have had issues in the past 2 years. The video finishes encoding, and I've got smearing.... LOTS of smearing. Again, this has never happened until the update i just added. [MeGUI ver 0.3.3.0, x264 ver 1376 jeebs]
1. Is this a preset issue? I noticed the x264 preset window has changed drastically. Do I need to remake a preset (or use someone elses?)?
program --profile main --pass 2 --bitrate 3000 --stats ".stats" --thread-input --threads 2 --deblock -4:-4
--bframes 1 --no-weightb --ref 5 --me umh --subme 5 --partitions p8x8,b8x8,i4x4 --no-8x8dct --output "output" "input"
Above is what comes up in MeGUI when I select my Quicktime preset. Of course, this is AFTER the update, so I cant say if MeGUI is reading my preset correctly anymore, but you get the idea.
2. Is this a x264 issue? Did something change in x264 to create this problem?
If someone can let me know what's up, that be great! Thanks!
blsbball
29th January 2010, 16:42
i made another pack that overwrites most of the sharktooth presets. this should probably be a separate update from the other presets as it is really only providing legacy support. I blew through them as quick as i could, so errors are possible, but they're a def improvement with all sane options for the current state of x264.
my only intent is to curb all the preset related whining. :)
http://www.mediafire.com/?ymdnjyjhm0m
i should add i'm not discrediting sharktooth's contribution, it was invaluable to me and many others obviously. so i'm merely building upon his expertise.
Thanks for the presets. Appreciate the work you put into them. However when I go to use the costant quality one pass insane. It says that it will take more than an entire day to encode when usually this preset takes anywhere from 1 to 2 hours.
nurbs
29th January 2010, 17:26
The video finishes encoding, and I've got smearing.... LOTS of smearing. Again, this has never happened until the update i just added. [MeGUI ver 0.3.3.0, x264 ver 1376 jeebs]
Maybe quicktime can't handle weighed p-frame prediction. I wouldn't be surprised since AppleTV for instance can't. For a description of the problem see here (http://x264dev.multimedia.cx/?p=212). Basically there is some software and hardware out there that doesn't comply to the h.264 spec and produces artifacts when decoding streams encoded with that feature. With most devices --weightp 1 works but I heard for some you have to completely deactivate it (--weightp 0). Keeping it at 1 is of course preferable.
Dayvon
29th January 2010, 18:22
Maybe quicktime can't handle weighed p-frame prediction. I wouldn't be surprised since AppleTV for instance can't. For a description of the problem see here (http://x264dev.multimedia.cx/?p=212). Basically there is some software and hardware out there that doesn't comply to the h.264 spec and produces artifacts when decoding streams encoded with that feature. With most devices --weightp 1 works but I heard for some you have to completely deactivate it (--weightp 0). Keeping it at 1 is of course preferable.
Yeah, that's not what I'm talking about. The file ITSELF has smearing when played back in VLC or via FFdShow player. It's not a quicktime decoding issue. Like I previously stated, this preset has worked for me before, as little as 2 months ago, I used it successfully without any issue. So I'm pretty sure something updated, and my preset now seems borked :/
I'm testing with the iphone preset that came with the latest update... Hopefully that will work (no smearing) and then I hope it will be quicktime compatible as I need it to be. I'll update soon.
poisondeathray
29th January 2010, 18:45
Dayvon - why don't you try updating to r1400 ?
nurbs
29th January 2010, 18:50
Post a log please.
quantum5uicid3
29th January 2010, 21:59
...................
JoeH
30th January 2010, 09:27
ok i raised the speeds of the "Insane" and "HQ"
don't think it's gonna be within 2 hours still, try "HQ" or "Extra Quality"
http://www.mediafire.com/?1zouwh1u4jn
One thing it might be good to keep in mind is that build 1183 of X264 (which the old MeGUI used) is actually much faster than actual builds, at least when run on default settings. However, current builds offer much higher quality, and even lowering the settings to up the speed to match the speed of build 1183 the quality is still superior.
I set the speed option to "Faster" to match the speed of 1183, and the quality is much higher. I should say - I use bitrates of about 20,000, so at lower levels results could differ.
TheSane
30th January 2010, 10:04
I have a few Problems in setting the corect parameters. I want to habe 5 reframes. In the gui it is set to 5, but the commandline shows only 4 and the encoded output has only 3.
Here are the MediaInfo's:
Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L4.1
Format settings, CABAC : Yes
Format settings, ReFrames : 3 frames
Muxing mode : Container profile=Unknown@4.1
Codec ID : V_MPEG4/ISO/AVC
Duration : XXXX
Bit rate : 14.7 Mbps
Nominal bit rate : 15.0 Mbps
Width : 1 920 pixels
Height : 800 pixels
Display aspect ratio : 2.40:1
Frame rate : 23.976 fps
Resolution : 8 bits
Colorimetry : 4:2:0
Scan type : Progressive
Bits/(Pixel*Frame) : 0.399
Stream size : 15.8 GiB (98%)
Writing library : x264 core 84 r1400kGIT 20fa784
Encoding settings : cabac=1 / ref=4 / deblock=1:0:0 / analyse=0x3:0x113 / me=hex / subme=7 / psy=1 / psy_rd=1.0:0.0 / mixed_ref=1 / me_range=16 / chroma_me=1 / trellis=0 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=-2 / threads=6 / sliced_threads=0 / slices=4 / nr=0 / decimate=1 / mbaff=0 / constrained_intra=0 / bframes=3 / b_pyramid=1 / b_adapt=2 / b_bias=0 / direct=1 / wpredb=1 / wpredp=2 / keyint=24 / keyint_min=2 / scenecut=40 / intra_refresh=0 / rc_lookahead=24 / rc=2pass / mbtree=1 / bitrate=15000 / ratetol=1.0 / qcomp=0.60 / qpmin=10 / qpmax=51 / qpstep=4 / cplxblur=20.0 / qblur=0.5 / vbv_maxrate=40000 / vbv_bufsize=30000 / ip_ratio=1.40 / aq=1:1.00 / pulldown=0 / nal_hrd=1
Here are my config in MeGui:
http://www.abload.de/img/megui45ra.gif
How can i configure to have 5 reframes?
Thanks for reply.
Dayvon
30th January 2010, 15:55
Post a log please.
Did two more runs with minor adjustments and no luck. VOB files are clean.
[Information] Log
-[Information] Versions
--[NoImage] MeGUI Version : 0.3.3.0
--[NoImage] OS : Windows XP Professional x86 SP3 (5.1.196608.2600)
--[NoImage] Latest .Net Framework installed : .x (..)
--[NoImage] Avisynth Version : 2.5.7.0
-[Information] AutoEncode job generation log
--[NoImage] Split Size : null
--[Information] Eliminating duplicate filenames
---[NoImage] Video output file: E:\Rev Video\Video Temp\BoB\VIDEO_TS\BoB-09.264
---[NoImage] Muxed output file: E:\Rev Video\Video Temp\BoB\VIDEO_TS\BoB-09-muxed.mp4
---[NoImage] Encodable audio stream 0: E:\Rev Video\Video Temp\BoB\VIDEO_TS\BoB-09 T80 3_2ch 384Kbps DELAY 0ms.m4a
-[Information] Log for job61 (video, BoB-09.avs -> )
--[Information] [1/30/2010 12:44:50 AM] Started handling job
--[Information] [1/30/2010 12:44:50 AM] Preprocessing
--[NoImage] Job commandline: "C:\Rev Finder\Rev Media Station\MeGUI\tools\x264\x264.exe" --profile main --pass 1 --bitrate 3000 --stats "E:\Rev Video\Video Temp\BoB\VIDEO_TS\BoB-09.stats" --thread-input --threads 2 --deblock -4:-4 --bframes 1 --no-weightb --ref 5 --me umh --subme 5 --partitions p8x8,b8x8,i4x4 --no-8x8dct --sar 1:1 --output NUL "E:\Rev Video\Video Temp\BoB\VIDEO_TS\BoB-09.avs"
--[Information] [1/30/2010 12:44:50 AM] Encoding started
--[NoImage] Standard output stream
--[NoImage] Standard error stream
---[NoImage] avs [info]: 720x400 @ 23.98 fps (82792 frames)
---[NoImage] x264 [info]: using SAR=1/1
---[NoImage] x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 Cache64
---[NoImage] x264 [info]: profile Main, level 3.0
---[NoImage]
---[NoImage] x264 [info]: frame I:600 Avg QP:14.71 size: 50472
---[NoImage] x264 [info]: frame P:46113 Avg QP:17.56 size: 21861
---[NoImage] x264 [info]: frame B:36079 Avg QP:20.60 size: 6861
---[NoImage] x264 [info]: consecutive B-frames: 12.2% 87.8%
---[NoImage] x264 [info]: mb I I16..4: 14.3% 0.0% 85.7%
---[NoImage] x264 [info]: mb P I16..4: 17.0% 0.0% 0.0% P16..4: 76.2% 0.0% 0.0% 0.0% 0.0% skip: 6.8%
---[NoImage] x264 [info]: mb B I16..4: 3.1% 0.0% 0.0% B16..8: 35.7% 0.0% 0.0% direct:31.0% skip:30.2% L0:21.6% L1:31.9% BI:46.5%
---[NoImage] x264 [info]: final ratefactor: 15.58
---[NoImage] x264 [info]: coded y,uvDC,uvAC intra: 70.0% 52.1% 16.4% inter: 54.8% 21.4% 1.4%
---[NoImage] x264 [info]: i16 v,h,dc,p: 35% 21% 26% 18%
---[NoImage] x264 [info]: i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 21% 18% 11% 7% 9% 8% 9% 8% 9%
---[NoImage] x264 [info]: Weighted P-Frames: Y:5.2%
---[NoImage] x264 [info]: kb/s:2979.04
---[NoImage] encoded 82792 frames, 55.25 fps, 2979.04 kb/s
--[Information] [1/30/2010 1:09:49 AM] Postprocessing
--[Information] [1/30/2010 1:09:49 AM] Job completed
-[Information] Log for job62 (video, BoB-09.avs -> BoB-09.264)
--[Information] [1/30/2010 1:09:50 AM] Started handling job
--[Information] [1/30/2010 1:09:50 AM] Preprocessing
--[NoImage] Job commandline: "C:\Rev Finder\Rev Media Station\MeGUI\tools\x264\x264.exe" --profile main --pass 2 --bitrate 3000 --stats "E:\Rev Video\Video Temp\BoB\VIDEO_TS\BoB-09.stats" --thread-input --threads 2 --deblock -4:-4 --bframes 1 --no-weightb --ref 5 --me umh --subme 5 --partitions p8x8,b8x8,i4x4 --no-8x8dct --sar 1:1 --aud --output "E:\Rev Video\Video Temp\BoB\VIDEO_TS\BoB-09.264" "E:\Rev Video\Video Temp\BoB\VIDEO_TS\BoB-09.avs"
--[Information] [1/30/2010 1:09:53 AM] Encoding started
--[NoImage] Standard output stream
--[NoImage] Standard error stream
---[NoImage] avs [info]: 720x400 @ 23.98 fps (82792 frames)
---[NoImage] x264 [info]: using SAR=1/1
---[NoImage] x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 Cache64
---[NoImage] x264 [info]: profile Main, level 3.0
---[NoImage]
---[NoImage] x264 [info]: frame I:600 Avg QP:14.76 size: 49871
---[NoImage] x264 [info]: frame P:46113 Avg QP:17.00 size: 21810
---[NoImage] x264 [info]: frame B:36079 Avg QP:19.99 size: 7190
---[NoImage] x264 [info]: consecutive B-frames: 12.2% 87.8%
---[NoImage] x264 [info]: mb I I16..4: 14.3% 0.0% 85.7%
---[NoImage] x264 [info]: mb P I16..4: 4.2% 0.0% 14.0% P16..4: 18.7% 23.3% 32.9% 0.0% 0.0% skip: 6.8%
---[NoImage] x264 [info]: mb B I16..4: 1.3% 0.0% 2.3% B16..8: 34.1% 4.7% 4.9% direct:24.8% skip:27.9% L0:30.6% L1:26.0% BI:43.4%
---[NoImage] x264 [info]: coded y,uvDC,uvAC intra: 82.7% 63.5% 17.5% inter: 51.8% 31.7% 1.2%
---[NoImage] x264 [info]: i16 v,h,dc,p: 38% 24% 24% 14%
---[NoImage] x264 [info]: i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 22% 18% 15% 6% 9% 8% 8% 7% 7%
---[NoImage] x264 [info]: Weighted P-Frames: Y:5.2%
---[NoImage] x264 [info]: ref P L0: 53.0% 13.2% 20.0% 5.4% 4.9% 3.3% 0.1%
---[NoImage] x264 [info]: ref B L0: 78.2% 10.5% 5.8% 5.5%
---[NoImage] x264 [info]: kb/s:3000.36
---[NoImage] encoded 82792 frames, 15.25 fps, 3000.36 kb/s
--[Information] Final statistics
---[NoImage] Video Bitrate Desired: 3000 kbit/s
---[NoImage] Video Bitrate Obtained (approximate): 3000 kbit/s
--[Information] [1/30/2010 2:40:29 AM] Postprocessing
--[Information] [1/30/2010 2:40:29 AM] Job completed
-[Information] Log for job63 (mux, BoB-09.264 -> BoB-09-muxed.mp4)
--[Information] [1/30/2010 2:40:29 AM] Started handling job
--[Information] [1/30/2010 2:40:29 AM] Preprocessing
--[NoImage] Job commandline: "C:\Rev Finder\Rev Media Station\MeGUI\tools\mp4box\mp4box.exe" -add "E:\Rev Video\Video Temp\BoB\VIDEO_TS\BoB-09.264:fps=23.976" -add "E:\Rev Video\Video Temp\BoB\VIDEO_TS\BoB-09 T80 3_2ch 384Kbps DELAY 0ms.m4a#trackID=1" -tmp "E:\Rev Video\Video Temp\BoB\VIDEO_TS" -new "E:\Rev Video\Video Temp\BoB\VIDEO_TS\BoB-09-muxed.mp4"
--[Information] [1/30/2010 2:40:30 AM] Muxing started
--[NoImage] Standard output stream
---[NoImage] AVC-H264 import - frame size 720 x 400 at 23.976 FPS
---[NoImage] Import results: 82792 samples - Slices: 600 I 46113 P 36079 B - 1 SEI - 591 IDR
---[NoImage] IsoMedia import - track ID 1 - Audio (SR 48000 - 2 channels)
---[NoImage] Saving E:\Rev Video\Video Temp\BoB\VIDEO_TS\BoB-09-muxed.mp4: 0.500 secs Interleaving
--[NoImage] Standard error stream
--[Information] [1/30/2010 2:43:39 AM] Postprocessing
--[Information] [1/30/2010 2:43:39 AM] Job completed
Results are as follows.
http://www.crossing-church.com/download/Temp/snapshot20100130083801.jpg
http://www.crossing-church.com/download/Temp/snapshot20100130083839.jpg
http://www.crossing-church.com/download/Temp/snapshot20100130083915.jpg
HOLD ON... I tested in VLC once more, and I am not seeing the issue with this latest render. Might be a playback issue. Otherwise, the log is normal?
poisondeathray
30th January 2010, 16:14
How can i configure to have 5 reframes?
Thanks for reply.
You're using a megui profile that overrides your settings. In the last tab (misc), check the custom command line box
Dayvon
30th January 2010, 16:19
Looks like an FFdShow reinstall cleaned it up... So weird that i have a playback issue ONLY on a new file and AFTER a MeGUI update. Good news, all is well. Sorry bout the false alarm. :eek:
sneaker_ger
30th January 2010, 16:27
Looks like an FFdShow reinstall cleaned it up... So weird that i have a playback issue ONLY on a new file and AFTER a MeGUI update. Good news, all is well. Sorry bout the false alarm. :eek:
Could be this (http://x264dev.multimedia.cx/?p=212).
TheSane
30th January 2010, 16:39
You're using a megui profile that overrides your settings. In the last tab (misc), check the custom command line box
Okay, is this new? In the past i don't do "commandline work".
That i understand correctly, when i toggle an option in megui it will not be used unless i change it in the commandline?
poisondeathray
30th January 2010, 16:49
Okay, is this new? In the past i don't do "commandline work".
That i understand correctly, when i toggle an option in megui it will not be used unless i change it in the commandline?
The way these new preset profiles are setup (in terms of megui's profiles , not x264's presets, profiles or tunings), some commands are entered in that box to ensure compatibility. e.g. if you are using a blu-ray profile or avchd profile or some device profile. Otherwise it might break compliance for that target device.
You must have selected one of these profiles, because there are items already written in that commandline box
If you erase everything in that commandline box, the gui should work as you expect, and whatever you enter (but if you don't know what you're doing, it might break compliance for your target)
Taddeusz
31st January 2010, 18:03
Please explain the problem in more detail (e.g. with log, mediainfo, ...)
Sorry for taking so long. Had a bad motherboard in my server. Here are a couple MediaInfo showing the difference. Notice the second one is missing the Writing Library and Encoding Settings.
The way it was:
General
Complete name : Z:\Videos\HD Movies\10 Things I Hate About You.mkv
Format : Matroska
File size : 5.59 GiB
Duration : 1h 37mn
Overall bit rate : 8 196 Kbps
Encoded date : UTC 2010-01-13 19:25:35
Writing application : mkvmerge v3.0.0 ('Hang up your Hang-Ups') built on Dec 12 2009 15:20:35
Writing library : libebml v0.7.9 + libmatroska v0.8.1
Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L4.1
Format settings, CABAC : Yes
Format settings, ReFrames : 3 frames
Muxing mode : Container profile=Unknown@4.1
Codec ID : V_MPEG4/ISO/AVC
Duration : 1h 37mn
Bit rate : 6 139 Kbps
Nominal bit rate : 6 300 Kbps
Width : 1 920 pixels
Height : 1 040 pixels
Display aspect ratio : 16:9
Frame rate : 23.976 fps
Resolution : 8 bits
Colorimetry : 4:2:0
Scan type : Progressive
Bits/(Pixel*Frame) : 0.128
Stream size : 4.18 GiB (75%)
Writing library : x264 core 80 r1376M 3feaec2
Encoding settings : cabac=1 / ref=4 / deblock=1:0:0 / analyse=0x3:0x133 / me=hex / subme=7 / psy=1 / psy_rd=1.0:0.0 / mixed_ref=1 / me_range=16 / chroma_me=1 / trellis=1 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=-2 / threads=6 / sliced_threads=0 / slices=4 / nr=0 / decimate=0 / mbaff=0 / constrained_intra=0 / bframes=3 / b_pyramid=1 / b_adapt=1 / b_bias=0 / direct=1 / wpredb=1 / wpredp=2 / keyint=24 / keyint_min=2 / scenecut=40 / rc_lookahead=24 / rc=2pass / mbtree=1 / bitrate=6300 / ratetol=1.0 / qcomp=0.60 / qpmin=10 / qpmax=51 / qpstep=4 / cplxblur=20.0 / qblur=0.5 / vbv_maxrate=40000 / vbv_bufsize=30000 / ip_ratio=1.40 / aq=1:1.00
Language : English
Audio #1
ID : 2
Format : DTS
Format/Info : Digital Theater Systems
Codec ID : A_DTS
Duration : 1h 37mn
Bit rate mode : Constant
Bit rate : 1 510 Kbps
Channel(s) : 6 channels
Channel positions : Front: L C R, Surround: L R, LFE
Sampling rate : 48.0 KHz
Resolution : 24 bits
Stream size : 1.03 GiB (18%)
Language : English
Audio #2
ID : 3
Format : AC-3
Format/Info : Audio Coding 3
Codec ID : A_AC3
Duration : 1h 37mn
Bit rate mode : Constant
Bit rate : 384 Kbps
Channel(s) : 6 channels
Channel positions : Front: L C R, Surround: L R, LFE
Sampling rate : 48.0 KHz
Stream size : 268 MiB (5%)
Language : English
Menu
00:00:00.000 : en:00:00:00.000
00:05:44.469 : en:00:05:44.469
00:12:34.128 : en:00:12:34.128
00:15:51.284 : en:00:15:51.284
00:21:54.396 : en:00:21:54.396
00:25:59.391 : en:00:25:59.391
00:31:53.495 : en:00:31:53.495
00:36:00.742 : en:00:36:00.742
00:41:40.998 : en:00:41:40.998
00:51:32.631 : en:00:51:32.631
00:56:35.350 : en:00:56:35.350
01:00:01.223 : en:01:00:01.223
01:03:02.362 : en:01:03:02.362
01:05:06.486 : en:01:05:06.486
01:07:39.597 : en:01:07:39.597
01:10:15.461 : en:01:10:15.461
01:14:55.491 : en:01:14:55.491
01:18:12.187 : en:01:18:12.187
01:25:58.111 : en:01:25:58.111
01:29:08.718 : en:01:29:08.718
01:32:11.192 : en:01:32:11.192
The way it is now:
General
Complete name : Z:\Videos\HD Movies\Moon.mkv
Format : Matroska
File size : 4.88 GiB
Duration : 1h 37mn
Overall bit rate : 7 195 Kbps
Encoded date : UTC 2010-01-31 15:29:22
Writing application : mkvmerge v3.0.0 ('Hang up your Hang-Ups') built on Dec 12 2009 15:20:35
Writing library : libebml v0.7.9 + libmatroska v0.8.1
Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L4.1
Format settings, CABAC : Yes
Format settings, ReFrames : 3 frames
Muxing mode : Container profile=Unknown@4.1
Codec ID : V_MPEG4/ISO/AVC
Duration : 1h 37mn
Bit rate : 5 158 Kbps
Width : 1 920 pixels
Height : 800 pixels
Display aspect ratio : 2.40:1
Frame rate : 23.976 fps
Resolution : 8 bits
Colorimetry : 4:2:0
Scan type : Progressive
Bits/(Pixel*Frame) : 0.140
Stream size : 3.50 GiB (72%)
Language : English
Audio #1
ID : 2
Format : DTS
Format/Info : Digital Theater Systems
Codec ID : A_DTS
Duration : 1h 37mn
Bit rate mode : Constant
Bit rate : 1 510 Kbps
Channel(s) : 6 channels
Channel positions : Front: L C R, Surround: L R, LFE
Sampling rate : 48.0 KHz
Resolution : 24 bits
Stream size : 1.02 GiB (21%)
Language : English
Audio #2
ID : 3
Format : AC-3
Format/Info : Audio Coding 3
Codec ID : A_AC3
Duration : 1h 37mn
Bit rate mode : Constant
Bit rate : 384 Kbps
Channel(s) : 6 channels
Channel positions : Front: L C R, Surround: L R, LFE
Sampling rate : 48.0 KHz
Stream size : 267 MiB (5%)
Language : English
Menu
00:00:00.000 : en:00:00:00.000
00:05:41.967 : en:00:05:41.967
00:11:05.164 : en:00:11:05.164
00:18:00.955 : en:00:18:00.955
00:22:58.836 : en:00:22:58.836
00:28:47.976 : en:00:28:47.976
00:34:35.907 : en:00:34:35.907
00:42:52.987 : en:00:42:52.987
00:47:28.012 : en:00:47:28.012
00:54:35.939 : en:00:54:35.939
01:01:55.211 : en:01:01:55.211
01:07:38.221 : en:01:07:38.221
01:13:15.182 : en:01:13:15.182
01:16:49.939 : en:01:16:49.939
01:22:32.656 : en:01:22:32.656
01:30:40.143 : en:01:30:40.143
Roy Knable
2nd February 2010, 07:45
What Sharktooth preset is the current AVCHD 2-pass preset equivalent to? I just re-encoded a TV episode and found the quality was noticeably worse than the old 2-pass Extra Quality. I could now see pixelation in smooth backgrounds like skies which changed with every keyframe. Quite distracting. I also noticed Constant Quality Very High Quality isn't very good when I tried that with a few movies. Both the Very High and the 2-pass encode a lot faster than the old preset, but I don't like the quality at about 980kbps. Sorry, I just used presets over the last few years and never mess with the CLI settings. Am I doing something wrong? I'm starting to think I'll go back to the last build I got good results with (0.3.1 with x264 build 1183).
Warbucks81
2nd February 2010, 16:31
I upgraded to the latest version of x264 last night and now It crashes anytime I try running a job. I reverted back to the previous version and it's working fine now.
Just thought i'd give everyone a heads up.
TheSane
2nd February 2010, 18:58
The way these new preset profiles are setup (in terms of megui's profiles , not x264's presets, profiles or tunings), some commands are entered in that box to ensure compatibility. e.g. if you are using a blu-ray profile or avchd profile or some device profile. Otherwise it might break compliance for that target device.
You must have selected one of these profiles, because there are items already written in that commandline box
If you erase everything in that commandline box, the gui should work as you expect, and whatever you enter (but if you don't know what you're doing, it might break compliance for your target)
I don't understand how i can get 5 Reframes.
I configured this profile:
http://www.abload.de/thumb/3yddg.jpg (http://www.abload.de/image.php?img=3yddg.jpg) http://www.abload.de/thumb/19coj.jpg (http://www.abload.de/image.php?img=19coj.jpg) http://www.abload.de/thumb/4tgyk.jpg (http://www.abload.de/image.php?img=4tgyk.jpg) http://www.abload.de/thumb/2pckl.jpg (http://www.abload.de/image.php?img=2pckl.jpg) http://www.abload.de/thumb/5icb8.jpg (http://www.abload.de/image.php?img=5icb8.jpg)
with the follwoing result:
Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L4.1
Format settings, CABAC : Yes
Format settings, ReFrames : 4 frames
Muxing mode : Container profile=Unknown@4.1
Codec ID : V_MPEG4/ISO/AVC
Duration : XXXX
Bit rate : 14.7 Mbps
Nominal bit rate : 15.0 Mbps
Width : 1 920 pixels
Height : 800 pixels
Display aspect ratio : 2.40:1
Frame rate : 23.976 fps
Resolution : 8 bits
Colorimetry : 4:2:0
Scan type : Progressive
Bits/(Pixel*Frame) : 0.399
Stream size : 15.8 GiB (98%)
Writing library : x264 core 84 r1400kGIT 20fa784
Encoding settings : cabac=1 / ref=5 / deblock=1:0:0 / analyse=0x3:0x133 / me=umh / subme=10 / psy=1 / psy_rd=1.0:0.0 / mixed_ref=1 / me_range=64 / chroma_me=1 / trellis=2 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=-3 / threads=6 / sliced_threads=0 / nr=0 / decimate=1 / mbaff=0 / constrained_intra=0 / bframes=3 / b_pyramid=1 / b_adapt=1 / b_bias=0 / direct=1 / wpredb=1 / wpredp=2 / keyint=250 / keyint_min=25 / scenecut=40 / intra_refresh=0 / rc_lookahead=60 / rc=2pass / mbtree=1 / bitrate=15000 / ratetol=1.0 / qcomp=0.70 / qpmin=10 / qpmax=51 / qpstep=4 / cplxblur=20.0 / qblur=0.5 / vbv_maxrate=50000 / vbv_bufsize=50000 / ip_ratio=1.40 / aq=1:1.00 / pulldown=0 / nal_hrd=0
Language : English
What must i change to get this?
Zathor
2nd February 2010, 19:38
I upgraded to the latest version of x264 last night and now It crashes anytime I try running a job. I reverted back to the previous version and it's working fine now.
Just thought i'd give everyone a heads up.
Can you please provide more details (OS, avs, log, what kind of crash... )? I have no problems so far with the new build.
PzSniper
2nd February 2010, 21:37
Upgraded to latest 0.3.3.2 version but this is the first time i encounter error processing files:
After i ran DGIndex i processed files with MeGui and got this:
[Error] Log for job9 (audio, Discovery Sci @12d2fcfa.Joined PID 5dd L2 2ch 48 160 DELAY -308ms.mp2 -> Discovery Sci @12d2fcfa.Joined PID 5dd L2 2ch 48 160 DELAY 0ms.mp3)
-[Information] [02/02/2010 11:51:23] Started handling job
-[Information] [02/02/2010 11:51:23] Preprocessing
-[NoImage] Avisynth script
--[NoImage] LoadPlugin("V:\megui2\tools\avisynth_plugin\NicAudio.dll")
--[NoImage] NicMPG123Source("Q:\1- iTUNES\Discovery Sci @12d2fcfa\Discovery Sci @12d2fcfa.Joined PID 5dd L2 2ch 48 160 DELAY -308ms.mp2")
--[NoImage] DelayAudio(-308.0/1000.0)
--[NoImage] 6<=Audiochannels(last)?x_stereo87c9c60b624447989f612438bb34ebe1(ConvertAudioToFloat(last)):last
--[NoImage] Normalize()
--[NoImage] 32==Audiobits(last)?ConvertAudioTo16bit(last):last
--[NoImage] return last
--[NoImage] function x_stereo87c9c60b624447989f612438bb34ebe1(clip a)
--[NoImage] {
--[NoImage] fl = GetChannel(a, 1)
--[NoImage] fr = GetChannel(a, 2)
--[NoImage] c = GetChannel(a, 3)
--[NoImage] lfe = GetChannel(a, 4)
--[NoImage] sl = GetChannel(a, 5)
--[NoImage] sr = GetChannel(a, 6)
--[NoImage] l_sl = MixAudio(fl, sl, 0.2929, 0.2929)
--[NoImage] c_lfe = MixAudio(lfe, c, 0.2071, 0.2071)
--[NoImage] r_sr = MixAudio(fr, sr, 0.2929, 0.2929)
--[NoImage] l = MixAudio(l_sl, c_lfe, 1.0, 1.0)
--[NoImage] r = MixAudio(r_sr, c_lfe, 1.0, 1.0)
--[NoImage] return MergeChannels(l, r)
--[NoImage] }
-[NoImage] Commandline used: --abr 128 -h - "{0}"
-[Information] [02/02/2010 11:51:23] Encoding started
-[Information] [02/02/2010 11:51:23] Encode thread started
-[Information] [02/02/2010 11:51:23] Avisynth script environment opened
-[Error] An error occurred
--[NoImage] Exception message: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
--[NoImage] Stacktrace
---[NoImage] at MeGUI.AviSynthClip.dimzon_avs_init_2(IntPtr& avs, String func, String arg, AVSDLLVideoInfo& vi, AviSynthColorspace& originalColorspace, AudioSampleType& originalSampleType, String cs)
---[NoImage] at MeGUI.AviSynthClip..ctor(String func, String arg, AviSynthColorspace forceColorspace, AviSynthScriptEnvironment env)
---[NoImage] at MeGUI.AviSynthAudioEncoder.encode()
--[NoImage] Inner exception: null
-[Information] [02/02/2010 11:51:30] Job completed
i alrady moved files on another HDD, reindexed it, nothing works..i always get MeGui close with error.
can someone help me?
please... this happen ONLY on this file, i've processed many of them last night
PS:
Last one
[Error] Log for job9 (audio, Discovery Sci @12d2fcfa.Joined PID 5dd L2 2ch 48 160 DELAY -308ms.mp2 -> Discovery Sci @12d2fcfa.Joined PID 5dd L2 2ch 48 160 DELAY 0ms.mp3)
-[Information] [02/02/2010 20:28:09] Started handling job
-[Information] [02/02/2010 20:28:09] Preprocessing
-[NoImage] Avisynth script
--[NoImage] LoadPlugin("V:\megui2\tools\avisynth_plugin\NicAudio.dll")
--[NoImage] NicMPG123Source("Q:\1- iTUNES\Discovery Sci @12d2fcfa\Discovery Sci @12d2fcfa.Joined PID 5dd L2 2ch 48 160 DELAY -308ms.mp2")
--[NoImage] DelayAudio(-308.0/1000.0)
--[NoImage] 6<=Audiochannels(last)?x_stereo29484f8215994d508e67d25fa3faff74(ConvertAudioToFloat(last)):last
--[NoImage] Normalize()
--[NoImage] 32==Audiobits(last)?ConvertAudioTo16bit(last):last
--[NoImage] return last
--[NoImage] function x_stereo29484f8215994d508e67d25fa3faff74(clip a)
--[NoImage] {
--[NoImage] fl = GetChannel(a, 1)
--[NoImage] fr = GetChannel(a, 2)
--[NoImage] c = GetChannel(a, 3)
--[NoImage] lfe = GetChannel(a, 4)
--[NoImage] sl = GetChannel(a, 5)
--[NoImage] sr = GetChannel(a, 6)
--[NoImage] l_sl = MixAudio(fl, sl, 0.2929, 0.2929)
--[NoImage] c_lfe = MixAudio(lfe, c, 0.2071, 0.2071)
--[NoImage] r_sr = MixAudio(fr, sr, 0.2929, 0.2929)
--[NoImage] l = MixAudio(l_sl, c_lfe, 1.0, 1.0)
--[NoImage] r = MixAudio(r_sr, c_lfe, 1.0, 1.0)
--[NoImage] return MergeChannels(l, r)
--[NoImage] }
-[NoImage] Commandline used: --abr 128 -h - "{0}"
-[Information] [02/02/2010 20:28:09] Encoding started
-[Information] [02/02/2010 20:28:09] Encode thread started
-[Information] [02/02/2010 20:28:09] Avisynth script environment opened
-[Error] An error occurred
--[NoImage] Exception message: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
--[NoImage] Stacktrace
---[NoImage] at MeGUI.AviSynthClip.dimzon_avs_init_2(IntPtr& avs, String func, String arg, AVSDLLVideoInfo& vi, AviSynthColorspace& originalColorspace, AudioSampleType& originalSampleType, String cs)
---[NoImage] at MeGUI.AviSynthClip..ctor(String func, String arg, AviSynthColorspace forceColorspace, AviSynthScriptEnvironment env)
---[NoImage] at MeGUI.AviSynthAudioEncoder.encode()
--[NoImage] Inner exception: null
-[Information] [02/02/2010 20:28:15] Job completed
Guest
2nd February 2010, 22:33
What is the file and where did you get it?
forum king
3rd February 2010, 20:36
guys a lot has changed since sharktooth became inactive and pleasently since zathor took megui up :)
i have a few very simple things...
1 ... which profiles in new megui correspond to HQ Slower ones ?
2 ... secondly can we now safely turn b pyramid to make our rips DXVA compatible ?
3 ... which are the settings one should alter while encoding on low bitrates ( i means 600 to 1000 wrt to smaller to higher resolutions) as a lot of new things have been added.
4 ... i am talking about deblocking , subme , trellis , pfarmes , ref frames , b frames and macroblocks... please suggest which settinsf are optimal for low bitrate encoding
Regards
sorry if i am being too noob , but i just want to expand my knowledge about it all.
quantum5uicid3
3rd February 2010, 22:34
1. there isn't, just use the same bitrate as before and adjust the preset slider until you get a comparable speed as before.
2. yes it has been "fixed." there are no restrictions for newer nvidia cards+mpc-hc dxva decoder. other decoders and maybe still all ATI cards force level 4.1
3-4. just put the preset slider as slow as you can bear
i put preset on placebo, but change ME algorithm to multihex
forum king
4th February 2010, 04:51
Thanks quantum matey :)
a few Q
.. i am thinking of usinf -2,-1 as deblocking , and subme 7 ( coz slider does stuff but i believe some tweaks are inevitable like the deblocking , bframes (10) , ref frames 8-10 , off course ME algorithm..
all the other settings i am leaving as they were in the earlier unrestricted 2 pass..
are these reasonable ?
help_me!
4th February 2010, 17:13
I don't understand how i can get 5 Reframes.
I configured this profile:
http://www.abload.de/thumb/3yddg.jpg (http://www.abload.de/image.php?img=3yddg.jpg) http://www.abload.de/thumb/19coj.jpg (http://www.abload.de/image.php?img=19coj.jpg) http://www.abload.de/thumb/4tgyk.jpg (http://www.abload.de/image.php?img=4tgyk.jpg) http://www.abload.de/thumb/2pckl.jpg (http://www.abload.de/image.php?img=2pckl.jpg) http://www.abload.de/thumb/5icb8.jpg (http://www.abload.de/image.php?img=5icb8.jpg)
with the follwoing result:
What must i change to get this?
I have the same problem. Anyone can help us? :)
poisondeathray
4th February 2010, 17:21
I don't understand how i can get 5 Reframes.
You entered 5 and got 5. (look at your 4th screenshot). What's the problem?
EDIT: Oh I See, there is a difference in mediainfo. It reports 4 at the top and 5 at the bottom for the encoding settings. Perhaps mediainfo is reading it incorrectly?
Format settings, ReFrames : 4 frames
Encoding settings : cabac=1 / ref=5
You have to use a stream analyzer like h264visa or streameye to be certain what it really is, mediainfo just reads the header and maybe incorrect
What does the log file say?
quantum5uicid3
4th February 2010, 17:46
one of the options lowers --ref by one. i forgot the details, b-pyramid perhaps. it's expected.
Fr4nz
5th February 2010, 13:23
I upgraded to the latest version of x264 last night and now It crashes anytime I try running a job. I reverted back to the previous version and it's working fine now.
Just thought i'd give everyone a heads up.
Same thing here: had to revert from 1416 to 1400. It seems that all 1416 builds are affected (not only the komisar build bundled with MeGUI);
Oh Zathor, I'd like to ask you also another thing: actually MeGUI tries to force you to use the "official" x264 build downloaded from MeGUI repository (if I use a custom build it always asks me to upgrade); it would be nice if we could use more easily customized builds, as the old versions of MeGUI let you do.
Ah, my specs:
Win7 64-bit;
Intel E6750 (but it crashes also on my other PC, an AMD quad-core);
2Gb of RAM;
etc.
Command-line used:
program --profile high --level 4.1 --preset slow --tune film --pass 2 --bitrate 3440
--stats ".stats" --thread-input --b-pyramid normal --slices 4 --vbv-bufsize 15000
--vbv-maxrate 15000 --aud --nal-hrd --threads 4 --output "output" "input"
Zathor
5th February 2010, 15:25
Oh Zathor, I'd like to ask you also another thing: actually MeGUI tries to force you to use the "official" x264 build downloaded from MeGUI repository (if I use a custom build it always asks me to upgrade); it would be nice if we could use more easily customized builds, as the old versions of MeGUI let you do.
If you want to have your own build you can disable the update check for this file and copy your files into the \tools\x264 directory.
And what kind of crash do you get? Is MeGUI crashing or x264 or... and what kind of error message do you get. Can you provide more details about your avs file and the source file? I would like to reproduce this problem.
Fr4nz
5th February 2010, 16:02
If you want to have your own build you can disable the update check for this file and copy your files into the \tools\x264 directory.
Yes I know this, but old version of MeGUI didn't bother for an update if it found a custom x264 build... :D
And what kind of crash do you get? Is MeGUI crashing or x264 or... and what kind of error message do you get. Can you provide more details about your avs file and the source file? I would like to reproduce this problem.
Apparently the culprit is x264; the behaviour is system dependent: on my Intel it doesn't crash, it simply freezes (and the CPU stays at 100%); on my father's AMD a message is returned (atm I don't remember it, I'm going to give you an update later when I can access it again), but when I close the window of that message, the x264 window remains open, so it also seems a lock-up at the end.
The avs file I'm using is this:
DirectShowSource("E:\work\Condiviso\INGLORIOUS\inglorious.mkv", fps=23.976, audio=false, convertfps=true)
BilinearResize(1280,720) # Bilinear (Soft)
In this case the source is an original Inglorius Bastards blu-ray disc, italian version, extracted with makemkv, but note that lockups occur with every movie I've tried. Another curious thing is that lockups occur always at frame 10290 during the first pass.
I've tried also to use an unpatched x264 build and exclude settings regarding blu-ray compliancy (NAL-HRD), but the problem persists.
The only solution is reverting back to x264 version 1400.
MrCommunistGen
6th February 2010, 00:52
I don't understand how i can get 5 Reframes.
I'm not entirely sure what ReFrames actually means in MediaInfo (I've been using it pretty much as long as it has existed) but it is not an actual measure of reference frames. For a lot of my older x264 based encodes it was way off. Back then I was using ref=3 and MediaInfo often shows ReFrames of 7 or more if I remember correctly... I'm not at home right now (to clarify: if I check my old encodes with the current version of MeGUI). With newer builds (or maybe my newer settings) the MediaInfo reported ReFrames has gotten closer to the actual number of references, but as you've found it does not always represent the actual value.
If you check your log after the encode you will see that x264 actually is using 5 reference frames (based on your command line).
-mcg
TheSane
7th February 2010, 09:48
I have the same problem. Anyone can help us? :)
So, i have the conclusion of the mysterious "bug".
I recoded the movie once more and disabled "b-Pyramid" and the correct reframe where used.
The only thing i don't tested yet, when i increase the reframe number with activated b-pyramid, if there is a decrease of one or the fall back to 4 reframes.
one of the options lowers --ref by one. i forgot the details, b-pyramid perhaps. it's expected.
You could be right, thanks for your hint.
I'm not entirely sure what ReFrames actually means in MediaInfo (I've been using it pretty much as long as it has existed) but it is not an actual measure of reference frames. For a lot of my older x264 based encodes it was way off. Back then I was using ref=3 and MediaInfo often shows ReFrames of 7 or more if I remember correctly... I'm not at home right now (to clarify: if I check my old encodes with the current version of MeGUI). With newer builds (or maybe my newer settings) the MediaInfo reported ReFrames has gotten closer to the actual number of references, but as you've found it does not always represent the actual value.
If you check your log after the encode you will see that x264 actually is using 5 reference frames (based on your command line).
-mcg
Can't approve your experience.
forum king
7th February 2010, 18:21
hey folks please advise if you can , i ll be thankful folks :)
1.. on the first page of this thread zarhor says use 1056 build and install and update, which update server to use
Default or development ( its not mentioned )
2.. The newer builds have certainly raised the bar of encoder settings :D
i wanted to ask how much subme is enough if are encoding at low bit rates i mean 600 to 1000 , also how mant ref frames and bframes are sufficient ( i am concerned more about quality and less about speed but no doubt a balanced setting will be prefeered which is not very slow... )
3 .. i am unable to decide upon deblocking , sometimes 0.0 give very good results and sometimes it doesnt, i find edges horribly blurred..
regards
TDC.net
7th February 2010, 22:45
Having issues with the x264 build from the dev-server here.
The resulting video does not play correctly with ffdshow (skipping several frames, repeatable) and it cannot be muxed with MKVtoolnix.
I coded the file again with the new x264 build and again it failed.
Downgraded to x264 from stable server: File is 100% ok, muxes fine.
Any idea what's wrong with the dev-build?
Thanks
Dark Eiri
8th February 2010, 01:32
I'm having no issues with it. Working flawlessly with several encodes, muxed to MKV just fine.
forum king
8th February 2010, 04:27
hey folks please advise if you can , i ll be thankful folks :)
1.. on the first page of this thread zarhor says use 1056 build and install and update, which update server to use
Default or development ( its not mentioned )
2.. The newer builds have certainly raised the bar of encoder settings :D
i wanted to ask how much subme is enough if are encoding at low bit rates i mean 600 to 1000 , also how mant ref frames and bframes are sufficient ( i am concerned more about quality and less about speed but no doubt a balanced setting will be prefeered which is not very slow... )
3 .. i am unable to decide upon deblocking , sometimes 0.0 give very good results and sometimes it doesnt, i find edges horribly blurred..
regards
guys also .. after the last 2 updates i am seeing that the settings which used to give me decent quality are encoding lot of blocks and blurred edges despite good bitrate ( then before )
could some one suggest me how can i reverse all the chnges that have been made in last 2 updates ( the first had some files other than x264 build updated and the second has x264 and a few more ) after that i didnt update at all.. :(
Zathor
8th February 2010, 17:22
Yes I know this, but old version of MeGUI didn't bother for an update if it found a custom x264 build... :D
MeGUI has never ever checked the files. So it doesn't matter if you copy a custom build to the directoty as long as the file names are still present (x264.exe, x264_64.exe, vfw4x264.exe and avs4x264.exe).
The only solution is reverting back to x264 version 1400.
I have forced a downgrade at the development server now. I have still no problems but there have been several reports like yours.
1.. on the first page of this thread zarhor says use 1056 build and install and update, which update server to use
Default or development ( its not mentioned )
Use the server you like. The default / stable one should be more stable and with the development server you get the latest tools and builds.
guys also .. after the last 2 updates i am seeing that the settings which used to give me decent quality are encoding lot of blocks and blurred edges despite good bitrate ( then before )
It may be that the video is fine but your decoder can't play it properly. Try adding --weightp 0 to the custom command line.
aegisofrime
8th February 2010, 17:49
I'm not sure if this will help, but I have been using an AMD optimized 1416 version compiled by outlaw87 over at Doom10 without any problems. My encodes are TGMC'ed DVD videos...
Here's the link to grab the build, if you guys want to try it out.
http://doom10.org/index.php?topic=26.msg1265#msg1265
My settings are simply CRF 21 with Preset "Slower", tuning Film. Nothing else.
Fr4nz
8th February 2010, 21:53
I have forced a downgrade at the development server now. I have still no problems but there have been several reports like yours.
Okay. I wrote in the x264 subforum, let's see if someone can make some light on this issue.
mozzle
9th February 2010, 01:35
Okay. I wrote in the x264 subforum, let's see if someone can make some light on this issue.
Just for the record, I too had issues with x264 1416. My encode would go for about an hour and then x264 would crash. It did this twice in a row so I reverted to 1400 and things worked fine again.
quantum5uicid3
9th February 2010, 19:45
i also have no issues with 1416. what decoder and settings are you guys using?
Fr4nz
9th February 2010, 22:58
i also have no issues with 1416. what decoder and settings are you guys using?
I'm using the latest ffdshow tryouts as decoder and these are the "usual" settings I use under MeGUI:
program --profile high --level 4.1 --preset slow --tune film
--pass 2 --bitrate XXXX --stats ".stats" --thread-input
--b-pyramid normal --slices 4 --vbv-bufsize 15000 --vbv-maxrate
15000 --aud --nal-hrd --threads 4 --output "output" "input"
thedozer
11th February 2010, 18:47
Having issues with the x264 build from the dev-server here.
The resulting video does not play correctly with ffdshow (skipping several frames, repeatable) and it cannot be muxed with MKVtoolnix.
I coded the file again with the new x264 build and again it failed.
Downgraded to x264 from stable server: File is 100% ok, muxes fine.
Any idea what's wrong with the dev-build?
Thanks
I'm having the exact same problem.
What x264 build did you use to fix the problem?
rapscallion
12th February 2010, 21:03
see post # 767 above. Also the dev server will now downgrade to 1400, just click on the "update" option to see it.
Zathor
12th February 2010, 21:38
Also the dev server will not downgrade to 1400
I'm confused. The downgrade works for me. Maybe you have mixed up not and now?
rapscallion
12th February 2010, 22:25
Z...that's exactly what happenned.Post edited.
thedozer
12th February 2010, 22:32
I tried 1400 build and it does the same (skipping frames) but not as always, the best build I could find is 1376 which is in the stable update
help_me!
13th February 2010, 11:08
I can confirm that:
Megui from development server produces videos that neither the DXVA decoder of MPC-HC nor FFDSHOW can decode properly.
Megui from stable server produces videos that play perfectly on both.
Most likely it's the newer x264 versions that are problematic.
Zathor
13th February 2010, 13:02
I can confirm that:
Megui from development server produces videos that neither the DXVA decoder of MPC-HC nor FFDSHOW can decode properly.
Megui from stable server produces videos that play perfectly on both.
Most likely it's the newer x264 versions that are problematic.
So you have changed nothing beside the x264 build? Are the problems reproducable with 1400/1416? Please provide more information about your system (especially 32/64 bit), the source file, avs used and the megui log (command line for x264).
help_me!
13th February 2010, 15:22
So here's what I did for you:
Uninstalled Megui, and did a fresh install of 1056.
Updated to the latest core and tools from stable server.
Encoded a video (Unrestricted DXVA - Very High Quality, preset: slower)
It plays beautifully.
Updated the x264 (only) from the development server. (I have also tested to update the core and tools, the problem is exactly the same)
Encoded the same video with the same settings.
Upon playback MPC-HC DXVA crashes, MPC-HC with FFDSHOW decoding skips tons of frames.
Both of the videos are included in the following rar: http://www.massmirror.com/a32d8720450fe289baf163e6f8ac531b.html
The one with the underscore "_" is the problematic.
I'm using Windows 7 x64, a quad core, source file is a 291MB HFYU avi, script consists of opening the source with AviSource and converting to YV12 with ConvertToYV12.
Zathor
13th February 2010, 15:35
I'm using Windows 7 x64
x64 - so maybe vfw4x264.exe or x264_64.exe could be part of the problem. Please rename the file vfw4x264.exe and rename avs4x264.exe to vfw4x264.exe. Does the newly encoded file still crash? If yes, then rename x264_64.exe to something else and rename x264.exe to x264_64.exe. Does the new encode crash? Rename the original vfw4x264.exe back to vfw4x264.exe and try again. If it is still not working then delete/rename vfw4x264.exe and rename the original x264.exe back to x264.exe and try it again.
help_me!
13th February 2010, 15:51
Tried all of the combinations.. result is always a file that crashes upon playback.
thedozer
13th February 2010, 18:17
I'm having the same results as "help_me!" in a Win7 32bit system with a Core2Duo processor
I also encoded different types of video files like: AVI(Xvid), MP4(H264) and MKV, and I always have the same result which is skipping frames mostly at the beginning of the videos.
I only use FFDShow for decoding though.
mozzle
13th February 2010, 22:16
This x264 issue is bizarre. Some folks have no issues while others are experiencing crashes and still others are successfully encoding but with a bunch of skipped frames.
WTF?!?
Inspector.Gadget
13th February 2010, 22:26
No issues here with the x264 1400 downgrade on Vista x64 and muxed with mkvmerge / then using Haali -> MPC-HC internal DXVA decoder to play back resulting file.
horvathd
13th February 2010, 22:55
I made some testing around the x264 r1416 and the problem is with the builds by Komisar, not the x264 itself.
I don't know which versions were included into MeGUI (generic or core2, 32 or 64 bit). The main problem is that the generic 32 and 64 bit executables are the same, probably due mislabeling. They should be the the 64 version because they don't run on my PC. (The core2 32 and 64 bit version also don't run.)
I suggest grab an executable from the following topic http://doom10.org/index.php?topic=3.0 or build one yourself. I did the latter one, and left out the unused lavf and ffms input methods.
thedozer
13th February 2010, 23:28
@horvathd:
For my tests I used 1400 & 1416 builds from http://x264.nl and still the same problem with those skipped frames.
I should mention that I only mux into MKV, and skipped frames sometimes play normally after muxing the encoded video with audio using mkvmerge.
saint-francis
13th February 2010, 23:35
I must say that there are no problems on my end with the Dev build. I've been using it all the time too.
horvathd
13th February 2010, 23:42
@thedozer:
Then probably you should report this issue in this topic (http://forum.doom9.org/showthread.php?t=108571) to the developers.
quantum5uicid3
13th February 2010, 23:46
someone upload some clips
help_me!
14th February 2010, 02:45
I did: http://forum.doom9.org/showthread.php?p=1373819#post1373819
The one with the _ (encoded with the x264 from the dev. server) doesn't play correctly.
The other one (encoded with the x264 from the stable server) plays without problems.
horvathd
14th February 2010, 08:45
I did: http://forum.doom9.org/showthread.php?p=1373819#post1373819
The one with the _ (encoded with the x264 from the dev. server) doesn't play correctly.
The other one (encoded with the x264 from the stable server) plays without problems.
Maybe you have the same problem I did. Check these posts: http://forum.doom9.org/showthread.php?p=1371125#post1371125
Poutnik
14th February 2010, 09:42
Vulnerability scan of Personal software inspector by Secunia.com claims that
mplayer.exe 0.x version in mencoder tool folder of MeGUI is not supported anymore.
( it means in general authors of such product either did not respond to several vulnerability notifications,
or they responded or actively announced the product version is not supported anymore )
Edit: It seems all revealed vulnerabilities for MP 0.x seems patched, but it need not to be checked anymore.
http://secunia.com/advisories/product/2129/?task=advisories
OTOH, with mplayer 1.x the situation is not better as far as several vulnerabilities are unpatched
Both of Highly Critical vulnerabilities of all 4 unpatched issues
seems related to media streaming, so in context of MeGUI they do not look like big issue.
http://secunia.com/advisories/product/2255/?task=advisories
Zathor
14th February 2010, 11:59
Honestly said I have no idea anymore regarding the x264 problem. Can someone with the problem please try to encode from the command line with the official build 1416 from x264.nl? (Use the command line from the MeGUI log - replace vfw2x264.exe with x264.exe in the command line if running on x64 and of course replace the file x264.exe with the one from x264.nl). If the problem can be reproduced this way with build 1416 and with build 1376 (from the stable server) it is gone I assume that the x264 build is the source of the problem.
help_me!
14th February 2010, 12:44
Using 32bit 1416 from x264.nl (not messing with vfw) and the same settings as previously produces a file that:
- the MPC-HC DXVA decoder doesn't crash this time but now has the same problem of skipping frames like the FFDSHOW decoder did (I've never tested 1416 before so maybe that's why there's slightly different behavior from 1400)
- FFDSHOW skips frames as previously with megui's dev. server x264 1400
Using 32bit 1376 from x264.nl:
- with MPC-HC DXVA decoder plays great!
- with FFDSHOW plays great!
quantum5uicid3
14th February 2010, 14:32
sorry didnt see them. can you upload a clip of the source plz
Fr4nz
14th February 2010, 16:59
Hi Zathor, I have good news!
With latest MeGUI development version (0.3.3.5 with all the components updated) I don't have anymore freezing problems with unpatched 264.nl 1416 64-bit build. I guess that something in MeGUI code was updated and solved this issue.
Now I'm gonna try Komisar 1416 NAL-HRD patched build in order to see if it also works with MeGUI...
UPDATE: Okay, the culprit seems to be Komisar's 1416 builds: they keep freezing; don't use them.
UPDATE2: Found that probably there's a bug in NAL-HRD patch; see here (http://forum.doom9.org/showpost.php?p=1374315&postcount=2988);
help_me!
14th February 2010, 18:58
sorry didnt see them. can you upload a clip of the source plz
http://www.megaupload.com/?d=D1T7FUXN
Here's a 4 second clip from the 10 second Huffyuv source. Size is a bit big as you can understand (120MB) but Megaupload should give you good speeds. :)
quantum5uicid3
15th February 2010, 11:29
http://www.megaupload.com/?d=D1T7FUXN
Here's a 4 second clip from the 10 second Huffyuv source. Size is a bit big as you can understand (120MB) but Megaupload should give you good speeds. :)
komisar 1416/hrd both 32 and 64 are working flawlessly on this too. plz post your settings, but i think a decoding chain issue is more likely though, like the haali media splitter prob horvathd pointed out.
addition:
i tried 32bit and 64bit outputting to mp4, mkv, and raw. all played back perfectly with both dxva and ffdshow...
Fr4nz
15th February 2010, 11:46
komisar 1416/hrd both 32 and 64 are working flawlessly on this too. plz post your settings, but i think a decoding chain issue is more likely though, like the haali media splitter prob horvathd pointed out.
addition:
i tried 32bit and 64bit outputting to mp4, mkv, and raw. all played back perfectly with both dxva and ffdshow...
Actually latest Komisar's NAL-HRD patched build is bugged (culprit is the NAL-HRD patch used). See here (http://forum.doom9.org/showpost.php?p=1374315&postcount=2988) and here (http://forum.doom9.org/showpost.php?p=1372665&postcount=769).
quantum5uicid3
15th February 2010, 11:59
what's the trigger? i'm enabling nalhrd on all encodes and yet to have an issue. is it a certain vbv?
Fr4nz
15th February 2010, 12:07
what's the trigger? i'm enabling nalhrd on all encodes and yet to have an issue. is it a certain vbv?
This is what I get when using avs2yuv (but it freezes also with MeGUI):
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
Assertation failed!
Program: E:\dvd\avs2yuv\x264_x64.exe
File: encoder/set.c, Line 679
Expression: dpb_output_delay < pow( 2, sps->vui.nal_hrd_parameters.i_dpb_output_delay_length )
E:\work\Up.2009.1080p.avs:
1920x1080, 2500000/104271 fps, 138282 frames
Output error: wrote only 2676405 of 3110400 bytes
Fatal Error: The encoder has encountered an unexpected error!
quantum5uicid3
15th February 2010, 12:16
i think help_me is having different issues, but hopefully that's it. u should remove anything that could insinuate rule 6 violations btw.
help_me!
15th February 2010, 15:23
edit See below
help_me!
15th February 2010, 15:28
Forget it guys!!
This was the problem:
Maybe you have the same problem I did. Check these posts: http://forum.doom9.org/showthread.php?p=1371125#post1371125
:thanks::thanks::thanks:
edit I feel stupid for wasting your time! I will be more careful from now and on! Thanks to all who helped me.
mikey1984
15th February 2010, 21:16
Any of u guys have problem with megui adding "work tasks" to que twice?
I mean, when i add two x264 passes to ques, 1st then 2nd, then i go to que view, and both jobs are added twice, 1st,2nd,1st,2nd....
Kinda bizzare, and i noticed it happening after last core update to 3.3.5... anyone else with such problem?
EDIT:
After some looking around, i noticed, that while using bitrate calculator and applying its calculations to already pre-saved x264 profiles, it automaticaly changes my "2 pass 1st pass" and "2pass 2nd pass" x264 modes in those presets into "Automated 2 pass", thus it gets added "twice" to work que.
Any way to fix this issue? Seems like there is some problem within bitrate calc.
Fr4nz
15th February 2010, 22:53
Hi Zathor,
in case you didn't knew this: syntax for --nal-hrd parameter has been changed in latest revisions. See here (http://forum.doom9.org/showpost.php?p=1374503&postcount=85).
Zathor
15th February 2010, 23:01
After some looking around, i noticed, that while using bitrate calculator and applying its calculations to already pre-saved x264 profiles, it automaticaly changes my "2 pass 1st pass" and "2pass 2nd pass" x264 modes in those presets into "Automated 2 pass", thus it gets added "twice" to work que.
Thanks, the change in 0.3.3.5 has been too agressive. I will fix it with the next dev (which is likely the stable) build.
Hi Zathor,
in case you didn't knew this: syntax for --nal-hrd parameter has been changed in latest revisions. See here (http://forum.doom9.org/showpost.php?p=1374503&postcount=85).
Ok, I will change it in one of the next builds. I think I will push out a stable build first still with x264 1376 and change the nal-hrd handling with the first dev build.
Lyle_JP
16th February 2010, 08:57
I don't suppose you'd be willing to push out the x264.nl or techouse r1376. The Jeeb's and Komisar builds never play well with my equipment. I can't be the only one.
help_me!
16th February 2010, 11:13
FYI this clip: http://www.massmirror.com/4931a8e5af68704161fde207bae78fb7.html crashes x264_64 from the very first moment of encoding.
Tried the x264 build from both stable and dev. servers.
I eventually encoded it from CLI with a x264.nl 32bit build. As it was the only video that failed from the 30 or so clips I encoded successfully yesterday night, I didn't bother researching the cause. Perhaps a vfw4x264 issue? I uploaded it in case anyone wants to experiment with it.
edit From the very few tests I did, I don't think that settings matter at all but I tried CRF only encodes..
Zathor
16th February 2010, 11:15
I don't suppose you'd be willing to push out the x264.nl or techouse r1376. The Jeeb's and Komisar builds never play well with my equipment. I can't be the only one.
The problem is that the x264.nl build has no nal-hrd support and therefore a patched one has to be used. This will change sometime in the future as soon as the support for nal-hrd will be implemented in the default x264 builds.
Fr4nz
16th February 2010, 11:19
The problem is that the x264.nl build has no nal-hrd support and therefore a patched one has to be used. This will change sometime in the future as soon as the support for nal-hrd will be implemented in the default x264 builds.
After some testing, latest Komisar patched build seems to work well Zathor (keeping in mind that NAL-HRD parameter has a different syntax!), so you could include it in development version of MeGUI without problems...
SacredCultivator
16th February 2010, 20:37
I guess I should have asked this a while back as I've been doing it manually in the past.
When there are updates for the x264 builds, when updating, does that only update the 32-bit version? Or does it also update the 64-bit, as I know the 64-bit doesn't always get updated at the same time as the 32-bit.
So just thought I would ask, even though I generally manually dl the 64-bit.
MuLTiTaSK
16th February 2010, 20:52
I guess I should have asked this a while back as I've been doing it manually in the past.
When there are updates for the x264 builds, when updating, does that only update the 32-bit version? Or does it also update the 64-bit, as I know the 64-bit doesn't always get updated at the same time as the 32-bit.
So just thought I would ask, even though I generally manually dl the 64-bit.
no need to update manually unless you want to use a special build both 32-bit and 64-bit builds always get updated together just use the ones included and save yourself the trouble plus you never know what x264 switches might change;)
avs4x264.exe
vfw4x264.exe
x264.exe
x264_64.exe
SacredCultivator
16th February 2010, 21:03
@MuLTiTaSK: Ahh, thanks for the response, again, I just wasn't sure, so I always did it manually just to be 100% sure that I had the latest 64-bit build. But now that you mention it updates both, shall leave it up to that, thanks.
Hiritsuki
17th February 2010, 06:24
I think this problem is megui dev server update new a method for x64 suport
I'd useing Windows7 x64 and mgui update dev server no problem
x86 maybe wrong in this way
quantum5uicid3
17th February 2010, 12:32
heres new preset with bluray and avchd updated for new hrd switch. i added a "max compatibility (Dxva)" with level 4.1 and vbv 40000 too. if it don't work with all cards support avc acceleration plz post.
http://www.mediafire.com/?zeyydehngrm
[ReX]
18th February 2010, 06:15
There's a new version of AVI-Mux GUI, 1.17.8.3.
Contains fixes for a couple of problems: reading certain DTS files, reading certain AAC files, settings dialog was cropped when the system font size was larger than normal, should not require compatibility mode setting on Vista and Windows 7 anymore. It's partially migrated from C-string functions to STL. This is NOT PROPERLY TESTED, I just want to release it, otherwise I'd never get it out. Maybe you want to test...
http://www.alexander-noe.com/video/amg/AVI-Mux_GUI-1.17.8.3.zip
ninja_racoon
18th February 2010, 15:38
can I use x264 64bit and avisynth 32bit using megui?
HeadlessCow
18th February 2010, 16:03
It does that automatically, ninja_racoon.
rapscallion
18th February 2010, 23:20
heres new preset with bluray and avchd updated for new hrd switch. i added a "max compatibility (Dxva)" with level 4.1 and vbv 40000 too. if it don't work with all cards support avc acceleration plz post.
http://www.mediafire.com/?zeyydehngrm
What is the "new" hrd sw ? The "vbr" following hrd has no (-), but is that it?
Also, the post referenced above by @Fr4nz indicates x264 build 1442 for the new sw.
The current dev build is 1400 , so we should not use the new presets yet, right ?.
quantum5uicid3
19th February 2010, 05:02
that's it :)
yeah, im using komisar1442. it should be the standard going forward.
ninja_racoon
20th February 2010, 06:19
How do I turnoff the subtitles getting hardsubbed in megui?
Barough
20th February 2010, 12:36
New MediaInfo released, v0.7.2.8
http://mediainfo.sourceforge.net/en/Download/Windows
poisondeathray
20th February 2010, 15:57
How do I turnoff the subtitles getting hardsubbed in megui?
Takeout textsub() line in the avs script
or
Remove soft subs from the source
Zathor
20th February 2010, 18:52
0.3.3.6
- update MediaInfo library and its wrapper to the latest release (0.7.28)
- [UpdateWindow] moved the MediaInfo files to a separate download package
- [Calculator] encoding mode will only be changed if profile encoding mode is const. quality or const. quantizer. Bug #2952574
- [dgiReader] enhanced error handling
- [SourceDetector] enhanced error handling in analyseFF. Bug #2810830
- [Calculator] settings can only be applied if bitrate > 0. Bug #2812840
- [AviSynthWindow] enabling clever anamorphic encoding applies immediately the selected settings. Bug #2827053
EDIT:
If someone wants to test the newer x264 builds you can replace the x264.exe and x264_64.exe with newer builds. If using nal-hrd you have to add e.g. --nal-hrd vbr to the custom command line.
Zathor
20th February 2010, 21:52
0.3.3.7
- [JobControl] error handling added. Bug #2279852
- [x264Encoder] corrected scenecut handling. Bug #2942446
- [LogItem] error handling added. Bug #2947565 + #2925500
himan2001
21st February 2010, 07:25
eac3to (auto-update) is still on 0 Bytes, maybee wrong or invalid zip compression on update-server.
Zathor
21st February 2010, 09:35
eac3to (auto-update) is still on 0 Bytes, maybee wrong or invalid zip compression on update-server.
Thanks, the wrong file name has been fixed.
hajj_3
22nd February 2010, 16:18
regarding:
http://i45.tinypic.com/35bi0x5.jpg
You can choose not to use a built-in de-interlacer, but disabling the checkbox would be better, as for the resizer you have to choose 1 unfortunately even when you select nvidia's resizer, this causes the video not to encode and gives you the following error:
http://i50.tinypic.com/fjlts5.jpg
Please disable the dropdown box for the resizer and don't add any info to the .avs script when we select nvidia's resizer.
Thanks zathor :)
Zathor
23rd February 2010, 19:53
0.3.4.1
- [x264Encoder] added support for new nal-hrd (requires x264 revision 1442 or higher)
rapscallion
23rd February 2010, 19:59
Zathor, what exactly is the benefit of the "new" nal-hrd sw?
hajj_3
23rd February 2010, 20:03
nice to see x264 1442 support, hope you can fix the stuff 3 posts up from this post.
Zathor
23rd February 2010, 20:09
Zathor, what exactly is the benefit of the "new" nal-hrd sw?
The syntax of x264 for nal-hrd has changed. --nal-hrd has been the old switch and this is the new one:
--nal-hrd <string> Signal HRD information (needed e.g. for Blu-Ray compliance)
- vbr, cbr. (requires vbv-bufsize; cbr-hrd not allowed in .mp4)
nice to see x264 1442 support, hope you can fix the stuff 3 posts up from this post.
Hopefully :)
kool
23rd February 2010, 20:51
Hi,
I have tried to analyse Blu-Ray source for test purpose throw megui with dgindexnv, it toke very long almost after 30min i haven't got any result.
rack04
23rd February 2010, 20:57
Hi,
I have tried to analyse Blu-Ray source for test purpose throw megui with dgindexnv, it toke very long almost after 30min i haven't got any result.
Try closing the preview window before analyzing.
kool
24th February 2010, 01:31
That way it works fine, what would be the reasone when it is not working when the preview window is on? and one more strenge thing what I've come across is, when I crop and chose the nvidia resizer the resolution shewed up 1920x552 instead of 1920x816, the script come out after analysing as below
LoadPlugin("C:\Program Files (x86)\megui\tools\dgindexnv\DGDecodeNV.dll")
DGSource("C:\Users\kool\Desktop\test\test.dgi",fieldop=0, resize_w=1920, resize_h=816)
#deinterlace
crop( 0, 132, 0, -132)
#resize
#denoise
and AvsP preview http://i48.tinypic.com/9a0l1f.png
Inspector.Gadget
24th February 2010, 01:44
In that script, you're resizing before cropping. If you want to use the NV resizer, you must also use the NV crop rather than the Avisynth crop for any pre-resize cropping tasks.
hajj_3
24th February 2010, 11:36
p.s please add the following size to the bitrate calculator: 746mb (1/6 dvdr)
x264 build 1462 is out now btw, nice changelog too:)
Nightshiver
24th February 2010, 18:53
Is it that hard for you to just set the bitrate yourself? The calc has even numbers, and 746 is just a weird size and besides that, it's just to simple to increase the bit rate yourself to get that size.
SledgeHammer_999
24th February 2010, 20:20
A regression from 0.3.3.5:
In the calculator user-defined file sizes aren't saved after closing the calculator.(either by apply or cancel).
Feature request:
After each update remember user-defined file sizes and don't delete them.
rapscallion
24th February 2010, 22:47
Speaking of the calculator....I still find that it's on the high side for m2ts container in both dvd5 and dvd9 sizes.
So, I've been able to adjust accordingly. However I'm at a loss for bd25 size. Suggestions welcome.
Anyone else ?
Zathor
24th February 2010, 23:55
0.3.4.2
- [AviSynthProfileConfigPanel] if clever anamorphic encoding is enabled the dropdown box will be also enabled
- [AviSynthWindow] openning a file also triggers the clever anamorphic encoding event. Bug #2957647
- [UpdateWindow] set file changed time of extracted files
- [UpdateWindow] files which need a reboot will also be backuped if selected
- update ICSharpCode.SharpZipLib.dll
XhmikosR
24th February 2010, 23:59
Zathor, please update the SVN; that's why it exists. Thanks.
Zathor
25th February 2010, 00:03
Speaking of the calculator....I still find that it's on the high side for m2ts container in both dvd5 and dvd9 sizes.
So, I've been able to adjust accordingly. However I'm at a loss for bd25 size. Suggestions welcome.
The m2ts calculation is experimental. I'm open for any suggestions to improve this part.
Feature request:
After each update remember user-defined file sizes and don't delete them.
Please post all feature requests also to the sourceforge page. Otherwise they may get lost.
Zathor
25th February 2010, 00:43
Zathor, please update the SVN; that's why it exists. Thanks.
Most of the time I update the SVN a few minutes before or a few minutes after I publish a new version. This time I had a few other things to do between these tasks. Because I am the only active developer at the moment I do it as fast and in the order and way I am able to do it - there is no other developer waiting to incorporate my code. It would be a good thing if there would be one.
If the source code is not committed a few days after a new build has been published you can remind my and I will apologize for my laziness. Please do not push me a few minutes after an update.
By the way - SVN should be up to date in all relevant parts now.
XhmikosR
25th February 2010, 01:22
Most of the time I update the SVN a few minutes before or a few minutes after I publish a new version. This time I had a few other things to do between these tasks. Because I am the only active developer at the moment I do it as fast and in the order and way I am able to do it - there is no other developer waiting to incorporate my code. It would be a good thing if there would be one.
If the source code is not committed a few days after a new build has been published you can remind my and I will apologize for my laziness. Please do not push me a few minutes after an update.
By the way - SVN should be up to date in all relevant parts now.
I know you are the only developer and I appreciate all the hard work you are doing. Don't get me wrong but sometimes you didn't commit your changes for days, although you had released a new version on the server. That's why I thought you would do the same. The SVN exists for a reason and this has nothing to do with the fact that you are the only dev. At least this is how I see it.
I just compile the latest meGUI for testing purposes and most of the times I find that a new build exists without the changes in the source code being published. Anyway, I hope you get my thinking, I didn't want to sound like I don't appreciate your work.
Lyle_JP
25th February 2010, 07:47
With b-pyramid normal now on as default (r1462 and higher), we now need a GUI switch for explicitly turning b-pyramid off.
jeremy33
25th February 2010, 12:55
I have a probleme. I encode a movie in x264 in mp4 container but when I want to mux it with mkvtoolnix 3.20 there is just a few minute of movie in my mkv.
sorry for my bad english
Inspector.Gadget
25th February 2010, 14:20
jeremy33, read the last few pages of the mkvtoolnix thread, where i believe a similar problem was reported and perhaps resolved.
quantum5uicid3
26th February 2010, 00:51
i haven't tested extensively, but i've hit 4.35-4.36GB everytime i've selected DVD5. files were a 640kbps AC3 and a raw h264 stream muxed to m2ts with tsmuxer.
himan2001
27th February 2010, 05:54
There is a Uint64 Overflow Error in The Bitratecalculator.
I try to calculate audio & video for a stream that is 21 hours in length. When i select the 1rst Audio i get uint64 Overflow Error. At the Moment it is not possible to calculate a stream for 24h length with Audio (mp3 or ac3). 24h are typical for Security video/cam for exsample.
This must be calculated with external calculator for the moment.
rkalwaitis
27th February 2010, 18:40
I have downloaded this build from scratch. Everything seems to go fine except I can not create a dv2 file. It starts to make the file but hangs. The log does not give an error as I end the abort the process myself. I am obviously missing something simple but can not figure it out. I ran the dv2 creator from the folder not using Megui and had the same problem.
poisondeathray
27th February 2010, 18:44
I have downloaded this build from scratch. Everything seems to go fine except I can not create a dv2 file. It starts to make the file but hangs. The log does not give an error as I end the abort the process myself. I am obviously missing something simple but can not figure it out. I ran the dv2 creator from the folder not using Megui and had the same problem.
what happens when you use standalone dgindex (not from megui) ?
are you sure you have a mpeg2 file?
rkalwaitis
27th February 2010, 18:49
Ill download the standalone dgindex a new an not use the one from megui and let you know what happens.
rkalwaitis
27th February 2010, 19:58
I downloaded version 1.5.7 and it hung again. I tried another source and they hang as well.
poisondeathray
27th February 2010, 20:01
rkalwaitis - what does mediainfo say about your source files?
what are they/where are they from? is it possible they are corrupted?
rkalwaitis
27th February 2010, 20:15
Streamtype MPEG2Program
profile main@main
Frame Size 720x480
Display Size (not specified)
aspect Ration 16:9 (3)
Frame Rate 29.970030
Video Type Film 99.99%
Vob Cell ID 1 3.
The files are from my original DVD ripped with DVDdecrypter, they are VOB files. Im almost positive that its not a problem with Neuron's App or Megui. I have another computer and these applications work fine on it. This is a newer computer and its giving me no love. That is why I feel as if Im missing something that I should of loaded. But for the love of me, I can't figure it out. As for being corrupted, I suppose anything is possible :) Ill redo them and try another source.
poisondeathray
27th February 2010, 20:17
is that the correct frame size? 729x480? or is that a typo?
my guess would be it's not decrypted properly
try dvdfabhd decrypter (or dvd fab, or anydvd)
rkalwaitis
27th February 2010, 20:21
Typo--okay Ill try another ripper from your suggestions and see what happens.
rkalwaitis
27th February 2010, 20:43
I guess your guess is spot on, as it worked after having tried again. Strange...
kool
2nd March 2010, 22:40
I get this error when I make d2v file through meGUI, the error start after meGUI create the d2v file and prepare it for next step croping > resize and so on...
http://i49.tinypic.com/14uwbxf.png
Installed everything fresh, no help as well.
I have tried to make the d2v through separate DGIndex, everything goes normal.
poisondeathray
2nd March 2010, 22:42
kool - you have to make an .avs script
eg.
MPEG2Source("VTS_02_2.d2v")
MeGUI has an .avs script creator in the tools menu, try plugging the .d2v into that
kool
2nd March 2010, 22:49
Can't load as well, getting the exact same error. Tried to open the d2v with AvsP and that gives me this error.
http://i47.tinypic.com/11k8ar5.png
poisondeathray
2nd March 2010, 22:52
did you follow the instructions (i.e. check avisynth version, clean out plugins)
kool
2nd March 2010, 22:56
Yes I tried as you said from meGUI > Tools > AVS Creator that also can't load the d2v. This start happen to me from yesterday, I tried to install all fresh, remove the old plugin directory and all, but that also doesn't help. Everything was all fine till yesterday, suddenly all this start to happen.
Edit:
OS is Win7 U 64-bit. Using 32-bit Avisynth and avisynth.dll is in SysWOW64 folder.
quantum5uicid3
3rd March 2010, 01:10
1. (re)install ffdshow-tryouts
2. configure it to handle raw YV12 "Raw Video"
3. (re)install avisynth
4. make sure avs file plays back in mpc-hc
and i guess maybe
5. force reinstall dgindex through the megui updater
kool
3rd March 2010, 10:01
Well actually I (re)install every single thing, ffdshow,haali,mpc-hc,avisynth and megui. I enabled the raw video section in ffdshow to (all supported) I have installed the separate DGIndex, and I can make d2v with success but I can't make .avs file through megui nor avsp, both throw me error as I post them few post above.
quantum5uicid3
3rd March 2010, 15:34
can you play the d2v with a simple avs through mpc-hc though?
kool
3rd March 2010, 22:19
No, can't play that as well.
Nightshiver
4th March 2010, 21:38
I had a problem similar to yours, and it was because of a "broken" .avsi script that I had in my plugins. By removing it, everything worked fine. Have you tried completely emptying your plug-ins folder except for what's needed to just see the video in AvsP?
kool
7th March 2010, 07:02
Well after trying few things which doesn't work, I come to re-install the Win, lets hope everything works now.
MrCommunistGen
10th March 2010, 05:01
If someone wants to test the newer x264 builds you can replace the x264.exe and x264_64.exe with newer builds. If using nal-hrd you have to add e.g. --nal-hrd vbr to the custom command line.
So you don't need to replace the vfw4x264.exe or avs4x264.exe files?
-mcg
Warbucks81
11th March 2010, 16:07
So you don't need to replace the vfw4x264.exe or avs4x264.exe files?
-mcg
No, just x264.exe or x264_64.exe whichever you use.
BlackPrince
13th March 2010, 00:45
oh whats this...
http://www.abload.de/img/megadet.png (http://www.abload.de/image.php?img=megadet.png)
??? :confused:
quantum5uicid3
13th March 2010, 01:12
old preset, new x264. add "vbr" behind --nalhrd. syntax changed.
"--nal-hrd vbr" in the custom command line
Zephyr_Truesdale
13th March 2010, 05:00
In my post for "MeGUI: General Questions and Troubleshooting" #5283, Windows 7 Users have to install "Windows 7: Preferred Tweaker for Windows 7" as it would seem that the pre-installed codecs won't work with MeGUI as I've had trouble as some of my other friends had. There was this guide I saw a while back that mentioned it.
J_Darnley
13th March 2010, 11:06
oh whats this...
http://www.abload.de/img/megadet.png (http://www.abload.de/image.php?img=megadet.png)
??? :confused:
You have an error on your command line which is causing "strict" to be interpreted as an input file. Alternatively, your x264 is too old and doesn't understand --b-pyramid strict. Try posting the entire line.
BlackPrince
13th March 2010, 11:14
old preset, new x264. add "vbr" behind --nalhrd. syntax changed.
"--nal-hrd vbr" in the custom command line
hy mate!
thx, now it works :):thanks::thanks:
Barough
14th March 2010, 14:28
This '--nal-hrd vbr' switch, what does it actually do for/on an encode. Looked around but i haven't found out what it does.
Zathor
14th March 2010, 14:40
This '--nal-hrd vbr' switch, what does it actually do for/on an encode. Looked around but i haven't found out what it does.
From the x264 help:
--nal-hrd <string> Signal HRD information (needed e.g. for Blu-Ray compliance)
- vbr, cbr. (requires vbv-bufsize; cbr not allowed in .mp4)
Barough
14th March 2010, 15:14
From the x264 help:
--nal-hrd <string> Signal HRD information (needed e.g. for Blu-Ray compliance)
- vbr, cbr. (requires vbv-bufsize; cbr not allowed in .mp4)
Thnx :)
Zathor
14th March 2010, 20:18
0.3.4.3
- [HDStreamExtractorIndexer] improved mpls parsing
- [BitrateCalculator] fixed overflow for very long video durations
- update MediaInfo library and its wrapper to the latest release (0.7.29)
- [MainForm] suspend the update progress until the profiles have been imported
- [x264Encoder] + [x264ConfigurationPanel] changed the default b-pyramid value to normal (requires x264 revision 1455 or higher)
- [JobWorkerWindow] enhanced error handling
- [AudioEncoderInterface] earlier preprocessing status update
- [tsMuxeR] ISO639-2-Code will be used for the language during muxing
- [tsMuxeR] fixed muxing of srt files. Bug #2958514
- [x264] removed the lossless checkbox, changed turbo to "fast first pass", changed thread-input, cosmetics
- [tsMuxeR] + [CommandlineMuxer] changed the way the projected filesize is estimated
hajj_3
15th March 2010, 01:23
thanks for the new update:)
buzzqw
15th March 2010, 12:22
any hope for fixing download updates using proxy ?
BHH
Zathor
15th March 2010, 12:27
any hope for fixing download updates using proxy ?
BHH
http://forum.doom9.org/showthread.php?p=1367724#post1367724
http://forum.doom9.org/showthread.php?p=1367751#post1367751
http://forum.doom9.org/showthread.php?p=1360346#post1360346
buzzqw
15th March 2010, 14:20
i will test proxy support (with autentication too)
if you have a debug build please send me a pm
thanks
BHH
Zathor
15th March 2010, 18:50
0.3.4.4
- [MP4BoxMuxer] + [CommandlineJobProcessor] changed the way the remaining time is estimated. Bug #2124705
- [MainForm] updatecopier.exe will only be elevated if necessary
- simplified updatecopier.exe
carlmart
15th March 2010, 22:57
I am getting two errors:
1) When I am trying to update I get a message "Could not load file or assembly 'ICSharpcode.SharZipLib, version=9.85.5.452, Culture=neutral, PublicKeyToken= 1b03e6acfll164f73'.
2) When I try load an avs script, which works fine in AvsP and VirtualDub, I get an error "unable to load Avisynthwrapper.dll". The dll is already on avisynth's plug-in directory.
What can I do to solve both problems?
Zathor
15th March 2010, 23:20
The dlls and megui are out of sync. Download this file and extract it to your megui folder: http://megui.org/auto/megui-libs_0_3_5.zip. Restart megui and let it update itself.
mozzle
17th March 2010, 21:09
The dlls and megui are out of sync. Download this file and extract it to your megui folder: http://megui.org/auto/megui-libs_0_3_5.zip. Restart megui and let it update itself.
I followed these instructions but when I restarted MEGUI, it did not prompt me for an update. And, when I attempted a forced reinstall on core 0.3.4.0, it throws the following error:
"MeGUI encountered a fatal error and may not be able to proceed. Reason: Could not load or assembly 'ISharpCode.SharpZipLib, Version=0.85.4.369, Culture=neutral,PublickKeyToken=1b03e6acf1164f73' or one of its dependencies. The located assembly's manifest destination does not match the assembly reference. (Exception from HRESULT: 0X80131040"
Windows XP Pro SP3
Thanks.
Zathor
17th March 2010, 22:38
If you switch back to the stable version you will receive this error. You have to stay with the dev version. I will (try to) fix it with the next dev release. As a fast solution you have to replace megui.exe with this one http://megui.org/auto/megui-core_0_3_4_4.zip and the dlls with the link provided above.
mozzle
18th March 2010, 03:15
If you switch back to the stable version you will receive this error. You have to stay with the dev version. I will (try to) fix it with the next dev release. As a fast solution you have to replace megui.exe with this one http://megui.org/auto/megui-core_0_3_4_4.zip and the dlls with the link provided above.
Okay. Thanks Zathor! Keep up the great work.
AMED
18th March 2010, 06:04
I'm wondering if there was any chance of adding support for FFmpegSource and it's indexing in to MeGUI?
Zathor
18th March 2010, 06:37
I'm wondering if there was any chance of adding support for FFmpegSource and it's indexing in to MeGUI?
There is always a chance :)
To be honest I have thought about this topic because of some problems I am facing in the last days during my encodes. But I am unsure how to implement this. There are several possibilities like to add this as a third indexer in the dg creator window or to add it in the avisynth creator. And the question is should it be the default for all file types, only for some file types (which one) or only a selectable option? Any thoughts are welcome!
quantum5uicid3
18th March 2010, 07:52
to keep it simple i would just make an "ffindex creator" interface in the tools menu and then just have avs creator do a check for the presence of the index when it opens the source file, if present have it automatically use FFmpegSource2 or ask.
addition
make it easy to index multiple files in different directories though
Cisco7
19th March 2010, 10:04
Hello evereybody, do you think MeGUI will support Theora in the near future ? Would be awesome for HTML5 video.
Zathor
20th March 2010, 22:34
First strike - please report bugs, problems or enhancements :thanks:
0.3.4.5
- [MainForm] renamed "DG Creator" to "File Indexer"
- added FFMS (FFmpegSource2) to the file indexer
Second strike...
0.3.4.6
- [AviSynthWindow] FFVideoSource will be used automatically if a corresponding ffindex file exists
- [MeGUISettings] fixed ffms file not found problem
Alex_080
21st March 2010, 03:05
can i encode a video file with two audio track ??
AMED
21st March 2010, 03:13
I've just given v0.3.4.6 with FFMSIndex a try, it indexed and opened fine in the AviSynth script creator.
I also like how you have hard set the dir for FFMSIndex, wouldn't this be a good idea to do this for the other indexers as well or could there be an option for the default output dir in the settings to be ignored for indexing?
I noticed some else that's not related to FFMS.
When you run the updater and it for some reason you press cancel, especially if its the core your updating. It will try and install the half downloaded .zip and bork MeGUI. Would there be some way if a user presses cancel while it is downloading a update it would automatically delete the incomplete .zip from the \update_cache\ dir.
AMED
21st March 2010, 03:14
can i encode a video file with two audio track ??right click beside the track 1 tab in the audio bit and add a track.
http://img19.imageshack.us/img19/5281/meguiaudio.png (http://img19.imageshack.us/i/meguiaudio.png/)
HeadlessCow
21st March 2010, 06:56
When you run the updater and it for some reason you press cancel, especially if its the core your updating. It will try and install the half downloaded .zip and bork MeGUI. Would there be some way if a user presses cancel while it is downloading a update it would automatically delete the incomplete .zip from the \update_cache\ dir.
The easiest way (in my opinion) to do this is to just download to something like filename.zip.temp and then rename to filename.zip when it completes. That should prevent you from getting a partial file even if your system crashes during the download.
AMED
21st March 2010, 07:08
Yup that seems a more logical method, hopefully its not too hard to implement.
kthxbye
21st March 2010, 18:54
With the newest update, when I try to disable MBtree and run an encode, it's still using MBtree although I did uncheck it in the settings!
It creates an .stats.mbtree file, yet does not show it in the commandline. When I open the .mkv file, mediainfo shows "mbtree=1" though. I did not check MBtree in the settings. Any info on this?
-edit- adding "--no-mbtree" to the commandline fixes this problem temporarily, but I didn't have to use this before...
Zathor
21st March 2010, 19:46
When you run the updater and it for some reason you press cancel, especially if its the core your updating. It will try and install the half downloaded .zip and bork MeGUI. Would there be some way if a user presses cancel while it is downloading a update it would automatically delete the incomplete .zip from the \update_cache\ dir.
The easiest way (in my opinion) to do this is to just download to something like filename.zip.temp and then rename to filename.zip when it completes. That should prevent you from getting a partial file even if your system crashes during the download.
I have added a zip file crc check before the archive will be extracted.
Zathor
21st March 2010, 19:48
With the newest update, when I try to disable MBtree and run an encode, it's still using MBtree although I did uncheck it in the settings!
It creates an .stats.mbtree file, yet does not show it in the commandline. When I open the .mkv file, mediainfo shows "mbtree=1" though. I did not check MBtree in the settings. Any info on this?
-edit- adding "--no-mbtree" to the commandline fixes this problem temporarily, but I didn't have to use this before...
As soon as I uncheck the mbtree check box "--no-mbtree" will be added to the command line. Please give me more details for reproducing the problem.
Zathor
21st March 2010, 20:06
I also like how you have hard set the dir for FFMSIndex, wouldn't this be a good idea to do this for the other indexers as well or could there be an option for the default output dir in the settings to be ignored for indexing?
Because there is no reference to the video file inside of the ffindex file I had to lock the location. This should be no big problem because the index file is rather small.
kthxbye
21st March 2010, 20:10
As soon as I uncheck the mbtree check box "--no-mbtree" will be added to the command line. Please give me more details for reproducing the problem.
I'm using MeGUI 0.3.4.6 (latest update) on Windows 7 64bit. If I check or uncheck "Use MB-Tree" in the configuration dialog, nothing happens in the commandline. If I select another profile and check/uncheck "Use MB-Tree" nothing happens either.
What else do you need to know? I'll gladly provide the information :)
Zathor
21st March 2010, 21:04
I'm using MeGUI 0.3.4.6 (latest update) on Windows 7 64bit. If I check or uncheck "Use MB-Tree" in the configuration dialog, nothing happens in the commandline. If I select another profile and check/uncheck "Use MB-Tree" nothing happens either.
What else do you need to know? I'll gladly provide the information :)
I found only a problem if the fast preset is beeing used. If this is not your problem please reset the profile to the default values (misc\default settings) and try again.
0.3.4.7
- [UpdateCacher] + [UpdateWindow] + [MainForm] added offline install capability
- [UpdateCacher] + [UpdateWindow] zip files will be verified before extracting
- [UpdateCacher] improved proxy support
- user.config will be migrated to new version if possible
- [x264Encoder] mbtree can be disabled while fast preset is active
kthxbye
21st March 2010, 21:55
I found only a problem if the fast preset is beeing used. If this is not your problem please reset the profile to the default values (misc\default settings) and try again.
That seems to have fixed the problem, thanks!
Just for verification, I had to redo all the settings:
program --level 3.1 --pass 2 --bitrate 1750 --stats ".stats" --deblock -3:-3 --bframes 6 --b-adapt 2 --ref 8 --no-mbtree --aq-strength 0.9 --merange 32 --me tesa --direct auto --subme 10 --partitions all --trellis 2 --psy-rd 0.9:0 --no-dct-decimate --no-fast-pskip --sar 40:33 --output "output" "input"
Any strange things in here? :)
cryphog
21st March 2010, 23:53
Stable or Development build? Which is the better of the two to use?
buzzqw
22nd March 2010, 11:21
here proxy isn't working :(
would be better to use something like wget/download.exe ?
BHH
Alf Bundy
22nd March 2010, 11:51
Hi :)
I've just tried FFindexer and FFVideoSource().
When I enqueue the script, I get a message box telling me "colorspace is not YV12, do you want to add ConvertToYV12() at the end of the script ?"
I say Yes and then I get this message :
http://img502.imageshack.us/img502/237/ffvideosource.png
If I click Yes, the job is enqueued properly and the encode runs fine.
Should I worry about this ?
PS: Thank you for your work Zathor. :thanks:
Zathor
22nd March 2010, 13:12
here proxy isn't working :(
Can you send me any proxy data (server, port, uid, pwd) so that I can check it myself? And please provide the complete log of the update window.
buzzqw
22nd March 2010, 13:39
pm send
thanks
BHH
Zathor
22nd March 2010, 15:10
I've just tried FFindexer and FFVideoSource().
When I enqueue the script, I get a message box telling me "colorspace is not YV12, do you want to add ConvertToYV12() at the end of the script ?"
I got the same messages. You can try to set the colorspace with FFVideoSource(source,colorspace=YV12)
AMED
23rd March 2010, 08:52
i tried with colorspace=YV12 and i got avisynth script error: i don't know what "YV12" means
LoadPlugin("C:\Program Files (x86)\megui\tools\ffms\ffms2.dll")
FFVideoSource("E:\The_Naked_Gun\The Naked Gun.mkv", colorspace=YV12)
#deinterlace
#crop
#resize
#denoise
I'm testing with a DVD ripped with makemkv.
EDIT: Found out why it isn't working, it should be like this.
LoadPlugin("C:\Program Files (x86)\megui\tools\ffms\ffms2.dll")
FFVideoSource("E:\The_Naked_Gun\The Naked Gun.mkv", colorspace="YV12")
#deinterlace
#crop
#resize
#denoise
that stops the colorspace not YV12 errors appearing in MeGUI.
Alf Bundy
23rd March 2010, 20:23
Thank you Zathor & AMED.
Problem solved for me too.
yaous
26th March 2010, 19:08
I'm using MeGUI 0.3.4.7
When I set modes:const. quality,
Temp. Blur of est. Frame complexity(cplxblur) and
Temp. Blur of Quant after CC(qblur) are disabled.
and when I set modes:const. quantizer,
all the options in [Quantizers] box of [Rate Control] tap are disabled except credits quantizer.
and AQ is activated in const. quantizer mode.
Is this normal?
Zathor
27th March 2010, 14:46
I'm using MeGUI 0.3.4.7
When I set modes:const. quality,
Temp. Blur of est. Frame complexity(cplxblur) and
Temp. Blur of Quant after CC(qblur) are disabled.
and when I set modes:const. quantizer,
all the options in [Quantizers] box of [Rate Control] tap are disabled except credits quantizer.
and AQ is activated in const. quantizer mode.
Is this normal?
I do not know. These things have been disabled since I am involved in the development. If someone agrees that this is incorrect I will change it - sadly I have no time to check it myself (e.g. with x264 --fullhelp or the Wiki).
Zathor
27th March 2010, 16:45
0.3.4.8
- [ffmsReader] + [ScriptServer] FFVideoSource defaults to the YV12 colorspace
- [VideoUtil] improved the ConvertToYV12() handling
MajorX
28th March 2010, 01:19
How can i encode a dual audio file with MeGUI ...i tried with adding Track 2 but it encode the first track not the second..how can i use the DGIndex???
yaous
28th March 2010, 05:03
I do not know. These things have been disabled since I am involved in the development. If someone agrees that this is incorrect I will change it - sadly I have no time to check it myself (e.g. with x264 --fullhelp or the Wiki).
http://forum.doom9.org/showthread.php?t=153672
from that post,
It seems that
--qpmin/max/step, --ip/pbratio and --chroma-qp-offset are adjustable in CQP mode.
and AQ is not used in CQP mode.
Knuffi
28th March 2010, 10:48
How can i encode a dual audio file with MeGUI ...i tried with adding Track 2 but it encode the first track not the second..how can i use the DGIndex???
You have to press the "Enque" button on both tabs - "Track 1" and "Track 2".
Zathor
28th March 2010, 10:53
http://forum.doom9.org/showthread.php?t=153672
from that post,
It seems that
--qpmin/max/step, --ip/pbratio and --chroma-qp-offset are adjustable in CQP mode.
and AQ is not used in CQP mode.
Thanks.
I have to change the handling for the upcoming new x264 build (superfast preset, nal-hrd, ...) and will have a look at your findings, too.
Zathor
28th March 2010, 18:23
0.3.4.9
- x264 - some CQP mode adjustments
- x264 - added superfast preset support (requires x264 revision 1509 or higher)
hajj_3
28th March 2010, 20:27
Can you make it so that the widths of the columns in the "queue" tab are saved instead of reverted back to default when you upgrade the megui version please.
Zathor
28th March 2010, 21:19
Can you make it so that the widths of the columns in the "queue" tab are saved instead of reverted back to default when you upgrade the megui version please.
Since 0.3.4.7 these settings are migrated if possible. At least it is working for me.
hajj_3
28th March 2010, 22:20
the main window is but the width of the columns in the "queue" tab didn't migrate for me.
Zathor
28th March 2010, 22:36
After a quick test I can say that beside the "Owner" column the other columns are being saved. I did not check the source code, but it looks in general as it is working.
cryphog
28th March 2010, 23:21
Hello Zathor! Thanks for the great work on MeGUI! I just have a question about the stable server, Is it gonna get updated any time soon or should I switch over to the development server? Thanks
Zathor
29th March 2010, 05:20
A new stable build will be released together will all recent tools as soon as I think that MeGUI and the tools are ready for this step. With the fresh commit of the new x264 I would like to wait at least a week before I decide if this is gonna be a stable release.
AMED
29th March 2010, 05:30
@Zathor
I just gave your update zip crc check a go by canceling the core update mid download. Once i reopened MeGUI, it prompted me that the core update still needed to be downloaded and installed.
JoeH
29th March 2010, 08:08
0.3.4.9
- x264 - some CQP mode adjustments
- x264 - added superfast preset support (requires x264 revision 1509 or higher)
Thanks Zathor! Works great. It's exciting to see the new improvements in X264, and equally exciting to see how quickly you are keeping up! :thanks:
Zathor
29th March 2010, 11:45
I just gave your update zip crc check a go by canceling the core update mid download. Once i reopened MeGUI, it prompted me that the core update still needed to be downloaded and installed.
So it is working as expected, isn't it? :)
Thanks Zathor! Works great. It's exciting to see the new improvements in X264, and equally exciting to see how quickly you are keeping up! :thanks:
:eek:
alexcel
29th March 2010, 23:45
Hi Zathor:
This is an old bug.
When selecting keep input resolution in one click encoder, the program passes wrong aspect ratio AR to encoder and muxer.
Typically, one click encoder in MeGui passes the AR as if the frames were cropped. But as the frames are not cropped when "Keep input res" is set, the resulting AR is wrong
My last encode, was a 16:9 PAL film. The final AR in the mkv file should be 16:9 also, but is was 2,525. One click thought the black bars were going to be cropped, but they were not
Please Help. :thanks:
Here I add a extract from the log, I have marked in red what I think is wrong
--- OneClick postprocessor
----[NoImage] Desired size: null
----[NoImage] Split size: null
----[NoImage] Auto-detect aspect ratio now: True
----[NoImage] Aspect ratio: 1,823361
----[NoImage] Output resolution: 720x416 [I](frame was not cropped, should be 720*576)
----[NoImage] AVC level: Level 3
----[NoImage] Resolution adjusted for AVC Level: 720x416
----[NoImage] Automatic deinterlacing: True
----[NoImage] Deinterlacing used: #Not doing anything because the source is progressive
----[NoImage] Generated Avisynth script
-----[NoImage] global MeGUI_darx = 154
-----[NoImage] global MeGUI_dary = 61
AMED
30th March 2010, 03:01
So it is working as expected, isn't it? :) Yes works perfectly, thanks for the feature :)
EDIT: now i think of it, would it possible to show an error box to the user if one of the downloads are corrupt. Without this a user might wonder why an update is not applying.
Octo-puss
30th March 2010, 17:37
Just a question: http://sourceforge.net/projects/megui/ seems to be updated. Is it this patched build or did the devs come back?
rapscallion
30th March 2010, 18:03
No, not a patched build on sourceforge. That's 3.3, while patched is ver 3.4.9
Carpo
30th March 2010, 19:43
here is a strange little issue, i was trying to encode a video with 3.4.9, the first pass went fine but when i tried to do the 2nd pass x264.exe would not run and megui would not encode the 2nd pass, i thought i may have been something my end so i backed up the jobs folder and removed megui, i then reinstalled it and updated to 3.4.9 again, but the jobs will not show up in the queue nor can i load them when i click on the load tab, nothing happens, i could redo the first passes but one of them took 12 hours so i don't really wish to do that again.
Is this a known error or is there something wrong on my end?
Octo-puss
30th March 2010, 19:53
No, not a patched build on sourceforge. That's 3.3, while patched is ver 3.4.9
Okay. But what is going on there, then? I'm confused as hell :D I believe all the devs simply disappeared few months ago.
rapscallion
30th March 2010, 20:14
@carpo. You don't mention the output or if it's automated 2 pass that you're using.
I have never been able to get the jobs to reload, all the way back to ver 1051.
If, in fact, you used automated 2 pass there's a method I've used in the past and it worked.
1. Reload your avs script. Select the same preset/settings as before, under "config"
2. Enqueue the jobs, then delete job 1.
3. Still in "config" and then "main". Under "modes" click on the dialog box for passes and change "automated 2 pass" to " 2pass 2nd pass".
4. Go back to the "queue" tab and start job 2.
This should work as long as the 1st pass files are still in the same dir. Good luck !
Edit: As to why it borked job2 in the first palce, I can't answer.
I'm running 3.4.8 w/no problems.
rapscallion
30th March 2010, 20:17
Okay. But what is going on there, then? I'm confused as hell :D I believe all the devs simply disappeared few months ago.
Then you haven't been following this thread, or even the last couple of pages. Zathor has picked up the development since last December and is doing a great job.
Carpo
30th March 2010, 20:45
@carpo. You don't mention the output or if it's automated 2 pass that you're using.
I have never been able to get the jobs to reload, all the way back to ver 1051.
If, in fact, you used automated 2 pass there's a method I've used in the past and it worked.
1. Reload your avs script. Select the same preset/settings as before, under "config"
2. Enqueue the jobs, then delete job 1.
3. Still in "config" and then "main". Under "modes" click on the dialog box for passes and change "automated 2 pass" to " 2pass 2nd pass".
4. Go back to the "queue" tab and start job 2.
This should work as long as the 1st pass files are still in the same dir. Good luck !
Edit: As to why it borked job2 in the first palce, I can't answer.
I'm running 3.4.8 w/no problems.
Yes your right i forgot about that, and yes it is automated 2 pass, sorry about that, just really tired here atm ;-) i will try your suggestions - thanks
Update, it started the second pass, but its doing the same as before - vfw4x264.exe is taking one core (25%) but x264.exe is no where to be found in the task manager, that and the pc is not as loud as the fans aren't speeding up
update2: after looking in the log i see
--[Information] [30/03/2010 21:11:11] Encoding started
--[Error] An error occurred: x264 [error]: different bframes setting than first pass (8 vs 3)
--[Error] An error occurred: x264 [error]: x264_encoder_open failed
but like i say i have not changed anything between the passes
rapscallion
30th March 2010, 21:46
but like i say i have not changed anything between the passes
The only way to know that for sure is to check the log for the first pass to see what the bframes setting is. If it's different, then set the 2nd pass to match.
Carpo
30th March 2010, 21:59
The only way to know that for sure is to check the log for the first pass to see what the bframes setting is. If it's different, then set the 2nd pass to match.
if i had kept the logs when i reinstalled i would have, i have set it to redo the whole thing, will see if i get same issue as before, if i do then its not me :-) although i have noticed that the version of x264 that comes with the dev branch (3.4.9) (x264 1510) is slower than the stable tree, losing about 4 fps
Octo-puss
30th March 2010, 22:04
Then you haven't been following this thread, or even the last couple of pages. Zathor has picked up the development since last December and is doing a great job.
I have not, that's right. I was kinda busy and didn't need MeGUI at all. Guess the guys could at least hand over the Sourceforge access, but whatever... The most important is that development keeps going :)
Zathor
30th March 2010, 22:13
I have the sourceforge access since a few months so everything is fine. Therefore the patched builds mentioned on the first pages of this thread are now the official builds.
rapscallion
30th March 2010, 22:21
if i had kept the logs when i reinstalled i would have, i have set it to redo the whole thing, will see if i get same issue as before, if i do then its not me :-) although i have noticed that the version of x264 that comes with the dev branch (3.4.9) (x264 1510) is slower than the stable tree, losing about 4 fpsOk, I was going to suggest reverting back to 3.4.8 (x264 1471 Komisar's kgit generic)
That bframes mismatch was a little strange though.
You wouldn't really us "8", right ?
JoeH
31st March 2010, 07:32
I have the sourceforge access since a few months so everything is fine. Therefore the patched builds mentioned on the first pages of this thread are now the official builds.
But you did in fact update the SourceForge build to 3.3, even though that isn't the latest version.
Carpo
31st March 2010, 08:03
Ok, I was going to suggest reverting back to 3.4.8 (x264 1471 Komisar's kgit generic)
That bframes mismatch was a little strange though.
You wouldn't really us "8", right ?
its all set by megui profiles, i dont touch anything, and after doing another test run, the first pass went fine, but it wont call x264 for second pass and there is no errors in the logs, so will have to find the old version of x264 from somewhere
Zathor
31st March 2010, 13:39
But you did in fact update the SourceForge build to 3.3, even though that isn't the latest version.
Yes, I have updated the SourceForge installer build to 0.3.3. At the moment it is not necessary to update the installer because a connection to the intranet for the tools is mandatory - if only the tools will be updates or the tools and the main program doesn't matter. But this will change with the next stable release. I am planing to release an offline install package which includes all of the necessary files from the update server.
livetolove92
31st March 2010, 15:31
[Error] Log
-[Information] Versions
--[NoImage] MeGUI Version : 0.3.4.0
--[NoImage] OS : Windows Seven x64 (6.1.0.7600)
--[NoImage] Latest .Net Framework installed : 3.5 SP1 (3.5.30729.4926)
--[NoImage] Avisynth Version : 2.5.8.5
-[Error] Log for job1 (video, 720p1.mkv)
--[Information] [3/31/2010 8:46:50 AM] Started handling job
--[Information] [3/31/2010 8:46:50 AM] Preprocessing
--[NoImage] Job commandline: "C:\Program Files (x86)\megui\tools\x264\vfw4x264.exe" --preset slower --pass 2 --bitrate 2555 --stats "E:720p1.stats" --thread-input --bframes 5 --b-pyramid normal --b-bias 2 --interlaced --vbv-maxrate 31250 --sar 1:1 --output "E:\720p1.mkv" "E:\Track1.avs"
--[Information] [3/31/2010 8:46:51 AM] Encoding started
--[Error] An error occurred: x264 [error]: ratecontrol_init: can't open stats file
--[Error] An error occurred: x264 [error]: x264_encoder_open failed
--[NoImage] Standard output stream
--[NoImage] Standard error stream
---[NoImage] x264 [info]: 960x408 @ 23.98 fps
---[NoImage] x264 [warning]: interlace + direct=temporal is not implemented
---[NoImage] x264 [warning]: interlace + weightp is not implemented
---[NoImage] x264 [warning]: NAL HRD parameters require VBV max bitrate and buffer size to be specified
---[NoImage] x264 [info]: using SAR=1/1
---[NoImage] x264 [warning]: VBV bitrate (31250) > level limit (17500)
---[NoImage] x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 FastShuffle SSE4.2
---[NoImage] x264 [warning]: VBV maxrate specified, but no bufsize.
--[Information] [3/31/2010 9:20:38 AM] Job completed
How can I fix it >.< . Plz
rapscallion
31st March 2010, 15:55
......, so will have to find the old version of x264 from somewhere
From page 1 of this thread :
http://megui.org/auto/
Top of page for previous versions of Megui, or scroll to bottom of page for previous versions of x264.
Carpo
31st March 2010, 17:31
@livetolove92 - i am getting vaious errors like that with latest megui
@rapscallion - found old version of x264 from x264.nl - still having same issues, have gone back to stable version, if i still get errors then its probably something my end
AMED
31st March 2010, 20:26
@livetolove92
From that log it looks like your running the 2nd pass before running the 1st pass.
Carpo
31st March 2010, 22:56
stats line looks wrong, shouldn't --stats "E:720p1.stats" show as --stats "E:\720p1.stats"
Carpo
1st April 2010, 01:00
Little update on my issue going back to stable 3.4.0 seems to have sorted out the issue i was having so it must be an issue with megui, newer x264's and vfw4x264.
livetolove92
1st April 2010, 05:02
stats line looks wrong, shouldn't --stats "E:720p1.stats" show as --stats "E:\720p1.stats"
I clear the path to be suitable with the rule.
Carpo
1st April 2010, 15:14
seems uninstalling every codec (ffdshow, divx - used to show mkv thumbs and haali) and removing megui, rebooting, cleaning registry and then reinstalling everything seems to have cleared my issue (so far) have done one film with stable 3.4.0 and and on 2nd pass with 3.4.9 - seems strange that a registry entry may have been stopping it
quantum5uicid3
1st April 2010, 20:51
i added
--weightp 0 --colorprim "bt709" --transfer "bt709" --colormatrix "bt709"
in the AVCHD and Bluray presets. disabling weightp is detrimental to quality and only required for playback on certain "bugged" standalone, so remove it from custom commandline if you wish.
enabled bpyrimid on most of the presets and fixed some little stuff too.
http://www.mediafire.com/?mwlzi1ztimm
Zathor, i think there's a bug that copies the --vbv-maxrate setting when changing from one megui preset to another from within the x264 configuration dialog window. i think it only happens when changing from a preset with it forced to one without it being specified at all. like when changing from "bluray.." to xbox360.."
thanks very much for the ffms2 support and fixes :thanks:
Lyle_JP
1st April 2010, 20:54
Zathor, i think there's a bug that copies the --vbv-maxrate setting when changing from one megui preset to another from within the x264 configuration dialog window. i think it only happens when changing from a preset with it forced to one without it being specified at all. like when changing from "bluray.." to xbox360.."
I also experience this bug frequently.
rapscallion
1st April 2010, 21:34
i added
--weightp 0 --colorprim "bt709" --transfer "bt709" --colormatrix "bt709"
in the AVCHD and Bluray presets. disabling weightp is detrimental to quality and only required for playback on certain "bugged" standalone, so remove it from custom commandline if you wish.
Thanks for the new presets ! Does --weightp 0 command disable or enable ? :confused:
Both this and the previous (33) version preset shows :
<WeightedBPrediction>true</WeightedBPrediction>
<WeightedPPrediction>2</WeightedPPrediction>
Also, are the new presets only for X264 1510 or do they apply to previous versions as well ?
Shevek
2nd April 2010, 15:15
I'm returning to x264 encoding using MeGUI after a break of about a year and having read through the last few pages of this (http://forum.doom9.org/showthread.php?t=139765) thread I've just about got to grips with the new profiles, this being my current cmd line for a 720p encode, based on Unrestricted (DXVA) - 2-pass with preset and bitrate changed:
program --preset faster --pass 2 --bitrate 3000 --stats ".stats" --output "output" "input"
However I still have one question - does the old rule of updating the Max & Min GOP for the frame-rate still apply?
i.e. 240/24 for film, 250/25 for PAL, 300/30 for NTSC
TIA
Zathor
2nd April 2010, 18:07
Yes works perfectly, thanks for the feature :)
EDIT: now i think of it, would it possible to show an error box to the user if one of the downloads are corrupt. Without this a user might wonder why an update is not applying.
There should already be an error message in the update window log:
Error: Could not unzip filename. Deleting file. Please run updater again...
Zathor
2nd April 2010, 18:55
When selecting keep input resolution in one click encoder, the program passes wrong aspect ratio AR to encoder and muxer.
Thanks, has been fixed locally and will be in the next build.
Zathor
2nd April 2010, 20:20
0.3.4.10
- [x264Encoder] --aud will only be appended if selected in the configuration dialog. Bug #2979294
- [OneClickSettings] the MKV container is enabled by default
- [x264ConfigurationPanel] fixed wrong vbvmaxrate value after profile switching
- [OneClickWindow] fixed keep input resolution behavior
- [VideoEncodingComponent] improved error handling
- [FilmCutter] changed default transition type in AVS Cutter to "No transition". Fade transition will blend in/out 10 frames. Bug #2913546
alexcel
3rd April 2010, 09:54
Hi Zathor
Very glad to know you are working on it :thanks:
The problemn is almost solved
Now Correct DAR and PAr is finally recorded in muxer, but videolan player can't handle such large numbers
in mkv file, display width/heigt is 34709:19036
When encoding &creating avs manually, the values are 31:17 or 16:9
I do not know why megui ends with such long figures. I have tested vaules in mkv as long as 1024:576 or 1920:1080. Probably the maximum figure is 4000 or 16000 or 32000.
Even x264 changes the input darX &darY to lower values, as seen in log:
global MeGUI_darx = 69419
global MeGUI_dary = 38072
but x264 rounds to
yuv [info]: 720x576p 69419:47590 @ 25/1 fps (cfr)
x264 [info]: using SAR=34709/23795
Can you change the way megui calculates darx & darY so that lower figures are used? Something like 16:9 or 31:17 or 1024:576 would be nice
Here is an extract from log
---[Information] OneClick postprocessor
----[NoImage] Desired size: null
----[NoImage] Split size: null
----[NoImage] Auto-detect aspect ratio now: True
----[NoImage] Aspect ratio: 1,823361
----[NoImage] Output resolution: 720x576 (CORRECT!!)
----[NoImage] Automatic deinterlacing: True
----[NoImage] Deinterlacing used: #Not doing anything because the source is progressive
----[NoImage] Generated Avisynth script
-----[NoImage] global MeGUI_darx = 69419
-----[NoImage] global MeGUI_dary = 38072 When Manually creating Avs the values are 31/17
-----[NoImage] LoadPlugin("D:\Downloads\DVD\MeGUI\tools\dgindex\DGDecode.dll")
-----[NoImage] DGDecode_mpeg2source("E:\Ultimas\MainMovie\\VIDEO_TS\VTS 01 1.d2v", info=3)
-----[NoImage] LoadPlugin("D:\Downloads\DVD\MeGUI\tools\avisynth_plugin\ColorMatrix.dll")
-----[NoImage] ColorMatrix(hints=true, threads=0)
-----[NoImage] #Not doing anything because the source is progressive
-----[NoImage] #denoise
----[Information] Eliminating duplicate filenames
-----[NoImage] Video output file: E:\Ultimas\MainMovie\\VIDEO_TS\VTS 01 1_Video.mkv
-----[NoImage] Muxed output file: E:\Ultimas\MainMovie\\VIDEO_TS\VTS 01 1.mkv
-----[NoImage] File already exists. New muxed output filename: E:\Ultimas\MainMovie\\VIDEO_TS\VTS 01 1_0.mkv
--[Information] [02/04/2010 22:27:48] Job completed
-[Information] Log for job16 (video, VTS 01 1.avs -> VTS 01 1_Video.mkv)
--[Information] [02/04/2010 22:27:48] Started handling job
--[Information] [02/04/2010 22:27:48] Preprocessing
--[NoImage] Job commandline: "D:\Downloads\DVD\MeGUI\tools\x264\vfw4x264.exe" --level 3 --tune film --crf 21.5 --b-pyramid none --sar 69419:47590 --output "E:\Ultimas\MainMovie\\VIDEO_TS\VTS 01 1_Video.mkv" "E:\Ultimas\MainMovie\\VIDEO_TS\VTS 01 1.avs"
--[Information] [02/04/2010 22:27:48] Encoding started
--[NoImage] Standard output stream
--[NoImage] Standard error stream
---[NoImage] yuv [info]: 720x576p 69419:47590 @ 25/1 fps (cfr)
---[NoImage] x264 [info]: using SAR=34709/23795
---[NoImage] x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 FastShuffle SSE4.2
---[NoImage] x264 [info]: profile High, level 3.0
---[NoImage]
Zathor
3rd April 2010, 13:45
0.3.4.11
- [DAR] + [ARChooser] enhanced ITU values
- [OneClickSettings] changed the default output resolution to 720
- [OneClickWindow] custom AR can be applied if "Keep Input Resolution" is selected
- [OneClickWindow] "Keep Input Resolution" disables "Signal AR"
Now Correct DAR and PAr is finally recorded in muxer, but videolan player can't handle such large numbers
MPC HC can :)
Can you change the way megui calculates darx & darY so that lower figures are used? Something like 16:9 or 31:17 or 1024:576 would be nice
I have optimized the internal ITU values so that the correct and better divisible values will be used:
PAL:
16x9 = 720/576 * 512/351 = 640/351
4x3 = 720/576 * 128/117 = 160/117
NTSC:
16:9 = 720/480 * 5760/4739 = 8640/4739
4x3 = 720/480 * 4320/4739 = 6480/4739
And additionally I fixed a problem which prevents applying the custom AR values if "keep input resolution" is selected. So you can change it to 16:9 if you want.
alexcel
3rd April 2010, 21:09
Great job, Zathor, Keep input resolution now works like a charm.
:thanks::thanks::thanks::thanks::thanks::thanks::thanks:
You've me saved tons of time.
Just a minor suggestion, when keep input res is checked, signal AR is disabled in one click advanced setting tab, but it is not disabled in the one click profile configuration window.
And someday i will try to understand ITU values or why the exact values are 640:351 and not 16:9. I feel like an absolut newbie
But today I am happy, this fix is ...great. Thanks again
Zathor
3rd April 2010, 21:35
Just a minor suggestion, when keep input res is checked, signal AR is disabled in one click advanced setting tab, but it is not disabled in the one click profile configuration window.
It's only cosmetic because even if signal AR is enabled it will not change anything if keep input res is selected, too. Nevertheless I will change it in the next build.
JoeH
4th April 2010, 14:35
I just output and burned a Blu-ray disc using the Blu-ray 2 pass with the latest development build, X264 1510, etc. The disc plays just fine on the computer, but neither my Panasonic BD-35 nor my Panasonic BD-60 will read it. I have output many BD discs before using MeGUI and have never had this problem. My firmware is up to date on the Panasonics.
I am currently outputting a file with the MeGUI stable build and will rebuild and burn and see if that fixes the problem.
---------------------------------------------------------------------------------
UPDATE: I just saw here (http://forum.doom9.org/showthread.php?t=152127&page=23) that others are having difficulties with the latest X264 being in fact Blu-ray incompatible, and that it is a problem which Dark_Shikari is aware of and is working on.
UPDATE2: I investigated a little more, and it turns out my x264 build was actually 1442, even though MeGUI was reporting 1510. So, this is most likely a false positive.
Zathor
4th April 2010, 14:57
0.3.4.12
- [OneClickConfigPanel] "Keep Input Resolution" disables "Signal AR"
- [JobQueue] CTRL+A selects all queue items. Feature request #2981335
- [JobQueue] SHIFT+UP or DOWN to move an queue item, UP or DOWN to navigate in the list
- user.config settings will also be migrated for queue settings and custom AR, file size and FPS
the main window is but the width of the columns in the "queue" tab didn't migrate for me.
After a quick test I can say that beside the "Owner" column the other columns are being saved. I did not check the source code, but it looks in general as it is working.
Sorry, had to dig deeper into the code and found the source of the problem. Now all settings should be migrated including queue settings and custom AR, file size and FPS.
JoeH
4th April 2010, 14:57
Zathor,
Whenever I have tried to update my development build from version 0.3.4.10 to version 0.3.4.11 or version 0.3.4.12 I am getting the attached error. MeGUI then reverts to build 0.3.4.10.
Zathor
4th April 2010, 14:58
Zathor,
Whenever I have tried to update my development build from version 0.3.4.10 to version 0.3.4.11 or version 0.3.4.12 I am getting the attached error.
We have to wait for the approval or you can upload the file somewhere else :)
Zathor
4th April 2010, 15:31
UPDATE2: I investigated a little more, and it turns out my x264 build was actually 1442, even though MeGUI was reporting 1510. So, this is most likely a false positive.
MeGUI does not know about the file itself and will only report which file has been successfully downloaded. If the files are replaced after the download MeGUI will still report the old build numbers. But glad to hear that your problem is solved.
Zathor
4th April 2010, 16:30
Zathor,
Whenever I have tried to update my development build from version 0.3.4.10 to version 0.3.4.11 or version 0.3.4.12 I am getting the attached error. MeGUI then reverts to build 0.3.4.10.
Please extract this file (http://megui.org/auto/updatecopier_0_3_4_1.zip) to your MeGUI directory replacing the old file.
JoeH
4th April 2010, 20:03
Please extract this file (http://megui.org/auto/updatecopier_0_3_4_1.zip) to your MeGUI directory replacing the old file.
Thanks. That did the trick.
JoeH
4th April 2010, 20:05
MeGUI does not know about the file itself and will only report which file has been successfully downloaded. If the files are replaced after the download MeGUI will still report the old build numbers. But glad to hear that your problem is solved.
I did the encode with the 1510 build, using the Blu-ray 2 pass at 17500 bitrate.
I ended up with a file with an average bitrate of under 7000. In the log file, both the goal bitrate of 17500 and the final result of under 7000 were listed.
Here is the MediaInfo on the file. Any ideas why this happened? I'm not sure if it is an X264 or a MeGUI issue.
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L4.1
Format settings, CABAC : Yes
Format settings, ReFrames : 3 frames
Muxing mode : Container profile=Unknown@4.1
Codec ID : V_MPEG4/ISO/AVC
Duration : 2h 7mn
Bit rate : 6 557 Kbps
Nominal bit rate : 17.5 Mbps
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate : 23.976 fps
Resolution : 8 bits
Colorimetry : 4:2:0
Scan type : Progressive
Bits/(Pixel*Frame) : 0.132
Stream size : 5.82 GiB (98%)
Writing library : x264 core 92 r1510 33d382a
Encoding settings : cabac=1 / ref=4 / deblock=1:-1:-1 / analyse=0x3:0x113 / me=hex / subme=4 / psy=1 / psy_rd=0.00:0.15 / mixed_ref=0 / me_range=16 / chroma_me=1 / trellis=1 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=-1 / threads=12 / sliced_threads=0 / slices=4 / nr=0 / decimate=1 / interlaced=0 / constrained_intra=0 / bframes=3 / b_pyramid=1 / b_adapt=1 / b_bias=0 / direct=1 / wpredb=1 / wpredp=1 / keyint=24 / keyint_min=2 / scenecut=40 / intra_refresh=0 / rc_lookahead=20 / rc=2pass / mbtree=1 / bitrate=17500 / ratetol=1.0 / qcomp=0.60 / qpmin=10 / qpmax=51 / qpstep=4 / cplxblur=20.0 / qblur=0.5 / vbv_maxrate=40000 / vbv_bufsize=30000 / ip_ratio=1.40 / aq=1:1.00 / nal_hrd=vbr
nurbs
4th April 2010, 20:19
Post the x264 log. Can't say anything without that.
Maybe the source is extremely easily compressible and you didn't get the filesize you wanted because qpmin=10
JoeH
4th April 2010, 21:56
Post the x264 log. Can't say anything without that.
Maybe the source is extremely easily compressible and you didn't get the filesize you wanted because qpmin=10
Thanks for your help. Here is the log. Job 34 was the 1st pass, Job 35 the 2nd.
--[NoImage] MeGUI Version : 0.3.4.10
--[NoImage] OS : Windows Seven Enterprise Edition x64 (6.1.0.7600)
--[NoImage] Latest .Net Framework installed : 3.5 SP1 (3.5.30729.4926)
--[NoImage] Avisynth Version : 2.6.0.1
-[Information] Log for job34 (video, VegasEdits.avs -> )
--[Information] [4/4/2010 4:02:22 PM] Started handling job
--[Information] [4/4/2010 4:02:22 PM] Preprocessing
--[NoImage] Job commandline: "C:\Program Files (x86)\megui\tools\x264\vfw4x264.exe" --preset faster --tune film --pass 1 --bitrate 17500 --stats "E:\4 Peliculas\Render\VegasEdits.stats" --profile high --level 4.1 --bframes 3 --ref 4 --slices 4 --aud --nal-hrd vbr --b-pyramid strict --keyint 24 --min-keyint 2 --vbv-bufsize 30000 --vbv-maxrate 40000 --sar 1:1 --output NUL "E:\4 Peliculas\Render\VegasEdits.avs"
--[Information] [4/4/2010 4:02:23 PM] Encoding started
--[NoImage] Standard output stream
--[NoImage] Standard error stream
---[NoImage] yuv [info]: 1920x1080p 1:1 @ 2997/125 fps (cfr)
---[NoImage] x264 [info]: using SAR=1/1
---[NoImage] x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 FastShuffle SSE4.2
---[NoImage] x264 [info]: profile Main, level 4.1
---[NoImage]
---[NoImage] x264 [info]: frame I:8680 Avg QP:15.15 size:252962
---[NoImage] x264 [info]: frame P:102539 Avg QP:17.63 size:101531
---[NoImage] x264 [info]: frame B:71813 Avg QP:19.49 size: 52378
---[NoImage] x264 [info]: consecutive B-frames: 28.7% 46.3% 8.8% 16.2%
---[NoImage] x264 [info]: mb I I16..4: 32.3% 0.0% 67.7%
---[NoImage] x264 [info]: mb P I16..4: 43.0% 0.0% 0.0% P16..4: 51.4% 0.0% 0.0% 0.0% 0.0% skip: 5.7%
---[NoImage] x264 [info]: mb B I16..4: 13.0% 0.0% 0.0% B16..8: 37.0% 0.0% 0.0% direct:25.9% skip:24.1% L0:25.7% L1:35.0% BI:39.3%
---[NoImage] x264 [info]: final ratefactor: 16.43
---[NoImage] x264 [info]: coded y,uvDC,uvAC intra: 78.8% 66.8% 34.6% inter: 43.1% 29.7% 2.5%
---[NoImage] x264 [info]: i16 v,h,dc,p: 25% 14% 40% 22%
---[NoImage] x264 [info]: i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 19% 16% 19% 8% 8% 8% 7% 8% 8%
---[NoImage] x264 [info]: kb/s:17152.87
---[NoImage] encoded 183032 frames, 37.22 fps, 17152.86 kb/s
--[Information] [4/4/2010 5:24:21 PM] Postprocessing
---[Information] Deleting intermediate files
--[Information] [4/4/2010 5:24:21 PM] Job completed
-[Information] Log for job35 (video, VegasEdits.avs -> VegasEdits.mkv)
--[Information] [4/4/2010 5:24:21 PM] Started handling job
--[Information] [4/4/2010 5:24:21 PM] Preprocessing
--[NoImage] Job commandline: "C:\Program Files (x86)\megui\tools\x264\vfw4x264.exe" --preset faster --tune film --pass 2 --bitrate 17500 --stats "E:\4 Peliculas\Render\VegasEdits.stats" --profile high --level 4.1 --bframes 3 --ref 4 --slices 4 --aud --nal-hrd vbr --b-pyramid strict --keyint 24 --min-keyint 2 --vbv-bufsize 30000 --vbv-maxrate 40000 --sar 1:1 --output "E:\4 Peliculas\Render\VegasEdits.mkv" "E:\4 Peliculas\Render\VegasEdits.avs"
--[Information] [4/4/2010 5:24:23 PM] Encoding started
--[NoImage] Standard output stream
--[NoImage] Standard error stream
---[NoImage] yuv [info]: 1920x1080p 1:1 @ 2997/125 fps (cfr)
---[NoImage] x264 [info]: using SAR=1/1
---[NoImage] x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 FastShuffle SSE4.2
---[NoImage] x264 [info]: profile High, level 4.1
---[NoImage]
---[NoImage] x264 [info]: frame I:8680 Avg QP:11.63 size:460646
---[NoImage] x264 [info]: frame P:102539 Avg QP:11.38 size: 17427
---[NoImage] x264 [info]: frame B:71813 Avg QP:11.76 size: 8316
---[NoImage] x264 [info]: consecutive B-frames: 28.7% 46.3% 8.8% 16.2%
---[NoImage] x264 [info]: mb I I16..4: 4.8% 26.6% 68.6%
---[NoImage] x264 [info]: mb P I16..4: 1.2% 3.1% 0.4% P16..4: 15.9% 1.3% 0.7% 0.0% 0.0% skip:77.3%
---[NoImage] x264 [info]: mb B I16..4: 0.5% 1.3% 0.1% B16..8: 5.6% 0.2% 0.1% direct: 9.4% skip:82.8% L0:30.4% L1:48.3% BI:21.3%
---[NoImage] x264 [info]: 8x8 transform intra:43.3% inter:68.2%
---[NoImage] x264 [info]: coded y,uvDC,uvAC intra: 93.8% 88.4% 65.3% inter: 7.9% 5.0% 0.8%
---[NoImage] x264 [info]: i16 v,h,dc,p: 22% 11% 47% 20%
---[NoImage] x264 [info]: i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 16% 20% 37% 4% 4% 4% 4% 5% 6%
---[NoImage] x264 [info]: i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 15% 24% 15% 6% 7% 7% 9% 7% 9%
---[NoImage] x264 [info]: ref P L0: 88.3% 7.5% 2.2% 2.0%
---[NoImage] x264 [info]: ref B L0: 81.1% 18.9%
---[NoImage] x264 [info]: ref B L1: 94.7% 5.3%
---[NoImage] x264 [info]: kb/s:6688.59
---[NoImage] encoded 183032 frames, 32.98 fps, 6688.59 kb/s
--[Information] Final statistics
---[NoImage] Video Bitrate Desired: 17500 kbit/s
---[NoImage] Video Bitrate Obtained (approximate): 6690 kbit/s
--[Information] [4/4/2010 6:57:09 PM] Postprocessing
---[Information] Deleting intermediate files
----[Information] [4/4/2010 6:57:09 PM] Successfully deleted E:\4 Peliculas\Render\VegasEdits.stats
----[Information] [4/4/2010 6:57:09 PM] Successfully deleted E:\4 Peliculas\Render\VegasEdits.stats.mbtree
--[Information] [4/4/2010 6:57:09 PM] Job completed
nurbs
4th April 2010, 22:45
---[NoImage] x264 [info]: frame I:8680 Avg QP:11.63 size:460646
---[NoImage] x264 [info]: frame P:102539 Avg QP:11.38 size: 17427
---[NoImage] x264 [info]: frame B:71813 Avg QP:11.76 size: 8316
So that's it. Set the minimum quantizer to 1 and you'll get the bitrate you want, or at least you'll get closer. You don't really need it 'cause it's just a waste of space.
JoeH
5th April 2010, 00:07
So that's it. Set the minimum quantizer to 1 and you'll get the bitrate you want, or at least you'll get closer. You don't really need it 'cause it's just a waste of space.
Thanks a lot. :thanks:
In this case, I'm preparing a video to burn to a Blu-ray disc, so I've got space to kill!
I can often see a visible difference in quality between when x264 outputs according to the type of bitrate I usually encode at (around 18000) and a bitrate around 6000 or 7000, especially in dark scenes or small gradiants of color of a large space.
nurbs
5th April 2010, 12:19
That quality difference has more to do with the quantizer than the bitrate. IIRC the default minimum quantizer is 10 so the decoder doesn't waste bits when you wouldn't see the difference so that the rest of the file has better quality, but I guess there are some rare situations where it could help to go lower. Since your target is blu-ray you got plenty of space anyway so that doesn't really matter for you.
Cyber-Mav
5th April 2010, 15:54
i use a minimum quant of 8 to get better quality, it especially helps out on high complexity screens. do some test encodes and see how it is.
nurbs
5th April 2010, 16:20
Doesn't high complexity stuff get encoded at a higher quantizer because the quality loss is less noticable?
hajj_3
12th April 2010, 21:08
im having this problem:
http://i40.tinypic.com/2dilkp2.jpg
1st pass encodes fine but then the 2nd pass doesn't display the time remaing for the encode or fps etc. It stays like this for the whole encode then gives an error.
The .avs file was created with megui file indexer, here is the .avs file contents:
LoadPlugin("C:\Users\Sdesktop\Desktop\megui2\tools\dgindex\DGDecode.dll")
DGDecode_mpeg2source("F:\golf day 1.d2v", info=3)
LoadPlugin("C:\Users\Sdesktop\Desktop\megui2\tools\avisynth_plugin\ColorMatrix.dll")
ColorMatrix(hints=true, interlaced=true, threads=0)
LoadPlugin("C:\Users\Sdesktop\Desktop\megui2\tools\avisynth_plugin\LeakKernelDeint.dll")
LeakKernelDeint(order=1,sharp=true)
crop( 2, 6, -2, -2)
Lanczos4Resize(1280,720) # Lanczos4 (Sharp)
#denoise
nakTT
13th April 2010, 13:15
Hi Zathor,
Can we expect an update to the latest version of OggVorbis used in MeGUI in the near future?
:thanks:
merlinmage
13th April 2010, 14:23
How can I encode only a part of my Source(AVS file)?
I wanted to extract a clip from a longer video without putting it into an editing program and render this again.
Guest
13th April 2010, 14:38
How can I encode only a part of my Source(AVS file)? Use Trim().
thedozer
13th April 2010, 14:51
How can I encode only a part of my Source(AVS file)?
Use the "AVS cutter" under MeGUI's Tools menu
tebasuna51
13th April 2010, 15:32
Can we expect an update to the latest version of OggVorbis used in MeGUI in the near future?
Where there are a windows stable lastest version of ogg encoder?
zanuda
13th April 2010, 16:20
Where there are a windows stable lastest version of ogg encoder?
http://www.hydrogenaudio.org/forums/index.php?showtopic=79762&st=25
nakTT
13th April 2010, 17:50
Where there are a windows stable lastest version of ogg encoder?
The one used by people at HidrogenAudio, hosted at rarewares is crashing all the time. That is why I post the question here perhaps someone here have a self-compiled version that can be share with all of us.
:thanks:
tebasuna51
14th April 2010, 01:17
http://www.hydrogenaudio.org/forums/index.php?showtopic=79762&st=25
Yep, crash with AviSynth:
http://www.hydrogenaudio.org/forums/index.php?showtopic=79762&view=findpost&p=697701
rtjnyoface
21st April 2010, 11:10
Hey guys, I just wanted to pop in again and say thanks to the devs for continuing the work on megui. I really love the program despite not using many of its features and I was crushed when dev stopped for awhile. I've been very happy to see dev continue. So, thanks guys, I really appreciate the work :).
tebasuna51
21st April 2010, 13:02
Yep, crash with AviSynth
Seems last oggenc2.87-1.3.1 in http://www.rarewares.org/ works now with AviSynth.
The command line to use can be:
oggenc2 --ignorelength -q <QUALITY> -o "<FILENAME>.ogg" -
or
oggenc2 --ignorelength -b <KBPS> -o "<FILENAME>.ogg" -
Relevant info about the parametres:
-b, --bitrate Choose a nominal bitrate to encode at. Attempt
to encode at a bitrate averaging this. Takes an
argument in kbps. By default, this produces a VBR
encoding, equivalent to using -q or --quality.
See the --managed option to use a managed bitrate
targetting the selected bitrate.
-q, --quality Specify quality between -2 (low) and 10 (high),
instead of specifying a particular bitrate.
This is the normal mode of operation.
Fractional qualities (e.g. 2.75) are permitted
The default quality level is 3.
--ignorelength Ignore the datalength in wav headers. This will allow
support for files > 4GB and STDIN data streams.
-o, --output=fn Write file to fn (only valid in single-file mode)
INPUT FILES:
OggEnc input files must currently be 32, 24, 16, or 8 bit PCM WAV,
or 32 bit IEEE floating point WAV. Files may be mono or stereo
(or more channels) and any sample rate.
You can specify taking the file from stdin by using - as the input filename.
Works fine until 6 channels, 7 and 8 channels have, at least, channel mapping problems.
Other audio encoder than can be added to MeGUI is Flac (don't exist any lossless output).
FLAC v.1.2.1b also in rarewares can be used with command line like this:
flac --ignore-chunk-sizes --channel-map=none -8 --output-name="<FILENAME>.flac" -
Recommended AviSynth filter:
AudioBits(last)>24 ? ConvertAudioTo24bit(last) : last
Zathor
24th April 2010, 18:42
0.3.4.13
- [HDBDStreamExtractor] DTS output type option for DTS-MA or DTS-HR extracts only the core DTS track. Feature Request #2695340
- [x264Encoder] fixed rc-lookahead. Bug #2991069
- [OSInfo] improved .NET 4.0 detection. Bug #2988751
- [x264Settings] changed the default b-pyramid value to normal
- [x264Config] fixed the log file button
- [UpdateWindow] added platform type
- [UpdateWindow] only the platform matching updates will be downloaded
- if the x64 MeGUI build is used only x64_64.exe is referenced
merlinmage
24th April 2010, 22:39
I have one question regarding the different settings and parameters in MeGUI.
Currently I use Fraps on my PC with an HDTV (1080p) for recording ingame material of WoW and CoD 6 for example.
My question is, should I use the BluRay Insane profile given in MeGUI or is there any other profile that suits these sort of source input better?
AMED
29th April 2010, 06:45
I'm getting some weird queue behavior when there are encoding jobs with the same name filenames when using 2 workers.
http://i41.tinypic.com/2q21k3k.png
http://i40.tinypic.com/wjckyu.png
The pics sort of explains the problem, there are 2 workers running but for some reason they are both processing the same job 7. if you look in the log you can see jobs 4, 5 and 7 are processed twice.
Taurus
29th April 2010, 08:06
Since last update (dev) aften encoder errrors out.
Former version works right.
Here are the log files:
[Error] Log
-[Information] Versions
--[NoImage] MeGUI Version : 0.3.4.13
--[NoImage] OS : Windows XP Professional x86 SP3 (5.1.196608.2600)
--[NoImage] Latest .Net Framework installed : 3.5 (3.5.30729.01)
--[NoImage] Avisynth Version : 2.5.8.5
-[Error] Log for job2 (audio, Don`t you.wav -> Don`t you.ac3)
--[Information] [29.04.2010 08:51:12] Started handling job
--[Information] [29.04.2010 08:51:12] Preprocessing
--[NoImage] Avisynth script
---[NoImage] LoadPlugin("C:\Programme\megui\tools\avisynth_plugin\NicAudio.dll")
---[NoImage] RaWavSource("G:\Wave\Don`t you.wav")
---[NoImage] Normalize()
---[NoImage] return last
--[NoImage] Commandline used: -readtoeof 1 -b 448 - "{0}"
--[Information] [29.04.2010 08:51:12] Encoding started
--[Information] [29.04.2010 08:51:12] Encode thread started
--[Information] [29.04.2010 08:51:12] Avisynth script environment opened
--[Information] [29.04.2010 08:51:12] Script loaded
--[Information] Output Decoder
---[NoImage] Channels: 2
---[NoImage] Bits per sample: 16
---[NoImage] Sample rate: 48000
--[NoImage] Commandline: C:\Programme\megui\tools\aften\aften.exe -readtoeof 1 -b 448 - "G:\Wave\Don`t you.ac3"
--[Error] An error occurred
---[NoImage] Exception message: Can't start encoder: Der Thread ist deaktiviert. Auf die Priorität kann nicht zugegriffen werden.
---[NoImage] Stacktrace
----[NoImage] bei MeGUI.AviSynthAudioEncoder.createEncoderProcess(AviSynthClip a)
----[NoImage] bei MeGUI.AviSynthAudioEncoder.encode()
---[NoImage] Inner exception
----[NoImage] Exception message: Der Thread ist deaktiviert. Auf die Priorität kann nicht zugegriffen werden.
----[NoImage] Stacktrace
-----[NoImage] bei System.Threading.Thread.SetPriorityNative(Int32 priority)
-----[NoImage] bei MeGUI.AviSynthAudioEncoder.createEncoderProcess(AviSynthClip a)
----[NoImage] Inner exception: null
--[Information] [29.04.2010 08:51:13] Job completed
Her is the log file from the working older aften:
[Information] Log
-[Information] Versions
--[NoImage] MeGUI Version : 0.3.4.13
--[NoImage] OS : Windows XP Professional x86 SP3 (5.1.196608.2600)
--[NoImage] Latest .Net Framework installed : 3.5 (3.5.30729.01)
--[NoImage] Avisynth Version : 2.5.8.5
-[Information] Log for job1 (audio, Don`t you.wav -> Don`t you.ac3)
--[Information] [29.04.2010 08:32:08] Started handling job
--[Information] [29.04.2010 08:32:13] Preprocessing
--[NoImage] Avisynth script
---[NoImage] LoadPlugin("C:\Programme\megui\tools\avisynth_plugin\NicAudio.dll")
---[NoImage] RaWavSource("G:\Wave\Don`t you.wav")
---[NoImage] Normalize()
---[NoImage] return last
--[NoImage] Commandline used: -readtoeof 1 -b 448 - "{0}"
--[Information] [29.04.2010 08:32:13] Encoding started
--[Information] [29.04.2010 08:32:13] Encode thread started
--[Information] [29.04.2010 08:32:13] Avisynth script environment opened
--[Information] [29.04.2010 08:32:16] Script loaded
--[Information] Output Decoder
---[NoImage] Channels: 2
---[NoImage] Bits per sample: 16
---[NoImage] Sample rate: 48000
--[NoImage] Commandline: C:\Programme\megui\tools\aften\aften.exe -readtoeof 1 -b 448 - "G:\Wave\Don`t you.ac3"
--[Information] [29.04.2010 08:32:17] Encoder process started
--[NoImage] Output from encoder via stderr
---[NoImage] Aften: A/52 audio encoder
---[NoImage] Version SVN
---[NoImage] (c) 2006-2007 Justin Ruggles, Prakash Punnoor, et al.
---[NoImage] input format: Microsoft WAVE Signed 16-bit little-endian 48000 Hz stereo
---[NoImage] output format: 48000 Hz stereo (2/0)
---[NoImage] SIMD usage: MMX SSE
---[NoImage] Threads: 1
---[NoImage] progress: 100% | q: 338.4 | bw: 60.0 | bitrate: 448.0 kbps
--[Information] [29.04.2010 08:32:33] Postprocessing
---[Information] Deleting intermediate files
--[Information] [29.04.2010 08:32:33] Job completed
This is on two Athlon XP machines, WinXP SP3.
On an Intel machine both versions work fine
So I guess its a compiler problem ICL11 maybe?
There are some optimations in ICL11 that are known to crash AMD's if not modified.
Please switch back to older version or all people with older hardware will come here to shout and haunt you :p.
Zathor
29th April 2010, 15:13
I'm getting some weird queue behavior when there are encoding jobs with the same name filenames when using 2 workers.
The pics sort of explains the problem, there are 2 workers running but for some reason they are both processing the same job 7. if you look in the log you can see jobs 4, 5 and 7 are processed twice.
Can you please provide the log file?
Since last update (dev) aften encoder errrors out.
Former version works right.
This is on two Athlon XP machines, WinXP SP3.
On an Intel machine both versions work fine
So I guess its a compiler problem ICL11 maybe?
There are some optimations in ICL11 that are known to crash AMD's if not modified.
Please switch back to older version or all people with older hardware will come here to shout and haunt you :p.
Thanks, I have used the least optimized version and if even this does not work I have to switch back to the old one.
I have one question regarding the different settings and parameters in MeGUI.
Currently I use Fraps on my PC with an HDTV (1080p) for recording ingame material of WoW and CoD 6 for example.
My question is, should I use the BluRay Insane profile given in MeGUI or is there any other profile that suits these sort of source input better?
This depends on your desired quality and your target device(s).
AMED
29th April 2010, 20:28
@Zathor
The log is too big to put in a single post so i have uploaded it to mediafire.
http://www.mediafire.com/?wgjz0ajayid
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.