How to detect hyperdecks on the network (without SDK)

Ask software engineering and SDK questions for developers working on Mac OS X, Windows or Linux.
  • Author
  • Message
Offline

agraham

  • Posts: 12
  • Joined: Sun Apr 07, 2019 10:15 pm
  • Real Name: Anthony Graham

How to detect hyperdecks on the network (without SDK)

PostThu Nov 10, 2022 9:29 am

Hi,

Is there a network broadcast / multicast message I can send / listen for to detect hyperdecks on the same network without the sdk if I just want to use the ethernet control protocol and not the full sdk?

I can do everything I need with the ethernet control protocol except find the devices. I'm guessing there's something but can't find documentation on it.

Thanks
Offline

lathoub

  • Posts: 4
  • Joined: Sun Nov 20, 2022 2:53 pm
  • Real Name: Bart De Lathouwer

Re: How to detect hyperdecks on the network (without SDK)

PostSun Nov 20, 2022 2:55 pm

Hi
HyperDecks announce their ftp service using Bonjour (so look for _ftp._tcp)
Cheers
Lathoub
Offline

Ninakadin

  • Posts: 1
  • Joined: Mon Nov 21, 2022 12:54 pm
  • Real Name: Nina Menssen

Re: How to detect hyperdecks on the network (without SDK)

PostMon Nov 21, 2022 12:59 pm

Older HyperDecks (as well as all ATEM switchers) use Bonjour to broadcast their information.

Search for service "_blackmagic._tcp.".
Newer HyperDecks announce their information with the service "_bmd_blockcfg._tcp.".

You can check your devices on your network using a Bonjour browser, for macOS e.g. there is a free app called "Discovery".

Cheers,

Nina
Offline

lathoub

  • Posts: 4
  • Joined: Sun Nov 20, 2022 2:53 pm
  • Real Name: Bart De Lathouwer

Re: How to detect hyperdecks on the network (without SDK)

PostThu Nov 24, 2022 2:58 pm

Thanks Binakadin, did not know that!
_bmd_blockcfg._tcp. works like a charm

Lathoub
Offline

lathoub

  • Posts: 4
  • Joined: Sun Nov 20, 2022 2:53 pm
  • Real Name: Bart De Lathouwer

Re: How to detect hyperdecks on the network (without SDK)

PostSun May 19, 2024 11:16 am

I noticed a strange thing in the DDNS record.

When using _bmd_blockcfg._tcp
the HyperDeck Mini reports it listens on port 9977
When using _hyperdeck_ctrl._tcp
the HyperDeck Mini reports it listens on port 9993

I'm using the latest HyperDeck version 8.4

I believe that 9977 is the ATEM port and 9993 the HyperDeck port. So _bmd_blockcfg._tcp reports the wrong port - not?

Return to Software Developers

Who is online

Users browsing this forum: No registered users and 3 guests