MeGUI: bug reports and feature requests [Archive] - Page 26

doc_dvxm

7th July 2010, 10:42

same answer as above. megui automatically made a backup folder with your old presets.
read this post if you need your old presets: http://forum.doom9.org/showthread.php?p=1415179#post1415179

:)

Thanx.. Fixed.

Cisco7

7th July 2010, 11:18

Very good work, developpers. I wonder why you wait so long to add the bits*pixels ratio in the bitrate calculator. Anyway you did and you will continue doing an incredible work for people like me who wants to control anything while encoding videos (I used to encode with Gordian Knot few years ago), update feature is amazing (I replace stable url by developpement url in the settings, I like to have newest and fresh tools to encode my videos) many thanks !

nurbs

7th July 2010, 11:23

I wonder why you wait so long to add the bits*pixels ratio in the bitrate calculator.
I guess since it's completely useless it wasn't priority.

Sharktooth

9th July 2010, 03:58

new megui dev build:

0.3.5.3
- (sharktooth) [x264ConfigurationPanel] Trigger GenericUpdate() on macroblockOptions.SelectIndex change to keep coherency between macroblock options checkboxes and commandline generation
- (sharktooth) [x264] Added --pic-struct support
- (sharktooth) [x264] Added --fake-interlaced support
- (zathor) [x264] old nal-hrd profile values will be migrated
it adds compatibility with 0.3.5.1 and older presets

Sharktooth

9th July 2010, 04:15

for a stupid copy&paste mistake please re-download the 0.3.5.3 update otherwise the newly added x264 settings wont be saved into your presets...

Guest

12th July 2010, 03:02

I'm probably stupid but update does not work for me. It does the update and restarts but it's still the old version (0.3.1.1058) and it asks me to update again. Also, I got LOTS of silly profile import errors and had to hit LOTS of cancel buttons.

Seems like this should be easy. Just think what Joe Six-Pack will experience if I can't figure it out. Usually I'm pretty good at this computer gig.

AMED

12th July 2010, 06:11

Delete all the MeGUI-core files in your update cache and try again.

there was a check put in place to see if the updates downloaded correctly, if it wasn't the user would be prompted to download it again after MeGUI was restarted

Lyle_JP

12th July 2010, 07:27

Despite the fact that I have "Use CUVID Server" unchecked, MeGUI still uses it whenever I open a .dgi file with the AVS Script Creator. It wouldn't be such a big deal except that in the latest build of DGindexNV, Graft has fixed the memory leak that allows him to deep-six the CUVID server forever, which he has now done. So this behavior of the AVS script creator could become a problem in the future.

Also, MeGUI x64 probably shouldn't have the --open-gop bluray option until an x64 build of x264 r1666 is available, no?

RyaNJ

12th July 2010, 09:23

Would there be any chance of getting WebM encoding support at some point? It would be nice since the new standard could get quite popular, quite quickly. Especially with its YouTube adoption.

Sharktooth

12th July 2010, 15:14

@Lyle_JP: i didnt develop the dgindexnv support, so i cant answer right now. i need to check the code. x264 r1666 x64 is in the megui update server... what are you talking about?

@RyaNJ: probably yes.

Zathor

12th July 2010, 15:33

Despite the fact that I have "Use CUVID Server" unchecked, MeGUI still uses it whenever I open a .dgi file with the AVS Script Creator
I cannot verify it at the moment but this would not be the intended behavior and therefore it would be a bug.

The best way to bring a bug to the attention of the developers is to open a bug report at sourceforge. If it is only posted here it may be missed.

Inspector.Gadget

12th July 2010, 16:27

It's time to phase out the CUVID server entirely anyway. See neuron2's latest few posts in the *NV thread.

Guest

12th July 2010, 16:34

Zathor and the OP are well aware of that. The problem is that the OP cannot currently stop MEGUI from using the server.

Sharktooth

12th July 2010, 17:01

ok. fixed locally. i left the cuvid support intact however the "Use CUVID Server" option now works as expected (and disabled by default since some versions).
next build will include the fix and the DG NV Tools 2020 (or newer).

Sharktooth

12th July 2010, 18:00

new build is up on the main update mirror.
changelog:
0.3.5.4
- (sharktooth) [x264ConfigurationPanel] AVCProfile and AVCLevel groupboxes Enable status now depends on the Show Advanced Settings status
- (sharktooth) [x264ConfigurationPanel] Moved Profile and Level to the main tab and made some more space for more VUI options
- (sharktooth) [DialogManager] Check the "Use CUVID Server" option status before launching CUVID server
Also DG NV Tools were updated to ver. 2020 and there are new presets for you...

Lyle_JP

12th July 2010, 18:55

@Lyle_JP: i didnt develop the dgindexnv support, so i cant answer right now. i need to check the code. x264 r1666 x64 is in the megui update server... what are you talking about?

The 64 bit x264 in your distribution is r1659, not r1666. I promise. Check for yourself. The most recent version of x64 x264 from x264.nl is also r1659.

Sharktooth

12th July 2010, 18:56

you could be possibly right... im checking...

EDIT: You're right. That happened coz i download builds from direct links instead of checking the x264.nl website...

Sharktooth

12th July 2010, 19:00

@Lyle_JP: test this version: http://komisar.gin.by/old/1666/x264.1666.generic.x86_64.exe
if it works i will upload that bin...

Lyle_JP

12th July 2010, 19:11

@Lyle_JP: test this version: http://komisar.gin.by/old/1666/x264.1666.generic.x86_64.exe
if it works i will upload that bin...

Well, my encoding now starts without error, and is running presently. Sadly, I have to be afk for a few hours, so I won't be able to test output immediately.

Sharktooth

12th July 2010, 19:12

ok. if it starts then it should be good ;)
i'll upload it to the update server. if i get some negative responses i will downgrade it to 1659. but im confident it will work flawlessly.

Sharktooth

13th July 2010, 20:53

the work on x264 configuration page is almost done. --colorprim, --colormatrix and --tranfer now are supported. when i find 2 minutes ill add also --pulldown.

Shevek

13th July 2010, 22:42

I'm stuck in a loop updating DGIndexNV to 2020

Every time I start MeGUI it tells me DGIndexNV needs updating.

I've tried emptying the update-cache and the DGIndexNV folder but it keeps updating every time.

I have checked and the <CurrentVersion /> section of AutoUpdate.xml for DGIndexNV is not being updated.

(0.3.5.4)

Sharktooth

13th July 2010, 22:52

Are you running MeGUI as Admin?

Shevek

13th July 2010, 23:05

I'm not running as admin, however I have granted my user full permission on the MeGUI folder and all subfolders/files (I don't get a UAC prompt on launch).

All other components have updated correctly and the AutoUpdate.xml file contains a correct <CurrentVersion><FileVersion>...</FileVersion><Url>...</Url></CurrentVersion> for all others.

Sharktooth

13th July 2010, 23:08

it depends where DGIndexNV is located...
however run it as admin and see if it gets updated. once you did it you can close it and launch normally

Shevek

13th July 2010, 23:18

Tried as admin, same issue.

DGIndexNV is installing to C:\Program Files\megui\tools\dgindexnv

It's backing up the current files and installing the new files.

I now have each file doubled with a .backup version (these are identical, as confirmed using BeyondCompare)

It seems to me that the update process itself is running fine until it comes to updating the AutoUpdate.xml file - it still has an empty <CurrentVersion /> for DGIndexNV

Shevek

13th July 2010, 23:23

Shevek

13th July 2010, 23:33

Next problem!

I am loading a VC-1 source (MKV container) into the Indexer and my only option is FFMSIndex - DGIndexNV is greyed out.

I have a GeForce 210 installed as a secondary video card alongside an ATI 4850 primary

Sharktooth

14th July 2010, 03:23

the first problem seems to be related to an autoupdate.xml corruption. you already fixed it, however you can delete the file and megui will regenerate it.
about the second problem, it works here with avc but i didnt test with a vc-1 mkv file coz i dont have it.
if you can upload a small clip i can test it and see where the problem lies.

Zathor

14th July 2010, 06:18

I am loading a VC-1 source (MKV container) into the Indexer and my only option is FFMSIndex - DGIndexNV is greyed out.
Please check if you have a licence.txt in the dgindexnv folder.

rack04

14th July 2010, 13:27

More info:

I switched back to stable and it updated to 2013, AutoUpdate.xml updated with correct CurrentVersion (2013) and it doesn't update again on launch.

Switch back to development again, it updated to 2020, AutoUpdate.xml updated with correct CurrentVersion (2020) and it doesn't update again on launch.

Problem solved!

Could this be because it is a fresh install of MeGUI and I cancelled the initial update, switched straight to Development and then did my update?

I have this same problem. I installed a fresh version of MeGUI and updated from the development server. Every time I open MeGUI it asks to update DGDecNV. If I switch to stable upload it downloads 2013 and doesn't ask again. If I switch to developmental it downloads 2020 and asks to update every time I open.

Does this have anything to do with DGDecNV not including CUVIDServer.

Renzz

14th July 2010, 15:18

I have this same problem. I installed a fresh version of MeGUI and updated from the development server. Every time I open MeGUI it asks to update DGDecNV. If I switch to stable upload it downloads 2013 and doesn't ask again. If I switch to developmental it downloads 2020 and asks to update every time I open.

Does this have anything to do with DGDecNV not including CUVIDServer.

Me too - exactly the same problem.

Sharktooth

14th July 2010, 17:34

as i already said... delete the autoupdate.xml file... megui will re-download all the updates an will also recreate the autoupdate file...

Renzz

14th July 2010, 18:42

as i already said... delete the autoupdate.xml file... megui will re-download all the updates an will also recreate the autoupdate file...

I did try that but it hasn't fixed it.

It seems to be reporting the current version of dgindexnv as blank - where does it get that info from?

Sharktooth

14th July 2010, 18:49

from here: http://megui.org/auto/upgrade.xml
and here (64bit) http://megui.org/auto/upgrade_x64.xml

rack04

14th July 2010, 19:13

from here: http://megui.org/auto/upgrade.xml
and here (64bit) http://megui.org/auto/upgrade_x64.xml

The problem is in the AutoUpdate.xml file. It is not recognizing the current version of dgindexnv.

--- C:/Program Files/MeGUI/AutoUpdate_orig.xml Wed Jul 14 13:09:02 2010
+++ C:/Program Files/MeGUI/AutoUpdate.xml Wed Jul 14 13:10:46 2010
@@ -836,7 +836,10 @@
<Reinstall>false</Reinstall>
<DownloadChecked>false</DownloadChecked>
<SavePath>C:\Program Files\MeGUI\tools\dgindexnv\dgindexnv.exe</SavePath>
- <CurrentVersion />
+ <CurrentVersion>
+ <FileVersion>2020</FileVersion>
+ <Url>dgindexnv_b2020.zip</Url>
+ </CurrentVersion>
<AvailableVersions>
<Version>
<FileVersion>2020</FileVersion>

Sharktooth

14th July 2010, 19:19

those xml tags are automatically generated...

Sharktooth

14th July 2010, 20:04

Shevek

14th July 2010, 20:44

Please check if you have a licence.txt in the dgindexnv folder.

That was exactly it! Now all working.

Shevek

14th July 2010, 20:46

Renzz

14th July 2010, 23:03

Mine was fine once I went back to 2013 then back to 2020.

I think the problem is to do with CUVIDserver.exe being removed from the build in ver 2020. I had manually deleted it from MEGUI's dgindexnv folder, and if I go back to 2013, CUVIDserver.exe gets reinstalled, and the update then works to 2020 - and I no longer get prompted to keep doing to upgrade. If I manually delete CUVIDserver.exe, the update window then shows my current version as blank, and it goes back to continually prompting to upgrade it.

Looks like MEGUI is somehow using CUVIDserver.exe to work out it's current version and if it's not there, you get this issue.

Shevek

14th July 2010, 23:19

I think the problem is to do with CUVIDserver.exe being removed from the build in ver 2020. I had manually deleted it from MEGUI's dgindexnv folder, and if I go back to 2013, CUVIDserver.exe gets reinstalled, and the update then works to 2020 - and I no longer get prompted to keep doing to upgrade. If I manually delete CUVIDserver.exe, the update window then shows my current version as blank, and it goes back to continually prompting to upgrade it.

Looks like MEGUI is somehow using CUVIDserver.exe to work out it's current version and if it's not there, you get this issue.

sounds plausible - I had thought the same, but not got around to testing the theory.

EDIT: Confirmed!

Without CUVIDServer.exe in directory, this is the Updater window AFTER updating. Note Existing Version is missing and Update Available:
http://i20.photobucket.com/albums/b223/DrShevek/SuperUser/MeGUI1.png

With CUVIDServer.exe in directory, this is the Updater window AFTER updating. Note Existing Version is correct and No Update Available:
http://i20.photobucket.com/albums/b223/DrShevek/SuperUser/MeGUI2.png

jimmydrac

15th July 2010, 00:09

Hey Shark...Thanks :thanks: for all your hard work!!! I'm probably having a brain fart :stupid: here but I searched for info on the new pulldown tab buy couldn't find anything. Does this have anything to do with 3:2? Any help on what this does would be greatly appreciated.

Thanks......MEGUI ROCKS!!!!!!

Sharktooth

15th July 2010, 13:03

@jimmydrac: http://en.wikipedia.org/wiki/Telecine#2:2_pulldown

@shevec: ill look into it...

Rat Killer

15th July 2010, 19:19

I only use the faac encoder once in a while so this could have changed at any point in the last few weeks but....

The options checked in the faac config do not get applied when encoding. I am using either an mkv or an .ac3 file for input and asking for an aac output, downmix to stereo and vbr of 100.

What I get is an aac file with 5 channels and approx 320kbps. This used to work fine.

Suggestions? Did I muck something up or has something in the faac front end changed or what?

Thanks for any suggestions. I can do this conversion manually with ffmpeg (command line ffmpeg -i test.ac3 -ac 2 -ab 128000 test.aac) but its much easier to keep everything inside megui.

Sharktooth

15th July 2010, 21:32

@rat killer: could you please try if it happens with nero encoder and/or vorbis too?

Rat Killer

15th July 2010, 21:52

@rat killer: could you please try if it happens with nero encoder and/or vorbis too?

Nero works fine. Should have been using it all along I suppose. Did not know the codec was free until I went looking. Thanks for the help.

Sharktooth

16th July 2010, 03:21

you're welcome. however, if nero works fine there there should be a problem with faac.

WorBry

16th July 2010, 14:58

0.3.5.5
- (sharktooth) [x264] Added --pulldown option plus some various fixes
- (sharktooth) [x264] Added --colorprim, --transfer and --colormatrix options
- (sharktooth) [x264] Added --non-deterministic support plus some cosmetic changes

development update: work on x264 options is complete. now ill focus on fixing --tune and --preset support

Thanks for the new additions. Just wondering if you are you still intending to add an AR control option?

http://forum.doom9.org/showpost.php?p=1416106&postcount=46