#Picoreplayer jivelite with clock windows

Hence my comment about not being able to reproduce it. What DAC(s) are people using who have this issue? How are you changing the volume to affect the VUs? > by the volume control which is the problem. > Is this a mistype ? On piCore Squeezer/Jive Lite the VU's ARE affected

#Picoreplayer jivelite with clock windows

> I will try Squeezelite with Jivelite on WIndows when I get a little time > Squeezeplay (On windows at least) displays correctly IE Neither VU or SA Thanks for looking into this, if there is anything I can do to help let Is this a mistype ? On piCore Squeezer/Jive Lite the VU's ARE affectedД«y the volume control which is the problem. > I've been unable to have the VU meters be affected by hardware or I will try Squeezelite with Jivelite on WIndows when I get a little time Squeezeplay (On windows at least) displays correctly IE Neither VU or SA > Looking at the code, it is based on what's in the touch (squeezeplay). I think there may be some misunderstanding, That's the best I can do without rewriting the code. Reduces the samples accumulator by 2 so the VU meters are not so 'hot'. I've uploaded a modified jivelite_touch.tcz to the 'picoreplayer beta I've been unable to have the VU meters be affected by hardware or There have been reports of the VU meters not working correctly withДў4-bit source audio, as I don't have a 24-bit capable usb dac I can't Squeezelite only writes 16-bit samples to the shared memory that Is based on what's in the touch (squeezeplay). There were no VU meters in squeezelite/jivelite until rpress added theДЇeature for a display project he was building. > What do other people think of the current VU Meters behaviour? > respond to the output signal strength rather than the input signal > Do you think it was at the same time that the VU Meters were made to _drawMeter(self, surface, sampleAcc, 2, self.x2, self.y, self.w, self.h) _drawMeter(self, surface, sampleAcc, 1, self.x1, self.y, self.w, self.h) Self.bgImg:blit(surface, self:getBounds()) I can't fix it but just in case it helps someone I'll post my findings. *Music:* 383GB,1269 albums 17756 songs 4381 artists mostly FLACs *Remotes:* iPeng8/Orangesqueeze/PC/Jivelite *Plugins:* AutoRescan/BBCiPlayer/PowerSave/PowerSwitchIII/Squeezecloud *Server:* Logitech Media Server Version: 7.9.0 - 1444881383 on Centos 7 PiCorePlayer/RPi2/Hifiberry DAC+ x2,PiCorePlayer/RPi2/Hifiberry *Players:* SliMP3,Squeezebox3 x3, Squeezebox Receiver, SqueezePlayer, Know wether this is a problem only in PiCorePlayer. I have only these systems to try so do not Squeezeplay on Windows has the correct behaviour as does the SB3 but On my picoreplayer the volume has to be at level 24 for the vu meters toД®ven move and the SA not to be completely blank. If you play a 0Db test tone it should read 0Db wherever the the volume Set at 0 and should not change in level when the volume control is IE the meters should read the music level even if the volume control is VU meter reading and the spectrum analyser should not be effected by the I have been told that my explanation of the problem is not clear so I *Music:* 383GB, 1269 albums with 17756 songs by 4381 artists mostly *Plugins:* AutoRescan / BBCiPlayer / PlayHLS / PowerSave / *Server:* Logitech Media Server Version: 7.9.0 - 1443766458 on Centos 7 PiCorePlayer on RPi 2 with Hifiberry DAC+ x 2 *Players:* SliMP3, Squeezebox 3 x 3, Squeezebox Receiver, SqueezePlayer, I have searched but cannot find it if it has. Has this (unusual) behaviour been discussed / decided on by anyone I noticed that the VU meter and Spectrum analyser Now Playing displays I have just got piCoreplayer working on the Pi 7' LCD and am using