by totyc » Mon Dec 24 2018 20:55
#this file is generated by the plugin. You should not edit it unless you know what you do. It will be overwrite by the plugin each time a change in config is detected
./vollibrespot -b 320 -c /tmp \
--name 'vu7Volumio' --initial-volume 100\
--device plughw:2 \
--mixer alsa \
--mixer-name 'XMOS Clock Selector' --mixer-card 'hw:2' \
[Vollibrespot] : Connecting to AP "gew1-accesspoint-b-d4sn.ap.spotify.com:4070"
[Vollibrespot] : Authenticated as "totyc" !
[Vollibrespot] : Setting up new mixer: card:hw:2 mixer:XMOS Clock Selector index:0
[Vollibrespot] : Alsa min: 0 (MilliBel(-12700)[dB]) -- max: 127 (MilliBel(0)[dB]) HW: true
[Vollibrespot] : Alsa min-db is not SND_CTL_TLV_DB_GAIN_MUTE!!
[Vollibrespot] : Using alsa sink
[Vollibrespot] : Current alsa volume: 127[i64] MilliBel(0)
[Vollibrespot] : Mapping volume [100.000%] 65535 [u16] ->> Alsa [0.000%] 0 [dB]
[Vollibrespot] : Metadata pipe established
[Vollibrespot] : Country: "HU"
[Vollibrespot] : SessionActive!
[Vollibrespot] : Loading track "London Calling - Remastered" with Spotify URI "spotify:track:5jzma6gCzYtKB1DbEwFZKH"
[Vollibrespot] : Track "London Calling - Remastered" loaded
by ashthespy » Tue Dec 25 2018 13:21
i have some founding ...
1. When changing output device in volumio UI ( Playback Option / Output Device),
there is a need to "restart" VSC2, eg. ON->OFF->ON. In this case startconnect.sh will be correctly updated. If it is not correctly updated,
volspotconnect2 daemon will hang up in never ending loop ....
I believe this is due to a current limitation with the way Volumio handles output devices, and keeping compatibility with balbuze other equaliser plugins. There is a manual timer. But yeah, it should trigger on an event, and not need manual intervention - will fix this!
2. The most safety way to have running VSC2 is next :
- STOP VSC2 plugin
- CHANGE OUTPUT device
- START VSC2 plugin
3. Topping D30 USB DAC issue is probably related to "BAD" mixer-name 'XMOS Clock Selector,1'. If i choose in output device 'XMOS Clock Selector' instead of 'XMOS Clock Selector,1' daemon works as expected.
Has this always been the case - or did this behaviour start only from the 2.513? While it would be easy to strip out the `,1` from the plugin, don't want to add more spaghetti code, if its an error from elsewhere!
4. Change plugin settings in UI ( volume level from 100% to 50%), after pressing SAVE, generate message "Configuration has been sucessfully updated", but the volume level is still 100%.
My mistake here
Merry Christmas !
by exiton » Thu Mar 14 2019 21:25