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

[LoRd_MuldeR]

Updated x264 to r1210 (JEEB's builds). Download link in first post updated.

[LoRd_MuldeR]

Updated x264 to r1214 (JEEB's builds). This fixes a bug in QPRD (SubME 10) and greatly improves 1-Pass VBV. Update to x264 r1214+ is highly recommended.

[nakTT]

Updated x264 to r1214 (JEEB's builds). This fixes a bug in QPRD (SubME 10) and greatly improves 1-Pass VBV. Update to x264 r1214+ is highly recommended.
Hi Lord,

I have one question regarding your software. Is the software only encode video without audio or it also encode audio for the movie (like Megui)?

[Wishbringer]

Is the software only encode video without audio or it also encode audio for the movie (like Megui)?

It's a launcher for x264 64bit version for AviSynth 32bit.
x264 is an AVC video encoder...

It's not an all-in-one-tool like MeGui, RipBot etc.

[nakTT]

It's a launcher for x264 64bit version for AviSynth 32bit.
x264 is an AVC video encoder...

It's not an all-in-one-tool like MeGui, RipBot etc.
Sorry if my question wasn't clear. I know x264 is an AVC VIDEO encoder. I'm just asking for a confirmation whether or not this Application made by Loard can encode a complete movies or or just a video part of it.

Since you have answered the question, I thank you very much.

:thanks:

[LoRd_MuldeR]

It's not an all-in-one-tool like MeGui, RipBot etc.

Correct. It's a very simple front-end to x264.exe, nothing else. And x264.exe doesn't process audio at all ;)

I recommend MKVToolnix or YAMB to mux in the audio after encoding, when needed...

[nakTT]

Correct. It's a very simple front-end to x264.exe, nothing else. And x264.exe doesn't process audio at all ;)

I recommend MKVToolnix or YAMB to mux in the audio after encoding, when needed...
Any suggestion for simple tools to make avs for the Launcher?

:thanks:

[LoRd_MuldeR]

Any suggestion for simple tools to make avs for the Launcher?

:thanks:

Notepad++ :p

Or maybe this one:
http://avisynth.org/qwerpoi/index.html

[LoRd_MuldeR]

Updated x264 to r1217 (JEEB's builds). Download link in first post updated.

[nakTT]

Notepad++ :p

Or maybe this one:
http://avisynth.org/qwerpoi/index.html
Thanks. But until now I still using MeGUI tools "AVS Script Creator" in the tools menu. Any other simple to use AVS creator like in MeGUI that you want to suggest.

:thanks:

[Teddl]

Hi there!
Benchmarks are fun! :)

AMDPhenom(tm 9950 Quad-Core Processor 2.60GHz; Windows Vista(tm) Ultimate 64bit SP2,
Source: DivX.Avi@17000kbits (Ingame Video); x264 JEEB's builds from your .7z archive


Source: H:\17000B&B.avs
Preset: Faster
Tuning: None
Profile: High
Params: (din't show but --crf 23.0 --output H:\17000B&B2.mp4)

[Type: 32-Bit, Pipe Buffer Size: 0 MByte]
encoded 10104 frames, 30.87 fps, 4849.01 kb/s
encoded 10104 frames, 31.22 fps, 4848.35 kb/s
encoded 10104 frames, 31.35 fps, 4847.00 kb/s

[Type: 64-Bit, Pipe Buffer Size: 0 MByte]
encoded 10104 frames, 31.96 fps, 4850.68 kb/s
encoded 10104 frames, 31.95 fps, 4850.15 kb/s
encoded 10104 frames, 31.88 fps, 4847.02 kb/s

[Type: 64-Bit, Pipe Buffer Size: 1 MByte]
encoded 10104 frames, 32.17 fps, 4843.76 kb/s
encoded 10104 frames, 32.13 fps, 4848.87 kb/s
encoded 10104 frames, 32.22 fps, 4851.95 kb/s

[Type: 64-Bit, Pipe Buffer Size: 2 MByte]
encoded 10104 frames, 32.74 fps, 4849.16 kb/s
encoded 10104 frames, 32.77 fps, 4849.17 kb/s
encoded 10104 frames, 32.74 fps, 4844.90 kb/s

[Type: 64-Bit, Pipe Buffer Size: 4 MByte]
encoded 10104 frames, 32.97 fps, 4847.00 kb/s
encoded 10104 frames, 32.93 fps, 4851.58 kb/s
encoded 10104 frames, 33.01 fps, 4846.86 kb/s

[Type: 64-Bit, Pipe Buffer Size: 8 MByte]
encoded 10104 frames, 32.86 fps, 4847.44 kb/s
encoded 10104 frames, 32.95 fps, 4849.03 kb/s
encoded 10104 frames, 32.92 fps, 4849.81 kb/s

Resolution: 1280 x 720
Frame No. : 10104
Frame Rate: 25/1

x264 0.72.1217M 5e9ae4c
built on Aug 20 2009, gcc: 4.3.4 20090220 (prerelease) (x64.generic.Komisar)
Revision: 1217

6 or 7% gain for 64-Bit 4MB to 32-Bit 0MB? Math is long time ago for me. :o

Source: YV12 640x360
Source: H:\17000B&B.avs
Preset: Faster
Tuning: None
Profile: High
Params:

[Type: 32-Bit, Pipe Buffer Size: 0 MByte]
encoded 10104 frames, 128.38 fps, 1441.13 kb/s
encoded 10104 frames, 117.09 fps, 1441.13 kb/s
encoded 10104 frames, 117.66 fps, 1441.13 kb/s

[Type: 64-Bit, Pipe Buffer Size: 0 MByte]
encoded 10104 frames, 123.71 fps, 1441.13 kb/s
encoded 10104 frames, 125.47 fps, 1441.13 kb/s
encoded 10104 frames, 123.43 fps, 1441.13 kb/s

[Type: 64-Bit, Pipe Buffer Size: 1 MByte]
encoded 10104 frames, 136.70 fps, 1441.13 kb/s
encoded 10104 frames, 134.54 fps, 1441.13 kb/s
encoded 10104 frames, 136.24 fps, 1441.13 kb/s

[Type: 64-Bit, Pipe Buffer Size: 2 MByte]
encoded 10104 frames, 134.89 fps, 1441.13 kb/s
encoded 10104 frames, 142.73 fps, 1441.13 kb/s
encoded 10104 frames, 134.41 fps, 1441.13 kb/s

[Type: 64-Bit, Pipe Buffer Size: 4 MByte]
encoded 10104 frames, 137.39 fps, 1441.13 kb/s
encoded 10104 frames, 137.96 fps, 1441.13 kb/s
encoded 10104 frames, 135.49 fps, 1441.13 kb/s

[Type: 64-Bit, Pipe Buffer Size: 8 MByte]
encoded 10104 frames, 139.85 fps, 1441.13 kb/s
encoded 10104 frames, 139.96 fps, 1441.13 kb/s
encoded 10104 frames, 139.14 fps, 1441.13 kb/s



Don't know if you can use this:
DivX.Avi@17000kbits with JEEB's builds from your yesterday.. no big changes:

Source: H:\17000B&B.avs
Preset: Faster
Tuning: None
Profile: High
Params: (din't show.. but: --crf 23.0 --output H:\17000B&B2.mp4)

[Type: 32-Bit, Pipe Buffer Size: 0 MByte]
encoded 10104 frames, 31.01 fps, 4820.78 kb/s
encoded 10104 frames, 30.86 fps, 4820.53 kb/s
encoded 10104 frames, 31.17 fps, 4819.30 kb/s

[Type: 64-Bit, Pipe Buffer Size: 0 MByte]
encoded 10104 frames, 31.68 fps, 4819.03 kb/s
encoded 10104 frames, 31.82 fps, 4817.60 kb/s
encoded 10104 frames, 31.79 fps, 4818.23 kb/s

[Type: 64-Bit, Pipe Buffer Size: 1 MByte]
encoded 10104 frames, 32.07 fps, 4818.78 kb/s
encoded 10104 frames, 31.77 fps, 4818.48 kb/s
encoded 10104 frames, 32.19 fps, 4818.60 kb/s

[Type: 64-Bit, Pipe Buffer Size: 2 MByte]
encoded 10104 frames, 32.69 fps, 4818.92 kb/s
encoded 10104 frames, 32.39 fps, 4819.50 kb/s
encoded 10104 frames, 32.92 fps, 4818.74 kb/s

[Type: 64-Bit, Pipe Buffer Size: 4 MByte]
encoded 10104 frames, 33.03 fps, 4817.76 kb/s
encoded 10104 frames, 32.77 fps, 4820.07 kb/s
encoded 10104 frames, 33.23 fps, 4820.41 kb/s

[Type: 64-Bit, Pipe Buffer Size: 8 MByte]
encoded 10104 frames, 33.20 fps, 4818.04 kb/s
encoded 10104 frames, 33.01 fps, 4818.66 kb/s
encoded 10104 frames, 32.49 fps, 4817.34 kb/s

x264 0.72.1235M 448b138
built on Aug 27 2009, gcc: 4.3.4 20090220 (prerelease) (x64.generic.Komisar)
Revision: 1235


Want your GUI with Automatic 3pass :p

[nakTT]

Updated x264 to r1217 (JEEB's builds). Download link in first post updated.
Can it work with x264 from:

http://x264.nl/ ?

[LoRd_MuldeR]

Updated x264 to r1247 (JEEB's builds). Download link in first post updated!

Can it work with x264 from:

http://x264.nl/ ?

Sure, why not? :confused:

(Just be sure to save the 32-Bit build as "x264.exe" and the 64-Bit build as "x264_x64.exe" in the same folder as the "launcher.exe")

Want your GUI with Automatic 3pass :p

3-Pass is a placebo :sly:

[LoRd_MuldeR]

Updated x264 to r1251 (JEEB's builds (http://forum.doom9.org/showpost.php?p=1322616&postcount=2273)). Download link in first post updated!

I also fixed job control on Vista/Win7. This should make "abort" work on those OS. Before only 'pipebuf.exe' was terminated, but not 'x264.exe' and 'avs2yuv.exe' ;)

[nakTT]

Updated x264 to r1251 (JEEB's builds (http://forum.doom9.org/showpost.php?p=1322616&postcount=2273)). Download link in first post updated!

I also fixed job control on Vista/Win7. This should make "abort" work on those OS. Before only 'pipebuf.exe' was terminated, but not 'x264.exe' and 'avs2yuv.exe' ;)
When I mux my output video from the launcher with aac audio using Megui, the audio seems to be out of sync. I don't have this issue when I do the whole encoding job with Megui. Any idea? Please advice.

:thanks:

[LoRd_MuldeR]

When I mux my output video from the launcher with aac audio using Megui, the audio seems to be out of sync. I don't have this issue when I do the whole encoding job with Megui. Any idea? Please advice.

:thanks:

This is a GUI for x264.exe only! And x264 does not process audio at all.

The one and only thing that could effect the audio sync would be the framerate. My GUI will obtain the framerate from Avisynth and forward it to x264.

And that seems to work properly for me...

[nakTT]

This is a GUI for x264.exe only! And x264 does not process audio at all.

The one and only thing that could effect audio sync would be the framerate. But my GUI will obtain the framerate from Avisynth and forward it to x264. Seems to work properly for me.
Thanks for the reply. I do know that the launcher do not process audio (you already let me know sometime ago, remember? ;)). That is why I mux the video and audio using MeGUI instead. Anyway, any chance the total frame for the output is a bit different (more?) from Avisynth?

:thanks:

[LoRd_MuldeR]

That is why I mux the video and audio using MeGUI instead.

Why not use MKVToolnix ???

Anyway, any chance the total frame for the output is a bit different (more?) from Avisynth?

This shouldn't happen. The encoded file should always have exactly the same number of frames as the input Avisynth script! And in my experience that is the case ;)

So unless there is any indication that something is wrong with the video part, your muxing problem doesn't belong to this thread...

[nakTT]

Why not use MKVToolnix ???
Thanks for the suggestion. Will try to use it.

:thanks:

[LoRd_MuldeR]

Updated x264 r1251 with latest JEEB builds (http://forum.doom9.org/showpost.php?p=1323501&postcount=2294), including the fixed HRD patch (http://forum.doom9.org/showpost.php?p=1323313&postcount=2291). Download link in first post updated!

[m3mbran3]

megui just uses its on front-end for MKVToolnix so it should be the same thing.

I must say that this program really is useful and use it for all my encodes now. The only issue I have is if I'm trying to batch encode because there is no queue like in megui, anyway to overcome this? be it either by command line or batch file.

[LoRd_MuldeR]

The only issue I have is if I'm trying to batch encode because there is no queue like in megui, anyway to overcome this? be it either by command line or batch file.

Not implemented yet and not currently planned, because I'm busy with "real life" stuff. But feel free to hack that in, the sources are included...

[yesgrey]

LoRd_MuldeR,
In the dialog, group "Rate Control", I think it's missing a "t" in the word "Quanizer"...

[LoRd_MuldeR]

LoRd_MuldeR,
In the dialog, group "Rate Control", I think it's missing a "t" in the word "Quanizer"...

Well spotted. I will fix the typo for next release ;)

[yesgrey]

Well spotted.
It's easier when we're looking at it for the first time...:)
By the way, is it possible for you to add .264 file output?

Thanks.

[LoRd_MuldeR]

By the way, is it possible for you to add .264 file output?

Yes, that was easy and quick to do. Download link in first post updated!

[yesgrey]

Thanks!
I prefer to mux into mkv using eac3to.;)

[LoRd_MuldeR]

Updated x264 to r1259 (Komisar's builds). Download link in first post updated.

[click2]

Is sources.tar missing a few files? mulder_toolz.pas and unit_runprocess.pas for instance

[LoRd_MuldeR]

Is sources.tar missing a few files? mulder_toolz.pas and unit_runprocess.pas for instance

You are right. That is code shared with other project, so I forgot to include it :o

http://www.mediafire.com/file/cmkztvt4ynm/MuldeR_Toolz.2009-09-21.zip

[Widok]

[edit]

[LoRd_MuldeR]

Looks like some DirectShow problem, so this is not the right thread to complain. Anyway, it seems other people saw the same issue:
http://forum.doom9.org/showthread.php?p=1327378#post1327378

:search:


I can only recommend to try something that isn't DirectShowSource(), for example FFVideoSource() (http://code.google.com/p/ffmpegsource/) from FFmpegSource project ;)

[XadoX]

:thanks: for this nice GUI!

[LoRd_MuldeR]

Updated x264 to r1271 (Komisar's builds). Download link in first post updated!

[dstln]

Thanks for keeping this updated, looking forward to playing around with it on new OS.

Nice progress bar too :P

[ACrowley]

i like your gui, its exactly what i need..a simple x264 gui :)

Can you add 1 Pass Options please ? I want to use different lowered Settings in 1st Pass.

I know that new x264 should work autom "fast" in 1 Pass :
"For all encodes, regardless of preset or not, using --pass 1 will automatically trigger "turbo" settings....."

But for some reason i get only half FPS/Perfomance in 1 Pass when using your gui in 2 pass Mode ?
Its as slow as with --slow-firstpass but i havent set it to --slow-first pass.

[LoRd_MuldeR]

i like your Build :)

Can you add 1 Pass Options please ? I use different lowered Settings in 1st Pass.

What more than 1-Pass CRF and 1-Pass CQP do you need? For bitrate-based encodes you really should use 2-Pass mode!

[ACrowley]

What more than 1-Pass CRF and 1-Pass CQP do you need? For bitrate-based encodes you really should use 2-Pass mode!

im talking about 2pass VBR! And the 1st Pass is very slow

The gui sets x264 to use same Paramerets for both passes...so 1 pass is very slow

[LoRd_MuldeR]

im talking about 2pass VBR! And the 1st Pass is very slow

2-Pass is always VBR. It can be constrained via VBV though.

The gui sets x264 to use same Paramerets for both passes...so 1 pass is very slow

Wrong. Unless you explicitly pass "--slow-firstpass", which my GUI definitely does not do, x264 will automatically run the first pass with "turbo" settings.

So it's perfectly fine to pass the same settings for both passes and let x264 decide which settings can be lowered during the first one ;)

Of course it's up to you. You can always add the "--slow-firstpass" parameter to the "Advanced Options" edit box, if you really want a SLOW first pass.

[ACrowley]

2-Pass is always VBR. It can be constrained via VBV though.



Wrong. Unless you explicitly pass "--slow-firstpass", which my GUI definitely does not do, x264 will automatically run the first pass with "turbo" settings.

So it's perfectly fine to pass the same settings for both passes and let x264 decide which settings can be lowered during the first one ;)

Of course it's up to you. You can always add the "--slow-firstpass" parameter to the "Advanced Options" edit box, if you really want a SLOW first pass.
I understand. But why do i get only ~4,5fps in 1 pass with your Gui ?
With all other guis or via cmdline i get ~15fps with the same Settings/Source ?

Log : ( from 500 frames sample, but its the same Speed with the Full Source)

[First Pass]
encoded 501 frames, 4.79 fps, 14969.11 kb/s

[Second Pass]
encoded 501 frames, 2.40 fps, 15057.99 kb/s


-- [Detailed Report] --

Source: F:\test.avs
Output: F:\encode.mkv
Preset: Veryslow
Tuning: Grain
Profile: High
Params: --level 4.1 --deblock -3:-3 --ref 5 --vbv-bufsize 30000 --vbv-maxrate 40000 --no-dct-decimate --no-fast-pskip --partitions p8x8,b8x8,i4x4,i8x8 --me umh --subme 9

Analayzing source file:
F:\test.avs: 1920x816, 48000/2002 fps, 501 frames

Resolution: 1920 x 816
Frame No. : 501
Frame Rate: 24000/1001

x264 0.76.1271 496d79d
built by Komisar on Sep 25 2009, gcc: 4.4.1 (x86_64.core2.Komisar)
Revision: 1271

Commandline for x264:
"C:\AV Tools\x264 Launcher\pipebuf.exe" "C:\AV Tools\x264 Launcher\avs2yuv.exe" F:\test.avs -raw - : "C:\AV Tools\x264 Launcher\x264_x64.exe" --preset veryslow --tune grain --bitrate 14800 --pass 2 --stats F:\encode.mkv.x264-stats --level 4.1 --deblock -3:-3 --ref 5 --vbv-bufsize 30000 --vbv-maxrate 40000 --no-dct-decimate --no-fast-pskip --partitions p8x8,b8x8,i4x4,i8x8 --me umh --subme 9 --output F:\encode.mkv --frames 501 --fps 24000/1001 - 1920x816 : 4

x264 [info]: 1920x816 @ 23.98 fps
x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 Cache64
x264 [info]: profile High, level 4.1
F:\test.avs: 1920x816, 48000/2002 fps, 501 frames

x264 [info]: frame I:9 Avg QP:16.48 size:141729
x264 [info]: frame P:106 Avg QP:16.03 size: 95216
x264 [info]: frame B:386 Avg QP:16.25 size: 72442
x264 [info]: consecutive B-frames: 1.4% 0.4% 20.7% 11.4% 5.1% 23.2% 32.7% 3.3% 1.8%
x264 [info]: mb I I16..4: 44.3% 50.4% 5.3%
x264 [info]: mb P I16..4: 10.8% 12.5% 2.8% P16..4: 47.8% 16.2% 9.8% 0.0% 0.0% skip: 0.1%
x264 [info]: mb B I16..4: 4.2% 3.1% 0.6% B16..8: 52.1% 2.1% 3.6% direct:23.6% skip:10.6% L0:42.3% L1:40.1% BI:17.6%
x264 [info]: 8x8 transform intra:44.1% inter:28.5%
x264 [info]: direct mvs spatial:79.0% temporal:21.0%
x264 [info]: coded y,uvDC,uvAC intra: 98.3% 80.3% 70.4% inter: 60.7% 49.3% 15.4%
x264 [info]: i16 v,h,dc,p: 1% 1% 61% 36%
x264 [info]: i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 7% 6% 19% 10% 12% 11% 11% 11% 13%
x264 [info]: i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 6% 5% 13% 11% 14% 12% 13% 12% 15%
x264 [info]: ref P L0: 47.2% 21.8% 15.2% 8.9% 7.0%
x264 [info]: ref B L0: 67.7% 16.9% 9.9% 5.4%
x264 [info]: kb/s:15057.99
encoded 501 frames, 2.40 fps, 15057.99 kb/s

[LoRd_MuldeR]

I understand. But why do i get only ~4,5fps in 1 pass with your Gui ?
With all other guis or via cmdline i get ~15fps with the same Settings/Source ?

It is technically impossible to get different speed with my GUI compared to other GUI's, unless you are either using a different x264 binary or passing other parameters to x264 ;)

But if you don't trust the GUI, copy the full command-line form the log window and run it manually from the command prompt...

[ACrowley]

It is technically impossible to get different speed with my GUI compared to other GUI's, unless you are either using a different x264 binary or passing other parameters to x264 ;)

But if you don't trust the GUI, copy the full command-line form the log window and run it manually from the command prompt...

As i say i use exactly the same Options!

But your gui use the x264 Build and other guis 32Bit rev 1281 thats the one and only difference

[LoRd_MuldeR]

As i say i use exactly the same Options!

Do you only select the same options in both GUI's or do both GUI's really pass identical parameters to x264? That's a difference!

But your gui use the x264 Build and other guis 32Bit rev 1281 thats the one and only difference

That's definitely something you should investigate. Exchange the builds and try again ;)

[ACrowley]

Do you only select the same options in both GUI's or do both GUI's really pass identical parameters to x264? That's a difference!
That's definitely something you should investigate. Exchange the builds and try again ;)
ofcourse..im not stupid.
--preset veryslow --tune grain --bitrate 14800 --level 4.1 --deblock -3:-3 --ref 5 --vbv-bufsize 30000 --vbv-maxrate 40000 --no-dct-decimate --no-fast-pskip --partitions p8x8,b8x8,i4x4,i8x8 --me umh --subme 9

obviously theres something wrong:)...but it works with all other x264 guis/cmdline.

I use x264 rev1281 32Bit (tested with megui/Staxrip/Ripbot,x264.exe) and rev1281 x64 in your gui

everytime 14,96fps in 1pass and 4,79fps with your gui

Can somebody reproduce it ?

[dstln]

Post the log from the other gui.

[Keiyakusha]

ACrowley
Note, that megui's "turbo" first pass probably uses different settings than 1st pass in x264. But I'm not using megui since I found Simple x264 Launcher so I'm not sure what settings MeGui uses now.

[LoRd_MuldeR]

Updated x264 to r1281 (JEEB's builds). Download link in first post updated!

[ACrowley]

ACrowley
Note, that megui's "turbo" first pass probably uses different settings than 1st pass in x264. But I'm not using megui since I found Simple x264 Launcher so I'm not sure what settings MeGui uses now.

as i say i use exactly the same cmdline everytime,also i dont use megui anymore!
Same 1 pass Perfomance with x264.exe via cmdline too since years.
But not with this launcher....i dont know why, strange. Theres something wrong

It looks like the placebo preset in 1pass where the turbo is disabled. I get 4-4fps with placebo in 1 pass too...

But i use the preset very slow ...and the launchers log shows the correct cmdline.

I really want to know Results from other Users. Please can someone test the 2 pass VBR Mode with the same cmdline with this gui ?

Preset: Veryslow
Tuning: Grain
Profile: High
Params: --level 4.1 --deblock -3:-3 --ref 5 --vbv-bufsize 30000 --vbv-maxrate 40000 --no-dct-decimate --no-fast-pskip --partitions p8x8,b8x8,i4x4,i8x8 --me umh --subme 9

Perhaps somebody can reproduce it...im sure its not my fault.

EDIT:
It works:) 1 pass fps are normal now. I changed nothing but x264 to latest rev1281 techhouse. Same cmdline/Source/AvS as above
However, its strange.In Fact i hade same Perfomance with the older Build via x264.exe. There was something confused here. But now its fine.

By the Way, a autom creation of the output logf Feature woule be nice ? Ofcourse i can manually copy it to clipboard, sure

[ACrowley]

Another Question :)

How can i delete all the old cmdline in the custom cmd scrooll down list ? The List is dozens of entrys long filled with every single cmdline ive used with the gui.

[LoRd_MuldeR]

AHow can i delete all the old cmdline in the custom cmd scrooll down list ? The List is dozens of entrys long filled with every single cmdline ive used with the gui.

Not exactly. It only shows the last eight parameters used and it only adds a new item to the list, if the current parameters are different from the previous ones!
This way you don't end up with a bunch of identical items in your history list, if you run several encodes with the very same parameters...

Anyway, you can simply delete all the "history_n" entries in your "%APPDATA%\x264_x64.ini" file or rename/move/delete the entire file, if that makes you feel better :p