Simple x264/x265 Launcher v3.02 (2022-06-16) - Page 72

LoRd_MuldeR · 22nd December 2014, 17:58

Quote:

Originally Posted by kypec

Could it be that the problem is caused by two backslashes in path after drive letter for output file?

Code:

Source file : G:\01 More Than Meets The Eye (Part 1).avs
Output file : G:\\01 More Than Meets The Eye (Part 1).hevc

Shouldn't be a problem. There is an infinite number of possible ways to write a path that refers to the same file. And there generally is no requirement to pass a path in canonical form.

Dion · 5th January 2015, 07:01

Quote:

Originally Posted by LoRd_MuldeR

What issues?

Anyway, recent x264 has support for L-SMASH MP4 Muxer built-in, so there's no need for any "modded x264" to get L-SMASH support.

And if you encounter any problems with the built-in L-SMASH muxer in up-to-date (vanilla) x264, better report to the developers!

Apparently it has been updated and was buried in the comments.

However your launcher detects it out of date when its running on the latest x264.

https://github.com/jpsdr/x264/releases/tag/r2525

LoRd_MuldeR · 5th January 2015, 20:40

Quote:

Originally Posted by Dion

However your launcher detects it out of date when its running on the latest x264.

https://github.com/jpsdr/x264/releases/tag/r2525

This modified build of x264 changes the x264 outputs in a way which breaks compatibility to "vanilla" x264. Thus the version number cannot be read correctly by the GUI

Or, more precisely, the GUI does read the version number correctly, but at the position where the build number is supposed to be, the "modified" build prints a zero.

And, of course, you cannot expect that a GUI, such as Simple x264 Launcher, will support any non-standard variant of x264 that might be floating around somewhere on the Internet...

Instead, find the person who thought that it would be a good idea to totally mess up the x264 version string. And then ask him or her to get rid of this pointless quirk!

Standard x264, i.e. how the output is supposed to look:

Code:

x264_8bit_x86.exe --version
x264 0.144.2525 40bb568

...and what the so-called "t_mod" build produces:

Code:

x264_x86.exe --version
x264 0.144.0+2574 9abcd72 t_mod_Custom [8-bit@all X86]

Remicade · 11th January 2015, 18:48

I get this error with avi, mkv, mov. Why ?

LoRd_MuldeR · 11th January 2015, 18:58

Quote:

Originally Posted by Remicade

I get this error with avi, mkv, mov. Why ?

Did you actually read the error message?

(It should be rather clear. If something remains unclear, please specify your question more precisely.)

Remicade · 11th January 2015, 19:06

I read but vidcoder and internet friendly media encoder works with this file and x265.exe. Simple x264 Launcher has another version of x265.exe ? What I have to do for x265.exe to work in Simple x264 Launcher ? I don't know much about x265.exe, I make many conversions with x264.exe (megui, staxrip and ripbot) and It's works very well.
Maybe this is the problem ?

LoRd_MuldeR · 11th January 2015, 19:08

x265 does not support anything but uncompressed input yet. So, unless this has changed very recently, x265 can not read AVI files (directly).

If you want this to be changed, ask the x265 developers, not me. And, until then, simply use Avisynth or VapurSynth input in order to feed your AVI file into x265

Quote:

Simple x264 Launcher has another version of x265.exe ?

No. Simple x264 Launcher uses a "vanilla" build of x265, i.e. it has been built from the official x265 sources with no modifications whatsoever.

Quote:

Maybe this is the problem?

Yes, trying to open an AVI file with a program that is known to not support AVI as input, is a problem. It means you are trying to do something that is not currently possible.

LoRd_MuldeR · 31st January 2015, 20:49

Simple x264 Launcher v2.46
https://github.com/lordmulder/Simple...ases/tag/v2.46

Quote:

Simple x264/x265 Launcher v2.46 [2015-01-31]
* Updated x265 to version 1.4+424
* Updated x264 to revision 2525
* Updated Avs2YUV to version 0.24 (BugMaster's mod 3)
* Proper detection of Windows 10
* Added new Tuning options for x265 encoder

VideoFanatic · 2nd February 2015, 20:27

Got the following crash on MT Avisynth 2.6 running in Non-MT mode with Simple x264 Launcher:

WARNING: Input process exited with error (code: 1), your encode might be *incomplete* !!!

Bit annoying as I was encoding the 24 hours of Le Mans and it was 3/4s of the way finished then it crashed. I thought you don't get crashes when running in single threaded mode? Here's my script - the plugins I'm using are pretty stable:

Code:

DGSource("D:\Le Mans 24 Hour 2014 Race.dgi")

AssumeTFF() 
DeGrainMedian(limitY=2, limitUV=3, mode=1, interlaced=true)

Yadif(mode=1, order=1)
Vinverse()
Spline36Resize(1280,720)

Crop(2,2,-2,-8)
AddBorders(2,6,2,4, $000000)

LoRd_MuldeR · 2nd February 2015, 21:31

Quote:

Originally Posted by VideoFanatic

Got the following crash on MT Avisynth 2.6 running in Non-MT mode with Simple x264 Launcher:

WARNING: Input process exited with error (code: 1), your encode might be *incomplete* !!!

Bit annoying as I was encoding the 24 hours of Le Mans and it was 3/4s of the way finished then it crashed. I thought you don't get crashes when running in single threaded mode? Here's my script - the plugins I'm using are pretty stable:

Code:

DGSource("D:\Le Mans 24 Hour 2014 Race.dgi")

AssumeTFF() 
DeGrainMedian(limitY=2, limitUV=3, mode=1, interlaced=true)

Yadif(mode=1, order=1)
Vinverse()
Spline36Resize(1280,720)

Crop(2,2,-2,-8)
AddBorders(2,6,2,4, $000000)

Since this is almost certainly not a GUI-related problem, please discuss in the proper Avisynth forum.

Anyway, I highly recommend to use latest stable Avisynth, if you encounter any strange issues with Avisynth MT. If it does work with stable Avisynth, you know that it's either an Avisynth-MT issue or one of your plug-in's is not MT-safe.

The MT branch has always been a game of luck

LoRd_MuldeR · 9th February 2015, 20:19

New Test Build:

This is the first build that is based on the MUtilities library. Please report any regressions you may notice

LoRd_MuldeR · 28th February 2015, 18:24

New Test Build:

This version offers much improved VapourSynth detection code. 32-Bit and 64-Bit editions of VapourSynth are now detected separately. And, if both are available, you can choose which one you want to use.

Note that, in order to get both, 32-Bit and 64-Bit, editions VapourSynth, you must install both, 32-Bit and 64-Bit, Python before installing VapourSynth. Make sure you install them to different directories!

LoRd_MuldeR · 9th March 2015, 20:40

New Test Build:

This version includes: Improved Avisynth detection code + updated included x265 binaries.

r0lZ · 10th March 2015, 16:40

The link to the x264 Online Doc in your "?" menu is dead, and it seems that it's for ever. Do you know another site with the explanation of the x264 command line options? I've googled and found several sites, but all of them are completely outdated. If you know a good up to date site, can you change the link in the next version of Simple x264 Launcher, and, in the meantime, post it here too? Thanks.

I'm using the latest non-beta release, v2.46.902. I haven't checked the last test build.

LoRd_MuldeR · 10th March 2015, 19:43

Quote:

Originally Posted by r0lZ

The link to the x264 Online Doc in your "?" menu is dead, and it seems that it's for ever. Do you know another site with the explanation of the x264 command line options? I've googled and found several sites, but all of them are completely outdated. If you know a good up to date site, can you change the link in the next version of Simple x264 Launcher, and, in the meantime, post it here too? Thanks.

I could change the link to point to the Archive.org mirror, if the site is permanently down:
https://web.archive.org/web/20150203.../X264_Settings

Alternatively, there would be this article on the Wikibooks.org web-site:
http://en.wikibooks.org/wiki/MeGUI/x264_Settings

r0lZ · 10th March 2015, 20:01

I have checked the old link several times since two weeks or so, and it was always down. So, yes, it seems that the site is abandoned.

IMO, the wikibook article looks better. Wayback is a great tool, but linking to a page that is not maintained officially any more is not a very good alternative imo.
Anyway, thanks for the links!

LoRd_MuldeR · 14th March 2015, 15:16

New Test Build:

Update x264 to r2538 and x265 to v1.5+200. Also fixed the link to x264 documentation, since the "mewiki" site seems to be gone for good.

THEAST · 23rd March 2015, 13:04

I had a small request: is there a chance a horizontal slider could be added to the job details windows? Depending on screen resolution, sometimes lines (usually commands with too many switches) will not fit on the screen no matter how much the GUI windows is stretched horizontally.

LoRd_MuldeR · 23rd March 2015, 21:28

Quote:

Originally Posted by THEAST

I had a small request: is there a chance a horizontal slider could be added to the job details windows? Depending on screen resolution, sometimes lines (usually commands with too many switches) will not fit on the screen no matter how much the GUI windows is stretched horizontally.

Try this version please:

Note the changes in the context menu of the log view, where you can enable line-wrapping now!

THEAST · 24th March 2015, 12:50

Quote:

Originally Posted by LoRd_MuldeR

Try this version please:
http://sourceforge.net/projects/muld...3.exe/download

Note the changes in the context menu of the log view, where you can enable line-wrapping now!

Thank you.

2nd February 2015, 20:27	#1429 \| Link
VideoFanatic Registered User Join Date: Sep 2011 Posts: 241	Got the following crash on MT Avisynth 2.6 running in Non-MT mode with Simple x264 Launcher: WARNING: Input process exited with error (code: 1), your encode might be incomplete !!! Bit annoying as I was encoding the 24 hours of Le Mans and it was 3/4s of the way finished then it crashed. I thought you don't get crashes when running in single threaded mode? Here's my script - the plugins I'm using are pretty stable: Code: DGSource("D:\Le Mans 24 Hour 2014 Race.dgi") AssumeTFF() DeGrainMedian(limitY=2, limitUV=3, mode=1, interlaced=true) Yadif(mode=1, order=1) Vinverse() Spline36Resize(1280,720) Crop(2,2,-2,-8) AddBorders(2,6,2,4, $000000)

9th February 2015, 20:19	#1431 \| Link
LoRd_MuldeR Software Developer Join Date: Jun 2005 Location: Last House on Slunk Street Posts: 13,275	New Test Build: This is the first build that is based on the MUtilities library. Please report any regressions you may notice __________________ Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ Last edited by LoRd_MuldeR; 28th February 2015 at 18:37.

28th February 2015, 18:24	#1432 \| Link
LoRd_MuldeR Software Developer Join Date: Jun 2005 Location: Last House on Slunk Street Posts: 13,275	New Test Build: This version offers much improved VapourSynth detection code. 32-Bit and 64-Bit editions of VapourSynth are now detected separately. And, if both are available, you can choose which one you want to use. Note that, in order to get both, 32-Bit and 64-Bit, editions VapourSynth, you must install both, 32-Bit and 64-Bit, Python before installing VapourSynth. Make sure you install them to different directories! __________________ Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ Last edited by LoRd_MuldeR; 9th March 2015 at 20:41.

9th March 2015, 20:40	#1433 \| Link
LoRd_MuldeR Software Developer Join Date: Jun 2005 Location: Last House on Slunk Street Posts: 13,275	New Test Build: This version includes: Improved Avisynth detection code + updated included x265 binaries. __________________ Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ Last edited by LoRd_MuldeR; 14th March 2015 at 15:18.

10th March 2015, 16:40	#1434 \| Link
r0lZ PgcEdit daemon Join Date: Jul 2003 Posts: 7,524	The link to the x264 Online Doc in your "?" menu is dead, and it seems that it's for ever. Do you know another site with the explanation of the x264 command line options? I've googled and found several sites, but all of them are completely outdated. If you know a good up to date site, can you change the link in the next version of Simple x264 Launcher, and, in the meantime, post it here too? Thanks. I'm using the latest non-beta release, v2.46.902. I haven't checked the last test build. __________________ r0lZ PgcEdit homepage (hosted by VideoHelp) BD3D2MK3D A tool to convert 3D blu-rays to SBS, T&B or FS MKV

10th March 2015, 20:01	#1436 \| Link
r0lZ PgcEdit daemon Join Date: Jul 2003 Posts: 7,524	I have checked the old link several times since two weeks or so, and it was always down. So, yes, it seems that the site is abandoned. IMO, the wikibook article looks better. Wayback is a great tool, but linking to a page that is not maintained officially any more is not a very good alternative imo. Anyway, thanks for the links! __________________ r0lZ PgcEdit homepage (hosted by VideoHelp) BD3D2MK3D A tool to convert 3D blu-rays to SBS, T&B or FS MKV

14th March 2015, 15:16	#1437 \| Link
LoRd_MuldeR Software Developer Join Date: Jun 2005 Location: Last House on Slunk Street Posts: 13,275	New Test Build: Update x264 to r2538 and x265 to v1.5+200. Also fixed the link to x264 documentation, since the "mewiki" site seems to be gone for good. __________________ Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ Last edited by LoRd_MuldeR; 17th April 2015 at 21:05.

23rd March 2015, 13:04	#1438 \| Link
THEAST Registered User Join Date: Apr 2009 Posts: 76	I had a small request: is there a chance a horizontal slider could be added to the job details windows? Depending on screen resolution, sometimes lines (usually commands with too many switches) will not fit on the screen no matter how much the GUI windows is stretched horizontally. Last edited by THEAST; 23rd March 2015 at 14:07.

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode