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.
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?
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.
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!
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.
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:
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:
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?
Good: build is complete & everything seems to be working nicely; too soon to evaluate audible changes
Questionable: get SIGNIFICANT pop upon first start clicking play in Roon – loud enough that failing to turn down gain prior to start could damage speakers. Have used several other Roon endpoints/streamers including R-Pi’s (with various hats) WiiM, FiiO, iFi Zen, and Bluesound. Have not experienced said pop with any of those over 2-3 years. Ideas of source?
NOTE 1: No pop if queue paused and restarted.
NOTE 2: Outputting from Target thru SMSL PO100 PRO to either Toslink or coax to audio-interface/DAC (Motu 828).
I’ve not experienced this, and no one else has reported this issue. If you move the USB cable to from the Target to the Host, do you still have the issue? Can you try it without the SMSL DDC?
With SMSL, pop is output on both coax and Toslink.
Before investing time on other tests, I took the path of least resistance/work (and quickest – for me) and substituted the Douk Audio U2 PRO DDC I have on hand. No pop on either SPDIF connection on the Motu interface.
Tonight will try outputting to other DACs I have on hand with USB inputs in attempt to start isolating root cause. (Will have to pull DACs out of storage boxes.)
You suggested to “move the USB cable from the Target to the Host”. That confuses me. Does the Host output the digital stream to USB – as in simultaneous/parallel to the Target USB?
Installing Digital Audio Hat on Target to Get SPDIF Outputs on Target?
I have multiple Pi hats to choose from including a Pi2AES-LITE and a couple of HifiBerry Digi2-Pro HW 2.2’s. If I could use any of those, I would not need any DDC between the Target and my interface.
A DIGI HAT may be worth a try. Some folks have reported success. I’ve not had much luck optimizing sound quality with my Pi2AES Pro HAT. It was unstable with DSD64 over DoP when I tried it also.
@David_Snyder Thanks for your excellent guide! My 2x rpi5 with AudioLinux license got up and running at once as RAAT/Diretta host and Diretta target. Very happy! I have a Paul Pang Quad switch prior to Diretta Host and a Rockna Wavelight DAC after Diretta Target. I have been testing all tweaks in the guide with success, but need to do more testing regarding enabling Jumbo frames or not. Anyone else here with 2x rpi5 that have tested Jumbo frames?
Glad to hear that you’ve had a good experience so far. Most folks report that working through appendices 8 and 9 (100 Mbps + Jumbo Frames) gives a nice bump up in sound quality. I’ll admit that this is a highly unusual configuration, combing Jumbo Frames with a slower 100 Mbps link. But, it’s the right call for this particular application.
I’m looking forward to your impressions after completing these last two tweaks.
Note: if you have not completed appendices 6 and 7 yet, be sure to do those first.
Jepp, did some more testing on my favorite test tracks today; I will stay on Jumbo frames activated!
Regarding running menu and update, you need to run the sudoer fix script on both Host and Target, any other things you have to typically redo to be sure everything is on track?
I just run the QA scripts in Appendix 5. For any failures, I simply re-run those steps. That’s about it.
Once things are working, I generally recommend on not bothering with updates. Just enjoy.
Since I have committed to maintaining my guide, I run through the entire process from start to finish roughly once/month, but you should just use that time to listen to more music!
This is a great data point for some objective testing that goes beyond the failures to demonstrate value of Diretta thus far! Have you or anyone associated with the Diretta project shown any value of the system at this point (beyond subjective claims, of course!)? I’m still hoping for some kind of setup guide because I can’t quite wrap my head around how connection strategies with widely variable DAC architectures can uniformly benefit from these tweaks. It seems there must be better or lesser improvements and that Diretta architects can give some guidance on these variables?
