Home of the Squeezebox™ & Transporter® network music players.
Page 97 of 97 FirstFirst ... 4787959697
Results 961 to 965 of 965
  1. #961
    Junior Member
    Join Date
    May 2018
    Posts
    16
    Quote Originally Posted by garym View Post
    Because of a problem with my main LMS server unit, I built a pi-3B+ running picoreplayer (ver 4.1.0). I have attached a USB 3 portable drive. I have about 100,000 tracks, mostly FLAC, some mp3 or m4a. Mostly 16/44.1 files with a handful of 24/96 files.

    My observation is that the pi does a great job running LMS. No problem with serving files, including to two or three synched players. I expected this part would be fine. I assumed that the browsing and searching would be very slow. But for browsing I find it very snappy (within album artist or within album, for example). And even searching seems relatively fast. This surprises me.

    Great job! (2nd donation just made). Am I just lucky or can this little pi really function well as a server with a 100k+ library. (I recall starting my squeezebox journey with squeezeserver running on a ReadyNas Duo (v1) and it was painful to browse on even a 40k library).
    I have piCorePlayer running on a Rasp Pi 3. I have LMS running on it, I also have a 500GB USB SSD drive connected that is SAMBA served. I use dbPowerAmp on my Windows PC to rip CDs to the SSD on the RPI and the RPI has a Allo Spdif board on it that feeds a DAC. It also acts via the network as a server to another RPI with an Allo Spdif board (no disk) that feeds it music file remotely. The music on both systems sounds awesome and the system is super snappy, I don't see a difference in the system with the disk locally attached or remotely with the system attached via a wireless network.

    I ordered a RPI 4 and am waiting for piCorePlayer to officially support the RPI 4 as I want to add disk mirroring to the system that has the SSD mounted on it for reliability. SSDs are reliable but I would hate to have to rip all those CDs again. I also want to add a built in display for the system with the disks that has a touch screen. I need the extra memory of the RPI 4 to do all of that but I am super satisfied with the setup. The only glitch that I have is that if my wireless goes down the remote system gets a little confused sometimes even the local RPI but its not to hard to reset. Good luck with your setup, I really love piCorePlayer and can't wait for it to be ported to the RPI 4. Regards

  2. #962
    Senior Member paul-'s Avatar
    Join Date
    Jan 2013
    Posts
    2,514
    pCP 6 supports it. It's technically a beta, but it's pretty stable.

    https://forums.slimdevices.com/showt...-0-PI4-support
    piCorePlayer a small player for the Raspberry Pi in RAM.
    Homepage: https://www.picoreplayer.org

    Please donate if you like the piCorePlayer

  3. #963
    Junior Member
    Join Date
    Jan 2020
    Posts
    2

    352.8 khz

    Hi, does piCorePlayer 5.0 support 352.8 khz and 384 khz over i2s? I have a rpi 3b with a kali reclocker connected to an audio-gd r8 dac and when I play a 352.8 khz flac file sox gets used and it consumes about 25% cpu, I'm assuming sox is resampling because 192 khz flac files playback without sox, flac is set to native.

    Thanks

  4. #964
    Senior Member paul-'s Avatar
    Join Date
    Jan 2013
    Posts
    2,514
    Quote Originally Posted by guzz46 View Post
    Hi, does piCorePlayer 5.0 support 352.8 khz and 384 khz over i2s? I have a rpi 3b with a kali reclocker connected to an audio-gd r8 dac and when I play a 352.8 khz flac file sox gets used and it consumes about 25% cpu, I'm assuming sox is resampling because 192 khz flac files playback without sox, flac is set to native.

    Thanks
    The onboard RPi i2s hardware only supports 192k. You would have to do USB to get those rates, and it can be very difficult with the RPI USB weakness.

    The PI4 has better chances with the USB
    piCorePlayer a small player for the Raspberry Pi in RAM.
    Homepage: https://www.picoreplayer.org

    Please donate if you like the piCorePlayer

  5. #965
    Junior Member
    Join Date
    Jan 2020
    Posts
    2
    Quote Originally Posted by paul- View Post
    The onboard RPi i2s hardware only supports 192k. You would have to do USB to get those rates, and it can be very difficult with the RPI USB weakness.

    The PI4 has better chances with the USB
    Ok, I was using rune 5 beta before piCore and it played the 352.8 khz file fine, at least mpd indicated it was playing it without any resampling, they said they patched the kernel to allow 384 khz support, on the other hand I couldn't tell any difference between native 352.8 and resampled 352.8 so maybe I should just convert them to 192 khz and same some space.

    Thanks

Posting Permissions

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