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

[VideoFanatic]

Hi, from this post http://forum.doom9.org/showthread.php?p=1696590#post1696590 we discussed having a portable version of Simple x264 Launcher. I had it working fine but today I opened the program and I get a popup saying VapouSynth is not installed despite me disabling that warning before (I also checked the options and "Never show warning about missing Avisynth or Vapoursynth is still ticked"). Also when I go to add a new job none of my templates show up, the only thing that shows is Default. This has happened before in previous versions. My templates file is still where it should be but none of the templates show up in the program.

[LoRd_MuldeR]

Hi, from this post http://forum.doom9.org/showthread.php?p=1696590#post1696590 we discussed having a portable version of Simple x264 Launcher. I had it working fine but today I opened the program and I get a popup saying VapouSynth is not installed despite me disabling that warning before (I also checked the options and "Never show warning about missing Avisynth or Vapoursynth is still ticked"). Also when I go to add a new job none of my templates show up, the only thing that shows is Default. This has happened before in previous versions. My templates file is still where it should be but none of the templates show up in the program.

So, do you currently run Simple x264 Launcher in "portable mode" or not? :confused:

If you do so, it will store all INI files in the very same folder where the program file resides. Otherwise, it will store the INI files at "%LOCALAPPDATA%\LoRd_MuldeR\Simple x264 Launcher". Of course, in "portable mode", you must make sure the directory where the program file resides is actually writable! If it is not writable, e.g. because you put the program to "C:\Program Files\Something", your settings cannot be saved, obviously! Conversely, %LOCALAPPDATA% is always writable.

Also, if you switch from "portable mode" back to "standard" mode (or vice versa), your settings will be lost. That's because the program will now look for the INI files in a different place than where they have been saved before. Of course you can simply move the INI files to the new location and everything will be fine again. Anyway, moving your INI files around is only needed if you switch between "portable mode" and "standard" mode. It is not required as long as you stick to one mode.

Having said that, if you think that your settings are not saved correctly, I would suggest to inspect the INI files! Also, you can run the program with "--console" option to get more diagnostic output...

[VideoFanatic]

As far as I know I was running it in portable mode and the files are not in the C Drive so it should be writeable. The INI files are still in the folder where the program is. However when no templates showed up in the program I saved another one and it showed up in AppData\Local\LoRd_MuldeR\Simple x264 Launcher so it looks like the program changed to non-portable mode somehow.

How do you actually switch between modes?

[LoRd_MuldeR]

The INI files are still in the folder where the program is. However when no templates showed up in the program I saved another one and it showed up in AppData\Local\LoRd_MuldeR\Simple x264 Launcher so it looks like the program changed to non-portable mode somehow.

So, apparently, you have been using "portable mode" at some point in the past, but you are using the "standard" mode now. That's exactly the case that I described in my previous post...

How do you actually switch between modes?

C'mon! At least have a look at the README (http://muldersoft.com/docs/x264_launcher_readme.html) file before asking this :rolleyes:

[yangshao]

Use the simple x264 default parameters encoded video in iphone4s/5S inside can only play the start of 7mn31s, and then the picture stagnant not fast forward rewind, dance music playback, voice only! What is the reason? Should I fill in which parameters in the "custom encoder options"? The red line is shown as below:
http://image16.poco.cn/mypoco/myphoto/20141128/19/6253250320141128191919047.png?570x602_130
Code out of the MP4: Guardians of the Galaxy.2014.1280x720_23.976fps_121mins_2500KB,bit （The video using the computer to play is normal, but in iphone4s in error, unable to drag around playing!!）
Please tell me what I should do, thank you!

[LoRd_MuldeR]

1. There is are no "simple x264 default parameters", because Simple x264 Launcher defaults to whatever x264 defaults to (i.e. Simple x264 Launcher, by default, doesn't overwrite any x264 default settings).

2. Nobody ever claimed that a stream created with x264 default settings will play correctly on device XYZ.

3. Settings a specific H.264 Level via "--level" switch does not guarantee that the resulting H.264 stream will actually conform to that Level! There are many properties of the input file (frame rate, frame size, etc) that may violate the desired H.264 Level. And, if your input file violates the desired Level already, then there is nothing x264 could do about that. So be aware for any warnings that x264 may spit out!

4. You may need to setup the required VBV parameters for your playback device in order to ensure proper playback. But please don't ask me what the correct VBV parameters for your device are. Use Google ;)

[yangshao]

1. There is are no "simple x264 default parameters", because Simple x264 Launcher defaults to whatever x264 defaults to (i.e. Simple x264 Launcher, by default, doesn't overwrite any x264 default settings).

2. Nobody ever claimed that a stream created with x264 default settings will play correctly on device XYZ.

3. Settings a specific H.264 Level via "--level" switch does not guarantee that the resulting H.264 stream will actually conform to that Level! There are many properties of the input file (frame rate, frame size, etc) that may violate the desired H.264 Level. And, if your input file violates the desired Level already, then there is nothing x264 could do about that. So be aware for any warnings that x264 may spit out!

4. You may need to setup the required VBV parameters for your playback device in order to ensure proper playback. But please don't ask me what the correct VBV parameters for your device are. Use Google ;)

MP4-INFO:
http://image16.poco.cn/mypoco/myphoto/20141129/13/62532503201411291312043046902787195_001.jpg?541x629_130
Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L4.0
Format settings, CABAC : Yes
Format settings, ReFrames : 4 frames
Codec ID : avc1
Codec ID/Info : Advanced Video Coding
Duration : 1h 33mn
Source duration : 7mn 31s
Bit rate : 2 600 Kbps
Maximum bit rate : 17.0 Mbps
Width : 1 920 pixels
Height : 1 040 pixels
Display aspect ratio : 1.85:1
Frame rate mode : Constant
Frame rate : 23.976 fps
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.054
Stream size : 1.70 GiB (100%)
Source stream size : 1.70 GiB (100%)

Player iphone4s：
http://image16.poco.cn/mypoco/myphoto/20141129/13/62532503201411291312043046902787195_000.jpg?960x640_130
Play 7min31s and picture suspension, the only sound...

[kypec]

yangshao you have to correct the input parameter first because according to your screenshot you made an obvious typo:
-- level 3.1 is wrong
--level 3.1 is the correct setting

[LoRd_MuldeR]

Good observation, kypec. Actually I think the GUI shouldn't allow to enter "--" without an option name. Will be fixed for next version.

[Dion]

Can you please add an option to disable x264 version check.

[LoRd_MuldeR]

Please try with this TEST version:
http://sourceforge.net/projects/muldersoft/files/Simple%20x264%20Launcher/Testing/x264_launcher.2014-12-10.exe/download

This adds the "--skip-version-checks" command-line switch, or better, makes that switch work again ;)

[Dion]

Please try with this TEST version:
http://sourceforge.net/projects/muldersoft/files/Simple%20x264%20Launcher/Testing/x264_launcher.2014-12-10.exe/download

This adds the "--skip-version-checks" command-line switch, or better, makes that switch work again ;)

That works but not exactly ideal for the portable version.

x264_launcher_portable.exe

Was thinking an option in the options menu.

[LoRd_MuldeR]

That works but not exactly ideal for the portable version.

Where's the problem? You could write a Batch script that runs the program with the desired extra arguments and put it into the same folder as the EXE file - portable or not.


Was thinking an option in the options menu.

I don't want to encourage people to use outdated versions too much ;)

[Dion]

I don't want to encourage people to use outdated versions too much ;)

You already include the skip option via command.. Don't see how an option in the options would encourage people to use patched x264 builds. Alot easier then dealing with batch files. :/

[LoRd_MuldeR]

Alot easier then dealing with batch files. :/

That's the point. This is something you should use only in "special" situations (e.g. for testing something), but not for your every-day work.

Why exactly do you want to use an old/outdated encoder version anyway, except for testing? The only reason I can think of is that the latest version has some kind of regression(s).

But in that case, you should better get the developers to fix the regression, instead of reverting to on older version...

[Dion]

That's the point. This is something you should use only in "special" situations (e.g. for testing something), but not for your every-day work.

Why exactly do you want to use an old/outdated encoder version anyway, except for testing? The only reason I can think of is that the latest version has some kind of regression(s).

But in that case, you should better get the developers to fix the regression, instead of reverting to on older version...

Newer x264 have LSMASH issues. So they arent updated. ( modded x264 ).

So newer isn't always better.

[chinobino]

Hi all, I have been having trouble with x264 Launcher (2014-11-02) and the test build (2014-12-10) on Windows 8.1 x64.

I am loading avs scripts in to re-encode some decrypted MPEG-2 videos from DVD to 10-bit x264 or 10-bit x265.

The problem is that if I abort a job (to analyse the output) and then restart it (or recreate it), the job will always fail unless I rename the output file to something different.

If I don't rename the output file x264 Launcher asks me if I want to overwrite the existing file, I say 'Yes' and then the encoding process starts and errors out with this;

http://members.iinet.net.au/~michaeldd/x264_Launcher_Runtime_Error.png

And the log reads;

Simple x264 Launcher (Build #898), built 2014-12-10

Job started at 2014-12-15, 16:11:08.

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

--- SYSTEMINFO ---

Binary Path : C:\Program Files (x86)\MuldeR\Simple x264 Launcher v2
Avisynth : Yes
VapourSynth : C:\Program Files (x86)\VapourSynth\core32

--- SETTINGS ---

Encoder : x265 (H.265/HEVC), x64, 16-Bit
Source : Avisynth (avs)
RC Mode : CRF
Preset : Veryfast
Tuning : <None>
Profile : <Unrestricted>
Custom : --ref 10

--- CHECK VERSION ---

Detect video encoder version:

Creating process:
"C:\Program Files (x86)\MuldeR\Simple x264 Launcher v2\toolset\x64\x265_16bit_x64.exe" --version

x265 [info]: HEVC encoder version 1.4
x265 [info]: build info [Windows][MSVC 1800][64 bit] 16bpp
x265 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX

Detect video source version:

Creating process:
"C:\Program Files (x86)\MuldeR\Simple x264 Launcher v2\toolset\x86\avs2yuv_x86.exe"

Avs2YUV 0.24bm2

> x265 version: 1.4+0
> Avs2YUV version: 0.24.2

--- GET SOURCE INFO ---

Creating process:
"C:\Program Files (x86)\MuldeR\Simple x264 Launcher v2\toolset\x86\avs2yuv_x86.exe" -frames 1 "G:\\01 more than meets the eye (part 1).avs" NUL

G:\\01 more than meets the eye (part 1).avs: 960x720, 24000/1001 fps, 32949 frames

Resolution: 960x720
Frame Rate: 24000/1001
No. Frames: 32949

--- ENCODING VIDEO ---

Creating input process:
"C:\Program Files (x86)\MuldeR\Simple x264 Launcher v2\toolset\x86\avs2yuv_x86.exe" "G:\\01 more than meets the eye (part 1).avs" -

Creating encoder process:
"C:\Program Files (x86)\MuldeR\Simple x264 Launcher v2\toolset\x64\x265_16bit_x64.exe" --crf 22.0 --preset veryfast --ref 10 --output "G:\\01 More Than Meets The Eye (Part 1).hevc" --frames 32949 --y4m -

y4m [info]: 960x720 fps 24000/1001 i420p8 unknown frame count
x265 [info]: HEVC encoder version 1.4
x265 [info]: build info [Windows][MSVC 1800][64 bit] 16bpp
x265 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX
x265 [warning]: level 4 detected, but NumPocTotalCurr (total references) is non-compliant
x265 [info]: NONE profile, Level-NONE (Main tier)
x265 [info]: WPP streams / frame threads / pool : 23 / 3 / 8
x265 [info]: Internal bit depth : 10
x265 [info]: CTU size / RQT depth inter / intra : 32 / 1 / 1
x265 [info]: ME / range / subpel / merge : hex / 57 / 1 / 2
x265 [info]: Keyframe min / max / scenecut : 23 / 250 / 40
x265 [info]: Lookahead / bframes / badapt : 15 / 4 / 0
x265 [info]: b-pyramid / weightp / weightb / refs: 1 / 1 / 0 / 10
x265 [info]: Rate Control / AQ-Strength / CUTree : CRF-22.0 / 1.0 / 0
x265 [info]: tools: rd=2 esd lft sao signhide fast-intra tmvp
encoded 81 frames in 33.53s (2.42 fps), 2539.74 kb/s
x265 [info]: frame I: 9, Avg QP:10.57 kb/s: 8887.56
x265 [info]: frame P: 19, Avg QP:14.89 kb/s: 2303.27
x265 [info]: frame B: 53, Avg QP:16.88 kb/s: 1546.57
x265 [info]: global : 81, Avg QP:15.72 kb/s: 2539.74
x265 [info]: Weighted P-Frames: Y:5.3% UV:0.0%
x265 [info]: consecutive B-frames: 46.4% 3.6% 3.6% 7.1% 39.3%
av2y [info]: G:\\01 more than meets the eye (part 1).avs: 960x720, 24000/1001 fps, 32949 frames

WARNING: Input process exited with error (code: 3), your encode might be *incomplete* !!!
Final file size is 1.02 MB bytes.

--- COMPLETED ---

Job finished at 2014-12-15, 16:11:52. Process took 0 minutes, 44 seconds.

This happens regardless of which codec and parameters are used.

It also occurs if I delete the partially created file from the job that I aborted.

My avs script's process fine in VirtualDub but I would prefer to use x264 Launcher.

I searched for other instances of this problem but didn't find anything.

[LoRd_MuldeR]

Newer x264 have LSMASH issues. So they arent updated. ( modded x264 ).

So newer isn't always better.

What issues?

Anyway, recent x264 has support for L-SMASH MP4 Muxer built-in (http://git.videolan.org/?p=x264.git;a=blob;f=output/mp4_lsmash.c;), 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!


http://members.iinet.net.au/~michaeldd/x264_Launcher_Runtime_Error.png

It means Avisynth (or, more likely, one of the Avisynth plug-in's you are using) has just crashed. It's not a Simple x264 Launcher problem. Don't shoot the messenger!

Time to load up your debugger ;)

My avs script's process fine in VirtualDub but I would prefer to use x264 Launcher.

The joys of undefined behavior (http://en.wikipedia.org/wiki/Undefined_behavior) :rolleyes:

In the best case, the buggy program will crash right away, so at least you know that something is wrong and you can track down the cause (easily).

In the worst case, it will not crash at all - but produce corrupted outputs silently...

[chinobino]

It means Avisynth (or, more likely, one of the Avisynth plug-in's you are using) has just crashed. It's not a Simple x264 Launcher problem. Don't shoot the messenger!

Time to load up your debugger ;)

The joys of undefined behavior (http://en.wikipedia.org/wiki/Undefined_behavior) :rolleyes:

In the best case, the buggy program will crash right away, so at least you know that something is wrong and you can track down the cause (easily).

In the worst case, it will not crash at all - but produce corrupted outputs silently...

Ok, thankyou for clarifying - do you happen to know of a good source for debugging avs scripts and plug-ins?

At the moment I am trying to wrap my head around this (http://avisynth.nl/index.php/Filter_SDK/Debugging_instructions) one.

[kypec]

Could it be that the problem is caused by two backslashes in path after drive letter for output file?
Source file : G:\01 More Than Meets The Eye (Part 1).avs
Output file : G:\\01 More Than Meets The Eye (Part 1).hevc

[LoRd_MuldeR]

Could it be that the problem is caused by two backslashes in path after drive letter for output file?
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 (http://msdn.microsoft.com/en-us/library/windows/desktop/bb773569%28v=vs.85%29.aspx) form.

[Dion]

What issues?

Anyway, recent x264 has support for L-SMASH MP4 Muxer built-in (http://git.videolan.org/?p=x264.git;a=blob;f=output/mp4_lsmash.c;), 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]

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 :rolleyes:

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:
x264_8bit_x86.exe --version
x264 0.144.2525 40bb568

...and what the so-called "t_mod" build produces:
x264_x86.exe --version
x264 0.144.0+2574 9abcd72 t_mod_Custom [8-bit@all X86]

:scared:

[Remicade]

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

[LoRd_MuldeR]

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

Did you actually read the error message? :confused:

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

[Remicade]

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]

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 ;)

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.

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]

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

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]

Got the following crash (http://pastebin.com/bPp8qBt0) 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:

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]

Got the following crash (http://pastebin.com/bPp8qBt0) 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:

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 (http://forum.doom9.org/showthread.php?t=171668), 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]

New Test Build:

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

[LoRd_MuldeR]

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]

New Test Build:

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

[r0lZ]

The link to the x264 Online Doc (http://mewiki.project357.com/wiki/X264_Settings) 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]

The link to the x264 Online Doc (http://mewiki.project357.com/wiki/X264_Settings) 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/20150203203142/http://mewiki.project357.com/wiki/X264_Settings

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

[r0lZ]

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]

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]

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]

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]

Try this version please:
http://sourceforge.net/projects/muldersoft/files/Simple%20x264%20Launcher/Testing/x264_launcher.2015-03-23.exe/download

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

[LoRd_MuldeR]

New test build:

x265 binaries updated to v1.5+370.

[LoRd_MuldeR]

Simple x264 Launcher v2.50

Simple x264/x265 Launcher v2.50 [2015-04-17]
* Simple x264/x265 Launcher is based on the MUtilities (https://github.com/lordmulder/MUtilities) library
* Updated Qt runtime libraries to v4.8.7 snapshot-5 (2015-03-25)
* Overhauled startup code + show spinner while initializing
* Much improved Avisynth and VapourSynth detection code
* Added option to prefer 64-Bit VapourSynth, when available
* Updated x264 to revision 2538
* Updated x265 to version 1.6+174

[StinDaWg]

Something happened during the update and I lost all my prefs/templates. It's like it did a clean install. I still have the LoRd_MuldeR folder under AppData/Local with the old saved settings/templates, but none of the settings are being used. Also, no new log files are going to this folder (or anywhere else that I can see).

How do I get it working properly again?

It also keeps saying I need to check for an update because it's been longer than 14 days, even though I just updated it.

[LoRd_MuldeR]

Something happened during the update and I lost all my prefs/templates. It's like it did a clean install. I still have the LoRd_MuldeR folder under AppData/Local with the old saved settings/templates, but none of the settings are being used. Also, no new log files are going to this folder (or anywhere else that I can see).

For what version did you update to which one? Can you share (http://pastie.org/) your "templates.ini" files?

It also keeps saying I need to check for an update because it's been longer than 14 days, even though I just updated it.

Just let it check. The date when you last checked for updates with the current version has nothing to do with what you did (or did not do) with some previous version.

[StinDaWg]

You must have changed the default directory of installs recently. I now have two folders in program files (x86). MuldeR and LoRd_MuldeR.

I tried to copy the files from the old LoRd_MuldeR appdata folder into MuldeR, but it still won't take the old settings, and no new log files are created.

As for the version, it updated from whatever the previous one was to 2.50.948.

[LoRd_MuldeR]

Nope, nothing has changed regrading the paths! The default installation path is, and has always been:
%PROGRAMFILES%\MuldeR\Simple x264 Launcher v2

But of course the user decides the actual installation path during setup, so this can be whatever destination path you have selected during setup!


Furthermore, and totally independent from the chosen installation path, your settings will be stored to and loaded from:
%LOCALAPPDATA%\LoRd_MuldeR\Simple x264 Launcher

...unless you are running in "portable" mode, of course. In the latter case, settings are stored to and loaded from the application directory, i.e. where the EXE file is located.

(Note: In "portable" mode you have to ensure the application directory is actually writable, or your settings cannot be saved!)


As for the version, it updated from whatever the previous one was to 2.50.948.

I need the exact version from which you were upgrading (or at least your "templates.ini file). Otherwise I cannot try to reproduce your problem...

[StinDaWg]

Yes, I'm aware of that. But I'm very sure I did not not tell it to install to \LoRd_MuldeR when I first installed it months ago.

I'm going to uninstall everything, reboot, re-install, then try to copy over the template pref files.

Edit: So this is bizarre. Uninstalled, reboot, installed. It created %LOCALAPPDATA%\LoRd_MuldeR\LameXP - Audio Encoder Front-End.

The settings are located in this folder. There is no %LOCALAPPDATA%\LoRd_MuldeR\Simple x264 Launcher

I copied the old settings and template into the LameXP - Audio Encoder Front-End folder and now everything is back to normal.

Why did it create a folder named LameXP - Audio Encoder Front-End instead of Simple Launcher? I've never heard of this program and didn't install it. Is this an installer glitch on your end?

[LoRd_MuldeR]

So this is bizarre. Uninstalled, reboot, installed. It created %LOCALAPPDATA%\LoRd_MuldeR\LameXP - Audio Encoder Front-End.

The settings are located in this folder. There is no %LOCALAPPDATA%\LoRd_MuldeR\Simple x264 Launcher

I copied the old settings and template into the LameXP - Audio Encoder Front-End folder and now everything is back to normal.

Why did it create a folder named LameXP - Audio Encoder Front-End instead of Simple Launcher? I've never heard of this program and didn't install it. Is this an installer glitch on your end?

It's actually not that "bizarre", if you take into account that Simple x264 Launcher and LameXP now share a huge portion of their code-base, aka MUtilities (https://github.com/lordmulder/MUtilities) library ;)

But, of course, this is certainly not supposed to happen and I will have to investigate... :o

EDIT: This was a stupid Copy&Paste error, which has been fixed now. Fixed version will be available shortly, please stay tuned...

[LoRd_MuldeR]

Simple x264 Launcher v2.51
https://github.com/lordmulder/Simple-x264-Launcher/releases/tag/v2.51

Simple x264/x265 Launcher v2.51 [2015-04-26]
* Fixed regression: Config files were stored in a wrong directory
* Updated x265 to version 1.6+239

[r0lZ]

Just installed the newest version and now I have these dialogs, and the main window doesn't open:
---------------------------
MUtils
---------------------------
FATAL ERROR: MUtils library version mismatch detected!
---------------------------
OK
---------------------------

---------------------------
MUtils
---------------------------
Please re-build the complete solution in order to fix this issue!
---------------------------
OK
---------------------------