Different skip methods?

[pippin]

I had a report that iPeng has an issue skipping tracks on a mclient player (supposedly using slimp3 protocol) connected to SC. It is reported to pause for 10-15s when skipping. It's also claimed that the default skin does not show this behavior.

What I do in iPeng to skip tracks is to call

playlist index +1
or
playlist index -1

through the JSON/RPC I/F. Is there anything I can do different to improve skipping behavior?

[andyg]

On Jun 16, 2008, at 8:38 AM, pippin wrote:

>
> I had a report that iPeng has an issue skipping tracks on a mclient
> player (supposedly using slimp3 protocol) connected to SC. It is
> reported to pause for 10-15s when skipping. It's also claimed that the
> default skin does not show this behavior.
>
> What I do in iPeng to skip tracks is to call
>
> playlist index +1
> or
> playlist index -1
>
> through the JSON/RPC I/F. Is there anything I can do different to
> improve skipping behavior?

Shouldn't you be using playlist jump +1 instead?

[Fred]

Use command debug to discover what commands other skins are using. Playlist index +1 sounds right.

[andyg]

On Jun 16, 2008, at 8:51 AM, Andy Grundman wrote:

>
> On Jun 16, 2008, at 8:38 AM, pippin wrote:
>
>>
>> I had a report that iPeng has an issue skipping tracks on a mclient
>> player (supposedly using slimp3 protocol) connected to SC. It is
>> reported to pause for 10-15s when skipping. It's also claimed that
>> the
>> default skin does not show this behavior.
>>
>> What I do in iPeng to skip tracks is to call
>>
>> playlist index +1
>> or
>> playlist index -1
>>
>> through the JSON/RPC I/F. Is there anything I can do different to
>> improve skipping behavior?
>
> Shouldn't you be using playlist jump +1 instead?

Oops, playlist index is the same thing as playlist jump, so I don't
know why it doesn't work. Especially if the default skin works.

[mherger]

> playlist index +1
> or
> playlist index -1

For consistency reason with the IR remote (and Controller) I'm using ['button', 'jump_fwd'] in the web interface. This will also handle "intelligent" fwd/back to the beginning of a track etc.

--

Michael

[pippin]

> playlist index +1
> or
> playlist index -1

For consistency reason with the IR remote (and Controller) I'm using ['button', 'jump_fwd'] in the web interface. This will also handle "intelligent" fwd/back to the beginning of a track etc.

OK, so that could behave differently then? I'll try that.
What exactly is "intelligent" fwd/back (that is, how many seconds does it skip back vs. jump to the start)? I'm doing this myself at the moment.

playlist jump +1

is undocumented, I should not use that, shouldn't I?