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. |
17th December 2016, 21:45 | #5202 | Link |
Registered User
Join Date: Feb 2011
Posts: 331
|
When I add files using one click-encoder, a lot of jobs fail with a message like this:
Code:
D:\Dreambox\movie\projectx\656\xxxx\xxxx.mkv.lwi not moved to D:\Dreambox\movie\projectx\656\xxxx\3ffvhydb.fze\xxxx.mkv.lwi. error: The process cannot access the file 'D:\Dreambox\movie\projectx\656\xxxx\xxxx.mkv.lwi' because it is being used by another process. --[Information] [16.12.2016. 20.01.02] Job completed |
18th December 2016, 21:45 | #5204 | Link | |
Registered User
Join Date: Nov 2009
Posts: 2,405
|
Quote:
Start MeGUI, reproduce the problem, close MeGUI and send me the full log again please. |
|
20th December 2016, 22:35 | #5208 | Link |
Registered User
Join Date: Nov 2009
Posts: 2,405
|
Code:
2695 improved redistributable handling 2694 [VobSubber] fixed error if output path contains blanks removed 1GB warning added CC files to the to be deleted intermediate files 2693 [AudioEncoder] default to LWLibavAudioSource()/LSMASHAudioSource() added downmix option to 5.1 added proper LoadPlugin calls for TimeStrech()/TimeStretchPlugin() and SoxFilter() x64: remove filter/functions where the not available plugins AudioLimiter.dll or SoxFilter.dll are required 2692 [qaac] removed --no-delay option if LC is not used (regression of 2377). Bug #865 2691 [x265] fixed wrong command line (regression of 2685). Bug #863 changed default --crf vaue to 28 |
21st December 2016, 03:41 | #5209 | Link | |
Registered User
Join Date: Feb 2014
Posts: 355
|
How To Use kMod Version Of 10bit x264
Quote:
Zathor: As always, thank you for maintaining MeGUI . I've been using the standalone 32bit MeGUI (updating from the development server) with the 64bit x264 hack for years. Unfortunately, since your recent updates I'm no longer able to replace "x264-10b_64.exe" with Komisar's modded version (kMod) by renaming it and replacing the unmodded version in "MeGUI/Tools/x264_10b". As a test, I've also tried replacing "x264-10b.exe" with the kMod version, but any encoded video still uses the unmodded version (according to MediaInfo). Please, what's the current location of the "x264-10b_64.exe" or "x264-10b.exe" that the latest updated version of 32bit MeGUI uses? Thanks. |
|
21st December 2016, 12:10 | #5211 | Link |
Registered User
Join Date: Oct 2007
Posts: 385
|
[QUOTE=Zathor;1790527]
Code:
2694 [VobSubber] fixed error if output path contains blanks removed 1GB warning added CC files to the to be deleted intermediate files If it's possible to disable the forced subs routine for Single File Output, that would be greatly appreciated. |
21st December 2016, 12:28 | #5212 | Link | |
Moderator
Join Date: Feb 2005
Location: Spain
Posts: 6,890
|
Quote:
__________________
BeHappy, AviSynth audio transcoder. |
|
21st December 2016, 15:26 | #5213 | Link | |
Registered User
Join Date: Nov 2009
Posts: 2,405
|
Quote:
You are more than welcome! To be honest most of the points are based upon your thoughts/recommendations |
|
21st December 2016, 16:44 | #5214 | Link | |
Registered User
Join Date: Feb 2014
Posts: 355
|
Quote:
Thanks a bunch for that, hello_hello, I appreciate it . I'm certain I would've discovered this eventually, as my next course of action was to search the entire MeGUI folder for the x264 .exe . I think I remember reading recently in this thread (or the MeGUI General Questions and Troubleshooting Thread, I can't remember), that MeGUI has changed it's use of "avs4x26x.exe" such that it no longer requires the "avs4x26xmod.exe". Am I remembering correctly? Also, would this be the reason that the 64bit version of "x264-10b.exe" ("x264-10b_64.exe") is seemingly no longer needed? Thanks in advance for any clarity. |
|
21st December 2016, 19:23 | #5215 | Link | |
Registered User
Join Date: Nov 2009
Posts: 2,405
|
Quote:
- the 8-bit and 10-bit packages have been merged - the 32bit and 64bit exe files however have been separated - the 32bit package is downloaded and used on a 32bit OS (without avs4x26x), the 64bit package is used on 64bit OS (with avs4x26x when using the 32bit version of MeGUI, without when using the 65bit version) ==> you only have to replace the files in one directory - the x264 one |
|
25th December 2016, 04:28 | #5217 | Link | |
Registered User
Join Date: Feb 2014
Posts: 355
|
Quote:
|
|
26th December 2016, 16:48 | #5219 | Link |
Registered User
Join Date: Dec 2011
Posts: 148
|
What is the advantage of the 64bit version version oppositte the 32bit? I've encode the same movie with both versions and the picture quality is the same. I do not see any difference. Used the same settings for x264 MKV.
|
26th December 2016, 17:31 | #5220 | Link |
German doom9/Gleitz SuMo
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 6,753
|
You should certainly not expect any difference in quality.
The 64-bit CPU architecture is a bit more efficient (twice as wide and twice as many direct-access CPU registers), some encoders may work up to ~10% faster. But AviSynth used to be only available reliably in 32-bit code, and most plugins for AviSynth also existed in 32-bit code only. And you cannot call a 32-bit code DLL (like vanilla AviSynth 2.5 / 2.6) in a 64-bit code EXE. For x264 and x265, a helper application (avs4x26x) was called to pipe a stream of raw video from the AviSynth output into the encoder. If all used tools would be available in 64-bit code, making them work together would be easier and more efficient - thus faster. Now with the development of AviSynth+, chances are good that this will happen for MeGUI, as it already happened for StaxRip. |
Thread Tools | Search this Thread |
Display Modes | |
|
|