Home of the Squeezebox™ & Transporter® network music players.
Page 236 of 255 FirstFirst ... 136186226234235236237238246 ... LastLast
Results 2,351 to 2,360 of 2548
  1. #2351
    Senior Member JackOfAll's Avatar
    Join Date
    Dec 2005
    Location
    London, UK
    Posts
    2,749
    Quote Originally Posted by Rob P View Post
    Has anyone experienced such a strange results?
    Rob, need to be sure you are comparing apples to apples, not apples to oranges. 50% of a CPU running at 396MHz, or 50% at a Gig? Latest release (R8) went back to using the ondemand governor by default. When it drops to a lower freq core speed, % used will increase.

  2. #2352
    Junior Member
    Join Date
    Apr 2014
    Location
    US
    Posts
    26
    Quote Originally Posted by JackOfAll View Post
    Rob, need to be sure you are comparing apples to apples, not apples to oranges. 50% of a CPU running at 396MHz, or 50% at a Gig? Latest release (R8) went back to using the ondemand governor by default. When it drops to a lower freq core speed, % used will increase.
    Silly me! I forgot that we are not using fixed CPU speed in R8!

  3. #2353
    Senior Member JackOfAll's Avatar
    Join Date
    Dec 2005
    Location
    London, UK
    Posts
    2,749
    Quote Originally Posted by badboygolf16v View Post
    I'm having a couple of issues with DSDPlay.
    Going to have to come back to this. Probably not until I get time at the weekend. I suspect the radio reboot might have more to do with UI code and null artwork than the audio data it is being sent.

  4. #2354
    Senior Member
    Join Date
    Aug 2008
    Posts
    152
    Thanks. I'll download Audiogate in the meantime to convert the dff file to dsf, and tag it, see if that makes a difference.

  5. #2355
    Senior Member JackOfAll's Avatar
    Join Date
    Dec 2005
    Location
    London, UK
    Posts
    2,749

    logitechmediaserver-7.9.0-0.10.20140508git1399582156

    logitechmediaserver-7.9.0-0.10.20140508git1399582156

    Changes...
    Code:
    * Thu May 08 2014 - 7.9.0-0.10.20140508git1399582156
    - Git revision public/7.9 e762679322afdd1ed505f1f5b16c673d0d96b433.
      We need to use the default_dbsource string to open other databases than 
       library.db.
      Change-Id: I8411808943b74c76a2dfcd9ac5e287ab842b55d2
    - Git revision public/7.9 3cdfebe6f43fafba64b36be2d7b21fc994090e03.
      Use the same track information order (Title/Artist/Album) in the web UI
       as on the players.
    - Git revision public/7.9 59dcf766693d99ae668542c752f7e94d8df8eed6.
      Cache library's total play time.
    - Git revision public/7.9 c6e49881029b56643563ef0b1497e7cc82bf0d05.
      VACUUM a little more aggressively during scans.
    - Git revision public/7.9 1d41075a79ce6e96db88d7bc9d290f85ea631f6e.
      Move the VACUUM process to the optimizeDB step. Only run after a new &
       changed scan if no player is active.
    - Git revision public/7.9 4bd6548abef5621f957dc5eeedbf4fb56c5a12b6.
      Delete temporary table if it already exists.
      Don't reset the isScanning flag before we're really done.
    - Git revision public/7.9 4085fbeddeee3f68139b7e2302fff97d37e1e150.
      Add third dbhighmem option "max": use up to 500MB of memory for the
       SQLite cache. In most cases only a fraction of this will be used, but
       should cover most large collections, too.
    - Git revision public/7.9 445aaa1c854c36bc2273571907c465d479f4c37e.
      Use VACUUM to re-organize library files during a wipe & rescan.
      library.db is always VACUUMed after all the tables have been emptied. It
       should be really quick on mostly empty databases.
      persist.db only gets compressed when a certain level of fragmentation
       (20%) is reached. Compressing it on every run might be too expensive, as
       the data is mostly static anyway.
    - Git revision public/7.9 002a5aadc9a9ef4fea0b4ef22e2cdd5c94b9a5e6.
      Don't cache prepared statements, they're pretty much unique at every
       call.
    - Git revision public/7.9 30e7f2485dddd8ba663c26eb050583ce5db07e75.
      Enable auto_vacuum on caches. Caches see a lot of updates/deletes,
       potentially wasting disk space.
    - Git revision public/7.9 de18e31e2c649bff5d381ad58bd60c317592f653.
      Optimize ignoreCaseArticle: The scanner often does a call using
       transliteration first, then without second. Cache both values when we
       create them anyway to save one pass in the scanner.
    - Git revision public/7.9 750e0461022278db4dbbe0e4f62df076000fe0a3.
      Cache cleaned tags so we don't need to process every track of an album.
    - Git revision public/7.9 65e792632ff9440ebe141749f2cc24ad1bc2174d.
      use dbh->prepare_cached instead of dbh->do for repeated query.
    - Git revision public/7.9 bcff71512772dc7bed68732ee62dce9d23ccb5b4.
      Use readdir in list mode instead of scalar mode - should use less memory on 
       larger folders.
      Change-Id: I2628b3ab327853d27bc3994e5aacea3c1f9bea19
    - Git revision public/7.9 42b270b5e2810ff702cc47309ea96410263a1a45.
      The scanner calls _validTrackOrURL twice for every track. Keep track of
       the previous result to skip one processing.
    - Git revision public/7.9 d91bc7234c19dfa65362514addf8dac7c8e53ca8.
      Tweak artwork scanner: disable autocommit, use prepared SQL statements.
      Change-Id: If5419a3ca47f2c4c995220c07a17550a96912600
    - Git revision public/7.9 da0fd7bc6129a92bbd514b2fda1377fd1355eb58.
      Don't evaluate the inDBOnlyCount and changedOnlyCount when running a wipe 
       & rescan. These would always return 0.
      Wipe scanned_files table between scan steps, as we don't want the overhead 
       of the previous scan when there are multiple folders to be scanned
       (eg. files & playlists).
      Change-Id: Ib8bb92d0fe8bdb9d98027521e4dbe40265c9ae19
    - Git revision public/7.9 f8f4a3baf9c14272812474d1366a9d6ebf76faf6.
      The variousArtistsObject doesn't change during an external scan. Create it 
       once and cache its ID, as we access it very often.
      Change-Id: I5e12969c110d1a19dc02f95eb39cc56e979847c4
    - Git revision public/7.9 776e0d9d5e22a04b560e4d115239fad00533883b.
      Optimize mergeSingleVAAlbum.
      Don't run the full evaluation if the compilation flag is set already,
       and the call only wants to know whether an album is a compilation or
       not. No need to double-check whether it really is a compilation.  
      Re-arrange the WHERE condition to make better use of indices.
    - Git revision public/7.9 850a21546785adc9dfde94c6cf284cdbf2a01eaf.
      Optimize scanning of new tracks.
      Create temporary table of onDiksOnly tracks, instead of querying the
       main tracks table over and over again.
    - Git revision public/7.9 850a21546785adc9dfde94c6cf284cdbf2a01eaf.
      Optimize scanning of new tracks.
      Create temporary table of onDiksOnly tracks, instead of querying the
       main tracks table over and over again.
    - Git revision public/7.9 908388433d767d03d3fa2f3602aa56f9c8516b1a.
      Set the cache_size on persist.db, too.
    - Git revision public/7.9 bc9ac0b80c28ed358a55bd09fc81a41efcbb0978.
      Changelog update.
    - Git revision public/7.9 11a2ae55361a562d86a0edd02ddedb8803eb1fe8.
      Add ALBUMARTIST tag support for Cue files.
      Interpret and export the top-level PERFORMER in the Cue file as the 
       ALBUMARTIST tag.  If the per-track PERFORMER (e.g. track artist) is different, 
       flag this album as a compilation.
      This also helps LMS recognize multi-disc sets of compilations (when using 
       cue sheets).
    Update...
    Code:
    sudo csos-cleanUpdate-unstable logitechmediaserver

  6. #2356
    Senior Member JackOfAll's Avatar
    Join Date
    Dec 2005
    Location
    London, UK
    Posts
    2,749
    One potential issue with the logitechmediaserver-7.9.0-0.10.20140508git1399582156 update, I've just noticed. Re-scan "new and changed" seems to be locking the web-gui out of the database. Can't remember, but I don't think this was the previous behaviour. Might have something to do with Michael's recent db "optimisations".

  7. #2357
    Babelfish's Best Boy mherger's Avatar
    Join Date
    Apr 2005
    Location
    Switzerland
    Posts
    20,354

    Community Squeeze OS F19 Release 1

    > One potential issue with the
    > logitechmediaserver-7.9.0-0.10.20140508git1399582156 update, I've just
    > noticed. Re-scan "new and changed" seems to be locking the web-gui out
    > of the database. Can't remember, but I don't think this was the previous
    > behaviour. Might have something to do with Michael's recent db
    > "optimisations".


    Can you tell me at which point this happens? By "locking" do you mean
    the web UI becomes non-responsive? Any error in server.log? How large is
    your collection, the library.db and persist.db files? And are you using
    any 3rd party plugins?

    Feel free to post all the responses to some 7.9 related thread if you
    don't want to add that noise to this one.

    --

    Michael

  8. #2358
    Senior Member JJZolx's Avatar
    Join Date
    Apr 2005
    Location
    Colorado
    Posts
    11,531
    Quote Originally Posted by JackOfAll View Post
    One potential issue with the logitechmediaserver-7.9.0-0.10.20140508git1399582156 update, I've just noticed. Re-scan "new and changed" seems to be locking the web-gui out of the database. Can't remember, but I don't think this was the previous behaviour. Might have something to do with Michael's recent db "optimisations".
    I definitely don't see this behavior on Windows. FWIW.

  9. #2359
    Babelfish's Best Boy mherger's Avatar
    Join Date
    Apr 2005
    Location
    Switzerland
    Posts
    20,354

    Community Squeeze OS F19 Release 1

    >> One potential issue with the
    >> logitechmediaserver-7.9.0-0.10.20140508git1399582156 update, I've just
    >> noticed. Re-scan "new and changed" seems to be locking the web-gui out
    >> of the database. Can't remember, but I don't think this was the previous
    >> behaviour. Might have something to do with Michael's recent db
    >> "optimisations".

    >
    > I definitely don't see this behavior on Windows. FWIW.


    It could be the VACUUM step at the end of a scan. Depending on your
    library size and I/O performance this can take a while, during which the
    web UI is non-responsive. It should only be run if no player is active.
    You might not have seen it if the step was skipped due to some player
    playing music in the background.

    --

    Michael

  10. #2360
    Senior Member
    Join Date
    Jun 2011
    Posts
    131

    Working DSD DoP DACs

    Quote Originally Posted by JackOfAll View Post
    I was asked to provide a list of DAC's that would work with squeezelite DoP output. The answer should be, we're DoP compliant, therefore any DAC that claims to support DoP will work. But in the real world....

    So I know lintweaker uses a Mytek, Triode was testing with Sonore, and I can vouch for Buffalo. I could go back through the thread and find the other DAC's that people are using....... Rather than do that, (yes, I'm being lazy, I know), people using DAC's successfully with DoP output from squeezelite, if it isn't already mentioned, can you remind me, please? Thank you.
    Not sure where the list with, known working, DACs with DSD via DoP is. So for completeness:

    - Mytek Stereo192 DSD DAC
    - Sonore/exD DSD DAC
    - Marantz SA-14S1

    In general, every DAC which support DSD over DoP, should work.

Posting Permissions

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