RE: Slim connector problem (slightly long description!)

["Paul Gordon" <paul@xxxxxxxxxxxxxxxxxxxxx>]

More Info...

I've been able to install the service version OK, and it seems to be
working... (Homeseer detected a new device OK)

I've also got a slim display showing on xAP-desktop which "sort
of"
works, - but somehow the desktop display has managed to get a bit out of
step with the real slim display....

Some observations:

Using the slim remote, I queued up a track (that actually I shouldn't
have), which couldn't play since it is a WAV file, and I have a slim not
a squeeze.  However the new slimserver software showed it for selection
and I forgot it was a WAV so selected it without realising my mistake.
Obviously the slim didn't *actually* play anything...

So (again with the remote), I selected a different (MP3 this time) file,
& pressed "Play" on the remote, thus removing the previous
track, and
replacing it with the new one. The slim device correctly shows "Now
Playing (1 of 1)", however the desktop display shows "Now playing
(2 of
1)" and shows the correct track details on the 2nd line.

Using the remote to pause & unpause the player doesn't cause the
correct
transport status to show up on the desktop display; - it never changes
to "Paused (x of x)" but remains steadfastly on "Now
playing...."

The same is true if I use the slim remote to turn the player off, - the
desktop display remains on "Now playing..."

Using the slim remote, I go back to the browse selection and select
another track, - I press "Play" on the remote to replace the
playing
track with the new one... - The desktop display correctly updates the
track details in the 2nd line, but still doesn't update the (x of x)
part  - it sill says "(2 of 1)"

Using the slim remote, I add another track to the playlist by using the
"REC" button to append another track, the slim now correctly
displays
"(2 of 2)" on the VFD, but still the desktop part does not
update. -
Still says "(2 of 1)"

I let the first track finish and the slim moves on to the next track (in
reality 2 of 2). The desktop display correctly updates to the new track
details on line 2, and this time the 1st line *does* update, :-)  but
not correctly... :-(    It has updated to say "(3 of 2)"

I let the 2nd track finish, the slim stops playing, and the VFD
correctly displays "Stopped (1 of 2)", but the desktop display
does not
update at all, and still says "Now Playing (3 of 2)" Also,
because the
slim has reached the end of the playlist, it returns to the top entry,
so the 2nd line on the VFD shows the track name of track no. 1 (as it
should, since it also says "1 of 2"), however, the track display
on line
2 of the desktop viewer does not follow that behaviour and continues to
show the track details for track 2 (the last track played).

Finally, - using the buttons on the xAP-desktop slim display to
pause/unpause/stop the player does work correctly (at the transport
level), - the slimp3 correctly plays/pauses/stops as appropriate, and
the VFD shows the correct status. But yet again, the desktop display
never shows any transport status other than "Now playing" - even
when it
has just issued a pause or a stop command, which has been actioned by
slimserver.... And in this case line 1 has updated the (x of x) count to
something closer to (but still not correct) the real situation.... - it
has changed to say "(2 of 2)" - so at least the number of tracks
in the
playlist has updated to the correct number, however, the slimp3 is
actually playing track "(1 of 2)" Line 2 on the desktop display
is at
this point showing the track name of track 1 (which is correct). I then
pressed the "next track" button on the xAP-desktop slimp3
display, and
the slim obeyed, - I was about to say the desktop display did not update
in any to reflect that, but actually I've just noticed that it has - but
it seemed to take quite a while to do it... - now it has reverted to
"(3
of 2)" but at least line 2 is showing the correct track name...

Now I appreciate that I probably confused it by trying to load an
invalid track (WAV) into he playlist the first time round, but having
done so, the desktop display seems determined not to "sync"
properly
with the real situation.... It's also disconcerting that the transport
status (playing, paused or stopped) or the slim's power status (of /
off) does not seem to be reported by desktop, - is this how it should
be?

One other slightly odd thing...  When I started up the slim connector
service the Homeseer plugin correctly detected the new device and
launched the new hardware wizard, much as I expected...

However, the first time I used the slim remote to pause the player,
Homeseer again launched the new hardware wizard and created another
device (which I wasn't expecting) - what's that all about?

- Is there ay debugging that I can turn on to help diagnose this?

- *should* the desktop display correctly report the transport status?

As much as I want to, I don't think I can currently use the desktop slim
display with these inaccuracies.... :-(

Cheers.

Paul G.





> -----Original Message-----
> From: Paul Gordon
> Sent: 11 June 2004 09:10
> To: xap_automation@xxxxxxx
> Subject: [xap_automation] Slim connector problem
>
> I just failed at the very first hurdle trying to install the GUI
version
> of
> the slim connector... :-(
>
> As soon as I run slimserverconnector.exe to install it, I get the
> following
> error:
>
>
------------------------------------------------------------------------
--
> -------------------------------
> SlimserverConnector.exe - Common Language Runtime Debugging Services
>
> Application has generated an exception that could not be handled
>
> Process id = 0xf24 (3876), Thread id = 0x4b0 (1200)
>
> Click OK to terminate the application
> Click CANCEL to debug the application
>
------------------------------------------------------------------------
--
> ------------------------------
>
>
> Any ideas?
>
> Thanks
>
> Paul G.
>
>
>
>
> ------------------------ Yahoo! Groups Sponsor
>
>
> Yahoo! Groups Links
>
>
>
>
>