Yes, there is!
First you verify that the file is really 64 bytes long, and that the first 32 bytes of the file are really "== ed25519v1-public: type0 ==\0\0\0".
Having done that, you base64-encode the second 32 bytes of the file, with no "=" padding.
thank you for this description, so I can confirm that this:
cut -b 33- ed25519_master_id_public_key |base64
gives me the same string as in the file fingerprint-ed25519
kind regards, nusenu