

Works fine (other than the ones in question)Notice you have flac:wav24 set, ie transcode all flac files to 24 bit wav, which should not have produced the. Or, did you get CUETools to produce FLAC track files from the original FLAC and rely on MinimServer to transcode them to WAV, via its MinimStreamer transcoder, so with its anscode property set to 'flac:wav'?įlac:wav24, mp3:wav24, alac:wav24, aac:wav24 in 'stream transcode'. How have you done this? So:ĭid you either get CUETools to produce the WAV track files directly from the original downloaded FLAC? I do know that JPLAYStreamer can't actually stream & play FLAC files, so it needs something to convert them to WAV which it can stream. Does that mean you also can't even get Foobar to play those CUETools produced files? Are there any error messages being displayed on Foobar, especially in its Console view? You also mention 'using' the Foobar2000 music player application and it being the 'same as described previously'. So your problem then, is not acessing the files from MinimServer, but seemingly getting JPLAYStreamer to play them. Also all their tracks selectable from MinimServer's media library, appearing as they normally would to the Kazoo controller app, ready to get them to be streamed & played by JPLAYStreamer. I'm guessing then, that the CUETools produced files are actually being properly scanned by MinimServer and entered into its media library, especially as you say, with no mention of errors in the log. You mention using JPLAY music player software, so presumably you are using its built-in OpenHome supporting streamer, JPLAYStreamer, to stream the files from MinimServer and play them on the computer its running on, all being controlled by the Kazoo OpenHome controller app you also mention. FINAL_REJECT: IN=wlp3s0 OUT= MAC=3c:a9:f4:56:ee:8c:00:08:9b:c7:ec:72:08:00 SRC=192.168.169.130 DST= didn't actually directly answer my questions, so you are going to have to bear with me as I attempt to interpret things from your actual reply! However grabbing a section from the firewall log I have what is given dmesg | grep -i REJECT | grep -i 192.168.169.130 | grep -i 192.168.169.226 Retrying monitor subscription for server at 192.168.169.130:9791 (attempt 10)Ĭlearly port 9791 is being used, I think this is telling me that minimserver on 192.168.169.130 is sending on port 9791. Retrying monitor subscription for server at 192.168.169.130:9791 (attempt 9) Retrying monitor subscription for server at 192.168.169.130:9791 (attempt 8) Retrying monitor subscription for server at 192.168.169.130:9791 (attempt 7) Retrying monitor subscription for server at 192.168.169.130:9791 (attempt 6) Retrying monitor subscription for server at 192.168.169.130:9791 (attempt 5) Retrying monitor subscription for server at 192.168.169.130:9791 (attempt 4) Retrying monitor subscription for server at 192.168.169.130:9791 (attempt 3) Retrying monitor subscription for server at 192.168.169.130:9791 (attempt 2)

Retrying monitor subscription for server at 192.168.169.130:9791 (attempt 1) I have checked the minimwatch log and here is an extract from the log:.

I am still trying to work out which of the several packet ports which feature in my data grab might be relevant or used in my firewall. I am sorry I was less than precise by referring to "correct" port. I have now asked the NAS supplier and am trying to learn more. On the other hand looking at the firewall log it seems some form of dynamic port configuration is being used and I cannot find where or how this is set. In my ignorance I have captured a short extract from the firewall log, from which I conclude that minimserver is trying to talk to minimwatch on my laptop but traffic on Port 9791 is not getting through. Minimserver is running on a NAS and I am still trying to work out where the problem is. If MinimServer is running but MinimWatch 2 can't see MinimServer, check that you don't have a firewall blocking port udp/1900. As far as he is concerned the port should be set:. I did of course start with the application writer a while ago.
