-
Notifications
You must be signed in to change notification settings - Fork 4
Playslave API
Matt Windsor edited this page Jun 25, 2014
·
7 revisions
- An implementation of playslave uses a text-based protocol, for reasons of ease of debugging, manual control of playslave without a frontend, and transparency.
- The API is separated into requests, sent from the frontend/user to playslave, and responses, sent from playslave to the frontend/user.
- Requests and responses both take the form
WORD arg1 arg2… argn, where arguments are either single words or quoted strings (use\"to escape a string), andWORDis a four-character identifier (lowercase for requests, uppercase for responses).
-
Syntax:
play - Valid when: stopped
-
Syntax:
stop - Valid when: playing
-
Usage:
load FILE - Valid when: in any state
-
Syntax:
ejct - Valid when: not ejected
-
Syntax:
seek TIME - Valid when: not ejected
-
Syntax:
quit - Valid when: in any state
-
Syntax:
OHAI MESSAGE
-
Syntax:
TIME MICROSECONDS
-
Syntax:
TTFN MESSAGE
-
Syntax:
WHAT MESSAGE