Home of the Squeezebox™ & Transporter® network music players.
Page 361 of 376 FirstFirst ... 261311351359360361362363371 ... LastLast
Results 3,601 to 3,610 of 3755
  1. #3601
    thanks ralphy. Same result with the -e mad option

    I'm using the default windows 10 Virus & threat protection. I tried with real-time protection off but it didn't help.

    Since on the same laptop it works via WiFi and not via Ethernet, could it be an MTU setting, or some other network-related issue ? Do you happen to know what mpeg decoder SqueezePlay uses (as it doesn't exhibit the problem)?

  2. #3602
    Senior Member dolodobendan's Avatar
    Join Date
    Dec 2017
    Location
    Braunschweig, Germany
    Posts
    1,353
    I don't know if this is related, but when I played the provided mp3, I got this in the log:

    Code:
    [20-08-30 02:56:42.6781] Slim::Schema::_preCheckAttributes (2610) Invalid ReplayGain tag found in /share/Multimedia/Music/Air/Moon Safari/07 - Air - You Make It Easy.mp3: REPLAYGAIN_TRACK_GAIN -> eplaygai
    [20-08-30 02:56:42.7024] Slim::Schema::_preCheckAttributes (2610) Invalid ReplayGain tag found in /share/Multimedia/Music/Air/Moon Safari/07 - Air - You Make It Easy.mp3: REPLAYGAIN_TRACK_PEAK -> eplaygai
    [20-08-30 02:56:42.8562] Slim::Schema::_createOrUpdateAlbum (1202) Invalid ReplayGain tag found in /share/Multimedia/Music/Air/Moon Safari/07 - Air - You Make It Easy.mp3: REPLAYGAIN_ALBUM_GAIN -> eplaygai
    But I just hot-swapped (no rescan) my mp3 that doesn't have replay gain tags with the provided one, maybe LMS got confused by that.
    QLMS 8.2@2.21 x64 (digimaster) with perl 5.30.1 / QNAP 469L QTS 4.3.4

  3. #3603

    same outcome

    Ralphy same test with extra param:

    C:\squeezelite\squeezelite-x64.exe -o 9 -M "ArthurPC" -e mad -d all=debug

    result is the same playing stoppen at 05:33 and resumed after about 10 seconds

    Windows 10 Pro 1909 (clean install and completely disabled auto update)

    default Windows Antivirus and TinyWall outbound firewall

    Arthur

  4. #3604
    bingo, it is related to buffer size. The following commands ran fine:

    Code:
    squeezelite-x64.exe -s 192.168.9.1 -d all=debug -e mad -f madnoav.log -b 1400:1400
    
    squeezelite-x64.exe -s 192.168.9.1 -d all=debug -f smallbuffer.log -b 1400:1400
    This is a very small buffer size, but it may work a wired gig Eth network.

    I'm not certain how to send the argument to the Squeezelite-X shortcut though, the following doesn't work (unless the squeezelite used is different in SLX version 2.6.35.0?) :

    Code:
    "C:\Program Files\Squeezelite-X\SqueezeliteX.exe" -b 1400:1400
    @rgdawson, any suggestion?

    @Arthur, do you mind giving it a try?

  5. #3605
    C:\squeezelite\squeezelite-x64.exe -o 9 -M "ArthurPC" -b 1400:1400 -d all=debug

    Nice find it's buffer related

    Because now, for the first time it stopped at 05:08 (instead at 05:33)

    After diner will try some variants

    Arthur

  6. #3606
    :-)

  7. #3607

    Finally all files are playing

    as what mcoste allready discovered it's buffer related.

    Now the complicated part, the codec should hold at least one mp3 frame input (advised 5) and a higher number on the output side.

    So for a 2 second buffer i toke a 320 kbps bitrate => 655360 bits
    and for the output i doubled the size => 1310720 bits

    C:\squeezelite\squeezelite-x64.exe -o 9 -M "ArthurPC" -b 655360:1310720 -d all=debug

    BUT THE MAIN QUESTION IS: what is the real max size of a MP3 frame ???

    see ti.pdf (Texas Instruments - Bitstream Buffer in Audio Coprocessor)

    Arthur
    Attached Images Attached Images

  8. #3608
    Senior Member
    Join Date
    May 2008
    Location
    Canada
    Posts
    6,921
    Quote Originally Posted by Arthur View Post
    as what mcoste allready discovered it's buffer related.

    Now the complicated part, the codec should hold at least one mp3 frame input (advised 5) and a higher number on the output side.

    So for a 2 second buffer i toke a 320 kbps bitrate => 655360 bits
    and for the output i doubled the size => 1310720 bits

    C:\squeezelite\squeezelite-x64.exe -o 9 -M "ArthurPC" -b 655360:1310720 -d all=debug

    BUT THE MAIN QUESTION IS: what is the real max size of a MP3 frame ???

    see ti.pdf (Texas Instruments - Bitstream Buffer in Audio Coprocessor)

    Arthur
    Size are in KBytes. So 1400 is actually 1.4MB. What might happen is a problem at buffer wrap. By changing the size, you're changing the moment where it wraps. Just an hypothesis
    Last edited by philippe_44; 2020-08-31 at 15:10.
    LMS 8.1.x on Odroid-C4 - SqueezeAMP!, 5xRadio, 5xBoom, 2xDuet, 1xTouch, 1xSB3. Sonos PLAY:3, PLAY:5, Marantz NR1603, Foobar2000, ShairPortW, 2xChromecast Audio, Chromecast v1 and v2, Squeezelite on Pi, Yamaha WX-010, AppleTV 4, Airport Express, GGMM E5, RivaArena 1 & 3

  9. #3609
    Senior Member ralphy's Avatar
    Join Date
    Jan 2006
    Location
    Canada
    Posts
    2,832
    Quote Originally Posted by Arthur View Post
    Ralphy same test with extra param:

    C:\squeezelite\squeezelite-x64.exe -o 9 -M "ArthurPC" -e mad -d all=debug

    result is the same playing stoppen at 05:33 and resumed after about 10 seconds

    Windows 10 Pro 1909 (clean install and completely disabled auto update)

    default Windows Antivirus and TinyWall outbound firewall

    Arthur
    Quote Originally Posted by mcoste View Post
    bingo, it is related to buffer size. The following commands ran fine:

    Code:
    squeezelite-x64.exe -s 192.168.9.1 -d all=debug -e mad -f madnoav.log -b 1400:1400
    
    squeezelite-x64.exe -s 192.168.9.1 -d all=debug -f smallbuffer.log -b 1400:1400
    That helps to confirm that libmad is not the cause, thanks for testing it.
    Ralphy

    1-Touch, 5-Classics, 3-Booms, 2-UE Radio
    Squeezebox client builds donations always appreciated.

  10. #3610
    Quote Originally Posted by Arthur View Post
    Because now, for the first time it stopped at 05:08 (instead at 05:33)
    @Arthur, now that I managed to pass the argument to SLX I found like you that it solved the problem only for the one mp3 I was using as a reference. Others still stop but at a different time :-(

Posting Permissions

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