Skip to content

Conversation

@rroohhh
Copy link
Member

@rroohhh rroohhh commented Nov 26, 2025

Then we can switch (more easily) to h264_videotoolbox on the mac worker.

@rroohhh rroohhh requested review from anuejn, pajowu and phlmn November 26, 2025 11:07
@anuejn
Copy link
Member

anuejn commented Nov 26, 2025

I dont really understand just from the code how this would be used. Where is data["REENCODE_VIDEO_CODEC"] coming from?

@phlmn
Copy link
Member

phlmn commented Nov 26, 2025

Then we can switch (more easily) to h264_videotoolbox on the mac worker.

Is this a good idea? Encoding is already pretty fast and h264_videotoolbox is a bit crappy (e.g. it does not support crf)...

@rroohhh
Copy link
Member Author

rroohhh commented Nov 26, 2025

I dont really understand just from the code how this would be used. Where is data["REENCODE_VIDEO_CODEC"] coming from?

From the line above REENCODE_PROFILES. That way one can simply set REENCODE_VIDEO_CODEC as env var (instead of having to set the whole profiles via an env var.

Then we can switch (more easily) to h264_videotoolbox on the mac worker.

Is this a good idea? Encoding is already pretty fast and h264_videotoolbox is a bit crappy (e.g. it does not support crf)...

Well, good question. Somehow its just strictly slower using videotoolbox (which does by now support constant quality coding using q:v btw). So I guess it would not make any sense to move to videotoolbox.

@rroohhh rroohhh closed this Nov 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants