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. |
22nd April 2019, 15:56 | #1781 | Link |
Registered User
Join Date: Dec 2006
Location: Germany
Posts: 91
|
It would be very nice, if you wouldn't force everyone using your launcher to check for updates after six months even the checkbox "never show auto-update notifications on application startup" is enabled. Maybe there's another checkbox necessary for that six-month-message - but I definitively do not want to be forced to check for updates or to wait for a felt eternity before I am allowed to click the discard button.
|
27th April 2019, 11:23 | #1782 | Link | |
Registered User
Join Date: Dec 2010
Posts: 29
|
Quote:
|
|
2nd May 2019, 16:30 | #1784 | Link |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
This is just a GUI front-end. It "accepts" whatever Avisynth or VapourSynth script as input that you load
The actual question, IMO, is whether Avisynth or VapourSynth and the particular filters (especially the source filter) that you are using properly support “UHD” material, i.e. 4K resolution + High Dynamic Range (HDR). I think "classic" Avisynth is out of scope here, as it was 8-Bit only and development is pretty much dead, AFAIK. But VapourSynth should work fine, as it has supported "high bit-depth" color formats ever since. Maybe Avisynth+ can be made to work too, as it is supposed to add more color formats (including 10, 12, 14 and 16 bits) to Avisynth. The next big question is, how the encoders, i.e. x264 or x265, deal with “UHD” input. My experience on that field is limited, but you will probably have to use some sort of "tone mapping", if you want to encode as SHD.
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ Last edited by LoRd_MuldeR; 2nd May 2019 at 16:40. |
2nd May 2019, 16:42 | #1785 | Link | |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
Simple x264/x265 Launcher v2.90
https://github.com/lordmulder/Simple...ases/tag/v2.90 Quote:
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ Last edited by LoRd_MuldeR; 2nd May 2019 at 17:04. |
|
2nd May 2019, 17:27 | #1786 | Link | |
Registered User
Join Date: Sep 2018
Posts: 391
|
Quote:
Is it considered better? Sent from my SM-G965U1 using Tapatalk |
|
2nd May 2019, 18:10 | #1787 | Link | ||
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
Quote:
But, according to its author, VapourSynth... Quote:
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ |
||
3rd May 2019, 03:36 | #1788 | Link | |
Registered User
Join Date: Sep 2018
Posts: 391
|
Quote:
Sent from my SM-G965U1 using Tapatalk |
|
3rd May 2019, 22:50 | #1789 | Link |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
Well, it depends
Simple x264/x265 Launcher, for example, supports VapourSynth scripts as input – provided that VapourSynth is installed. It does not provide any kind of VapourSynth editor though; that is out of scope for this program. So, if you are looking for a fully-fledged GUI editor for VapourSynth scripts, you should probably have a look at the VapourSynth Editor.
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ Last edited by LoRd_MuldeR; 4th May 2019 at 20:34. |
6th May 2019, 19:47 | #1790 | Link |
Registered User
Join Date: Sep 2007
Posts: 52
|
I'm having any issue with the latest release where sometimes on running the program and queueing an encode, I get a complaint that VapourSynth is not installed. Closing and reopening the program and queueing the encode again seems to solve the problem. I'm running VS and the launcher in portable mode.
|
6th May 2019, 19:51 | #1791 | 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 🇺🇦✊ |
|
6th May 2019, 23:59 | #1792 | Link | ||
Registered User
Join Date: Sep 2007
Posts: 52
|
Quote:
Quote:
|
||
7th May 2019, 21:10 | #1793 | Link | |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
Quote:
Code:
VapourSynth EXE: E:/Tools/Simple x264 Launcher v2/extra/VapourSynth/core64/vspipe.exe VapourSynth DLL: E:/Tools/Simple x264 Launcher v2/extra/VapourSynth/core64/vapoursynth.dll VSPIPE.EXE process encountered a deadlock -> aborting now! VSPIPE.EXE process still running, going to kill it! VSPIPE.EXE failed with code 0x0000F291 -> disable Vapousynth support! VapourSynth 64-Bit edition was found, but version check has failed! If a program takes unusually long to start for no comprehensible reason, then – more often than not – so-called "anti-virus" software was interfering. Anyhow, coincidentally I did some clean-up and refactoring of the startup code today and also slightly increased the time limit. You can try with the latest TEST build and see if that makes any difference for you...
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ Last edited by LoRd_MuldeR; 7th May 2019 at 21:21. |
|
8th May 2019, 10:18 | #1794 | Link |
RipBot264 author
Join Date: May 2006
Location: Poland
Posts: 7,815
|
Maybe other app is blocking vspipe.exe? I have seen similar problem in my thread
https://forum.doom9.org/showthread.p...06#post1862506 https://forum.doom9.org/showthread.p...84#post1872384
__________________
Windows 7 Image Updater - SkyLake\KabyLake\CoffeLake\Ryzen Threadripper Last edited by Atak_Snajpera; 8th May 2019 at 10:22. |
8th May 2019, 20:29 | #1795 | Link | |
Registered User
Join Date: Sep 2007
Posts: 52
|
Quote:
Edit: Excluding it worked, Simple launched on the first try and VSEdit is opening faster. Last edited by Chouonsoku; 8th May 2019 at 20:33. |
|
18th May 2019, 21:00 | #1797 | Link |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ |
19th May 2019, 00:18 | #1798 | Link |
Registered User
Join Date: Sep 2012
Posts: 156
|
well, it's like i said. which is why i'm confused...
Code:
[2019-05-19][02:16:40] avs [error]: failed to load avisynth [2019-05-19][02:16:40] x264 [error]: could not open input file `C:\Temp\8E5_python.vpy' [2019-05-19][02:16:40] [2019-05-19][02:16:40] PROCESS EXITED WITH ERROR CODE: -1 -- further updates: um. latest simple x264/x265 gui. using latest this (https://github.com/jpsdr/x264/releases) for my encoding, always have been, swapping it out in the C:\Program Files (x86)\MuldeR\Simple x264 Launcher v2\toolset\x64 folder. does this mean i cannot use tmod anymore? that would be very unfortunate... Code:
[2019-05-19][02:45:34] [2019-05-19][02:45:36] vpyp [info]: Error: fwrite() call failed when writing frame: 0, plane: 0, errno: 22 [2019-05-19][02:45:36] vpyp [info]: Output 9 frames in 1.82 seconds (4.95 fps) [2019-05-19][02:45:36] [2019-05-19][02:45:36] WARNING: Input process exited with error (code: 1), your encode might be *incomplete* !!! [2019-05-19][02:45:36] [2019-05-19][02:45:36] FATAL ERROR: The encoder process has *crashed* -> your encode probably is *incomplete* !!! [2019-05-19][02:45:36] Note that this indicates a bug in the current encoder, *not* in Simple x264/x265 Launcher. [2019-05-19][02:45:36] [2019-05-19][02:45:36] PROCESS EXITED WITH ERROR CODE: -1073741795 #update 2: that sucks. tmod indeed doesn't work at all. whereas regular x264 does. with regular avisynth script it has always worked though. is it something inherent to tmod and there's no hope or what? thanks! Last edited by LoRd_MuldeR; 19th May 2019 at 10:29. Reason: fixed code tags |
19th May 2019, 10:34 | #1799 | Link | ||
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
Quote:
Quote:
From the exit code -1073741795, which is equivalent to STATUS_ILLEGAL_INSTRUCTION (0xC000001D), we can conclude that x264 crashed because it tried to execute an instruction that is not supported by your CPU. If you get that error with "tmod" build, whereas the vanilla build that ships with Simple x264/x265 Launcher is working, then this indicates that the person who compiled "tmod" build used different compiler settings – settings not compatible with your CPU. Anything else concerning "tmod" build would have to be discussed with the person who provides those builds. I don't provide or use "tmod" build. BTW: You can ignore the warning about the input process (VapourSynth) in this case, because when the encoder processes crashes and thus breaks the pipe, then the input process won't be able to write to the pipe anymore, obviously.
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ Last edited by LoRd_MuldeR; 19th May 2019 at 17:31. |
||
|
|