The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

Re: Re: xAP on Squeezebox 3 AND Floorplan crash



--------------080101010909010604090005
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Well that's not good! I presume you have a raw device setup to capture
data from the Slimserver? Does that device trigger any script? If it
does then could you try making a blank file called 'global.xsp' inside
the /Scripts/ folder , that may well be the issue. If not is there a
specific xAP message that triggers the issue?

Thanks

James
p.s. I have played with an earlier version of Edward's slim connector
and it really does works rather well! I'm sure it'll be out soon
max wrote:
> James,
>
> I've just found that using the old xFx slim connector causes a hard
> crash of floorplan! Tried it with both service and GUI versions on the
> same machine as floorplan, and the GUI on another pc. All crash
> floorplan with a "Run time error '52':Bad file name or
number".
> Seems to happen as soon as the slim conduit starts sending messages.
>
> Max
>
> rb_ziggy wrote:
>
>> Ditto here! I'd be v interested too.
>>
>> I've now got the squeezebox 3, cracking bit of kit but haven't
>> succeeded in getting messages to it yet. The current conduit does
>> seem to see the traffic and will show some messages on the
softqueeze
>> version but then seems to hang up.
>>
>> rgds
>>
>> Richard
>>
>> --- In xap_automation@xxxxxxx
>> <mailto:xap_automation%40yahoogroups.com>,
max <max@...> wrote:
>>
>>> Just wondering if you're any nearer to posting the new
conduit, Edward?
>>>
>>> Max
>>>
>>> Edward Pearson wrote:
>>>
>>>> Available now! (coding is done, I just need to put it up
on my
>>>>
>> website...)
>>
>>>>
>> ----------------------------------------------------------
>>
>>>> *From:* xap_automation@xxxxxxx
>>>>
>> <mailto:xap_automation%40yahoogroups.com>
>>
>>>> [mailto:xap_automation@xxxxxxx
>>>>
>> <mailto:xap_automation%40yahoogroups.com>]
*On Behalf Of *rb_ziggy
>>
>>>> *Sent:* 28 October 2006 15:15
>>>> *To:* xap_automation@xxxxxxx
>>>>
>> <mailto:xap_automation%40yahoogroups.com>
>>
>>>> *Subject:* [xap_automation] Re: xAP on Squeezebox 3
>>>>
>>>> Kevin
>>>>
>>>> Well, I'm not actually running any version of Slimserver
yet!
>>>>
>>>> I've got a bit of a lashup streaming solution in the
lounge
>>>>
>> where the
>>
>>>> 'normal' hi-fi sits and the resulting quality is pretty
poor. I've
>>>> been hankering over a squeezebox but I'd really like it to
>>>>
>> work with
>>
>>>> the xAP infrastructure (caller ID etc.)
>>>>
>>>> So it's a pre-purchase question!
>>>>
>>>> It's good to hear that the conduit is under development.
Is that a
>>>> REAL soon or 'real' soon? ;-)
>>>>
>>>> regards
>>>>
>>>> Richard
>>>>
>>>> --- In xap_automation@xxxxxxx
>>>>
>> <mailto:xap_automation%40yahoogroups.com>
>>
>>>> <mailto:xap_automation%40yahoogroups.com>,
Kevin Hawkins
>>>> <lists@> wrote:
>>>>
>>>>> The issue is more to do with the version of SlimServer
than the
>>>>>
>>>> player.
>>>>
>>>>> What ver are you running. The conduit works best for
pre 6 but
>>>>>
>>>> depending
>>>>
>>>>> on your display complexities may work for V6. Also
there
>>>>>
>> will be an
>>
>>>>> alternative solution 'real soon now' that will work
nicely with
>>>>>
>>>> latest
>>>>
>>>>> SlimServer (6.51).
>>>>>
>>>>> K
>>>>>
>>>>> rb_ziggy wrote:
>>>>>
>>>>>> COuld anyone let me know if the Slimp plugins work
for
>>>>>>
>>>> displaying on
>>>>
>>>>>> the the latest Squeezebox 3?
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> Richard
>>>>>>
>>>>>>
>>>>>>
>>>> __._
>>>>
>>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>
>


--------------080101010909010604090005
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01
Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">


Well that's not good! I presume you have a raw device setup to capture
data from the Slimserver? Does that device trigger any script? If it
does then could you try making a blank file called 'global.xsp' inside
the /Scripts/ folder , that may well be the issue. If not is there a
specific xAP message that triggers the issue?<br>
<br>
Thanks<br>
<br>
James<br>
&nbsp;p.s. I have played with an earlier version of Edward's slim
connector
and it really does works rather well! I'm sure it'll be out soon<br>
max wrote:
<blockquote cite="mid454C7FDC.5080805@xxxxxxx"
type="cite">
<pre wrap="">James,

I've just found that using the old xFx slim connector causes a hard
crash of floorplan! Tried it with both service and GUI versions on the
same machine as floorplan, and the GUI on another pc. All crash
floorplan with a "Run time error '52':Bad file name or number".
Seems to happen as soon as the slim conduit starts sending messages.

Max

rb_ziggy wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Ditto here! I'd be v interested too.

I've now got the squeezebox 3, cracking bit of kit but haven't
succeeded in getting messages to it yet. The current conduit does
seem to see the traffic and will show some messages on the softqueeze
version but then seems to hang up.

rgds

Richard

--- In <a class="moz-txt-link-abbreviated" href="mailto:xap_automation@xxxxxxx";>xap_automation@xxxxxxx</a>
<a class="moz-txt-link-rfc2396E" href="mailto:xap_automation%40yahoogroups.com";>&lt;mailto:xap_automation%40yahoogroups.com&gt;</a>,
max <a class="moz-txt-link-rfc2396E" href="mailto:max@...";>&lt;max@...&gt;</a>
wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Just wondering if you're any nearer to posting
the new conduit, Edward?

Max

Edward Pearson wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Available now! (coding is done, I just need to
put it up on my
</pre>
</blockquote>
</blockquote>
<pre wrap="">website...)
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">
</pre>
</blockquote>
</blockquote>
<pre
wrap="">----------------------------------------------------------
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">*From:* <a
class="moz-txt-link-abbreviated" href="mailto:xap_automation@xxxxxxx";>xap_automation@xxxxxxx</a>
</pre>
</blockquote>
</blockquote>
<pre wrap=""><a class="moz-txt-link-rfc2396E"
href="mailto:xap_automation%40yahoogroups.com";>&lt;mailto:xap_automation%40yahoogroups.com&gt;</a>
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">[<a class="moz-txt-link-freetext"
href="mailto:xap_automation@xxxxxxx";>mailto:xap_automation@xxxxxxx</a>
</pre>
</blockquote>
</blockquote>
<pre wrap=""><a class="moz-txt-link-rfc2396E"
href="mailto:xap_automation%40yahoogroups.com";>&lt;mailto:xap_automation%40yahoogroups.com&gt;</a>]
*On Behalf Of *rb_ziggy
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">*Sent:* 28 October 2006 15:15
*To:* <a class="moz-txt-link-abbreviated" href="mailto:xap_automation@xxxxxxx";>xap_automation@xxxxxxx</a>
</pre>
</blockquote>
</blockquote>
<pre wrap=""><a class="moz-txt-link-rfc2396E"
href="mailto:xap_automation%40yahoogroups.com";>&lt;mailto:xap_automation%40yahoogroups.com&gt;</a>
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">*Subject:* [xap_automation] Re: xAP on
Squeezebox 3

Kevin

Well, I'm not actually running any version of Slimserver yet!

I've got a bit of a lashup streaming solution in the lounge
</pre>
</blockquote>
</blockquote>
<pre wrap="">where the
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">'normal' hi-fi sits and the resulting quality
is pretty poor. I've
been hankering over a squeezebox but I'd really like it to
</pre>
</blockquote>
</blockquote>
<pre wrap="">work with
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">the xAP infrastructure (caller ID etc.)

So it's a pre-purchase question!

It's good to hear that the conduit is under development. Is that a
REAL soon or 'real' soon? ;-)

regards

Richard

--- In <a class="moz-txt-link-abbreviated" href="mailto:xap_automation@xxxxxxx";>xap_automation@xxxxxxx</a>
</pre>
</blockquote>
</blockquote>
<pre wrap=""><a class="moz-txt-link-rfc2396E"
href="mailto:xap_automation%40yahoogroups.com";>&lt;mailto:xap_automation%40yahoogroups.com&gt;</a>
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""><a class="moz-txt-link-rfc2396E"
href="mailto:xap_automation%40yahoogroups.com";>&lt;mailto:xap_automation%40yahoogroups.com&gt;</a>,
Kevin Hawkins
&lt;lists@&gt; wrote:
</pre>
<blockquote type="cite">
<pre wrap="">The issue is more to do with the version of
SlimServer than the
</pre>
</blockquote>
<pre wrap="">player.
</pre>
<blockquote type="cite">
<pre wrap="">What ver are you running. The conduit works
best for pre 6 but
</pre>
</blockquote>
<pre wrap="">depending
</pre>
<blockquote type="cite">
<pre wrap="">on your display complexities may work for V6.
Also there
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">will be an
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">alternative solution 'real soon now' that will
work nicely with
</pre>
</blockquote>
<pre wrap="">latest
</pre>
<blockquote type="cite">
<pre wrap="">SlimServer (6.51).

K

rb_ziggy wrote:
</pre>
<blockquote type="cite">
<pre wrap="">COuld anyone let me know if the Slimp plugins
work for
</pre>
</blockquote>
</blockquote>
<pre wrap="">displaying on
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">the the latest Squeezebox 3?

Thanks

Richard


</pre>
</blockquote>
</blockquote>
<pre wrap="">__._
</pre>
</blockquote>
</blockquote>
<pre wrap="">
</pre>
</blockquote>
<pre wrap=""><!---->



xAP_Automation Main Index | xAP_Automation Thread Index | xAP_Automation Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.