mirror of
https://github.com/owntone/owntone-server.git
synced 2025-03-31 01:33:44 -04:00
[docs] README update
This commit is contained in:
parent
ea184a2844
commit
bbb5d16ac3
27
README.md
27
README.md
@ -97,14 +97,21 @@ probably obsolete when you read it :-)
|
|||||||
|
|
||||||
## Using Remote
|
## Using Remote
|
||||||
|
|
||||||
If you plan to use Remote with forked-daapd, read the following sections
|
If you plan to use Remote for iPod/iPhone/iPad with forked-daapd, read the
|
||||||
carefully. The pairing process described is similar for other controllers, but
|
following sections. The pairing process described is similar for other
|
||||||
some do not require pairing.
|
controllers/remotes (e.g. Retune), but some do not require pairing.
|
||||||
|
|
||||||
### Pairing with Remote on iPod/iPhone
|
### Pairing with Remote on iPod/iPhone
|
||||||
|
|
||||||
forked-daapd can be paired with Apple's Remote application for iPod/iPhone/iPad;
|
If you just started forked-daapd for the first time, then wait til the library
|
||||||
this is how the pairing process works:
|
scan completes before pairing with Remote (see [library](#library)). Otherwise
|
||||||
|
you risk timeouts. Then do the following.
|
||||||
|
|
||||||
|
The Quick Way:
|
||||||
|
|
||||||
|
1. Download and run the helper script from [here](https://raw.githubusercontent.com/ejurgensen/forked-daapd/master/scripts/pairinghelper.sh)
|
||||||
|
|
||||||
|
Or, if that doesn't work:
|
||||||
|
|
||||||
1. Start forked-daapd
|
1. Start forked-daapd
|
||||||
2. Start Remote, go to Settings, Add Library
|
2. Start Remote, go to Settings, Add Library
|
||||||
@ -340,12 +347,12 @@ informations.
|
|||||||
|
|
||||||
The library is scanned in bulk mode at startup, but the server will be available
|
The library is scanned in bulk mode at startup, but the server will be available
|
||||||
even while this scan is in progress. You can follow the progress of the scan in
|
even while this scan is in progress. You can follow the progress of the scan in
|
||||||
the log file.
|
the log file. When the scan is complete you will see the log message: "Bulk
|
||||||
|
library scan completed in X sec".
|
||||||
|
|
||||||
Of course, if files have gone missing while the server was not running a request
|
The very first scan will take longer than subsequent startup scans, since every
|
||||||
for these files will produce an error until the scan has completed and the file
|
file gets analyzed. At the following startups the server looks for changed files
|
||||||
is no longer offered. Similarly, new files added while the server was not
|
and only analyzis those.
|
||||||
running won't be offered until they've been scanned.
|
|
||||||
|
|
||||||
Changes to the library are reflected in real time after the initial scan. The
|
Changes to the library are reflected in real time after the initial scan. The
|
||||||
directories are monitored for changes and rescanned on the fly. Note that if you
|
directories are monitored for changes and rescanned on the fly. Note that if you
|
||||||
|
Loading…
x
Reference in New Issue
Block a user