Server crashes when trying to play file casted to it from another device

[PureTryOut]

I can cast a file when having both server and client on the same machine just fine, but doing the same with the server on another device currently crashes both the server and client (also I don't see how castFile() in the library is supposed to cast the file to the server anyway, as far as I can see it's just giving it a filename. How is the file actually supposed to get to the server?).

Server:

EOF is 0
PB error, checking autoexit.
Goto 'fail'. Exiting main loop...
SetDuration. 0
Closing audio stream component...
Closing audio device...
Terminating player...
: Invalid data found when processing input
Opening stream failed. Safe exit...
Goto 'fail'. Exiting main loop...
SetDuration. 0
fish: Job 1, 'nymphcast_server -c /etc/nymphc…' terminated by signal SIGSEGV (Address boundary error)

Client (nymphcast-player):

Media Read callback function called.
Status: Set playing...
Read block with size 32000 bytes.
5 - 100482.0    NymphListener   133     Adding request for message ID: 401.             - src/nymph_listener.cpp
2 - 100482.0    NymphListener   139     Handle 0 not found. Dropping message ID 401             - src/nymph_listener.cpp
Error calling remote method: Failed to send message: Broken pipe
terminate called after throwing an instance of 'Poco::SystemException'
  what():  System exception
fish: Job 1, 'nymphcast-player' terminated by signal SIGABRT (Abort)

[MayaPosch]

This is with both client and server on Alpine Linux systems? I assume nymphcast-player is the custom client using C API of libnymphcast?

As for how the file gets to the server, the client reads them in chunks and transfers these to the server via NymphRPC calls.

[PureTryOut]

The server is Alpine Linux, the player (nymphcast-player) is the example player from this repository also running on Alpine Linux.
I haven't tried this with my custom client yet.

As for how the file gets to the server, the client reads them in chunks and transfers these to the server via NymphRPC calls.

Sure, but how do I tell the library where the file is. Is it just a full path to the file? The current API suggests to me it just needs a filename which seems weird.

[MayaPosch]

For the basic CLI client the path to the file is provided with the -f flag. For the library the same path is provided to the castFile() function. This opens that file locally for reading. So yes, it's literally just a full, or relative path to the file in question.

[MayaPosch]

Confirmed server crashes when casting to it on current revision, happening on Win10, MinGW. Stand by for updates/a fix :)

[MayaPosch]

I fixed one issue with setting up the audio filter graph that may or may not be the same as what you encountered. It appears that FFmpeg 8.x has been changing things around again...

Please retest and see whether this fixed your problems :)