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, 19: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, 21:33   #1802  |  Link
LoRd_MuldeR
Software Developer
 
LoRd_MuldeR's Avatar
 
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,017
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 21:49.
LoRd_MuldeR is offline   Reply With Quote
Old 22nd May 2019, 20: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, 20:30   #1804  |  Link
LoRd_MuldeR
Software Developer
 
LoRd_MuldeR's Avatar
 
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,017
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 21:05.
LoRd_MuldeR is offline   Reply With Quote
Old 1st June 2019, 00: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, 20:33   #1806  |  Link
LoRd_MuldeR
Software Developer
 
LoRd_MuldeR's Avatar
 
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,017
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
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 02:04.


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