[FFmpeg-user] Resolve (was Re: key frame)
Mark Filipak
markfilipak.imdb at gmail.com
Sat Jun 29 22:56:45 EEST 2024
On 29/06/2024 14.58, Carl Zwanzig wrote:
> On 6/28/2024 4:07 PM, Mark Filipak wrote:
>> I have to consider Blackmagic DaVinci Resolve to be a virus hub that is probably selling access to
>> my system through those ports to outside clients.
>
> You're welcome to consider it such, but that doesn't make it so.
>
>
> BMD is a rather old and respected company, if you're concerned about the open ports in their _free_
> software you're welcome not to use it. Or welcome to block those ports ...
I did. The program crashes on launch.
>... or to even ask BMD why they're open?
I did that. The support people don't know anything. They don't even know video.
> Right in some BMD notes for v19--
> Setting up Remote Monitoring over IP connections on the Resolve Clients
Outbound ports like that are fine. It's the inbound ports that had me concerned.
> [...]
> Firewall exceptions and appropriate port forwarding will need to be manually configured in order to
> use this mode. The procedure to initiate a session and accept connections remains the same. This
> mode uses TCP server port 16410 and TCP/UDP port 16411, 16412, etc. for each client.
>
> (Took me a only a few minutes to find that.)
>
> They also use some ports for collaboration and probably for license management; can't blame them for
> that, can we?
Outbound ports are fine. Inbound ports are not fine.
> Before quickly trashing some well-respected software, please do a little research.
I did. That's why I decided not to use it.
> z!
More information about the ffmpeg-user
mailing list