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. |
12th October 2012, 19:39 | #961 | Link |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
--crf 20 --preset veryslow
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ |
12th October 2012, 23:10 | #963 | Link |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
Nope.
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ |
15th October 2012, 18:44 | #964 | Link |
Registered User
Join Date: Jan 2008
Location: Romania - neighbor of Dracula
Posts: 327
|
how to use 10bit encode? i select high10 profile but stil x264 x86 8 bit is used.
__________________
I7 920 @ 3.60GHz + Thermalright Ultra 120 Extreme Asus P6T Deluxe, 6GB Corsair XMS3 1600MHZ 8-8-8-24 2x1TB Samsung + 1x500GB Samsung, Corsair 520W, Thermaltake Soprano DX GeForge GTX280 |
15th October 2012, 18:49 | #965 | Link |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
8-Bit vs. 10-Bit is a compile-time decision. It's nothing you can change at runtime via option
The "--profile" option of x264 only restricts your other option to (at most) the selected H.264 Profile. It does not enforce the selected Profile, if a lower Profile is sufficient for your file. In other words: Using 10-Bit H.264 implies the "High 10" Profile, but selecting the "High 10" Profile (alone) does NOT trigger or imply 10-Bit encoding! You can enable "10-Bit encoding" in the preferences dialog. This will use the 10-Bit x264 binary for subsequent encodes, instead of the 8-Bit x264 binary that is used by default.
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ Last edited by LoRd_MuldeR; 15th October 2012 at 19:06. |
15th October 2012, 19:13 | #966 | Link | |
Registered User
Join Date: Jan 2008
Location: Romania - neighbor of Dracula
Posts: 327
|
Quote:
__________________
I7 920 @ 3.60GHz + Thermalright Ultra 120 Extreme Asus P6T Deluxe, 6GB Corsair XMS3 1600MHZ 8-8-8-24 2x1TB Samsung + 1x500GB Samsung, Corsair 520W, Thermaltake Soprano DX GeForge GTX280 |
|
15th October 2012, 19:24 | #967 | Link | |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
Quote:
If you ask how to enable 10-Bit encoding in Simple x264 Launcher, just go to "File" -> "Preferences" and enable "Use 10-Bit version of x264". It will show a warning. Read that warning and, if you have understood the consequences, click "Continue".
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ |
|
15th October 2012, 19:39 | #968 | Link |
Registered User
Join Date: Jan 2008
Location: Romania - neighbor of Dracula
Posts: 327
|
Iddiot me, thanks, nice that you had implemented queue
__________________
I7 920 @ 3.60GHz + Thermalright Ultra 120 Extreme Asus P6T Deluxe, 6GB Corsair XMS3 1600MHZ 8-8-8-24 2x1TB Samsung + 1x500GB Samsung, Corsair 520W, Thermaltake Soprano DX GeForge GTX280 |
18th October 2012, 11:32 | #970 | Link |
Telewhining
Join Date: Mar 2010
Posts: 272
|
After upgrading to the newest version I'm getting constant crashes from avs2yuv:
Code:
Problem signature: Problem Event Name: APPCRASH Application Name: avs2yuv_x86.exe Application Version: 0.0.0.0 Application Timestamp: 4e78e870 Fault Module Name: avisynth.DLL Fault Module Version: 2.6.0.3 Fault Module Timestamp: 4f7b27cf Exception Code: c0000005 Exception Offset: 00066e34 OS Version: 6.1.7601.2.1.0.256.4 Locale ID: 1033 Additional Information 1: 9bb2 Additional Information 2: 9bb2af9eb5b5e3c312278cd2f1aa9dbe Additional Information 3: 9af5 Additional Information 4: 9af54169938890e76fe9ec03370a170d Is x264_x64.2012-07-22.exe the previous build? I will try it with that version and make sure it still runs stable. |
18th October 2012, 12:33 | #971 | Link |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
All previous versions can be found here:
http://code.google.com/p/mulder/down...+DownloadCount But Avs2YUV neither is my work nor did I change the included Avs2YUV binaries lately... I've always been using the latest version from here: http://komisar.gin.by/tools/avs2yuv/ What you are experiencing is probably a crash in Avisynth or (more likely) in one of the Avisynth plug-in's involved. Does the very same Avisynth script open in VirtualDub and play through all the way to the end?
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ Last edited by LoRd_MuldeR; 18th October 2012 at 12:36. |
18th October 2012, 21:23 | #972 | Link | |
Telewhining
Join Date: Mar 2010
Posts: 272
|
Quote:
After reverting to x264_x64.2012-07-22.exe I still have the crash, though without the avs2yuv notice. The application just reports that x264 is not responding. Each time it appears to be in a different portion of the video. The only other thing that has changed was a small mvtools2.dll update. That is probably the cause of the crash, though it's strange that it only happens on my newer i7 box. I'm trying the encode again without filters; will report back. |
|
18th October 2012, 21:41 | #973 | Link |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
That's the problem with software testing: The fact that you didn't get a crash, doesn't prove the absence of bugs
Depending on the nature of the bug, it may only be triggered under specific conditions. The conditions may even not be deterministic, which is especially true for "race conditions" errors! And with memory corruption bugs, like "buffer overruns" or "dangling pointers", it's sheer luck whether you get an instant crash or "only" corrupted output (or no effect at all).
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ Last edited by LoRd_MuldeR; 19th October 2012 at 22:21. |
26th October 2012, 17:02 | #975 | Link |
Registered User
Join Date: Jan 2002
Posts: 581
|
in preferences I have checked "Automatically save output to log file when job has finished" - Where can I locate this log file, its not among my movie source files and I have tried look in the temp folder where the .ffindex file are saved. Can you give me a hint on where to find it ?
|
26th October 2012, 17:10 | #976 | Link |
PgcEdit daemon
Join Date: Jul 2003
Posts: 7,469
|
C:\Users\<YOU>\AppData\Local\LoRd_MuldeR\Simple x264 Launcher\logs\
__________________
r0lZ PgcEdit homepage (hosted by VideoHelp) BD3D2MK3D A tool to convert 3D blu-rays to SBS, T&B or FS MKV |
28th October 2012, 11:11 | #977 | Link |
Registered User
Join Date: Dec 2011
Posts: 9
|
Hey!
Thaks for this great x264 encoder software! I love it! I want to ask something. I downloaded the newest version (v2.06), I installed and I checked the version of x264 encoders: toolset\x264_8bit_x64.exe x264 core:128 r2216 198a7ea I downloaded the newest x64 8bit version EXE from there: http://x264.nl/ and I checked this version also: x264 core:128 r2216 198a7ea The versions are same, but I noticed there are difference between the file sizes. \Simple x264 Launcher v2\toolset\x264_8bit_x64.exe 9,034,240 Bytes x264.nl_x64_8bit\x264.exe 10,607,616 Bytes. Can someone explain why is difference these file sizes? I thought, x264 Simple Launcher uses the original x264 files. May I should replace the original files that located in \toolset\ folder with the www.x264.nl files? Thank you! |
28th October 2012, 13:52 | #978 | Link |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
There is no such thing as "original" x264 files. x264 is OpenSource software and released as source code. There are no "official" binaries
Everybody can make his/her own builds. And the resulting file size will depend on many things, like the compiler version that was used, the compiler settings that were used, the libraries included in the build (or not), the versions of the included libraries, the debug symbols being stripped (or not), and so on. The binaries might even have been compressed with an "exe packer" like UPX... I didn't compile x264 myself this time. The binaries I included in the Simple x264 Launcher download are those provided by Komisar (http://komisar.gin.by/) and the differences to JEEB's binaries (http://x264.nl/) should be negligible.
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ Last edited by LoRd_MuldeR; 28th October 2012 at 16:08. |
28th October 2012, 16:35 | #979 | Link | |
Registered User
Join Date: Dec 2011
Posts: 9
|
Ohh, I understand. Thank you very much for quick answer! Please keep up this great software, and continue your work as you always do
Quote:
|
|
19th November 2012, 13:52 | #980 | Link |
Registered User
Join Date: Sep 2011
Posts: 241
|
Can't Drag and Drop AVS file into Simple x264 Launcher
I've installed the latest version of your program (2.06) on a new Windows 7 64-bit installation. I can't drag and avs files into your program. Even if I open the job window and drag it into the source file box, it doesn't work. The only way I can open a file is to manually select the file in the directory.
On my Vista 32-bit PC I had the 22nd July 2012 version and I could drag and drop an AVS file into main window and it would automatically populate the job source file. Last edited by VideoFanatic; 19th November 2012 at 14:01. |
|
|