[Bouke Vahl]

[Anton Nordstrand] “1080×1080, 2 pass vbr 45-50”

here is (at least one of) your problems.
You render to a delivery codec, probably H264, we can’t know in probably 420, again, we can’t know.
So, you loose half your color resolution and get compression artefacts.
Now I don’t know the encoding software, but perhaps there is kicking in a scaler as well (that should not do that, just a crop.)

But, before posting here, did you spent an hour or so testing other encoders / codecs / settings like the rest of us does here to learn how it works and be able to answer questions like this?

Bouke
http://www.videotoolshed.com

[Bouke Vahl]

Render out as QT with alpha?
(That’s what I do for Avid, but with empty titles as no gaps is plain ugly.)

Bouke
http://www.videotoolshed.com

[Bouke Vahl]

If it is converted with a scale and that was not done interlace aware, the short answer is ‘no’.
(The long answer does not help you either.)

Bouke
http://www.videotoolshed.com

[Bouke Vahl]

[Jeremy Garchow] ”
Actually it’s the death of QuickTime and it’s 32 bit libraries.”

No death, that is not the issue, it’s the rise of the machines.

[Jeremy Garchow] “The QuickTime libraries are dead. Long live … I don’t know … 64 bit yadda yadda”

I do know: Long live the people who praise Newspeak.
(I’m in the resistance btw)

Bouke
http://www.videotoolshed.com

[Bouke Vahl]

I guess your stuttering has nothing to do with drive speed but with a lack of knowledge on interlacing and upscaling.
I suggest you have a look frame by frame / step field by field to see what is going on.
THen,
If you want to go from SD interlaced to 50p progressive, you do gain going from 25i to 50p, as you do not have to de-interlace that reduces sharpness.
BUT, you end up scaling one FIELD (app 690 pixels x 260 pixels after cropping to active area) to one HD frame (1920 x 1080)
So, even if you have the best upscaling algorithm, this WILL be very noticable, as you stretch the image 3 times horizontal, and 4 times vertical.

Bouke
http://www.videotoolshed.com

[Bouke Vahl]

No idea what happens, but with a speed change some frames will be affected, and you don’t know which ones.
Its easier / faster / better / no render to cut out or duplicate a frame here and there in places where you are sure the content won’t be used.

Bouke
http://www.videotoolshed.com

[Bouke Vahl]

I added a new text parser to Subbits, wasn’t that difficult.
(Note, it is not available in the public version yet, if you need to do tons more, let me know.)

Bouke
http://www.videotoolshed.com

[Bouke Vahl]

You yourself made a nice list of things Apple did that hurt you. Ok, your pleasure.

And if you think it is a very good idea to have everybody use a propiatary codec that is NOT free, and be paid by everyoe someday, or just disappear cause someone does not think that Apple should be downwards compatible (yes, that does happen, remember…), have fun.

I for one think that open source is the way to go.

And now I’m done with this. You are the FaceBook abb that is no longer allowed here, I am the opposite.

Bouke
http://www.videotoolshed.com

[Bouke Vahl]

Perhaps this might help…

Download link:
https://we.tl/t-XDlc09c3DV

Bouke
http://www.videotoolshed.com

[Bouke Vahl]

It is NOT similar to SRT.
Srt has milliseconds instead of frames, is tab delimited, has no duration and some more stuff.

This has TC in / out and duration, followed by the text. Probably this was outputted for proof reading / spellcheck. (That did not happen, as I found some mistakes I believe ☺

I’ve converted the file to SRT, assuming 25 fps speed.

Bouke
http://www.videotoolshed.com