Re: [SlimDevices: Plugins] Announce: Denon AVP Control Plugin
In refer to my github issue I am writing here to discuss an issue I am experiencing. https://github.com/aesculus/denonavpcontrol/issues/23#issuecomment-1296308288 LMS shows volume control in % (0% - 100%). My AVR shows also volume in % (0%-98%). When I set LMS volume to 5%, it is translated to 20% on my AVR. 10% is translated to 28.5% on my AVR and so on. I do not know if this is intended behavior or not. In my opinion, this does not make much sense and is not straightforward. Why would I want to have two different % values for one player? I think such a nonlinear behavior only makes sense for transforming % to dB and vice versa. The behavior is independent from client apps (Squeezer, LMS Material). So if this behavior is a bug, please see my github issue as a bug report. If the behavior is intended, please see this as a feature request, to get an optional 1:1 volume transfer, where 5% in LMS is 5% on my AVR and 10% is 10% and so on. gnackwatschn's Profile: http://forums.slimdevices.com/member.php?userid=71199 View this thread: http://forums.slimdevices.com/showthread.php?t=60114 ___ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
Re: [SlimDevices: Plugins] ANNOUNCE: AirPlay Bridge = integrate AirPlay devices with LMS (squeeze2raop)
philippe_44 wrote: > Reduce log level to start with (do not set any "additional debugging") Somehow I have missed your reply. Here is the new log file: I started playing and then, after a few seconds, I clicked on the next button. The next song played for one second and then stopped. Code: Starting Squeeze2raop: /config/cache/InstalledPlugins/Plugins/RaopBridge/Bin/squeeze2raop-aarch64 -Z -I -f /config/logs/raopbridge.log -x /config/prefs/raopbridge.xml [10:53:18.191919] main:1572 Starting squeeze2raop version: v0.4.63.1 (Feb 21 2022 @ 18:43:24) [10:53:18.204575] Start:1314 Binding to 192.168.178.101 [10:53:18.205031] StartActiveRemote:1202 DACP port: 57403 [10:53:18.252866] AddRaopDevice:883 [0x5074a0]: adding renderer (wohnzimmer-heimkino) [10:53:18.255087] raopcl_create:735 [0x7fa8009600]: using PCM coding [10:53:18.281663] output_raop_thread_init:126 [0x4ab878]: init output raop [10:53:18.281809] output_init_common:290 allocating 16777216 [10:53:18.283078] slimproto:835 squeezelite [0x4ab878] <=> player [0x5074a0] [10:53:18.283257] slimproto:836 [0x4ab878] connecting to 192.168.178.101:3483 [10:53:18.284471] slimproto:866 [0x4ab878] connected [10:53:18.284609] sendHELO:118 [0x4ab878] cap: CanHTTPS=1,Model=squeezelite,ModelName=RaopBridge,AccuratePlayPoints=0,HasDigitalOut=1,MaxSampleRate=192000,ogf,flc,alc,wav,aif,pcm [10:53:36.184010] PlayerThread:554 [0x5074a0]: flushing ... [10:53:36.215360] PlayerThread:418 [0x5074a0]: Disconnecting 1443515223 [10:53:36.220498] process_strm:241 [0x4ab878] strm command s [10:53:36.220633] process_strm:316 [0x4ab878], strm s autostart: 1 transition period: 10 transition type: 0 codec: f [10:53:36.220861] process_strm:348 [0x4ab878]: codec:f, ch:255, s:255, r:255 [10:53:36.220987] PlayerThread:527 [0x5074a0]: raop connecting ... [10:53:36.221780] raopcl_connect:1017 [0x7fa8009600]: local interface 192.168.178.101 [10:53:36.611922] exec_request:702 [0x7fa800e010]: Body data 1076, LfÊFåïËL5?9^OnÌoí-CçÃ}y [10:53:36.623663] PlayerThread:538 [0x5074a0]: raop connected [10:53:37.186523] raopcl_accept_frames:433 [0x7fa8009600]: begining to stream hts:0 n:3875504017.801105889 [10:53:37.186862] raopcl_accept_frames:441 [0x7fa8009600]: restarting w/o pause n:3875504017.801105889, hts:170909727157925 [10:53:37.207120] _output_frames:53 [0x4ab878]: start buffer frames: 134784 [10:53:37.207292] _output_frames:100 [0x4ab878]: track start sample rate: 44100 replay_gain: 65536 [10:53:37.217568] output_raop_thread:99 [0x4ab878]: track actual start time:1443517444 (gap:1443517444) [10:53:38.762863] raopcl_send_chunk:610 [0x7fa8009600]: check n:1443517770 p:1443519008 ts:170909727227269 sn:9355 retr: 0, avail: 0, send: 0, select: 0) [10:53:39.625995] PlayerThread:516 [0x5074a0]: volume repeat or trigger timeout 29 [10:53:48.761701] raopcl_send_chunk:610 [0x7fa8009600]: check n:1443527769 p:1443529010 ts:170909727668325 sn:10608 retr: 0, avail: 0, send: 0, select: 0) [10:53:58.762678] raopcl_send_chunk:610 [0x7fa8009600]: check n:1443537770 p:1443539011 ts:170909728109381 sn:11861 retr: 0, avail: 0, send: 0, select: 0) [10:54:08.770218] raopcl_send_chunk:610 [0x7fa8009600]: check n:1443547778 p:1443549012 ts:170909728550437 sn:13114 retr: 0, avail: 0, send: 0, select: 0) [10:54:18.767325] raopcl_send_chunk:610 [0x7fa8009600]: check n:1443557775 p:1443559014 ts:170909728991493 sn:14367 retr: 0, avail: 0, send: 0, select: 0) [10:54:28.765827] raopcl_send_chunk:610 [0x7fa8009600]: check n:1443567773 p:1443569015 ts:170909729432549 sn:15620 retr: 0, avail: 0, send: 0, select: 0) [10:54:33.342746] PlayerThread:554 [0x5074a0]: flushing ... [10:54:33.342877] raopcl_flush:1129 [0x7fa8009600]: flushing up to s:16192 ts:96024165 [10:54:33.374257] PlayerThread:418 [0x5074a0]: Disconnecting 1443572382 [10:54:33.377869] process_strm:241 [0x4ab878] strm command s [10:54:33.377992] process_strm:316 [0x4ab878], strm s autostart: 1 transition period: 10 transition type: 0 codec: f [10:54:33.378088] process_strm:348 [0x4ab878]: codec:f, ch:255, s:255, r:255 [10:54:34.231832] PlayerThread:527 [0x5074a0]: raop connecting ... [10:54:34.232693] raopcl_connect:1017 [0x7fa8009600]: local interface 192.168.178.101 [10:54:34.617576] exec_request:702 [0x7fa800e010]: Body data 1076, kçofö¨¶û ïKN¢?¹¹Èë²3³2Èhì¯ak [10:54:34.628497] PlayerThread:538 [0x5074a0]: raop connected [10:54:34.635475] raopcl_accept_frames:433 [0x7fa8009600]: begining to stream hts:170909729633893 n:3875504074.2729340047 [10:54:34.635719] raopcl_accept_frames:441 [0x7fa8009600]: restarting w/o pause n:3875504074.2729340047, hts:170909729691424 [10:54:34.645875] _output_frames:53 [0x4ab878]: start buffer frames: 1457280 [10:54:34.646019] _output_frames:100 [0x4ab878]: track start sample rate: 44100 replay_gain: 65536 [10:54:34.656391] output_raop_thread:99
Re: [SlimDevices: Plugins] [Announce] Spotty 4.6 - sorting option for Albums/Artists/Songs, replay gain fix
Hello everyone, unfortunately I could not find a documentation, where the ports are listed, which are used by Spotty, so I cannot open them in my firewall. I am using ufw and have already opened up 9000/tcp 9090/tcp 3483/tcp 3483/udp 4070/tcp 5353/udp everything is working fine, except of local player broadcast. In my ufw logs I found out, that my smartphone tries to connect to lms on the following ports: 35623/tcp 42978/tcp 3/tcp after opening these ports, my players were accessible. so here my question: - is there any logic behind these port numbers and can they be found out, without searching manually in my ufw logs? - are the port numbers fixed, or may they be changed in the future (maybe after a restart, or an update of the server / spotty plugin)? thank you in advance gw gnackwatschn's Profile: http://forums.slimdevices.com/member.php?userid=71199 View this thread: http://forums.slimdevices.com/showthread.php?t=114836 ___ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
Re: [SlimDevices: Plugins] Announce: UPnPBridge = integrate UPnP/DLNA players with LMS (squeeze2upnp)
Hi! I am having issues to get the plugin to work with my Denon AVR. My server: - Raspberry PI 3b on Raspbian Buster - LMS 8.1.0 - UPNP Bridge 1.45.0 My Player: Denon AVR S750H The player is able to receive UPnP/DLNA streams, I have tested this with Bubble UPnP on my Android Phone and with Windows Media Player on my Win 10 device. I can start / stop playback, control the volume over UPnP and the devices automatically switches on, as soon as I start playback. My Issue: In LMS / UPnP Bridge the player is also detected and shown under as a player. It seems like the connection basically works, because the volume changes in LMS are instantly synced to the AVR. Unfortunately the playback does not work. When I press the "play" button, LMS shows "playing" for 1s and then stops it. On the AVR itself nothing happens. What I tried so far: I already applied the "Denon" profile for the player and restarted the pugin. I also tried the "_safe_mode" profile and played and some manual configurations. But nothing got the player to work. My Logs: Code: Starting Squeeze2upnp: /var/lib/squeezeboxserver/cache/InstalledPlugins/Plugins/UPnPBridge/Bin/squeeze2upnp-armv6hf -Z -I -b 192.168.178.102 -f /var/log/squeezeboxserver/upnpbridge.log -d all=debug -x /var/lib/squeezeboxserver/prefs/upnpbridge.xml [12:08:44.775795] main:1756 Starting squeeze2upnp version: v1.45.0 (Dec 27 2020 @ 14:23:57) [12:08:44.793695] output_init:610 success loading FLAC encoder [12:08:44.793875] register_alac:550 using alac to decode alc [12:08:44.795276] load_mad:411 loaded libmad.so.0 [12:08:44.795337] register_mad:433 using mad to decode mp3 [12:08:44.795789] load_faad:626 loaded libfaad.so.2 [12:08:44.795839] register_faad:647 using faad to decode aac [12:08:44.797004] load_vorbis:325 loaded libvorbisfile.so.3 [12:08:44.797092] register_vorbis:346 using vorbis to decode ogg [12:08:44.797136] register_pcm:339 using pcm [12:08:44.797212] load_flac:292 loaded libFLAC.so.8 [12:08:44.797255] register_flac:313 using flac to decode flc [12:08:44.797453] load_opus:251 dlerror: libopusfile.so.0: cannot open shared object file: No such file or directory [12:08:44.797544] register_m4a_thru:307 using mp4 to aac (ADTS) [12:08:44.797587] register_flac_thru:247 using flac [12:08:44.797628] register_thru:106 using thru [12:08:44.797667] register_soxr:394 using soxr for resampling [12:08:44.797711] Start:1518 Binding to 192.168.178.102:49152 (http:0) [12:08:45.032535] AddMRDevice:1405 [0x138d00]: adding renderer (wohnzimmer-heimkino) [12:08:45.032705] GetProtocolInfo:359 [0x138d00]: uPNP GetProtocolInfo [12:08:45.036157] XMLGetFirstDocumentItem:181 ixmlNode_getFirstChild(tmpNode) returned (nil) (nil) [12:08:45.036245] GetProtocolInfo:370 [0x138d00]: ProtocolInfo (null) [12:08:45.036276] AddMRDevice:1426 [0x138d00] unable to get protocol info, set [12:08:45.036589] stream_thread_init:464 [0xb7e88] streambuf size: 1048576 [12:08:45.038712] MasterHandler:1036 [0x138d00]: subscribe success [12:08:45.045305] output_thread_init:574 [0xb7e88] init output media renderer [12:08:45.045498] decode_thread_init:168 [0xb7e88]: init decode [12:08:45.045769] resample_init:345 [0xb7e88]: resampling sync recipe: 0x00, flags: 0x00, scale: 0.89, precision: 0.0, passband_end: 0.0, stopband_begin: 0.0, phase_response: -1.0 [12:08:45.045824] UpdateThread:1255 Updating configuration /var/lib/squeezeboxserver/prefs/upnpbridge.xml [12:08:45.047646] discover_server:806 [0xb7e88] sending discovery [12:08:45.048717] discover_server:838 [0xb7e88] got response from: 192.168.178.102:3483 [12:08:45.048827] slimproto:858 squeezelite [0xb7e88] <=> player [0x138d00] [12:08:45.048858] slimproto:859 [0xb7e88] connecting to 192.168.178.102:3483 [12:08:45.050221] slimproto:889 [0xb7e88] connected [12:08:45.050341] sendHELO:134 [0xb7e88] mac: bb:bb:78:4c:a0:a8 [12:08:45.050375] sendHELO:135 [0xb7e88] cap: CanHTTPS=1,Model=squeezelite,ModelName=UPnPBridge,AccuratePlayPoints=0,HasDigitalOut=1,MaxSampleRate=48000, [12:08:45.052757] process:500 [0xb7e88] strm [12:08:45.052896] process_strm:241 [0xb7e88] strm command q [12:08:45.052929] decode_flush:208 [0xb7e88]: decode flush [12:08:45.052959] output_flush:569 [0xb7e88]: flush output buffer [12:08:45.052990] sq_callback:314 [0x138d00]: device off or not controlled by LMS [12:08:45.053093] process:500 [0xb7e88] strm [12:08:45.053124] process_strm:241 [0xb7e88] strm command q [12:08:45.053152] decode_flush:208 [0xb7e88]: decode flush [12:08:45.053180] output_flush:569 [0xb7e88]: flush output buffer [12:08:45.053615] process:500 [0xb7e88] setd [12:08:45.053652] sendSETDName:227 [8]: set playername: wohnzimmer-heimkino [12:08:45.053850] process:500 [0xb7e88] setd [12:08:45.054152] process:500 [0xb7e88] aude [12:08:45.054192] process_aude:392 [0xb7e88] on/off using aude 1 [12:08:45.054223]
Re: [SlimDevices: Plugins] Announce: Material Skin
cpd73 wrote: > I agree it should not affect functionality. My point was that if the > volume shown in LMS was not the volume used on the player, then it has > no real meaning and would be confusing. If it does reflect the real > volume then it should be shown. > > I have updated Material to be consistent - and removed the 'Fixed > volume' label. I've added a server-side yes/no option as to whether > fixed volume should be respected. If set to 'No' then Material will > treat a fixed volume player as a normal player - show volume slider and > value. If set to 'Yes' it will show the slider as disabled and not show > a volume level. I guess this resolves the issue? For me, this sounds perfect. Thank you! Any tips on how I can download your dev version? I know, I could download manually and copy the files, but maybe there is an 'official' way? Never installed fom a git until now. gnackwatschn's Profile: http://forums.slimdevices.com/member.php?userid=71199 View this thread: http://forums.slimdevices.com/showthread.php?t=109624 ___ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
Re: [SlimDevices: Plugins] Announce: Material Skin
cpd73 wrote: > Actually, AFAICS, iPeng has the volume control disabled - except on the > lockscreen, but the control does not seem to work. > > > > Cosmetics do matter. > > I have no real fixed volume devices, so I cannot really test. But, does > the volume shown in the Default web UI reflect the real volume? i.e. if > you change the volume on the real player, does LMS show the real volume > level? If not, then showing the level here is bad - as it implies its a > value it is not. Firstly: I am only using default skin and also Squeezer. So I can definitely confirm, that on both the volume controls are working perfectly and also reflect the values of the AVR volume. As iPeng is recommended by the Denon plugin developers, I suggested that it works the same. I apologize if that part of my post was wrong. Secondly: I agree, cosmetics do matter. But cosmetics should not impact functionality to a level that makes software unusable for some users. In case it really matters so much in our situation, also the volume buttons and the volume controls in the 'manage players' view should be disabled, to be consistent. I understand totally understand the point, that some people want to keep it as it is. That's why I requested this as an optional setting. I never intendend to change the default behaviour for everyone. So maybe that would be the best way to go? I also did not want to start a big discussion about that, just wanted to give feedback. That said I think it is up to you, to decide and I will respect your decision in every case. Keep up the great work. gnackwatschn's Profile: http://forums.slimdevices.com/member.php?userid=71199 View this thread: http://forums.slimdevices.com/showthread.php?t=109624 ___ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
Re: [SlimDevices: Plugins] Announce: Material Skin
cpd73 wrote: > The dev version sends +/- the defined volume increment when using the > up/down vol buttons when a player has fixed volume. This is also > extended by a server-side Material setting that will cause Material to > 'ignore' the fixed volume state. When that is set, the volume for fixed > volume players will be controlled as if they are not fixed volume - so > the slider will be active, and the up/down buttons will set a volume > relative to the current (as shown in the slider) volume. So, if vol=80% > and increment=5%, then down will set volume to 75% > > However, I'm not sure if this is really required. Or if Material should > just ignore fixed volume? In my opinion MS should ignore the fixed volume setting (slider and button) , or, at least give an Option to do so. Here a short sum up of the reasons I see: - Consistency: It would work like default skin, Squeezer and iPeng. All those ignore the fixed volume setting, or, at least have an option for doing so. - Less development effort: Fixed volume string is not localized yet, manage player settings still ignores it - Functional vs. cosmetic: Leaving the slider fixed strongly impacts the usability in some cases and forces users to switch to another skin. On the other side there is just a small cosmetic downside for others, when the slider isn't fixed aymore. This is only my opinion, but there are some objective reasons to think so. gnackwatschn's Profile: http://forums.slimdevices.com/member.php?userid=71199 View this thread: http://forums.slimdevices.com/showthread.php?t=109624 ___ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
Re: [SlimDevices: Plugins] Announce: Material Skin
cpd73 wrote: > So, jsut to confirm; Player's volume is fixed at 100%, but the > volume-slider, etc, should function as normal? This -should- be easy > eniough. Are there scenarios where this would not be wanted? > > This would make the code easier, as I dont really need to care about > fixed volume, etc. (So I could remove the 'Fixed volume' label, and > remove special cases required for this). Thank you for your fast reply. I could not dig into this deep enough, to give you a reliable answer. I use the skin called "Standard" which allows manipulating the volume slider and I could not recognize any disadvantages beside of having a useless volume slider which could potentially confuse some users. But as I wrote before: I did not dive into this very deeply, as I am not an LMS developer and there is the possibility, that there is still a "special case" and something happening under the hood. gnackwatschn's Profile: http://forums.slimdevices.com/member.php?userid=71199 View this thread: http://forums.slimdevices.com/showthread.php?t=109624 ___ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
Re: [SlimDevices: Plugins] Announce: Material Skin
PasTim wrote: > Can't you change the LMS setting, allow volume changes, and fix the > squeezelite volume to 100% (-U) ? Or won't that do what you want? Thank you for your reply. I already tried this and unfortunatley it did not work. In this case the Denon Serial plugin stops adjusting the AVR volume, because it assumes, that the volume is adjusted by the player itself. This should avoid changing volume on both devices simultaneously. gnackwatschn's Profile: http://forums.slimdevices.com/member.php?userid=71199 View this thread: http://forums.slimdevices.com/showthread.php?t=109624 ___ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
Re: [SlimDevices: Plugins] Announce: Material Skin
cpd73 wrote: > Why? The slider sets a value, which is fixed at 100% - therefore it > cannot work. The reason why I am requesting this feature is: In Classic Skin this is possible and it is very useful in some scenarios. In my case and also for other people who already posted here is: I have a Raspberry Pi with SqueezeLite, connected to a Denon AVR. The SqueezeLite volume is fixed at 100% and should always stay there, because all volume adjustments should be done on the Denon AVR. Therefor the Denon Serial plugin or Denon AVP Plugin can be used in LMS. The plugins recognize volume changes made in LMS web interface (although the player volume is fixed at 100%) and send the value it over to the AVR. As stated before: this works fine in classic skin, simpy because the volume slider is not greyed out. I hope I could clarify the reason, why I think this is useful for me and also others. Making this "feature" optional via checkbox in the settings page and also "off by default" would additionaly ensure that nobody has disadvantages. So I really hope you consider implementing it in a future version. Your Skin is really awesome and I really wish I could switch over to it from classic skin, for many reasons, but this little volume slider issue prevents me from doing so. gnackwatschn's Profile: http://forums.slimdevices.com/member.php?userid=71199 View this thread: http://forums.slimdevices.com/showthread.php?t=109624 ___ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
Re: [SlimDevices: Plugins] Announce: Material Skin
cpd73 wrote: > For 2.2.0, I have changed the up/down volume keys to send +/- > volume-step (e..g +5, -5) when pressed if player's volume is fixed. Thank you for the fast support. Do you think it would also be possible to give us an option for using the slider? If you want to keep the actual default behaviour, maybe a checkbox in the plugin settings aka "Activate volume slider for fixed volume devices" would be sufficient. The checkbox can be unchecked by default, so nothing changes by deafult. gnackwatschn's Profile: http://forums.slimdevices.com/member.php?userid=71199 View this thread: http://forums.slimdevices.com/showthread.php?t=109624 ___ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
Re: [SlimDevices: Plugins] Announce: Material Skin
DAR wrote: > I have a similar situation to the one just described by gnackwatschn. > One of my players is a squeezelite instance running on a Raspian/RPi4 > device through a hifiberry digi+ card to an old Denon receiver. I had > previously used the IRBlaster plugin (with an SB3 classic and an IR > transmitter) to control the receiver remotely (power on/power off/volume > up/volume down/audio in), but I have recently switched over to a serial > controller device with an ethernet connection that is plugged in to the > RS232 port on the receiver. > > I initially tried using the Denon AVP/AVR Control LMS plugin mentioned > by gnackwatschn, but that had problems controlling volume even through > the default skin on LMS. I switched over to Peter Watkin's DenonSerial > plugin to control my receiver, and that works great through the default > skin. > > My problems arise using the material skin when the volume of the player > is changed. As gnackwatschn mentioned, the audio setting for the player > needs to be at 100% in order for the volume to be controlled by the > receiver. This works fine with the default skin, where clicking the > button on either side of the volume slider (see picture below) causes a > stepwise change in volume, and clicking within the slider causes the > volume to jump to the specified volume. This works similarly with the > iPeng and Squeeze Ctrl apps (in the case of Squeeze Ctrl after setting a > preference to send volume signals even though the player is set to > 100%). > > 32878 > > With the material skin, the slider shows up as "fixed volume", but the > buttons on either side are indeed active (see picture below). > Unfortunately, when I click the left button, the volume jumps to a fixed > high level, and when I click the right button, the volume jumps to a > fixed higher level. Further clicking those buttons doesn't change > anything. > > 32876 > > There is clearly a difference in how the volume controls are sent to the > receiver from the two different skins, but I am not sure how to sort > this out. The Denon controller plugins also clearly impact how the > volume levels are set. I am happy to troubleshoot the situation if > anyone has suggestions. Thanks in advance for your help! Thank you for your reply, now i know, that I am not the only one with this issue. Maybe it is worth noting: In the meantime I also switched to Denon Serial, because of other issues with volume control in Denon AVP Plugin. The main problem stays the same: With classic web-ui and also with Squeezer app I am able to change the volume of the player, even if it is fixed at 100% in LMS settings. The Denon Serial plugin recognizes these changes and sends it perfectly overt to the avr. gnackwatschn's Profile: http://forums.slimdevices.com/member.php?userid=71199 View this thread: http://forums.slimdevices.com/showthread.php?t=109624 ___ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
Re: [SlimDevices: Plugins] Announce: Material Skin
slartibartfast wrote: > I thought this had come up before and worked now. What happens if you > tap on volume up or down? Does that change the volume of your AVR? > > Sent from my Pixel 3a using Tapatalk Unfortunately this doesn't work for me. I can click the buttons, but it has not the desired effect, like in classic web-ui. gnackwatschn's Profile: http://forums.slimdevices.com/member.php?userid=71199 View this thread: http://forums.slimdevices.com/showthread.php?t=109624 ___ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
Re: [SlimDevices: Plugins] Announce: Material Skin
PasTim wrote: > I don't really understand how the Denon plugin works - trying to control > 2 devices for the same playback seems 'unusual' to me. Still, can you > leave the volume variable in LMS for the avr and fix it at 100% in > squeezelite with -U? Thank you for your reply. It is not my intention to control 2 devices for the same playback. My raspberry pi with squeezelite is connected to the avr as audio source and should always output the sound at 100% to the avr. Therefore I forced the player volume to 100% in the player settings of LMS. This step is also neccessary for the denon plugin to work, otherwise it does not send volume changes to the avr, because it would lead to a "double volume change" (squeezelite + avr). With the described setup it is ensured that the denon plugin is the only thing which controls the output volume. To change the volume I have to "tell" the plugin what volume change I want to have. With the classic web-ui this is possible via volume slider, because it is not greyed out. So I am able to change the volume via slider and/or buttons and while the squeezelite player itself is forced to 100% the plugin sees the volume change in the web-ui and passes it to the denon receiver. Unfortunately your suggested solution would not work for this problem, because it is mandatory to fix the player volume at 100%, otherwise the denon plugin does not work, to prevent the "double volume change". And as I wrote before: Fixing the player volume at 100% leads to the greyed out volume slider in Material web-ui which is my big issue here. gnackwatschn's Profile: http://forums.slimdevices.com/member.php?userid=71199 View this thread: http://forums.slimdevices.com/showthread.php?t=109624 ___ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
Re: [SlimDevices: Plugins] Announce: Material Skin
The buttons are not disabled, but clicking on them has no effect for me. cpd73 wrote: > The slider is disabled, the buttons are not. gnackwatschn's Profile: http://forums.slimdevices.com/member.php?userid=71199 View this thread: http://forums.slimdevices.com/showthread.php?t=109624 ___ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
Re: [SlimDevices: Plugins] Announce: Material Skin
Hi! I am using LMS for some years now and want to use Material Skin. I like the UI and the ability to use it on small and big screens. Unfortunately there is an issue with volume control, which prevents me from using Material skin: In the Standard skin it is possible to use the volume slider for a player, although if the volume for this player is locked to 100% in audio settings. In Material Skin the slider is greyed out and can't be used. I think this is intended and makes sense in many cases. In my case (and maybe others too) it is a downside and makes Material skin unusable. Here is the explanation: One of my players (Squeezelite) is connected to a Denon avr. All volume controls done in LMS are sent to the avr through the Denon AVP plugin for LMS. The plugin simply takes the volume which is set in LMS and sends a volume command directly to the avr. To prevent volume changes on both devices (the player and the avr) the volume for the player is locked at 100% in player's audio settings. Now, as the control is greyed out in Material Skin, this is not possible. So I am not able to adjust the volume for my player anymore, if I switch the skin. So my question: Is there a possible workaround? If not, would it be possible to implement this as a "feature"? I suggest sth. like "allow volume control for players with locked volume". Many thanks in advance. gnackwatschn's Profile: http://forums.slimdevices.com/member.php?userid=71199 View this thread: http://forums.slimdevices.com/showthread.php?t=109624 ___ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
Re: [SlimDevices: Plugins] Announce: Denon AVP Control Plugin
AFAIK it is not possible to play multiple dlna streams to a Denon receiver at the same time. This might be the reason, why it only shows up as one device. muflon_ wrote: > Gents, > any hints (for beginner) how can I use 3 zones in my Denon receiver as > separate players in LMS > I would like to integrate it with Loxone and I'm playing with plugin > UPNP Bridge but this can see receiver only once (not 3 for each zone) > > Many thanks gnackwatschn's Profile: http://forums.slimdevices.com/member.php?userid=71199 View this thread: http://forums.slimdevices.com/showthread.php?t=60114 ___ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
Re: [SlimDevices: Plugins] Announce: Denon AVP Control Plugin
Hi everyone, I have installed the plugin on my LMS 8.1.0 under Raspbian Buster. The configuration of my AVR (DENON S750H) was easy and nearly everything works fine (on / off, quick settings, volume changing...). Unfortunatly there is one show-stopper: While playing a playlist or a TuneIn radio station the volume of my AVR suddenly jumps from my selected volume to maximum volume. Most of the time this happens, when a new song starts or when I change the radio station. This is how I manually reproduced the issue (see also attached logfile): 1. I manually set the Volume to 8% in LMS Web Interface -> AVR Volume changed to 22.5 2. I click on "next song" in the Web Interface 3. LMS Volume jumps to 100% -> AVR Volume jumps to 80 (Maximum) Are there any suggestions why this happens and what I can do to prevent this? Thank you in advance for your help. Code: [21-01-05 15:14:10.2977] Plugins::DenonAvpControl::Plugin::commandCallback (687) *** DenonAvpControl: commandCallback() p0: mixer [21-01-05 15:14:10.2986] Plugins::DenonAvpControl::Plugin::commandCallback (688) *** DenonAvpControl: commandCallback() p1: volume [21-01-05 15:14:10.2996] Plugins::DenonAvpControl::Plugin::commandCallback (736) *** DenonAvpControl:new SB vol: 8 [21-01-05 15:14:10.3005] Plugins::DenonAvpControl::Plugin::commandCallback (738) *** DenonAvpControl:max volume: 0 [21-01-05 15:14:10.3014] Plugins::DenonAvpControl::Plugin::commandCallback (745) *** DenonAvpControl:Calc Vol: 225 [21-01-05 15:14:10.4280] Plugins::DenonAvpControl::Plugin::handleVolChanges (763) *** DenonAvpControl: VolChange: 225 [21-01-05 15:14:10.4289] Plugins::DenonAvpControl::DenonAvpComms::SendNetAvpVol (130) Calling writemsg for volume command: MV225 [21-01-05 15:14:10.4328] Plugins::DenonAvpControl::DenonAvpComms::writemsg (350) Sent AVP command request: MV225 [21-01-05 15:14:10.5650] Plugins::DenonAvpControl::DenonAvpComms::_error (360) error routine called [21-01-05 15:14:10.5659] Plugins::DenonAvpControl::DenonAvpComms::_error (366) error connecting to url: error=Timed out waiting for data url=*removed* [21-01-05 15:14:47.5472] Plugins::DenonAvpControl::Plugin::commandCallback (687) *** DenonAvpControl: commandCallback() p0: playlist [21-01-05 15:14:47.5481] Plugins::DenonAvpControl::Plugin::commandCallback (688) *** DenonAvpControl: commandCallback() p1: index [21-01-05 15:14:47.5564] Plugins::DenonAvpControl::Plugin::commandCallback (687) *** DenonAvpControl: commandCallback() p0: playlist [21-01-05 15:14:47.5574] Plugins::DenonAvpControl::Plugin::commandCallback (688) *** DenonAvpControl: commandCallback() p1: stop [21-01-05 15:14:47.5984] Plugins::DenonAvpControl::Plugin::commandCallback (687) *** DenonAvpControl: commandCallback() p0: playlist [21-01-05 15:14:47.5992] Plugins::DenonAvpControl::Plugin::commandCallback (688) *** DenonAvpControl: commandCallback() p1: open [21-01-05 15:14:47.6034] Plugins::DenonAvpControl::Plugin::commandCallback (687) *** DenonAvpControl: commandCallback() p0: playlist [21-01-05 15:14:47.6043] Plugins::DenonAvpControl::Plugin::commandCallback (688) *** DenonAvpControl: commandCallback() p1: open [21-01-05 15:14:48.5275] Plugins::DenonAvpControl::Plugin::commandCallback (687) *** DenonAvpControl: commandCallback() p0: playlist [21-01-05 15:14:48.5287] Plugins::DenonAvpControl::Plugin::commandCallback (688) *** DenonAvpControl: commandCallback() p1: newsong [21-01-05 15:14:48.5300] Plugins::DenonAvpControl::Plugin::commandCallback (699) *** DenonAvpControl: power request1: Slim::Control::Request=HASH(0x6257fa0) [21-01-05 15:14:48.5313] Plugins::DenonAvpControl::Plugin::handleVolumeRequest (816) *** DenonAvpControl: this vol player: Slim::Player::SqueezePlay=ARRAY(0x579a130) [21-01-05 15:14:48.5378] Plugins::DenonAvpControl::DenonAvpComms::writemsg (350) Sent AVP command request: MV? [21-01-05 15:14:48.5657] Plugins::DenonAvpControl::DenonAvpComms::_read (404) read routine called [21-01-05 15:14:48.5741] Plugins::DenonAvpControl::DenonAvpComms::_read (416) Read 6 [21-01-05 15:14:48.5819] Plugins::DenonAvpControl::DenonAvpComms::_read (419) Buffer read MV225 [21-01-05 15:14:48.5833] Plugins::DenonAvpControl::DenonAvpComms::_read (420) Client name: wohnzimmer [21-01-05 15:14:48.5845] Plugins::DenonAvpControl::DenonAvpComms::_read (431) Command is:MV? [21-01-05 15:14:48.5856] Plugins::DenonAvpControl::DenonAvpComms::_read (433) Subcommand is:MV? [21-01-05 15:14:48.5868] Plugins::DenonAvpControl::DenonAvpComms::_read (457) Volume setting inquiry [21-01-05 15:14:48.5880] Plugins::DenonAvpControl::Plugin::updateSqueezeVol (851) *** DenonAvpControl: The Client is: Slim::Player::SqueezePlay=ARRAY(0x579a130) [21-01-05 15:14:48.5889] Plugins::DenonAvpControl::Plugin::updateSqueezeVol (852) *** DenonAvpControl: avp vol: 225 [21-01-05 15:14:48.5901] Plugins::DenonAvpControl::Plugin::updateSqueezeVol
