Home of the Squeezebox™ & Transporter® network music players.
Page 39 of 39 FirstFirst ... 29373839
Results 381 to 385 of 385
  1. #381
    Senior Member
    Join Date
    Oct 2005
    Location
    Ireland
    Posts
    15,487
    I think keep this thread to the use of Net::UDAP - otherwise this digression will fill it.

  2. #382
    Senior Member Julf's Avatar
    Join Date
    Dec 2010
    Posts
    2,463
    Quote Originally Posted by bpa View Post
    I think keep this thread to the use of Net::UDAP - otherwise this digression will fill it.
    Indeed. There is an "audiophile" subforum for discussing imagined improvements in sound quality.
    "To try to judge the real from the false will always be hard. In this fast-growing art of 'high fidelity' the quackery will bear a solid gilt edge that will fool many people" - Paul W Klipsch, 1953

  3. #383
    Junior Member
    Join Date
    Aug 2017
    Posts
    1
    Hi, I am on windows 10 and have troubles getting the udap_shell.pl running , so I used the udap_shell_1_0_0 exe that was posted earlier in this thread.

    My squeezebox duet receiver works with wpa2 and plays the music, but when the server is turned off, the receiver also stops (the light indicator is off) and when the server is turned back on, the receiver stays off.
    My Squeezebox boom does not have this problem, but the duet receiver does not seem to see that the server is running again.

    So when I wake up and turn on the squeezebox server, I open the udap_shell exe on my laptop and tell the receiver to reset and then it works.
    Does anybody know what I can do to make sure that I don't have to reset the receiver every time the server is turned on?

    Thank you very much!

  4. #384
    Senior Member dolodobendan's Avatar
    Join Date
    Dec 2017
    Location
    Braunschweig, Germany
    Posts
    105
    Quote Originally Posted by Julf View Post
    Indeed. There is an "audiophile" subforum for discussing imagined improvements in sound quality.
    Great, there I can tell the world about how my newly acquired iridium plated remote control improved the sound of my USB headphones!

    And back to Net::UDAP.

    Code:
    UDAP> discover
    info: *** Broadcasting adv_discovery message to MAC address 00:00:00:00:00:00 on 255.255.255.255
    Use of uninitialized value in length at /PerlApp/Net/UDAP/Util.pm line 57, <FIN> line 1.
    Use of uninitialized value in length at /PerlApp/Net/UDAP/Util.pm line 67, <FIN> line 1.
    Supplied string has length0(expected length: 6) at /PerlApp/Net/UDAP.pm line 296
    Use of uninitialized value in concatenation (.) or string at /PerlApp/Net/UDAP.pm line 297, <FIN> line 1.
    info:   adv_discovery response received from
    Use of uninitialized value in length at /PerlApp/Net/UDAP/Util.pm line 57, <FIN> line 1.
    Use of uninitialized value in length at /PerlApp/Net/UDAP/Util.pm line 67, <FIN> line 1.
    Supplied string has length0(expected length: 6) at /PerlApp/Net/UDAP.pm line 358
    mac not found in msg at /PerlApp/Net/UDAP/Shell.pm line 156
    Anyone else got this with udap_shell_1_0_0.exe? (And maybe even has a solution?)

    Edit:

    My bad, this has been asked before and a solution was posted

    (http://forums.slimdevices.com/showth...l=1#post501429)

    I got it to work using this:

    https://github.com/robinbowes/net-udap/tree/1.0.x

    And a direct connection between my PC (first ethernet port) and the receiver.
    Last edited by dolodobendan; 2018-01-02 at 10:25.
    LMS 7.9.1@1.05 (digimaster) / QNAP 469L QTS 4.3.4

  5. #385
    Senior Member dolodobendan's Avatar
    Join Date
    Dec 2017
    Location
    Braunschweig, Germany
    Posts
    105
    Quote Originally Posted by Thomas8675309 View Post
    Then I followed the general instructions here:

    http://www.practicalreason.net/item/...out-controller
    Whoever wrote this mixed up local and receiver's IP, but since he was consistent in his misuse, it should work (if it is works at all), despite stuff like:

    Open a command window and get the IP address of the Squeezebox Receiver using the following DOS command:

    Code:
    ipconfig /all
    Here you should find a section Autoconfiguration IPv4 Address which will list the IP address assigned to the device connected on the ethernet port. See the highlighted line above for an example - you can see how the IP address of the Receiver is 192.168.1.4.

    To get the Net::UDAP application to connect to the Squeezebox Receiver you need to run its udap_shell.pl script and specify the IP address of the Receiver you determined in the previous section.
    LMS 7.9.1@1.05 (digimaster) / QNAP 469L QTS 4.3.4

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •