Threaded Mode | Linear Mode

simoncn · 05-04-2013, 17:53

(05-04-2013 17:45)Holzohr Wrote: Thanks for the quick reply! I have installed WireShark and MinimServer on my PC. Oppo is scanning for media servers now. How to send you the capture file?

PM sent. Many thanks!

simoncn · 06-04-2013, 20:18

(05-04-2013 16:49)Holzohr Wrote: Hello Simon, is there any progress? I have the same problem with my Oppo 103, can not see the MinimServer in my network. I have installed the server on my DiskStation 110j successfully and can browse through the music files via smartphone/tablet with BubbleUPnP and also Kinsky.

The current Beta-Firmware lets the Oppo 103/105 play DSD-files from local or network storage. Therefore I would like to try the MinimServer.

Thanks in advance.
Regards

(another) Mario

With a lot of help from Mario, I've identified the cause of the problem with MinimServer not being found by the OPPO. It will be fixed in the next release.

diddle · (This post was last modified: 19-04-2013 11:24 by diddle.)

Hi Simon,

just started testing MinimServer... and it looks quite promising. Thank's at lot for this excellent work.

However, I'm hitting similar issues with your brand new 0.71 as discussed in this thread. I'm using BubbleUPnP (latest 1.6.7.1) as control point... and browsing MinimServer works perfectly fine, but I'm unable to play anything.

With my Onkyo TX-NR616 as renderer I receive the "Resource not found (code 716)" error, but also with BubbleUPNP's local renderer playing does not work.

The minidlna running in parallel on the same content on the same (Linux x86) server works just fine... so this seems to be an MinimServer issue. Should be reproducible alone with BubbleUPnP easily. At least here it is on 2 android phones and a Nexus7 tablet. Smile

Are the fixes discussed in this thread already supposed to be implemented in 0.71?

Best regards
Diddle.

simoncn · 19-04-2013, 11:24

(19-04-2013 11:18)diddle Wrote: Hi Simon,

just started testing MinimServer... and it looks quite promising. Thank's at lot for this excellent work.

However, I'm hitting similar issues with your brand new 0.71 as discussed in this thread. I'm using BubbleUPnP (latest 1.6.7.1) as control point... and browsing MinimServer works perfectly fine, but I'm unable to play anything.

With my Onkyo TX-SR607 as renderer I receive the "Resource not found (code 716)" error, but also with BubbleUPNP's local renderer playing does not work.

The minidlna running in parallel on the same content on the same (Linux x86) server works just fine... so this seems to be an MinimServer issue. Should be reproducible alone with BubbleUPnP easily. At least here it is on 2 android phones and a Nexus7 tablet.

Are the fixes discussed in this thread already supposed to be implemented in 0.71?

Best regards
Diddle.

Yes, all these fixes are in 0.71. What type of file are you unable to play (format, resolution)? When I have these details, I'll try it on BubbleUPnP with my Nexus 7.

diddle · 19-04-2013, 11:29

(19-04-2013 11:24)simoncn Wrote: Yes, all these fixes are in 0.71. What type of file are you unable to play (format, resolution)? When I have these details, I'll try it on BubbleUPnP with my Nexus 7.

I tested with several MP3 music files, most of them quite standard CBR 192kbps/44.1kHz.

Best regards
Dietmar.

simoncn · 19-04-2013, 13:30

(19-04-2013 11:29)diddle Wrote: I tested with several MP3 music files, most of them quite standard CBR 192kbps/44.1kHz.

Best regards
Dietmar.

This is working for me when using BubbleUPnP to play to its local renderer. Do you have a firewall on your Linux x86 machine? If so, please try disabling it. By default, MinimServer uses port 9790 to play tracks, and you won't be able to play anything if this port is blocked by a firewall.

If this isn't the problem, please run a trace, as follows:

1) Start MinimServer
2) If your Linux x86 media server is headless, start MinimWatch
3) From the minim icon, select 'Show log'
4) In the log window, change the logging level to Trace
5) Leave the log window open
6) In BubbleUPnP, browse to a track and try to play it on the BubbleUPnP local renderer
7) In the log window, press 'Save as' to save the log data to a file
8) In the log window, change the logging level back to Info
9) Zip the log file and attach it here, together with the name of the track that failed to play

Many thanks!

diddle · 19-04-2013, 14:52

Hi Simon,

(19-04-2013 13:30)simoncn Wrote: This is working for me when using BubbleUPnP to play to its local renderer. Do you have a firewall on your Linux x86 machine? If so, please try disabling it. By default, MinimServer uses port 9790 to play tracks, and you won't be able to play anything if this port is blocked by a firewall.

thank's for the simple hint to look for port 9790. Although no firewall is active on my server, this looked strange:

# netstat -an |grep 9790
tcp6 0 0 :::9790 :::* LISTEN

Only listening on IPv6!

To change this I simply added to the start options in autostart.sh:

-Djava.net.preferIPv4Stack=true

An Bingo... works now. Smile

# netstat -an |grep 9790
tcp 0 0 0.0.0.0:9790 0.0.0.0:* LISTEN

Thank you again,
Diddle.

simoncn · 19-04-2013, 15:00

(19-04-2013 14:52)diddle Wrote: Only listening on IPv6!

To change this I simply added to the start options in autostart.sh:

-Djava.net.preferIPv4Stack=true

I've never seen this myself, and no other users have reported it. Which Linux distro and which version of Java are you using? I'd like to find out why Java is choosing IPv6 by default in preference to IPv4.

diddle · 19-04-2013, 15:06

Hi Simon,

(19-04-2013 15:00)simoncn Wrote: I've never seen this myself, and no other users have reported it. Which Linux distro and which version of Java are you using? I'd like to find out why Java is choosing IPv6 by default in preference to IPv4.

this is Debian Wheezy:
# java -version
java version "1.6.0_26"
Java™ SE Runtime Environment (build 1.6.0_26-b03)
Java HotSpot™ Client VM (build 20.1-b02, mixed mode, sharing)

However, this is standard behavior, see e.g.:
http://docs.oracle.com/javase/1.5.0/docs...pv6_guide/

"IPv6 stack is preferred by default, since on a dual-stack machine IPv6 socket can talk to both IPv4 and IPv6 peers."

Actually I really think, this is not a issue for you, but a problem I need to resolve here in my network... maybe my WiFi router is the culprit.

Best regards
Diddle.

simoncn · 19-04-2013, 15:29

(19-04-2013 15:06)diddle Wrote: Hi Simon,

this is Debian Wheezy:
# java -version
java version "1.6.0_26"
Java™ SE Runtime Environment (build 1.6.0_26-b03)
Java HotSpot™ Client VM (build 20.1-b02, mixed mode, sharing)

However, this is standard behavior, see e.g.:
http://docs.oracle.com/javase/1.5.0/docs...pv6_guide/

"IPv6 stack is preferred by default, since on a dual-stack machine IPv6 socket can talk to both IPv4 and IPv6 peers."

Actually I really think, this is not a issue for you, but a problem I need to resolve here in my network... maybe my WiFi router is the culprit.

Best regards
Diddle.

Thanks for the pointer. MinimServer is limited to IPv4 only because this is what the ohNet UPnP stack assumes. I'd therefore like to force Java to use IPv4 only, and it seems from this Java web page that setting the java.net.preferIPv4Stack property is the only way to do this.

I'm concerned about this because the property needs to be set externally to the MinimServer code (i.e., by the user). I don't want users to need to understand and deal with this, or to find their music won't play if they get this wrong.

I'll do some more searching to try to find a way to force this setting within the MinimServer code. If this isn't possible, perhaps I can detect that Java has chosen to use IPv6 and abort MinimServer with an error message.