I do have another Isue with the DAC.
While playing an Playlist from Spoty there is always a “KNACK” between the songs. It happens also when i`m changing to the next song. Does anybody has / had this with his DAC?
OS info
Version of Volumio: 3.396
Hostname: jimi
Kernel: 5.10.92-v7l+
Governor: performance
Uptime: 0 days, 2 Hrs, 15 Minutes, 54 Seconds
Audio info
Hw audio configured: Audiophonics I-Sabre ES9028Q2M
Mixer type: Hardware
Number of channels: 2
Supported sample rate: 44100 48000 88200 96000 176400 192000
Board info
Manufacturer: Raspberry Pi Foundation
Model: Raspberry Pi 4 Model B Rev 1.5
Version: b03115
Firmware Version: Jan 20 2022 13:56:48 - bd88f66f8952d34e4e0613a85c7a6d3da49e13e2
The Audiophonics is the only one doing this her @ my home.
I run 3 other DAC with Raspi (Pi 4 with OKTO dac8 Stereo, Pi4 with HiFi Berry DAC Pro + DSP, Pi2 with HiFiberry DAC), none of them shows this Problem with my Playlist.
it seems, @ your replay the volumio statuspage send identical info, but with seek <> 0,
so my dirty hack does not work.
you can test it (client with bash console, replace 10.10.11.122 with your volumio ip):
while true; do wget -O - http://10.10.11.122/api/getState; sleep 1; done
and check the json-payload returned.
changing refreshrate only chagnes the pollingtime like the sleep above,
disabling the comparsion (===) changes everything @ every poll, so the information/text resets.
@philipC regarding the “knack”, I have this issue as well
another issue I have is the de-synchronization of the volume levels when switching from Spotify to the web radio interface (in a browser). I almost blew my ears and loudspeakers when I touched the volume slider in the web interface ! the slider was in a 100% position (to the right) but volume levels where at the same level as in Spotify. As soon as I touched it the volume slider, the actual volume shot to 100% (over 250W) until I immediately moved the slider to the left to reduce the output. This could be quite dangerous, especially when using a powerful amp. It gave me quit a fright to be honest and luckily, no one was in the house at the time.
I would like to elaborate on what happened with the volume in my previous post as I consider this a issue which could have physical consequences for equipment (loudspeakers) but also to the hearing devices of people (ears) and maybe even provoque a malaise (heart attack) if the person has issues with that.
I am using the Audiophonics Evo DAC connected directly to the power amplifier. The DAC controls the volume (i.e. “hardware” setting). Also, volume control by users was deactivated.
But, somehow it was not, since just nudging the volume slider in Spotify or the web interface pushed the volume instantly to 100%. This can’t be right and I hope there will be a fix so the volume is synchronised over all the different services like Spotify, Web interface, etc.
I’ve just installed the latest build and tried it again with the same result as in my previous post.
So, I just wanted to warn you all. If your DAC is controlling the volume directly, be aware. I’ve switched to Dietpi for fear it might happen again until this is fixed.
Since I updated to the latest Volumio version and installed the EVO Sabre plugin my screen is not working anymore. It was with the custom image before.
Well that’s odd. According to this output, the software is running as expected. Sorry for asking this, but are you sure you are using the correct device? It should look like this.
No problem.
3 Solutions for you (ordered by ascending complexity) :
1st option : You can find a “relatively” recent image for this here. Just flash it on a card and you are good to go.
2nd option : If you want the very latest version of Volumio, you can do a manual install on a standard Volumio image following those instructions.
3rd option : If you want it to work as a plugin (with options available in Volumio webUI), I have also been trying to build a Volumio plugin for the RaspDac Mini LCD. It has not been really tested nor deployed anywhere yet, but if you are a bit linux-savy and not afraid of reading a big documentation, you could give it a try.
Everyone else reading this, please do not use any of this on an Evo Sabre.
Having been through the process - taking many hours I have the following walk through comments:
Point to instructions for setup of wi-fi of EVO sabre - this is nowhere to be found!
A screen shot of the OLED screen after booting of EVO-sabre would help.
Under 6 - put open a volmio account top of the list
More empahsis needed (bold?) and explanation of "enable plug in test mode - there are many options on the screen - whicf are needed?
Add that until 4 is compelte you will not see the "Audiophonics Evo Sabre "plug in under system hardware. Do NOT use the Audiophonics ON/OFF plug in - this is not the required plug in
Befroe leaving the plug in screen click “enable”
Reboot the EVO-sabre - the term “remote” is unhelpful
Point to a online file to test (any relevant sound file)
I hope these cooments may ghelp others?
So recently bought this Evo-Sabre. On the whole it’s a very good setup. However, whenever I try to play a 192Khz 24Bit FLAC (tried via both Tidal and Qobuz), while Volumio shows that it is getting the 192Khz track, the DAC OLED shows 96Khz. Seems that the track is being downsampled. Any ideas why is that? I thought the device is capable of 384Khz over I2S?
P.S. Downsampling is off in Volumio settings
Edit: Yeah, definitely downsampling. Here is what the outputput from /proc/asound/card2/pcm0p/sub0/hw_params looks like
Yes, you are right - I must have accidentally enabled it. But was a pain to find that was what was causing it - until I happened to look at asound.conf.
not quite on subject but I would like to know if anyone else is getting popping sounds between each song change while using the spotify plug-in on the Audiophonics Sabre DAC ? Not a big issue but it would be nice to have silent changes
PS. currently using the 4.0.2 version of the plug-in (4.0.4 had the same popping sounds) and the latest volumio distro.
Update: Called Audiophonics, who stated that the “pops / knacks” between songs is a known issue when the EVO-DAC is used with a direct connection over the I2S GPIO (pinout RPI-DAC) to the Raspberry Pi. Other connections apparently don’t have the issue but that kind of defies the whole idea of having the RaspiPi in the the same box as the DAC pcb.
According to Audiophonics there unfortunately seems to be no software fix.
So, the issue is not linked to the Spotify plug-in or in fact any other plug-in, playback system, etc.
Just thinking but If enough users of the EVO Sabre DAC call Audiophonics maybe they will release a fixed version of the EVO. In any event, the crackling sound between tracks is way more noticeable in Volumio + Spotify plug-in than in Dietpi + Spotify plugin… so, it leaves me wondering what the heck the real problem is ! Software or Hardware ???
Has anyone been successful in changing the default logo.logo file to display an alternative to the Audiophonics logo on startup? I would like to customise to it to say VOLUMIO