How is the Pi 4?

[TomJ]

So Squeezelite is included in the modified piCorePlayer release, but not the newest version from Klaus?

What kind of RPI 4 do you recommend? 2GB or 4GB? 

[seeteeyou]

On 1/30/2021 at 7:50 PM, TomJ said:

So Squeezelite is included in the modified piCorePlayer release, but not the newest version from Klaus?

 

Bingo, it wouldn't be appropriate to include the work of another developer.

 

FYI - someone else also tried those tweaks provided by Klaus

 

https://soundcheck-audio.blogspot.com/p/in-part-2-of-project-i-address-setup-of.html

Quote

I have implemented all your software tweaks on the streamer side and took the advise to move the server side from a nas to a rpi4 with a rock solid power supply. The results are stunning!
Soundstage is bigger, far more low level details i can hear now, sound is silky smooth and i can go on...
If this was the result of upgrading a Dac from €500,- to a €1000,- Dac i would be very very pleased! I can not really get my head around why the results are so good... Especially compiling your own kernel makes a big step. How? Why? I can not tell.. but it works big time ;-)
Your tweaks are very much recommended.
Thank you for your effort.

 

https://soundcheck-audio.blogspot.com/p/soundchecks-tass-intro.html

Quote

The Audio Streaming Series is meant to encourage and support fellow audio enthusiasts in building their very own highest quality Raspberry PI based audio streaming solution.

 

---

 

Klaus also announced the beta release of his tuning kit for piCorePlayer this week

 

https://soundcheck-audio.blogspot.com/2021/02/introducing-pcp-toolbox-beta.html

Quote

Note: sKit incorporates some important recent changes also announced in the Audio Streaming Series. It also provides some workarounds for recently discovered pCP related flaws.

 

https://soundcheck-audio.blogspot.com/p/the-skit-pcp.html

Quote

sKit provides a small set of tools to customize and enhance the piCorePlayer base OS.
All tools are supporting RPi3, RPi4 and related CM modules. The tool set supports 32-bit and 64-bit pCP versions.

 

https://soundcheck-audio.blogspot.com/p/the-pcp-toolbox.html

Quote

Works great on a AlloBridge with a Rpi 3CM module.
I did have to extend file system to 500Mb, but after that smooth install and great sound.
Thanks!

 

---

 

On 1/30/2021 at 7:50 PM, TomJ said:

What kind of RPI 4 do you recommend? 2GB or 4GB? 

 

https://soundcheck-audio.blogspot.com/p/in-part-2-of-project-i-address-setup-of.html

Quote

If you run the PI4 as client 1GB is usually sufficient. If you consider to use the PI4 also as server or even later as desktop machine it'd be not a bad idea to go for 2/4/8 GB. 2gig is very interesing from a price point nowadays and will also cover most server duties. If you consider desktop duties 4gig is the minimum. If you go 8g you need the new 64bit Rasberry Pi OS.

Make sure though you'll get the latest RPI HW batch!

 

---

 

There's yet another updated version of piCorePlayer available since the end of January, the author managed to achieve even better sound quality by further optimizing the kernel 

 

http://www.stsd99.com/phpBB3/viewtopic.php?p=19458#p19458

https://raw.githubusercontent.com/sam0402/pcp-44.1KHz/master/piCorePlayer6.1.0-Noel.zip

https://raw.githubusercontent.com/sam0402/pcp-44.1KHz/master/piCorePlayer6.1.0-Noel.z01

https://raw.githubusercontent.com/sam0402/pcp-44.1KHz/master/piCorePlayer6.1.0-Noel.z02

https://raw.githubusercontent.com/sam0402/pcp-44.1KHz/master/piCorePlayer6.1.0-Noel.z03

 

He mentioned that he might start working on piCorePlayer 7 during the Lunar New Year if time were allowed

 

https://www.my-hiend.com/vbb/showthread.php?13157-piCorePlayer6-1-0-Xenomai-44-1-48KHz雙機入門簡易安裝教學&p=243416#post243416

[al2813]

Hi, first of all many thanks to seeteeyou for these detailed accounts and information collected and presented here! 

I recieved this weekend a real surprise in form of the Teradak TDA1387 HAT DAC. Just with Moodeaudio with no tweaks and allo Nirvana power supply, I got really nice results (albeit streaming from a decently built Euphony Roon server with an endpoint squeezlite). This gives me the appetite to explore this further. A few questions to those who already tested: 

 

- Would a RPI 4 rev 1.2 with 2GB be sufficient, or do I need to get a 4gb ram one? 

- Cooling - I just have heat sinks on the Pi and I keep it with a simple acrylic stack structure - Do I need something more serious. Of course I want to stay fanless? 

- What is the optimal setup the base Noel Picoreplayer + Soundcheck twaeked Squeezelite?I got confused with the latest Soundcheck tweaks as I am not sure anymore how to proceed? 

- Over the weekend I did a quick install but could not get the DAC to work. In Moode and Volumio I select Hifiberry DAC. Any idea what I need to select in PCP? 

- And finally, I am considering adding Allo Kali Reclocker which some users reported as adding to SQ with the TDA1387, while other tell me they don't think this will make any changes. If anyone has any feedback that would be great. My idea is power everything via the Kali. I have a new HDplex 300W LPS delivered this week. 

 

 

 

[seeteeyou]

It looks pretty sweet for 298 RMB (about 50 bucks) a piece, ETA should be August 2021

 

https://item.taobao.com/item.htm?id=650821434968

 

 

[seeteeyou]

Now we've got quite a few styles available, have fun

 

https://www.stsd99.com/phpBB3/viewtopic.php?p=19929#p19929

https://raw.githubusercontent.com/sam0402/pcp-44.1KHz/master/pCP610-Quantum_DuoGaN.img.7z.001

https://raw.githubusercontent.com/sam0402/pcp-44.1KHz/master/pCP610-Quantum_DuoGaN.img.7z.002

https://raw.githubusercontent.com/sam0402/pcp-44.1KHz/master/pCP610-Quantum_DuoGaN.img.7z.003

 

That's accomplished by swapping different copies of the following libasound.tcz file

 

http://forum.tinycorelinux.net/index.php?topic=6197.0

http://picoreplayer.sourceforge.net/tcz_repo/12.x/aarch64/tcz/libasound.tcz.info

[bodiebill]

On 10/13/2020 at 2:13 PM, seeteeyou said:

Another one from Japan called lightMPD

 

https://groups.google.com/forum/#!topic/lightmpd/JsN0Tw-p2v0

https://drive.google.com/file/d/1v0pM5Q7ieP57tvmvaxoFQJM7c53SXiAT/view

 

Finally symphonic mpd is optimized for I2S HATs and only wired network connections are supported, no USB audio and no Wi-Fi at all

 

https://www.stereo.net.au/forums/topic/317583-journeys-with-a-pi-from-a-standing-start-to-symphonic-mpd/?tab=comments#comment-4581125

https://www.facebook.com/565378050602738/posts/965376323936240

https://www.youtube.com/watch?v=sEkcPvplElY

 

 

So, thanks to @seeteeyou I had a look at Symphonic mpd (smpd) and LightMPD, trying to make sense of the webpages translated from Japanese. I managed to get smpd to work but given that it deactivates all usb ports, I had to play from NAS via the network, and SQ in that case is considerably less than moOde playing files from a local usb disk.

 

I did understand that there is an option to use two rpi's (as in router --> rpi1 --> rpi2 --> DAC) to isolate the 2nd rpi and DAC from the network, but could not find out how this can be done. Wouldn't it be nice to have an rpi version of the dual PC JPLAY setup? Anyone has experience with this?

[seeteeyou]

https://audiophilestyle.com/forums/topic/55235-gentooplayer/page/110/#comment-1166295

On 11/6/2021 at 3:18 AM, falco henri said:

Hi guys,

Just to Say how play2dir and moc player sound Amazing with an allo usbridge SIG. For me the best quality sound on a RPI ! Better than all others players.... If the quality sound IS the more important for you try play2dir with MOC player and enjoy it !

 

FYI - that should be fairly similar to wtfplay or Console Album Player etc.

 

https://sites.google.com/view/gentooplayer-documentation/info-software/moc-player

https://sourcedigit.com/22078-command-line-music-player-moc-music-on-console-linux/

 

Source code could be found below

 

https://github.com/jonsafari/mocp

https://github.com/antonellocaroli/mocp1

http://ftp.daper.net/pub/soft/moc/unstable/moc-2.6-alpha3.tar.xz

 

While binaries could be extracted from Debian packages

 

https://launchpadlibrarian.net/490740103/moc_2.6.0~svn-r3005-1_arm64.deb

https://launchpadlibrarian.net/490740101/moc-ffmpeg-plugin_2.6.0~svn-r3005-1_arm64.deb

 

http://http.us.debian.org/debian/pool/main/m/moc/moc_2.6.0~svn-r3005-1_arm64.deb

http://http.us.debian.org/debian/pool/main/m/moc/moc-ffmpeg-plugin_2.6.0~svn-r3005-1_arm64.deb

 

https://www.deb-multimedia.org/pool/main/m/moc-dmo/moc_2.6.0~svn3005.20190914-dmo1_arm64.deb

https://www.deb-multimedia.org/pool/main/m/moc-dmo/moc-ffmpeg-plugin_2.6.0~svn2984.20180805-dmo2_arm64.deb

 

Or extracted from GentooPlayer itself

 

https://drive.google.com/file/d/1kMMXoz7L3TAOfRgLSwrmWwzy2peh59TA/view

 

(Simply find anything related to moc or mocp)

 

GentoPlayerRpi4-64-6.40.img.xz → GentoPlayerRpi4-64-6.40.img → 1.img

 

---

 

The latest and greatest Linux distro of choice should be this particular version of piCorePlayer with 176.4KHz kernel timer frequency

 

https://www.stsd99.com/phpBB3/viewtopic.php?p=20326#p20326

 

Whole bunch of copper heat sinks for adequate cooling since we're going for lower latency with a (much) higher kernel timer frequency

 

https://www.mobile01.com/topicdetail.php?f=348&t=5840425&p=59#83400362

[seeteeyou]

https://audiophilestyle.com/forums/topic/27123-wtfplay/page/21/#comment-1166680  

On 11/9/2021 at 2:20 AM, bodiebill said:

Agreed. Or perhaps I would sooner downgrade (use a low-footprint NUC, underclock, lower voltage, etc.) than upgrade for best results with wtfplay.

 

If there would be an image for the Raspberry Pi, I would use it!

 

YMMV

 

http://jplay.eu/forum/index.php?/topic/4350-win10-pe-as-audio-os/page-2#entry57337

Quote

It seems to me personally that Win PE is superior to everything I have tried, Windows 10, Server Core 2019, Server Core 2019 in RAM, WTFPlay.
But I think that everyone has to test the different OS and form their own opinion.

 

Basically I just shared the link to this nice little trick to prevent network connections to be initiated in the first place

 

https://serverfault.com/questions/866479/disable-network-connection-in-windows-pe

 

Someone got PE going with Snapdragon 850 and that might also work for Raspberry Pi 4B

 

http://bbs.c3.wuyou.net/forum.php?mod=viewthread&tid=420897

 

This driver might be good since USB Audio already worked under Windows 10 IoT Core

 

https://docs.microsoft.com/en-us/windows-hardware/drivers/audio/usb-2-0-audio-drivers

https://docs.microsoft.com/en-us/windows/iot-core/learn-about-hardware/hardwarecompatlist

https://stackoverflow.com/questions/46487208/windows-iot-raspberry-pi-3-c-sharp-enumerate-usb-audio-adapter

 

XMOS wrote this player and that could be compiled for a processor with different architecture

 

https://github.com/xmos/xplay

[kvad]

On 7/15/2021 at 8:10 AM, seeteeyou said:

It looks pretty sweet for 298 RMB (about 50 bucks) a piece, ETA should be August 2021

 

https://item.taobao.com/item.htm?id=650821434968

 

Did you ever get a chance to test this? Looks like an affordable way of testing a better clock. 

[al2813]

This morning I tried to pick up an extra RPI4 as I only have one left after I managed (yes silly me) to fry two units over the past 6 months. Now I regret these accidents even more. It is pretty much impossible to buy a new PI4 board in Western Europe, and those available go for 100 EUR minimum while you could pick up one before for less then 50. 

 

Any alternatives. I want to build an extra streamer (was going to get extra HATs as I want SPDIF out), but no options left for cheap....

 

[firedog]

6 hours ago, al2813 said:

This morning I tried to pick up an extra RPI4 as I only have one left after I managed (yes silly me) to fry two units over the past 6 months. Now I regret these accidents even more. It is pretty much impossible to buy a new PI4 board in Western Europe, and those available go for 100 EUR minimum while you could pick up one before for less then 50. 

 

Any alternatives. I want to build an extra streamer (was going to get extra HATs as I want SPDIF out), but no options left for cheap....

 

What about a late model Pi3+?

You won't really notice any difference, especially if you are using a HAT with SPDIF out.

[al2813]

18 minutes ago, firedog said:

What about a late model Pi3+?

You won't really notice any difference, especially if you are using a HAT with SPDIF out.

 

Right now the situation is pretty dramatic. No new boards and 2nd hand we're seeing prices going up to 100 EUR. As I know there are a lot of SBCs out there I am curious to see if any of them can support HATs and the audiophile OSs - I know the Asus Tinkerboard for example, but this one also goes for 100+ as far as I know. 

[adosero]

What do you think about the new pi zero 2w? Seems like there is more availability for  it.

[bobfa]

I have just settled on the Pi4 to keep the same hardware everywhere.  I have been able to get a couple of them on and off by watching carefully.    

[Zauurx]

I post here (and on DietPi forum).
I am doubtful and without a solution (for the moment).

 

Maybe a kernel problem but it's not my dac.
I use a Musician Pegasus dac (same as Denafrips) with a STM usb chip.
It works with an Allo USBridge under GentooPlayer.
I wanted to test a new Rpi4 with DietPi which I used before and which I find more flexible... but... nothing!!!
No dac detected while everything works with a dac (xmos).
I don't have the skills but I would be surprised if the STM is not in the kernel... there should be a trace.
An "lsusb" does not give nothing.  

 

 

The same thing under GentooPlayer on the USBridge (Pi3+):

- - - 

lsusb

Bus 001 Device 005: ID 152a:8829 Thesycon Systemsoftware & Consulting GmbH USB HiRes Audio
Bus 001 Device 003: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet
Bus 001 Device 002: ID 0451:8142 Texas Instruments, Inc. TUSB8041 4-Port Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
- - - - 

 

Nothing under DietPi v7.8.2 (but same thing with Ropieee Xl, etc).

 

[LondonDan]

On 10/11/2020 at 5:11 PM, seeteeyou said:

 

Yeah, everyone on GitHub must play by the rules by splitting that relatively large piCorePlayer image into 4 parts

 

https://docs.github.com/en/free-pro-team@latest/github/managing-large-files/conditions-for-large-files

 

It's such a nice HAT from Pi 2 Design with fantastic voltage regulators, many of their fans could be found here

 

https://www.superbestaudiofriends.org/index.php?threads/raspberry-pi-i2s-to-spdif-hat.1990/

https://www.superbestaudiofriends.org/index.php?threads/dummies-guide-to-pi2aes-throw-away-your-pc-or-laptop.8878/

 

BTW, recently Ian Canada designed this StationPi and it should be coming in the (near?) future

 

https://www.diyaudio.com/forums/digital-line-level/192465-asynchronous-i2s-fifo-project-ultimate-weapon-fight-jitter-548.html#post6335309

 

I'm thinking of this exact set up, I have looked at Pi2AES but the clocks are not upgradable unless anyone knows that you can?

 

With the Ian Canada Pi Station, Fifo Pi Q3 and transport, the clocks are upgradable. Anyone seen / heard upgrades to this clocks above the 45-49 MHz standard most blogs report on? looking into ocxo or xo clocks. what is the top level you can get to this set up without going to external clock board. I see accusilicon  90Mhz and 98 MHz clocks could be a good option but any other suggestions for good clocks under £150 each?

 

Then onto power supply must the clean side for the fifo pi q3 always be 3.3v or could it be higher? if the higher quality ocxo clocks were put in what would be the power requirements here\? still 3.3v? 

 

Is there another top quality system pr Pi 4 B to clock and get Spdif out in a great way? I like the look of the Pi 2 design products including the Pi2AES and the upcoming mercury but not sure because you can't up spec the clocks and the 24v means I need a special LPS.

 

 

[seeteeyou]

On 12/6/2021 at 10:39 PM, Zauurx said:

lsusb

Bus 001 Device 005: ID 152a:8829 Thesycon Systemsoftware & Consulting GmbH USB HiRes Audio
Bus 001 Device 003: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet
Bus 001 Device 002: ID 0451:8142 Texas Instruments, Inc. TUSB8041 4-Port Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

 

https://dietpi.com/phpbb/viewtopic.php?t=9748

 

Congratulations, that's exactly what we're looking for because they're licensing USB driver from Thesycon

 

https://aoshida-audio.com/products/musician-pegasus

Quote

Licensed Thesycon USB Driver For Windows Platform

 

https://github.com/torvalds/linux/blob/master/sound/usb/quirks.c

Quote

VENDOR_FLG(0x152a, /* Thesycon devices */

 

http://www.linux-usb.org/usb.ids

Quote

152a  Thesycon Systemsoftware & Consulting GmbH

 

https://www.xmos.ai/software/usb-audio/driver-support/

Quote

Production (Thesycon Driver)

 

---

 

https://www.xingcore.com/?page_id=12

https://audiophilestyle.com/forums/topic/61945-usb-interface-into-the-mix/#comment-1108274

https://audiophilestyle.com/forums/topic/58164-building-a-diy-music-server/page/78/#comment-1115931

 

Pretty much the same deal for both Musician Audio and Denafrips, everything should be done by XING in the first place

 

https://www.denafrips.com/firmware-update-usb

 

FYI - XING provided this utility and its "USB Descriptor" tab could allow us to change anything we want as shown below

 

https://www.head-fi.org/threads/xingcore-af200-configuration-for-iis-port.960369/#post-16688375

[seeteeyou]

On 11/23/2021 at 5:01 AM, kvad said:

Did you ever get a chance to test this? Looks like an affordable way of testing a better clock. 

 

That's pretty much what my game plan back then because plenty of audiophiles here in Asia seemed to have only positive things to talk about the SQ afterwards.

 

However, recently someone who already upgraded 3 units of Raspberry Pi 4B with the same Solid Copper Maker Block Case (i.e. 250 bucks × 3 = $750) just tried Intel NUC D34010WYB with Arch Linux (highly optimized kernel version 5.15 with Xenomai 4 / EVL and 176.4kHz kernel timer frequency) was quite impressed by the performance in spite of having pretty darn old hardware

 

https://www.my-hiend.com/vbb/showthread.php?13157-piCorePlayer6-1-0-Xenomai-44-1-48KHz雙機入門簡易安裝教學&p=245441#post245441

 

Then he tried another Mini-ITX motherboard / i5-8500T / Corsair AX1600i etc. and that's getting even better

 

https://www.my-hiend.com/vbb/showthread.php?13157-piCorePlayer6-1-0-Xenomai-44-1-48KHz雙機入門簡易安裝教學&p=245453#post245453

 

He's running Daphile on the same machine / ATX PSU before and that kinda "plain vanilla" kernel should be nothing to write home about, it's a totally different story once he received the instructions to install another operating system with a much better kernel.

 

So basically he mentioned that he could no longer go back to Pi 4 (despite the fact that he's also running piCorePlayer 8.0.0 with Xenomai 4 / EVL and 176.4kHz kernel timer frequency from the same developer) anymore after realizing what one could accomplish with more powerful hardware. Other "hardcore" fans of pCP also reported similar results with Arch Linux while personally I'm also planning to jump ship myself.

 

The kernel itself might be cut from the same cloth since both of them were created by the same developer to begin with, though the performance (or lack thereof) of BCM2711 could very well be the bottleneck once we dial up the kernel time frequency from 44.1kHz to 176.4kHz. It's quite taxing for the SoC already and passive cooling might not be able to cut it unless we're having to something to that Solid Copper Maker Block Case.

 

I really don't mean to bash Pi 4 on this thread by any means, though it's certainly a stepping stone for that developer to learn what he could actually do about tweaking the kernel while giving everything away for free.

[Zauurx]

@seeteeyou :  Thank you for the consideration, but in the end, how can I manage to get the Pegasus recognized by his RPI4.
I'm not sure how I'll be able to do this.
What I don't understand is that it works with RPI3 under GentooPlayer and not under DietPi (for example).
Kernel problem or, to be recognized by any distribution (and kernel), change the descriptor to a generic USB-audio descriptor ?
And all this, without bricking my dac 😉

 

Musician and Denafrips claim a "linux driverless".

[seeteeyou]

Sometimes running lsusb alone might not be sufficient for troubleshooting, see my post below and then post some links to PasteBin

 

https://audiophilestyle.com/forums/topic/64016-diy-server-and-streamer-systems/page/2/#comment-1173271

[Zauurx]

@seeteeyou
 

Things are moving forward... but I don't know how to fix them.
The Pegasus is present, detected at boot ... but no permanent identification and it disappears.

This is what "dmesg|grep USB" does:
 

root@DietPi:~# dmesg|grep USB
[    0.701634] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 1
[    0.702606] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.10
[    0.702613] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.702945] hub 1-0:1.0: USB hub found
[    0.703356] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 2
[    0.703365] xhci_hcd 0000:01:00.0: Host supports USB 3.0 SuperSpeed
[    0.703569] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.10
[    0.703575] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.703859] hub 2-0:1.0: USB hub found
[    0.709577] usbhid: USB HID core driver
[    0.963227] usb 1-1: new high-speed USB device number 2 using xhci_hcd
[    1.113882] usb 1-1: New USB device found, idVendor=2109, idProduct=3431, bcdDevice= 4.21
[    1.113890] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[    1.113896] usb 1-1: Product: USB2.0 Hub
[    1.115068] hub 1-1:1.0: USB hub found
[    1.415238] usb 1-1.3: new high-speed USB device number 3 using xhci_hcd
[    1.520154] usb 1-1.3: New USB device found, idVendor=152a, idProduct=8829, bcdDevice= 3.12
[    1.520165] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    1.520170] usb 1-1.3: Product: USB HiRes Audio
[    2.869119] usb 1-1.3: USB disconnect, device number 3
[    3.099249] usb 1-1.3: new high-speed USB device number 4 using xhci_hcd
[    3.204148] usb 1-1.3: New USB device found, idVendor=152a, idProduct=8829, bcdDevice= 3.12
[    3.204176] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    3.204182] usb 1-1.3: Product: USB HiRes Audio
[    3.893112] usb 1-1.3: USB disconnect, device number 4
[    4.123225] usb 1-1.3: new high-speed USB device number 5 using xhci_hcd
[    4.224052] usb 1-1.3: New USB device found, idVendor=152a, idProduct=8829, bcdDevice= 3.12
[    4.224059] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    4.224065] usb 1-1.3: Product: USB HiRes Audio
[    4.661206] usb 1-1.3: USB disconnect, device number 5
[    4.883245] usb 1-1.3: new high-speed USB device number 6 using xhci_hcd
[    5.380040] usb 1-1.3: New USB device found, idVendor=152a, idProduct=8829, bcdDevice= 3.12
[    5.380047] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    5.380053] usb 1-1.3: Product: USB HiRes Audio
[    6.709477] usb 1-1.3: USB disconnect, device number 6
[    6.931225] usb 1-1.3: new high-speed USB device number 7 using xhci_hcd
[    7.636104] usb 1-1.3: New USB device found, idVendor=152a, idProduct=8829, bcdDevice= 3.12
[    7.636112] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    7.636117] usb 1-1.3: Product: USB HiRes Audio
[    8.757841] usb 1-1.3: USB disconnect, device number 7
[    8.979283] usb 1-1.3: new high-speed USB device number 8 using xhci_hcd
[    9.476135] usb 1-1.3: New USB device found, idVendor=152a, idProduct=8829, bcdDevice= 3.12
[    9.476147] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    9.476154] usb 1-1.3: Product: USB HiRes Audio
[    9.781984] usb 1-1.3: USB disconnect, device number 8
[   10.007225] usb 1-1.3: new high-speed USB device number 9 using xhci_hcd
[   10.108046] usb 1-1.3: New USB device found, idVendor=152a, idProduct=8829, bcdDevice= 3.12
[   10.108054] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   10.108060] usb 1-1.3: Product: USB HiRes Audio
[   10.806114] usb 1-1.3: USB disconnect, device number 9
[   11.027225] usb 1-1.3: new high-speed USB device number 10 using xhci_hcd
[   11.524079] usb 1-1.3: New USB device found, idVendor=152a, idProduct=8829, bcdDevice= 3.12
[   11.524093] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   11.524099] usb 1-1.3: Product: USB HiRes Audio
[   11.830299] usb 1-1.3: USB disconnect, device number 10
[   12.055225] usb 1-1.3: new high-speed USB device number 11 using xhci_hcd
[   12.839236] usb 1-1.3: new high-speed USB device number 12 using xhci_hcd
[   12.940053] usb 1-1.3: New USB device found, idVendor=152a, idProduct=8829, bcdDevice= 3.12
[   12.940060] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   12.940066] usb 1-1.3: Product: USB HiRes Audio
[   13.109950] usb 1-1.3: USB disconnect, device number 12
[   13.331225] usb 1-1.3: new high-speed USB device number 13 using xhci_hcd
[   13.436104] usb 1-1.3: New USB device found, idVendor=152a, idProduct=8829, bcdDevice= 3.12
[   13.436116] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   13.436122] usb 1-1.3: Product: USB HiRes Audio
[   14.902741] usb 1-1.3: USB disconnect, device number 13
[   15.355224] usb 1-1.3: new high-speed USB device number 14 using xhci_hcd
[   15.456158] usb 1-1.3: New USB device found, idVendor=152a, idProduct=8829, bcdDevice= 3.12
[   15.456171] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   15.456177] usb 1-1.3: Product: USB HiRes Audio
[   16.438953] usb 1-1.3: USB disconnect, device number 14
[   16.663225] usb 1-1.3: new high-speed USB device number 15 using xhci_hcd
[   16.764104] usb 1-1.3: New USB device found, idVendor=152a, idProduct=8829, bcdDevice= 3.12
[   16.764112] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   16.764118] usb 1-1.3: Product: USB HiRes Audio
[   17.207048] usb 1-1.3: USB disconnect, device number 15
[   17.431226] usb 1-1.3: new high-speed USB device number 16 using xhci_hcd
[   17.532035] usb 1-1.3: New USB device found, idVendor=152a, idProduct=8829, bcdDevice= 3.12
[   17.532047] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   17.532053] usb 1-1.3: Product: USB HiRes Audio
[   18.487273] usb 1-1.3: USB disconnect, device number 16
[   18.711225] usb 1-1.3: new high-speed USB device number 17 using xhci_hcd
[   19.495244] usb 1-1.3: new high-speed USB device number 18 using xhci_hcd
[   19.596090] usb 1-1.3: New USB device found, idVendor=152a, idProduct=8829, bcdDevice= 3.12
[   19.596101] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   19.596107] usb 1-1.3: Product: USB HiRes Audio
[   20.023487] usb 1-1.3: USB disconnect, device number 18
[   20.247225] usb 1-1.3: new high-speed USB device number 19 using xhci_hcd
[   20.348056] usb 1-1.3: New USB device found, idVendor=152a, idProduct=8829, bcdDevice= 3.12
[   20.348064] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   20.348069] usb 1-1.3: Product: USB HiRes Audio
[   21.047615] usb 1-1.3: USB disconnect, device number 19
[   21.691233] usb 1-1.3: new high-speed USB device number 20 using xhci_hcd
[   21.792100] usb 1-1.3: New USB device found, idVendor=152a, idProduct=8829, bcdDevice= 3.12
[   21.792108] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   21.792114] usb 1-1.3: Product: USB HiRes Audio
[   22.327802] usb 1-1.3: USB disconnect, device number 20
[   22.551257] usb 1-1.3: new high-speed USB device number 21 using xhci_hcd
[   22.651993] usb 1-1.3: New USB device found, idVendor=152a, idProduct=8829, bcdDevice= 3.12
[   22.652002] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   22.652008] usb 1-1.3: Product: USB HiRes Audio
[   23.351988] usb 1-1.3: USB disconnect, device number 21
[   23.575245] usb 1-1.3: new high-speed USB device number 22 using xhci_hcd
[   23.676034] usb 1-1.3: New USB device found, idVendor=152a, idProduct=8829, bcdDevice= 3.12
[   23.676042] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   23.676047] usb 1-1.3: Product: USB HiRes Audio
[   24.120054] usb 1-1.3: USB disconnect, device number 22
[   24.343225] usb 1-1.3: new high-speed USB device number 23 using xhci_hcd
[   24.444070] usb 1-1.3: New USB device found, idVendor=152a, idProduct=8829, bcdDevice= 3.12
[   24.444077] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   24.444083] usb 1-1.3: Product: USB HiRes Audio
[   25.399772] usb 1-1.3: USB disconnect, device number 23
[   25.627256] usb 1-1.3: new high-speed USB device number 24 using xhci_hcd
[   25.727997] usb 1-1.3: New USB device found, idVendor=152a, idProduct=8829, bcdDevice= 3.12
[   25.728005] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   25.728011] usb 1-1.3: Product: USB HiRes Audio
[   27.448118] usb 1-1.3: USB disconnect, device number 24
[   27.671235] usb 1-1.3: new high-speed USB device number 25 using xhci_hcd
[   27.772102] usb 1-1.3: New USB device found, idVendor=152a, idProduct=8829, bcdDevice= 3.12
[   27.772110] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   27.772115] usb 1-1.3: Product: USB HiRes Audio
[   28.472745] usb 1-1.3: USB disconnect, device number 25
[   28.695236] usb 1-1.3: new high-speed USB device number 26 using xhci_hcd
[   28.796026] usb 1-1.3: New USB device found, idVendor=152a, idProduct=8829, bcdDevice= 3.12
[   28.796033] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   28.796040] usb 1-1.3: Product: USB HiRes Audio
[   29.240331] usb 1-1.3: USB disconnect, device number 26
[   29.899232] usb 1-1.3: new high-speed USB device number 27 using xhci_hcd
[   30.000155] usb 1-1.3: New USB device found, idVendor=152a, idProduct=8829, bcdDevice= 3.12
[   30.000164] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   30.000170] usb 1-1.3: Product: USB HiRes Audio
[   30.264905] usb 1-1.3: USB disconnect, device number 27
[   30.487225] usb 1-1.3: new high-speed USB device number 28 using xhci_hcd
[   31.479219] usb 1-1.3: new high-speed USB device number 29 using xhci_hcd
[   32.184031] usb 1-1.3: New USB device found, idVendor=152a, idProduct=8829, bcdDevice= 3.12
[   32.184038] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   32.184044] usb 1-1.3: Product: USB HiRes Audio
[   32.825373] usb 1-1.3: USB disconnect, device number 29
[   33.047225] usb 1-1.3: new high-speed USB device number 30 using xhci_hcd
[   33.148063] usb 1-1.3: New USB device found, idVendor=152a, idProduct=8829, bcdDevice= 3.12
[   33.148070] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   33.148076] usb 1-1.3: Product: USB HiRes Audio
[   33.593461] usb 1-1.3: USB disconnect, device number 30

... etc ...

 

[seeteeyou]

https://community.roonlabs.com/t/roon-endpoint-dropping-connections-with-denafrips-pontus-ii-dac/166508/2

Quote

The Denafrips is known for having issues (on Linux). I see it constantly disconnecting and reports about formats not supported. See if you can find a firmware update for the device.

 

Then I also read your post below

 

https://www.head-fi.org/threads/musician-audio-pegasus-r2r-dac.942618/page-41#post-16626895

 

Does / did USB MCU v3.12.0.zip make it better or worse?

 

https://www.denafrips.com/firmware-update-usb

Quote

- Date 29th Nov 2021 
- Compatible with macOS / winOS / Linux  
- Improved low level STM MCU32 USB handshake with host
- Supports PCM1536 / DSD1024

 

V3.12 seemed to have something to do with USB port compatibility as mentioned below

 

https://www.xingcore.com/?page_id=10

 

BTW, other users of Pi 4 seemed to have better luck after updating the EEPROM

 

Raspberry Pi 4/400 Bootloader Firmware Update/Recovery Guide
https://jamesachambers.com/raspberry-pi-4-bootloader-firmware-updating-recovery-guide/

[Zauurx]

Thanks Seeteeyou, but if you read you can see in the log :

 

[    1.415238] usb 1-1.3: new high-speed USB device number 3 using xhci_hcd
[    1.520154] usb 1-1.3: New USB device found, idVendor=152a, idProduct=8829, bcdDevice= 3.12
[    1.520165] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    1.520170] usb 1-1.3: Product: USB HiRes Audio
[    2.869119] usb 1-1.3: USB disconnect, device number 3

 

I already have the latest firmware... "bcdDevice= 3.12".
The dac is detected but then disconnected.
And I did an update of the RPI4 eeprom.
Frankly surprising, especially since it works without a problem with an RPI3.

 

[seeteeyou]

Hence my question as I stated above, did V3.12 actually make things worse or better? I couldn't tell if previous ones were making any differences or not.

 

Compatibility could lead to a tricky situation, sometimes it's a combination of different hardware / different version of firmware / different releases of software / different kernel versions / different cables (with or without +5V VBUS) etc.

 

If XHCI (USB 3.0 with VL805 from VIA Labs) were no good, how about EHCI (USB 2.0) then?

 

And then in some cases incompatibility issues related to USB might be resolved by adding USB hubs of some sort

 

https://audiophilestyle.com/forums/topic/38110-innuos-zenith-se-mkii/page/14/#comment-838015

 

Stuff like symphonic-mpd wouldn't work very well with the latest version of rpi-eeprom at all, while downgrading to an older version would work just fine. Even the revision (1.2 versus 1.4) of Pi 4 seemed to make a difference.

 

There's also something about newer versus older stepping as well

 

https://www.jeffgeerling.com/blog/2021/raspberry-pi-4-model-bs-arriving-newer-c0-stepping

 

Finally how about running dmesg | grep -i usb again with a different distro other than Volumio? Not sure if / ALSA / JACK / PulseAudio were behaving any differently

 

https://linuxmusicians.com/viewtopic.php?t=20370

[seeteeyou]

V3.12.0 ain't even any good under Windows, duh

 

http://jplay.eu/forum/index.php?/topic/3687-denafrips-usb-driver/?p=57873

Quote

okay, its not usb drivers, its  USB MCU FIRMWARE UPDATE.  Last version 3.6.0 work fine with asio JPLAY DRIVER, but new version 3.12.0 didn't work at all.  Jplaymini everytime get error "dac star fail"