[Bouke Vahl]

No, just put:
I’ve studied English while i was in America.

If you translate to english, what’s the point of including Japanese characters in the subs?

Occasions where you do need tricks like this are in movies where people go back to slang / dialects / foreign languages intended NOT to understand by other people on screen.

But if someone is just making a point, make the same point in the target language.

Bouke

https://www.videotoolshed.com/
smart tools for video pros

[Bouke Vahl]

Few basic rules of sutbtitling:

You translate everything. If a single word is in the target language, pick it along or you won’t have a logic sentence.

You translate everything. Including all foul language. (that’s where you have to get creative and know you swear words)

You translate everything. That means also you need to know local habits. Some languages don’t use the word ‘no’, if you know the speaker means ‘no’ where he says ‘yes’, you translate with ‘no’.

You translate everything. That means you don’t explain, you translate in a way that the viewers know what is going on.

You DON’T translate everything, if that means the readspeed gets too high. In that case, you shorten so readspeed requirements are met.
(rule of thumb, speak out LOUD the translated sentence. If you can do so in the time the title is up, you’re save.
(Be afraid of things like double negative, as that takes huge human processing time!)

You NEVER EVER use color. It’s not CC, it’s not for deaf.
Color looks ugly/distracting.

And you don’t use more than two lines, and stick to less than 42 chararctes a line.

hth,

Bouke

https://www.videotoolshed.com/
smart tools for video pros

[Bouke Vahl]

To clarify, my original math was wrong, 100.1 is the correct number.
(as that is indeed a .1 % speed change)

But, in all cases:
If it works, don’t fix it…
I don’t know how your speedchange works, but as rule of thumb:
Speedchanges that involve sample rate correction use a pitch shift.
In your case, you want that.

To find out what kind of speedchange is used, watch the render time.
A speed change with SR conversion should be instant, while a speed change that tries to keep things intact takes time.

If in doubt, use an external util that gives you control over what you are doing.

hth,

Bouke

https://www.videotoolshed.com/
smart tools for video pros

[Bouke Vahl]

You’re totally right.
What i’ve tried to say that a speedchange of 0.1 %, not 1 %
100.1 is indeed 0.1 percent more than 100…

My bad, sorry.

Bouke

https://www.videotoolshed.com/
smart tools for video pros

[Bouke Vahl]

as high as you have light, and as high as you visually accept.
(High shutter speeds result in a ‘strobing’ movement.)

Bouke

https://www.videotoolshed.com/
smart tools for video pros

[Bouke Vahl]

Rafael is right, but you also might kick him to fix his system.
(that would be my option)

Bouke

https://www.videotoolshed.com/
smart tools for video pros

[Bouke Vahl]

Or, (my way of doing this)
Make a chroma key on your keycolor (red in your case), inverse the matte and use a desaturated version of the clip as background.

Bouke

https://www.videotoolshed.com/
smart tools for video pros

[Bouke Vahl]

I don’t get what you are describing.

Do you have TC on the audio or not? (BWF or QT audio only)
If so, it ‘should’ be doable, but if there is no reference at all…

Please try to describe more in depth what you have.
(i don’t get what you mean by take / clip)

Bouke

https://www.videotoolshed.com/
smart tools for video pros

[Bouke Vahl]

precisely NOT.
Interlacing in a digital file, you get the ‘artefacts’ where the OP was complaining about.

And now i’m tired of this discussion, as it jumps all over the place.

Peace out,

Bouke

https://www.videotoolshed.com/
smart tools for video pros

[Bouke Vahl]

well, yes. This is what i was saying…

What my question / our difference was:
You stated that not all displays can show progressive, while i stated that not all displays can show interlaced correctly…

Bouke

https://www.videotoolshed.com/
smart tools for video pros