Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Poor sound quality #258

Open
robfrye opened this issue Mar 28, 2020 · 12 comments
Open

Poor sound quality #258

robfrye opened this issue Mar 28, 2020 · 12 comments

Comments

@robfrye
Copy link

robfrye commented Mar 28, 2020

Playing via USB on a Raspberry Pi 4b - the sound quality is always significantly worse using Spotify Connect compared with using the Volumio Spotify plugin.

@illtrick
Copy link

Bitrate (320kbs), Bitdepth (16bit) and Samplerate (44.1khz) are all unique values.

@robfrye
Copy link
Author

robfrye commented Mar 28, 2020

Fair enough, updated the question. Any idea why sound quality is so much worse using Connect than using the regular Spotify plugin?

@robfrye robfrye changed the title bitrate is always 44.1khz regardless of setting Poor sound quality Mar 28, 2020
@illtrick
Copy link

Interesting, can you describe the difference? Volume level is certainly different for me when switching back and forth but I don’t notice any sonic difference after volume matching.

@robfrye
Copy link
Author

robfrye commented Mar 28, 2020

sound is very muted and lacks dynamic range. Not much volume difference for me.
If it's helpful, I am running USB out to an external DAC and then into a pretty decent amp/speaker setup.

@illtrick
Copy link

volume normalization could be the culprit, that squashes dynamic range. is it set to on in either the plugin or globally?

@robfrye
Copy link
Author

robfrye commented Mar 29, 2020

Off in both places. Happy to send you logs or whatever if you can tell me how to do it.

@illtrick
Copy link

illtrick commented Mar 29, 2020

I can help you part of the way, I'm no dev but I can at least help you get logs. I actually came here to post my own issue but got distracted by yours. Best of luck!

  1. Make sure you have debug mode enabled in the plugin
  2. SSH to your device (if you don't know how to do that there's links in the instructions on the main page )
  3. copy paste and this command: sudo journalctl -f -o cat -u volspotconnect2.service
  4. It should print events as they occur. I'd go through a standard startup process (spotify app closed, open app, connect to device, play track) and copy paste them here.

@ashthespy
Copy link

Interesting, can you describe the difference? Volume level is certainly different for me when switching back and forth but I don’t notice any sonic difference after volume matching.

That shouldn't be the case - can you describe your setup?

@robfrye Try turning off the volume control as well, if your using a software mixer.

@robfrye
Copy link
Author

robfrye commented Mar 31, 2020

I wasn't using the volume control, however now it won't even connect so I can't help more at the moment. I'll pile on to the Cannot Connect thread with my logs

@illtrick
Copy link

Interesting, can you describe the difference? Volume level is certainly different for me when switching back and forth but I don’t notice any sonic difference after volume matching.

That shouldn't be the case - can you describe your setup?

@ashthespy I’ll take another go at it tomorrow. You’re making me think I’m crazy now. I swear the volume levels were different...

@ashthespy
Copy link

@illtrick
The volume level depends on the setup. For a hardware mixer, spop - the dameon used in the spotify plugin uses sox and 'alsa' for the output. Thus the volume level is as defined by the "system volume" set by Volumio through alsa (some esoteric cases use a septate I2C device, but most is done with alsa).
The daemon we use, vollibrespot by comparison, ties directly to alsa for both the output and hardware mixer. Thus, changing volume from your client, should result in a direct change of the "system" volume for Volumio. Software mixers on the other hand, map the 0-100 of the client volume, to the current "system volume" of Volumio.

@gorgias0
Copy link

gorgias0 commented Jun 15, 2020

Hi,
I have the same problem with poor sound quality.
I tried the above command to see the log from volspotconnect 2 and everything looks ok except for this line:
[Vollibrespot] : Reducing normalisation factor to prevent clipping. Please add negative pregain to avoid.

edit:
I have normalisation off in spotify and mixer disabled in volumio.

Tried to start alsamixer via ssh in volumio and pcm volume was set to 100, can this be the problem?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants