(03-08-2023, 11:00 PM)Tim Curtis Wrote: Here are the draft release notes for upcoming 8.3.0 release. The first ~pre image is being tested and is looking great :-) 

The changes since last post include: 

- UPD: Improve WiFi section in startup (faster AP mode activation)
- UPD: Update Chip Options help for Piano 2.1 DAC Stereo mode
- FIX: Error not logged when source mount fails
- FIX: Wrong PSK used in saved SSID's

There is also an updated Security section in the Setup Guide. Please read it carefully to understand whats required to setup the pi userid and password, WiFi SSID and password and Access Point password.

SECURITY

The ISO image does not contain the userid pi, SSH service, WiFi SSID or Access
Point password.

- The pi userid/password and WiFi SSID/password can can be created using the
  official Raspberry Pi Imager. Refer to the link below for information on
  operating system security and how to use the Raspberry Pi Imager.
  https://www.raspberrypi.com/news/raspberry-pi-bullseye-update-april-2022/

- The Access Point password can be entered via the WebUI, Network Config screen
  after the system starts or via an edited /boot/moodecfg.ini file. The file is
  described in this document in the CUSTOM CONFIGURATION section.

To access the operating system command console use Secure Shell (SSH). An easy
to use WebSSH terminal is available in System Config.

Release notes

Code:

################################################################################
#
# 2023-MM-DD TC moOde 8.3.0
#
################################################################################

New Features

- NEW: Volume type "CamillaDSP" software volume (64-bit with dither)
- NEW: CamillaDSP Loudness, Volume Control and Polarity Inversion configs
- NEW: Use ALSA instead of MPD to control Hardware volume
- NEW: Monitor in-place update via WebUI Status screen instead of SSH

Audio devices

- NEW: ProtoDAC TDA1387 X8 (I2S)

Security (new image only)

- UPD: The ISO image does not contain the userid pi, SSH service, WiFi SSID or
       Access Point password. Refer to the moOde Setup guide for details on
       how to set these up.

Updates

- UPD: Bump to MPD 0.23.12
- UPD: Bump to bluez-alsa 4.0.0
- UPD: Add CamillaDSP volume support to Airplay and Spotify Connect
- UPD: Add ALSA buffer_time option to MPD Config
- UPD: Add WPA3-Personal Transition Mode to Network Config
- UPD: Add Home button to configs header (returns to Playback view)
- UPD: Add quick jump indexes back to Pi Touch
- UPD: Add AlbumArtist to ashuffle mode to handle same name albums
- UPD: Add moodeutl option for printing ALSA hwparams
- UPD: Add System Config option for downloading the Startup log
- UPD: Improve readability of Receivers modal
- UPD: Improve help text and labels in CamillaDSP Config
- UPD: Improve viewswitch tabs in configs (use icons for mobile)
- UPD: Improve Airplay protocol option
- UPD: Improve WiFi section in startup (faster AP mode activation)
- UPD: Sync CoverView auto and toggle during startup
- UPD: Move Metadata file option to MPD section of Audio Config
- UPD: Update Chip Options help for Piano 2.1 DAC Stereo mode
- UPD: Sort the output from the Wifi SCAN
- UPD: Setup guide to reflect new security information

Bug fixes

- FIX: Session ID missing in moodeutl -i (autocfg-import.php)
- FIX: Mapped ALSA volume not being used to set ALSA volume max
- FIX: Allo Piano 2.1 mixer name "Digital" no longer used by driver
- FIX: Audioinfo does not report renderer info
- FIX: Default thumb image not showing in Queue for UPnP files
- FIX: Format of auto_coverview value in System info
- FIX: Error not logged when source mount fails
- FIX: Wrong PSK used in saved SSID's

(03-09-2023, 08:18 AM)the_bertrum Wrote: If I'm reading the page from raspberrypi.com correctly, then new installations will either have to be done with the Raspberry Pi imager, or have a correctly configured ini file on the SD card in order to create the initial user.  Have I understood that correctly?
Also, what happens in in-place upgrades, I assume the default pi user remains?  If so will the user renaming process work?

(03-09-2023, 11:52 AM)Tim Curtis Wrote: Note that the userid pi should not be renamed because there are still a few hard coded "/home/pi" paths left in the code. A future release will address this :-)

(03-10-2023, 07:41 AM)the_bertrum Wrote: Thanks for the explanation Tim, all very clear now.

Out of interest how is this fact:

(03-09-2023, 11:52 AM)Tim Curtis Wrote: Note that the userid pi should not be renamed because there are still a few hard coded "/home/pi" paths left in the code. A future release will address this :-)

dealt with on new systems where the default user is specified?  Is there still a /home/pi created even without a pi user?

(03-10-2023, 07:41 AM)the_bertrum Wrote: Thanks for the explanation Tim, all very clear now.

Out of interest how is this fact:

(03-09-2023, 11:52 AM)Tim Curtis Wrote: Note that the userid pi should not be renamed because there are still a few hard coded "/home/pi" paths left in the code. A future release will address this :-)

dealt with on new systems where the default user is specified?  Is there still a /home/pi created even without a pi user?