Home of the Squeezebox™ & Transporter® network music players.
Page 1 of 10 123 ... LastLast
Results 1 to 10 of 551

Hybrid View

  1. #1
    Senior Member paul-'s Avatar
    Join Date
    Jan 2013
    Posts
    2,276

    ANNOUNCE: piCorePlayer 5.0.0

    The pCP team is happy to announce the release of piCorePlayer 5.0.0

    Significant changes

    pCP 5.0.0
    • Kernel 4.19.40
    • AudioCore kernel 4.19.40-rt19. All RPi processors supporting Realtime Kernels.
    • RPi Firmware 2019/05/02
    • Update to Squeezelite v1.9.2-1158-pCP. Includes https direct streaming support.
    • Stream sound from Audio Input cards supported with pcp-streamer

    Updates to base OS and packages
    • Upgrade to Busybox 1.30.1
    • Multi-threaded extension bootloader for faster boots.
    • glibc 2.29
    • wpa_supplicant/hostapd 2.27
    • Perl 5.28.
    • Samba 4.10.4

    DAC Additions
    • Hifiberry DAC+ADC (Input and Output)
    • Audiophonics ISabre Q2M Dac
    • ApplePi Dacs.

    Various web interface changes.
    • Redesigned extension page.
    • Add iperf3 to diagnostic tools.
    • Many fixes and correction

    Changes to IR remote functionality.
    • GPIO Based IR receivers with Jivelite installed, now use kernel Keytables for function. See Create Keytable configurations
    • Slimdevices remote is the default controller.
    • Other configurations can be uploaded from the IR page.


    Notes

    • Adding a file named "netusb" to the boot partition will automatically load/configure net-usb kernel modules.
    • Adding wpa_supplicant.conf to the boot partition will automatically enable wifi.


    Recommended Upgrade path.
    • Download new image and configure from scratch.
    • Insitu_update is availiable, and handles most installations. You will need to run HotFix on your 4.1.0 installation. And may need to remove and re-install added features. However, downgrading versions will not be possible.



    Downloads Can be found: https://www.picoreplayer.org/main_downloads.shtml
    Last edited by paul-; 2019-06-10 at 17:22.
    piCorePlayer a small player for the Raspberry Pi in RAM.
    Homepage: https://www.picoreplayer.org

    Please donate if you like the piCorePlayer

  2. #2
    Senior Member paul-'s Avatar
    Join Date
    Jan 2013
    Posts
    2,276
    5.0.1: A Hotfix has been pushed to correct the LMS autostart problem......use the Hotfix button on the main page.
    Last edited by paul-; 2019-09-08 at 06:13.
    piCorePlayer a small player for the Raspberry Pi in RAM.
    Homepage: https://www.picoreplayer.org

    Please donate if you like the piCorePlayer

  3. #3
    Member
    Join Date
    Apr 2019
    Location
    Wunstorf, Germany
    Posts
    53
    The link to the normal 5.0.0 on the downloadpage is incorrect: https://repo.picoreplayr.org/insitu/...layer5.0.0.zip
    it should be: https://repo.picoreplayer.org/insitu...layer5.0.0.zip

    There is simply an "e" missing. :-)

  4. #4
    Senior Member
    Join Date
    Mar 2010
    Posts
    114
    Quote Originally Posted by paul- View Post
    Recommended Upgrade path.
    • Download new image and configure from scratch.
    • Insitu_update is availiable, and handles most installations. You will need to run HotFix on your 4.1.0 installation. And may need to remove and re-install added features.
    Should I also do this when upgrading from the beta, or is in-site update OK for that situation?

  5. #5
    Senior Member paul-'s Avatar
    Join Date
    Jan 2013
    Posts
    2,276
    Quote Originally Posted by carsten_h View Post
    The link to the normal 5.0.0 on the downloadpage is incorrect: https://repo.picoreplayr.org/insitu/...layer5.0.0.zip
    it should be: https://repo.picoreplayer.org/insitu...layer5.0.0.zip

    There is simply an "e" missing. :-)
    Thx....links in too many places

    Quote Originally Posted by pputzer View Post
    Should I also do this when upgrading from the beta, or is in-site update OK for that situation?
    Depends on what version of the beta I let you test.... there were a few betas with glitched update packages. If it works you should be fine.
    Last edited by paul-; 2019-06-09 at 12:22.
    piCorePlayer a small player for the Raspberry Pi in RAM.
    Homepage: https://www.picoreplayer.org

    Please donate if you like the piCorePlayer

  6. #6
    Senior Member
    Join Date
    Mar 2010
    Posts
    114
    Quote Originally Posted by paul- View Post
    Depends on what version of the beta I let you test.... there were a few betas with glitched update packages. If it works you should be fine.
    Beta 9. But apparently, for that version it does not work (only 4.1.0 and 4.0.0 are listed as versions to update from, so when trying to download the update script, it fails).

  7. #7
    Senior Member
    Join Date
    Dec 2008
    Location
    Alexandria, Va USA
    Posts
    191
    Nice! Thanks for the treat.
    I just bought a new 7" RPi screen yesterday ( 1st was not working, bad touch calibration ).
    Setting it up I saw the new version. Tried the in-situ upgrade from 4.0.
    Wacked my sd ( no boot ), so I got a new image.
    Works great so far.
    2 Duets controllers, 1 X Boom, 1 X Radio
    1 X Receiver + Edifier S1000DB
    1 X Receiver + Yamaha RX-A2000, Polk M70
    1 X Receiver + Boston MicroSystem CD
    Raspberry Pi 3 B+ HiFi Berry Amp2 7" touchscreen PiCorePlayer 5.0 Audioengine A5 ( passive mode )
    Raspberry Pi 2 B, HiFiBerry Dac+ & Max2play
    HTC 10 w/ Squeeze Ctrl
    ReadyNAS 516 LMS 7.9.2 nightly

  8. #8
    Senior Member
    Join Date
    Jun 2012
    Posts
    250
    Insitu isn't showing up the 5.0 option for me. I've run the hotfix to 4.1.2, but only seeing 4.0.0 and 4.1.0 as options for update

    Code:
    [ INFO ] Internet accessible.
    [ INFO ] pCP repository accessible.
    [ INFO ] You are currently using piCorePlayer v4.1.2
    [ INFO ] Step 1. - Downloading insitu.cfg...
    [  OK  ] Successfully downloaded insitu.cfg

  9. #9
    Senior Member
    Join Date
    Mar 2010
    Posts
    114
    I'll investigate more tomorrow, but for now I'm back on beta 9:
    With 5.0.0, WIFI was flaky - slow ssh, sometimes the player even dropped out from being listed in the LMS web interface. Issues disappeared when I rebooted into b9.


    Gesendet von iPad mit Tapatalk

  10. #10
    Senior Member
    Join Date
    Mar 2010
    Posts
    114
    Quote Originally Posted by pputzer View Post
    I'll investigate more tomorrow, but for now I'm back on beta 9:
    With 5.0.0, WIFI was flaky - slow ssh, sometimes the player even dropped out from being listed in the LMS web interface. Issues disappeared when I rebooted into b9.
    Just to be sure, I re-installed the audio kernel image and only added the iperf3 package before running the diagnostics:

    Code:
    Test Complete. Summary Results:
    [ ID] Interval           Transfer     Bitrate         Jitter    Lost/Total Datagrams
    [  5]   0.00-21.21  sec   759 MBytes   300 Mbits/sec  0.000 ms  0/555748 (0%)  sender
    [  5]   0.00-21.00  sec   148 MBytes  59.2 Mbits/sec  0.174 ms  436688/544068 (80%)  receiver
    CPU Utilization: local/receiver 6.0% (0.7%u/5.3%s), remote/sender 0.8% (0.1%u/0.7%s)
    Where as with beta 9, I get the following results:
    Code:
    Test Complete. Summary Results:
    [ ID] Interval           Transfer     Bitrate         Jitter    Lost/Total Datagrams
    [  5]   0.00-21.12  sec   755 MBytes   300 Mbits/sec  0.000 ms  0/550827 (0%)  sender
    [  5]   0.00-21.00  sec   265 MBytes   106 Mbits/sec  0.084 ms  355604/547567 (65%)  receiver
    CPU Utilization: local/receiver 21.6% (2.7%u/18.9%s), remote/sender 0.7% (0.1%u/0.6%s)
    Both are with the default "download" setting. When running iperf3 from the command line using soundcheck's settings (i.e. non-reverse mode, CLI command "iperf3 -c 192.xxx.xxx.xx -V -i 1 -A 1 -u -b 0 -t 60"), I get the following results onon 5.0.0:
    Code:
    Test Complete. Summary Results:
    [ ID] Interval           Transfer     Bitrate         Jitter    Lost/Total Datagrams
    [  5]   0.00-60.00  sec   811 MBytes   113 Mbits/sec  0.000 ms  0/586940 (0%)  sender
    [  5]   0.00-60.08  sec   160 MBytes  22.3 Mbits/sec  0.378 ms  471148/586935 (80%)  receiver
    CPU Utilization: local/sender 6.8% (0.5%u/6.3%s), remote/receiver 0.3% (0.0%u/0.2%s)
    And on beta 9:
    Code:
    Test Complete. Summary Results:
    [ ID] Interval           Transfer     Bitrate         Jitter    Lost/Total Datagrams
    [  5]   0.00-60.00  sec   838 MBytes   117 Mbits/sec  0.000 ms  0/606790 (0%)  sender
    [  5]   0.00-60.05  sec   838 MBytes   117 Mbits/sec  0.219 ms  1/606779 (0.00016%)  receiver
    CPU Utilization: local/sender 21.0% (1.4%u/19.7%s), remote/receiver 1.1% (0.2%u/0.9%s)
    Edit: Doh! I forgot to change the WIFI country code. No wonder there were issues
    Last edited by pputzer; 2019-06-10 at 04:44. Reason: Found out what I did wrong

Posting Permissions

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