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. |
20th May 2019, 21:33 | #1801 | Link | |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
Quote:
First of all, try to resolve your obvious x264 crash problem. VapourSynth input can not work, as long as x264 is crashing on you! It would be best to just stick with the vanilla x264.exe that ships with Simple x264/x265 Launcher. Secondly, encoding from ".vpy" script requires that an up-to-date version VapourSynth is installed on your machine – x264.exe can not read ".vpy" scripts directly, the frames need to be pipe'd via vspipe.exe. Simple x264/x265 Launcher does that automatically for you. But, if you think that Simple x264/x265 Launcher did not detect VapourSynth even though it is installed, then run x264_launcher.exe with parameter "--console" and… It is supposed to look like this: https://i.imgur.com/dfyuEwa.png
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ Last edited by LoRd_MuldeR; 20th May 2019 at 21:49. |
|
22nd May 2019, 20:30 | #1803 | Link | |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
Quote:
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ Last edited by LoRd_MuldeR; 22nd May 2019 at 21:05. |
|
1st June 2019, 00:12 | #1804 | Link |
Registered User
Join Date: Sep 2012
Posts: 156
|
indeed, my sincere apologies.
was indeed for some brain-fart reason trying to get the boardwell version of the tmod to work until this very moment. the regular, latest build works issue-free just as the vanilla x264 does. thank you for your software! |
14th July 2019, 20:33 | #1805 | Link | |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
Simple x264/x265 Launcher v2.91
https://github.com/lordmulder/Simple...ases/tag/v2.91 Quote:
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ |
|
16th July 2019, 23:28 | #1806 | Link |
Rome Total War
Join Date: Mar 2013
Location: C:\Python33
Posts: 39
|
for me Simple x264 Launcher v2.91.1170 (64-bit) is unable to detect 32-bit and 64-bit VapourSynth. (Windows 7 SP1)
At this point only VapourSynth (64-Bit) R46 (non-portable) was installed using this new separate installer for 64-bit. (since R46). 64-bit vapoursynth installation: Code:
C:\Program Files\VapourSynth\ ├─ core ├─ docs ├─ pismo └─ etc… Code:
[Check for VapourSynth support] VapourSynth thread has been created, please wait... VapourSynth Dir: C:/Program Files/VapourSynth VapourSynth EXE: C:/Program Files/VapourSynth/core32/vspipe.exe VapourSynth DLL: C:/Program Files/VapourSynth/core32/vapoursynth.dll VapourSynth 32-Bit edition *not* found! VapourSynth EXE: C:/Program Files/VapourSynth/core64/vspipe.exe VapourSynth DLL: C:/Program Files/VapourSynth/core64/vapoursynth.dll VapourSynth 64-Bit edition *not* found! VapourSynth thread finished. VapourSynth could not be found -> VapourSynth support disabled! --- After instaling Python 3.7.4 (32-bit) and VapourSynth (32-bit) R46, now both 32-bit and 64-bit (non-portable) versions of vapoursynth are installed: 32-bit vapoursynth installation: Code:
C:\Program Files (x86)\VapourSynth-32\ ├─ core ├─ docs ├─ pismo └─ etc… Code:
[Check for VapourSynth support] VapourSynth thread has been created, please wait... VapourSynth Dir: C:/Program Files (x86)/VapourSynth-32 VapourSynth EXE: C:/Program Files (x86)/VapourSynth-32/core32/vspipe.exe VapourSynth DLL: C:/Program Files (x86)/VapourSynth-32/core32/vapoursynth.dll VapourSynth 32-Bit edition *not* found! VapourSynth EXE: C:/Program Files (x86)/VapourSynth-32/core64/vspipe.exe VapourSynth DLL: C:/Program Files (x86)/VapourSynth-32/core64/vapoursynth.dll VapourSynth 64-Bit edition *not* found! VapourSynth thread finished. VapourSynth could not be found -> VapourSynth support disabled!
__________________
GOTO:EOF Last edited by RTW47; 17th July 2019 at 00:27. |
17th July 2019, 22:37 | #1807 | Link | |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
Quote:
I will have to look into that, as soon as I have some spare time. This is probably not going to happen before next week, because I am very busy right now and I will be on a trip this weekend...
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ |
|
22nd July 2019, 17:41 | #1809 | Link | ||
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
Simple x264/x265 Launcher v2.92
https://github.com/lordmulder/Simple...ases/tag/v2.92 Quote:
Quote:
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ Last edited by LoRd_MuldeR; 22nd July 2019 at 21:26. |
||
22nd July 2019, 20:04 | #1810 | Link |
Registered User
Join Date: Oct 2004
Posts: 64
|
Getting this error with this new version.
https://images2.imgbox.com/da/f1/DxDYncGx_o.png I don't have Vapoursynth installed or use it. Is there no way to suppress this fully? |
22nd July 2019, 21:03 | #1811 | Link | |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
Quote:
Sorry, there is a stupid regression in the latest release, when VapourSynth is not found at all. You can safely ignore the "critical error" message. Anyway, please try with the "hotfix" version from here: x264_launcher.2019-07-22.hotfix-1.zip
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ Last edited by LoRd_MuldeR; 22nd July 2019 at 21:11. |
|
22nd July 2019, 23:20 | #1812 | Link | |
Rome Total War
Join Date: Mar 2013
Location: C:\Python33
Posts: 39
|
Quote:
thanks LM^^
__________________
GOTO:EOF |
|
6th August 2019, 21:56 | #1814 | Link | |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
Simple x264/x265 Launcher v2.93
https://github.com/lordmulder/Simple...ases/tag/v2.93 Quote:
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ |
|
11th September 2019, 12:02 | #1815 | Link |
Registered User
Join Date: Jan 2019
Location: Russia
Posts: 105
|
Something strange in log file. Launcher v2.93, x265 v3.1+14
Code:
[2019-09-11][07:24:09] x265 [info]: Rate Control / qCompress : CRF-15.0 / 0.65 [2019-09-11][07:24:09] x265 [info]: VBV/HRD buffer / max-rate / init : 160000 / 160000 / 0.900 [2019-09-11][07:24:09] x265 [info]: tools: rect amp limit-modes rd=4 psy-rd=2.00 rdoq=2 psy-rdoq=2.00 [2019-09-11][07:24:09] x265 [info]: tools: rskip limit-tu=4 signhide tmvp b-intra deblock(tC=-3:B=-3) [2019-09-11][07:46:49] 92 fps, 10111.82 kb/s, eta 17:40:01 [2019-09-11][07:53:16] , 2.84 fps, 11286.77 kb/s, eta 18:03:51 [2019-09-11][09:29:39] [9.7%] 18339/189480 fram [2019-09-11][09:29:39] es, 2.43 fps, 19276.08 kb/s, eta 19:31:29 [2019-09-11][09:39:19] [10.3%] 19556/189480 fr [2019-09-11][09:39:19] ames, 2.41 fps, 19775.16 kb/s, eta 19:34:43 [2019-09-11][09:47:19] [10.9%] [2019-09-11][09:47:19] 20745/189480 frames, 2.41 fps, 19664.61 kb/s, eta 19:24:41 [2019-09-11][10:17:49] 19267.50 kb/s, eta 18:56:01 [2019-09-11][11:19:28] ps, 18573.33 kb/s, eta 17:40:10 [2019-09-11][13:38:17] [29.0%] [2019-09-11][13:38:17] 54899/189480 frames, 2.45 fps, 18180.11 kb/s, eta 15:17:14 [2019-09-11][13:41:21] 73.79 kb/s, eta 15:14:14 [2019-09-11][14:13:59] 6.31 kb/s, eta 14:50:27 [2019-09-11][14:14:44] 2 kb/s, eta 14:49:52 [2019-09-11][14:19:23] 18461.43 kb/s, eta 14:47:00 [2019-09-11][14:46:51] 3:37 [2019-09-11][15:12:06] [36 [2019-09-11][15:12:06] .1%] 68451/189480 frames, 2.44 fps, 18191.34 kb/s, eta 13:47:26 [2019-09-11][15:43:05] 2.54 kb/s, eta 13:13:47 |
11th September 2019, 21:44 | #1816 | Link |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
So, I suppose you manually updated the x265 binary to v3.1+14. Does it only happen with x265 v3.1+14, but not with the x265 binary that originally shipped with Simple x264 Launcher? Is the "issue" reproducible?
Also: Which specific x265 build are you using? Are there any "custom" patches included in that build? If you run that binary in the terminal (no GUI), does the output look normal?
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ Last edited by LoRd_MuldeR; 11th September 2019 at 21:52. |
14th September 2019, 13:59 | #1817 | Link | |
Registered User
Join Date: Jan 2019
Location: Russia
Posts: 105
|
Quote:
I've made few tests: 1) x265 that shipped with Simple x264 Launcher - OK 2) x265 (3.1+14 and 3.1+19) AVX2 VS2019 from msystem.waw.pl/x265 - Have this bug 3) x265 (3.1+19) AVX2 GCC9.2 from from msystem.waw.pl/x265 - OK 4) x265 (3.1+19) build by Barough - OK So, it seems like a VS2019 compile bug. So, LoRd_MuldeR , i'm sorry for disturbing. Last edited by redbtn; 14th September 2019 at 14:03. |
|
6th October 2019, 12:22 | #1818 | Link | |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
Simple x264/x265 Launcher v2.94
https://github.com/lordmulder/Simple...ases/tag/v2.94 Quote:
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ |
|
27th October 2019, 11:35 | #1819 | Link |
Registered User
Join Date: Dec 2018
Posts: 58
|
sadly the simple x264 launcher doesn't work anymore after the latest update.
I'm still using the 2.60 (https://www.videohelp.com/software/Avisynth) version of Avisynth and really didn't chance anything in my configuration. The problem is the following. I can't re-encode any of my commercial released blu-rays anymore. It only outputs about 21-25 mb and the encodes all come out as this mess: https://ufile.io/0mptrzot screenshot of x264 during the encode: any help would be appreciated. |
27th October 2019, 12:10 | #1820 | Link | |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
Quote:
The included x264 binaries were not even changed in the last two releases of my Simple x264 Launcher package. The last time that the x264 binaries were updated was in version 2.92 [2019-07-22]. So, IMO, there is nothing in the last (or second last) release of Simple x264 Launcher that could possibly have changed encoding with x264 and Avisynth input! You didn't replace the x264 binaries manually, right? I can only speculate about the cause of your problem. Might be that the Avisynth process crashed; might be that the x264 process crashed. Hard to tell, since your screenshot excludes the most important part of the log – the very end. It would be helpful if you posted a complete log of your encoding task that shows everything from start to finish... Anyway, if you open the very same Avisynth script that you are trying to encode in Simple x264 Launcher in, e.g., VirtualDub, does it open and "play" (seek) properly all the way to the end without problem?
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ Last edited by LoRd_MuldeR; 27th October 2019 at 12:47. |
|
|
|