Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
28th October 2015, 20:29 | #7962 | Link |
German doom9/Gleitz SuMo
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 6,752
|
You don't need to install QuickTime or even iTunes into your system if you use the makeportable.bat from the qaac "cabinet" to extract the required DLLs from their installer (preferably iTunes6464setup.exe).
|
1st November 2015, 23:16 | #7963 | Link |
Registered User
Join Date: Oct 2010
Posts: 9
|
Hi! ...to everyone here (reading, questioning or answering)
At first I want to be forgiven for my terrible English... (its not my mother language) Also I want to be forgiven because I'm gonna raise a question that has already been answered (but not for me) and has to do with pale colors and (or) washed-out blacks or colors. Before anyone starts to say or write down "oh! what does he say? ..it's already perfectly answered on another thread" or feels the need to say or write down (but can't) "f..ck you! not again.." My question is.. how could 2 perfectly identical encodes (with exactly same settings) but different encoding tools (MeGUI & TX264) (program --level 4.1 --preset veryslow --pass 2 --bitrate 1000* (8GB file size) --stats ".stats" --deblock -3:-3 --keyint 240 --bframes 6 --ref 4 --vbv-bufsize 32500 --vbv-maxrate 40000 --aq-strength 0.8 --merange 64 --me esa --psy-rd 1.0:0.20 --no-fast-pskip --colorprim bt709 --transfer bt709 --colormatrix bt709 --output "output" "input") and played back with same media player (MPC-Home Cinema) with same render-er, gives 2 different results when viewing. TX264's encode is at first completely identical to the source in the color encode part (something that's not happened for MeGUI) & even more weird is that TX264 re-produces perfectly the grainy parts for the same film, but MeGUI not. For me it makes no sense to have different results (despite the same settings) in 2 critical parts for a final quality result.. and I'm not a noob with encoding's and settings. Someone could say "why don't you stick with TX264 if it suite's you better? The reason is that I prefer MeGUI as it is by far a more complete tool and another reason is that with TX264.. you give-it a file size of exactly 8GB and it produces a file size of 8.11GB or 8.48GB or 8.26GB or something near.. but never the exact 8GB file that I need. Why do I need a exact 8GB file size and not something so close or near to that? I could say that I have a obsession with the perfect. (I hope you don't think that I'm crazy!) ..A big pre-thanks for any answer or suggestion and or any help. (Except the advice that the best solution for me is to visit a doctor). Last edited by Bryce2; 1st November 2015 at 23:22. |
1st November 2015, 23:58 | #7964 | Link |
Registered User
Join Date: Nov 2013
Posts: 136
|
Hi
why recently MeGUI backs up everything in the same folder as the packege that's being updated ? sometimes it causes problems. like when I updated "eac3to" MeGUI backed up everything in the folder including NeroAAC encoder and after updating, MeGUI forced a NeroAACEnc reinstallation :| |
2nd November 2015, 20:15 | #7966 | Link | |
Registered User
Join Date: Nov 2009
Posts: 2,405
|
Quote:
Are you sure that both encodes are the same? You have not mentioned the avisynth script. Both script file used in both encodes? Also both times the same x264 executable and avisynth version? |
|
2nd November 2015, 20:59 | #7967 | Link | |
Registered User
Join Date: Oct 2010
Posts: 9
|
Quote:
1. If you mean the job log file.. I will attach a MeGUI .log file of a random encode (the problem with the pale colors & washed-out blacks is with each & every encode.. and not just for a specific one). 2. Avisynth* "TX264" does not use "Avisynth" (is not in tools folder of the app - perhaps it uses the main systems Avisynth installation without a mention? - not possible). Anyway... the MeGUI avs. script does not include any extra filters or anything else - just a simple video load & undot filter). 3. As for now both tools don't use the same x264 executable because TX264 has not an update since "October 08, 2014".. but a long time ago (a year or so) they used the same. Then also MeGUI's problem with pale colors was the same. As I mentioned before, for the x264 part, the settings for the 2 programs are the same (for now and then) with the only difference that I have raised for both, the "M.E Algorithm" since a year ago. (I have an 8core AMD now & then I had a 4core AMD Black Edition) a) I have attached a profile and a .log file for TX264 from my last encode. b) A .log file from my last encode and a standard avisynth script for MeGUI that I always use. Last edited by Bryce2; 3rd November 2015 at 19:28. Reason: uncomplete post |
|
8th November 2015, 18:04 | #7969 | Link | |
Registered User
Join Date: Oct 2010
Posts: 9
|
Quote:
I'll try FFMS2 & or L-SMASH as you suggest.. but what do you mean with "how did I manage to get so much out of date stuff with a developer version". Does your question have to do with me using DirectShowSource instead of using "File Indexer"? If not.. can you light me up? |
|
27th November 2015, 09:57 | #7970 | Link |
Registered User
Join Date: Jun 2005
Posts: 236
|
I just switched to the developer update server, and something has changed how AVIs are muxed. Before I updated, doing mp4 or mkv h264 to xvid, using 2 pass xvid, would have 4 jobs: lame, xvid, xvid, avimuxgui.
Now, without changing any settings, it wants to do MKV to AVI in 5 jobs: lame, xvid, xvid, ffmpeg mux M4V to AVI, avimuxgui AVI to AVI. I don't get why M4V is involved. |
29th November 2015, 12:04 | #7972 | Link |
Moderator
Join Date: Feb 2005
Location: Spain
Posts: 6,890
|
I see the differences between this new XVID version and the previous one:
New: Code:
xvid_encraw built at 16:08:51 on Jun 21 2015 ... -o string : save an Elementary Stream for the complete sequence -avi string : save an AVI file for the complete sequence Code:
xvid_encraw built at 10:22:53 on Aug 31 2007 ... -o string : save an Elementary Stream, or AVI file, or MKV file, based on filename extension -avi string : save an AVI file for the complete sequence -mkv string : save a MKV file for the complete sequence In my test, using -avi, the xvid_encraw output load in AVIMuxGUI or VirtualDub without problems. And the ffmpeg pass seems not necesary.
__________________
BeHappy, AviSynth audio transcoder. |
29th November 2015, 12:10 | #7973 | Link |
German doom9/Gleitz SuMo
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 6,752
|
Yes, there are issues with large output, it didn't work well in AVI container, multiplexing a raw M4V was more reliable. AviMux-GUI was unusable either due to a lack of M4V support. Documented months ago, I bet...
Unfortunately, the MKV output patch belongs to a much older version of xvid_encraw, you can't apply it to current sources without adapting a lot of places. I am not good enough with C/C++, my attempts failed... Last edited by LigH; 29th November 2015 at 12:12. |
3rd December 2015, 12:26 | #7977 | Link |
Registered User
Join Date: Apr 2009
Posts: 76
|
Is it me or Drag & Drop into MeGUI does not work in Windows 10? I remember there was such issue in Windows 7 long ago but I believe it was fixed and I never had any problem with Drag & Dropping in Windows 7.
OS: Windows 7 Pro x64 MeGUI x86 |
4th December 2015, 06:15 | #7978 | Link |
Registered User
Join Date: Sep 2011
Posts: 241
|
MeGUI apparently uses the C Drive Avisynth and plugins installation directory instead of a directory within the MeGUI folder. Is that correct? I asked the MeGUI staff and they said that was the case so I'm wondering what the "Avisynth_plugin" and "avs" folders are for within the MeGUI tools folder? I deleted those folders and MeGUI still encoded my Avisynth scripts fine. On occasion however when I try to start an encoding it will show a popup window saying something like the avisynth plugins needs to be installed but they're already installed in C:\Program Files (x86)\AviSynth\plugins. Can someone explain this please?
Anyway I downloaded the updates within MeGUI and it was working again. |
4th December 2015, 08:23 | #7979 | Link | ||
Registered User
Join Date: Nov 2009
Posts: 2,405
|
Quote:
Quote:
|
||
4th December 2015, 10:58 | #7980 | Link | |
Registered User
Join Date: Mar 2011
Posts: 4,823
|
Quote:
MeGUI has it's own Avisynth plugin folders but the plugins don't auto-load. That's where MeGUI expects them to be when it needs to load one "manually" while creating a script. You shouldn't delete them or the plugins within. If you use some of those plugins regularly it can't hurt to copy them to the "installed" Avisynth plugins folder so they'll auto-load if you create a script yourself. Just make sure you don't end up with a different version of the same plugin in both folders. Last edited by hello_hello; 4th December 2015 at 11:02. |
|
Tags |
megui |
Thread Tools | Search this Thread |
Display Modes | |
|
|