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. |
27th October 2019, 14:06 | #1821 | Link | |
Registered User
Join Date: Dec 2018
Posts: 58
|
I don't have virtual dub but I can play the AVSscript flawless in AVSPmod. Also mpeg2 DVD's can be encoded flawless even with x264 launcher.
So only x264/avc seems to be crashed. I made a short encode so I have a proper log for you to see: Quote:
|
|
27th October 2019, 15:56 | #1823 | Link | ||
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
I highly recommend you grab VirtualDub2 from here:
VirtualDub2_43803.zip Quote:
Please run the following command manually in a terminal: avs2yuv_x86.exe -frames 1 "C:\path\to\your\source.avs" NUL ...and then please tell us what the output is. (You find "avs2yuv_x86.exe" in your Simple x264 Launcher install directory below "toolset\x86" and, of course, you have to adjust the path to your AVS file as needed!) Output should be something like: Quote:
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ Last edited by LoRd_MuldeR; 27th October 2019 at 16:06. |
||
27th October 2019, 17:39 | #1824 | Link |
Registered User
Join Date: Dec 2002
Posts: 5,565
|
It's not simply "weird". It is the root of the problem. He has set "--bitrate 38200" i.e. 38200 kilobits per second. If you distribute these 38200 kilobits to 25000 frames that will 1528 bits per frame. Of course the output will look like garbage if you apply only 1/1000th of the bits you intended to.
|
27th October 2019, 18:17 | #1825 | 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 🇺🇦✊ |
|
11th November 2019, 02:36 | #1827 | Link |
Herr
Join Date: Apr 2009
Location: North Europe
Posts: 556
|
I can't run the newest version of x265 (3.2.1+1-b5c86a6) in Simple x264/x265 Launcher v2.94 (2019-10-05), it complains that it's a too old version of x265.
Also, there is a newer version (not any important feature, but it's compiled with a more newer compiler) of Avs2YUV released than is included in that package, http://avisynth.nl/index.php/Avs2YUV Thanks. EDIT: Thanks for the advice redbtn. Last edited by Forteen88; 12th November 2019 at 09:06. Reason: Thanking |
11th November 2019, 12:36 | #1828 | Link | ||
Registered User
Join Date: Jan 2019
Location: Russia
Posts: 105
|
Quote:
Quote:
|
||
20th November 2019, 13:03 | #1829 | Link |
Herr
Join Date: Apr 2009
Location: North Europe
Posts: 556
|
I'm having errors when I'm encoding with x265 (I updated to x265-3.2+15) using 2-pass with Simple x264/x265 Launcher v2.94 (2019-10-05), it fails in the 2nd pass. Anyone else got this problem?
x265 in CRF-mode works great though. I only want to use 2-pass mode (to get same average bitrate) to make tests on which --psy-rd & --psy-rdoq values I prefer most. Maybe I should reinstall Simple x264/x265 Launcher with the old software (x265) to see if 2-pass mode works... BTW, what happened to LoRd_MuldeR (who created this software)? He has not been online at Doom9 for a long time now (Last Activity: 29th October 2019), I hope that he's OK. EDIT: Never mind, it seems that the version of x265 had problem with 2-pass encoding. I've not tried it though. Last edited by Forteen88; 6th December 2019 at 11:05. Reason: updates |
13th December 2019, 00:02 | #1831 | Link | |||
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
Quote:
Everything is okay. It's just real life kicking in, every now and then
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ Last edited by LoRd_MuldeR; 13th December 2019 at 00:36. |
|||
28th December 2019, 11:00 | #1834 | Link |
Acid fr0g
Join Date: May 2002
Location: Italy
Posts: 2,582
|
Notice that http_//download.videolan.org/pub/x264/binaries/ is discontinued as service.
Please update to https_//artifacts.videolan.org/x264/ to get them. Plus using latest x264 gives following warning: Code:
[2019-12-28][11:02:33] x264 0.159.2991 1771b55 [2019-12-28][11:02:33] (libswscale 5.6.100) [2019-12-28][11:02:33] (libavformat 58.33.100) [2019-12-28][11:02:33] built on Dec 16 2019, gcc: 8.2-win32 20190215 [2019-12-28][11:02:33] x264 configuration: --chroma-format=all [2019-12-28][11:02:33] libx264 configuration: --chroma-format=all [2019-12-28][11:02:33] x264 license: GPL version 2 or later [2019-12-28][11:02:33] libswscale/libavformat license: LGPL version 2.1 or later [2019-12-28][11:02:33] [2019-12-28][11:02:33] WARNING: Your x264 binary uses an untested core (API) version, take care! [2019-12-28][11:02:33] This application works best with x264 core (API) version 158. Newer versions may work or not.
__________________
@turment on Telegram Last edited by tormento; 28th December 2019 at 11:17. |
31st December 2019, 16:23 | #1835 | Link | |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
Quote:
But I have been using LigH's builds for quite some time now, because those have FFMS support enabled – which the Videolan.org builds do not have – and because Komisar's builds have not been updated in a long time. Anyways, as far as I can tell, there have not been any relevant changes since r2984 (the last time I updated the included x264 binaries), except maybe for this VBV-related fix: https://code.videolan.org/videolan/x...c9e3933db32db2 (Unless you are using CFR+VBV, you don't need to care. And even if you do, the bug they fixed recently probably only occurs under very rare circumstances)
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ Last edited by LoRd_MuldeR; 31st December 2019 at 16:35. |
|
1st January 2020, 16:32 | #1836 | Link |
Herr
Join Date: Apr 2009
Location: North Europe
Posts: 556
|
LoRd_MuldeR, there is a newer version (not any important features, but it's compiled with a more newer compiler) of Avs2YUV released than is included in that package,
http://avisynth.nl/index.php/Avs2YUV How do I use that newer version of Avs2YUV in "Simple x264/x265 Launcher v2.94 (2019-10-05)"? I got an error last time I tried to use it after updating Avs2YUV. BTW, Happy New Year! |
1st January 2020, 20:49 | #1837 | Link | |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
Quote:
Also, the only change in Avs2YUV 0.24 "mod 6", since Avs2YUV 0.24 "mod 5" that is currently included with Simple x264 Launcher, is the addition of 4:0:0 (monochrome) output support. Unless you need exactly that, you don't need to care. Anyhow, next Simple x264 Launcher release will probably be updated to Avs2YUV 0.24 "mod 6".
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ Last edited by LoRd_MuldeR; 1st January 2020 at 20:51. |
|
3rd January 2020, 01:39 | #1838 | Link |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
Here is a new TEST build that has the latest x264 and Avs2YUV versions included:
x264_launcher-TEST.2020-01-03.exe
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ |
4th January 2020, 13:11 | #1840 | Link |
Registered User
Join Date: Sep 2012
Posts: 17
|
Lord_Mulder, I have a problem with determining clip properties. It fails on "Get source info" step, but it seems that the command that is used is ok.
When I run it manually, I get following response: K:\dg.avs: 1280x534, YV12, 8-bits, progressive, 24000/1001 fps, 154508 frames From what I saw in the code, this step is about extracting some of these values using regex. Is my output somehow different from the one that is expected by the regex? |
|
|