Random Observation of Metadata & Timecode Burn-In Effect

This effect was brought to my attention today, decided to check it out. Likely won't have to use it much myself, but I can see this being handy for tons of folks: A more expanded version of the TC generator, very nice!

That said, one thing I recalled about the current TC generator isthat... it isn't very great at generating timecode, and I noticed this new beta effect still has the same issue. I specifically am referring to timecode conversions, and how it handles it (or the lack thereof).

When selecting timebases other than the source timebase, it doesn't do any calculations or conversions, it just changes the target frame # at to which increment the seconds counter, resulting in differing real time values. (iex 00;00;10;15 in 29.97 DF is 00:00:13:03 in 23.976 as opposed to 00:00:10:12.). I guess it's just doing [Raw Frame #] / [Timebase Choice] = Timecode.

Just figured I'd mention it, could be something useful for someone one day if corrected! Or maybe I'm missing something and it's purposely done this way. Anyways, that's all!