View Full Version : MeGUI: bug reports and feature requests
Zathor
20th September 2015, 10:26
It'll just take little while to get used to the "load defaults" function not loading the defaults in scratchpad as it did. I don't think that's a big deal either way. Maybe it'll be better as it is once I'm used to it.....
"Load defaults" for me is another word for "reset [current preset]". It was strange that it switched before to the scratchpad one and has reset there everything to default. I think only x264 has currently in the specific settings a "reset" button - which likely should be removed now.
Btw... in MeGUI the words profile and presets are several times mixed up. I am not sure myself where the difference should be (profile e.g. = x264, preset = x264 specific profile configuration?) so maybe it makes sense to rename everything - to profile?
Zathor
20th September 2015, 10:27
I said it already, avi. All I know I clicked on file indexer, that's all I ever used. Sorry I don't understand the specifics of MeGUI very much, I learned one way to encode video years ago and just do that without really caring what it actually does.
As a starting point please create the index again (so the step which takes so long time) and then please upload the MeGUI log e.g. to pastebin.com. You can find the log in the MeGUI\Log folder (please close MeGUI before you export the log so that it is written in the correct way).
LigH
20th September 2015, 10:41
Since encoders use presets to set a whole group of parameters at once, I believe you should avoid "preset" in MeGUI where possible. The set of parameters per encoder managed by MeGUI may possibly be best called "templates", I believe?!
Octo-puss
20th September 2015, 11:26
This is no satisfying amount of information. Never trust in a filename extension, there is always a chance that it has been renamed for the craziest reasons (e.g. people don't know how to assign a media player to an unassigned but correct extension so that it will start playing after a double-click in the Explorer).
To help us helping you, do an analysis of this source file using MediaInfo, and post the result in "Text" format in a CODE block (or in a pastebin service).
If you are sure that it is an AVI because you made it, you may also know which codec was used; 115 GB is really huge, so it possibly contains completely uncompressed video. It would be a pity to have uncompressed RGB video saved, what a waste of space, and furthermore it is not the optimal color space as source for modern video codecs. This would also explain why the Indexer takes aged to build an index: It will write keyframe data for really every frame, because completely uncompressed video consists of keyframes everywhere. Such a video is hard to handle by L-SMASH Source. In this case only, AviSource is to be preferred.
I think it IS uncompressed, or barely compressed. It's a game footage captured with MSI Afterburner, using some lossless codec.
That doesn't seem to be the problem though - the problem is MeGUI using the same physical disk for processing the file, resulting in extreme slowdowns.
As a starting point please create the index again (so the step which takes so long time) and then please upload the MeGUI log e.g. to pastebin.com. You can find the log in the MeGUI\Log folder (please close MeGUI before you export the log so that it is written in the correct way).
The file is gone, but I think I found the log. http://www.mediafire.com/download/lm9sge4b4qfa9eq/logfile-15-09-19_17-09-53.log
hello_hello
21st September 2015, 19:33
I said it already, avi. All I know I clicked on file indexer, that's all I ever used. Sorry I don't understand the specifics of MeGUI very much, I learned one way to encode video years ago and just do that without really caring what it actually does.
Given it's an AVI containing lossless video, you could try opening the Script Creater from the Tools menu and selecting the AVI as the input video. When MeGUI asks how you want to open it, select AviSource. No indexing required.
hello_hello
21st September 2015, 19:52
"Load defaults" for me is another word for "reset [current preset]". It was strange that it switched before to the scratchpad one and has reset there everything to default. I think only x264 has currently in the specific settings a "reset" button - which likely should be removed now.
Loading the defaults in scratchpad makes sense to me as if you have a saved encoder preset and load the defaults, the new settings are no longer those of the selected preset. Not that it matters.... either way it's not hard to work out how it works.
I've often longed for a "scratchpad" button next to "ok" and "cancel". That way you could change a preset and hit the "scratchpad" button to load the new settings in scratchpad while closing the encoder configuration, without MeGUI having to offer a dialogue box asking you what you want to do.
All the video/audio encoders have a "load defaults" button, if that's what you mean by a "reset" button. As do the OneClick and AVS profiles etc. I definitely wouldn't remove them. They're kind of like a sanity check button.
Btw... in MeGUI the words profile and presets are several times mixed up. I am not sure myself where the difference should be (profile e.g. = x264, preset = x264 specific profile configuration?) so maybe it makes sense to rename everything - to profile?
That's probably a good idea. Off the top of my head though everything has profiles, except the encoders which have presets, so it's kind of logical, but I don't know why they all couldn't be called one or the other.
hello_hello
21st September 2015, 20:41
Every so often, for reasons unexplained, it seems Avisynth doesn't load a plugin from it's auto-load directory when MeGUI opens a script (I have MeGUI set to use the "installed" Avisynth 2.6.0.6). When it happens, the problem is 100% repeatable until I restart MeGUI, then the problem goes away. Any script in the queue requiring the plugin in question will fail to encode. In the mean time, I can open the same scripts with MPC-HC without issue.
http://s10.postimg.org/8ahzau609/megui.gif
It only happens now and then, and usually loading a script while another one is being encoded seems to be where the problem starts, but would it be fair to assume this will remain one of life's unexplained mysteries? :)
I was having trouble making sense of the log file because my attempts at loading scripts seemed to be mixed up with the jobs that were running, but below is the error for a job in the queue that failed to run.
-[Error] Log for job93 (video, Ep1x07.mkv.avs -> Ep1x07.mkv.mkv)
--[Information] [22/09/15 3:15:19 AM] Started handling job
--[Information] [22/09/15 3:15:19 AM] Preprocessing
--[Information] [22/09/15 3:15:19 AM] Avisynth input script
---[NoImage] LoadPlugin("C:\Program Files\MeGUI\tools\ffms\ffms2.dll")
---[NoImage] FFVideoSource("E:\Extras\Ep1x07.mkv", cachefile="D:\Ep1x07.mkv.ffindex", fpsnum=24000, fpsden=1001, threads=1)
---[NoImage] QTGMC(InputType=1)
---[NoImage] crop(2, 0, -2, 0)
---[NoImage] Spline36Resize(832,468)
---[NoImage] gradfun3()
--[Error] [22/09/15 3:15:20 AM] Error starting job
---[Error] [22/09/15 3:15:20 AM] Exception message
----[NoImage] Calling setup of processor failed with error 'The file D:\Ep1x07.mkv.avs cannot be opened.
----[NoImage] Error message for your reference: Script error: there is no function named "MSuper"
----[NoImage] (QTGMC 3.33s (mod).avsi, line 436)
----[NoImage] (D:\Ep1x07.mkv.avs, line 4)'
---[Error] [22/09/15 3:15:20 AM] Stacktrace: at MeGUI.core.gui.JobWorker.startEncoding(TaggedJob job)
---[Error] [22/09/15 3:15:20 AM] Inner exception: null
Zathor
21st September 2015, 20:43
If you have a OneClick profile where video encoding is disabled, when you select it, under the Advanced config tab the "display aspect ratio" option becomes greyed out. After changing back to a OneClick profile where video re-encoding is enabled though, the "display aspect ratio" option remains greyed out until you close the OneClick encoder and re-open it.
I want to fix this but cannot reproduce it. I have two profiles with enabled/disabled video and switching between them enabled/disables that AR option as it should be. Any hints what I do wrong?
All the video/audio encoders have a "load defaults" button, if that's what you mean by a "reset" button. As do the OneClick and AVS profiles etc. I definitely wouldn't remove them. They're kind of like a sanity check button
No, I meant the "Default Settings" button in the x264 profile in the "Misc" tab. This one is now obsolete.
EDIT:
It only happens now and then, and usually loading a script while another one is being encoded seems to be where the problem starts, but would it be fair to assume this will remain one of life's unexplained mysteries? :)
How much memory is consumed by MeGUI at that moment?
hello_hello
21st September 2015, 21:01
I want to fix this but cannot reproduce it. I have two profiles with enabled/disabled video and switching between them enabled/disables that AR option as it should be. Any hints what I do wrong?
Sorry, because no, it doesn't seem to work for me that way. I don't know if I'm doing something odd.
Profile with video encoding disabled:
http://s16.postimg.org/6jg2jbwdh/oc1.gif
Profile with video encoding enabled. Manually enabling it without changing profiles still results in a greyed out drop down aspect ratio arrow. Opening a video gets the correct aspect ratio to display, but the drop down arrow is still disabled:
http://s27.postimg.org/3lv6toxsz/oc2.gif
After restarting the OneClick encoder. No settings changed in between:
http://s13.postimg.org/qm0i1vep3/oc3.gif
I rarely use the OneClick encoder, but it was something I noticed.
No, I meant the "Default Settings" button in the x264 profile in the "Misc" tab. This one is now obsolete.
Ahhhhh..... the button to reload the preset's settings doesn't work any more either. I'd forgotten about those two.
hello_hello
21st September 2015, 21:05
How much memory is consumed by MeGUI at that moment?
At the moment: 3,384K (it's running an encode)
When it happened, I don't know as I didn't look before restarting MeGUI. I shall next time. I'm still running XP so maybe it is just a memory issue.
Zathor
21st September 2015, 23:00
Sorry, because no, it doesn't seem to work for me that way. I don't know if I'm doing something odd.
Still works for me as expected. Maybe related to XP?
Ahhhhh..... the button to reload the preset's settings doesn't work any more either. I'd forgotten about those two.
Sorry, this button also works for me :(
hello_hello
22nd September 2015, 00:35
Still works for me as expected. Maybe related to XP?
I guess anything's possible......
Sorry, this button also works for me :(
I had another play and it's kind of working for me.
I previously tested it by selecting a preset, loading the default x264 settings, then using the "preset settings" button. I think now because the defaults are loaded in the current preset, if they're loaded first they become the preset settings so the preset settings button appears not to work.
Also for me, no changes under the Misc tab seem to be altered when using the "preset settings" button. I can't remember if that's always been the case, but it probably shouldn't be. The Misc settings should be reverted too.
Edit: A bit more testing seems to indicate the "preset settings" button is more hit and miss than I thought. None of the settings under the Main tab seem to be effected by it. It reverts any changes to the deblock settings and number of B frames but the B Frame bias setting is unaffected by it. I haven't tested everything but I can't see a pattern to what it reverts and what it doesn't. Odd.....
There is a difference between the main "load defaults" button and the "default settings" button under the Misc tab. The former resets everything to the defaults, whereas the latter leaves the custom command line area alone, and doesn't make all the advanced settings tabs disappear, which means I'd probably be more inclined to use it now I've refreshed my memory as to how it works. :)
Unless all of the above works differently when you're not using XP.....
I really should pull my finger out and get the new PC build under way.
tormento
23rd September 2015, 10:15
Is there a way to get as included AviSynth the 2.6 MT (http://forum.doom9.org/showthread.php?p=1312666#post1312666) one instead of standard AviSynth?
I have tried to manually replace but it's overwritten at every startup.
Morku
25th September 2015, 18:53
When I delete a Preset (I created) in x264 configuration dialog, it is back when I restart MeGUI, so I need delete manually in explorer. Just saying.
hello_hello
25th September 2015, 19:09
Is there a way to get as included AviSynth the 2.6 MT (http://forum.doom9.org/showthread.php?p=1312666#post1312666) one instead of standard AviSynth?
I have tried to manually replace but it's overwritten at every startup.
I'm pretty sure if you replace avisynth.dll in the "MeGUI\tools\avs" folder, that'll do the trick as it's the avisynth.dll MeGUI is copying and using to replace the other ones.
tormento
25th September 2015, 19:13
I'm pretty sure if you replace avisynth.dll in the "MeGUI\tools\avs" folder, that'll do the trick as it's the avisynth.dll MeGUI is copying and using to replace the other ones.
LOL. You are right and I'm working too much.
Zathor
27th September 2015, 12:28
When I delete a Preset (I created) in x264 configuration dialog, it is back when I restart MeGUI, so I need delete manually in explorer. Just saying.
Works for me :( Which MeGUI version do you have?
EDIT: I was able to reproduce it now...
EDIT2: Fixed in 2592
I received a bug report that lsmash cannot deal with 10 bit sources.
http://sourceforge.net/p/megui/bugs/812/
After some investigation this seems to be true:
http://forum.doom9.org/showthread.php?p=1713627#post1713627
In any case I have to check if the source is > 8bit. Question is what to do then:
- ignore lsmash (and use ffms)
- or add the format="YUV420P8" or format="YUV420P16" (stacked) as mentioned a few posts below
Sorry, because no, it doesn't seem to work for me that way. I don't know if I'm doing something odd.
I have tried to reproduce the OnceClick profile button oddness with my virtual XP machine and there ii works also as expected. Are you able to upload your profiles which you use for the test?
Zathor
27th September 2015, 13:54
2594 [Update] fixed update installation detection (regression of 2586)
2593 [L-SMASH Indexer] improved support for 10bit files
2592 [Profile] fixed profile deletion (regression of 2590)
2591 [AudioEncoder] improved job abort and priority change. Bug #813
Morku
27th September 2015, 14:45
Thanks for the fix.
Another question:
Why does the updater delete any other file when tools get updated?
For example, when I got the qaac update, I had to copy back the DLL files from Apple to make qaac work again.
I also like to keep the x64 files of qaac and dgindexnv in the same folder, but x64 builds aren't part of the updates, so they get deleted, too.
Zathor
27th September 2015, 16:51
Why does the updater delete any other file when tools get updated?
In order to have a clean environment. Runtime files may be different, obsolete other files, ...
For example, when I got the qaac update, I had to copy back the DLL files from Apple to make qaac work again.
Thanks for the hint. These files should stay. Do you know which should not be deleted? I will then exclude them.
EDIT: found it
I also like to keep the x64 files of qaac and dgindexnv in the same folder, but x64 builds aren't part of the updates, so they get deleted, too.
Easiest way is to create a new directory in tools. E.g. .\tools\qaac_x64
Barough
27th September 2015, 17:15
Another question:
Why does the updater delete any other file when tools get updated?
For example, when I got the qaac update, I had to copy back the DLL files from Apple to make qaac work again.
<snip>
Was about to ask the same myself. The update function didn't remove them earlier.
All files in the QTfiles folder got renamed to *.backup after the latest qaac update
Zathor
27th September 2015, 17:24
2598 [Log] delete log files after 90 days
2597 [QAAC] do not delete portable dll files during update
2596 [DGIndexIM/NV] improved error handling
2595 [DGIndexIM/NV] fixed crash when the indexer directory is not available (regression of 2585)
Barough
27th September 2015, 17:30
Thnx for the fixes Zathor :)
hello_hello
27th September 2015, 20:13
Zathor,
MeGUI 2598 is deleting the SelectedProfiles.xml file when it runs (or when it closes) and as a result, the selected profiles function is broken. Edit: I tried copying SelectedProfiles.backup and renaming it to SelectedProfiles.html and the html file isn't being deleted when MeGUI starts any longer, but MeGUI seems to be ignoring it anyway. Something odd is going on there.
Creating backups for all the profiles, that's new isn't it? Is there a reason for doing so? (I'm just curious)
I'll upload my OneClick profiles for you shortly.
Cheers.
hello_hello
27th September 2015, 20:28
Seems the change to not delete the portable files when updating QAAC isn't working as expected. MeGUI is isn't deleting them, but it's changing their file extensions to "backup".
Feature request:
Could we have an option for MeGUI not to delete old files, such as old log files? The latter certainly took me by surprise after the last update. It also annoyed me a bit. I sometimes search through old log files to help me remember what filtering I might have used for a particular encode, or what the source file was etc, and up until a few minutes ago I could use the Windows search function to quickly search through three or fours years worth of log files. Now it only goes back a few months.....
"Fortunately" my second PC had a hard drive failure a few days ago, so I copied the MeGUI folder from this PC to the other one and I now know to at least backup those log files before updating MeGUI there.
And those old files in the update_cache folder marked as obsolete..... I backed that folder up as soon as a saw it happen, but what should I expect there? I assume at some stage MeGUI will delete them all without asking?
Thanks.
hello_hello
27th September 2015, 20:48
I have tried to reproduce the OnceClick profile button oddness with my virtual XP machine and there ii works also as expected. Are you able to upload your profiles which you use for the test?
I created two new profiles, as mine use my own encoder configurations, so they'd probably give you errors when you try to load them. These OneClick profiles use "scratchpad" encoder and avisynth presets, but the oddness hasn't changed.
no video encode profile:
<?xml version="1.0"?>
<GenericProfileOfOneClickSettings xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<Name>no video encode</Name>
<Settings>
<VideoProfileName>x264: *scratchpad*</VideoProfileName>
<AvsProfileName>AviSynth: *scratchpad*</AvsProfileName>
<PrerenderVideo>false</PrerenderVideo>
<AudioProfileName>migrated</AudioProfileName>
<AudioEncodingModeString>migrated</AudioEncodingModeString>
<AudioSettingsString>
<OneClickAudioSettings>
<AudioEncodingModeString>Always</AudioEncodingModeString>
<Language>[default]</Language>
<Profile>FFmpeg AC-3: *scratchpad*</Profile>
<UseFirstTrackOnly>true</UseFirstTrackOnly>
</OneClickAudioSettings>
</AudioSettingsString>
<DontEncodeVideo>true</DontEncodeVideo>
<SignalAR>false</SignalAR>
<AutomaticDeinterlacing>false</AutomaticDeinterlacing>
<AutoCrop>true</AutoCrop>
<KeepInputResolution>true</KeepInputResolution>
<OutputResolution>720</OutputResolution>
<Filesize xsi:nil="true" />
<SplitSize xsi:nil="true" />
<ContainerCandidates>
<string>AVI</string>
<string>MKV</string>
</ContainerCandidates>
<LeadingName />
<WorkingNameReplace />
<WorkingNameReplaceWith />
<UseChaptersMarks>true</UseChaptersMarks>
<UseNoLanguagesAsFallback>false</UseNoLanguagesAsFallback>
<DisableIntermediateMKV>false</DisableIntermediateMKV>
<DefaultWorkingDirectory>D:\</DefaultWorkingDirectory>
<DefaultOutputDirectory>D:\</DefaultOutputDirectory>
<DefaultLanguage>English</DefaultLanguage>
<DefaultAudioLanguageString>
<string>English</string>
</DefaultAudioLanguageString>
<DefaultSubtitleLanguageString>
<string>English</string>
</DefaultSubtitleLanguageString>
<IndexerPriorityString>
<string>DGI</string>
<string>DGM</string>
<string>D2V</string>
<string>LSMASH</string>
<string>FFMS</string>
<string>AVISOURCE</string>
</IndexerPriorityString>
</Settings>
</GenericProfileOfOneClickSettings>
with video encode profile:
<?xml version="1.0"?>
<GenericProfileOfOneClickSettings xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<Name>with video encode</Name>
<Settings>
<VideoProfileName>x264: *scratchpad*</VideoProfileName>
<AvsProfileName>AviSynth: *scratchpad*</AvsProfileName>
<PrerenderVideo>false</PrerenderVideo>
<AudioProfileName>migrated</AudioProfileName>
<AudioEncodingModeString>migrated</AudioEncodingModeString>
<AudioSettingsString>
<OneClickAudioSettings>
<AudioEncodingModeString>Always</AudioEncodingModeString>
<Language>[default]</Language>
<Profile>FFmpeg AC-3: *scratchpad*</Profile>
<UseFirstTrackOnly>true</UseFirstTrackOnly>
</OneClickAudioSettings>
</AudioSettingsString>
<DontEncodeVideo>false</DontEncodeVideo>
<SignalAR>false</SignalAR>
<AutomaticDeinterlacing>false</AutomaticDeinterlacing>
<AutoCrop>true</AutoCrop>
<KeepInputResolution>false</KeepInputResolution>
<OutputResolution>720</OutputResolution>
<Filesize xsi:nil="true" />
<SplitSize xsi:nil="true" />
<ContainerCandidates>
<string>AVI</string>
<string>MKV</string>
</ContainerCandidates>
<LeadingName />
<WorkingNameReplace />
<WorkingNameReplaceWith />
<UseChaptersMarks>true</UseChaptersMarks>
<UseNoLanguagesAsFallback>false</UseNoLanguagesAsFallback>
<DisableIntermediateMKV>false</DisableIntermediateMKV>
<DefaultWorkingDirectory>D:\</DefaultWorkingDirectory>
<DefaultOutputDirectory>D:\</DefaultOutputDirectory>
<DefaultLanguage>English</DefaultLanguage>
<DefaultAudioLanguageString>
<string>English</string>
</DefaultAudioLanguageString>
<DefaultSubtitleLanguageString>
<string>English</string>
</DefaultSubtitleLanguageString>
<IndexerPriorityString>
<string>DGI</string>
<string>DGM</string>
<string>D2V</string>
<string>LSMASH</string>
<string>FFMS</string>
<string>AVISOURCE</string>
</IndexerPriorityString>
</Settings>
</GenericProfileOfOneClickSettings>
Zathor
27th September 2015, 22:27
Seems the change to not delete the portable files when updating QAAC isn't working as expected. MeGUI is isn't deleting them, but it's changing their file extensions to "backup".
I need to test it with backup enabled.
EDIT: works as expected. are you sure qaac has been updated with build 2598? Or which portable files do you use?
Could we have an option for MeGUI not to delete old files, such as old log files?
Mhm, I can merge this option with the backup option. So if backup is disabled it will delete the files, if not they stay.
Zathor
27th September 2015, 22:47
MeGUI 2598 is deleting the SelectedProfiles.xml file when it runs (or when it closes) and as a result, the selected profiles function is broken. Edit: I tried copying SelectedProfiles.backup and renaming it to SelectedProfiles.html and the html file isn't being deleted when MeGUI starts any longer, but MeGUI seems to be ignoring it anyway. Something odd is going on there.
The file extension is xml :)
I found the problem and have fixed it locally.
Creating backups for all the profiles, that's new isn't it? Is there a reason for doing so? (I'm just curious)
Yes, if the new xml file cannot be created the backup will be restored. But as this will be done in one step I should delete the backup files at the end.
hello_hello
27th September 2015, 23:07
The file extension is xml :)
I found the problem and have fixed it locally.
I wrote xml the first time, but now I can't remember whether I renamed it xml or html for testing. Oh well.... you've found the problem anyway.
Thanks.
LeMoi
28th September 2015, 17:21
With latest version (2598), every time I launch the program, my default video profile always changes to x264: Android G1, instead of the one i always use. This did'nt happen with previous versions...
Zathor
28th September 2015, 18:51
2601 [OneClick] fixed DAR button behaviour
2600 obsolete packages and log files will only be deleted if the backup option is disabled
2599 [Profile] fixed unsaved selected profile (regression of 2590)
hello_hello
28th September 2015, 23:08
Awesome! I haven't downloaded the update yet, but thanks!
So the OneClick DAR button problem..... I wasn't imagining it? What was the cause?
Cheers.
LeMoi
28th September 2015, 23:10
Can't find the update yet with the MEGUI included updater?
kotuwa
28th September 2015, 23:12
Today I updated MeGUI. Development Servers.
and faced a thing that I never faced yesterday. Not sure whether the reason is the updating it or something else changed in the system.
FFAudioSource failed to open a MKV file, that was opened successfully before updating.
It gives this message in the Log.
Failed opening the file with FFAudioSource(). Script error: There is no function named 'HelpMeRondaLoadPlugin'.
NicAudio, LWLibavAudioSource used for AC-3, LWLibavAudioSource used for MKV as FFAudioSource fails.
Any idea why, and how to fix!
:/
hello_hello
28th September 2015, 23:18
I need to test it with backup enabled.
EDIT: works as expected. are you sure qaac has been updated with build 2598? Or which portable files do you use?
Sorry, I missed your question earlier.
Yes, I'm sure QAAC was updated. It went through the "build 2598 is required" process on both PCs and restarted MeGUI before then updating QAAC.
QAAC is in the "MeGUI\tools\qaac" folder.
The portable files are located in "MeGUI\tools\qaac\QTfiles"
QTfiles has a subfolder: "MeGUI\tools\qaac\QTfiles\Microsoft.VC80.CRT"
All the files in the "QTfiles" and "Microsoft.VC80.CRT" folders had backup added as their file extension.
At least it's not just me this time. ;)
http://forum.doom9.org/showthread.php?p=1740628#post1740628
Zathor
28th September 2015, 23:24
FFAudioSource failed to open a MKV file, that was opened successfully before updating.
Sorry, silly remaining code in the sources. It is now fixed with build 2602 (online on one of the two servers as the other is currently not available)
Zathor
28th September 2015, 23:26
Sorry, I missed your question earlier.
Yes, I'm sure QAAC was updated. It went through the "build 2598 is required" process on both PCs and restarted MeGUI before then updating QAAC.
QAAC is in the "MeGUI\tools\qaac" folder.
The portable files are located in "MeGUI\tools\qaac\QTfiles"
QTfiles has a subfolder: "MeGUI\tools\qaac\QTfiles\Microsoft.VC80.CRT"
All the files in the "QTfiles" and "Microsoft.VC80.CRT" folders had backup added as their file extension.
At least it's not just me this time. ;)
http://forum.doom9.org/showthread.php?p=1740628#post1740628
I have all necessary files directly copied in the qaac directory without any subdirectories. Can you try that as well please? Btw I have used the recent makeportable script with the recent Itunes installer.
kuchikirukia
29th September 2015, 00:23
Could we get finer control of x264 qcomp? In 2525 you can manually enter it in the box and it will enter it into the commandline, but MeGUI rounds to tenths it for display which gives a display mismatch (if you entered 0.65 you can't just look at the qcomp box to see what you have entered since it's now saying 0.7.), and the arrows move it by tenths. Considering the rather large effect, movement by hundredths makes more sense than tenths, and it should certainly display to hundredths. Going from qcomp of 0.6 to 0.7 can increase file size in CRF encoding upwards of 25%, and 0.8 is pretty much always going to be complete bloat, so going by tenths basically only gives you the option of, "Do I want qcomp 0.60 or 0.70?"
hello_hello
29th September 2015, 03:46
I have all necessary files directly copied in the qaac directory without any subdirectories. Can you try that as well please? Btw I have used the recent makeportable script with the recent Itunes installer.
I tried that and some of the files had the extension backup added and some didn't. Here's a list of the extracted Apple files before re-installing QAAC:
From the QTfiles folder
ASL.dll
CoreAudioToolbox.dll
CoreFoundation.dll
icudt46.dll*
icuin40.dll*
icuuc40.dll*
libdispatch.dll
libicuin.dll
libicuuc.dll
objc.dll
pthreadVC2.dll*
From the Microsoft.VC80.CRT folder
Microsoft.VC80.CRT.manifest*
msvcp80.dll*
msvcr80.dll*
After copying all the files to the qaac directory and re-installing QAAC, the files marked with an asterisk were given a backup extension. The others weren't (as opposed to when they were left in the sub-directories and they were all given a backup extension).
The four original QAAC files in the QAAC folder remained, with a backup copy also created. I guess that's to be expected.
libsoxconvolver.dll
libsoxr.dll
qaac.exe
refalac.exe
I used makeportable and the QuickTime installer to extract the required files. I'm pretty sure it was makeportable 0.9 and QuickTime 7.7.7, but to be sure I downloaded them both again (QuickTime 7.7.8) and ran makeportable. Exactly the same files were extracted (still CoreAudioToolbox 7.9.8.3), just with more recent modified dates.
You're not using an old makeportable or QuickTime installer are you? I'm pretty sure the files extracted changed at some stage, but that was a fair while ago. Or does it extract different files for XP.... :(
Cheers.
kotuwa
29th September 2015, 04:27
Sorry, silly remaining code in the sources. It is now fixed with build 2602 (online on one of the two servers as the other is currently not available)
Hey, updated to 2602.
Now a different error message...
Failed opening the file with FFAudioSource(). I don't know what 'xxxx' means.
:(
Zathor
29th September 2015, 07:04
Sorry, I did not had the time to test myself and at the moment I do not have time at all. Maybe I have the chance to do it in the next 24 hours but I cannot predict it yet. If you have to encode now you have to enforce a downgrade.
Zathor
29th September 2015, 07:09
I used makeportable and the QuickTime installer to extract the required files. I'm pretty sure it was makeportable 0.9 and QuickTime 7.7.7, but to be sure I downloaded them both again (QuickTime 7.7.8) and ran makeportable. Exactly the same files were extracted (still CoreAudioToolbox 7.9.8.3), just with more recent modified dates.
You're not using an old makeportable or QuickTime installer are you? I'm pretty sure the files extracted changed at some stage, but that was a fair while ago. Or does it extract different files for XP.... :(
I have used the itunes installer 12.3 with makeportable 0.9 and my files for 32bit are different compared to yours.
LigH
29th September 2015, 07:23
The version number of some QT DLLs may change, e.g. there was a new dummy DLL released to replace the huge icudt??.dll; so you may have to exclude with wildcards.
The iTunes installer may contain a few more (or more recent) files than the QuickTime installer. Especially additional 64-bit DLLs.
hello_hello
29th September 2015, 08:29
I have used the itunes installer 12.3 with makeportable 0.9 and my files for 32bit are different compared to yours.
I've previously used the QuickTime installer as it's a much smaller download, but I downloaded the current iTunes installer (12.3) and ran makeportable. Yes it does extract different files. It also appears LigH is correct and the iTunes installer contains a newer version of CoreAudioToolbox (7.10.5.0 instead of 7.9.8.3), so now I've extracted those files, I'll update. I don't know whether that means AAC encoding will be different.
The files extracted from the iTunes installer were:
ASL.dll
CoreAudioToolbox.dll
CoreFoundation.dll
icudt55.dll
libdispatch.dll
libicuin.dll
libicuuc.dll
msvcp100.dll
msvcr100.dll
objc.dll
There was no "Microsoft.VC80.CRT" folder created.
Barough
29th September 2015, 08:44
I tried that and some of the files had the extension backup added and some didn't. Here's a list of the extracted Apple files before re-installing QAAC:
From the QTfiles folder
ASL.dll
CoreAudioToolbox.dll
CoreFoundation.dll
icudt46.dll*
icuin40.dll*
icuuc40.dll*
libdispatch.dll
libicuin.dll
libicuuc.dll
objc.dll
pthreadVC2.dll*
From the Microsoft.VC80.CRT folder
Microsoft.VC80.CRT.manifest*
msvcp80.dll*
msvcr80.dll*
After copying all the files to the qaac directory and re-installing QAAC, the files marked with an asterisk were given a backup extension. The others weren't (as opposed to when they were left in the sub-directories and they were all given a backup extension).
The four original QAAC files in the QAAC folder remained, with a backup copy also created. I guess that's to be expected.
libsoxconvolver.dll
libsoxr.dll
qaac.exe
refalac.exe
I used makeportable and the QuickTime installer to extract the required files. I'm pretty sure it was makeportable 0.9 and QuickTime 7.7.7, but to be sure I downloaded them both again (QuickTime 7.7.8) and ran makeportable. Exactly the same files were extracted (still CoreAudioToolbox 7.9.8.3), just with more recent modified dates.
You're not using an old makeportable or QuickTime installer are you? I'm pretty sure the files extracted changed at some stage, but that was a fair while ago. Or does it extract different files for XP.... :(
Cheers.
I get the same files here when using makeportable v0.9 and QuickTime v7.7.8
Zathor
29th September 2015, 19:59
2604 [QAAC] do not delete portable runtime files during an update if they are in the QTfiles subdirectory
2603 [AudioEncoder] fixed FFAudioSource. part II (regression of 2591)
hello_hello
30th September 2015, 05:02
I updated to MeGUI 2604, after which MeGUI updated QAAC again. I'd put the Apple files back in the QTfiles folder and this time they remained untouched. Thanks Zathor!
Feature request.
Could the size of the drop down box for selecting encoder presets be increased in order to eliminate the need to scroll through the list? It's just a little thing, but the number of presets is fairly limited before the maximum size is reached and scrolling is required. The same could probably be applied to all the drop down preset selections. Unless there's a need to limit the size of the dropdown lists I'm missing.
Like this (VirtualDub's file type menu):
http://s12.postimg.org/dvs9ss7f1/dropdown_list_c.gif
Or something with a larger limit before scrolling is required, and maybe able to open in either direction, depending on the position on the monitor.
http://s27.postimg.org/wmliobddv/dropdown_list_b.gif
Thanks.
hello_hello
4th October 2015, 06:51
I have what may be a "how long is a piece of string" question, but.....
The problem with the script creator's cropping and resizing causing crashes if you adjust them too enthusiastically, especially when ffmsindex is used..... why does it go away when the source video is another script, even if it's a script using ffmsindex to open the video?
The problem's started to annoy me enough now that if I know I'm going to be playing with cropping and resizing a bit, I use Avisynthesizer (https://www.mediafire.com/folder/hb26mthbjz7z6/StainlessS) (link for the StainlessS mod version) to quickly create a script, then I use that script as the source for MeGUI to open. Works a treat and cuts down on crashes, but why should it work like that? Any logical reason?
Cheers.
LigH
5th October 2015, 08:44
May be hard to guess without comparing MediaInfo reports of the real source videos against each other, or even deeper statistics (e.g. one having Blu-ray compatible short GOPs, the other having efficient long GOPs for PC use).
I could imagine that if you reload the script faster than the decoder can decode from the beginning of a GOP to the displayed position, the interrupted decoder gets unstable. Who knows... :o
hello_hello
5th October 2015, 10:25
It mainly seems like some weird interaction between ffms2 and MeGUI, although I've had similar errors occur when using other indexers (I'm still using ffms2 2.20 because I've had problems with the newer versions, but I don't think anything changed in relation to MeGHUI's cropping and resizing).
It's easy to replicate. I remuxed an Xvid encoded AVI as an MKV and indexed it with L-Smash. Cropping and resizing in the script creator was problem free. After indexing the same MKV with ffms2 and holding down one of the arrows to increase the cropping, it doesn't take long for something like this to happen:
http://s24.postimg.org/9qnudlx2d/error.gif
Save a script for opening the same MKV as before with ffmsindex, then use that script for the source video in the script creator, and cropping and resizing becomes trouble free again.
Zathor knows about the problem, but as far as I know hasn't been able to track down the cause. I just found it odd the problem goes away when you effectively put a script between the source video and the script creator, and I wondered why that might change the behaviour.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.