A tool to join, split or fix subtitle files., Version 1.0, Size: 32,854 bytes.
CRC32/MD5 codes: D4174FA3/0F4B2DD81FE0B20667875256501F2E52.
This is tested and known to work on all 32-bit versions of Windows.
Operation in Win64, and Wine under Linux, has not been tested, but it may work.

If you're reading this, you already know why you might want it, so I won't say much. The pictures will make it clear enough.

What I must say is that VOBSUB can't handle SRT files. This can. Actually, VOBSUB in one case I tried, failed to handle its own format without huge sync errors! I couldn't even find a tool to use with SRT files, so at that point I knew I had to make my own, or do without.

I was determined to join all my files to avoid interruptions while watching them. There's little point now in forcing files into CD-sized chunks when it's better to use old hard disks to store them because if done carefully, this has a longer lifetime than DVD, CD or Flash storage.

Between VirtualDubMod and this tool, I have fixed enough files to know this tool is solid (it even fixed the VOBSUB files that VOBSUB couldn't fix), so now I make it available to you.




Assuming the tool got passed the correct command line arguments, it will output the data intended. It will put it into the current working directory, usually the desktop if not otherwise specified. The data preserves all internal timestamp and file offset references as cleanly as in the original sources, adjusting as required. If the user-supplied timestamp is correct, the output will be correct. Input files are never modified. If by some co-incidence an input filename matches the default output name, the tool will not overwrite the file. Try on some test copies first, just so you know it's safe.

This tool can join more than two parts. While it can only use two at once, you can call it to append any extras if you know the resulting timestamp needed after joining the first. Likewise, it can split a very large file into multiple parts the same way. I could have made the tool more complicated, but this is unwise. It's better to keep it simple to minimise the risk of error.

The only thing left to say is that this tool was built using the language Lua (developed in the university in Rio, Brazil), using Luac to prepare a separate executable file that runs independently of any Lua installation. When I have prepared the system that built this, I will put that online too, and replace this sentence with a link to it. I think people should be willing and able to make their own tools, so if I can make that easier, I do it.