Bug 13348 - playlist index ?<LF> does not return an index
: playlist index ?<LF> does not return an index
Status: RESOLVED INVALID
Product: Logitech Media Server
Classification: Unclassified
Component: CLI
: 7.4.0
: PC Windows Vista
: -- normal (vote)
: 7.4.0
Assigned To: Squeezebox QA Team email alias
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-08-12 03:06 UTC by Joggs
Modified: 2009-08-17 01:20 UTC (History)
1 user (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Joggs 2009-08-12 03:06:14 UTC
Hi,
<playerid> playlist index ?<LF> does not return the id for the currently playing song in the playlist for me using SC 7.4 latest build.

According to the cli help example:
Request: "04:20:00:12:23:45 playlist index ?<LF>"
Response: "04:20:00:12:23:45 playlist index 5<LF>"

ALSO when entering the command the CLI pushes out an erroneous string on the listener channel as this: <playerid> playlist newsong <songtitle> %3F%3CLF%3E   

As you can see the current song index is actually an escaped string for ?<LF>
Comment 1 James Richardson 2009-08-13 09:13:53 UTC
Michael: is this one yours to address?
Comment 2 Michael Herger 2009-08-13 10:22:33 UTC
Works for me. 

You don't enter the "<LF>", do you? It means you send a line feed, typically by hitting the enter key when testing in telnet.

QA - can you reproduce this issue?
Comment 3 Michael Herger 2009-08-13 10:23:31 UTC
Actually - from your comment I see you did enter the <LF>. After all it's what you got in the response. Don't type it. Hit Enter.
Comment 4 Joggs 2009-08-16 09:48:24 UTC
(In reply to comment #3)
> Actually - from your comment I see you did enter the <LF>. After all it's what
> you got in the response. Don't type it. Hit Enter.

Well, as I program a player in C# I have a method that I use for all my cli commands that do exactly the same thing at each command and it always work, but not for this command.

My method adds the question mark and the linefeed i.e \r\n after the actual command and that has always worked but not for this command so that feels strange.

So even if you can get it to work with telnet it seems like the parsing of the linefeed that I use, which is \r\n in a c-3 string, doesn't work?
Comment 5 Michael Herger 2009-08-17 01:20:24 UTC
Please turn on debugging for the CLI queries/command (Settings/Advanced/Logging) and upload the output you get from SC when submitting that command.