TCAX 的历史（英文+谷歌机翻中文）

Part One

At the very beginning (in the summer of 2008), I wrote karaoke FXs all by hand, which was bloody complicated (amaXsora taught me how to timing ASS files and create some simple effects). After a few months’ study of writing ASS by means of programming with the help of scf2 and small, I then wrote a very simple python module (in the autumn) which could help me create more awesome karaoke FXs, however it was a little dull and I still had to do many tasks manually. So I called it semi-automatic ASS FX generator (which was also named milkyjing.pyc v0.1, rather than calling it a generator, maybe we’d better call it a helper). Although I could create better FXs using that tool, it seemed that actually I spent more time on doing something very rigid. This situation didn’t improve until I met 卜卜猪 the guy who told me the mind of fully automation. As soon as I got that idea, I continued improving my little python module resulting in the NOT very well-known milkyjing.pyc (I called this one fully-automatic ASS FX generator, I remembered it was winter that time), besides me it was also used by Soleilの艾. I believed milkyjing.pyc could be used by anyone who had somebasic knowledge of programming and a great love of karaoke FX. But I knew there were many karaoke FXers wanted to create some complex yet awesome effects such as particle effects including pixelate text effects etc, which were all no easy tasks. For some of them, to learn programming (or, say, to learn how to use helpers such as milkyjing.pyc or some other similar ones, like 7*3’s pawaa_xd.pyc, small’s small_code.pyc etc, or even the popular Aegisub automation, Lua, overLua etc.) was also a hard work. So I decided to develop a tool with GUI for creating karaoke FXs with only simple configurations so that users who might not have the knowledge of programming or even a whole understanding of ASS could still use it to generate cool FXs. Plausibly, there were two basic requirements:

1. It must be easy to use

2. It must be flexible and extensible (i.e. many different effects could be generated from it).

With these in mind I started the TCSub project immediately (in the late March of 2009)…

Part Two

This part will be relatively briefer, since I couldn’t remember the events clearly due to poor documentation.

At first I planned to compile all the already made FX templates into the only one GUI. This could bring great simplicity for the users, as their task was no more than setting the style for the ASS and making some simple configurations. But the flexibility was poor, since all the effects were compiled, hence the kinds of effects were very limited, moreover, it was never easy to write many built-in effects, especially in C/C++. Anyway, I got to the first milestone TCSub_ver.0.5.7.3_Full (late April of 2009). But it was no more than a Demo.

Later, I found a way to use python in C/C++ and vice versa (such technique is called scripting). So I decided to add python compatibility to TCSub, and achieved the only one public distributed version of TCSub v1.0 (in the November). It still contained some built-in FXs written in C/C++. However its practical applicability required the basic knowledge of programming with python. And users could write their own FX script through python interface, working alone or together with build-in ones.

Gradually, I found it was almost useless to have compiled built-in FXs, and should better use ‘built-in’ python scripts instead (the reason was that it was much easier to write FX scripts by python rather than C/C++, yet still having the same effect and gaining much more flexibility). With some updates, the final version (not functionally, but terminated) came out, TCSub_1.9.1.8 (early March of 2010). I also developed a brand new file format for storing karaoke FX. It was called TCS. At that time, I just played with it myself, and left it undocumented for it being far away from practical use.

Part Three

I stopped working on the project for months, and did not restart until the beginning of summer holiday. I found that I coded more on the GUI than on the core modules. This made me frustrated, and I had to admit it was inefficient to build a GUI using WIN32 and C/C++ programming. So I divided the core modules together with a console user interface from the old TCSub project and named the new one Teco, which was an open source project whose most modules were licensed under GPL v2. I then worked on Teco continuously, until the last usable version of tcx came out. Though the Teco project was no longer maintained, you could still check out the legacy code and try tcx_demo (late September of 2010) with some examples.

Note

1. The name of TCSub came after a fansub I once organized, its full name was Ternary Color Fansub.

2. In the later works, TC will always be short for Ternary Color.

Acknowledgement

小逆, 琉香, 泪烬缘散, saiyaku

Special Thanks

MeteorX

p.s. Thanks to all the nice guys & girls I mentioned above, you really helped me a lot 😃

Download Links (Deprecated, use TCAX instead):

milkyjing.pyc

TCSub_ver.0.5.7.3_Full

TCSub v1.0

TCSub_1.9.1.8

tcx_demo

examples

【以下为上述内容的谷歌机翻】

第一部分

一开始（2008 年夏天），我都是手工编写卡拉 OK FX，这非常复杂（amaXsora 教我如何对 ASS 文件进行计时并创建一些简单的效果）。经过几个月的学习，在scf2和small的帮助下通过编程的方式写ASS，然后我写了一个非常简单的python模块（在秋天），可以帮助我创建更多很棒的卡拉OK FX，但是有点乏味而且我仍然必须手动完成许多任务。所以我叫它半自动ASS FX生成器（也叫milkyjing.pyc v0.1，与其说是生成器，不如说是帮手）。虽然我可以使用该工具创建更好的 FX，但实际上我花了更多时间做一些非常严格的事情。这种情况没有 直到我遇到了告诉我全自动化思想的家伙卜卜猪。一旦我有了这个想法，我就继续改进我的小 python 模块，从而产生了不是很出名的 Milkyjing.pyc（我称这个为全自动 ASS FX 生成器，我记得当时是冬天），除了我之外Soleilの艾也使用过。我相信milkyjing.pyc 可以被任何有一些编程基础知识和非常喜欢卡拉OK FX 的人使用。但我知道有很多卡拉 OK FXers 想要创建一些复杂但很棒的效果，例如粒子效果，包括像素化文本效果等，这些都不是一件容易的事。对于他们中的一些人来说，学习编程（或者说，学习如何使用诸如milkyjing.pyc或其他类似的帮助程序，如7*3的pawaa_xd.pyc、small的small_code.pyc等，甚至流行的 Aegisub 自动化、Lua、overLua 等）也是一项艰巨的工作。所以我决定开发一个带有 GUI 的工具，用于创建仅具有简单配置的卡拉 OK FX，以便可能没有编程知识甚至对 ASS 没有完全了解的用户仍然可以使用它来生成很酷的 FX。似乎有两个基本要求：

1. 它必须易于使用

2. 它必须具有灵活性和可扩展性（即可以从中产生许多不同的效果）。

考虑到这些，我立即开始了 TCSub 项目（在 2009 年 3 月下旬）…

第二部分

这部分将相对简短，因为由于文档不佳，我无法清楚地记住这些事件。

起初我打算将所有已经制作好的 FX 模板编译到唯一的一个 GUI 中。这可以为用户带来极大的简单性，因为他们的任务只不过是为 ASS 设置样式并进行一些简单的配置。但是灵活性很差，因为所有的效果都是编译的，所以效果的种类非常有限，而且编写很多内置的效果从来都不是一件容易的事，尤其是在C/C++中。无论如何，我达到了第一个里程碑 TCSub_ver.0.5.7.3_Full（2009 年 4 月下旬）。但它只不过是一个演示。

后来，我找到了一种在 C/C++ 中使用 python 的方法，反之亦然（这种技术称为脚本）。所以我决定在TCSub中加入python兼容性，并实现了TCSub v1.0的唯一一个公共分布式版本（11月）。它仍然包含一些用 C/C++ 编写的内置 FX。然而，它的实际适用性需要使用 python 编程的基本知识。用户可以通过python接口编写自己的FX脚本，单独工作或与内置脚本一起工作。

渐渐地，我发现编译内置 FX 几乎没有用，最好使用“内置”python 脚本代替（原因是用 python 编写 FX 脚本比 C/C++ 容易得多，但是仍然具有相同的效果并获得更大的灵活性）。随着一些更新，最终版本（不是功能性的，而是终止的）出来了，TCSub_1.9.1.8（2010 年 3 月上旬）。我还开发了一种全新的文件格式来存储卡拉 OK FX。它被称为 TCS。当时我只是自己玩了一下，离实际使用还很远，没有记录下来。

第三部分

我停止了几个月的项目工作，直到暑假开始才重新开始。我发现我在 GUI 上编写的代码比在核心模块上编写的要多。这让我很沮丧，我不得不承认使用 WIN32 和 C/C++ 编程来构建 GUI 是低效的。因此，我将旧 TCSub 项目中的核心模块和控制台用户界面分开，并命名为新的 Teco，这是一个开源项目，其大部分模块都在 GPL v2 下获得许可。然后我一直在 Teco 上工作，直到最后一个可用的 tcx 版本问世。尽管 Teco 项目不再维护，但您仍然可以查看遗留代码并通过一些示例尝试 tcx_demo（2010 年 9 月下旬）。

笔记

1. TCSub的名字来源于我曾经组织的一个fansub，它的全名是Ternary Color Fansub。

2.在以后的作品中，TC将永远是Ternary Color的简称。

致谢

小逆，琉香，泪焰缘散，saiyaku

特别感谢

MeteorX

ps 感谢我上面提到的所有好男人和女孩，你们真的帮了我很多 😃

下载链接（已弃用，使用TCAX代替）：

milkyjing.pyc

TCSub_ver.0.5.7.3_Full

TCSub v1.0

TCSub_1.9.1.8

tcx_demo

examples