On the system updates, my doc covers this:
- Run
menu in the terminal.
- Select INSTALL/UPDATE menu.
- On the next screen, select UPDATE system and let the process complete.
- After the system update finishes, select Update menu from the same screen to get the latest version of the AudioLinux scripts.
- Exit the menu system to get back to the terminal.
I’ve provided Piero with a script for packaging images that flash much faster. I suspect he used the script to create the audiolinux_pi4-pi5_510.img.xz file, which you can download (using password “A”). Raspberry Pi Imager works very well with these *.xz files.
.xz WAY FASTER! Like magnitude faster.
Both the .gz and .xz files were available for download. I downloaded both, but went with the much-more-familiar-to-me .gz for flashing. (Remember, I’m an old, retired IT guy – never encountered .xz till yesterday.) And better still, the .xz variant DOES display progress as percentage rather than as mb’s. Perhaps let folks know about the .xz advantage in the documentation?
AGAIN, thanks for your help and responsiveness.
1 Like
As of yesterday, price difference before shipping was $2 between V2 case ($25@Amazon) vs. adapter ($23@PiShop). But with USPS shipping ($7), the adapter from the PiShop winds up $5 more – not to mention that Amazon will get the case here tomorrow vs. who-knows-when from the increasingly-unreliable USPS.
1 Like
Yeah, I see it now that you point it out. I was following your step-by-step so meticulously so as not to miss anything, and mention of the “menu” wasn’t until step 4, while the download email arrived and was read much sooner. Would any part of the process be compromised if someone did it sooner than step 4 due to the email’s suggestion? (I’m past it now, but some other senior citizen like me could use some clarification.)
NOT complaining, but rather observing/suggesting as you are clearly generous with your knowledge and time. Thanks!
I’m hoping Piero makes the .xz file the default / only file for future releases.
No. And I’ve designed the steps in my doc so that there’s no harm in running them more than once. Helpful if someone loses track of where they are. It’s safe to repeat steps, just to be safe. And, the QA scripts in Appendix 5 will catch any commonly missed steps.
@David_Snyder Again, thanks a million for all your help.
Point-of-confusion (for me & perhaps others with similar experience):
When instructed in step 4.4 to “…run menu in the terminal…select install/update"…” I was confused because all I could see was below:
Being a newbie to this specific experience, I did not notice, nor understand the significance of, the faint “35%” in the lower-right corner. In hindsight, I now understand it was telling me that my menu choices were NOT all visible. (Yeah, large fonts necessary for my septuagenarian eyesight.) Once I mucked around a bit, I accidentally ran across the full menu:
…and there it was!
One more point of disorientation was after choosing “5 INSTALL/UPDATE menu” there was another screen that required clicking [Yes] to get to initiate step 3 - updating the kernel:
I muddled through and got it done (I think) correctly.
I’m sure that seasoned iTerm2/ssh users would know this stuff, but for us new-to-the-experience folks…
Cheers!
Digital Audio Hats or DDC Reclockers to Output Toslink/Coax?
Back in December, a couple of posts mention audio hats on the Target, but no mentions since.
My use case requires a Toslink or Coax output to my audio interface (Motu 828). I have multiple Pi hats to choose from including a Pi2AES-LITE and a couple of HifiBerry Digi2-Pro HW 2.2’s. Anyone have experience with either of these on a Target? Other suggestions/options?
Another option would be to use a reclocker between the Target’s USB output and my interface’s SPDIF inputs. I have both a SMSL PO100 PRO and a Douk Audio U2 PRO on hand. Any experience/suggestions here?
