Actually the people to ask is Spotify themselves.
Hello Harry! @spockfish
Long time no speak. That’s a good thing though - everything has been buttery smooth with me and my old man’s setups
Since I was one of the first to ask you for Pi3 touchscreen support, it’s only right I have a next gen request
Once you finished working with the Allo Gentlemen on bringing RoPieee to Sparky, can you ask them to consider supporting a bigger screen (like 10 inches) that would work with Sparky (and of course your Sparky version of RoPieee…)
Something like an “official” Sparky supported screen that’s out there, so you would also need to support just 1 screen. Just like you only support the official Raspberry Pi 7" screen at the moment…
I’ll be naughty and tag Johan here also… @allo.com
Can you imagine a nice iPad sized screen with bigger cover art !
PS: hope you’re enjoying your Hugo2 !
The Hugo2 is the best hardware I bought since my PMC’s. Awesome device.
I’m running ropieee using a Pi3 with IFI micro idsd. I am running this using an anker powerbank.
When I have to recharge the battery, I’m wondering if there is a recommended sequence for powering down the pi within Ropieee.
Do you have any suggestions?
Basically you can pull the plug. RoPieee is running from RAM, so that should not be a problem.
If you want to ‘feel save’ there’s a ‘shutdown’ button on the advanced tab of the web page.
Would it be possible to add internal temperature to the Information tab? Something like:
I have no idea if it is feasible, but it would be very cool to be able to toggle the display to old school VU meters.
VU Meters, but also some Now Playing text would be the sh17!
Yeah the VU meters would be awesome indeed
Problem is that Roon’s API does not provide (low-level) information about the audio stream to be able to come up with something like this…
allo usbridge would be huge…
My Accuphase E-360 just got a post Christmas present - a DAC-50 card. I’ve now connected Ropieee to it, all works and sounds great, but two small issues:
- DSD Native is not supported
- DAC-50 should support DSD256 but Roon only supports up to DSD128.
Is that something that can be easily addressed? Could you point me to how to configure that, or let me know if you’d need anything from me to make it happen.
Thanks a lot,
Congrats with your Accuphase, awesome machine!
Because DSD-Native is not supported, it uses DoP. And DoP uses standard PCM to encapsulate the DSD, resulting in requiring more bandwith, hence the DSD128.
Now, this can be addressed, but requires the Linux kernel to be patched. That’s doable on it’s own, but it highly depends on the firmware of the DAC’s USB chipset if it will work at all.
Are you familiair with Linux or at least SSH? I can then guide you through some commands that needs to be executed to get an idea if it’s possible to get native DSD working.
Yes if you will briefly describe the concept I’ll find my way around.
Here’s the USB Device ID of the Accuphase DAC-50 card:
idVendor 0x21ed idProduct 0xd37a
and some more output:
T: Bus=01 Lev=02 Prnt=02 Port=02 Cnt=02 Dev#= 4 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=ef(misc ) Sub=02 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=21ed ProdID=d37a Rev=00.01 S: Manufacturer=Accuphase Laboratory, Inc. S: Product=Accuphase USB Audio Product6 C: #Ifs= 3 Cfg#= 1 Atr=80 MxPwr=100mA I: If#=0x0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=00 Prot=00 Driver=usbhid I: If#=0x1 Alt= 0 #EPs= 0 Cls=01(audio) Sub=01 Prot=20 Driver=snd-usb-audio I: If#=0x2 Alt= 0 #EPs= 0 Cls=01(audio) Sub=02 Prot=20 Driver=snd-usb-audio I: Bus=0003 Vendor=21ed Product=d37a Version=0100 N: Name="Accuphase Laboratory, Inc. Accuphase USB Audio Product6" P: Phys=usb-3f980000.usb-1.3/input0 S: Sysfs=/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3:1.0/0003:21ED:D37A.0001/input/input1 U: Uniq= H: Handlers=event1 B: PROP=0 B: EV=1
Ok. I need one more thing, the output of
When playing DSD256 downconverted to DSD128 over DoP:
[root@ropieee ~]# cat /proc/asound/card*/stream* Accuphase Laboratory, Inc. Accuphase USB Audio Product6 at usb-3f980000.usb-1.3 : USB Audio Playback: Status: Running Interface = 2 Altset = 3 Packet Size = 400 Momentary freq = 352800 Hz (0x2c.1999) Feedback Format = 16.16 Interface 2 Altset 1 Format: S16_LE Channels: 2 Endpoint: 3 OUT (ASYNC) Rates: 32000, 44100, 48000, 88200, 96000, 176400, 192000, 352800, 384000 Data packet interval: 125 us Interface 2 Altset 2 Format: S24_3LE Channels: 2 Endpoint: 3 OUT (ASYNC) Rates: 32000, 44100, 48000, 88200, 96000, 176400, 192000, 352800, 384000 Data packet interval: 125 us Interface 2 Altset 3 Format: S32_LE Channels: 2 Endpoint: 3 OUT (ASYNC) Rates: 32000, 44100, 48000, 88200, 96000, 176400, 192000, 352800, 384000 Data packet interval: 125 us
This is unfortunate, because the DAC (or rather the USB chipset) only supports PCM. Normally, to support native DSD on Linux, there should be an altset (normally either 2 or 3), that supports the format DSD_U32_BE (or LE). If that’s being supported then we can patch the Linux kernel.
Best chance you have is contact Accuphase and see if they’ve got a firmware update that fixes this.
Thanks Harry, OK I will reach out to Accuphase but I honestly don’t think they will address this – they’re not famous for firmware updates after releasing their products.
Right. I did receive a response from Accuphase on this:
DAC-50 covers up to the DSD256 of the DSD native. However as mentioned in the owner’s manual, it covers up to DSD128 thru the DoP connection. However it goes up to the DSD256 thru ASIO connection.
Just out of curiosity: RPi / Linux don’t support ASIO, right?
Yeah this is the typical answer
So what they say that they only support native DSD (up to DSD256) on ASIO.
And ASIO is windows only. So there’s the catch.