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.

 

Go Back   Doom9's Forum > Video Encoding > MPEG-4 Encoder GUIs

Reply
 
Thread Tools Search this Thread Display Modes
Old 20th May 2019, 20:52   #1801  |  Link
aldix
Registered User
 
Join Date: Sep 2012
Posts: 150
well, okay, but that doesn't answer the question why basically the exact script and the exact same encoding settings that work with avisynth script + simple x264/265 gui do not work with .vpy script.
aldix is offline   Reply With Quote
Old 20th May 2019, 22:33   #1802  |  Link
LoRd_MuldeR
Software Developer
 
LoRd_MuldeR's Avatar
 
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,050
Quote:
Originally Posted by aldix View Post
well, okay, but that doesn't answer the question why basically the exact script and the exact same encoding settings that work with avisynth script + simple x264/265 gui do not work with .vpy script.
That's probably a completely different issue.

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
__________________
There was of course no way of knowing whether you were being watched at any given moment.
How often, or on what system, the Thought Police plugged in on any individual wire was guesswork.



Last edited by LoRd_MuldeR; 20th May 2019 at 22:49.
LoRd_MuldeR is offline   Reply With Quote
Old 22nd May 2019, 21:00   #1803  |  Link
aldix
Registered User
 
Join Date: Sep 2012
Posts: 150
but the same x264 does not crash with an avisynth script, though. i really don't know how more clearly can i put it lol.
aldix is offline   Reply With Quote
Old 22nd May 2019, 21:30   #1804  |  Link
LoRd_MuldeR
Software Developer
 
LoRd_MuldeR's Avatar
 
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,050
Quote:
Originally Posted by aldix View Post
but the same x264 does not crash with an avisynth script, though. i really don't know how more clearly can i put it lol.
If you refuse to systematically track down your problems, one after the other, or if you don't provide the necessary information, then I can not help.
  • If the x264.exe process crashes on you – which it did according to the log you posted earlier – you obviously have a problem with x264. As long as you do not fix that problem, anything else will be futile! Whether the source was pipe'd in from avs2yuv.exe (Avisynth) or from vspipe.exe (VapourSynth) does not matter. And, as said before, the exit code STATUS_ILLEGAL_INSTRUCTION indicates that x264 has crashed because it tried to execute an instruction not supported by your CPU. This means whatever x264.exe you are using was compiled with "optimizations" not compatible with your CPU. Does x264 still crash, if you use the x264.exe that ships with Simple x264/x265 Launcher?
  • If VapourSynth input is not working – which probably is a completely unrelated problem – then the first thing you need to check is whether VapourSynth is installed properly on your system and whether it has been detected correctly. I already told you how to launch x264_launcher.exe with the debug console enabled. So, go check the debug output and see whether VapourSynth has been detected. Or, at the very least, post your debug output!
__________________
There was of course no way of knowing whether you were being watched at any given moment.
How often, or on what system, the Thought Police plugged in on any individual wire was guesswork.



Last edited by LoRd_MuldeR; 22nd May 2019 at 22:05.
LoRd_MuldeR is offline   Reply With Quote
Old 1st June 2019, 01:12   #1805  |  Link
aldix
Registered User
 
Join Date: Sep 2012
Posts: 150
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!
aldix is offline   Reply With Quote
Old 14th July 2019, 21:33   #1806  |  Link
LoRd_MuldeR
Software Developer
 
LoRd_MuldeR's Avatar
 
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,050
Simple x264/x265 Launcher v2.91
https://github.com/lordmulder/Simple...ases/tag/v2.91

Quote:
Version 2.91 [2019-07-14]
* Updated x265 to version 3.1+2
* Updated build environment to Visual Studio 2019 with Update-1
* Various improvements to Avisynth/VapourSynth detection
__________________
There was of course no way of knowing whether you were being watched at any given moment.
How often, or on what system, the Thought Police plugged in on any individual wire was guesswork.


LoRd_MuldeR is offline   Reply With Quote
Old 17th July 2019, 00:28   #1807  |  Link
RTW47
Rome Total War
 
RTW47's Avatar
 
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…
yet Simple x264 Launcher tried looking for vspipe.exe and vapoursynth.dll inside non-existing core64 folder:
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!
renaming core to core64, would make detection work for 64-bit vapoursynth, however everything else such as vapoursynth editor would fail by default.
---
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…
Simple x264 Launcher now keeps looking elsewhere, but paths are still not correct to detect 32-bit VS and (or) 64-bit VS:
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!
that new installer likely changed some folder names etc., since I clearly remember seeing core32 / core64 folders (at least for non-portable vapoursynth).
__________________
GOTO:EOF

Last edited by RTW47; 17th July 2019 at 01:27.
RTW47 is offline   Reply With Quote
Old 17th July 2019, 23:37   #1808  |  Link
LoRd_MuldeR
Software Developer
 
LoRd_MuldeR's Avatar
 
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,050
Quote:
Originally Posted by RTW47 View Post
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).
It appears there were some significant changes in latest VapourSynth release, which broke "our" detection routines

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...
__________________
There was of course no way of knowing whether you were being watched at any given moment.
How often, or on what system, the Thought Police plugged in on any individual wire was guesswork.


LoRd_MuldeR is offline   Reply With Quote
Old 18th July 2019, 00:24   #1809  |  Link
RTW47
Rome Total War
 
RTW47's Avatar
 
Join Date: Mar 2013
Location: C:\Python33
Posts: 39
Quote:
Originally Posted by LoRd_MuldeR View Post
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...
I'm not in a hurry, take your time and have a safe journey.
__________________
GOTO:EOF

Last edited by RTW47; 18th July 2019 at 00:38.
RTW47 is offline   Reply With Quote
Old 22nd July 2019, 18:41   #1810  |  Link
LoRd_MuldeR
Software Developer
 
LoRd_MuldeR's Avatar
 
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,050
Simple x264/x265 Launcher v2.92
https://github.com/lordmulder/Simple...ases/tag/v2.92

Quote:
Version 2.92 [2019-07-22]
* Updated x264 to revision 2984 (API v158)
* Updated x265 to version 3.1+8
* Fixed detection of VapourSynth R46
* Note: Minimum supported VapourSynth version is R46 now!
Quote:
Hotfix for Simple x264/x265 Launcher v2.92 to remedy an erroneous "critical error" message:
https://sourceforge.net/projects/mul...1.zip/download
__________________
There was of course no way of knowing whether you were being watched at any given moment.
How often, or on what system, the Thought Police plugged in on any individual wire was guesswork.



Last edited by LoRd_MuldeR; 22nd July 2019 at 22:26.
LoRd_MuldeR is offline   Reply With Quote
Old 22nd July 2019, 21:04   #1811  |  Link
Dion
Registered User
 
Join Date: Oct 2004
Posts: 63
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?
Dion is offline   Reply With Quote
Old 22nd July 2019, 22:03   #1812  |  Link
LoRd_MuldeR
Software Developer
 
LoRd_MuldeR's Avatar
 
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,050
Quote:
Originally Posted by Dion View Post
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?


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
__________________
There was of course no way of knowing whether you were being watched at any given moment.
How often, or on what system, the Thought Police plugged in on any individual wire was guesswork.



Last edited by LoRd_MuldeR; 22nd July 2019 at 22:11.
LoRd_MuldeR is offline   Reply With Quote
Old 23rd July 2019, 00:20   #1813  |  Link
RTW47
Rome Total War
 
RTW47's Avatar
 
Join Date: Mar 2013
Location: C:\Python33
Posts: 39
Quote:
Originally Posted by LoRd_MuldeR View Post
can confirm that new build now successfully detects both (32-bit & 64-bit) non-portable VapourSynth R46. (#1807)
thanks LM^^
__________________
GOTO:EOF
RTW47 is offline   Reply With Quote
Old 26th July 2019, 20:28   #1814  |  Link
Chouonsoku
Registered User
 
Join Date: Sep 2007
Posts: 39
Edit: Nevermind, user error.

Last edited by Chouonsoku; 26th July 2019 at 20:32.
Chouonsoku is offline   Reply With Quote
Old 6th August 2019, 22:56   #1815  |  Link
LoRd_MuldeR
Software Developer
 
LoRd_MuldeR's Avatar
 
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,050
Simple x264/x265 Launcher v2.93
https://github.com/lordmulder/Simple...ases/tag/v2.93

Quote:
Version 2.93 [2019-08-06]
* Fixed a regression in VapourSynth detection code
* Updated NVEncC to version 4.43
* Updated build environment to Visual Studio 2019 with Update-2
__________________
There was of course no way of knowing whether you were being watched at any given moment.
How often, or on what system, the Thought Police plugged in on any individual wire was guesswork.


LoRd_MuldeR is offline   Reply With Quote
Old 11th September 2019, 13:02   #1816  |  Link
redbtn
Registered User
 
redbtn's Avatar
 
Join Date: Jan 2019
Location: Russia
Posts: 126
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
redbtn is offline   Reply With Quote
Old 11th September 2019, 22:44   #1817  |  Link
LoRd_MuldeR
Software Developer
 
LoRd_MuldeR's Avatar
 
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,050
Quote:
Originally Posted by redbtn View Post
Something strange in log file. Launcher v2.93, x265 v3.1+14
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?
__________________
There was of course no way of knowing whether you were being watched at any given moment.
How often, or on what system, the Thought Police plugged in on any individual wire was guesswork.



Last edited by LoRd_MuldeR; 11th September 2019 at 22:52.
LoRd_MuldeR is offline   Reply With Quote
Old 14th September 2019, 14:59   #1818  |  Link
redbtn
Registered User
 
redbtn's Avatar
 
Join Date: Jan 2019
Location: Russia
Posts: 126
Quote:
Originally Posted by LoRd_MuldeR View Post
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?
Yes, the "issue" is reproducible. I used builds from msystem.waw.pl/x265

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 15:03.
redbtn is offline   Reply With Quote
Old 6th October 2019, 13:22   #1819  |  Link
LoRd_MuldeR
Software Developer
 
LoRd_MuldeR's Avatar
 
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,050
Simple x264/x265 Launcher v2.94
https://github.com/lordmulder/Simple...ases/tag/v2.94

Quote:
Version 2.94 [2019-10-05]
* Updated x265 to version 3.2+5, incl. AQ mode 4 slowdown fix
* Updated NVEncC to version 4.50 (v2)
* Updated build environment to Visual Studio 2019 with Update-3
__________________
There was of course no way of knowing whether you were being watched at any given moment.
How often, or on what system, the Thought Police plugged in on any individual wire was guesswork.


LoRd_MuldeR is offline   Reply With Quote
Old 27th October 2019, 11:35   #1820  |  Link
Metal-HTPC
Registered User
 
Join Date: Dec 2018
Posts: 38
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.
Metal-HTPC is offline   Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +1. The time now is 04:58.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2019, vBulletin Solutions Inc.