|
graph posted:https://x.com/FFmpeg/status/1775178803129602500 lol get hosed microsoft
|
# ¿ Apr 3, 2024 04:56 |
|
|
# ¿ May 17, 2024 08:31 |
|
rotor posted:if your support model is "maybe corporations will feel guilty and write me a check" then you are a loving idiot they asked for a support contract. i don't think that's unreasonable
|
# ¿ Apr 3, 2024 04:57 |
|
if the bug is "high priority" because ffmpeg is used "in a highly visible product at microsoft", microsoft should get someone on that and submit a patch
|
# ¿ Apr 3, 2024 05:05 |
|
rotor posted:i dont either, and msft said no well then their bug will be dealt with as all other bugs in ffmpeg are. considering they pissed off the main developers i think ms should really get someone to write a patch lol
|
# ¿ Apr 3, 2024 05:47 |
|
i mean, if they want priority bug fixes i don't think it's unreasonable that the ffmpeg team asked for a contract for that. since ms declined, it'll be dealt with as if anyone submitted it. and i don't think that's unfair either ms definitely has the resources for someone to patch ffmpeg to fix the issue too. so if it's that high priority, they should get someone they're already paying to fix it, and submit the patch to ffmpeg. that's how it's supposed to work and is fair enough imo
|
# ¿ Apr 3, 2024 06:38 |
|
that said i wonder what "high visibility" product they're talking about. maybe edge?
|
# ¿ Apr 3, 2024 06:40 |
|
fart simpson posted:it says right there in the ticket. it was some sort of captioning for teams meetings oh i didn't actually look at the ticket lol. my dns blocks t.co redirects
|
# ¿ Apr 3, 2024 06:43 |
|
why does teams need to convert subtitle formats anyway? if microsoft has full control over how teams works then they should just have it use the subtitle format they want it in to begin with
|
# ¿ Apr 3, 2024 06:53 |
|
Kazinsal posted:it's specifically about stuff that's been encoded using NTSC style line 608 closed captions being incidentally transmitted in a stream of SEI packets alongside the video, which sounds like it's being sent to each Teams client as a content sharing thing and not that something on the other end is generating normal captions on the fly who the gently caress is still using line 608 captions
|
# ¿ Apr 3, 2024 20:19 |
|
|
# ¿ May 17, 2024 08:31 |
|
Plorkyeran posted:atsc captions include eia-608 captions in addition to the newer textual ones because all digital video technologies just lump new layers on top of the previous era's standards yeah, i meant in software. it doesn't make any sense unless you have teams getting raw atsc input somehow luckily i don't use teams all that often so i don't know if it has that capability. i guess you could use a tv tuner input device, but i'd think if it does on-device conversion of mpeg-2 then the captions either get stripped or converted. if it's a stream dump like you'd get from a cable box via firewire then idk how it'd get to teams
|
# ¿ Apr 3, 2024 21:25 |