[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
RE: Re: xAP Plug-in for SlimServer beta 3 release
------=_NextPart_000_0172_01C71808.16CCE440
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
I removed the brightness override from beta3 because the current SlimServer
API was not honouring the parameter to override the brightness. Behaviour
observed is to show the message at the requested brightness then (after
less
than a second) revert to a preset brightness. As a workaround, you can set
the message display preset brightness by pressing the brightness button on
the remote while a message is being displayed; messages should then all be
displayed at that brightness.
Other odd behaviour reported is a message displaying for the first 30
seconds of the requested period and then the display being blank for the
remainder of the period. I've not managed to reproduce that here.
I too have had the occasional crash during message display but have not
been
able to replicate it so don't know what the cause is. If you find a
repeatable scenario, I'd be very happy to hear about it.
_____
From: xap_automation@xxxxxxx [mailto:xap_automation@xxxxxxx]
On Behalf Of rb_ziggy
Sent: 05 December 2006 00:23
To: xap_automation@xxxxxxx
Subject: [xap_automation] Re: xAP Plug-in for SlimServer beta 3 release
Edward
Thanks for the latest plugin. I've been using it for 10 days or so.
I think the latest version, according to your log and my experience,
no longer forces the brightness up to full on a display message. The
previous one was rather good in that if the squeezebox was powered
off, a display message came on at full and then reverted to low at the
end of the display period. I'm not sure why you removed this but
would you consider putting it back in as a configurable item (e.g.
'don't change', show at full, ...)?
Also, I do seem to be getting some problems on display messages.
After several displays (3??) the slim server just seems to stop
itself. I'm not quite sure of the message circumstances yet and it
could be something to do with my set up but thought I'd report it.
I'll try a few tests at the weekend and see if I can come up with
anything more definitive.
Richard
--- In xap_automation@ <mailto:xap_automation%40yahoogroups.com>
yahoogroups.com, "Edward Pearson"
<edward.mailgroup@...> wrote:
>
> Huge thanks to all the feedback from the beta 2 testers.
>
> Beta 3 is now available at:
> http://www.edjo.
<http://www.edjo.pwp.blueyonder.co.uk/edward/xAP/Slim/slim_downloads.htm>
pwp.blueyonder.co.uk/edward/xAP/Slim/slim_downloads.htm
>
> Change Log:
>
> beta3
> 14/11/06
>
> Changed open_port in Comm.pm to use INADDR_LOOPBACK,
INADDR_BROADCAST and
> INADDR_ANY
> rather than localhost, 255.255.255.255 and 0.0.0.0
>
> Added configuration entry for xAP broadcast address. Defaults to
> INADDR_BROADCAST.
>
> Removed restriction in Slim_Item.pm and SlimServer_Item.pm that
messages
> need to be targetted.
> BSC messages remain requiring a target as per spec.
>
> Now tries 'no hub' mode before trying to connect to hub (Plugin.pm and
> Comm.pm),
> so should work without a hub.
>
> Determined that CRC.pm should not be included in the distribution
(required
> functions in Comm.pm).
>
> Fixed issues en-queuing and de-queuing display messages.
>
> Removed attempt to force brightness on display messages;
> SlimServer v6.5 reverts to pre-set message brightness on next display
> refresh.
>
> Tidied up web settings. Used in-line HTML to work around default
skin CSS
> line spacing issues.
> Only tested with default skin.
>
> Persist player subID values in player preferences.
> Once an ID is allocated to a player it will keep that ID across
restarts.
> Previously done
> on a first come (connect) first served basis at startup.
>
> Fixed null pointer issue in song/transport data when no current
playlist
> exists for player.
>
------=_NextPart_000_0172_01C71808.16CCE440
Content-Type: text/html; charset=US-ASCII
Content-Transfer-Encoding: 7bit
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3c.org/TR/1999/REC-html401-19991224/loose.dtd";>
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html;
charset=us-ascii"><!-- Network content -->
<META content="MSHTML 6.00.5730.11"
name=GENERATOR></HEAD>
<BODY style="BACKGROUND-COLOR: #ffffff">
<DIV dir=ltr align=left><SPAN class=671514700-05122006><FONT
face=Arial
color=#0000ff size=2>I removed the brightness override from beta3
because the
current SlimServer API was not honouring the parameter to override the
brightness. Behaviour observed is to show the message at the requested
brightness then (after less than a second) revert to a preset brightness.
As a
workaround, you can set the message display preset brightness by pressing
the
brightness button on the remote while a message is being displayed;
messages
should then all be displayed at that
brightness.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=671514700-05122006><FONT
face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=671514700-05122006><FONT
face=Arial
color=#0000ff size=2>Other odd behaviour reported is a message
displaying for
the first 30 seconds of the requested period and then the display being
blank
for the remainder of the period. I've not managed to reproduce that
here.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=671514700-05122006><FONT
face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=671514700-05122006><FONT
face=Arial
color=#0000ff size=2>I too have had the occasional crash during message
display
but have not been able to replicate it so don't know what the cause is. If
you
find a repeatable scenario, I'd be very happy to hear about
it.</FONT></SPAN></DIV><BR>
<BLOCKQUOTE
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px
solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B>
xap_automation@xxxxxxx
[mailto:xap_automation@xxxxxxx]
<B>On Behalf Of
</B>rb_ziggy<BR><B>Sent:</B> 05 December 2006
00:23<BR><B>To:</B>
xap_automation@xxxxxxx<BR><B>Subject:</B>
[xap_automation] Re: xAP
Plug-in for SlimServer beta 3
release<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV id=ygrp-text>
<P>Edward<BR><BR>Thanks for the latest plugin. I've been
using it for 10 days
or so. <BR><BR>I think the latest version, according to your
log and my
experience,<BR>no longer forces the brightness up to full on a
display
message. The<BR>previous one was rather good in that if the
squeezebox was
powered<BR>off, a display message came on at full and then reverted
to low at
the<BR>end of the display period. I'm not sure why you removed this
but<BR>would you consider putting it back in as a configurable item
(e.g.<BR>'don't change', show at full, ...)?
<BR><BR>Also, I do seem to be
getting some problems on display messages. <BR>After several displays
(3??)
the slim server just seems to stop<BR>itself. I'm not quite sure of
the
message circumstances yet and it<BR>could be something to do with my
set up
but thought I'd report it. <BR>I'll try a few tests at the weekend
and see if
I can come up with<BR>anything more
definitive.<BR><BR>Richard<BR><BR>--- In
<A
href="mailto:xap_automation%40yahoogroups.com";>xap_automation@<WBR>yahoogroups.<WBR>com</A>,
"Edward
Pearson"<BR><edward.mailgroup@<WBR>...>
wrote:<BR>><BR>>
Huge thanks to all the feedback from the beta 2 testers.<BR>>
<BR>> Beta
3 is now available at:<BR>> <A
href="http://www.edjo.pwp.blueyonder.co.uk/edward/xAP/Slim/slim_downloads.htm";>http://www.edjo.<WBR>pwp.blueyonder.<WBR>co.uk/edward/<WBR>xAP/Slim/<WBR>slim_downloads.<WBR>htm</A><BR>>
<BR>> Change Log:<BR>> <BR>>
beta3<BR>> 14/11/06<BR>> <BR>>
Changed open_port in Comm.pm to use
INADDR_LOOPBACK,<BR>INADDR_BROADCAST
and<BR>> INADDR_ANY<BR>> rather than localhost,
255.255.255.<WBR>255 and
0.0.0.0<BR>> <BR>> Added configuration entry for
xAP broadcast address.
Defaults to<BR>> INADDR_BROADCAST.<BR>>
<BR>> Removed restriction in
Slim_Item.pm and SlimServer_Item.<WBR>pm that
messages<BR>> need to be
targetted.<BR>> BSC messages remain requiring a target as per
spec.<BR>>
<BR>> Now tries 'no hub' mode before trying to connect to hub
(Plugin.pm
and<BR>> Comm.pm),<BR>> so should work without a
hub.<BR>> <BR>>
Determined that CRC.pm should not be included in the
distribution<BR>(required<BR>> functions in
Comm.pm).<BR>> <BR>>
Fixed issues en-queuing and de-queuing display messages.<BR>>
<BR>>
Removed attempt to force brightness on display messages;<BR>>
SlimServer
v6.5 reverts to pre-set message brightness on next
display<BR>>
refresh.<BR>> <BR>> Tidied up web settings. Used
in-line HTML to work
around default<BR>skin CSS<BR>> line spacing
issues.<BR>> Only tested
with default skin.<BR>> <BR>> Persist player
subID values in player
preferences.<BR>> Once an ID is allocated to a player it will
keep that ID
across<BR>restarts.<BR>> Previously
done<BR>> on a first come (connect)
first served basis at startup.<BR>> <BR>> Fixed
null pointer issue in
song/transport data when no current playlist<BR>> exists for
player.<BR>><BR><BR></P></DIV><!--End
group email --></BLOCKQUOTE>
<span width="1" style="color:
white;"/>__._,_.___</span>
<!-- **begin egp html banner** -->
<img src="http://geo.yahoo.com/serv?s=97476590/grpId=9674343/grpspId=1705007709/msgId=3304/stime=1165281410";
width="1" height="1"> <br>
<!-- **end egp html banner** -->
<!-- **begin egp html banner** -->
<br><br>
<div style="width:500px; text-align:right; margin-bottom:1px;
color:#909090;">
<tt>SPONSORED LINKS</tt>
</div>
<table bgcolor=#e0ecee cellspacing="13"
cellpadding="0" width=500px>
<tr valign=top>
<td style="width:25%;">
<tt><a href="http://groups.yahoo.com/gads;_ylc=X3oDMTJjYmw4ZzBrBF9TAzk3NDc2NTkwBF9wAzEEZ3JwSWQDOTY3NDM0MwRncnBzcElkAzE3MDUwMDc3MDkEc2VjA3NsbW9kBHN0aW1lAzExNjUyODE0MTA-?t=ms&k=X10+home+automation&w1=X10+home+automation&w2=Home+automation&w3=Home+automation+product&w4=Home+automation+system&w5=Home+automation+security&c=5&s=133&g=0&.sig=tN49yZ8gLW44qGV8ngn-6Q";>X10
home automation</a></tt>
</td>
<td style="width:25%;">
<tt><a href="http://groups.yahoo.com/gads;_ylc=X3oDMTJjaXYxcDFvBF9TAzk3NDc2NTkwBF9wAzIEZ3JwSWQDOTY3NDM0MwRncnBzcElkAzE3MDUwMDc3MDkEc2VjA3NsbW9kBHN0aW1lAzExNjUyODE0MTA-?t=ms&k=Home+automation&w1=X10+home+automation&w2=Home+automation&w3=Home+automation+product&w4=Home+automation+system&w5=Home+automation+security&c=5&s=133&g=0&.sig=uxodCh5B-C-LfzJs4AF_uw";>Home
automation</a></tt>
</td>
<td style="width:25%;">
<tt><a href="http://groups.yahoo.com/gads;_ylc=X3oDMTJjZWg1ZnBqBF9TAzk3NDc2NTkwBF9wAzMEZ3JwSWQDOTY3NDM0MwRncnBzcElkAzE3MDUwMDc3MDkEc2VjA3NsbW9kBHN0aW1lAzExNjUyODE0MTA-?t=ms&k=Home+automation+product&w1=X10+home+automation&w2=Home+automation&w3=Home+automation+product&w4=Home+automation+system&w5=Home+automation+security&c=5&s=133&g=0&.sig=-7-yoKCdmzYOn0eQU41W8Q";>Home
automation product</a></tt>
</td>
</tr>
<tr valign=top>
<td style="width:25%;">
<tt><a href="http://groups.yahoo.com/gads;_ylc=X3oDMTJjZzZvazNyBF9TAzk3NDc2NTkwBF9wAzQEZ3JwSWQDOTY3NDM0MwRncnBzcElkAzE3MDUwMDc3MDkEc2VjA3NsbW9kBHN0aW1lAzExNjUyODE0MTA-?t=ms&k=Home+automation+system&w1=X10+home+automation&w2=Home+automation&w3=Home+automation+product&w4=Home+automation+system&w5=Home+automation+security&c=5&s=133&g=0&.sig=YiCpy6REMq-ZQ9BflM6GVg";>Home
automation system</a></tt>
</td>
<td style="width:25%;">
<tt><a href="http://groups.yahoo.com/gads;_ylc=X3oDMTJjYjM2Y3AwBF9TAzk3NDc2NTkwBF9wAzUEZ3JwSWQDOTY3NDM0MwRncnBzcElkAzE3MDUwMDc3MDkEc2VjA3NsbW9kBHN0aW1lAzExNjUyODE0MTA-?t=ms&k=Home+automation+security&w1=X10+home+automation&w2=Home+automation&w3=Home+automation+product&w4=Home+automation+system&w5=Home+automation+security&c=5&s=133&g=0&.sig=MqsbZg2eMmjgfWfWU0yLgQ";>Home
automation security</a></tt>
</td>
</tr>
</table>
<!-- **end egp html banner** -->
<!-- **begin egp html banner** -->
<br>
<div style="font-family: verdana; font-size: 77%; border-top: 1px
solid #666; padding: 5px 0;" >
Your email settings: Individual EmailTraditional <br>
<a href="http://groups.yahoo.com/group/xap_automation/join;_ylc=X3oDMTJmY3VkYWZzBF9TAzk3NDc2NTkwBGdycElkAzk2NzQzNDMEZ3Jwc3BJZAMxNzA1MDA3NzA5BHNlYwNmdHIEc2xrA3N0bmdzBHN0aW1lAzExNjUyODE0MTA-";>Change
settings via the Web</a> (Yahoo! ID required) <br>
Change settings via email: <a href="mailto:xap_automation-digest@xxxxxxx?subject=Email
Delivery: Digest">Switch delivery to Daily Digest</a> <a
href = "mailto:xap_automation-fullfeatured@xxxxxxx?subject=Change
Delivery Format: Fully Featured">Switch to Fully Featured</a>
<br>
<a href="http://groups.yahoo.com/group/xap_automation;_ylc=X3oDMTJkYTVlNTViBF9TAzk3NDc2NTkwBGdycElkAzk2NzQzNDMEZ3Jwc3BJZAMxNzA1MDA3NzA5BHNlYwNmdHIEc2xrA2hwZgRzdGltZQMxMTY1MjgxNDEw";>
Visit Your Group
</a>
<a href="http://docs.yahoo.com/info/terms/";>
Yahoo! Groups Terms of Use
</a>
<a href="mailto:xap_automation-unsubscribe@xxxxxxx?subject=Unsubscribe";>
Unsubscribe
</a>
<br>
</div>
<br>
<!-- **end egp html banner** -->
<span style="color: white;"/>__,_._,___</span>
</BODY></HTML>
------=_NextPart_000_0172_01C71808.16CCE440--
xAP_Automation Main Index |
xAP_Automation Thread Index |
xAP_Automation Home |
Archives Home
|