Home of the Squeezebox™ & Transporter® network music players.
Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 24
  1. #11
    Babelfish's Best Boy mherger's Avatar
    Join Date
    Apr 2005
    Location
    Switzerland
    Posts
    20,713

    Transporter won't play.

    > By the way, is there a special way to get access to:
    > svn.slimdevices.com/repos/slim/7.6/trunk/server/Changelog7.html


    http://htmlpreview.github.io/?https:...hangelog7.html

    But I believe you're wasting your time trying to chase a firmware issue.

  2. #12

    Transporter won't play but does everything else.

    I agree that it is probably not a firmware issue. I also see that the reset and xilinx reset do not clear out all previous settings. It is very possible that some setting is creating my issue and I was trying to revert to earlier firmware in hopes of returning to a clean slate.

    So far I have:
    • Factory reset (+) and xilinx reset (1) several time and in different orders.
    • Put LMS 7.5.5 on my PC so that I could revert to firmware 84. No luck with 84 nor with going back to 87.
    • Put SqueezeCenter 7.0.1 to 'update' the firmware to 37. No luck but observed that it puts Player Port Number to 26024 rather than expected 9000. Pushed some music from server: Correct title appeared on Transporter but time stuck at 0:00 while the server played from 0:00 to 0:08 and looped back continuously. At least the server seemed to also recognize something wrong.
    • Tried connecting to mysqueezebox.com, my own server on a Synology NAS, and my own server on my PC.
    • Tried digital input through RCA from a working Touch to see if it was the DAC. (Confirmed this setup by successfully doing the same with my working Transporter.)
    • Tried with and without the WiFi board. I generally use Ethernet if I can.
    • The three LED's on the motherboard are a constant red and the 4th LED blinks with remote inputs.
    • I see a lot of ground 'Test Points' on the motherboard but a few voltage 'Test Points.' At the big 5 hole points I got MCLK=3.292, 5V=5.01, -15=-15.05, +15=15.05. There are some little test points where I got 1V37=1.375 and 3v3=3.293, 3.298 & 3.3 at three spots. So I think that the power is healthy in general.
    • Just selected an internet radio station from mysqueezebox.com. The display on the Transporter said that the station was buffering. At the end of buffering the time stays at 0:00 and no sound.
    • Turned off and on the RSS News Ticker. It scrolls current news just fine. The RSS Plays!
    • I see that all the boards are Rohs compliant. For example, the change away from lead solder has put many TVs on the scrap heap from dendritic whiskers (usually Tin alloys,) which jump across tightly spaced PCB traces. (Lead is bad but the increase in electronics waste in all the landfills isn't good for the environment either.)



    I wrote to Johannes Franke and I agree with him that it seems like it could be a setting issue. However installing old firmware and playing with all of the settings I could find doesn't seem to help. With the display showing accurately what should be going on, could it be something electronic in some small localized area?
    1x Squeezebox Classic3, 1x Squeezebox Duet, 3x Squeezebox Controller, 1x Squeezebox Boom, 6x Squeezebox Touch, 5x Squeezebox Radio, 1x Transporters, 2x DOA Transporters, Logitech Media Server Version: 8.2.0, Synology NAS DS920+ Docker

  3. #13
    Senior Member
    Join Date
    Oct 2005
    Location
    Ireland
    Posts
    21,494
    IIRC The Transporter SE was launched after the Transporter when part for the haptic knob were no longer available.,

    The firmware was probably modified to allow for "missing" knob.
    The SE was launched around Dec 2011 so I'd suggest server software should be a minimum of 7.7.*

    Transporter display is generated wholly within server s/w - so if display is staying 0:00 it is because Transporter has not sent "OK" to LMS to send data.

    Enable logging of slimproto to see what is happening. Your descriptions seems very like the problem in https://forums.slimdevices.com/showt...er-Not-Playing

  4. #14
    Senior Member
    Join Date
    Oct 2005
    Location
    Ireland
    Posts
    21,494
    If you want to check hardware, I suggest get in contact with Joe (maybe PM JoeMuc2009) - he has been helping users repair Squeezebox devices and has good h/w knowledge of Transporter.
    https://joes-tech-blog.blogspot.com/...er-repair.html

  5. #15

    Transporter

    If Joe - JoeMuc2009 is Johannes Franke then I have already been in contact with him through his blog: https://joes-tech-blog.blogspot.com/...er-repair.html

    Thank you for the hint about the firmware 7.7. I will go see what I can find. I need to look up how to enable logging of slimproto to see what is happening. I'll go do that now.
    1x Squeezebox Classic3, 1x Squeezebox Duet, 3x Squeezebox Controller, 1x Squeezebox Boom, 6x Squeezebox Touch, 5x Squeezebox Radio, 1x Transporters, 2x DOA Transporters, Logitech Media Server Version: 8.2.0, Synology NAS DS920+ Docker

  6. #16

    Logging

    How do I do logging of slimproto? I have searched for it by several terms but I get a multitude of examples where it has been used but I have not been able to dig down to where the original instructions are.
    1x Squeezebox Classic3, 1x Squeezebox Duet, 3x Squeezebox Controller, 1x Squeezebox Boom, 6x Squeezebox Touch, 5x Squeezebox Radio, 1x Transporters, 2x DOA Transporters, Logitech Media Server Version: 8.2.0, Synology NAS DS920+ Docker

  7. #17
    Senior Member
    Join Date
    Jan 2010
    Location
    Hertfordshire
    Posts
    8,869
    Quote Originally Posted by Tom Sea View Post
    How do I do logging of slimproto? I have searched for it by several terms but I get a multitude of examples where it has been used but I have not been able to dig down to where the original instructions are.
    Go to LMS settings, then Advanced/Logging and find network.protocol.slimproto.

    Sent from my Pixel 3a using Tapatalk

  8. #18
    I found what you mean. At the top, for "Logging" what do I select?:
    • Please select log set...
    • Reset logging preferences
    • Internet Radio
    • Media Scanner
    • Server
    • Transcoder



    And lower down for "(network.protocol.slimproto) - SlimProto (Squeezebox/Transporter) Protocol" what do I select?:
    • Error:
    • Off
    • Fatal
    • Error
    • Warn
    • Info
    • Debug


    Also, how do I clear the log so that I can show only Transporter stuff and not everything since I reinstalled 8.2.0 and it scanned my music files? Is there a wiki for logging? I could not find it.
    1x Squeezebox Classic3, 1x Squeezebox Duet, 3x Squeezebox Controller, 1x Squeezebox Boom, 6x Squeezebox Touch, 5x Squeezebox Radio, 1x Transporters, 2x DOA Transporters, Logitech Media Server Version: 8.2.0, Synology NAS DS920+ Docker

  9. #19
    Senior Member
    Join Date
    Oct 2005
    Location
    Ireland
    Posts
    21,494
    Quote Originally Posted by Tom Sea View Post
    I found what you mean. At the top, for "Logging" what do I select?:
    • Please select log set...
    • Reset logging preferences
    • Internet Radio
    • Media Scanner
    • Server
    • Transcoder
    Ignore this - tehse are ways of setting a number of logging when looking at a class of problem.

    And lower down for "(network.protocol.slimproto) - SlimProto (Squeezebox/Transporter) Protocol" what do I select?:
    • Error:
    • Off
    • Fatal
    • Error
    • Warn
    • Info
    • Debug
    INFO will be adequate. Debug will be too verbose.


    With slimproto logging - make sure no other player is ON - otherwise there'll be lots of message regarding other players.

    Also, how do I clear the log so that I can show only Transporter stuff and not everything since I reinstalled 8.2.0 and it scanned my music files? Is there a wiki for logging? I could not find it.
    Delete server.log file. Best done when LMS is stopped.

    No wiki for logging - just too much to write down. Slimproto is documented in the WebGUI Help (bottom left) / Technical information / The Squeezebox Client protocol.

    You'll be looking at the STAT messages - logged as STMx (where x is a letter).

  10. #20

    Log?

    Here is what I think is the log people are talking about. I am more of a hardware guy.

    [22-01-27 22:33:15.2333] main::init (390) Starting Logitech Media Server (v8.2.0, 1627922070, Tue Aug 3 11:28:42 WEDT 2021) perl 5.014001 - MSWin32-x86-multi-thread
    [22-01-27 22:33:16.0295] Plugins::UPnPBridge::Squeeze2upnp::start (141) squeeze2upnp-win.exe not found
    [22-01-27 22:33:16.0350] Plugins::UPnPBridge::Plugin::initPlugin (76) $VAR1 = {
    'binArch' => 'MSWin32-x86-multi-thread',
    'fsType' => 'NTFS',
    'uid' => 'Tom',
    'osName' => 'Windows 10',
    'osArch' => 8664,
    'isWin6+' => 1,
    'os' => 'Windows'
    };
    [22-01-27 22:34:00.0027] Slim::Networking::Slimproto::_stat_handler (784) 00:04:20:10:19:35: STAT-STMt: fullness=0, output_fullness=-1, elapsed=0.000
    [22-01-27 22:34:00.0083] Slim::Networking::Slimproto::_stat_handler (784) 00:04:20:10:19:35: STAT-strm: fullness=0, output_fullness=-1, elapsed=0.000

    ...

    [22-01-27 22:34:40.0148] Slim::Networking::Slimproto::_stat_handler (784) 00:04:20:10:19:35: STAT-STMt: fullness=0, output_fullness=-1, elapsed=0.000
    [22-01-27 22:34:40.0156] Slim::Networking::Slimproto::_stat_handler (784) 00:04:20:10:19:35: STAT-strm: fullness=0, output_fullness=-1, elapsed=0.000
    [22-01-27 22:34:42.6963] Slim::Player::Squeezebox::stream (1049) strm-q
    [22-01-27 22:34:42.7132] Slim::Player::Squeezebox::stream_s (544) stream_s called: format: flc url: file:///C:/Users/Tom/Music/Loris%20Tjeknavorian/Borodin%3B%20Symphonies%20Nos.%201-3/02%20Loris%20Tjeknavorian%20-%20Symphony%20No.%201%20in%20E%20flat%20major%3B%2 0Scherzo%3B%20Prestissimo%3B%20Tr.flac
    [22-01-27 22:34:42.7135] Slim::Player::Squeezebox::stream_s (937) Using smart transition mode
    [22-01-27 22:34:42.7136] Slim::Player::Squeezebox::stream_s (997) Starting decoder with format: f flags: 0x0 autostart: 1 buffer threshold: 255 output threshold: 0 samplesize: ? samplerate: ? endian: ? channels: ?
    [22-01-27 22:34:42.7151] Slim::Networking::Slimproto::_stat_handler (784) 00:04:20:10:19:35: STAT-aude: fullness=0, output_fullness=-1, elapsed=0.000
    [22-01-27 22:34:42.7219] Slim::Networking::Slimproto::_stat_handler (784) 00:04:20:10:19:35: STAT-STMf: fullness=0, output_fullness=-1, elapsed=0.000

    ...

    [22-01-27 22:34:42.7414] Slim::Networking::Slimproto::_stat_handler (784) 00:04:20:10:19:35: STAT-STMe: fullness=0, output_fullness=-1, elapsed=0.000
    [22-01-27 22:34:42.7437] Slim::Networking::Slimproto::_stat_handler (784) 00:04:20:10:19:35: STAT-STMh: fullness=0, output_fullness=-1, elapsed=0.000
    [22-01-27 22:34:42.7442] Slim::Networking::Slimproto::_http_response_handle r (553) Squeezebox got HTTP response:
    HTTP/1.1 200 OK
    Server: Logitech Media Server (8.2.0 - 1627922070)
    Connection: close
    Content-Type: audio/x-flac
    Set-Cookie: Squeezebox-albumView=; path=/
    Set-Cookie: Squeezebox-expandPlayerControl=true; path=/
    Set-Cookie: Squeezebox-expanded-MY_MUSIC=1; path=/
    Set-Cookie: Squeezebox-expanded-FAVORITES=0; path=/
    Set-Cookie: Squeezebox-expanded-PLUGINS=0; path=/
    Set-Cookie: Squeezebox-expanded-PLUGIN_MY_APPS_MODULE_NAME=0; path=/
    Set-Cookie: Squeezebox-expanded-RADIO=0; path=/

    [22-01-27 22:34:42.8988] Slim::Networking::Slimproto::_stat_handler (784) 00:04:20:10:19:35: STAT-STMs: fullness=567980, output_fullness=72832, elapsed=0.000
    [22-01-27 22:34:43.4684] Slim::Networking::Slimproto::_stat_handler (784) 00:04:20:10:19:35: STAT-STMt: fullness=2923027, output_fullness=736384, elapsed=0.000
    [22-01-27 22:34:44.4661] Slim::Networking::Slimproto::_stat_handler (784) 00:04:20:10:19:35: STAT-STMt: fullness=3140673, output_fullness=2100352, elapsed=0.000


    Then it just keeps adding the same line with what looks like different time stamps at the beginning. I then changed what the server was telling the transporter to play:

    [22-01-27 22:43:20.0036] Slim::Networking::Slimproto::_stat_handler (784) 00:04:20:10:19:35: STAT-STMt: fullness=3145727, output_fullness=3501184, elapsed=0.000
    [22-01-27 22:43:20.0045] Slim::Networking::Slimproto::_stat_handler (784) 00:04:20:10:19:35: STAT-strm: fullness=3145727, output_fullness=3501184, elapsed=0.000
    [22-01-27 22:43:20.2140] Slim::Player::Squeezebox::stream (1049) strm-q
    [22-01-27 22:43:20.2195] Slim::Player::Squeezebox::stream (1049) strm-q
    [22-01-27 22:43:20.2276] Slim::Player::Squeezebox::stream_s (544) stream_s called: format: flc url: file:///C:/Users/Tom/Music/Leo%20Kottke/Balance/01%20Leo%20Kottke%20-%20Tell%20Mary.flac
    [22-01-27 22:43:20.2279] Slim::Player::Squeezebox::stream_s (937) Using smart transition mode
    [22-01-27 22:43:20.2280] Slim::Player::Squeezebox::stream_s (997) Starting decoder with format: f flags: 0x0 autostart: 1 buffer threshold: 255 output threshold: 0 samplesize: ? samplerate: ? endian: ? channels: ?
    [22-01-27 22:43:20.2312] Slim::Networking::Slimproto::_stat_handler (784) 00:04:20:10:19:35: STAT-STMf: fullness=0, output_fullness=3501184, elapsed=0.000
    [22-01-27 22:43:20.2313] Slim::Networking::Slimproto::_stat_handler (784) 00:04:20:10:19:35: STAT-strm: fullness=0, output_fullness=3501184, elapsed=0.000
    [22-01-27 22:43:20.2314] Slim::Networking::Slimproto::_stat_handler (784) 00:04:20:10:19:35: STAT-STMf: fullness=0, output_fullness=3501184, elapsed=0.000
    [22-01-27 22:43:20.2315] Slim::Networking::Slimproto::_stat_handler (784) 00:04:20:10:19:35: STAT-strm: fullness=0, output_fullness=3501184, elapsed=0.000
    [22-01-27 22:43:20.2316] Slim::Networking::Slimproto::_stat_handler (784) 00:04:20:10:19:35: STAT-audg: fullness=0, output_fullness=3501184, elapsed=0.000
    [22-01-27 22:43:20.2318] Slim::Networking::Slimproto::_stat_handler (784) 00:04:20:10:19:35: STAT-audp: fullness=0, output_fullness=3501184, elapsed=0.000
    [22-01-27 22:43:20.2338] Slim::Networking::Slimproto::_stat_handler (784) 00:04:20:10:19:35: STAT-STMf: fullness=0, output_fullness=3501184, elapsed=0.000
    [22-01-27 22:43:20.2343] Slim::Networking::Slimproto::_stat_handler (784) 00:04:20:10:19:35: STAT-STMc: fullness=0, output_fullness=3501184, elapsed=0.000
    [22-01-27 22:43:20.2457] Slim::Networking::Slimproto::_stat_handler (784) 00:04:20:10:19:35: STAT-strm: fullness=0, output_fullness=3501184, elapsed=0.000
    [22-01-27 22:43:20.2458] Slim::Networking::Slimproto::_stat_handler (784) 00:04:20:10:19:35: STAT-audg: fullness=0, output_fullness=3501184, elapsed=0.000
    [22-01-27 22:43:20.2459] Slim::Networking::Slimproto::_stat_handler (784) 00:04:20:10:19:35: STAT-STMe: fullness=0, output_fullness=3501184, elapsed=0.000
    [22-01-27 22:43:20.2498] Slim::Networking::Slimproto::_stat_handler (784) 00:04:20:10:19:35: STAT-STMh: fullness=0, output_fullness=3501184, elapsed=0.000
    [22-01-27 22:43:20.2500] Slim::Networking::Slimproto::_http_response_handle r (553) Squeezebox got HTTP response:
    HTTP/1.1 200 OK
    Server: Logitech Media Server (8.2.0 - 1627922070)
    Connection: close
    Content-Type: audio/x-flac
    Set-Cookie: Squeezebox-albumView=; path=/
    Set-Cookie: Squeezebox-expandPlayerControl=true; path=/
    Set-Cookie: Squeezebox-expanded-MY_MUSIC=1; path=/
    Set-Cookie: Squeezebox-expanded-FAVORITES=0; path=/
    Set-Cookie: Squeezebox-expanded-PLUGINS=0; path=/
    Set-Cookie: Squeezebox-expanded-PLUGIN_MY_APPS_MODULE_NAME=0; path=/
    Set-Cookie: Squeezebox-expanded-RADIO=0; path=/

    [22-01-27 22:43:20.4770] Slim::Networking::Slimproto::_stat_handler (784) 00:04:20:10:19:35: STAT-STMt: fullness=860576, output_fullness=258048, elapsed=0.000
    [22-01-27 22:43:21.4762] Slim::Networking::Slimproto::_stat_handler (784) 00:04:20:10:19:35: STAT-STMt: fullness=3142761, output_fullness=1400832, elapsed=0.000


    What does it mean to my Transporter not playing?
    1x Squeezebox Classic3, 1x Squeezebox Duet, 3x Squeezebox Controller, 1x Squeezebox Boom, 6x Squeezebox Touch, 5x Squeezebox Radio, 1x Transporters, 2x DOA Transporters, Logitech Media Server Version: 8.2.0, Synology NAS DS920+ Docker

Posting Permissions

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