otomad / om_midi Goto Github PK

这两天试用了一下，总体来说还是挺好用的吧，引入多轨，生成的轨道是带命名和根据midi截断的这一点挺让我印象深刻的，然后下面来点建议。

Recently used this script, pretty in all. Multiplied channels. named channel and just part of the track according to midi are really impressive add-ons. Followings are suggestions.

看密恐了 / Trypophobia lmao

面板实在是太大了
Too large the panel.

这个可以理解吧，毕竟功能确实是太多了，如果要手动加/删一些功能的话应该咋调？抱着好奇心开了一下发现代码跟毛线球一样...不知道用AE脚本专用的那个编辑器会不会好点。然后有些比较怪的子面板粘下面了希望看看是bug还是设计问题。

Understanding, so how could I edit the functions and keep those I need? Messy codes really disturb...If the special editor for AE Script could be better. And weird sub panels btw.

界面问题
Panel Problems

一些小小的疑问 / Questions

可能是专栏没提到或者是我看漏了，一些比较好奇的点就单独扔这问了。
Not mentioned or I just overlooked them, some curious points.

1. 关于变速 / About Varying BPM
   因为看到有个专门的BPM面板，比较好奇变速（即BPM通道包络）曲子的帧生成会不会异常（还没试过），比如严重的帧对不上的情况。
   Noticed an additional BPM input, I've never tried but curious about: will a midi file with BPM envelope be generated as a track comes up with problems such as fatal error on frames alignment.

2. 关于非对齐帧 / About generated frames' offset
   众所周知，AE的帧数对上曲速其实是一件很困难的事，要用60帧率去做BPM130/170/220或者其他偏的更离谱的是很常见的。在前面的一些版本中，这个偏移会导致更严重的问题，如异常的时间重映射和翻转动画等，不知道这一版改进了这个问题没。（因为我个人是用的表达式时间重映射回避掉了这个问题所以我可能用不到只是顺便问问w）
   As we all know, it's hard to let the frames align with the tempo for we always make otomads using 60fps + 130/170/220/etc. BPM. In preceding versions, the offset will lead to fatal errors on Time Remap and Mirroring animations. I wonder if the problem is fixed in this version. (However, I am using Expression-assisted Time Remap, so it never happened to me, just asked btw.)

TODO

A feature same as in Otomad Helper.

is there another way to put the script to ae 2021?

• Last selected tab
• Last selected check boxes
• Last mapping velocity
• Last selected tool

UST is UTAU and OpenUTAU's project file.