Home of the Squeezebox™ & Transporter® network music players.
Page 2 of 7 FirstFirst 1234 ... LastLast
Results 11 to 20 of 70
  1. #11
    Senior Member
    Join Date
    Jan 2007
    Location
    Next to my neighbours :-)
    Posts
    148
    I switched proxy streaming on and double checked that it was.

    Keith Jarrett, Koln concert, track #1, 26.01 minutes, FLAC 581kbps (qobuz://625183.flac)
    and it played the full length :-)

    While typing this post I had a different track playing I also knew that would be cut of before the end while using direct streaming.

    David Fray, Schubert Fantaisie, Track #1, 19.09 minutes, 349kbps FLAC (qobuz://21986694.flac)
    and it was cut off near 3:30 minutes from the end :-(
    I've restarted the track again....and again it cuts off near 3:30 from the end.

    Janine Jansen, Beethoven & Britten: Violin Concertos, Track #1, 23.56 minutes, 605kbps FLAC (qobuz://621425.flac)
    and played it in full :-)

    Proxy streaming did resolve the premature cut off's in 2 of 3 tracks. More testing needed. Maybe the David Fray track is not ok as stored on the servers at Qobuz....

    I'll keep eye open for other tracks and play other albums with long tracks.

    Huib

    PS.
    LMS running on a RPi2B using PicorePlayer 3.22
    does the all-black SB sound better than the white SB?

  2. #12
    Senior Member
    Join Date
    Jan 2007
    Location
    Next to my neighbours :-)
    Posts
    148
    London Symphony Orchestra, Ravel: Bolero, 14:27 minutes, 559kbps FLAC (qobuz://518619.flac)

    is cut of at around 4 to 5 minutes before the end :-(
    does the all-black SB sound better than the white SB?

  3. #13
    Babelfish's Best Boy mherger's Avatar
    Join Date
    Apr 2005
    Location
    Switzerland
    Posts
    19,986

    QOBUZ Plugin buffering/caching.

    > and it played the full length :-)

    I think what you're dealing with is different from the issue the others
    are reporting: they are complaining about intermittent re-buffering.
    That's a different story than the track ending too early.

    --

    Michael

  4. #14
    Senior Member
    Join Date
    Jan 2007
    Location
    Next to my neighbours :-)
    Posts
    148
    Quote Originally Posted by mherger View Post
    > and it played the full length :-)

    I think what you're dealing with is different from the issue the others
    are reporting: they are complaining about intermittent re-buffering.
    That's a different story than the track ending too early.

    --

    Michael
    Oops, yes wrong thread, my issue was also reported by others.

    By the way, proxy streaming did improve the situation, with direct stream it would cut off much sooner.
    does the all-black SB sound better than the white SB?

  5. #15
    Senior Member
    Join Date
    Dec 2009
    Location
    Albinea (Bologna Area) Italy
    Posts
    604
    Quote Originally Posted by bpa View Post
    If plugin is using normal LMS sysread - then I think the problem is with Quboz and their CDN - perhaps LMS plugin is not using some option (e.g. using http 1.0 vs http 1.1 - I don't know Qobuz format so this is just an example not a suggestion). Randomly changing various buffer sizes is not a good way to "fix" the problem. I'd use wireshark to examine the different dataflows and compare.
    I had a conversation with Qobuz customer support in this regard and this is what they answered:

    We currently use the cloud of AWS like most streaming services. So, to reply your specific question, all music is served the same and balanced the same way.

    We are very sorry that you face difficulties with Squeezebox.
    In a previous message, they suggest using the pre-cache function, which is not implemented in lms / qobuz-plugin.

    For them question is closed:

    Qobuz propose a lot of way to stream.
    On the other hand, as Michael reiterated, LMS does not save data on disk, so the implementation of this function is not going to happen.

    I think we all agree problem is not the buffer size per se, but seems to me that all other roads are precluded and having FIFO of some tens of MB will probably mask most of problems and solve the issue, with no hurts.

    I'll have a look to wireshark, anyway.
    __________________________________________________ ______________________
    Author of C-3PO plugin, Squeezelite-R2, Falcon Web interface - See www.marcoc1712.it

  6. #16
    Senior Member
    Join Date
    Oct 2005
    Location
    Ireland
    Posts
    15,722
    Quote Originally Posted by marcoc1712 View Post
    I'll have a look to wireshark, anyway.
    I believe Qobuz have a webplayer ?
    Does it have gaps ?
    If not how does it do streaming ? The Web player approach may then be best suited to SB as it should not involve disk storage or large caches. Chrome/Firefox console "network" tabs are great for analysing web players.

    edit:

    Since Qobuz webplayer supports chromecast - this means the web playing streams are probably either normal http or chunked http (DASH, HLS etc,).
    Last edited by bpa; 2018-01-17 at 06:29.

  7. #17
    Babelfish's Best Boy mherger's Avatar
    Join Date
    Apr 2005
    Location
    Switzerland
    Posts
    19,986

    QOBUZ Plugin buffering/caching.

    > I think we all agree problem is not the buffer size per se, but seems to
    > me that all other roads are precluded and having FIFO of some tens of MB
    > will probably mask most of problems and solve the issue, with no hurts.


    I don't remember this... is it possible to transcode those streams? Eg.
    transcode to PCM? When working on Spotty I saw that the helper often
    would download the audio data at full bandwidth, effectively buffering
    the data on the LMS host. If the Qobuz stream could be transcoded to PCM
    or flac again, you might be able to address the re-buffering at the cost
    of some computing and memory overhead on LMS.

    (And while Qobuz' claim, that they were using AWS like everybody else,
    might be true, this certainly doesn't guarantee the same quality across
    all services. AWS offers an endless number of options to make stuff work
    more or less good...)

    --

    Michael

  8. #18
    Senior Member
    Join Date
    Dec 2009
    Location
    Albinea (Bologna Area) Italy
    Posts
    604
    Quote Originally Posted by mherger View Post
    > I think we all agree problem is not the buffer size per se, but seems to
    > me that all other roads are precluded and having FIFO of some tens of MB
    > will probably mask most of problems and solve the issue, with no hurts.


    I don't remember this... is it possible to transcode those streams? Eg.
    transcode to PCM? When working on Spotty I saw that the helper often
    would download the audio data at full bandwidth, effectively buffering
    the data on the LMS host. If the Qobuz stream could be transcoded to PCM
    or flac again, you might be able to address the re-buffering at the cost
    of some computing and memory overhead on LMS.

    (And while Qobuz' claim, that they were using AWS like everybody else,
    might be true, this certainly doesn't guarantee the same quality across
    all services. AWS offers an endless number of options to make stuff work
    more or less good...)

    --

    Michael
    Sure is possible to transcode the stream, I normally do. What are you thinking about? implementing a FIFO as first step of the transcodind pipeline? If so, I foresee a problem in windows, but probably is viable using C.
    __________________________________________________ ______________________
    Author of C-3PO plugin, Squeezelite-R2, Falcon Web interface - See www.marcoc1712.it

  9. #19
    Senior Member
    Join Date
    Dec 2009
    Location
    Albinea (Bologna Area) Italy
    Posts
    604
    Quote Originally Posted by bpa View Post
    I believe Qobuz have a webplayer ?
    Does it have gaps ?
    If not how does it do streaming ? The Web player approach may then be best suited to SB as it should not involve disk storage or large caches. Chrome/Firefox console "network" tabs are great for analysing web players.

    edit:

    Since Qobuz webplayer supports chromecast - this means the web playing streams are probably either normal http or chunked http (DASH, HLS etc,).
    Good point, I never tried web player, I'll have a try when experiencing problems in LMS.
    Last edited by marcoc1712; 2018-01-17 at 07:24.
    __________________________________________________ ______________________
    Author of C-3PO plugin, Squeezelite-R2, Falcon Web interface - See www.marcoc1712.it

  10. #20
    Babelfish's Best Boy mherger's Avatar
    Join Date
    Apr 2005
    Location
    Switzerland
    Posts
    19,986

    QOBUZ Plugin buffering/caching.

    > Sure is possible to transcode the stream, I normally do.

    "normally"? Are you transcoding the Qobuz stream? If so, what if you
    didn't?...

    --

    Michael

Posting Permissions

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